A Discovery Framework is the operating contract between product, engineering, and leadership for how an idea becomes a built thing. Three phases — Requirements, Problem Validation, Solution Validation — each with clear roles, exit criteria, and a gate before the next phase starts.
The point is not “more discovery.” The point is the right amount of discovery for the right kind of problem, decided once at the top, instead of re-litigated on every initiative.
What decision this drives
How a vague stakeholder request becomes a shippable spec — predictably, on a known clock, without the political tax of “is this ready yet?” debates between teams.
What it looks like
Caption: Anonymized Discovery flow (multi-phase swimlane).
What you get
- Phase definitions with entry and exit criteria
- Roles and responsibilities per phase (PM, designer, eng lead, data, founder)
- Templates for each phase output (problem brief, solution brief, spec)
- Gate review format and decision log
- Calibration session with one in-flight initiative as the worked example
Real result
At a bootstrapped scale-up, this artifact cut discovery cycles from 7 months to 1.5.
Price
€6,000 fixed, 5 weeks.
