The Multi-Product UX Roadmap: Governing Experience Across Business Units
Here's what happens in large enterprises:
2018: Business Unit A builds a user management interface. Cost: $180K.
2019: Business Unit B needs user management. But they don't know Unit A already built it. They build their own. Cost: $165K.
2020: Business Unit C acquires a smaller company. That company has its own user management system. Now there are three.
2021: Corporate IT mandates SSO (Single Sign-On) for security compliance. All three systems need to be updated.
- Unit A's version: 6 weeks, $120K
- Unit B's version: 8 weeks, $140K
- Unit C's version: 12 weeks (legacy codebase), $200K
Total spent on user management across 3 business units: $805K
If they'd built it once and shared it: $180K initial + $120K SSO update = $300K
Money wasted: $505K. On one feature.
Now multiply that by:
- Authentication flows
- Settings screens
- Notification systems
- Search interfaces
- Dashboard templates
- Form builders
- File upload components
- Payment flows
This is the silo problem.
And it's costing enterprises millions of dollars every year.
The Silo Problem in Enterprise UX
In large companies (especially those with multiple business units, acquisitions, or legacy products), UX teams face a unique challenge:
Decentralized product development leads to duplicated effort, inconsistent experiences, and massive technical debt.
Here's how it happens:
The Typical Enterprise Structure
Enterprise Company ($2B+ revenue)
├─ Business Unit A: Healthcare SaaS
│ ├─ Product Team (10 engineers, 2 designers)
│ └─ Builds: Patient Management System
│
├─ Business Unit B: Medical Devices
│ ├─ Product Team (8 engineers, 1 designer)
│ └─ Builds: Device Management Portal
│
├─ Business Unit C: Billing & Insurance
│ ├─ Product Team (12 engineers, 2 designers)
│ └─ Builds: Claims Processing Platform
│
└─ Legacy Products (from acquisitions)
├─ Product D: EHR System (acquired 2016)
├─ Product E: Telehealth App (acquired 2019)
└─ Product F: Analytics Dashboard (acquired 2021)
The Problems This Creates
Problem 1: Redundant Development
Each business unit builds the same features independently:
- User authentication (3 versions)
- Role-based permissions (4 versions)
- Notification preferences (3 versions)
- Search functionality (5 versions)
- Data export (4 versions)
Problem 2: Inconsistent User Experience
Users who interact with multiple products (common in B2B) encounter:
- Different navigation patterns
- Inconsistent terminology ("Users" vs "Members" vs "Accounts")
- Different interaction patterns (keyboard shortcuts work differently)
- Varying visual design (colors, spacing, typography)
Problem 3: Compounding Technical Debt
Legacy products aren't maintained:
- Accessibility compliance? Only in 2 of 6 products
- Design system adoption? Only in the newest product
- Mobile responsive? 3 of 6 products
- Modern frameworks? Only products built after 2020
Problem 4: Inefficient Design Teams
Designers waste time:
- Reinventing solutions that already exist
- Creating custom components instead of using shared libraries
- Fighting for resources to fix basic usability issues
- Negotiating brand consistency across products
The Cost:
One enterprise I worked with calculated:
- $4.2M/year in duplicated engineering effort (building the same features multiple times)
- $1.8M/year in maintenance costs (updating 5 versions of the same feature)
- $900K/year in customer support costs (users confused by inconsistent UX)
- $600K/year in lost sales (prospects confused by product overlap)
Total: $7.5M/year wasted due to lack of UX governance.
The Solution: A Centralized Multi-Product UX Roadmap
A Multi-Product UX Roadmap is a strategic plan that:
- Maps all products and identifies redundancy
- Establishes governance tiers (mandatory, system, BU-specific)
- Coordinates UX work across business units
- Translates design initiatives into executive-level ROI
Think of it as UX-level architecture governance—like enterprise IT architecture, but for the experience layer.
Phase 1: The Audit Layer (Identifying Redundancy)
Before you can govern, you need to know what you're governing.
Step 1: Map All Products
Create a complete inventory:
| Product Name | Business Unit | Year Launched | Users | Tech Stack | Design System? |
|---|
| Patient Portal | Healthcare | 2018 | 45K | React 16 | No (custom) |
| Device Manager | Medical Devices | 2019 | 12K | Angular 8 | No (custom) |
| Claims Platform | Billing | 2020 | 8K | React 17 | Partial (v1.0) |
| EHR System (legacy) | Healthcare | 2010 (acquired) | 78K | jQuery | No |
| Telehealth App | Healthcare | 2019 (acquired) | 23K | Vue 2 | No |
| Analytics Dashboard | Cross-BU | 2021 | 5K | React 18 | Yes (v2.0) |
Step 2: Map Shared Features
For each product, list core features and identify overlap:
| Feature | Patient Portal | Device Manager | Claims Platform | EHR (legacy) | Telehealth | Analytics | Redundancy Level |
|---|
| User Authentication | ✓ (custom) | ✓ (custom) | ✓ (SSO) | ✓ (legacy) | ✓ (OAuth) | ✓ (SSO) | 6 versions |
| Role Management | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | 6 versions |
| Notification Settings | ✓ | ✓ | - | ✓ | ✓ | - | 4 versions |
| Search | ✓ | ✓ | ✓ | ✓ | - | ✓ | 5 versions |
| Data Export | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | 6 versions |
| Settings/Preferences | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | 6 versions |
| Help/Documentation | ✓ | ✓ | - | ✓ | ✓ | - | 4 versions |
Analysis:
Step 3: Quantify Technical and UX Debt
For each legacy product, assess:
| Product | WCAG Compliance | Mobile Responsive | Design System | Modern Framework | Debt Score (0-100) |
|---|
| Patient Portal | Partial (AA) | Yes | No | Yes (React 16) | 35 (moderate debt) |
| Device Manager | No | No | No | Partial (Angular 8) | 65 (high debt) |
| Claims Platform | Yes (AA) | Yes | Partial | Yes (React 17) | 20 (low debt) |
| EHR (legacy) | No | No | No | No (jQuery) | 90 (critical debt) |
| Telehealth | Partial (A) | Yes | No | Yes (Vue 2) | 40 (moderate debt) |
| Analytics | Yes (AA) | Yes | Yes | Yes (React 18) | 10 (minimal debt) |
Debt Score Calculation:
- WCAG Compliance: 25 points
- Mobile Responsive: 20 points
- Design System: 30 points
- Modern Framework: 25 points
Total = 100 points. Lower score = higher debt.
Findings:
Phase 2: The Three-Tier Alignment Strategy
Once you've mapped redundancy and debt, organize work into three tiers:
Tier 1: Mandatory (Corporate-Level Initiatives)
Definition:
Projects tied to company-wide goals, compliance requirements, or risk mitigation.
Characteristics:
- Applies to all products
- Non-negotiable (driven by legal, security, or corporate strategy)
- Funded centrally (not from BU budgets)
Examples:
| Initiative | Rationale | Scope | Timeline | Budget |
|---|
| WCAG 2.2 AA Compliance | Legal requirement (ADA, accessibility lawsuits) | All 6 products | 18 months | $1.2M |
| GDPR Data Privacy Updates | European market compliance | All products with EU users (4 of 6) | 12 months | $800K |
| SSO Migration | Security mandate (reduce password breaches) | All products | 9 months | $600K |
| Rebrand (Visual Identity) | Corporate rebrand | All customer-facing products (5 of 6) | 6 months | $400K |
Why Tier 1 Matters:
Without centralized governance, each BU would handle these independently:
- 6 separate WCAG compliance projects (instead of 1 coordinated effort)
- Inconsistent implementation (some products fully compliant, others not)
- Wasted budget (duplicated audits, training, testing)
Centralized Approach:
- Hire a central accessibility team
- Create shared compliance checklist and components
- Train all designers once (not 6 times)
- Audit products centrally
Savings: 40% less cost, 50% faster completion
Tier 2: System Investment (Design Infrastructure)
Definition:
Projects that build shared systems, components, or platforms used by multiple business units.
Characteristics:
- Benefits multiple products
- Reduces future development costs
- Funded centrally or cost-shared across BUs
Examples:
| Initiative | Benefiting Products | ROI | Timeline | Budget |
|---|
| Enterprise Design System v3.0 | All 6 products | $800K/year savings (reduced dev time) | 12 months | $500K |
| Centralized Component Library | 5 products (excluding legacy EHR) | $600K/year savings | 9 months | $350K |
| Shared Authentication Service | All 6 products | $400K/year savings (maintenance) | 6 months | $300K |
| Universal Search API | 5 products | $200K/year savings | 6 months | $180K |
Example: Enterprise Design System v3.0
Problem:
- 6 products, 5 different design languages
- Each product rebuilds common components (buttons, forms, modals)
- Inconsistent UX across products
Solution:
Build a centralized design system with:
- Figma component library (shared across all designers)
- React component library (shared code components)
- Design tokens (colors, spacing, typography)
- Documentation and usage guidelines
ROI Calculation:
Before Design System:
- Each product builds 50 components independently
- Average cost per component: $2,000 (design + dev)
- Total cost: 5 products × 50 components × $2,000 = $500K/year
After Design System:
- Build 50 components once: $100K
- Maintenance: $50K/year
- BUs customize only 10% of components: 5 products × 5 components × $2,000 = $50K
- Total: $200K first year, $100K/year after
Savings: $300K/year after year 1
Additional Benefits:
- Faster feature development (designers reuse components instead of designing from scratch)
- Consistency (users encounter familiar patterns across products)
- Easier onboarding (new designers learn one system, not six)
Tier 3: BU-Specific (Unique Features)
Definition:
Projects unique to a single business unit, tied to their specific revenue goals or user needs.
Characteristics:
- Only benefits one product
- Funded by the BU
- Not governed centrally (but should use shared components from Tier 2)
Examples:
| Business Unit | BU-Specific Features | Rationale | Budget |
|---|
| Healthcare | Patient appointment scheduling | Unique to healthcare workflows | $250K |
| Medical Devices | Device firmware update flow | Unique to hardware products | $180K |
| Billing | Insurance claim auto-adjudication | Unique to billing domain | $300K |
Why Tier 3 Matters:
BUs need autonomy to innovate and compete. But they should:
- Use Tier 2 design system components (for consistency)
- Follow Tier 1 compliance requirements (for legal/security)
- Share learnings (if a feature succeeds, consider promoting to Tier 2)
Example:
Healthcare BU builds a patient appointment scheduling feature using the shared design system:
- Uses shared Calendar component (from Tier 2)
- Uses shared Form components (from Tier 2)
- Custom logic for healthcare-specific workflows (Tier 3)
Result:
- 60% faster development (reused components)
- Consistent UX (familiar patterns)
- Healthcare-specific value (custom scheduling logic)
Phase 3: Communicating Value to Executives
Executives don't care about design systems or component libraries. They care about:
- Cost savings
- Revenue impact
- Risk mitigation
- Competitive advantage
Your job: Translate UX initiatives into executive-level metrics.
Translation Framework
| UX Initiative | Executive Metric | How to Calculate |
|---|
| Design System Adoption | Reduced Development Costs | $X saved per feature × Y features/year |
| WCAG Compliance | Legal Risk Mitigation | Potential lawsuit cost ($M) × probability |
| Centralized Authentication | Reduced Maintenance Costs | $X/year × 6 products vs $Y/year × 1 service |
| Legacy Modernization | Reduced Support Costs | Support tickets × cost per ticket |
| Consistent UX | Increased NPS | NPS increase → retention increase → revenue impact |
Example 1: Design System ROI
UX Initiative:
"Adopt Enterprise Design System v3.0 across all products"
Executive Translation:
"Reduce feature development costs by $800K/year"
Supporting Data:
Before Design System:
- Average time to build a feature: 6 weeks (4 weeks design, 2 weeks dev)
- Average cost: $50K per feature
- Features built per year (across 6 products): 60
- Total: $3M/year
After Design System:
- Average time to build a feature: 3.5 weeks (1 week design with reusable components, 2.5 weeks dev)
- Average cost: $30K per feature
- Features built per year: 60
- Total: $1.8M/year
Savings: $1.2M/year
ROI:
- Design system build cost: $500K (one-time)
- Annual savings: $1.2M
- Payback period: 5 months
- 3-year ROI: $3.6M - $500K = $3.1M
Example 2: Legacy Modernization ROI
UX Initiative:
"Modernize EHR (legacy) product"
Executive Translation:
"Reduce support costs by $600K/year and eliminate $2M legal risk"
Supporting Data:
Current State (Legacy EHR):
- Monthly support tickets: 2,400
- Average ticket cost: $45
- Annual support cost: $1.3M
Issues:
- Not WCAG compliant (accessibility lawsuit risk: $2M)
- Not mobile responsive (40% of users request mobile, causing support tickets)
- Slow performance (20% of tickets are "app is slow")
After Modernization:
- Support tickets reduced by 45% (research shows modern UX reduces confusion)
- Monthly support tickets: 1,320
- Annual support cost: $712K
Savings:
- Support: $1.3M - $712K = $588K/year
- Legal risk mitigation: $2M (one-time)
Total Value: $2.588M
Modernization Cost: $1.2M
Payback Period: 2 years
Example 3: Centralized Authentication ROI
UX Initiative:
"Build shared SSO service to replace 6 custom authentication systems"
Executive Translation:
"Reduce authentication maintenance costs by $400K/year and improve security posture"
Supporting Data:
Current State (6 Custom Systems):
- Annual maintenance per system: $90K
- Total: $540K/year
Issues:
- Security vulnerabilities (each system has different security standards)
- Password reset support tickets (15% of all support volume)
- Inconsistent login UX (users complain about "logging in differently for each product")
After Centralized SSO:
- Single system maintenance: $140K/year
- Savings: $400K/year
Additional Benefits:
- Security improvement (one hardened system vs. six fragmented systems)
- Reduced support tickets (one password reset flow)
- Better UX (users log in once, access all products)
Modernization Cost: $300K
Payback Period: 9 months
Building the Multi-Product UX Roadmap
Here's what a complete multi-product roadmap looks like:
Example: 18-Month Roadmap
Q1 (Months 1-3): Discovery & Foundation
Tier 1 (Mandatory):
Tier 2 (System Investment):
Tier 3 (BU-Specific):
- Healthcare: Patient Portal redesign (approved)
- Medical Devices: Mobile app beta (in progress)
Q2 (Months 4-6): Compliance & Quick Wins
Tier 1:
Tier 2:
Tier 3:
- Healthcare: Appointment scheduling feature
- Billing: Claims auto-adjudication
Q3 (Months 7-9): System Rollout
Tier 1:
Tier 2:
Tier 3:
- Medical Devices: Firmware update flow redesign
Q4 (Months 10-12): Adoption & Optimization
Tier 1:
Tier 2:
Tier 3:
- (No major BU-specific work; focus on Tier 2 adoption)
Q5-Q6 (Months 13-18): Legacy Modernization
Tier 1:
Tier 2:
Tier 3:
- Healthcare: Telehealth integration v2.0
Governance Structure: Who Owns What?
A multi-product roadmap requires clear ownership:
Organizational Model
Chief Design Officer (CDO)
├─ Design System Team (centralized)
│ ├─ Leads Tier 2 (System Investment)
│ ├─ Supports Tier 1 (Mandatory)
│ └─ Provides components for Tier 3 (BU-Specific)
│
├─ Compliance & Accessibility Team (centralized)
│ └─ Leads Tier 1 (WCAG, GDPR, Security)
│
└─ BU-Embedded Design Teams
├─ Healthcare Design Team (3 designers)
│ └─ Leads Tier 3 for Healthcare products
├─ Medical Devices Design Team (2 designers)
│ └─ Leads Tier 3 for Device products
└─ Billing Design Team (2 designers)
└─ Leads Tier 3 for Billing products
Decision-Making Framework
| Tier | Decision Owner | Approval Required From | Budget Owner |
|---|
| Tier 1 (Mandatory) | CDO / Compliance Lead | Executive team (CEO, CFO, Legal) | Corporate (centralized) |
| Tier 2 (System) | Design System Lead | CDO | Corporate or cost-shared |
| Tier 3 (BU-Specific) | BU Design Lead | BU Product Leader | Business Unit |
Common Challenges and How to Overcome Them
Challenge 1: "Our BUs Are Too Different"
The Objection:
"Healthcare and Medical Devices serve different users. A shared design system won't work."
The Reality:
80% of UI patterns are universal:
- Forms, buttons, modals, navigation
- Authentication, settings, notifications
- Search, filters, data tables
Only 20% are domain-specific.
The Solution:
- Build the 80% as Tier 2 (shared components)
- Allow 20% customization as Tier 3 (BU-specific)
Example:
Shared (Tier 2):
- Button component
- Form inputs
- Modal patterns
Healthcare-Specific (Tier 3):
- Patient chart component
- HIPAA-compliant consent forms
Challenge 2: "We Don't Have Budget for Centralized Teams"
The Objection:
"We can't afford a centralized design system team. BUs should handle their own UX."
The Counter-Argument:
You're already paying for it—just inefficiently.
Show the Math:
Current State (Decentralized):
- 5 BUs × 2 designers each = 10 designers
- Each designer spends 30% of time building components
- Cost: 10 designers × $120K salary × 30% = $360K/year on component work
Centralized Design System Team:
- 2 full-time design system designers: $240K/year
- Savings: $120K/year
- Plus: Components are higher quality, consistent, and reusable
Challenge 3: "BUs Won't Adopt the Design System"
The Problem:
You build a design system, but BUs keep building custom components.
Why It Happens:
- Design system doesn't meet their needs (missing components)
- Design system is hard to use (poor documentation)
- No incentive to adopt (BUs measured on delivery speed, not consistency)
The Solution:
1. Make Adoption Easy
- Provide Figma libraries (designers can drag-drop)
- Provide code components (engineers can import)
- Provide templates (common page layouts pre-built)
2. Align Incentives
- Tie BU bonuses to design system adoption (e.g., "80% of new features use design system components")
- Show time savings (features built 40% faster with design system)
3. Provide Support
- Office hours (design system team answers questions)
- Slack channel (quick support)
- Workshops (train designers on new components)
Conclusion: UX Governance is a Cost-Saving Measure
Here's the fundamental truth:
UX governance isn't about control. It's about eliminating waste.
When you govern UX across business units, you:
- Eliminate redundancy (stop building the same feature 6 times)
- Reduce maintenance costs (update once, not six times)
- Improve consistency (users encounter familiar patterns)
- Accelerate development (reuse components instead of rebuilding)
- Mitigate risk (centralized compliance is easier to manage)
The ROI is measurable:
Example Enterprise Savings (18-Month Roadmap):
- Design system adoption: $1.2M/year saved (reduced dev costs)
- Centralized authentication: $400K/year saved (maintenance)
- Legacy modernization: $600K/year saved (support costs)
- WCAG compliance (centralized): $2M risk mitigation (legal)
Total: $2.2M/year + $2M risk mitigation
Investment: $2.5M (one-time)
Payback: 13 months
The conversation shifts from:
❌ "Why did we build this twice?"
✅ "How much did we save by building it once?"
And that's a conversation executives understand.
Want to learn more about strategic UX leadership?
Have you managed UX across multiple products or business units? What governance challenges have you faced?
