Adapting a Thesis Defense for a General Audience

By Dr. Zubair Khalid, DVM, MS, PhD · 2026-08-27

Quick Answer

• Reframe your thesis defense presentation around one central question that a general audience can grasp within the first minute, then build every slide to answer that question.
• Replace technical methods with analogies and visuals that show what you did and why it matters, while keeping a backup slide with full technical detail for expert questions.
• Accept that you cannot preserve every nuance from your defense, prioritize a memorable take-home message over completeness when speaking to non-specialists.

Why a Defense Presentation Fails in Public Settings

A thesis defense presentation is built for a specific audience: committee members who share your disciplinary vocabulary, understand your methods, and evaluate your contribution against field-specific standards. That same structure collapses when presented to a general audience because the assumptions underneath it no longer hold.

Committee members arrive with context. They know why your research question matters, what methods are standard in your field, and what counts as a meaningful result. A public audience brings none of that context. They have limited attention, no obligation to evaluate you, and no shared technical vocabulary. When you present defense slides unchanged, you ask listeners to do work they did not sign up for.

The core problem is not that your research is too complex. The problem is that your presentation assumes prior knowledge that a general audience does not have. Your defense presentation answers questions your committee would ask. A public talk must answer questions your neighbor, your librarian, or a high school student would ask.

This transformation matters for practical reasons. Funding agencies increasingly expect researchers to communicate the value of their work to non-specialists. Public outreach events, university showcases, and community talks are common venues where your ability to translate your research affects how your work is perceived. The same skills apply when you interview for jobs outside academia, present to industry partners, or explain your work to family members who ask what you actually do all day.

At a Glance

Core Principles for Translating Your Research

Identify the One Question That Matters

Every thesis has a central question, but the way you phrase it for your committee differs from how you phrase it for the public. Your committee version might be "How does X modulate Y under Z conditions?" Your public version should be "Why do some people respond to treatment while others do not?" or "What makes one material stronger than another?"

The translation is not dumbing down. It is finding the human problem your research addresses. Ask yourself what problem existed before your work and what changed because of it. That problem, stated in plain language, becomes your public research question.

Write this question on one index card. If you cannot fit it, you have not simplified enough. Every slide in your public presentation should connect back to this question. If a slide does not help answer it, cut the slide.

Reframe Methods as Actions, Not Protocols

Your defense presentation describes methods with precision because your committee needs to evaluate their validity. A general audience needs to understand what you did well enough to trust your conclusion. These are different goals.

For each method in your defense presentation, ask what action it represents. Did you compare two groups? Track changes over time? Measure a physical property? Build something and test it? Each of these actions can be explained with a simple visual or analogy.

Consider a study that used RNA sequencing to compare gene expression. The defense version describes library preparation, sequencing depth, and bioinformatics pipelines. The public version might say "We looked at which genes were turned on and off in healthy cells compared to diseased cells, like reading the instruction manual for each cell to find which pages were different."

The analogy is not perfect, and it does not need to be. It gives the audience a mental model that is approximately correct, which is more useful than a precise explanation they cannot follow.

Simplify Data Visualization

Complex figures that work in a defense presentation often fail in public settings because they require too much interpretation. A figure with multiple panels, error bars, and statistical annotations assumes a viewer who knows how to read those elements.

For a public presentation, create new figures or simplify existing ones. Show one main result per visual. Use large text. Label axes in plain language instead of technical abbreviations. Choose colors that are distinguishable for color-blind viewers. If a figure requires more than ten seconds to understand, it needs to be simplified.

You do not need to discard your complex figures entirely. Keep them in a backup section of your slide deck for questions from experts in the audience. The main presentation should show only the visuals that support your central message.

Craft a Memorable Take-Home Message

A defense presentation ends with conclusions and future directions. A public presentation should end with one sentence the audience can repeat to someone else. This is your take-home message.

A strong take-home message states what you found and why it matters in plain language. It is specific enough to be credible and simple enough to be remembered. "We found that a common food additive changes how gut bacteria behave, which may explain why some people have digestive problems" is a take-home message. "Our results demonstrate a statistically significant interaction between dietary emulsifiers and the gut microbiome composition" is not.

Test your take-home message by saying it to a friend outside your field. Ask them to repeat it back. If they cannot, revise it.

Practical Workflow for Transforming Your Presentation

Step 1: Inventory Your Defense Slides

Open your defense presentation and list every slide on a piece of paper. For each slide, write down its purpose in one sentence. This inventory forces you to articulate what each slide contributes.

Group the slides into categories: background, methods, results, discussion, and conclusions. You will likely find that your defense presentation has more background and methods slides than you remembered. These are the slides that most need translation.

Step 2: Write the Public Narrative

Before touching your slides, write a short narrative of your talk in plain language. Aim for 300 to 500 words. This narrative should follow a simple structure:

• What problem did you start with?
• What did you do to investigate it?
• What did you find?
• Why does it matter?

Write this narrative without looking at your defense slides. If you cannot explain your work in plain language from memory, you have not fully understood it. This writing exercise is the most important step in the transformation process.

Step 3: Map Defense Slides to Public Slides

For each slide in your defense presentation, decide whether it survives in your public talk, needs to be translated, or should be cut. Use these criteria:

• Does this slide help answer your public research question?
• Can a general audience understand it with minimal explanation?
• Does it support your take-home message?

Slides that fail all three criteria should be cut. Slides that pass the first criterion but fail the others need translation. Slides that pass all three can be kept with minor adjustments.

Step 4: Translate Methods and Results

For each methods slide that survives, write a plain-language version of what you did. Replace technical terms with everyday language. Add a visual that shows the action instead of the protocol.

For each results slide, identify the single most important finding. Create a simplified visual that shows that finding clearly. Move detailed results to your backup section.

Step 5: Build the Public Slide Deck

Your public presentation should follow a different structure than your defense. A proven structure for public talks is:

1. Opening hook that introduces the problem
2. Your research question in plain language
3. What you did, explained simply
4. What you found, shown clearly
5. Why it matters
6. Take-home message

Aim for 10 to 15 slides for a 20-minute talk. This is fewer than most defense presentations, which often run 30 to 50 slides. The reduced slide count forces you to focus on what matters.

Step 6: Practice and Get Feedback

Practice your public presentation out loud, ideally with a non-specialist listener. Ask them to tell you what they remember afterward. Their answer will tell you whether your take-home message is working.

Record yourself and watch the recording. Look for places where you slip back into technical language or rush through an explanation. These are the moments that will lose a general audience.

Options and Tradeoffs in Presentation Design

Slide Density

You have two options for handling the volume of content in your defense presentation. The first is to cut aggressively, keeping only the slides that support your central message. The second is to keep more slides but simplify each one. The first option produces a cleaner talk but risks losing nuance. The second option preserves more content but risks overwhelming the audience.

For most public talks, aggressive cutting is the better choice. A general audience remembers a few points delivered clearly. They do not remember a comprehensive survey delivered quickly.

Technical Backup Slides

You can include a backup section at the end of your slide deck with technical details, complex figures, and full methods. This section is not shown in the main talk but is available if someone asks a detailed question.

This approach gives you the best of both worlds. Your main presentation stays accessible, and you can still answer expert questions with precision. Label the backup section clearly so you can navigate to it quickly during Q&A.

Analogies and Metaphors

Analogies are powerful tools for explaining technical concepts, but they have limitations. Every analogy breaks down at some point. The key is to use analogies that are approximately correct for the point you are making and to avoid pushing them too far.

When you use an analogy, state it briefly and move on. Do not belabor it. If an audience member asks a question that exposes the limits of the analogy, acknowledge the limitation and provide the technical explanation.

Audience Interaction

Some public talks benefit from audience interaction, such as asking a question at the start or inviting a show of hands. This can increase engagement but also adds unpredictability. If you use interaction, have a plan for what to do if the audience does not respond as expected.

For most researchers, a well-structured talk with clear visuals is more reliable than interactive elements. Save interaction for settings where you are comfortable with the audience and the format.

Observations and Measurements for Presentation Success

Measuring Audience Understanding

You cannot directly measure what an audience understands during your talk, but you can observe indirect signals. Watch for these behaviors:

• Are people looking at you or their phones?
• Do they laugh at appropriate moments?
• Do they nod or show other signs of engagement?
• Do questions at the end reflect understanding of your main points?

These observations are imperfect but useful. If you notice attention dropping, you may need to adjust your delivery, add more visuals, or simplify your language.

Recording Your Practice Sessions

Record your practice sessions and review them systematically. Note the following:

• How many times do you use technical terms without explanation?
• How long do you spend on each slide?
• Where do you rush or slow down?
• Do you maintain eye contact or read from notes?

These measurements give you concrete data about your presentation. Use them to target specific improvements.

Timing Your Talk

Time your presentation during practice. A 20-minute talk should be practiced to run 18 to 19 minutes, leaving buffer for transitions and unexpected pauses. If your practice run exceeds your time limit, cut content instead of speaking faster.

A common failure pattern is spending too much time on background and methods, leaving insufficient time for results and implications. Check your timing by section to ensure you are allocating time proportionally to importance.

Records and Documentation

Creating a Presentation Log

Keep a log of your public presentations, noting the date, venue, audience type, and what worked or did not work. This log becomes a valuable reference for future talks. After each presentation, write down:

• What questions did the audience ask?
• Which explanations seemed to work well?
• Which parts lost audience attention?
• What would you change next time?

This documentation helps you improve systematically instead of starting from scratch each time.

Maintaining Your Slide Versions

Keep separate files for your defense version and public version of each presentation. Label them clearly with dates and versions. This prevents confusion and allows you to track changes over time.

When you update your public presentation, save the new version with a new date. This creates a record of how your communication has evolved, which is useful for job applications and grant reports that ask about outreach activities.

Connecting to Your Researcher Identity

Your public presentations are part of your professional record. Maintaining a consistent researcher identity across your publications, presentations, and outreach activities helps others find and connect your work. An ORCID record provides a persistent identifier that links your research outputs and activities, which can be useful when you apply for grants or positions that value public communication.

Common Failure Patterns

The Background Overload

Many researchers spend too much time on background information, trying to give the audience enough context to understand their work. This approach backfires because the audience forgets the background by the time you reach your results.

The fix is to provide only the minimum background needed to understand your research question. If you can state your question without a slide of historical context, do so. Trust that the audience can follow a well-told story without a full literature review.

The Methods Dump

Presenting methods in technical detail is a common failure in public talks. Researchers who are proud of their technical work want to show it, but a general audience cannot evaluate methodological choices and does not need to.

The fix is to describe what you did in one or two sentences with a simple visual. Save the technical details for backup slides or Q&A.

The Data Wall

Showing complex figures with multiple panels, error bars, and statistical annotations is a reliable way to lose a general audience. They cannot parse the visual quickly enough to follow your argument.

The fix is to create simplified figures that show one finding each. Use large text and clear labels. If a figure requires explanation, it is too complex.

The Missing Take-Home Message

Some researchers end their public talks without a clear take-home message. The audience leaves with a vague sense that the research was interesting but cannot articulate what it found.

The fix is to state your take-home message explicitly in the last minute of your talk. Repeat it once or twice. Make it the last thing the audience hears.

The Q&A Trap

The question period after a public talk can derail your message if you are not careful. An audience member may ask a highly technical question that pulls you into a detailed explanation, losing the rest of the audience.

The fix is to answer technical questions briefly and redirect to your main message. You can say something like "That is a detailed question. The short answer is X, and I would be happy to discuss the details with you afterward." This acknowledges the question without sacrificing the clarity of your talk.

Limitations and Honest Boundaries

What You Cannot Simplify

Some research cannot be fully translated for a general audience without losing essential meaning. If your work involves complex mathematics, specialized equipment, or field-specific concepts that have no everyday equivalent, you may need to accept that some aspects will remain opaque.

In these cases, focus on what the audience can understand: the problem you are addressing, the general approach, and the potential implications. Be honest about what you cannot explain simply.

The Risk of Oversimplification

There is a tension between accessibility and accuracy. Simplifying your research for a public audience risks creating misunderstandings, especially if your work is nuanced or preliminary.

You can manage this risk by being explicit about uncertainty. If your findings are preliminary, say so. If your results apply only under specific conditions, state those conditions in plain language. Honesty about limitations builds trust with your audience.

Institutional and Ethical Boundaries

When you present your research publicly, you represent your institution and your field. Be aware of any institutional policies about public communication of research findings. If your work involves unpublished data, proprietary information, or sensitive topics, check with your advisor or institution before presenting publicly.

Research integrity standards apply to public presentations as well as publications. Present your findings accurately, acknowledge the contributions of collaborators, and do not overstate your conclusions. The same ethical principles that govern authorship and publication apply to how you communicate your work to the public.

Quality Controls and Professional Escalation

Pre-Presentation Review

Before you present publicly, have someone review your presentation. Ideally, this reviewer should be outside your field. Ask them to identify any parts they do not understand. Their feedback will reveal where your explanations need work.

If possible, do a full practice run with your reviewer present. This gives you experience delivering the talk and allows your reviewer to give feedback on delivery as well as content.

When to Seek Professional Help

If you are preparing for a high-stakes public presentation, such as a major outreach event or a presentation to funders, consider seeking help from your institution's communication office or a presentation coach. These professionals can provide feedback that goes beyond what a colleague can offer.

Your institution may also offer workshops or resources on science communication. These can be valuable for developing skills that transfer across presentations.

Escalation Criteria

If you encounter any of the following situations, escalate to your advisor, supervisor, or institution's communication office:

• You are asked to present research that has not been approved for public release
• Your presentation involves sensitive data or topics that could harm participants or communities
• You are uncertain about institutional policies regarding public communication
• You are asked to present on a topic outside your expertise

These situations require professional judgment beyond what this guidance can provide. Seek advice from people who know your specific context.

Safety and Regulatory Context

Research Integrity in Public Communication

Public presentations are part of your research record. The same standards of honesty and accuracy that apply to publications apply to your talks. Misrepresenting your findings, failing to acknowledge collaborators, or overstating your conclusions damages your credibility and your field.

The Committee on Publication Ethics core practices address authorship, data integrity, and conflicts of interest. These principles extend to how you present your work publicly. If you have questions about whether a presentation is appropriate, consult your institution's research integrity office.

Data Management Considerations

If your public presentation includes data, consider whether your data management plan covers this use. Many funding agencies require data management and sharing plans that describe how data will be handled. Public presentations are one way research outputs are shared, and your data management plan should account for them.

If you are presenting data that is part of a funded project, check your funding agreement for any requirements about public communication. Some funders require acknowledgment in presentations or have specific guidelines about how findings can be shared.

Funding Acknowledgment

If your research was funded by a grant, your public presentation should acknowledge the funding source. This is often a requirement of the funding agreement. Check your grant documents for specific language requirements.

The National Institutes of Health provides guidance on grant policies and requirements. If you are unsure about your obligations, consult the funding agency's guidance or your institution's grants office.

Frequently Asked Questions

How is a public presentation different from a thesis defense?

A thesis defense is evaluated by experts who share your technical vocabulary and understand your field's standards. A public presentation must work for people without that background. The defense emphasizes methodological rigor and scholarly contribution. The public talk emphasizes the problem you address, what you did in plain language, and why it matters. You keep the same research but change the framing, the level of technical detail, and the structure of the narrative.

How do I explain complex methods to a general audience?

For each method, identify the action it represents and describe that action in everyday language. Use an analogy that gives the audience an approximately correct mental model. Show a simple visual that illustrates what you did. Keep the technical details in backup slides for expert questions. The goal is not to fully explain your methods but to give the audience enough understanding to trust your conclusions.

How many slides should a public presentation have?

For a 20-minute talk, aim for 10 to 15 slides. This is fewer than most defense presentations because public audiences cannot process information as quickly as experts. Each slide should make one point clearly. If a slide requires more than a few seconds to understand, simplify it or cut it. You can keep additional slides in a backup section for Q&A.

What should I do with complex figures from my defense presentation?

Create simplified versions of your most important figures for the main presentation. Show one finding per visual, use large text, and label axes in plain language. Keep the complex versions in a backup section for expert questions. If a figure cannot be simplified effectively, consider replacing it with a different type of visual or an analogy.

How do I handle technical questions from the audience?

Answer technical questions briefly and redirect to your main message. You can acknowledge the question, give a short answer, and offer to discuss details afterward. This respects the questioner without losing the rest of the audience. If you do not know the answer, say so honestly and offer to follow up. Do not fabricate an answer.

How do I know if my public presentation is working?

Practice with a non-specialist listener and ask them what they remember afterward. Record yourself and review the recording for places where you use technical language or lose clarity. During the actual presentation, watch for signs of engagement such as eye contact, nodding, and relevant questions. After the talk, note what questions were asked and what seemed to resonate.

Should I acknowledge my funding sources in a public presentation?

Yes, if your research was funded by a grant, your public presentation should acknowledge the funding source. This is often a requirement of the funding agreement. Check your grant documents for specific language requirements. The National Institutes of Health and other funders provide guidance on grant policies and requirements. If you are unsure, consult your institution's grants office.

What if my research cannot be simplified for a general audience?

Some research is inherently difficult to translate. Focus on what the audience can understand: the problem you address, your general approach, and the potential implications. Be honest about what you cannot explain simply. You can also use analogies that are approximately correct, acknowledging their limitations. The goal is to give the audience a meaningful understanding of your work, not a complete technical explanation.

Using the Evidence

Related Articles

• Public Health Scientist Careers: From Research to Practice
• Data Presentation in Research: Tables, Figures, and Text
• The Role of the Research Ethics Committee: What Researchers Need to Know
• Ethical Considerations in Psychological Research: A Guide for Students and Early-Career Researchers
• How to Present Data in Research Papers: Methods, Tables, and Figures

References and Further Reading

• Research Methods Resources. National Library of Medicine.
• EQUATOR Network. EQUATOR Network.
• Core Practices. Committee on Publication Ethics.
• NIH Grants and Funding. National Institutes of Health.
• ORCID for Researchers. ORCID.
• Data Management and Sharing Policy. National Institutes of Health.
• NCBI Literature Resources. National Center for Biotechnology Information.
• PubMed. National Library of Medicine.

This article is educational and does not replace institutional policy, professional advice, or applicable safety and regulatory requirements.