Context
Customers relied on this platform to do critical work, but the experience demanded constant interpretation.
Screens were overloaded with information. Statuses were unclear. Small decisions carried outsized consequences. Users often had to rely on sales representatives or support teams to complete tasks that should have been straightforward.
Internally, there was a strong desire to improve the experience, but limited appetite for risk. Any change needed to preserve accuracy, compliance, and trust.
The tension was not between simplicity and complexity.
It was between clarity and confusion.
The Tension
Customers relied on this platform to do critical work, but the experience demanded constant interpretation.
Screens were overloaded with information. Statuses were unclear. Small decisions carried outsized consequences. Users often had to rely on sales representatives or support teams to complete tasks that should have been straightforward.
Internally, there was a strong desire to improve the experience, but limited appetite for risk. Any change needed to preserve accuracy, compliance, and trust.
The tension was not between simplicity and complexity.
It was between clarity and confusion.
The Misalignment
Much of the existing experience reflected how the system worked internally, not how customers thought about their work.
Information was technically correct, but poorly sequenced. Critical context was buried. Different roles saw similar screens but interpreted them very differently.
There was also inconsistency in visual language and interaction patterns, making it harder for users to build confidence over time.
The system was doing a lot.
It just was not helping people understand what it was doing.
How I Approached It
I focused on reducing cognitive load without reducing capability.
Rather than redesign everything at once, I worked iteratively, using interactive prototypes to explore how information could be grouped, revealed, and explained more intentionally. Complex scenarios were mapped end to end so that edge cases were understood before they became problems.
Customer conversations played a critical role. While internal teams understood the business deeply, customers brought clarity about where confusion actually surfaced and what information mattered most at each step.
Design decisions were reviewed collaboratively, with an emphasis on preserving trust. Changes needed to feel not only easier, but safer.
What Shifted
As the experience evolved, users spent less time interpreting the system and more time acting within it.
Ordering flows became easier to follow. Status and next steps were clearer. Information felt purposeful rather than overwhelming.
The system did not become simpler in terms of logic.
It became simpler to use.
Support interactions decreased. Confidence increased. Customers could focus on their work rather than on navigating the platform itself.
Why It Mattered
This project showed that clarity is not about removing complexity. It is about making complexity navigable.
By respecting the sophistication of the work while improving how it was presented, the platform became a better partner to its users. It reduced friction without diminishing trust.
It reinforced an idea central to my approach: when people understand what a system is asking of them, they can move through it with confidence instead of caution.
