We redesigned an operations platform that had grown feature by feature over several years. Navigation, dashboards, forms and common workflows became easier for everyday users, and no important features were removed.
Industry: Professional & Business ServicesService: Design & StrategyUpdated
Overview
The challenge
Years of growth had added menus, screens, settings and workflows with no consistent design. Long-time users had learned workarounds, while new users needed too much training.
The company did not want a cosmetic refresh. It needed people to understand the product and complete real tasks more simply.
Users were unsure where to find important actions and information.
Common tasks took too many screens, clicks and repeated fields.
Different parts of the product looked and behaved like separate systems.
The solution
We mapped the main workflows, support pain points, navigation problems and the tasks users do most often.
We removed unneeded steps, made page layouts clearer and reorganised information around what users are trying to do.
Shared components, patterns, forms, tables and states give the whole product a consistent feel.
Before and after
Before
Organised by feature
Users had to understand how the product was built to find things.
After
Organised by task
Navigation follows what users are trying to get done.
Before
Too many steps
Common actions meant moving back and forth between screens.
After
Fewer steps
Frequent tasks need fewer decisions and screens.
Before
Mixed patterns
Each module behaved in its own way.
After
One shared system
Reusable patterns make the product easier to learn.
Key features
Design decisions are based on real tasks and the friction users hit, not on visual taste alone.
Business impact
A more useful redesign
Pages, menus and content are organised around how users think about their work.
Business impact
Faster learning
Consistent components make future features quicker to design and build.
Business impact
A more consistent product
Results
Better Usability
Users can see more easily where to go and what to do next.
Before: ConfusingAfter: Clearer
Easier Adoption
New users meet fewer inconsistent patterns as they find their way around.
Before: High FrictionAfter: Consistent
Faster Future Delivery
Teams reuse shared patterns instead of redesigning common elements each time.
Before: RepeatedAfter: Reusable
Faster delivery
Reusing these tested components cut repeated setup, so the redesigned product reached users sooner.
Kept role-based access working while menus and screens were reorganised.
Let the redesigned screens draw on the product's existing data and integrations.
Tracked errors as the new screens rolled out, so problems could be fixed quickly.
Gave the product one consistent way to confirm actions, show errors and flag items that need attention.
Trust and control
The redesign keeps role-based access, so users see only the information and actions their role needs.
Access controlledCustomer, day-to-day and product information stays linked as users move between modules.
ConnectedMonitoring and clear error handling keep the product dependable as more people use the new design.
ReliableThe client owns the redesigned product, workflows, integrations and source code.
100% ownedYears of growth had added menus, screens, settings and workflows with no consistent design. Long-time users relied on workarounds, new users needed too much training, and common tasks took too many clicks. The company wanted people to complete real tasks more simply, not a cosmetic refresh of the same screens.
We started by mapping the main workflows, support pain points and the tasks users do most often. Navigation was then organised around those tasks instead of product features, unneeded steps were removed and page layouts were made clearer. Key features stayed in the product, but they became easier to find and use.
The design system gives the product shared components, patterns, forms, tables and states, so every module looks and behaves the same way. That makes the product easier for new users to learn. It also means the team can design and build future features faster, because common elements no longer need redesigning.
If long-time users rely on workarounds and new users need too much training, we can help you redesign around the tasks people actually do.