Case Study 02

Navigation & Homepage Redesign

Redesigning navigation and entry points for a growing B2B SaaS platform — creating a role-aware structure that improved clarity, scalability, and mobile adoption.

RoleLead Product Designer
Timeline[Add timeline]
PlatformWeb & Mobile (iOS/Android)
ScopeNavigation, IA, Homepage, Mobile UX
0%
Increase in mobile weekly active users ≈420 → 470 users
0%
Positive response to the new homepage.
Users believed it will meaningfully enhance their daily workflow.
0%
Faster onboarding.
New users completed their first task sooner, improving early-stage efficiency.
Click to expand
Mobile Navigation Updated - Introduced a bottom tab bar and a new homepage
Click to expand
Web Navigation Updated - Introduced grouping and hierachy to side bar navigation

This page is a concise walkthrough. For the full story behind the IA decisions, role logic, validation process, and cross-functional tradeoffs, open the complete case study deck.

View Full Case Study
The Problem

The platform had grown faster than its structure.

As the product expanded across features and platforms, navigation became increasingly fragmented. Different roles were forced through the same cluttered experience, making core workflows harder to find and understand.

What looked like a usability issue was really a systems issue: the information architecture no longer reflected how users thought about the product, and mobile inherited interaction patterns that created even more friction.

User impact
60% didn't know where to start
Users lacked a clear entry point and often felt dropped into the middle of the platform without direction.
Efficiency issue
4–5 clicks to key actions
Important workflows were buried, forcing extra navigation steps and slowing down task completion.
Behavior signal
46% of sessions used search
Search was compensating for weak navigation, becoming the fallback route instead of a complementary tool.
Business impact
Low mobile confidence
Poor mobile adoption limited growth, complicated sales conversations, and increased reliance on custom homepage setups.
Research & Discovery

Research embedded into real product decisions.

To understand whether the issue was visual, structural, or behavioral, I combined qualitative and quantitative signals: user interviews, stakeholder sessions, session recordings, and analytics. This helped us separate surface-level UI complaints from the deeper architecture problems underneath them.

01
Users needed a clearer entry point
Across roles, people described feeling "dropped into the middle." They needed orientation before action.
mediaClick to expand
Previously, users ended up landing on three different feature pages, based on their profile. The side menu wasn't intuitive enough to help users understand where to go next.
02
The navigation was role-blind
The same menu surfaced irrelevant options to everyone, reducing clarity and making prioritization harder.
mediaClick to expand
Our user base was segmented by both industry and role. While some features were relevant across multiple groups, most needs and workflows differed depending on the user’s context.
03
Mobile inherited the wrong model
The asset-first flow blocked access to org-wide features, adding friction where users needed speed and flexibility.
mediaClick to expand
Web allowed free exploration of the knowledge base; mobile required selecting a model first, limiting usability and access.
Solution

A structure based on mental models, not feature lists.

The redesign focused on creating a scalable navigation system and a more intentional entry experience. Instead of continuing to stack features into a growing menu, I restructured the product around clearer feature relationships, user goals, and role-specific relevance which then translated that logic consistently across web and mobile.

Object-oriented navigation
Reorganized the product into clearer groups like Search, Assistant, Knowledge Base, Asset Operations, and Dashboard.
Dynamic role-aware homepage
Introduced modular landing content that adapts to role and context, improving relevance without requiring custom client setups.
Mobile flow overhaul
Removed the asset-first gate and introduced bottom navigation plus interactive breadcrumbs for better orientation.
Faster knowledge capture
Reduced creation flows from 4–5 steps to 1–2, making common actions easier to access in the moment.
mediaClick to expand
Outcome

A clearer product foundation — and measurable adoption gains.

Validation showed a meaningful lift in task success, confidence, and orientation across roles. After launch, the redesigned experience supported stronger mobile adoption, improved feature discoverability, and gave the product a more scalable foundation for future growth.

Impact
This went beyond a UI cleanup and became a structural product decision.
The redesign reduced cognitive load, aligned web and mobile more closely, and made strategic features easier to surface. It contributed to a 12% increase in mobile weekly active users, helped close 3 new mobile app contracts, and reduced the need for one-off homepage configurations across clients.
Reflection

What the project reinforced.

Navigation problems are rarely just interface problems. They're structure problems. Once a product starts scaling, the quality of its information architecture directly shapes usability, discoverability, and business flexibility. Treating navigation as a strategic system rather than a menu design task changed both the product and the conversations around it.

This page is a concise walkthrough. For the full story behind the IA decisions, role logic, validation process, and cross-functional tradeoffs, open the complete case study deck.

View Full Case Study
Portfolio Case Study · Senior Product Designer
Navigation RedesignSystems ThinkingB2B SaaSInformation ArchitectureCross-Platform UXProduct Strategy