How to Present Data Analysis Results to Non-Technical Clients
The most rigorous analysis in the world fails if the decision-maker cannot act on it. Translating analytical findings into decisions is a distinct skill — and one that most data professionals are never explicitly taught.
The communication failure in data analysis
The most common failure in data consulting is not analytical error — it is communication failure. A statistically sound analysis presented in a way that a minister, director, or donor cannot interpret is a wasted investment. The analysis exists to change a decision. If it does not, it failed, regardless of its technical quality.
Non-technical clients are not unsophisticated. They are senior, time-constrained, and focused on decisions rather than methodology. They need to know what the data means for their situation — not how the analysis was conducted. These are fundamentally different questions, and answering the wrong one is the most common mistake analysts make in client presentations.
Eight principles for non-technical presentation
Lead with the answer
Start with the conclusion, not the methodology. "The programme increased school attendance by 18% among girls in target districts" is the first sentence. How you calculated it comes later, in an annex, for those who need it.
One insight per chart
Every chart should communicate exactly one finding. If a chart requires explanation to be understood, it has failed. The title of a chart should state the finding, not describe the data: "Girls' attendance rose fastest in districts with female teachers" not "Attendance by district and teacher gender."
Translate statistical language
A p-value means nothing to a programme director. "We are 95% confident this result was not due to chance" is imprecise but actionable. A confidence interval becomes "the true effect is most likely between 12% and 24%." Translate before you present — never during.
Use comparisons people can anchor
Absolute numbers are hard to interpret. "3,400 additional children enrolled" is clearer than "an increase of 18 percentage points." "Equivalent to filling 17 classrooms" is clearer still. Find the comparison that makes the number real to your specific audience.
Acknowledge uncertainty honestly but briefly
Decision-makers need to know when findings are solid and when they are indicative. A single sentence — "This finding is robust; the secondary finding on teacher retention is preliminary and should be confirmed in the next cycle" — is sufficient. Do not hide uncertainty; do not dwell on it.
Separate findings from recommendations
Findings are what the data shows. Recommendations are what you advise based on the findings plus your expert judgment. Conflating them undermines both. Present findings first, clearly labelled as such. Present recommendations separately, clearly labelled as your interpretation.
Prepare for the three questions
Non-technical clients almost always ask three things: Is this real or could it be chance? (Reliability) What should we do about it? (Action) How confident are you? (Credibility) Prepare direct, one-paragraph answers to each before the meeting.
Design for the decision, not the data
Before building any presentation, identify the specific decision the client needs to make. Every element of the presentation should serve that decision. Data that does not bear on the decision should be in the appendix.
Format guide by audience type
| Audience | Preferred format | Key considerations |
|---|---|---|
| Minister or senior official | 2-page brief + 10-slide deck max | Decision on slide 1. One number per slide. Pre-briefed by staff before the meeting. |
| Donor programme officer | Executive summary (3–4 pages) + full report | Results against logframe. Cost per outcome if available. Limitations acknowledged. |
| Board or steering committee | Dashboard + 15-minute verbal presentation | Trends over time. Comparison to targets. Traffic-light status. |
| Programme manager | Full report with detailed findings | Operational implications. District or group-level disaggregation. What to act on. |
| Media or public | Data story with three to five headline findings | Plain language. Compelling visual. One clear takeaway. |
The Claryon communication standard
Every Claryon deliverable is designed to the same communication standard: the executive can act on it in 10 minutes; the technical reviewer can validate it in full. This means every report ships with both a decision-oriented summary and a complete methodology annex. These are not compromises between rigour and accessibility — they are different documents for different readers, built from the same analytical foundation.
Analysis that gets acted on.
Claryon delivers research and data analysis in formats designed for the decisions they need to inform — not for analytical self-expression.