Question-first approach to understanding user journeys. Load when starting a new journey design or when the discovery phase needs deepening.
Discover journeys through deep questioning before any sketching. The sketch is proof of understanding, not the starting point.
Focus: What is the user trying to accomplish?
Questions:
After collecting goal, trigger, and success criteria, output a rough draft sketch showing what the journey might look like. Mark unknowns with ???. Purpose: make value visible immediately so the user sees progress, not just questions.
[Trigger: ???] → [Step 1: ???] → [Step 2: ???] → [Goal: {stated goal}]
Feels: ??? Sees: ??? Sees: ??? Feels: {success criteria}
Artifacts: ??? Artifacts: ??? Artifacts: ???
This is a working hypothesis, not a commitment. Update it after each phase as understanding deepens. The sketch gives the user something concrete to react to — "no, step 2 happens before step 1" is more productive than abstract discussion.
Focus: What does the user EXPECT to see?
Questions:
Focus: How should the user FEEL?
Questions:
Focus: What data is shared across steps?
Questions:
Focus: What could go wrong?
Questions:
Focus: How do steps connect?
Questions:
Focus: What commands and output does the user expect?
Questions:
Use AskUserQuestion with structured options:
Ready to sketch ONLY when all can be answered:
If ANY criterion is unclear -- ask more questions.
Always ask first when:
Continue asking until:
Instead: