Marcus Andrey Study
Ler em português Library

UX Research · Labs · 4 min read

Present findings in ten minutes

A guided lab: turn a study into a ten-minute readout that ends in a decision. One sentence of answer, three findings with evidence, recommendations with owners, and a clear ask, rehearsed against a timer. About two hours to prepare, ten minutes to deliver.

Ten minutes is not a short presentation. It's a decision with evidence attached. Most readouts run out of time on the method and rush the part people came for. You'll build one that starts with the answer, shows three findings people can feel, and ends by asking for something specific. Then you'll rehearse it until it fits.

What you'll do:

  • Write the study's answer in one sentence
  • Choose three findings and one piece of evidence for each
  • Turn each finding into a recommendation with an owner
  • Build a ten-minute readout and rehearse it against a timer
  • Send a follow-up within a day

You'll need: a finished synthesis (from Synthesise a study, or any study you know well), a slide tool or a single page, a timer, one colleague to rehearse with, about two hours.


1. Write the answer first

Go back to the decision in your plan (Write a research plan). Write the answer to it in one sentence, as if it were the only thing people remember:

We learned that ______, so we recommend ______.

For example: "We learned that people trust a split only when they can see how it was worked out, so we recommend showing the working under every split before building chat sharing." That sentence opens the readout and closes it.


2. Choose three findings, and one piece of evidence each

From your board, pick the three findings that most affect the decision, not the three most interesting. For each, prepare a slide with a headline that states what you learned, the key facts with a count, why it matters, and one piece of evidence: a quote with its code and timestamp, a screenshot, or a clip of one or two minutes. That's the structure the GOV.UK Service Manual recommends for findings slides (GOV.UK Service Manual, Sharing user research findings). Check every quote in the recording first (see AI in UX research, carefully), and use clips only where participants agreed.

The rest of the findings go in an appendix and the repository. Saying "there are nine more, here's where" is better than nine rushed slides.


3. Build the ten minutes

  1. 0–1
    The answer

    "We learned that…, so we recommend…" The decision it serves, and its date.

  2. 1–2
    What we did

    8 interviews, who, when. One slide; the rest is in the report.

  3. 2–7
    Three findings

    About 90 seconds each: headline, count, why it matters, one checked quote or clip.

  4. 7–9
    Recommendations

    One per finding, each with an owner agreed beforehand.

  5. 9–10
    The ask

    The answer again, and the decision you need, from whom, by when.

10 minutes, then 10 for questions · the other findings go in an appendix and the repository

A ten-minute readout, in minutes. Half the time goes to three findings; the method gets one minute, and the answer is said twice, at the start and at the end.Structure: Marcus Andrey, CC BY 4.0. Slide proportions after the GOV.UK Service Manual, Sharing user research findings.

GOV.UK suggests one or two slides on what you did, five to ten on findings and one or two on next steps (GOV.UK); in ten minutes, keep to the low end. Questions come after the ten minutes, not inside them: book a 20-minute slot and protect the last ten for discussion.


4. Turn findings into recommendations, with owners

A finding without a next step is easy to agree with and ignore. For each one, write a recommendation and who would own it. NN/g's work on research adoption makes the point: every recommendation should have "a named owner who has both authority and accountability" (Brian Utesch and Tammi Fitzwater, NN/g, 2026). Agree the owners before the readout if you can; nobody likes being assigned work in front of their manager.


5. Rehearse against a timer

Run it once alone, out loud, with a timer. Then once for a colleague, who answers two questions afterwards: "What was the answer?" and "What are we being asked to do?" If they can't say both, rewrite the first and last minute. Cut until you finish at nine and a half minutes; live, it always runs longer.


6. Deliver, then follow up

Start with the answer, even if it feels abrupt. After the readout, within a day, send a short note: the one-sentence answer, the three headlines, the recommendations with owners, and the link to the full report in the repository. Write down which recommendations were accepted: you'll need that for Showing the impact of research.


7. Check your work

Reflection questions: What did your rehearsal colleague say the answer was, and how close was it to yours? Which finding did you cut that you were sorry to lose, and where does it live now?

Research reports people read · Writing insights that change decisions · Showing the impact of research · Defining success

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close