Study first
Review the ideas behind the questions
Review how a research readout should help a team make the next decision. A useful readout explains what was learned, why it matters, and what action or question follows from the evidence.
Make Findings Easy To Use
A finding should not be a pile of notes. It should explain the user evidence, the important consequence, and the decision it can support.
- Research is useful when the team can use what was learned to improve the service, product, roadmap, or user stories.
- A findings slide should include what was learned, essential facts, why it matters, and evidence such as a quote, screenshot, or relevant data.
- Findings should stay focused on users: who they are, what they do, what they need, and what happened in the session.
In Practice
Write The Consequence
Do not stop at a quote. Explain why the finding matters for the decision the team is about to make.
Show The Method Briefly
Readers need a short outline of what research was done before they judge how far the finding can travel.
Common mistakes
Sharing only raw notes and expecting stakeholders to infer the finding.
Turn observations into a clear finding with facts, importance, and evidence before asking for a decision.
Q&A
What should a research finding explain?
It should explain what was learned, who it affects, why it matters, and what evidence supports it.
Why include the research method in a readout?
It helps the team understand the evidence boundary before using the finding for a decision.
Connect Findings To The Next Step
A strong handoff separates what the team learned, what action fits now, and what still needs more research.
- Analysis should turn observations into findings, then into possible actions such as design ideas, new research questions, prototype changes, or backlog updates.
- Involving observers in analysis can reduce researcher bias and limit the influence of one stakeholder's view.
- Themes should be challenged against the data before they become confident readout claims.
In Practice
Name The Next Decision
If the finding points to a change, say whether the next step is a design idea, more research, a prototype test, or a backlog update.
Challenge The Theme
Before handing off a finding, check whether the data supports the theme and whether any evidence pushes against it.
Common mistakes
Turning a weak theme into a confident roadmap recommendation.
State the finding's limit and choose a next research question or prototype test when the evidence is not strong enough for a final decision.
Q&A
Who should join analysis when several people observed the sessions?
Invite the observers into analysis so different views can challenge the finding before it is handed off.
What if the evidence suggests a problem but not the fix?
Report the problem clearly and choose a next research or test step instead of pretending the fix is proven.
Share The Limit With The Action
A readout can be practical and honest at the same time. The action should match the strength of the finding.
- A simple readout can include a brief outline of the research, a set of findings, and a short next-step section when relevant.
- A collection of research decks can create a record of what the team has learned over time.
- When a theme is weak or mixed, the handoff can name a new research question instead of forcing a final recommendation.
In Practice
Do Not Hide The Boundary
If the finding comes from a small or mixed set of evidence, say that clearly and choose a next step that fits.
Keep A Learning Record
Saving readouts helps later teams see what was learned, what was decided, and where evidence was still thin.
Common mistakes
Making the recommendation sound stronger than the evidence.
State the finding, evidence limit, and next action separately so the team knows what is known and what still needs checking.
Q&A
Can a readout include an action if the evidence is not final?
Yes, but the action should usually be a focused test, research question, or backlog detail rather than a claim that the final fix is proven.