Communicating Data to Non-Technical Audiences

You have spent weeks analyzing data, running statistical tests, and interpreting results. Now your preceptor asks you to present findings to community partners, elected officials, or program staff who do not share your statistical training. The gap between what you know and what they need to understand feels enormous.

This translation challenge is one of the most valuable skills you can develop during your practicum. Public health impact depends not on conducting sophisticated analyses but on communicating findings in ways that inform decisions and motivate action.

Understanding Your Audience

Before crafting any presentation, invest time understanding who will receive your information. What decisions will they make based on your findings? What background knowledge do they bring? What concerns or priorities shape how they will hear your message?

A county commissioner deciding budget allocations needs different information than a program manager adjusting service delivery. A community coalition planning advocacy needs different framing than clinicians changing practice protocols. The same data serves different purposes depending on who uses it.

Ask your preceptor about the audience before you begin preparing. What questions do they typically ask? What communication formats have worked well previously? What terminology resonates or creates confusion? This preparation is similar to the audience analysis required when presenting to unfamiliar audiences in any public health context.

Leading with Implications

Technical presentations often follow the structure you learned in research methods: background, methods, results, conclusions. This format works for academic audiences who want to evaluate your methodology before accepting your conclusions.

Non-technical audiences prefer inverted structures. Lead with what your findings mean for them. What should they do differently based on this information? What decisions does this evidence support? Hook their attention with relevance before providing supporting detail.

Consider opening with a statement like this: "Our analysis suggests that expanding clinic hours on Saturdays could reach two hundred additional families currently missing preventive care." This immediately communicates practical relevance. The methodology that supports this conclusion can follow for those who want it.

Translating Statistical Concepts

Statistical significance, confidence intervals, and p-values communicate important information to trained analysts. They often confuse or mislead non-technical audiences. Translate these concepts into plain language that preserves meaning without requiring statistical training.

Instead of reporting that results were statistically significant at p less than 0.05, explain that you are confident the difference you observed reflects a real pattern rather than random chance. Instead of confidence intervals, describe the range of likely values in concrete terms.

Relative risks and odds ratios particularly benefit from translation. Saying that a risk factor doubles the likelihood of an outcome is more accessible than reporting an odds ratio of 2.0. Better still, provide absolute numbers: "Among every 100 people with this exposure, we expect 10 cases compared to 5 cases among those without exposure."

Visualizing Effectively

Well-designed visuals communicate complex patterns more effectively than text or tables. However, visualization conventions that work for technical audiences often fail with general audiences.

Simplify charts to communicate single key messages. Remove gridlines, excessive axis labels, and decorative elements that distract from your main point. Use color strategically to highlight the comparison or trend you want audiences to notice.

Bar charts and line graphs remain the most universally understood formats. Pie charts work only for showing parts of a whole. Avoid scatter plots, box plots, and other formats that require statistical training to interpret correctly.

Always provide explicit interpretation. Do not assume audiences will draw the conclusion you intend from a visual. Include a clear title or caption that states what the chart shows: "Vaccination rates have increased 15% since program launch" rather than "Vaccination rates 2020-2024."

Anticipating Questions

Non-technical audiences often ask questions that seem basic or tangential to you. These questions reflect legitimate concerns about whether your findings apply to their context.

Prepare for questions about data quality and sources. Where did this information come from? How recent is it? Does it include our community specifically? These questions reflect appropriate skepticism rather than misunderstanding.

Also anticipate questions about what the data does not show. Can you explain why this pattern exists? What should we do about it? Some questions extend beyond your analysis. Acknowledge limitations honestly while redirecting to what you can address. If navigating hierarchical communication channels is new to you, practice how you will respond to questions from leadership with authority you are not accustomed to addressing.

Practicing and Getting Feedback

Before presenting to external stakeholders, practice with your preceptor or colleagues. Ask specifically whether your explanations make sense to someone without your technical background. Note where they ask clarifying questions and adjust those sections.

Request feedback after presentations as well. What resonated? What created confusion? What questions suggested you needed to explain something differently? Each presentation becomes a learning opportunity for the next one. Writing up your findings clearly also strengthens your academic writing skills for connecting theory to practice in your ILE and other program documents.

FAQ

Q: How do I simplify data without losing important nuance? A: Lead with the main finding in accessible language, then layer in nuance for those who want it. Provide a brief verbal or written caveat about limitations without letting caveats overshadow the core message. You can always provide detailed technical appendices for stakeholders who want the full picture.

Q: What should I do when an audience member challenges my data during a presentation? A: Respond calmly and acknowledge their concern. If you can address it with evidence, do so briefly. If the challenge requires further investigation, say so honestly and commit to following up. Defensiveness undermines credibility more than admitting uncertainty does.

Q: Should I include methodology in my presentation to non-technical audiences? A: Include a brief, accessible description of your methods—enough for the audience to understand where the data came from and trust its validity. Keep it to one or two sentences or one slide. Save detailed methodology for written reports or appendices rather than the presentation itself.

The ability to translate technical findings into accessible language distinguishes public health practitioners who influence decisions from those whose work sits unused in reports. Your practicum offers valuable practice in developing this essential skill.