Final Recommendation

What this activity covers

Package the evidence and choose the recommendation that best fits the current discovery confidence and risk picture.

Why it matters

Do not recommend build or scale simply because momentum exists. The recommendation should reflect evidence and readiness.

Typical output

Mass Product Discovery Brief and Final Recommendation

Questions this activity helps answer

• Is the product ready to build, pilot, roll out, improve, pause, or investigate further?
• Which major assumptions remain unresolved?
• What is the next decision gate and who owns it?

Build and pilot

• Problem, audience, and key flows are sufficiently understood.
• Trust and support risks are known and manageable.
• The team can build with a clear pilot learning plan.

Discovery indicates enough evidence to build the next version and validate it through a bounded pilot before broader rollout.

Define the pilot scope, success metrics, analytics QA, support owner, and evidence review date before build starts.

Proceed to controlled rollout

• The product or feature is ready for live exposure, but scale should expand in stages.
• Monitoring, support, and rollback rules are defined.
• The team needs real usage evidence before full launch.

Discovery indicates the product can move into a controlled live rollout, with careful monitoring and decision points before scale increases.

Launch with the agreed cohort, region, or percentage, then review metrics, complaints, support load, and trust signals before widening exposure.

Improve before scaling

• The product is live, but adoption, trust, retention, or support signals show meaningful friction.
• There is enough evidence to improve known issues before wider rollout.

Discovery indicates the current product should be strengthened before more investment in scale, growth, or promotion.

Prioritize the flow, trust, support, or measurement issues most likely to improve activation, retention, and user confidence.

Run more discovery before build

• Key assumptions still lack user, behavioral, or analytics evidence.
• The team cannot yet explain why users would trust, adopt, or repeat usage at scale.

Discovery indicates that more evidence is needed before the team should commit to build or scale.

Close the highest-risk knowledge gaps first, especially around user behavior, trust, support readiness, or launch measurement.

Do not proceed now

• Discovery indicates weak product value, unresolved trust risk, unmanageable support burden, or low readiness to launch responsibly.
• The product should not move forward in its current form.

Discovery indicates that the team should pause or stop the current direction until major issues are resolved or the opportunity is reframed.

Document why the team is pausing, what conditions would need to change, and what alternative paths should be considered instead.

Related outputs

These outputs usually sit beside this activity when the team reviews the evidence together.

• Rollout and Continuous Discovery Plan
• Final Recommendation
• Mass Product Discovery Brief