Revamping the entire platform was an imperative decision made by the management to elevate the technical infrastructure and enrich the user experience.
2025
Senior UX Designer
Figma, Condens, Excel, Doc
❝ From legacy limitations to limitless possibilities ❞
❝ From legacy limitations to limitless possibilities ❞
❝ From legacy limitations to limitless possibilities ❞
About the Project
About the Project
Revamp is a crucial step in upgrading our platform’s content, structure, format, navigation to significantly enhance user experience, performance and building a design system. As part of this process, my role is to ensure a smooth and seamless user experience throughout the platform.
Revamp is a crucial step in upgrading our platform’s content, structure, format, navigation to significantly enhance user experience, performance and building a design system. As part of this process, my role is to ensure a smooth and seamless user experience throughout the platform.
Outcome
The revamp was a successful upgrade of the platform while retaining the existing user base and helped in getting new users.
The revamp was a successful upgrade of the platform while retaining the existing user base and helped in getting new users.
300
300
%
%
Increase in core feature adoption rate
240
240
%
%
Reduction in task completion time
480
480
%
%
Increase in feature discoverability
❝ Change is not an event; it’s a process ❞
❝ Change is not an event; it’s a process ❞
❝ Change is not an event; it’s a process ❞
Talked to Users
Talked to Users
Talked to Users
We visited user on field and did virtual meetings, took interviewed in-order to find the specific problem in workflow that they use in their day to day life
We visited user on field and did virtual meetings, took interviewed in-order to find the specific problem in workflow that they use in their day to day life
Audit Current Design
Audit Current Design
Audit Current Design
We audited the existing platform using usability heuristics to identify usability issues, inconsistencies, and opportunities for improvement.
We audited the existing platform using usability heuristics to identify usability issues, inconsistencies, and opportunities for improvement.
Inconsistencies in the Platform
Inconsistencies in the Platform
Inconsistencies in the Platform
Over time, multiple features were built independently, leading to inconsistent patterns, interactions, and visual styles across platform.
Over time, multiple features were built independently, leading to inconsistent patterns, interactions, and visual styles across platform.
Identify key problem areas
Identify key problem areas
Identify key problem areas
Analyze the findings to highlight the most critical usability issues impacting user experience and workflow.
Analyze the findings to highlight the most critical usability issues impacting user experience and workflow.
Project Strategy
Project Strategy
Project Strategy
We decided to divide the revamp into two phase:
We decided to divide the revamp into two phase:
Phase 1: To improve the current platform with minimum effort and high impact work.
Phase 2: Entire redesign of the platform
Phase 1: To improve the current platform with minimum effort and high impact work.
Phase 2: Entire redesign of the platform
Phase 1: Improving the Current Platform (Optimization Phase)
Phase 1: Improving the Current Platform (Optimization Phase)
Phase 1: Improving the Current Platform (Optimization Phase)
Phase Improve the system with low effort and High impact
Goal: Reduce friction, improve usability, and increase operational efficiency without changing core architecture.
The phase that will stabilizes the system.
Phase 2: Revamp Entire Platform (Transformation Phase)
Phase includes architectural and product innovation.
Goal: Move from reactive operations to proactive, data-driven fleet intelligence.
The phase that will change the entire platform
❝ This is just the beginning of something big ❞
❝This is just the beginning of something big❞
❝ This is just the beginning of something big ❞
Objectives
Objectives
Centralized Design System
Simplifying Information Architecture
Inroducting persistent breadcrumbs, global search and smart filters
Applying WCAG Principles
Role-based dashboard customization
Leverage Mixpanel event tracking to fullest
Added new features like smart reports and notification etc.
Centralized Design System
Simplifying Information Architecture
Inroducting persistent breadcrumbs, global search and smart filters
Applying WCAG Principles
Role-based dashboard customization
Leverage Mixpanel event tracking to fullest
Added new features like smart reports and notification etc.
Centralized Design System
Simplifying Information Architecture
Inroducting persistent breadcrumbs, global search and smart filters
Applying WCAG Principles
Role-based dashboard customization
Leverage Mixpanel event tracking to fullest
Added new features like smart reports and notification etc.
We started by prioritising features and pages based on weighted scoreing system, moving away from subjective decisions to a data backed roadmap.
We started by prioritising features and pages based on weighted scoreing system, moving away from subjective decisions to a data backed roadmap.
Phase 2: Revamp Entire Platform (Transformation Phase)
Phase 2: Revamp Entire Platform (Transformation Phase)
The phase that will change the entire platform
Goal: Move from reactive operations to proactive, data-driven fleet intelligence.
Phase includes architectural and product innovation.
The phase that will change the entire platform
Goal: Move from reactive operations to proactive, data-driven fleet intelligence.
Phase includes architectural and product innovation.
Solution
Solution
Solution
The redesign wasn’t just about improving the interface. It was restructuring how the product worked in users’ minds, shifting it from scattered features to a unified ecosystem.
The redesign wasn’t just about improving the interface. It was restructuring how the product worked in users’ minds, shifting it from scattered features to a unified ecosystem.
Building the
Design
System
Foundation
Building the
Design
System
Foundation
Before
Before
The platform had no design system. Each module used different components, layouts, and interaction patterns, leading to an inconsistent and fragmented experience.
The platform had no design system. Each module used different components, layouts, and interaction patterns, leading to an inconsistent and fragmented experience.
The platform had no design system. Each module used different components, layouts, and interaction patterns, leading to an inconsistent and fragmented experience.
After
After
We established a scalable design system, defining reusable components, consistent interaction patterns, and a unified visual language. This improved usability for users and accelerated feature development for the product team.
We established a scalable design system, defining reusable components, consistent interaction patterns, and a unified visual language. This improved usability for users and accelerated feature development for the product team.
We established a scalable design system, defining reusable components, consistent interaction patterns, and a unified visual language. This improved usability for users and accelerated feature development for the product team.
Eliminating Dead Ends with Contextual Navigation
Eliminating Dead Ends with Contextual Navigation
Eliminating Dead Ends with Contextual Navigation
Before
Before
Before
The legacy platform created “dead ends” pages that stopped users from continuing their investigation. If an anomaly appeared in a report, users had to leave the page, navigate elsewhere, and reconstruct the same filters.
The legacy platform created “dead ends” pages that stopped users from continuing their investigation. If an anomaly appeared in a report, users had to leave the page, navigate elsewhere, and reconstruct the same filters.
The legacy platform created “dead ends” pages that stopped users from continuing their investigation. If an anomaly appeared in a report, users had to leave the page, navigate elsewhere, and reconstruct the same filters.
After
After
After
We redesigned the experience around contextual navigation, turning data points into interactive drill-downs. This connected previously isolated modules and enabled continuous investigative workflows, allowing users to move from insight to action without losing context.
We redesigned the experience around contextual navigation, turning data points into interactive drill-downs. This connected previously isolated modules and enabled continuous investigative workflows, allowing users to move from insight to action without losing context.
We redesigned the experience around contextual navigation, turning data points into interactive drill-downs. This connected previously isolated modules and enabled continuous investigative workflows, allowing users to move from insight to action without losing context.
Reducing Cognitive Load by Prioritizing What Matters
Reducing Cognitive Load by Prioritizing What Matters
Reducing Cognitive Load by Prioritizing What Matters
Before
Before
Before
Over time, the client-specific customizations created a bloated interface where every user saw every feature.
Over time, the client-specific customizations created a bloated interface where every user saw every feature.
Over time, the client-specific customizations created a bloated interface where every user saw every feature.
After
After
After
We led a feature weightage exercise, evaluating each feature based on usage patterns and business value. Features with low relevance were deprioritized or hidden, which significantly reducing cognitive load.
Outcome: This streamlined the interface and significantly reduced cognitive load, helping users focus on the tools that mattered most.
We led a feature weightage exercise, evaluating each feature based on usage patterns and business value. Features with low relevance were deprioritized or hidden, which significantly reducing cognitive load.
Outcome: This streamlined the interface and significantly reduced cognitive load, helping users focus on the tools that mattered most.
We led a feature weightage exercise, evaluating each feature based on usage patterns and business value. Features with low relevance were deprioritized or hidden, which significantly reducing cognitive load.
Outcome: This streamlined the interface and significantly reduced cognitive load, helping users focus on the tools that mattered most.
Outcome
The revamp was a successful upgrade of the platform while retaining the existing user base and helped in getting new users.
300
%
Increase in core feature adoption rate
240
%
Reduction in task completion time
480
%
Increase in feature discoverability
Learnings
Learnings
Learnings
The revamp was a successful upgrade of the platform but something which can be happened in past
The revamp was a successful upgrade of the platform but something which can be happened in past
Not every feature deserves equal visibility. Prioritizing features based on user needs and business value is essential to reduce cognitive load and create a focused product experience.
Feature bloat is not just a product problem, it’s a usability problem. Regularly evaluating features through usage data and user needs helps maintain a clean, scalable interface.
Design is not only about adding functionality but also about making deliberate decisions on what to hide or deprioritize. Strategic simplification can significantly improve usability.
Not every feature deserves equal visibility. Prioritizing features based on user needs and business value is essential to reduce cognitive load and create a focused product experience.
Feature bloat is not just a product problem, it’s a usability problem. Regularly evaluating features through usage data and user needs helps maintain a clean, scalable interface.
Design is not only about adding functionality but also about making deliberate decisions on what to hide or deprioritize. Strategic simplification can significantly improve usability.
Not every feature deserves equal visibility. Prioritizing features based on user needs and business value is essential to reduce cognitive load and create a focused product experience.
Feature bloat is not just a product problem, it’s a usability problem. Regularly evaluating features through usage data and user needs helps maintain a clean, scalable interface.
Design is not only about adding functionality but also about making deliberate decisions on what to hide or deprioritize. Strategic simplification can significantly improve usability.
Thank you for watching
If you like what you see and want to work together, get in touch!
ruchikasdesign@gmail.com
Thank you for watching
If you like what you see and want to work together, get in touch!
ruchikasdesign@gmail.com
Phase stabilizes the system.
Phase stabilizes the system.
Phase stabilizes the system.
Goal: Reduce friction, improve usability, and increase operational efficiency without changing core architecture.
Goal: Reduce friction, improve usability, and increase operational efficiency without changing core architecture.
Goal: Reduce friction, improve usability, and increase operational efficiency without changing core architecture.
The phase that will stabilizes the system.
Phase Improve the system with low effort and High impact
Phase Improve the system with low effort and High impact