part five · the five stations
The Five Stations
The discovery walk — Vision & Context, Problem Framing, User Journey & Slices, Solution Options, Decision & Scope.
The Five Stations is the corpus's prescribed sequence for Discovery on a new initiative. The stations are walked in order. Each one produces an artifact the next one needs. Skipping a station does not save time — it pushes the missing work into the station that comes after, where it is harder to catch.
Station 1 — Vision & Context
Question: Who is this for, what is their pain, why now, what does success look like?
Output: the Initiative Problem Story. A one-page document that names:
- The named person and their context.
- The pain — observed where possible, inferred where the observation is pending.
- Why now? — what has changed that makes this initiative timely.
- Success looks like — a one-paragraph description of the world if the initiative works.
This is the station where Volume I's named initiative becomes a story the team can carry. The Initiative Problem Story is the artifact every later station refers back to.
Station 2 — Problem Framing
Question: What do we believe, what do we know, what are we constrained by, what are we explicitly not doing?
Output: the frame. Four labelled sections.
- Validated assumptions. Witnessed in Discovery so far.
- Unvalidated assumptions. Believed but not yet witnessed.
- Constraints. Hard ones — regulatory, contractual, technical floor — that bound the design space.
- Explicit non-goals. What the team is not trying to do in this initiative, with rationale.
The non-goals are the most useful section in the long run. Six months later, when scope creeps, the frame is what the team returns to in order to remember what was deliberately excluded.
Station 3 — User Journey & Slices
Question: What is the full activity, where does it break, which break is in scope?
Output: the journey map (Part 3) plus a slice declaration that names which steps are in scope for this initiative and which are out.
A journey of fifteen steps with three friction points might produce three slices. The first slice is what this initiative addresses. The other two become candidate next-initiatives.
A station-3 conversation that produces we should fix all three is a station-3 conversation that has not yet become a Discovery decision. The discipline is to choose.
Station 4 — Solution Options
Question: What are 2–3 plausible directions the initiative could go, and what do they trade off?
Output: the options table. Each option has:
- A short name and a one-paragraph description.
- The journey steps it changes.
- The risks it carries.
- The implementation cost order-of-magnitude (S / M / L).
- The assumptions it leans on most.
This station deliberately holds the team back from picking. The act of writing the options is what reveals their trade-offs. A team that arrives at this station with the answer already chosen has not done Discovery — they have done justification.
The corpus pattern: always include a "do nothing" option. Sometimes the right move is to not pursue the initiative this cycle. The do-nothing option, written down with consequences, is what makes that decision honest.
Station 5 — Decision & Scope
Question: Which option, what is the smallest first slice, what would success look like?
Output: the decision artifact. Names:
- The chosen option, with a sentence on why this and not the other(s).
- The MVP scope — the smallest first feature with a Volume II Feature Brief written.
- The first three stories the trio recommends.
- The KPI — a single signal that, if it moves, will tell us the initiative is on track.
The KPI is not the prediction. The KPI is the leading signal that the initiative is alive. The prediction is the lagging signal, written into the Feature Brief with a check date.
Walking the stations
The stations are a sequence, not a meeting agenda. Each takes its own time. The corpus pattern is:
| Station | Typical duration |
|---|---|
| 1 — Vision & Context | A short series of conversations + the observation work in Part 1 |
| 2 — Problem Framing | A 90-minute trio session with the Initiative Problem Story in front |
| 3 — User Journey & Slices | A morning of journey-mapping in front of the observation notes |
| 4 — Solution Options | A 90-minute trio session, often with the Tech Lead leading the trade-off discussion |
| 5 — Decision & Scope | A 60-minute leadership-present session, ending with sign-off |
The stations cannot all happen in one day. Trying to compress the sequence is what produces the kind of brief that ships and is then surprised by reality.
The artifact bundle
When the stations have been walked, the initiative carries:
- The Initiative Problem Story.
- The frame (assumptions + constraints + non-goals).
- The journey map with slices declared.
- The options table with the chosen option marked.
- The decision artifact with the MVP scope and KPI.
This bundle is what the brief is built on. The brief is short — three pages, often two — because the bundle does the heavy lifting underneath.