Experience Mapping Matters More the Faster You Move

Jim Kalbach · rss · 2026-09-08 Reader 🖥️

AI as Amplifier Code Was Never the Bottleneck Coordination Cost Mental Models & Understanding Multiplayer vs Single-Player AI Organizational Legibility

Because AI now lets every team execute fast and independently, the real risk facing organizations is uncoordinated speed, not slow speed — so experience maps matter more, not less, because they are one of the few tools that reliably turn scattered, siloed knowledge into a shared, in-the-room conversation that AI cannot produce on its own.

practical · mixed — Argumentative essay (AI speeds execution -> coordination need must grow -> experience maps are the mechanism) built almost entirely on a single extended case-study narrative rather than data or a survey of evidence; ends in an explicit call to action ('Protect it. Expand it.').

Structure

Part	Role
Opening: AI lets every team move fast and independently, creating a coordination problem, not just an opportunity.	context / problem framing
'Dashboards don't interpret themselves' — data and real-time metrics can describe what happened but not decide what to do about it together.	premise
'The map freezes a moment so you can talk about it' — defines experience mapping's function as producing a shared object for a group to argue and align around, not an answer.	core mechanism claim
'The map isn't the point' — rebuts the claim that journey mapping is obsolete by reframing failed maps as a misuse of the artifact (treated as a deliverable) rather than a flaw in the medium.	counterargument / reframing
The invoice-dispute case study: customer interviews, a deliberately unfinished draft map, and a cross-functional workshop (billing, support, product) surface a systemic gap between disputed-invoice status and automated warning notices.	extended evidence / narrative
'What actually changed' — analyzes the case: each function held one piece of the picture beforehand; the shared field of view, not new information, produced concrete fixes and a new recurring cross-team meeting.	analysis of evidence
'What good collaboration looks like' — generalizes the conditions (right people, shared evidence, visible disagreement, clear ownership, a cadence for revisiting) from the single case into a prescriptive checklist.	generalization
'What this means for your team' — closing call to action: protect and expand alignment time as AI commoditizes execution; AI amplifies whatever collaboration state already exists.	conclusion / call to action

Key terms

Experience mapping
A broad field of visualizing human experience (journey maps, service blueprints, etc.) whose real function is not to deliver an answer but to freeze a fast-moving, chaotic situation so a cross-functional group can look at it together and argue about what it means.
The map
The artifact itself, explicitly distinguished from 'the mapping' as an activity — a boundary object people point at, but not the source of value. The author insists 'the value was never in the diagram.'
Execution speed
The rate at which individual teams can independently build and ship work, now accelerated by AI — explicitly separated from alignment/coordination speed, which does not automatically rise with it.
Draft (map)
A deliberately unfinished artifact used as a facilitation device to invite stakeholders to question and add to it, rather than simply approve a finished deliverable.

Propositions

explicitAs AI-enabled execution speed increases, an organization's need for collaboration, cocreation, and alignment needs to increase, not decrease.conf: high
supportsThe Organization Is the Bottleneck · p1 — Both argue AI's execution-speed gains don't automatically translate into organizational value; Kalbach specifies the mechanism (missing coordination) and a remedy (facilitated shared artifacts).
explicitData and dashboards cannot make decisions or tell cross-functional teams what to do together — that requires human conversation.conf: high
explicitThe value of experience mapping lies in the conversation the artifact makes possible, not in the diagram itself.conf: high
explicitVisualizing an abstract concept like 'customer experience' lets teams reach conclusions and detect cause-and-effect patterns that a spreadsheet or raw data alone cannot surface as effectively.conf: medium
explicitAI can surface patterns in data within seconds, but it cannot create the moment when a cross-functional team collectively recognizes how its own silos are hurting customers.conf: high
supportsTBM 434: How Maps Can Hide Problems · p7 — Both converge on AI as a surfacing/analysis tool that cannot itself resolve organizational misalignment or produce collective human recognition — only people looking at the same picture can.
implicitA map that is built, presented once, and filed away fails for the same reason a report fails: nobody keeps talking about it afterward.conf: high
explicitIn a typical organization, each stakeholder already knows only a piece of the customer-experience picture; no one holds the whole picture alone.conf: high
implicitDeliberately presenting an unfinished ('draft') artifact rather than a polished, finished one increases stakeholder engagement and ownership because it invites people to question and add to it instead of simply approving it.conf: medium
explicitProblems that fall through the gap between two systems or teams that never talk to each other can remain invisible for a long time, precisely because no single team owns or sees the whole flow.conf: high
extendsTBM 434: How Maps Can Hide Problems · p6 — Kalbach's invoice case is a concrete instance of exactly this dynamic (each team had a local workaround instead of confronting the shared gap) and shows what breaks the coping-substitutes-for-repair pattern: a facilitated shared artifact forcing confrontation.
implicitA visible emotional reaction from a cross-functional group (the room going 'quiet, then loud') signals that shared, collective visibility — not merely separate, individual awareness of the same fact — is what drives people to act.conf: medium
explicitAs AI commoditizes execution capability across competitors using similar models and data, the organizations that win will be the ones best at collaborative sensemaking, not the ones with the best dashboards or fastest execution alone.conf: high
explicitAI acts as an amplifier of whatever already exists in an organization: it makes existing collaboration strengths visible fast, and existing silos exposed just as fast.conf: high
supportsThe Organization Is the Bottleneck · p4 — Near-identical amplifier claim ('AI magnifies strengths... and dysfunctions...'), applied here specifically to cross-functional collaboration and silos rather than engineering practice generally.
implicitThe organizational change in the case study resulted from a specific combination of practices — customer interviews, a deliberately unfinished map, a structured cross-functional working session, and a subsequent recurring meeting cadence — not from the map artifact by itself.conf: medium

Arguments

Organizations must expand, not cut, the time and effort spent on cross-functional alignment as AI increases execution speed. strength: medium

Explicit premises:

AI lets each team move fast and independently.
When many teams move fast independently, there is a growing risk of chaotic, uncoordinated divergence.
Only human conversation — not data or dashboards — resolves what teams should do together in response to what data shows.

Implicit premises:

Coordination effort does not automatically scale up on its own as execution speed increases; it must be deliberately protected and invested in, or it falls behind the pace of independent action by default.
The organizational risk created by uncoordinated fast execution (chaos, customer harm, missed problems) outweighs the time cost of investing more in alignment.

Inferences:

If coordination effort must scale with execution speed rather than merely persist against it, organizations should treat recurring, protected alignment rituals as a fixed proportional cost of increased AI velocity, not a one-time fix.
Teams that are individually AI-accelerated but lack a shared coordination artifact are at elevated risk of customer-harming blind spots relative to the pre-AI baseline, even though each team is executing 'better' on its own metrics.

Experience maps (and similar boundary artifacts) are valuable specifically because they convert individually-held, siloed knowledge into one shared field of view that a cross-functional group can react to together. strength: medium

Explicit premises:

Each stakeholder already knows a piece of the picture; none holds the whole picture alone.
The map freezes a moving, chaotic situation so people can look at the same thing together.
In the case study, no single team (support, billing, product) held all three pieces of the invoice-dispute problem; the map made it visible to all three at once, and the fix followed.

Implicit premises:

People are more likely to acknowledge and act on a problem when they discover it collectively, in real time, alongside the people who own the adjacent pieces, than when they are separately informed of the same underlying fact.
The information needed to solve the problem already existed in the organization before the workshop (the author states he had 'already uncovered this' in his own research) — so the map's function was composing and socially co-locating already-distributed knowledge, not discovering new information.

Inferences:

If the mechanism is composition of already-distributed knowledge rather than information-discovery, it should generalize to any cross-functional problem where the relevant facts already exist somewhere in the organization but are never co-located in front of the right people — a broader class of problems than customer-experience mapping specifically.

Now — before AI forces the issue — is the time to invest in collaboration, not after. strength: low

Explicit premises:

AI acts as a 'spotlight,' amplifying whatever is already happening: it makes strong collaboration visible fast and exposes silos just as fast.
Waiting until AI forces the issue means the exposure and its costs happen before the fix does.

Implicit premises:

Organizations currently retain a real choice about whether to invest in collaboration now — this is urgent but not yet foreclosed for most organizations.
Being 'exposed' by AI (silos, dysfunction becoming visible fast) carries real costs — reputational, competitive, or customer-trust costs — that the organization would prefer to avoid.

Inferences:

Combined with the claim that AI commoditizes execution capability across competitors, this implies collaboration quality itself becomes the actual basis of competitive advantage in an AI-saturated market — a stronger, more specific claim than 'collaboration is good,' which the essay gestures at but never builds out with comparative or competitive evidence.

Narratives

The invoice-dispute case study: after customer interviews revealed that people disputing a charge kept receiving late-payment warnings anyway, the author built a deliberately unfinished draft journey map and convened billing, support, and product — teams at the same company for years that had never worked together — in a structured working session. The shared map exposed a gap between two systems that never talked to each other; the room's emotional reaction ('quiet, then loud') led directly to a fix and a new monthly cross-team meeting cadence.
→ Serves as the entire evidentiary basis for the piece's core mechanism claim (propositions p3, p5, p7, p9, p10, and Argument 2) — the author substitutes one vivid anecdote for a general argument or comparative data about why mapping works.
A brief counter-narrative/foil: 'Some claim that journey mapping is dead... static maps can't keep up with real-time data and AI-driven personalization.'
→ Set up specifically to be knocked down, installing the 'the map isn't the point, the conversation is' reframe — it functions as an implicit concession that some maps really do fail, while relocating the cause of failure to misuse of the artifact (treated as a one-off deliverable) rather than to the medium itself.

Questions addressed

✅ How should organizations sustain cross-team alignment as AI lets individual teams execute independently at much higher speed?
Protect and expand time for facilitated, artifact-anchored conversation — using shared visual maps as boundary objects and recurring structured sessions as the mechanism.
✅ Is journey/experience mapping obsolete now that real-time data and AI can analyze customer behavior directly?
No — the 'mapping is dead' critique conflates the artifact with the activity; mapping's value was never in the diagram's information content, so AI-driven personalization doesn't replace its function.
⭕ How should an organization decide which of its many cross-functional gaps deserve a facilitated mapping workshop, given that AI increases the number of independently-moving teams and thus the number of potential misalignments — i.e., how is this now-scarcer coordination time supposed to be prioritized?
⭕ Who actually bears the cost of reinvesting AI's saved execution time into alignment activity — is 'protect it, expand it' a matter of individual/team conviction, or does it require a structural resourcing and incentive change, given that delivery-speed metrics don't reward time spent in workshops?

Gaps

incompleteThe piece never explains how an organization should decide which of its (now more numerous, since AI lets more teams move independently) cross-functional gaps deserve a facilitated mapping workshop. It shows one successful case discovered via customer interviews but offers no general prioritization method for choosing where to spend this scarcer coordination time — the same gap already flagged against extract-tbm-434-how-maps-can-hide-problems, which asks for a way to decide which organizational misalignments are 'consequential' versus tolerable.
Read next: Leverage-points / prioritization literature (Meadows), or later Kalbach/O'Reilly material on triaging journey-mapping investment across a portfolio of possible workshops.
incompleteThe essay's closing advice ('Protect it. Expand it.') treats investing more time in alignment as a matter of individual/team will, without addressing the structural incentive problem: if delivery speed and shipped output remain what an organization measures and rewards, AI-accelerated teams under pressure to ship have no organizational cover to spend more time in workshops, however strongly an individual leader is urged to prioritize it.
Read next: DORA-style incentive and metrics literature, or Cutler's writing on institutional overload, flow, and where slack actually gets funded from.
incompleteThe case study is a single successful anecdote with no counterexample or failure case. The author doesn't address what happens when a facilitated mapping session fails to produce alignment — unresolved disagreement, turf/political defensiveness, a room that doesn't reach shared recognition — leaving open whether the mechanism (shared visual artifact plus facilitated session) is generally reliable, or whether this instance was helped by favorable conditions (the author's own facilitation skill, a factually uncontested gap, cooperative stakeholders).
Read next: Facilitation-failure case studies, or psychological-safety literature on when shared visibility produces defensiveness rather than collective action.
illogicalThe essay argues AI 'won't give you an edge' because competitors have access to the same models trained on much of the same data (implying execution-speed parity across companies), yet elsewhere argues AI lets a team's own internal functions move in many directions 'because they can' (implying execution speed is in fact a live, consequential differentiator inside an organization — the very thing creating the coordination problem the piece is about). These two claims are never reconciled: if AI-driven execution speed doesn't differentiate companies from each other, it's unclear why its intra-organizational effects are framed as such an urgent, novel problem rather than a wash.
Read next: Compare against extract-the-organization-is-the-bottleneck and Jevons-paradox material on whether AI-driven speed gains net out at the market level even as they reshape work at the organizational level.

Closes gaps elsewhere

TBM 434: How Maps Can Hide Problems · g1 — Partially: Kalbach's case study offers one concrete instantiation of the missing prioritization method — ground the map in direct customer evidence (interviews) first, then use structured facilitated exercises within the cross-functional session to let the group itself surface which specific gap is consequential, rather than deciding via top-down criteria in advance. It is a worked example, not a general method.

Experience Mapping Matters More the Faster You Move

Structure

Key terms

Propositions

Arguments

Narratives

Questions addressed

Gaps

Closes gaps elsewhere

Related documents