No new frameworks here — this module teaches the meta-skill: how to combine everything you've learned to crack open a real company and make a defensible recommendation. This is where 13 modules become one machine.
1The big idea
A case has no single right answer
A business case is a messy real situation with incomplete information. The goal isn't to find the answer — it's to build a logical, evidence-based argument for a clear course of action, and defend it. How you reason matters more than what you conclude.
Analyst's jobDiagnose the real problem → analyse with the right tools → recommend & justify a decision.
What's gradedStructured thinking, use of evidence, awareness of trade-offs & risks — not a "correct" verdict.
Memory hook 🧠Diagnosis before prescription. The most common failure is jumping to a solution before nailing the real problem. A doctor who prescribes before examining is dangerous — so is an analyst.
2★ How it all connects
The Master Map: your whole MBA on one diagram
Every framework you've learned isn't a separate tool — they form one chain. The outside shapes the inside; analysis feeds decision; decision needs financing & people to execute. Here's the flow:
Outside-in, then synthesize, then analyse through each function, then converge on one justified recommendation.
Memory hook 🧠Outside → Inside → Synthesize → Analyse → Decide. Always work from the environment inward; never start with "what should they do?" — start with "what's going on?"
3The repeatable recipe
The 6-Step Case Sequence
A reliable order that works for almost any case. Resist the urge to skip ahead — each step sets up the next.
1
Read & identify the problem
Skim, then read closely. State the central decision/problem in one sentence. Separate symptoms from root cause.
2
Scan external + internal
Industry attractiveness & trends, then the firm's resources & capabilities.
PESTEL · 5 Forces · Value Chain · VRIO
3
Synthesize into SWOT
Pull the scan together. The intersection of strengths & opportunities (and weaknesses & threats) frames the strategic options.
SWOT
4
Analyse through each function
Run the relevant marketing, operations & finance tools on the specific problem. Quantify wherever possible.
STP · CLV · bottleneck · ratios · NPV
5
Generate & evaluate options
Build 2–3 distinct options. Score each against criteria (cost, risk, fit, return). Avoid false either/or.
decision matrix · NPV comparison
6
Recommend & plan execution
Pick one, justify with the evidence, then address how to fund it, who executes it, the risks, and the metrics of success.
WACC · change mgmt · KPIs
4Knowing which tool to grab
The Toolbox — matched to the question
The skill is selecting the right tool for what the case is asking. A quick lookup by question type:
"Should they enter this market?"5 Forces (is it attractive?) + PESTEL + market sizing + NPV of entry.
"Why are profits falling?"Income statement waterfall + ratio trends + cost structure + competitive rivalry.
"Should they launch this product?"STP + 4Ps + break-even + CLV vs CAC + NPV.
"BrewCo, a regional coffee chain, has flat profits despite rising revenue. Should it expand to a new city?" Watch the tools chain together:
🔍 BrewCo — analysis in sequence
ProblemRoot cause, not symptom: revenue up but profit flat → a margin/cost problem, not a sales problem. Expansion may be the wrong fix.
5 ForcesNew city: low entry barriers + many substitutes → intense rivalry. Industry is only moderately attractive.
RatiosNet margin fell 12%→7% over 3 yrs while revenue grew. Confirms costs are outpacing sales — the real issue.
Break-evenA new store needs ~180 covers/day to break even; comparable areas average 140. Thin margin of safety.
NPVExpansion NPV is slightly positive but highly sensitive to footfall — fragile. Fixing existing-store margins has higher, safer NPV.
MarketingCLV:CAC at current stores is strong (4:1) — loyal base. The asset is the existing customers, not new geography.
The converged answerRecommendation: don't expand yet. The data points to a cost/margin problem, not a growth problem. Fix unit-level profitability first (higher-margin items, cost control), prove the model, then expand from strength. Same destination — better timing & lower risk.
Memory hook 🧠Notice: the obvious answer ("expand!") was wrong. Each tool added evidence that reframed the problem. That's the whole point — analysis beats intuition.
6Communicating the answer
Structuring the Recommendation
A brilliant analysis fails if it's not communicated clearly. Lead with the answer, then support it — the way executives actually want to receive it.
1
Recommendation first
Open with your decision in one clear sentence. Busy readers want the answer up front (the "executive summary" / BLUF — bottom line up front).
2
The 3 key reasons
Support it with your strongest 3 evidence-based arguments — ideally one strategic, one financial, one market/operational.
3
Risks & mitigation
Name the main risks and how you'd manage them. Showing you see the downside builds credibility.
4
Execution & metrics
Next steps, timeline, who's responsible, and the KPIs that prove it's working.
The Pyramid PrincipleStart with the conclusion, then group supporting arguments beneath it (Barbara Minto). The opposite of how you did the analysis (bottom-up) — but exactly how you should present it (top-down).
7What kills a case analysis
Common Pitfalls
Solution-firstRecommending before diagnosing. Always nail the real problem first.
Framework dumpRunning every tool to show off. Use only the tools the problem needs — depth over breadth.
Ignoring trade-offsPretending your option has no downside. Every choice has costs; name them.
No clear decisionWishy-washy "it depends." Commit to one recommendation and own it.
Tie it together 🧠The capstone is the proof that the MBA isn't 13 separate subjects — it's one integrated way of thinking: scan the world, diagnose with evidence, decide under uncertainty, and lead the execution. Next & final module: locking it all into long-term memory.
🎯 Active recall
Cover the answer, say it aloud, then tap to check. The big one: re-draw the master map (external → internal → synthesize → analyse → decide) from memory. Revisit today, +3 days, +1 week.
What is actually being assessed in a case — and what's the #1 mistake?
Structured, evidence-based reasoning (not a single "right" answer). The #1 mistake is solution-first: recommending before diagnosing the real problem. Diagnosis before prescription.
tap to reveal
★ State the master-map order of analysis.
External → Internal → Synthesize (SWOT) → Analyse by function (marketing/ops/finance) → Decide & execute. Work outside-in; start with "what's going on," not "what should they do."
tap to reveal
Which tools answer "is this industry attractive?"
Porter's Five Forces (plus PESTEL for the macro environment).
tap to reveal
Which tools answer "should we make this investment?"
NPV and IRR (discounted at WACC), plus sensitivity analysis to test how fragile the answer is.
tap to reveal
In the BrewCo case, why was "expand!" the wrong instinct?
Revenue was rising but profit was flat — that's a cost/margin problem, not a growth problem. The ratios and break-even confirmed it. Fix unit profitability first, then expand from strength.
tap to reveal
How should you structure a recommendation (and what's BLUF)?
Recommendation first (BLUF = bottom line up front), then 3 key reasons, then risks & mitigation, then execution & metrics. Present top-down even though you analysed bottom-up (Pyramid Principle).
tap to reveal
Name three case-analysis pitfalls.
Solution-first (no diagnosis), framework dump (using every tool to show off), no numbers (vague claims), ignoring trade-offs, and no clear decision ("it depends").
tap to reveal
Why does the capstone exist at all?
To prove the MBA is one integrated way of thinking, not 13 separate subjects: scan the environment, diagnose with evidence, decide under uncertainty, and lead the execution.
tap to reveal
Module 14 of your MBA · Capstone · Re-draw the master map from memory, then run it on a real company. 🎓