Fill in these first
- Product and flow tested: [e.g. the checkout on a grocery delivery app]
- Participants: [e.g. 7 people, first-time users, mixed ages, on phones]
- Tasks given: [list the tasks]
- Session notes: [paste notes per participant: task, success or fail, time, what they said and did]
- Audience for the readout: [e.g. product manager, designers, engineers, a director]
- Time slot: [e.g. 30 minutes with 10 for discussion]
Task
Write the readout deck so the team leaves agreeing what to fix first.
Deck outline
- Title slide with the flow tested and the dates.
- What we tested and with whom, in one slide.
- Headline: the three findings that matter most, each in one sentence.
- Task results: | Task | Completed | Struggled | Failed | Median time |
- One slide per major finding: the problem in a sentence, how many participants hit it, severity of blocker, major or minor, one short quote, and the screen to show.
- What worked well, so it is kept.
- Ranked fixes: | Fix | Findings it solves | Effort guess | Priority |
- Open questions and the next round of testing.
Rules
- Count people, not mentions: "5 of 7 participants" is the format.
- Quotes stay short and anonymous, labelled P1, P2 and so on.
- Separate what participants did from what they said, and trust what they did.
- Never call a finding from one person a pattern; list it under "worth watching".
- Speaker notes of up to 50 words for each slide.






