Aglet

Triage Competing Product Opportunities

Opportunity comparison begins by making candidate problems comparable. Triage each statement into a user situation, desired outcome, and evidence trail before ranking it. This prevents a memorable request, a proposed feature, and a recurring pain point from competing as if they were the same kind of claim.

Establish what is happening

  1. Normalize each opportunity

    Rewrite every candidate around who is trying to do what, when the difficulty appears, and what outcome is blocked. Remove solution names from the statement. Record whether the source is an observed behavior, a reported frustration, an internal hypothesis, or a market assumption.

  2. Trace the evidence

    Attach interviews, observations, support themes, task data, and known counterexamples to each opportunity. Note source date, user context, and gaps. Separate evidence that a problem exists from evidence that a particular solution would solve it.

  3. Set comparison boundaries

    Define the user groups, journey stage, and time horizon covered by the initial comparison. Flag candidates that describe different scales or outcomes. State what is out of scope so a broad strategic concern cannot quietly outrank a specific user need.

What to carry forward

The triage output is a normalized opportunity set with affected users, context, evidence type, and open questions. Stop when every candidate can be compared on the same terms. Keep a candidate provisional when the evidence only describes a solution request or one unusual case.

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