Why journey management has to prove itself first | Marc Stickdorn, JourneyOps Stockholm 2026
JourneyOps
0:00 / 0:00
Why journey management has to prove itself first | Marc Stickdorn, JourneyOps Stockholm 2026
71 просмотр · 11 дней назад
JourneyOps
56 подписчиков
71 просмотр · 11 дней назад
Marc Stickdorn, founder of Smaply, opened JourneyOps Stockholm with a situation most journey management teams will recognise. Somewhere in every organisation, someone is going through a spreadsheet of budgets and deciding what to keep and what to cut. His talk is about how to get journey management onto that spreadsheet as something worth funding, and why a journey map on its own is not a business case.
The first challenge is how journey management usually gets introduced. Teams pitch the methodology and ask the organisation to believe in it. Executives hear a request for a lot of trust and a lot of money, with an uncertain result. Marc's advice is to start in stealth mode: projects that are small enough to learn from, real enough to prove something and safe enough to try. That means low risk work, short cycles, real metrics and a deliberately boring name such as process optimisation. It also means calculating the return on investment for every project, because stealth without measurement is just hiding.
The second challenge is proving value in your own organisation. Examples from big companies are easy to wave away with "yes, but we are different". Marc suggests first taking stock of the maps you already have and learning which goals and metrics the organisation cares about, such as cost, churn, retention and risk. Look at who sponsored past CX projects and why. Then pick your first journey the way an investor would. Go for fast impact over the biggest impact, somewhere you already have data and are allowed to change things. Estimate the impact as a range before you start, for example by working out how many calls a pain point causes and what each call costs.
The third challenge is showing that the first result was not luck. Repeat the approach on two or three more journeys. Track several KPIs instead of one, because a single KPI always gets gamed. Report results instead of methodology, and use the organisation's language: talk about avoidable cost, not frustrated customers. Marc's "wall of pain" puts pain points, their cost and the budget needed to fix them on one map. That way funding becomes an investment decision.
Only after that should you build a governance structure. Marc explains why journey management needs service design capacity to act on decisions instead of collecting thousands of insights. He also covers why it should plug into the decision structures you already have, and why journey roles need to be part of people's actual job descriptions. Map levels should match the levels where decisions are made, and the tool should be chosen last, once you know how the work runs in your organisation.
He closes with a preview of scaling. Make journey knowledge available in the tools people already use, including AI tools. He also introduces the tic-tac-toe model from research for his upcoming book, which shows that organisations run journey management for different aims, such as strategic value, alignment between teams or efficiency. In the Q&A he explains how to estimate value for new products using prototypes and ranges.
Recorded at JourneyOps Stockholm on 30 September 2026. Marc opened the day, and it was great to have him back on the JourneyOps stage.
Chapters
00:00 Introduction
00:50 Getting journey management onto the budget spreadsheet
01:30 A journey map is not a business case
02:50 Why pitching the methodology fails
04:45 Start in stealth mode
06:00 Choose a boring name
06:30 Calculate the return on investment
07:40 Prove, repeat, govern, then scale
08:15 Understand your organisation and its metrics
10:05 Pick your first journey like an investor
11:00 Estimate impact as a range
12:00 Repeat on more journeys and use several KPIs
13:40 Show results and speak business language
14:50 The wall of pain
16:00 Building governance on existing decision structures
18:20 Make it part of the job description
19:30 Choose the tool last
21:15 Previews on scaling journey management
23:00 The tic-tac-toe model
26:45 Q&A: estimating value
About JourneyOps
JourneyOps is a global community for journey management practitioners. Want to be part of the conversation and get help from other journey management practitioners. Join the JourneyOps Circle: www.journey-ops.com
#JourneyManagement #CustomerExperience #ServiceDesign #CX #JourneyOps #Smaply