Discovery tests value, usability, feasibility, and business viability with Product, Design, and Engineering. Delivery builds robust solutions; both tracks are parallel activities of one team, not separate departments.

1. 1

   Opportunity

   Opportunity

   

   Goal

   Produce opportunity brief so the core question “Which solution is valuable, usable, feasible, and viable enough for delivery?” can be answered with stronger support.

   Inputs for this step

   • Product outcome
   • opportunity evidence
   • cross-functional product team

   Actions

   • Focus outcome and opportunity with customer and business evidence.
   • Record source, rationale, and open uncertainty directly in opportunity brief.

   Output

   opportunity brief

   opportunity brief · source · uncertainty · next decision

   Quality check

   Is the team commissioned with an outcome rather than a feature?

   Pitfall

   Discovery becomes upfront specification and hands work off to Delivery. Have the trio and engineers test early together, deliver thin slices, and feed outcome data back into discovery.

   Timing: 10–20 minutes

2. 2

   Test risks

   Test risks

   

   Goal

   Produce risk evidence so the core question “Which solution is valuable, usable, feasible, and viable enough for delivery?” can be answered with stronger support.

   Inputs for this step

   • opportunity brief
   • opportunity evidence
   • cross-functional product team

   Actions

   • Test value, usability, feasibility, and viability with prototypes.
   • Record source, rationale, and open uncertainty directly in risk evidence.

   Output

   risk evidence

   risk evidence · source · uncertainty · next decision

   Quality check

   Are all four risks explicit?

   Pitfall

   Discovery becomes upfront specification and hands work off to Delivery. Have the trio and engineers test early together, deliver thin slices, and feed outcome data back into discovery.

   Timing: 10–20 minutes

3. 3

   Delivery slice

   Delivery slice

   

   Goal

   Produce production slice so the core question “Which solution is valuable, usable, feasible, and viable enough for delivery?” can be answered with stronger support.

   Inputs for this step

   • risk evidence
   • opportunity evidence
   • cross-functional product team

   Actions

   • Deliver the validated solution as a thin robust slice.
   • Record source, rationale, and open uncertainty directly in production slice.

   Output

   production slice

   production slice · source · uncertainty · next decision

   Quality check

   Does problem context remain in the team?

   Pitfall

   Discovery becomes upfront specification and hands work off to Delivery. Have the trio and engineers test early together, deliver thin slices, and feed outcome data back into discovery.

   Timing: 10–20 minutes

4. 4

   Outcome

   Outcome

   

   Goal

   Produce outcome learning so the core question “Which solution is valuable, usable, feasible, and viable enough for delivery?” can be answered with stronger support.

   Inputs for this step

   • production slice
   • opportunity evidence
   • cross-functional product team

   Actions

   • Measure use and impact and derive the next discovery question.
   • Record source, rationale, and open uncertainty directly in outcome learning.

   Output

   outcome learning

   outcome learning · source · uncertainty · next decision

   Quality check

   Does evidence change the next priority?

   Pitfall

   Discovery becomes upfront specification and hands work off to Delivery. Have the trio and engineers test early together, deliver thin slices, and feed outcome data back into discovery.

   Timing: 10–20 minutes