Aglet

Verify Product Concept Comprehension Before Design

Verification asks whether the concept communicates its intended job to the audience in the tested context. Use a consistent low-fidelity stimulus, inspect explanations and questions, and preserve alternate meanings. The result should guide wording or scope without claiming market adoption in a wider population.

Check whether the outcome improved

  1. Define comprehension checks

    Require an explanation in the participant's own words, intended user or situation, likely next action, and a way to surface uncertainty. Add a rule that the moderator cannot correct the interpretation before recording it.

  2. Review varied audiences

    Compare people with different familiarity, language, and task context. Record where the concept is clear, where it sounds like another service, and where the participant asks for missing information. Keep visual polish constant or intentionally absent.

  3. Decide the wording boundary

    Choose whether to keep, rename, narrow, or retest the concept. State which audiences and situations the check covers and what it cannot establish about demand. Assign the next owner for unresolved interpretation.

What to carry forward

The verification record should show comprehension checks, uncoached explanations, audience differences, and the tested wording boundary. Approve the concept only for the context that understood it. Keep a retest when confusion persists or the audience is not yet represented.

Technical background: Nielsen Norman Group research 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