Phase 02
Elicit
Elicit turns expectations into requirements and gathers enough detail to estimate the work.
Read the workflow from top to bottom. Each column shows the role leading that step.
Client/User
Product
Engineering
Operations / Support
Reviews confirmed or open expectations.
Answers questions and confirms what satisfaction would mean.
Drafts requirements from expectations.
Identifies delivery dependencies, requirement detail, and likely constraints.
Adds run, support, access, and readiness concerns.
Enough detail to estimate and commit?
Answers gaps when more detail is needed.
Prepares the requirement set and accepted risks for Commit.
Records
- Expectation
- Requirement
- Constraints
- Dependencies
- Unknowns
- Risk
Important choices
- Is enough known to estimate responsibly?
- Which requirements need more confirmation?
- Which unknowns can wait, and which must be answered now?
- Does the request need to be narrowed before commitment?
Handoff
Elicit ends when requirements are clear enough to compare cost, value, risk, and confidence, or the accepted risk is visible.