Create a journey map grounded in a real task
Map workshop attendance across preparation, booking, travel, participation, and follow-up while distinguishing evidence, assumptions, opportunities, and organizational responsibilities instead of decorating an invented story.
Define the perspective and scope
A journey map represents how an experience unfolds over time. For a workshop visitor, the journey may begin before booking and continue after the session. Its usefulness depends on the perspective, scope, and evidence behind it. A polished curve of invented emotions can conceal uncertainty rather than help a team understand a problem.
Separate actions, observations, and assumptions
Define whose journey is represented, the task, and the start and end points. Use lanes for actions, questions, touchpoints, and relevant observations. Mark assumptions clearly and avoid filling emotional states from the team's imagination. Connect opportunities to actual obstacles instead of adding a feature idea to every stage by default. Prepare the work so that another person can inspect its reasoning without a live presentation. Use concrete examples, readable labels, and links to supporting material where appropriate. Avoid relying on a dense board whose meaning exists only in the facilitator's memory. The point is not to document every conversation; it is to preserve the context and distinctions that matter when somebody acts on the output later.
Map a provisional bookbinding visit
Create a provisional map for attending a bookbinding workshop: discovering it, assessing suitability, booking, preparing, arriving, participating, and following up. Use fictional notes only as a labeled practice exercise. Mark where real research would be required and where staff records or operational knowledge could clarify the process. Use a small worked example to examine the mechanics of the method. Keep invented material clearly labeled and separate from any real research evidence. The example should expose decisions about wording, grouping, order, or responsibility that would otherwise remain implicit. Where the activity requires a fact you do not have, leave a question rather than manufacturing a convenient answer to complete the diagram or make the exercise look finished.
Preserve variation and ownership
If the map combines several different situations into one confident story, split it or explain the variation. If every stage appears equally problematic, return to the evidence. If an opportunity has no owner, it may remain a vague aspiration. Use the map to expose dependencies between content, interface behavior, and service operations. Watch for a convenient example becoming the only situation the team considers. Add a case with a different starting condition, incomplete information, or an interruption, then inspect which assumptions no longer hold. Do not invent research findings to justify the additional case. Use it as a deliberate challenge to the working model and identify the real evidence or expertise needed to assess whether the concern matters.
Revise the map as understanding changes
Review the map with relevant participants or evidence and the people who deliver the service, using methods appropriate to the project. Preserve disagreements and gaps instead of smoothing them away for presentation. A useful journey map supports a focused decision and points to further inquiry. It should remain revisable as the team learns more about the actual experience.
Worked decision
A provisional preparation stage may contain an assumption about materials. Mark it for investigation rather than inventing an emotion to complete the row.
References & further reading
Examples and exercises in this guide are original teaching scenarios.
