Mapping Experiences: A Complete Guide to Creating Value Through Journeys, Blueprints, and Diagrams
Source: https://www.oreilly.com/library/view/mapping-experiences-2nd/9781492076629/ ↗
Kalbach's book is a reference manual for the visual tools of experience design — journey maps, service blueprints, empathy maps, ecosystem diagrams.
What makes it useful rather than just an inventory is the discipline Kalbach imposes: each tool has a specific purpose, specific inputs, specific failure modes, and they are not interchangeable.
For product direction it is the kind of book that makes a team stop arguing about which workshop to run and start picking the tool that fits the problem.
The second edition, updated in 2020, is the one to read. Kalbach writes with operational clarity — no dogma, much craft.
Central argument
Kalbach argues that experience mapping tools — journey maps, service blueprints, empathy maps, ecosystem diagrams — are not interchangeable instruments of facilitation but distinct analytical devices, each with its own purpose, required inputs, and failure conditions. The central thesis is that most organisations misuse these tools not from lack of effort but from category confusion: applying a journey map where a service blueprint is needed, or running an empathy map exercise to answer a question it cannot answer. The book's operative claim is that disciplined tool selection — matching the right diagram to the specific problem at hand — is itself a strategic act, not a workshop convenience.
Critique
The book's strength — its operational clarity and tool-by-tool taxonomy — is also its principal limitation: it treats the visualisation artefact as the primary unit of work, which risks overstating what alignment around a diagram can achieve in organisations where the deeper blockage is political rather than perceptual. A thoughtful reader might also note that the framework assumes a relatively stable product or service object to be mapped; in fast-moving digital contexts where the service boundary is itself under negotiation, the discipline of picking the 'correct' tool can become a premature closure on what the problem actually is.
Why it matters for product
For a product leader, the book's most concrete value is in cross-functional governance: when design, engineering, and business teams disagree about what discovery artefact to produce, the disagreement is often a proxy for misalignment on what question is actually being asked — Kalbach provides the vocabulary to surface that faster. It is also directly applicable to scaling product orgs, where journey maps and service blueprints are frequently used as team boundary tools, and where the failure mode Kalbach identifies — using a customer-facing map to diagnose an internal service delivery problem — maps precisely onto the gap between product squads and platform or operations teams.