O'Reilly Media • 2016 • 296 pages
Guide
~1 min read
A Complete Guide to Creating Value through Journeys, Blueprints, and Diagrams
The book argues that maps are only valuable when they are built to support a specific decision and shaped by real evidence rather than workshop theater.
Waypoint uses it to keep journey and service mapping grounded in evidence, scope discipline, and operational clarity.
Read this if: You need an end-to-end view of a service or journey and want the resulting artifact to change a decision instead of decorating a wall.
Quick skim
A practical read on what makes a map credible, how to avoid decorative synthesis, and how Waypoint should use mapping artifacts as decision tools.
Five key ideas
Editorial intro
Read this as a discipline for making maps decision-worthy, not simply more polished.
This summary focuses on the parts of the book that matter most in Waypoint: perspective and scope choices, evidence structure, and the move from diagramming to operationally useful synthesis.
Covers
The strongest mapping principles, the practical quality bar for journey artifacts, and the implications for workshops and outputs inside Waypoint.
Leaves out
Template sprawl, decorative diagram variation, and any sense that bigger maps automatically create better discovery.
Deep read
Kalbach argues that maps are not generic workshop outputs. They are designed representations of how people move through an experience and how organizations support or fail that movement. The book is strongest when it explains the decisions behind scope, perspective, sequencing, and what a map is supposed to help a team do next.
Kalbach argues that maps are not generic workshop outputs. They are designed representations of how people move through an experience and how organizations support or fail that movement. The book is strongest when it explains the decisions behind scope, perspective, sequencing, and what a map is supposed to help a team do next.
Judgment
Strongest
Mapping choices should be shaped by the decision the team needs to make, not by template familiarity. Evidence needs structure before it becomes a credible journey artifact. Experience maps become more powerful when they surface dependencies, handoffs, and invisible operational strain.
Limitation
Practical application
Waypoint should read this as a quality bar for mapping work. The book matters because it turns journey artifacts from decorative synthesis output into evidence-shaped decision tools that can justify action.
In Waypoint terms, this changes what a mapping workshop is for. The goal is not to produce a prettier wall of notes. The goal is to create a representation that helps the team align on where experience breaks, why it breaks, and what should happen next.
Use this when
Do not overapply when
Facilitation implications
Planning implications
Source details
Reviewed source
O'Reilly Media
2016
First edition
EN
Editorial notes
Reviewed 2026-03-07
Reviewed by Waypoint Editorial
Find the bookThe book can be misapplied as a license to create ever-larger artifacts when the real goal is decision clarity. A journey map without solid inputs will still look polished while remaining weak as evidence.
Bottom line
Waypoint should read this as a quality bar for mapping work. The book matters because it turns journey artifacts from decorative synthesis output into evidence-shaped decision tools that can justify action.
A shared end-to-end view that exposes dependencies, supports prioritisation, and turns synthesis into an action path.