Session 23: Reporting & Stakeholder Communication

Block 4: Email Automation, Influencer Briefs, Analytics & Finalizing A2

View lecture slides: Session 23 Slides

1-Hour Lecture (Theory & Strategy)

  • Data ≠ insight ≠ decision. A dashboard export is data; your Session 22 memo is insight; a report tells a stakeholder what decision to make and why.
  • Reporting structure: headline result (one sentence), 2–3 supporting charts/numbers, one recommendation, one risk/caveat.
  • Read the full theory here: Data-Driven Decisions and the automation/reporting AI workflow: Analytics (AI Launchpad).
  • Avoid the two common failure modes: (1) a data dump with no recommendation, (2) a recommendation with no supporting evidence.
flowchart LR
    DATA[Dashboard Export: Data] --> INS[S22 Insight Memo: Insight]
    INS --> RPT[One-Page Stakeholder Report]
    RPT --> HL[Headline Result]
    RPT --> CH[2 Supporting Charts]
    RPT --> REC[One Recommendation]
    RPT --> CAV[One Risk/Caveat]
    REC --> S24[Feeds Session 24 Capstone]

Figure 1: From data to stakeholder decision

1-Hour Lab (Agency Execution)

  1. Convert your Session 22 insight memo into a one-page visual report: headline metric, 2 supporting charts/tables, one clear recommendation, one caveat.
  2. Present your report to a partner in 90 seconds — practice the “headline first” delivery style used in the Session 12 peer review and the eventual Session 24 capstone.
  3. Get one piece of feedback: was the recommendation clear within the first 30 seconds?
  4. Revise your report based on that feedback.

Deliverable: Stakeholder Report (feeds Session 24 capstone)

A polished one-page analytics report — ready to fold into your Block 4 capstone review package.