Part 1 · Foundation
03
13 min read
Chapter 3

Building the Business Case

Connect user pain to business impact

Six elements turn Journeys Management from a design initiative into a funded organizational capability with executive sponsorship.

USER PAIN“I gave up at step 4.”“It took 3 calls.”“I couldn’t find it.”TRANSLATEBUSINESS IMPACT40% abandonment300 manual cases / wkCSAT 2.1 / 5
Fig. 03 · Pain → Impact bridgeA business case translates user friction into business language.

Why the Business Case Matters

Even with leadership support, Journeys Management implementation requires investment—in tools, people, time, and organizational change. A compelling business case secures necessary resources and sets clear success metrics.

Your business case must speak to both user experience improvements and tangible business outcomes. It should address the "what," "why," "how," and "what's in it for us."

Components of a Strong Business Case

A complete business case includes six essential elements:

1. Problem Statement

Clearly articulate the challenge Journeys Management will address, connecting user pain to business impact.

User Problem: Describe current experience gaps and user frustrations with specific examples.

Business Impact: Quantify how the current state affects business metrics—costs, satisfaction scores, efficiency, revenue loss.

Example Problem Statement: "Users struggle to complete [specific goal] efficiently, resulting in 40% abandonment at [step], requiring manual staff intervention in 300 cases weekly, costing $X annually. User satisfaction for this journey scores 2.1/5, creating risk of churn and negative perception."

2. Proposed Solution

Explain what Journeys Management is and how it addresses the identified problems.

Solution Overview: Describe the practice you'll establish—not just initial mapping, but ongoing management system.

Methodology Summary: Briefly explain the four-phase approach (discovery, measurement, prioritization, operationalization).

Differentiation: Clarify how this differs from existing practices—not just one-time projects but continuous operational capability.

3. Expected Outcomes

Define specific, measurable outcomes for both users and business.

User Experience Outcomes

  1. Increased completion rates for priority journeys

  2. Improved satisfaction scores across key touchpoints

  3. Reduced time and effort required to accomplish goals

  4. Decreased user-reported pain points and frustrations

PROBLEMSOLUTIONOUTCOMESAPPROACHRISKMETRICSCASE
Fig. 3.2 · Six componentsA funded case anchors on all six — missing one weakens the whole.

Business Outcomes

  1. Operational cost reductions through process improvements

  2. Efficiency gains from reduced manual interventions

  3. Revenue protection or growth through improved retention

  4. Competitive advantage through superior experiences

Set realistic targets based on your assessment findings and industry benchmarks.

4. Implementation Approach

Outline how you'll establish the practice over time.

Phased Roadmap: Show staged implementation, starting with pilot journeys and expanding based on learning.

Resource Requirements: Specify needed roles, tools, budget, and time commitments from stakeholders.

Timeline: Provide realistic timeframes for each phase—expect 12-18 months to full maturity.

Quick Wins: Identify early deliverables that will demonstrate value and build momentum.

5. Risk Assessment & Mitigation

Acknowledge potential challenges and how you'll address them.

Common Risks

  1. Stakeholder resistance to new ways of working

  2. Resource constraints limiting implementation pace

  3. Technical limitations in measurement capabilities

  4. Cultural barriers to cross-functional collaboration

  5. Competing priorities pulling focus elsewhere

For each risk, provide specific mitigation strategies.

6. Success Metrics

Define how you'll measure whether Journeys Management delivers promised value.

Leading Indicators (Early signals of progress)

  1. Number of journeys mapped and measured

  2. Research studies completed and insights generated

  3. Cross-functional workshops and collaborations

  4. Opportunities identified and prioritized

Lagging Indicators (Actual outcome measures)

  1. Journey performance metrics improvements

  2. User satisfaction score increases

  3. Operational cost reductions

  4. Business KPI impacts (retention, revenue, efficiency)

Building Stakeholder-Specific Cases

Different stakeholders care about different aspects. Tailor your message:

Reference table · 6 rows
Stakeholder
Executive Leadership
Key Messages
Strategic differentiation, business metrics, ROI
Stakeholder
Product/Service Teams
Key Messages
Better prioritization, user insights, impact clarity
Stakeholder
Operations
Key Messages
Reduced manual work, process efficiency, clear pain points
Stakeholder
Technology
Key Messages
Better requirements, aligned roadmaps, reduced rework
Stakeholder
Finance
Key Messages
Cost reduction opportunities, resource optimization
Stakeholder
Customer Service
Key Messages
Fewer escalations, better tools, empowered users
STAKEHOLDERKEY MESSAGEExecutiveDifferentiation, ROIProductBetter prioritizationOperationsLess manual workFinanceCost reductionCustomer serviceFewer escalations
Fig. 3.3 · Tailor the messageOne case, many translations — meet each stakeholder in their language.

Presenting the Business Case

Structure your presentation to build logical flow:

  1. Start with the problem—make it real and costly

  2. Introduce Journeys Management as the solution approach

  3. Show the implementation roadmap and quick wins

  4. Present expected outcomes with realistic targets

  5. Address risks honestly with mitigation plans

  6. End with clear ask and next steps

Use concrete examples and data from your assessment. Avoid jargon—make the case accessible to non-specialists.

Securing the Commitment

Beyond initial approval, secure ongoing commitment:

Executive Sponsorship: Identify a senior leader who will champion the initiative and remove barriers.

Steering Committee: Establish a cross-functional group to guide implementation and ensure alignment.

Resource Allocation: Get formal commitment of needed people, budget, and time from relevant teams.

Success Reviews: Schedule regular check-ins to review progress and demonstrate value being delivered.

Success Criteria for This Chapter

You're ready to proceed when you have:

  • Documented business case connecting user needs to business outcomes

  • Stakeholder-specific value propositions for key audiences

  • Secured executive sponsorship and resource commitments

  • Defined success metrics and review cadence

  • Established governance structure for implementation

Journeys Management

A field guide to operating Journey Management as a continuous practice—not a workshop deliverable.

For
  • Service Designers
  • Journey Management Practitioners
  • CX Strategists
  • Product & Design Leaders
Edition

v1.0 · Interactive companion to the Journeys Management Methodology Playbook.

© Journeys Management PlaybookDeveloped by Fredy Pascal