Context
The company had grown rapidly through acquisition, inheriting five separate product lines each with their own design language, navigation paradigm, and underlying user model. Customers — primarily enterprise operations teams — were forced to context-switch between disconnected interfaces to complete end-to-end workflows. The platform served mid-market and enterprise accounts generating hundreds of millions in ARR, with design reporting to the CPO.
Audit of the five legacy products revealed inconsistent navigation patterns, duplicated functionality, and conflicting information architecture.
Business Problem
The fragmented experience was directly eroding retention and competitive win rate. Internal research showed that 68% of users cited “fragmented experience” as their top frustration. Mid-market churn was accelerating as newer entrants offered unified platforms on modern stacks. The sales team was losing deals because prospects could not envision a cohesive workflow during demos.
The mandate from the CPO and CEO was clear: unify the platform experience or risk losing market position. This was not a design refresh — it was a strategic bet on whether the company could defend its installed base and unlock cross-sell across the portfolio.
Strategic Hypothesis
Rather than pursuing a big-bang rewrite, I advocated for a phased approach grounded in research-driven prioritization: unify information architecture around user goals (not product boundaries), invest in design infrastructure to accelerate delivery, and sequence rollout by customer impact to reduce migration risk.
I developed a strategic framework that connected design milestones to business KPIs — retention improvement, support ticket reduction, and expansion revenue. This gave leadership a shared language for evaluating design investment and allowed trade-off decisions with data rather than opinion. We presented quarterly roadmap updates to the board, framing each phase in terms of customer outcomes and business value.
Three-phase rollout strategy connecting design milestones to business outcomes, with validation gates between each phase.
Org & Cross-Functional Leadership
I joined as Director of Product Design reporting to the CPO, with scope that expanded to VP-level as the initiative grew. I built the team from 4 to 15 — hiring 8 designers and 3 researchers — and restructured into embedded product pods while maintaining centralized functions for design systems, research ops, and content design. This hybrid model gave pods autonomy to move fast while ensuring consistency through shared infrastructure.
Cross-functional partnership was the operating model, not an afterthought. I partnered daily with VP Engineering on technical feasibility and sequencing, with Product Management on roadmap alignment, and with Customer Success and Sales on migration risk and deal support. I introduced weekly design critiques, bi-weekly cross-pod syncs, monthly show-and-tells, and quarterly design offsites.
- Team structure: Embedded pods (design + research) per product area, with centralized systems and ops reporting to me.
- Career investment: Created leveling rubrics, career frameworks, and IC/management growth tracks. Promoted 4 designers during the initiative.
- Executive alignment: Monthly portfolio reviews with CPO and CTO. Quarterly board presentations on design ROI became a model adopted by other functions.
Org structure showing embedded product design pods, centralized research and design systems functions, and cross-functional partnerships.
Key Tradeoffs & Decisions
The design process collapsed five separate navigation models into one unified structure organized around user goals. We conducted card sorting, tree testing, and prototype testing to validate the IA before committing engineering investment. Key decisions:
- Phased migration vs. big-bang: Chose phased rollout to reduce risk and build organizational confidence. Ran beta programs with key accounts, iterated on behavioral data and qualitative feedback, and progressively migrated users. The tradeoff was maintenance overhead from running parallel experiences — compressed by investing in migration tooling and clear sunset timelines.
- Universal search + command palette: Prioritized a single entry point that worked across all product surfaces, reducing the IA learning curve and becoming the most-used navigation pattern within 3 months.
- Design system as strategic investment: Allocated a dedicated team with its own roadmap and adoption metrics. Within 8 months, component adoption reached 92%, dramatically reducing design-to-dev cycle time. The tradeoff was short-term velocity — but the compounding return justified the investment to the board.
- Role-based progressive disclosure: Rather than showing every feature to every user, implemented context-aware interfaces that reduced cognitive load by user type — a bet validated through 200+ participant tree tests.
Before and after of the core operations workflow, showing reduced steps and unified navigation.
Component library with tokens, patterns, and usage guidelines built for scale.
Unified IA model organized around user goals, validated through tree testing.
Results
40%
Reduction in task completion time
5→1
Legacy products unified
67
NPS score (from 31)
12
Designers hired and onboarded
- Retention & win rate: Unified platform experience reduced mid-market churn, simplified demos for Sales, and strengthened enterprise win rate by eliminating the top customer objection in competitive deals.
- Velocity & revenue: Design system investment accelerated feature delivery ~30%, enabling faster time-to-market on new revenue-generating capabilities across the portfolio.
- Support reduction: Navigation and workflow confusion tickets dropped 52%. Expansion revenue increased as customers discovered functionality previously buried in silos.
- Org health: Zero attrition on the core team across 14 months. 4 designers promoted. 3x retention vs. industry average.
Long-Term Impact
- Design system as platform: The system now serves 8 product teams across 3 business units with a governance and contribution model that scales without centralized bottlenecks.
- Executive design review cadence established with CPO and CTO became a permanent part of the company’s strategic planning cycle — and a model other functions adopted.
- Research infrastructure — participant panels, standardized templates, and an insight repository — made continuous discovery scalable and democratized across the org.
- Career framework and leveling rubrics created during this initiative are still in use, supporting 12+ promotions over the two years following the program.
