What this screen does
The User Journeys tab expands the specification's compact journeys into a full document: each journey names its actor (role plus a one-sentence persona), goal and trigger, walks the main path as numbered actor/action/screen steps, then adds alternate paths (legitimate variations, amber) and error paths (failures and rejections, red). A coverage panel at the bottom lists which roles and functional requirements the journeys exercise — and which they still miss.
Typical workflow
- Open the User Journeys tab on the Specification page and click Generate.
- Read each card as a story: does this person, doing these steps on these screens, actually reach the goal? Missing steps and wrong actors are cheapest to fix here.
- Correct what is almost right: the pencil button on a journey card adds a revision note ("The approver is the Finance Manager, not Ops"). Notes stack up as pending; Refine (N) applies them all in one pass — journeys without a note come back unchanged.
- Check the coverage panel: a role with no journey or an uncovered core requirement usually means a scenario was never written down.
- Use Sync journeys (v+1) to append genuinely new journeys to the specification. Existing spec journeys are never modified — the sync only adds names the spec does not have yet.
- Regenerate the screen map afterwards: when this document exists, its journeys drive the screen map's numbered flows.
Examples & tips
- The coaching preset controls depth: concise gives 4-5 lean journeys, probing gives 8-10 with richer personas and a fuller coverage analysis.
- A step with no screen chip means the journey needs a screen the specification never defined — that is a finding about the spec, not a rendering gap.
- Use the chat button on a journey card to ask the project agent about it — for example, "what happens if the approver is on vacation at step 3?"
- Error paths are worth reviewing hardest: approvals, payments and external dependencies each deserve at least one, and the generator is instructed to add them.