Learning Objectives

• Translate data insights to business language
• Create executive presentations
• Manage stakeholder expectations

1. Executive Summary (1 min): Problem, approach, key insight, recommendation
2. Context & Problem (2 min): Why this matters, business impact
3. Data & Methodology (2 min): What data, how analyzed (high-level)
4. Key Findings (3 min): Top 3-5 insights with visualizations
5. Recommendations (2 min): What to do, expected impact, next steps
6. Q&A (2 min)

Q1: How to explain technical concepts to non-technical stakeholders?

Use analogies, focus on business impact not methodology, visualize insights, avoid jargon, lead with conclusions. Instead of "p-value < 0.05", say "we're 95% confident this difference is real." Q2: How to handle stakeholder pushback?

Listen first, understand their perspective, show data evidence, acknowledge limitations, offer alternatives, find common ground on objective criteria. Q3: What makes a good data story?

Clear narrative arc, data-driven insights, visual evidence, relatable characters (customers), emotional connection, call to action. Q4: How to communicate uncertainty?

Use ranges ("estimated impact: $1-2M"), confidence intervals, scenario analysis ("best case: X, worst case: Y, expected: Z"). Be honest about limitations. Q5: What to include in executive summary?

Problem (one sentence), Approach (one sentence), Key finding (bullet), Recommendation (bullet), Expected impact (one metric). Maximum 5 bullets. Q6: How to structure recommendation?

What to do (specific action), Why (evidence), Expected impact (metric), Resources needed (cost/time), Risk/considerations. Q7: Stakeholder communication plan:

markdown
| Stakeholder | Interest | Communication | Frequency |
|-------------|----------|--------------|-----------|
| Executive sponsor | ROI, timeline | Dashboard, summary email | Weekly |
| Business users | Features, usability | Demo, feedback session | Bi-weekly |
| Data team | Technical details | Standup, code review | Daily |
| IT/DevOps | Infrastructure | Deployment plan | As needed |