Phase 01
Orient
Orient captures the desired outcome in stakeholder terms, restates expectations, and confirms how success will be recognized where possible.
This phase understands the result people need before translating it into requirements. Read the workflow from top to bottom. Each column shows the role leading that step.
Client/User
Product
Director
Shares the goal, problem, request, concern, or opportunity in their own words.
Captures the voice, asks clarifying questions, and restates expectations.
Confirms, corrects, or leaves expectations open.
Confirms who can decide priority and spending.
Adds missing context when needed.
Clear enough to translate into requirements?
Moves into Elicit, pauses, stops, or accepts the risk of open expectations.
Records
- Workspace
- Service Charter
- Initiative
- Voice
- Expectation
- Decision
- Risk
Important choices
- Has the original voice been captured in the person's own words?
- Are expectations confirmed, corrected, or still open?
- Do expectations describe how success will be recognized?
- Is the right decision authority involved?
- Should the request continue, pause, stop, or continue with accepted risk?
Handoff
Orient ends with expectations that are confirmed where possible, or carried forward with visible risk when confirmation is missing.