03
Case Study

Platform
Navigation

Defining Behavior Before Visuals.

// AT A GLANCE
ROLE UX Architect · Information Architecture · Interaction Spec
SCOPE 6 acquired products, 4 post-acquisition codebases, enterprise security platform
PROBLEM 4 acquisitions brought 4 navigation systems. Users switching products felt like changing apps — 40% of menu links were redundant, active states were contradictory, deep links broke between suites
Role
UI Designer, UX Architect
Timeline
2024
Status
Shipped

The company had 6 distinct products that were being merged into a single "Platform." However, each product had its own navigation logic. Users felt like they were leaving one website and entering another every time they switched tools.
The tech debt was massive.

The Goal

A unified navigation framework.

We needed a single source of truth for routing that solved three core issues:

Implementation

Phases to production.

01
Phase 1: Information Architecture (IA)

I audited every menu item across 6 products. I discovered that 40% of the links were redundant. I proposed a "Hub and Spoke" model:
The Global Bar: Product switcher, User profile, Global search.
The Side Rail: Contextual navigation for the active product.

02
Phase 2: Interactive States & Tokens

Navigation isn't just a list of links; it's a series of behaviors. I defined:
Active state logic: What happens when a user is in a sub-sub-menu?
Hover behaviors: Delay timings for fly-out menus to prevent "diagonal mouse" frustration.
Responsiveness: A "Slim" vs. "Expanded" state for the sidebar.

03
Phase 3: The Handoff

Instead of just handing off Figma files, I delivered a Navigation Matrix—a spreadsheet mapping every URL path to a navigation state. This became the source of truth for the engineering team.

The Impact
01
Reduced TTM: Engineering now uses a single JSON-driven navigation module, significantly reducing frontend dev time.
02
User Success: Established a consistent mental model for users moving between products, reducing navigation errors and friction.
03
Operational Efficiency: Eliminated the "logic gaps" in handoff, cutting down QA cycles related to navigation bugs.
04
System Adoption: The logic defined here became the standard for future platform components, proving the value of a token-driven interaction model.
Reflection
"I learned that polished visuals fail if behavior is unclear. My goal was to create a system with straightforward rules so teams could build confidently."

A key refinement was the site-switching experience. Initially, complex controls confused users about their location. By simplifying the tenant switcher from a search box to a dropdown and moving it to the top global bar, I provided a clear "where am I?" anchor. This small shift in IA made the entire platform feel more integrated.

// READ REPORT Want to go deeper?
View Detailed Case Study →
Next Case Study
Login Redesign