Narrative Structure for Insights

The Communication Gap in Data Work

Most analysts can produce accurate analysis. Far fewer can make that analysis drive a decision. The gap between those two skills is narrative structure. Without structure, even rigorous work gets ignored because the audience cannot extract the signal from the noise.

Executives do not consume analysis the way analysts produce it. Analysts think in process order: question, data, method, result, implication. Executives think in decision order: what changed, what does it mean, what should we do. When you present in process order, you force the audience to do the translation work themselves. Most will not. They will nod, say "interesting," and move on.

The Cost of Unstructured Findings

Consider two presentations of the same churn analysis. The first walks through the SQL query, the data cleaning steps, the statistical test, and finally mentions that churn increased 12% in Q3. The second opens with "Churn increased 12% in Q3, concentrated in accounts that onboarded after the pricing change. Here is what we recommend." The second version takes 3 minutes. The first takes 20. The second drives a decision. The first drives a meeting to schedule another meeting.

The difference is not the quality of the analysis. Both used the same data and methods. The difference is that the second analyst understood the audience's cognitive load and structured the information to minimize it.

What Narrative Structure Buys You

A clear narrative structure does three things simultaneously. First, it respects the audience's time by front-loading the conclusion. Second, it creates a logical chain that makes the conclusion feel inevitable rather than asserted. Third, it provides a repeatable framework you can apply to any analysis, reducing the cognitive overhead of figuring out how to present each new finding.

The situation-complication-resolution (SCR) framework is the most reliable structure for executive communication because it mirrors how people naturally process decisions. You establish the context, introduce the tension that demands action, and resolve it with a recommendation. Every executive briefing you give for the rest of your career can use this skeleton.

Situation: Establish Shared Context

The situation is the baseline. It answers the question "what does the audience already need to know to understand why this matters?" A good situation is one to three sentences of context that orient the listener without lecturing them.

For example: "Our subscription business has grown 15% year-over-year, with retention stable at 92%." That is a situation. It establishes the domain (subscription business), the trend (growth), and the current state (stable retention). The audience now has a reference point.

The situation must be factual and uncontroversial. If you open with a claim the audience disputes, you lose them before you reach the complication. Use metrics the audience already trusts. Reference time periods they care about. Avoid jargon that requires translation.

Complication: Introduce the Tension

The complication is the reason the audience cannot ignore the analysis. It is the gap between where things are and where they should be, or the change that demands a response. Without a complication, there is no story, just a status report.

"In Q3, churn among accounts acquired after the June pricing change reached 18%, compared to 8% for the existing base." That is a complication. It introduces a specific, measurable tension. The audience now understands that something has changed and that the change matters.

The complication should be specific enough to be actionable. "Revenue is down" is not a complication; it is a complaint. "Revenue from the enterprise segment declined 11% after the competitor's price cut in August" is a complication. It identifies the segment, the magnitude, the timing, and a potential cause.

Resolution: Deliver the Recommendation

The resolution is what you want the audience to do. It should be a clear, actionable recommendation supported by the evidence you presented in the complication. The resolution closes the loop the complication opened.

"We recommend grandfathering existing enterprise accounts at the current rate for 12 months and introducing a tiered pricing model for new accounts. This projects to a 4-point reduction in enterprise churn by Q2." That is a resolution. It states the action, the rationale, and the expected outcome.

The resolution must be proportional to the evidence. If your analysis identifies a correlation, recommend further investigation or a small experiment, not a company-wide policy change. Overreaching destroys credibility faster than underreaching.

The Executive Attention Budget

Executives operate under severe time constraints. A VP might give you 10 minutes. A C-suite executive might give you 3. Your narrative must be compressible without losing its logical spine. This means every sentence must earn its place.

The SCR framework helps because it is inherently hierarchical. If you have 3 minutes, you deliver one sentence per section: situation, complication, resolution. If you have 10 minutes, you add evidence under each section. If you have 30 minutes, you add methodology and appendix material. The structure scales because the logic is the same at every depth.

What to Cut and What to Keep

When compressing for executives, cut in this order: methodology first, then data caveats, then secondary findings. Executives rarely need to know you used a Welch t-test or that you excluded outliers. They need to know the finding is trustworthy, which you establish through confidence intervals and sample sizes, not through methodological detail.

Keep the decision-relevant numbers. If the recommendation is to increase marketing spend in the Southeast region, the executive needs to know the projected ROI, the required budget, and the timeline. They do not need to know the R-squared of your regression model.

The Pyramid Principle in Practice

Barbara Minto's pyramid principle, developed at McKinsey, formalizes this approach: start with the answer, then group supporting arguments logically, then provide the data. The SCR framework is a specific instance of the pyramid principle tuned for analytical work.

In practice, this means your first slide or first paragraph is the resolution. Your second slide is the complication with the key evidence. Your third slide is the situation and context. Everything after that is supporting detail the audience can request if they want to go deeper.

This inverted structure feels counterintuitive to analysts who are trained to build up to a conclusion. Resist the urge. The audience's question is never "how did you get there." It is "what should I do." Answer that first.

Evidence as Narrative Support, Not Narrative Replacement

A common failure mode is presenting evidence without narrative. The analyst shows 15 charts and says "the data speaks for itself." It does not. Data requires interpretation, and interpretation is the analyst's job. The narrative provides the interpretation; the evidence provides the credibility.

Each claim in your narrative should be anchored to a specific piece of evidence. "Churn increased 12%" is a claim. "Churn increased 12%, from 8% to 9% monthly, based on 4,200 accounts" is a claim with evidence. The second version lets the audience assess the magnitude and the reliability simultaneously.

Handling Uncertainty Honestly

Executives respect analysts who communicate uncertainty clearly. If your analysis shows a correlation but cannot establish causation, say so. "Accounts that used feature X had 20% higher retention. This is correlational; we have not established that feature X causes retention. A controlled experiment would confirm causality."

This honesty does not weaken your recommendation. It strengthens it because it shows you understand the limits of your evidence. The recommendation can still be to invest in feature X, but framed as a bet with a defined risk rather than a certainty.

The Role of Visuals in Narrative

Visuals should reinforce the narrative, not replace it. Each visual should make one point that supports one beat of the SCR structure. If a chart does not clearly support the situation, complication, or resolution, it does not belong in the executive presentation.

Label charts with the takeaway, not just the data. "Monthly churn rate" is a data label. "Churn doubled after pricing change" is a takeaway label. The audience should be able to understand the point of each visual in under 5 seconds without reading the axis labels.