The product had been built over 20 years for highly regulated industries, financial services, insurance, healthcare, utilities. It was deeply capable. But two decades of feature accumulation had created a product that required weeks of onboarding, 32 separate navigation modules, and an implementation process so complex it needed dedicated professional services teams just to get customers live.
The mandate was clear: take this battle-tested on-premises platform and bring it to the cloud as a modern SaaS product, without losing the power and flexibility that enterprise customers depended on. The challenge wasn't just a visual refresh. It was a fundamental rethinking of how a deeply complex product could serve multiple use cases across diverse regulated industries without overwhelming the humans using it every day.
The hardest part wasn't the design. It was understanding the system well enough to know what could change and what couldn't.
I led the UX and product design effort for the SaaS migration, working across product management, engineering, and enterprise customer stakeholders. My responsibilities spanned from early discovery and information architecture through interaction design, design system development, and customer validation.
Before touching any design tool, I spent time deeply understanding the product, its data model, its customer use cases across industries, and how the existing 32 modules mapped to real user workflows. I couldn't simplify what I didn't understand.
I worked directly with enterprise customers to map their end-to-end workflows, identify where the existing navigation structure broke down, and understand which complexity was essential versus accidental. This was the foundation for every structural decision that followed.
The 32-module structure had grown organically over two decades without a coherent organizational principle. I led the effort to reframe the entire IA around user goals rather than system features, consolidating 32 modules to 8 without removing a single core capability.
Working in close cycles with engineering and product, I built and tested prototypes with real users across multiple regulated industry verticals. Every structural change was validated before it was built.
Alongside the product redesign, I led the development of a scalable design system that could support the platform's multi-use-case requirements across industries, enabling faster future development and consistent experiences.
The biggest lesson from this project was the importance of earning trust before proposing change. In a product with 20 years of customer history, every structural decision carried weight, customers had built their entire communication operations around the existing architecture. Proposing to consolidate 32 modules to 8 required deep credibility built through research, not assumptions.
I also learned that complexity in enterprise products is rarely accidental. Most of it exists for a reason, often a very good one. The design challenge isn't to eliminate complexity, but to absorb it so the user doesn't have to.