Change Management & Adoption

The Change Management Challenge

Implementing Journeys Management requires significant organizational change. It asks teams to think differently, work differently, and embrace new processes and tools. Without intentional change management, even the best methodology will fail to gain traction.

This chapter provides strategies for building adoption, overcoming resistance, and fostering cultural transformation.

Understanding Resistance

Anticipate and address sources of resistance proactively.

Common Sources of Resistance

"We already do this"

Belief: Current journey mapping or user research is sufficient

Reality: Journeys Management is operational practice, not one-time projects

Response: Show gaps in current approach—fragmented insights, missing measurement, no systematic improvement

"Too much process"

Belief: This adds bureaucracy and slows work down

Reality: Structure enables rather than constrains when designed well

Response: Demonstrate efficiency gains—better prioritization, less rework, clearer requirements

"Not enough time"

Belief: Teams are too busy to adopt new practices

Reality: Journey approach ultimately saves time through better decisions

Response: Start small with pilot, show quick wins, gradually expand rather than boiling the ocean

"This threatens my role"

Belief: Journey-centric approach diminishes individual/team importance

Reality: Journey work elevates importance of user understanding across organization

Response: Clarify roles, show how journey work enhances rather than replaces existing responsibilities

"Our situation is different"

Belief: Methodology won't work in our unique context

Reality: Principles adapt to any domain with customization

Response: Acknowledge uniqueness, involve skeptics in adaptation, demonstrate flexibility

Change Strategy Framework

Apply structured change management approach.

Kotter's 8-Step Change Model Applied to Journeys Management

1. Create Urgency

Build compelling case for why change is needed:

1. Share user pain points and frustrations

2. Quantify cost of current fragmentation

3. Highlight competitive threats from poor experience

4. Present business risks of status quo

2. Form Coalition

Build guiding team of champions:

1. Secure executive sponsor

2. Recruit cross-functional advocates

3. Include influential skeptics who become believers

4. Give coalition authority and resources

3. Create Vision

Articulate clear picture of future state:

1. What will journey-centric organization look like?

2. How will this benefit users and business?

3. What will be different in daily work?

4. How will success be measured?

4. Communicate Vision

Share vision repeatedly through multiple channels:

1. Town halls and team meetings

2. Internal newsletters and communications

3. Workshop introductions and training

4. Executive messaging reinforcing importance

5. Empower Action

Remove obstacles and enable participation:

1. Provide necessary tools and training

2. Allocate time for journey work

3. Address structural barriers

4. Celebrate early adopters

6. Create Quick Wins

Demonstrate value early with visible successes:

1. Select high-impact pilot journeys

2. Deliver improvements rapidly

3. Measure and communicate results

4. Use wins to build momentum

7. Build on Change

Use momentum to tackle bigger challenges:

1. Expand to more journeys

2. Deepen integration with product process

3. Increase sophistication of practices

4. Scale across teams and departments

8. Anchor in Culture

Make journey-centricity "how we work":

1. Update role descriptions and expectations

2. Incorporate into performance evaluation

3. Make journey knowledge prerequisite for decisions

4. Tell stories celebrating journey-driven successes

Building Advocacy Network

Create network of champions throughout organization.

Journey Champions Program

Establish formal or informal champion network:

Champion Roles:

1. Advocate for journey thinking in their teams

2. Participate in journey research and workshops

3. Share journey insights with colleagues

4. Provide feedback on journey practices

5. Model journey-centric behaviors

Champion Support:

1. Regular community gatherings

2. Advanced training and skill development

3. Direct access to journey management leaders

4. Recognition and visibility for contributions

Cross-Functional Working Groups

Create collaborative forums:

1. Journey Review Board: Cross-functional group evaluating priorities and opportunities

2. Research Community of Practice: Practitioners sharing methods and learnings

3. Product-Journey Sync: Regular alignment between product and journey teams

Training & Enablement

Build organizational capability through structured learning.

Training Curriculum

Develop role-based training:

Journey Fundamentals (All staff):

1. What is Journeys Management and why it matters

2. How journeys are structured and measured

3. How to access and use journey insights

4. How to think in journey terms

Format: 1-hour intro session or self-paced learning

Journey Research Methods (Designers, researchers, product):

1. How to conduct journey research

2. Mental model and blueprint creation

3. Opportunity identification and documentation

4. Integration with product development

Format: Half-day workshop with practice exercises

Journey Measurement (Analytics, product, operations):

1. Journey metrics framework

2. Data instrumentation and tracking

3. Dashboard creation and interpretation

4. Connecting metrics to improvements

Format: Half-day technical workshop

Journey Leadership (Executives, managers):

1. Strategic value of journey management

2. How to prioritize and allocate resources

3. Leading journey-centric transformation

4. Measuring and communicating impact

Format: Executive briefing or strategy session

Learning Resources

Provide ongoing learning support:

1. Journey Playbook: This document as reference

2. Tool Templates: Ready-to-use frameworks and formats

3. Case Studies: Examples from your organization

4. Office Hours: Regular sessions for questions and support

5. Internal Community: Space for practitioners to connect and share

Pilot Projects

Demonstrate value through focused proof-of-concept efforts.

Pilot Selection Criteria

Choose pilots with high success probability:

Characteristics of Good Pilots:

1. Clear pain points with measurable impact

2. Manageable scope—can show results in 1-2 quarters

3. Cross-functional involvement demonstrating collaboration

4. Visible to organization—success will be noticed

5. Supportive stakeholders willing to experiment

Avoid:

1. Journeys with complex political dynamics

2. Overly large scope taking too long to show results

3. Journeys requiring massive technical investment

4. Areas with hostile stakeholders

Pilot Execution

Run pilots with discipline and rigor:

1. Establish baseline: Document starting state clearly

2. Apply methodology: Follow journey management process faithfully

3. Measure impact: Track both process and outcome metrics

4. Document learnings: Capture what worked and what needs adjustment

5. Share results: Communicate successes and challenges transparently

Scaling from Pilots

Use pilot success to expand:

1. Present results to leadership and stakeholders

2. Share lessons learned and methodology refinements

3. Identify next wave of journey priorities

4. Allocate additional resources based on proven value

5. Expand gradually rather than trying to scale overnight

Communication Strategy

Consistent communication builds awareness and support.

Communication Channels

Use multiple channels reaching different audiences:

1. Executive briefings: Quarterly updates to leadership

2. All-hands presentations: Share progress and wins with full organization

3. Team meetings: Regular touchpoints with involved teams

4. Internal newsletter: Stories and updates in existing communications

5. Intranet/wiki: Centralized information and resources

6. Workshops and trainings: Hands-on engagement and learning

Communication Messaging

Tailor messages to audience concerns:

For Executives: Strategic value, business impact, competitive advantage, ROI

For Product Teams: Better prioritization, clearer requirements, reduced rework, user validation

For Operations: Reduced manual work, fewer escalations, happier users, process efficiency

For Engineering: Clearer requirements, less ambiguity, better alignment, meaningful impact

For All Staff: Improved user experiences, organizational pride, customer satisfaction

Success Storytelling

Make journey impact tangible through stories:

Story Elements:

1. User name and situation (anonymized if needed)

2. Specific pain point or struggle they faced

3. How journey research revealed the issue

4. What improvement was made

5. Actual impact on user and business

6. Quote from user about improved experience

Real stories create emotional connection and demonstrate value more effectively than statistics alone.

Success Criteria for This Chapter

After implementing change management, you should have:

• Identified sources of resistance and mitigation strategies

• Executive sponsorship and guiding coalition actively engaged

• Journey champions network across organization

• Role-based training curriculum delivered

• Successful pilot projects demonstrating value

• Multi-channel communication reaching all stakeholders

• Momentum building for expanded adoption

Common Pitfalls to Avoid

Underestimating resistance: Change is hard—expect pushback and plan for it

Top-down mandate without support: Executive mandate isn't enough without enablement, tools, and reinforcement

Moving too fast: Attempting full-scale implementation before demonstrating value creates backlash

Inconsistent messaging: Mixed messages from leadership or contradictory priorities undermine adoption

Celebrating process over outcomes: Focus on user and business impact, not just completing journey maps