Phase 01
Orient
Orient captures the desired outcome in plain 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.
End User
Owner
Shares the goal, problem, request, concern, or opportunity in their own words.
Captures the statement, asks clarifying questions, restates expectations, and confirms the wording before recording it.
Approves expectations when authority approval is needed.
Confirms priority, spending authority, and the decision path.
Adds missing context when needed.
Clear enough to translate into requirements?
Decides whether to continue, pause, stop, or formally accept the open risk.
Records
- Workspace
- Statement
- Expectation
- DX Complete Ticket
Important choices
- Has the original statement been captured in the person's own words?
- Was captured wording confirmed before it was recorded?
- Are expectations approved, not approved yet, or moving forward with open risk visible?
- Do expectations describe how success will be recognized?
- Is the right decision authority involved?
- Should the request continue, pause, stop, or continue with open risk visible?
Handoff
Orient ends with expectations that are clear enough to use, with approval where needed or visible risk where approval is missing.