Two Modes, One Continuous Loop
<ul>
<li>Discovery reduces uncertainty before and during building.</li>
<li>Delivery turns decisions into shipped product value.</li>
</ul>
Healthy teams do both continuously. Discovery does not end when a roadmap is approved, and delivery is not just “build whatever is written down.”

Which activity is a discovery activity?

Discovery ends once the roadmap is approved for the quarter.

Who Belongs in Discovery?
Discovery is strongest when PM, design, and engineering participate early enough to shape the decision.
Why?
<ul>
<li>PM brings customer and business context</li>
<li>design brings usability and workflow thinking</li>
<li>engineering brings feasibility and implementation insight</li>
</ul>
Late collaboration usually creates avoidable rework.

When should engineering be involved in discovery?

Discovery is only the PM’s job; design and engineering should wait for finalized requirements.

A Common Failure Mode
A team can look busy and still learn very little.
Warning signs include:
<ul>
<li>many releases but flat adoption or retention</li>
<li>roadmap items chosen before the problem is understood</li>
<li>high rework because important assumptions were never tested</li>
</ul>
Strong discovery reduces expensive surprises.

Which pattern most strongly suggests a team is under-investing in discovery?