Communicating findings to non-technical stakeholders is one of the most important skills in program evaluation because even the strongest analysis has little value if decision-makers cannot understand, trust, and use it. In program evaluation, findings are the tested conclusions drawn from evidence about a program’s design, delivery, outcomes, efficiency, and impact. Non-technical stakeholders include executives, board members, funders, frontline managers, community partners, and participants who need clear implications rather than methodological detail. Reporting and communicating findings is the broader practice of turning raw analysis into useful messages, formats, and conversations that guide action.
I have seen solid evaluations lose momentum because reports answered the evaluator’s questions instead of the audience’s questions. A statistical appendix may be accurate, but if a superintendent, nonprofit director, or grant officer cannot quickly grasp what changed, why it matters, and what should happen next, the work stalls. This is why communication sits at the center of effective program evaluation. It affects whether leaders renew funding, whether staff adjust implementation, whether partners align around priorities, and whether communities see the process as credible and respectful.
This hub article covers reporting and communicating findings across the full lifecycle: identifying stakeholder needs, shaping key messages, choosing formats, using visuals, presenting limitations, and supporting decisions after publication. It also explains how to tailor communication without distorting evidence. Good reporting is not about “simplifying” until nuance disappears. It is about translating methods, uncertainty, and results into plain language that preserves accuracy. When done well, communication builds trust, increases utilization, and helps a program evaluation move from a document on a shared drive to a tool for better decisions.
Start with stakeholder needs, decisions, and context
The first rule of communicating findings to non-technical stakeholders is to begin long before the final report is drafted. In my own evaluation work, the clearest reports came from projects where we mapped users, decisions, and timing at the start. A city agency commissioner may need a two-page decision brief before budget hearings. A program manager may need implementation findings broken down by site within two weeks. A funder may want outcome evidence tied directly to grant objectives and reporting requirements. If those needs are identified late, communication becomes reactive and fragmented.
A practical way to frame this is to ask five questions: Who will use the findings? What decisions are coming? What level of detail can each audience absorb? What concerns or political sensitivities shape interpretation? What communication channels already carry credibility with that audience? These questions guide both analysis and reporting. They also reduce the common mistake of producing one master report and expecting it to work equally well for a board meeting, staff training, community debrief, and grant renewal package.
Context matters as much as content. In program evaluation, the same finding can land very differently depending on organizational history, public scrutiny, and prior expectations. For example, if an afterschool program served fewer students than planned but improved attendance among those enrolled, leaders may interpret that as either underperformance or proof of promising targeting. The evaluator’s job is to make the context visible: implementation constraints, referral patterns, staffing turnover, baseline conditions, and comparison points. Without that framing, stakeholders often substitute assumptions for evidence.
Build a message architecture before writing the report
Non-technical audiences understand findings best when the evaluator deliberately structures the story. I recommend creating a message architecture before drafting slides, memos, or reports. That means identifying the headline conclusion, the two to four supporting findings, the strongest evidence for each, the limitations that affect interpretation, and the action implied. This is different from simply listing every analytic result in the order it was produced.
The strongest headline conclusions are specific and decision-relevant. “The workforce program improved short-term job placement but did not increase six-month retention” is more useful than “Results were mixed.” “Participants with weekly coaching had better completion rates than those receiving monthly coaching” is stronger than “Coaching mattered.” Decision-makers can act on the first versions because they clearly connect evidence to a manageable issue.
Good message architecture also separates findings from recommendations. Findings describe what the evidence shows. Recommendations explain what stakeholders should consider doing in response. Blurring the two can make audiences feel pushed toward a preferred answer before they understand the facts. In a hospital outreach evaluation, for example, you might first report that no-show rates fell 18 percent after text reminders were introduced, then explain that scaling the reminder workflow across clinics is a reasonable operational next step. The evidence comes first; the advice follows from it.
Plain language is essential, but precision still matters. Replace technical labels with concrete wording: say “difference between groups” instead of “between-group variance” when possible, yet do not erase important distinctions such as correlation versus causation. If the evaluation used a randomized controlled trial, say so and explain that random assignment strengthens confidence that the program caused the observed effect. If the design was quasi-experimental, state that the findings indicate a likely contribution, not definitive proof of causality. Non-technical does not mean incapable of nuance; it means the nuance must be explained clearly.
Choose the right format for the audience and moment
Reporting and communicating findings is not a single product. It is a portfolio of products matched to audience needs. In practice, I usually prepare a layered set of outputs: an executive summary for leaders, a full technical report for analysts and compliance needs, a slide deck for meetings, and a short action memo for managers responsible for implementation changes. Sometimes a community-facing summary in accessible language is equally important, especially when participant trust is part of program success.
Each format should answer predictable stakeholder questions directly. Executives usually ask: What happened, why does it matter, what are the risks, and what should we do next? Program staff ask: Which sites or groups performed differently, what barriers drove the results, and what changes are realistic? Funders ask: Were goals met, how strong is the evidence, and what are the implications for future investment? Community stakeholders ask: Were participants heard fairly, what benefits emerged, and what will change because of this evaluation?
The table below shows how communication formats differ in purpose, length, and typical content.
| Format | Primary audience | Best use | Key content |
|---|---|---|---|
| Executive summary | Executives, board, funders | Fast decisions | Headline findings, implications, risks, next steps |
| Full report | Evaluators, analysts, oversight staff | Documentation and transparency | Methods, data sources, detailed findings, limitations, appendices |
| Slide presentation | Mixed stakeholder groups | Discussion and alignment | Core messages, visuals, speaking points, decision prompts |
| Action memo | Program managers | Operational change | Priority issues, responsible owners, timelines, implementation considerations |
| Community summary | Participants, partners, public | Accessibility and trust | Plain-language findings, participant voice, practical implications |
Timing is part of format choice. A perfect report delivered after a budget vote is less useful than a concise brief delivered one week earlier. In developmental or implementation-focused evaluations, interim updates are often more valuable than a single final product. Short readouts can flag emerging issues, validate course corrections, and prepare stakeholders for final findings so there are fewer surprises. That cadence improves uptake because people have already engaged the evidence before the formal report arrives.
Use visuals, narrative, and evidence together
Many non-technical stakeholders process information faster through visuals and narrative than through dense text. The key is to use visuals that clarify rather than impress. A simple bar chart comparing target versus actual enrollment by site is often more effective than a multi-axis dashboard. Good visuals answer one question at a time, label the takeaway directly, and avoid forcing the audience to infer the point. I advise teams to title charts with conclusions, not topics. “Site B retained participants at twice the rate of Site D” is far better than “Retention by site.”
Narrative matters because evaluation findings often involve human systems, not only numeric shifts. In a workforce program, for instance, quantitative data may show that completion rates improved after transportation stipends were introduced. Interviews can explain why: participants could reach training consistently, reduce missed sessions, and stay engaged long enough to earn credentials. Combining those forms of evidence gives non-technical stakeholders a more complete basis for action. It also reduces resistance because people can see both the measured outcome and the lived mechanism behind it.
That said, narrative should never overrule evidence. A memorable quote from one participant can illuminate a trend, but it cannot stand in for broad results. I often state this explicitly in presentations: stories illustrate patterns; they do not prove them. This keeps communication grounded and protects against cherry-picking. Tools such as Tableau, Power BI, Excel, and Datawrapper can help produce clear visuals, but software does not solve the communication problem by itself. The evaluator still has to decide what the audience needs to understand and what visual form will support that understanding.
Address limitations, uncertainty, and difficult findings honestly
Trust grows when evaluators explain what the evidence can and cannot support. Non-technical stakeholders do not need every statistical caveat, but they do need an honest account of uncertainty. If response rates were low, say how that affects confidence. If comparison groups differed at baseline, explain that estimated effects should be interpreted cautiously. If administrative data were incomplete, identify the likely direction of bias where possible. These statements do not weaken the evaluation. They show discipline and protect decision-makers from overclaiming.
Difficult findings require especially careful communication. When results are disappointing, leaders may feel defensive, and staff may hear criticism of their work rather than analysis of system conditions. I have found it useful to distinguish performance findings from blame. For example, if maternal health outreach failed to reach target enrollment, the report should examine referral workflows, staffing vacancies, transportation barriers, and eligibility rules before implying weak staff effort. This approach keeps the conversation focused on causes that can be addressed.
Balance is critical. Honest reporting does not mean framing every result negatively. If a literacy program improved reading gains for early enrollees but had inconsistent attendance later in the year, present both truths. Stakeholders need a complete picture: what worked, for whom, under what conditions, and where results fell short. That balanced framing is more credible than a document that sounds either defensive or punitive.
Turn findings into decisions, learning, and follow-through
The final measure of communication quality is use. A well-communicated evaluation leads to decisions, learning, or changed practice. To support that outcome, end every reporting process with explicit decision pathways. Identify what choice is pending, what evidence informs it, who owns the response, and when follow-up will occur. Without this step, even strong findings can dissolve into general agreement with no operational change.
One effective tactic is to pair each major finding with an implementation question. If participant satisfaction is high but completion is low, ask which barriers are interrupting attendance and what operational fix should be tested first. If one site consistently outperforms others, ask what practices can be standardized and what local conditions limit replication. This shifts meetings away from passive review and toward applied learning.
Communication should also continue after the main report is delivered. In many evaluations, I schedule follow-up sessions thirty to sixty days later to review what actions were taken, what questions remain, and whether additional analysis is needed. That loop reinforces accountability and helps stakeholders use findings correctly rather than selectively. As the hub page for reporting and communicating findings in program evaluation, this topic connects every later article on executive summaries, data visualization, presentation strategy, audience tailoring, and recommendation writing. Master these fundamentals, and your evaluation work becomes easier to understand, easier to trust, and far more likely to improve real programs. Review your current reporting process, identify one audience you are underserving, and redesign your next findings product around the decisions that audience must make.
Frequently Asked Questions
Why is communicating findings to non-technical stakeholders so important in program evaluation?
Communicating findings clearly to non-technical stakeholders is essential because evaluation only creates value when people can understand the results and act on them. In program evaluation, findings represent tested conclusions drawn from evidence about how a program was designed, delivered, and experienced, as well as what outcomes, efficiencies, and impacts it produced. Executives, board members, funders, frontline managers, community partners, and participants often rely on these conclusions to make real decisions about strategy, budgets, staffing, partnerships, and future investments. If the findings are overly technical, buried in jargon, or presented without context, even strong evidence may be ignored, misunderstood, or mistrusted.
Clear communication also supports credibility. Non-technical audiences do not need every statistical detail, but they do need to know that the conclusions are grounded in sound methods and honest interpretation. When evaluators explain what was studied, what was found, what the evidence means, and what limitations should be kept in mind, stakeholders are more likely to trust the process. Good communication builds alignment between data and decision-making, turning evaluation from a reporting exercise into a practical tool for learning, accountability, and improvement.
What makes evaluation findings difficult for non-technical audiences to understand?
Evaluation findings can be hard for non-technical audiences to interpret when they are presented in the language of researchers rather than the language of decision-makers. Terms such as validity, significance, comparison groups, effect sizes, implementation fidelity, and confidence intervals may be familiar to evaluators but not to stakeholders whose expertise lies in operations, governance, funding, or service delivery. Even when the analysis is excellent, too much technical terminology can create distance and confusion, leaving audiences unsure about what the findings actually say and why they matter.
Another common challenge is lack of focus. Stakeholders usually want to know a few practical things: what happened, why it happened, how confident they should be, and what should happen next. When presentations include too many metrics, too many charts, or lengthy methodological detail without a clear takeaway, the main message gets lost. Findings can also become difficult to understand when they are not tied to the audience’s priorities. A funder may care about outcomes and return on investment, while a frontline manager may care more about delivery barriers and implementation quality. Effective communication requires translating evidence into relevance, not simply simplifying it.
How can evaluators explain complex findings without oversimplifying the evidence?
The best approach is to simplify the language, not the thinking. Evaluators should preserve the accuracy of the evidence while presenting it in a structure that is easier to follow. Start with the headline finding in plain language, then briefly explain the supporting evidence, and finally describe what it means in practice. For example, instead of leading with a technical explanation of the analytic model, begin by stating that participation increased among a target group, outcomes improved in specific areas, or implementation varied across sites. Once the audience understands the core point, additional detail can be layered in as needed.
It is also important to communicate uncertainty honestly. Clear communication is not the same as making findings sound more certain than they are. Stakeholders should hear where the evidence is strong, where results are mixed, and where limitations affect interpretation. Useful phrases might include “the evidence suggests,” “the data indicate,” or “results were stronger in some locations than others.” Visuals, comparisons, and concrete examples can help make findings more accessible, especially when numbers alone feel abstract. In short, effective evaluators translate complexity into clarity while maintaining nuance, transparency, and professional integrity.
What should be included when presenting findings to executives, funders, or board members?
When presenting to senior stakeholders, the communication should be concise in structure but rich in meaning. Most high-level audiences want to understand the purpose of the evaluation, the most important findings, the implications for the organization or program, and any recommended next steps. A strong presentation usually includes a short reminder of the evaluation questions, a summary of the methods in non-technical language, the key findings prioritized by importance, and a clear explanation of what those findings mean for decisions. This allows leaders to quickly connect evidence to action.
Context matters just as much as conclusions. Executives and boards often need to know whether the program is achieving intended outcomes, where performance is strongest or weakest, what factors may be influencing results, and whether changes are warranted. Funders may also want to understand efficiency, reach, equity, and sustainability. It is helpful to include limitations so the audience understands what the findings can and cannot support, but these limitations should be framed constructively rather than defensively. The most effective presentations end with practical implications: what should be maintained, improved, tested further, or reconsidered based on the evidence.
What are the best practices for making evaluation findings useful and actionable for non-technical stakeholders?
Actionable communication begins with audience awareness. Evaluators should tailor the message to the stakeholder group, their level of familiarity with the program, and the decisions they need to make. This means choosing the right level of detail, organizing findings around real priorities, and using plain language throughout. A useful report or presentation often answers five core questions: What did we examine? What did we find? Why does it matter? How strong is the evidence? What should happen next? When those questions are answered clearly, stakeholders are much more likely to use the findings.
Other best practices include highlighting a small number of core messages, using straightforward visuals, defining key terms, and connecting evidence to specific recommendations. It is also valuable to distinguish between immediate actions and longer-term considerations. For example, findings may suggest quick improvements in program delivery while also raising broader strategic questions about scale, resources, or target populations. Whenever possible, recommendations should be realistic, prioritized, and linked directly to the evidence presented. Finally, evaluators should invite discussion. Communication is most effective when it is not a one-way transfer of information but a conversation that helps stakeholders interpret findings, ask questions, and decide how to respond.
