From Data to Insights — Analytical Storytelling
The Gap Between Findings and Insights
Most analysts can produce a correct analysis. Far fewer can produce an analysis whose findings actually change what a business does. The gap between "technically correct" and "actionable" is a communication problem, and it is solved by the same rigour that good analysts apply to their code: structured frameworks, explicit reasoning, and ruthless editing.
This lesson covers the analytical communication skills that determine whether your work ends up in a decision or in a drawer.
Findings vs Insights: The Distinction
A finding is an observation from data. An insight is a finding that has been extended with interpretation, implication, and a recommended action.
Finding: Revenue declined 18% in Q3 2023.
Insight: Revenue declined 18% in Q3 2023, driven entirely by a 34% churn increase in the SMB segment following the July price increase. Enterprise and Consumer segments were unaffected. This indicates price sensitivity is concentrated in SMB accounts, and a targeted retention offer for at-risk SMB customers could recover an estimated $240,000 in at-risk ARR before year-end.
The insight answers three questions the finding does not:
- Why? (Price-sensitive SMB cohort)
- How big is it really? (Enterprise unaffected — it's not systemic)
- What should we do? (Retention offer with an estimated value)
The Pyramid Principle
The Pyramid Principle (Barbara Minto, McKinsey) is the single most useful communication framework for analytical work. The core rule: lead with your conclusion, then provide the evidence. Never bury the answer.
Most analysts do the opposite: they present the methodology, then the data, then the findings, then — at the end — the recommendation. By then, the executive has stopped reading.
The SCR Framework
Situation → Complication → Resolution. This three-part structure works for any analytical narrative, from a single finding to a full board presentation.
Writing Precise Insight Statements
Precision is the most important attribute of analytical writing. Vague statements signal unclear thinking. Every insight statement should contain:
- The specific metric
- The magnitude (number, percentage, absolute value)
- The comparison baseline (vs prior period, vs benchmark, vs another group)
- The time period
- The population (who / what is affected)
Prioritising Insights: Impact vs Confidence Matrix
Not all insights are equal. Prioritise by two axes: analytical confidence (how certain are you?) and business impact (how large is the effect if true?).
Common Analyst Mistakes
Building the Findings Document
Generating a Python Insights Report
Key Takeaways
- A finding is an observation. An insight is a finding extended with interpretation, implication, and a recommended action. The difference is whether someone reading your memo knows what to do next.
- The Pyramid Principle: lead with your conclusion. Executives should understand the most important point from your first sentence. Evidence and methodology follow, for those who want validation.
- The SCR framework — Situation, Complication, Resolution — structures any analytical narrative in three moves that any audience can follow, from engineer to CEO.
- Every insight statement should contain five elements: the specific metric, the magnitude, the comparison baseline, the time period, and the population affected. Missing any of these weakens the analytical claim.
- Prioritise insights on two axes: confidence (how strong is the evidence?) and impact (how large is the effect if acted on?). High confidence + high impact = act now. High impact + low confidence = validate first.
- Common mistakes to eliminate: burying the lede, false precision, cherry-picking favourable metrics, confusing correlation with causation, reporting p-values without effect size, and ignoring null results.
- The findings document — executive summary, structured insights, methodology, limitations, appendix — is the professional deliverable. The notebook is the working document. Know the difference and write the memo as if the notebook does not exist.