EC-101 · Module 2

The 'So What' Layer

3 min read

Every data point in an executive communication needs a 'so what.' Not because executives cannot draw their own conclusions, but because the 'so what' you intend is not always the 'so what' they derive. An executive who draws the wrong conclusion from your data is not misreading you — you gave them data when you should have given them insight. The insight is the 'so what.' It is not optional. It is the communication.

The 'so what' has a formula: [finding] means [implication], therefore [action]. 'Processing time in the pilot was reduced by 34%' is a finding. 'Processing time in the pilot was reduced by 34%, which means the full deployment would eliminate the current backlog within 90 days, therefore the Q2 launch timeline is achievable' is a 'so what.' The difference is the complete reasoning chain — from what happened to what it means to what to do about it.

Do This

  • "Pilot processing time dropped 34%, eliminating the backlog within 90 days at full deployment" — finding plus implication
  • Write slide headlines as the 'so what', not as a label for the data below
  • State the action that follows from every major finding
  • Use call-out boxes or bold text to make the insight visually distinct from the supporting data

Avoid This

  • Present a chart labeled "Processing Time Comparison" without labeling the conclusion
  • Trust the executive to connect the data to the recommendation on their own
  • Use the slide headline to describe the data ("Q4 Volume Analysis") instead of the insight
  • Put the 'so what' in the speaker notes where the pre-reader will never see it