How to Prepare a Conference Presentation from Notes

The Problem with Going Straight from Notes to Slides

The most common mistake in preparing a conference presentation is building slides directly from research notes. Research notes are organized for the researcher: comprehensive, dense, source-cited, and structured around the process of inquiry — what was found and where. A conference audience needs something organized for them: selective, structured around the finding's significance, and sequenced to produce understanding in real time.

Slides built directly from notes inherit their organizational logic: they present information in the order it was encountered, include justification detail that the researcher needed but the audience doesn't, and compress the interesting part — the finding and its implications — into the last two minutes of a twelve-minute talk.

The transformation from research notes to conference presentation is a rewriting step, not a formatting step. It requires deciding what to say (selection), in what order (structure), and at what level of detail (density) — before opening a presentation tool.

By the end of this guide, you'll have a process for making those three decisions systematically, so the slides build the presentation rather than contain it.

---

Understanding What a Conference Presentation Must Accomplish

A conference presentation has a specific communicative goal that differs from a written paper. A paper makes an argument in full — it presents evidence, acknowledges counterarguments, reviews the relevant literature, and justifies every methodological choice. A conference presentation makes one claim memorable.

Michael Alley, in The Craft of Scientific Presentations (2nd edition, 2013, Springer), identifies the central failure of most scientific presentations: they present information rather than making an argument. A presentation that describes what the researcher did is a report. A presentation that argues that a specific finding matters, and why, is a talk.

The test: if someone who attends your talk is asked three weeks later "what was that talk about?", what do you want them to say? That answer — one or two sentences — is your presentation's thesis. Everything in the presentation builds toward or from that thesis.

For a 15-minute conference talk, the realistic structure is:

• One problem that the audience already cares about (or can be made to care about quickly)
• One gap in existing understanding
• One approach to filling that gap
• One main finding
• Two to three implications

That's it. Not the full literature review. Not every methodological consideration. Not all the findings. The one finding that most directly answers the question the talk raised.

---

Step 1: Write the Presentation's Thesis Before Building Any Slides

Before opening a presentation tool, write one sentence that states the claim your presentation will make. Not "my talk is about X." The specific claim: "I argue that [finding], which means [implication]."

Examples:

Weak (topic, not claim): "My presentation examines the effects of remote work on collaboration in cross-functional teams."

Strong (claim with implication): "I argue that remote cross-functional teams show significantly lower interdependency awareness than co-located teams — a finding that suggests current asynchronous collaboration tools address communication frequency but not shared context."

The strong version makes a specific, surprising, contestable claim. An audience member can agree with it, disagree with it, or find it useful. The weak version describes a topic — an audience member can only learn more or less about it.

Writing this sentence first forces clarity about what your research actually showed that's worth arguing. If you can't write a specific claim sentence, the presentation is not yet ready to be built.

---

Step 2: Map the Narrative Arc

A conference presentation is a story with a specific structure. The structure that works for most research presentations follows what's been called the "problem-gap-method-finding-implication" arc:

1. Problem (1-2 minutes): Why does this topic matter? What is the real-world or scholarly significance of the question you investigated? This is not the literature review — it's the hook that makes the audience care. One concrete example, one statistic, or one observation that makes the problem visceral.

2. Gap (1-2 minutes): What does existing knowledge miss? What specific question hasn't been answered? This is where you explain why your research needed to exist — not in the form of a literature review, but in the form of "here's what we still don't know."

3. Method (2-3 minutes): What did you do? The key decisions, not every step. For quantitative work: sample, design, key variables. For qualitative work: data source, analytical approach, rigor measures. Enough for the audience to evaluate the findings — not enough to replicate the study (that's what the paper is for).

4. Main finding (3-4 minutes): The one result that most directly answers the question. Show the data, figure, or evidence that makes the claim compelling. One finding shown well is worth more than five findings shown poorly.

5. Implications (2-3 minutes): What does this mean? For researchers in the audience: what does it change about how we think about this problem? For practitioners (if relevant): what should they do differently? For future research: what does this open up?

6. Conclusion (1 minute): One sentence restatement of the claim. Contact information or QR code to paper.

Total: 12-15 minutes. The remaining time is for questions.

---

Step 3: Mine Your Notes for the Right Material

With the narrative arc mapped, return to your research notes with a selective eye. You are not summarizing your notes — you are extracting the specific pieces that support each section of the arc.

For each section of the arc, identify:

Problem section:

• The most striking statistic or observation about the problem's scope or significance
• One concrete example that makes the problem real (not a literature citation — a story or observation)
• Not: every paper that has written about this problem

Gap section:

• The most direct statement of what's not yet known
• One or two citations that establish the boundaries of existing knowledge
• Not: a chronological review of the literature

Method section:

• Three key design decisions and why you made them
• The main limitation and why it doesn't invalidate the finding
• Not: every procedural step

Finding section:

• The data visualization or evidence that most clearly shows the finding
• The specific numbers, effect sizes, or examples that make it concrete
• Not: all the findings, especially the secondary or null results

Implications section:

• The two or three consequences of the finding that the audience is most likely to find useful or surprising
• One connection to a question the field is actively debating
• Not: all possible future research directions

The extraction process is also a prioritization process. Most researchers have more material than fits. The question is not "what can I cut?" but "what must I keep for the argument to work?"

---

Step 4: The One-Sentence Rule for Slides

Garr Reynolds, in Presentation Zen (2nd edition, 2012, New Riders), argues that most presentation slides fail because they try to serve two functions simultaneously: as a visual support for a live talk, and as a stand-alone document. A slide that serves both functions serves neither well — it's too dense to process as a visual during a talk, and too sparse to be useful as a document without the presenter.

A conference talk slide serves one function: supporting the talk. The test: can the audience look at this slide, look back at you, and follow what you're saying — or do they have to choose between reading the slide and listening?

The practical tool: the one-sentence title rule. Each slide's title is a complete sentence that states the slide's claim. Not "Remote Work Results" but "Remote teams show 34% lower interdependency awareness than co-located teams (p < .001)." The sentence title is the takeaway. The slide body is the evidence. If someone photographs your slide and sends it to a colleague, the title tells them what it shows.

For a 15-minute talk, the approximate slide count is 12-18 slides. More than 20 is almost always too many; fewer than 10 is often not enough structure for the audience to follow.

---

Talk vs. Poster: Different Format, Different Strategy

Many conferences offer both paper presentations (talks) and poster presentations. The preparation process differs.

For talks:

• Temporal sequence matters — the audience can only hold what they've already heard
• Each slide builds on the previous; you control the pace
• The finding can be a reveal ("so what did we find?")
• Q&A is at the end, concentrated

For posters:

• Spatial rather than temporal — visitors scan before reading
• The finding must be visible from three feet away (in the title or the first visual)
• Visitors arrive and leave at any point in your explanation
• Q&A is continuous throughout

For a poster, the preparation reversal: lead with the finding, then the evidence, then the method. The problem and gap are compressed into the background. Visitors who want detail can read; visitors who don't have time can see the result and move on. The poster title should be the claim sentence, not the topic.

---

Preparing for Questions

The Q&A period at a conference presentation is where the presentation's credibility is established or undermined. Questions most presentations should prepare for:

"How do you account for [alternative explanation]?" This is the most common question for empirical presentations. Prepare: what are the two most plausible alternative explanations for your finding, and what's your response to each? If you haven't anticipated them, someone in the audience will raise one and you'll be unprepared.

"Is this generalizable beyond your sample?" Have a clear, honest answer about the scope of your claim. "This is a study of 200 US undergraduates, so I'd be cautious about generalizing to other populations — I think the mechanism is likely to hold, but empirical confirmation in other contexts would be needed."

"What's next?" Know two specific follow-up directions that naturally extend the current work.

"Have you read [paper you don't know]?" The honest answer: "I'm not familiar with that work — could you say more about what they found? I'd be very interested to see how it relates." This is not a failure; it's a starting point for a conversation.

For each anticipated question, know your answer in two to three sentences. Longer answers eat into the Q&A time for other questions and can read as defensive.

---

Worked Example: A Psychology Student's Conference Talk

Setup: Priya is a third-year PhD student presenting a 15-minute talk at a regional psychology conference on her study of how notification interruptions affect working memory consolidation.

Her one-claim sentence: "I argue that smartphone notification interruptions during spaced repetition study sessions reduce working memory consolidation by 23%, an effect that persists even when students report the interruptions as non-disruptive."

Her arc:

• Problem (2 min): Rates of smartphone use during study; existing interventions focused on total time-off-phone, not on interruption frequency during active study
• Gap (1.5 min): No study has isolated the memory consolidation effect of notifications specifically during spaced repetition (vs. general study); existing literature measures performance at immediate post-study test only
• Method (2.5 min): Between-subjects design, 120 participants, notification condition vs. phone-off control; Anki-based spaced repetition session; test at 30 minutes and 72 hours
• Main finding (4 min): One slide — bar chart of 30-min test results (no difference); one slide — bar chart of 72-hour results (23% difference); one slide — subgroup analysis showing that self-reported "non-disruptive" interruptions show the same effect as self-reported "disruptive" ones
• Implications (3 min): Study-mode tools that silence the screen but allow notification sound underestimate the interruption effect; the 72-hour consolidation window is the mechanism, not immediate disruption; implications for phone-policy recommendations
• Conclusion + questions (2 min)

Preparation: She practiced the talk four times: once from notes, once from slides without speaking (checking slide clarity), once aloud with a timer, once with a colleague who asked challenging questions. The fourth run was 14:45 — she cut 30 seconds from the method section.

---

Key Takeaways

1. Write the thesis sentence before building any slides: the specific claim your presentation argues — not the topic it covers — is the organizing principle for everything else; if you can't write it, the presentation isn't ready.
2. The narrative arc (problem → gap → method → finding → implications) organizes talks, not literature reviews: the audience needs a story that justifies attention and builds to a punchline, not a survey of the field.
3. Mine notes selectively for each section of the arc: you are not summarizing your research notes — you are extracting the specific evidence, example, or statistic that each section of the arc requires.
4. One-sentence titles for slides make the argument explicit: a title that states the claim ("Remote teams show 34% lower interdependency awareness") is more useful than a label ("Results") because it tells the audience what the slide shows even at a glance.
5. Prepare for three specific question types: alternative explanations, scope/generalizability, and next steps — these cover most of the hard questions in a typical Q&A.

---

Conclusion

Preparing a conference presentation from research notes is a transformation, not a transfer. The research notes contain everything the researcher needs to do the research; the presentation contains the specific, curated argument that the audience needs to understand one finding and its implications. The process — thesis sentence first, narrative arc second, selective extraction from notes third, slide construction last — produces a talk structured around the audience's needs rather than the researcher's process. For a field where most presentations show more information than any audience can absorb, a presentation that argues one claim clearly and memorably is the one that gets cited in hallway conversations at the end of the conference.

See also: Clip Articles for Later Reading.