Aglet

Triage a Product Concept Comprehension Check

A concept can sound exciting while meaning something different to the people it is meant to help. Triage the concept promise before visual polish, identify the interpretation the team hopes to hear, and define the evidence that would show confusion. Keep interest separate from comprehension.

Establish what is happening

  1. Name the intended job

    Write what the concept should help a person accomplish, when it would matter, and what a useful outcome looks like. Remove implementation details. Record assumptions about domain knowledge, terminology, and urgency.

  2. List interpretation risks

    Identify words, metaphors, examples, and claims that could suggest several meanings. Prepare neutral prompts that ask participants to explain the concept or describe a likely next step. Mark what the team must not explain during the first response.

  3. Bound the decision

    Define whether the check will choose a name, narrow a promise, change the concept, or request another study. Record which audiences and contexts are included. Do not let enthusiasm become evidence that the concept is understood.

What to carry forward

The triage output is a concept brief with intended job, interpretation risks, neutral probes, audience, and decision. Stop when the check can distinguish comprehension from excitement. Keep the concept provisional when the audience or use context is unspecified.

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