Aglet

Verify an Opportunity Before Solution Selection

Verification checks whether the selected opportunity is sufficiently clear and evidenced for the next product step. It does not require certainty about a solution. Define the user outcome, review evidence from multiple contexts, and record unresolved differences before allowing a prototype or experiment to stand in for the problem itself.

Check whether the outcome improved

  1. Define the opportunity check

    Write the observable situation and outcome that must be present for the opportunity to remain in scope. Include a disconfirming case, a relevant user group, and the minimum context needed to interpret the observation without adding a solution preference.

  2. Compare evidence by context

    Review observations, interviews, task traces, or support records using the same opportunity definition. Compare first-time and experienced users, successful and workaround paths, and adjacent contexts. Investigate missing evidence rather than treating silence as absence.

  3. State the decision boundary

    Record whether the opportunity is ready for solution exploration, needs a narrower frame, or should return to discovery. Note what the check does not establish about adoption, willingness to pay, or technical feasibility. Give each open question an owner.

What to carry forward

The verification record should show the opportunity definition, evidence by context, counterexamples, and next decision. It can support solution exploration within a bounded user situation. It should not imply that the opportunity proves a particular feature, market size, or business outcome.

Technical background: Product Talk discovery guidance.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow