The Pyramid Principle (Minto)
Structure:
Start with the conclusion, then support with arguments.
Answer (Top)
├─ Supporting Argument 1
│ ├─ Evidence A
│ └─ Evidence B
├─ Supporting Argument 2
│ ├─ Evidence C
│ └─ Evidence D
└─ Supporting Argument 3
├─ Evidence E
└─ Evidence F
Example:
Top (Conclusion First):
"We should launch a mobile app by Q3 to capture 25% of lost mobile web traffic, generating ₹18L additional revenue annually."
Supporting Arguments:
- Market Opportunity: 60% of traffic is mobile, but mobile web conversion is 50% lower than desktop
- Competitor Analysis: Top 3 competitors have apps with 4.5+ ratings and 2× mobile engagement
- Financial Case: ₹12L development cost vs ₹18L annual revenue = 18-month payback
Key Principle: Busy executives read top → decide → ask for details if interested. Lead with conclusion, not data journey.
Situation-Complication-Resolution (SCR)
The 3-Part Story:
1. Situation: Establish baseline/context 2. Complication: Introduce the problem 3. Resolution: Propose solution with data
Example:
Situation:
"Our e-commerce platform has maintained 3% conversion rate for the past 2 years, processing ₹50 crore annually."
Complication:
"In Q4, conversion dropped to 2.1% (30% decline). Analysis shows mobile checkout abandonment increased from 40% → 65% after our October site redesign. This costs us ₹1.5 crore in lost quarterly revenue."
Resolution:
"Root cause: New mobile checkout requires 8 form fields vs previous 4. A/B test with simplified 4-field checkout shows 2.8% conversion (33% recovery). Recommendation: Rollback mobile checkout to previous version immediately, recover ₹1.2 crore/quarter."
Why it works: Natural story progression. Audience understands problem before solution (unlike Pyramid which leads with answer).
⚠️ CheckpointQuiz error: Missing or invalid options array
SCQA Framework (McKinsey)
The 4-Part Structure:
Situation: What's the context? Complication: What's the problem? Question: What does this make you wonder? Answer: Here's the solution (backed by data)
Example:
Situation:
"Our subscription product has 10K active users paying ₹500/month (₹5 crore ARR)."
Complication:
"Monthly churn increased from 5% → 9% in last quarter. At current rate, we'll lose 30% of users annually."
Question:
"Why are customers churning, and how can we reduce it to <5%?"
Answer:
"Analysis of 2,000 churned users shows: 70% cited 'lack of new features' in exit survey. Power users (who stay) use average 3 features daily vs churned users who used 1.2 features.
Recommendation: Launch feature adoption campaign pushing users to try 3+ features in first month. Pilot shows 55% feature adoption increase → churn reduced from 9% → 4.5%. Expected annual impact: Retain 4% more users = ₹2 crore saved."
Why it works: The "Question" frame engages audience intellectually before you answer. Creates curiosity.
Choosing the Right Framework
Framework Selection Guide:
| Framework | Best For | Example Use Case | |-----------|----------|------------------| | Pyramid Principle | Executive presentations, crisp recommendations | "Should we launch product X? Yes — here's why (3 reasons)" | | SCR | Complex problems needing context | "Q4 conversion drop — what happened and how to fix" | | SCQA | Strategic analysis, consulting-style | "Market entry decision — analyze opportunity and recommend" | | Simple 3-Act | General storytelling, team updates | "User growth analysis and action plan" |
Combining Frameworks:
Email to CEO (Pyramid):
Subject: Mobile app launch recommendation — ₹18L annual revenue opportunity
Recommendation: Launch mobile app by Q3 2026.
Why:
- 60% traffic is mobile; mobile web converts 50% worse than desktop
- Top competitors have apps with 2× engagement
- ₹12L development → ₹18L annual revenue (18-month payback)
Next steps: Approve ₹12L budget, start development April 1.
Detailed presentation (SCQA):
Slide 1 - Situation: Our traffic is 60% mobile Slide 2 - Complication: But mobile conversion is 1.5% vs desktop 3% Slide 3 - Question: How can we close this mobile conversion gap? Slide 4 - Answer: Native mobile app (competitor analysis shows 2× lift) Slides 5-10: Financial model, timeline, risks, recommendation
Practical Application Tips
Do's:
✅ Lead with headlines: "Sales dropped 15% due to competitor promo" (not "Sales analysis") ✅ Use action verbs: "Launch referral program" (not "Consider referral program") ✅ Quantify impact: "₹2.5 crore revenue increase" (not "significant improvement") ✅ One message per slide: Each slide has clear takeaway ✅ Use visuals to support story: Charts reinforce narrative, not replace it
Don'ts:
❌ Data dump: Showing every analysis you did (keep in appendix) ❌ Burying the lede: Saving conclusion for last slide ❌ Passive language: "It was found that..." (say "Analysis shows...") ❌ No recommendation: Presenting problem without solution ❌ Jargon overload: "Heteroscedasticity in residuals" (say "Model fit is good")
Template for Quick Presentations:
1-Slide Executive Summary (Pyramid):
Headline: [Recommendation in 1 sentence]
Why:
• Reason 1 [with metric]
• Reason 2 [with metric]
• Reason 3 [with metric]
Expected Impact: [₹ revenue or % improvement]
Next Steps: [Who does what by when]
⚠️ FinalQuiz error: Missing or invalid questions array
⚠️ SummarySection error: Missing or invalid items array
Received: {"hasItems":false,"isArray":false}