part three · journey mapping
Journey Mapping
The full activity with friction marks.
A journey map is the team's drawing of the named person's activity, end to end, with friction marked where it actually occurs. It is the artifact that the brief sits inside. Stories in Volume III refer to journey steps by number — J3, J4 — so the map needs to be authoritative.
What a journey map is, and isn't
It is:
- Sequential. Step 1 to step n, in the order the activity happens.
- Annotated. Each step has the person's domain language, the system the activity touches, and where friction occurs.
- Numbered. J1, J2, J3 — referenced from the brief, the stories, the analytics events.
- Owned by Discovery. Updated when the team learns more about the activity. Not a one-shot deliverable.
It isn't:
- A user flow inside a particular product. That comes later, in Volume III.
- A wireframe. Wireframes show the interface of a step, not the step.
- A funnel or analytics dashboard. Those measure aspects of a journey but cannot describe the lived activity.
How to draw the first version
Sit with the observation notes (Part 1). List every distinct action the named person took, in time order. Group consecutive same-tool actions together as one step. Mark friction.
A first journey for Gal's grading activity:
J1. Gal arrives at her desk. (08:50)
J2. Opens LMS, navigates to today's grading queue. (08:53) ⚠ nav-friction
J3. Pulls up the rubric on second monitor. (08:55)
J4. Opens the first student submission. (08:57)
J5. Reads the answer; references rubric several times. (08:58) ⚠ context-switch
J6. Edits student's display name in spreadsheet. (09:14) ⚠ workaround: Hebrew names
J7. Selects rubric scores; types brief comments. (09:18)
J8. Submits the grade. Returns to queue. (09:22)
J9. Repeats J4–J8 for next four students. (09:23–10:05)
J10. Closes the LMS, drinks water, switches activity. (10:30)The friction marks are the brief-writable points. Each one is a candidate for a Volume II prediction.
Levels of detail
A journey can be drawn at three resolutions. Pick the one the brief needs.
| Resolution | Steps | When |
|---|---|---|
| Activity-level | 5–10 | Initiative briefs, where the gap is at activity scale |
| Task-level | 15–30 | Feature briefs, where the gap is inside one activity |
| Action-level | 50+ | Specialised work — accessibility audit, performance hot-path, security review |
A team that reaches for action-level too early drowns in detail. A team that stays at activity-level too long writes briefs that miss the actual friction.
Marking friction honestly
Friction is not always inconvenience. The corpus uses three friction labels.
- Cognitive — the person had to hold something in their head that the system could have remembered.
- Mechanical — extra clicks, extra navigations, manual data shuffling.
- Domain-mismatch — the system's language or model differs from the person's. The person paid the cost of translation.
Each label points to a different kind of fix. The brief that names cognitive friction at J5 leads to a different feature than the one that names mechanical friction at J5.
The map and the brief
The brief uses the map as its anchor. The brief's prediction names the journey step that will change.
Initiative: Grading Flow v2
Person: Gal (and ~120 graders)
Map step: J6 (display-name workaround for Hebrew names)
Friction: Domain-mismatch + mechanical
Prediction: With native Hebrew name support in the LMS, J6
disappears. Time saved per cycle: ~3 minutes.
Cumulative across the cohort: ~6 hours/week.
Check date: 2026-06-01
Check method: Observation of three named graders post-deploy.
Owner: Alex (PO)The brief is short. The map is the context that makes it short.
Updating the map
Every model update (Volume V Part 6) is an opportunity to update the map. New friction surfaced by the cycle goes onto the map as a new annotation. Resolved friction is struck through, not deleted — the map carries the history of the activity.
A team whose map is current can write briefs faster, because the act of finding the moment has already been done.