Stop 12 · Communication & Data StorytellingTopics · 8/8

Answering 'So What?' in Every Report

Part of the Data Analyst Roadmap

In short

The most dangerous question in any meeting is "So what?" If your report can't answer it, the work gets politely ignored, however good the analysis was.

The single question every finding should survive — if a stakeholder can't tell what to do differently after reading your report, the analysis hasn't actually finished its job.

The jaadu sits in an auto-rickshaw driver's seat, turning back with a curious shrug.

Think of it like this

The auto driver's question

You hop into an auto and say, "It's very hot today and traffic is bad." The driver turns around: "Theek hai, but where do you want to go?" Facts without a destination go nowhere. Your report needs a destination too.

Watch it happen

What, so what, now what

What
So what
Now what

1/3What: "40% of trial users never open the app after day one."

The big ideas

What you need to know

Ask it of every chart

Before a chart goes in, ask "so what?" If you can't answer in one line, cut the chart.

Translate to stakes

Express the impact in money, customers or time. That's what makes leaders lean in.

Always suggest a next step

Even "we need more data on X" is a next step. Leaving it blank leaves the reader stuck.

Name an owner

A recommendation with a team and a date attached is far more likely to happen.

How it works

A quick self-check before you hit send

  1. 1

    Read the top line

    Does it state a finding, not a topic?

  2. 2

    Find the stakes

    Can a reader see why it matters in money, users or time?

  3. 3

    Find the action

    Is there a clear recommendation with an owner?

  4. 4

    Cut the rest

    Remove any chart that doesn't support the finding or the action.

Save yourself the pain

Common mistakes

Oops

Ending with "Interesting trends in the data" and no recommendation.

Do this instead

End with what should change, who should do it and how you'll know it worked.

Oops

Recommending something huge and vague like "improve the product".

Do this instead

Recommend something small and testable, like "add a day-two reminder for trial users".

Your mission

The so-what drill

~15 min

Quick check

"Average session time rose from 4 to 6 minutes." What's the best "so what" to add?

Go deeper

  1. 1Go through a past report and ask 'so what' after every single finding.
  2. 2Practice ending every analysis with an explicit recommendation, even a tentative one.
  3. 3Learn to flag when the honest answer is 'we need more data' rather than forcing a false conclusion.

More topics at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge