RESEARCH WORKFLOWS
Start with the decision.
Choose the next test.
Practical workflows for understanding a product idea, testing its explanation, and finding people with relevant experience.
Do people understand the idea?
Show one concept, capture an unaided explanation, and separate misunderstanding from a poor fit.
Run a concept test →02 · MESSAGEDoes the video explain it?
Use a before-and-after protocol, a timestamped evidence log, and a clear revision decision.
Test an explainer →03 · PARTICIPANTSAre we asking the right people?
Create behavioral screening questions with researcher-only routing notes and an editable export.
Build a screener →CHOOSE YOUR STARTING POINT
What is still uncertain?
If you do not yet understand the problem, begin with customer discovery. If the concept is understood but people cannot complete a task, choose usability testing. A polished explainer cannot settle either question on its own.
For a concept test, record one decision before recruiting: change the message, revise the workflow, narrow the audience, or investigate a missing need. Use the same stimulus version within a round so observations can be traced to what people actually saw.
Leave with something usable.
- A research plan with the decision and constraints.
- A worked video brief that separates evidence from claims.
- A record of uncertainties and a next test, rather than a pass/fail badge.
These are reusable methods and fictional examples, not customer success stories. A small qualitative study can reveal problems; it does not establish demand or a population conversion rate.
TASK-BASED COLLECTIONS
A shorter path to a useful shortlist.
Take a neutral script into the session.
Download the concept-test discussion guide →Study AI product onboarding
Observe the first useful result, including output review and recovery.
Read the guide →Build a reviewable repository
Pilot source references, retrieval and permissions before migrating more material.
Read the guide →