Rehearse the decision your audience needs to make, then test the delivery conditions and the questions that could challenge your recommendation.
Define what the audience should leave with
Write one sentence describing what the audience should understand or decide after your presentation. Then list the evidence they need to reach that point. A project update, a research talk, and a proposal require different levels of detail.
For each slide or section, write its job in the talk. If two sections do the same job, consider combining them. If a claim is important but has no evidence, add the evidence or narrow the claim before polishing your delivery.
Keep the required duration, format, and accessibility needs in view. Solo practice cannot tell you everything about a real audience, so make a note of assumptions you would want a colleague or organizer to check.
Give each rehearsal a different job
Changing slides while rehearsing delivery makes it hard to tell what improved. Separate the checks, then combine them in a final run.
| Pass | Test | Evidence to collect |
|---|---|---|
| Message | Can you state the recommendation without slides? | One sentence naming the audience decision |
| Explanation | Does each chart support that decision? | A spoken conclusion, not just a description of axes |
| Delivery | Can you finish within the assigned slot? | Which sections overrun, including transitions |
| Challenge | Can you explain a limitation or alternative? | A response that names the uncertainty and next check |
Duarte recommends rehearsing aloud under realistic conditions and learning concepts rather than memorizing every word. The four-pass matrix is our own exercise. Duarte: presentation rehearsal →
A chart is not yet a recommendation
Slide narration: “The blue bars are new tickets and the purple bars are resolved tickets.”
Decision-oriented explanation: “New requests exceeded completed requests in each of these three weeks, so the queue grew. Before adding staff, I recommend checking which categories account for the gap. This chart counts requests, not the time each takes, so it cannot yet tell us whether staffing is the main constraint.”
The second version gives the audience a claim, a limitation, and a next action. It avoids treating a ticket count as a workload measurement. Prepare the follow-up: “What would you measure before making a staffing recommendation?”
Practice a disruption without beginning again
Stop at a randomly chosen slide. State the decision, explain the current slide’s contribution, and continue. Then rehearse losing access to the chart: can you summarize the supported finding without inventing a number? A backup explanation is more useful than memorizing a longer opening.
Rehearse in three distinct passes
- Explanation pass: Say the main point and evidence for each section without reading full sentences from the slide. Note where you need to define a term or explain why a chart matters.
- Transition pass: Practice the sentence that connects each section to the next. Start from a middle slide as well as the beginning so one interruption does not force a full restart.
- Full run: Use the actual display setup if possible, speak aloud, and include the opening, ending, and allotted question time. Note where the talk runs long.
These are suggested exercises, not a validated scoring system. If you record a rehearsal, review one dimension at a time: first the argument, then timing and navigation. A fluent delivery does not make an unsupported conclusion correct.
A worked example: explain the meaning of a chart
Fictional first version: “This slide shows our requests for the month. The blue bar is email, and the green one is chat.”
Revised practice version: “Most recorded requests in this sample came through email. Before changing staffing, we need to check whether chat requests were logged as consistently. My proposed next step is to compare the two logging processes.”
The second version gives the chart a role in the decision while preserving a limitation. In your own presentation, verify the data and explain what it does and does not support. Do not use an exercise example as real evidence.
Prepare for Q&A without predicting every question
Write one question in each category:
- Evidence: What supports this claim?
- Alternative: What other explanation or approach did you consider?
- Scope: Where would this conclusion not apply?
- Action: What should happen next, and who would do it?
Draw a question after a section and answer it without restarting the talk. If you do not know, state what you would need to check. Distinguish a possible answer from a verified result.
A practice partner or AI can generate additional questions, but plausible questions are not evidence that an actual audience will ask them. If possible, seek feedback from someone with the audience's level of subject knowledge.
Practice a small disruption
Skip a slide deliberately, then explain the missing point without relying on the visual. Start from the middle of your notes. Practice returning to the main argument after a question. These exercises expose dependencies that a perfect uninterrupted run can hide.
If the full run is too long, remove a section that does not support the audience's task before trying to speak faster. Keep necessary definitions and limitations. End with the decision, conclusion, or next step you want the audience to remember.
Use your final review to choose one change. “Explain the denominator before comparing the bars” is more actionable than “be more confident.”
Your practice worksheet
Use the prompts above and record your own evidence. The worksheet is a plain-text file you can edit or print; no account is needed.
Method and scope
Further practice ideas: Carnegie Mellon Public Communication for Researchers: Communication Practice. This guide and worksheet are original atula materials, not a university-endorsed program or a validated assessment.
Turn this into a real conversation.
Bring your own experience to live practice with atula. Work on your answer, then handle a follow-up.
Practice live with atula ↗Apply for early access. Availability is limited; applying does not start an immediate session.
Need to organize an example first? Try the STAR builder →