1. Write a challengeable problem hypothesis
Begin with the user, situation and problem you believe exists. List the observations behind that belief, keeping interview opinions, personal experience and published information distinct.
Choose an important uncertainty that could change the direction of the solution. Whether users will change an existing habit may matter more than a visual preference. Investigate decision-changing questions first.
2. Test one main question at a time
Record the purpose, participant type, task and completion conditions before testing. A small test can reveal a problem without representing an entire market, so describe its scope.
Write the signal you expect and the result that would require a change. This reduces the temptation to select only favourable reactions or quietly replace the original goal afterwards.
3. Separate observation from interpretation
Record what actually happened: a completed step, a stopping point or a question asked. Put the team's explanation in another column and retain alternative explanations where relevant.
Keep original wording and permission for participant quotations. Use a checked anonymous summary if the original cannot be public. An imagined ideal reaction is not customer testimony.
4. Describe the current version accurately
Distinguish a concept image, working prototype, limited trial and version in ongoing use. Record the test date and available functions, and match the demonstration to the actual version.
Put unbuilt features in a plans section. If people manually carry out part of the demonstration, describe that method instead of presenting it as an existing automated capability.
5. Let findings determine the next test
State what to retain, change and pause, connecting each decision to an observation. Evidence against an assumption can be valuable when it helps stop an unsuitable direction.
Finish with one test and review date. Show a sequence of learning and decisions rather than using a future feature list as evidence of current competitiveness.
A worksheet you can copy
| Field | What to record | Check |
|---|---|---|
| Hypothesis | User, situation and problem | Which part is most uncertain? |
| Test | Date, participants, task and advance criteria | Is there one main question? |
| Observation | Behaviour, questions and original records | Is interpretation kept separate? |
| Version | Prototype, trial or ongoing use; manual steps | Does the demo match real capability? |
| Decision | Retain, change or pause; next test | Does the decision follow an observation? |
Before sharing
- The core hypothesis is explicit
- The purpose was written before testing
- Observation and interpretation are separate
- Product maturity is described accurately
- Findings support the next step
Common questions
Can we present a prototype?
Yes. Identify its stage, tested scope and unbuilt elements so the reader understands what currently exists.
Should an unfavourable test be removed?
Keep the record and explain how it changed a decision. Share within the appropriate permission scope; every test does not need to be described as a success.
Official reference and year
These guides provide original preparation methods. The 2026 material is a historical reference; formal 2027 requirements depend on the relevant edition's announcements. The worksheets do not replace official rules, eligibility decisions or professional advice.
- Awards and judging: 2026 edition reference — checked 2026-11-01
