← All work
Obosu Discovery
From conversation to approved, traceable scope
From conversation to approved, traceable scope
01 / 05
The problem
Scope disputes start early: a conversation becomes a proposal, the proposal becomes a contract, and nobody can point at where a given line came from.
What it does
- Structured discovery
- The conversation is captured as problems, outcomes and constraints rather than prose.
- Traceable scope
- Every scope line points back to the problem it answers and the outcome it is measured by.
- Client approval
- Sign-off happens against that structure, so later change requests are visible as change.
Decisions worth explaining
- No free-text proposal
- Prose hides disagreement. Structure surfaces it while it is still cheap.
- Outcomes carry thresholds
- An outcome with no number attached is an opinion, and opinions cannot be delivered against.
Where it got to
Discovery capture and scope structure are working; approval flow and client-facing view remain.
- Used only on OBOSU’s own engagements.
- No external customer figures exist.