Good Discovery Plans Tie Methods to Decisions
A PM should not do research for its own sake. Each method should answer a question that matters to a product decision.
For example:
<ul>
<li>interviews for depth and causal understanding</li>
<li>surveys for scale or segmentation</li>
<li>analytics for behavior patterns</li>
<li>prototypes or experiments for response to an idea</li>
</ul>

Activation dropped last month, and the team does not yet understand why. What is the strongest first move?

A broad survey is usually the best first method when the team still does not understand the problem space.

Sequence Research Intentionally
A simple pattern many PMs use:
<ul>
<li>start with existing behavior and qualitative clues</li>
<li>narrow the problem</li>
<li>test hypotheses with the right method</li>
<li>move into a prototype or experiment when confidence is high enough</li>
</ul>
This saves time and reduces thrash.

Which discovery plan is strongest?

Each research method in a discovery plan should connect to a concrete decision or uncertainty the team needs to resolve.

Discovery Does Not Completely End at Build Time
Even after a team starts building, PMs still learn. They may refine:
<ul>
<li>messaging</li>
<li>scope</li>
<li>onboarding</li>
<li>adoption risks</li>
<li>rollout strategy</li>
</ul>
Discovery and delivery overlap more than beginners expect.

Which signal suggests a team is ready to move from discovery into build for a narrow v1?

Discovery often continues during delivery because teams keep learning about adoption risks and product clarity even after work starts.