Case method: analysing and presenting a business case

In short

The case method teaches management by putting a student in a decision-maker's chair: a written description of a real company situation is analysed, alternatives are evaluated against stated criteria, and one recommendation is defended with evidence. Developed at Harvard Business School from 1921 and used across IIMs, XLRI, FMS, SPJIMR and most AICTE-approved MBA/PGDM programmes, it is both a teaching device and an examination format - many university papers carry a compulsory 20-25 mark case, and almost every consulting, FMCG, banking and analytics recruiter runs a case round. It matters because real managerial problems arrive incomplete, ambiguous and with conflicting data, and the method trains structured judgement under exactly those conditions. Case competitions (Tata Crucible-style business quizzes aside, think HUL L.I.M.E., ITC Interrobang, Flipkart Wired, Mahindra War Room, Bain BOLD) are a recognised recruitment channel in India. The skill examined is not the "right answer" - it is the quality of the structure, the arithmetic and the defence.

Explained

What a case is, and the types

• A case is a factual or disguised account of a business situation at a point in time, written from the viewpoint of a protagonist who must decide something, with exhibits (financials, market data, org charts) and deliberately no stated conclusion.
• Decision case: protagonist must choose (enter a market, make-or-buy, price a launch). Most common in exams.
• Evaluation / appraisal case: judge a past decision or current performance ("was the acquisition value-accretive?").
• Problem-finding case: symptom given, cause hidden (falling margins, attrition spike) - the diagnosis *is* the task.
• Illustrative / descriptive case: demonstrates a concept or best practice; no decision demanded.
• Critical-incident / mini-case (caselet): 200-500 words, 5-10 marks, one issue; dominant in Indian university papers and written tests.
• Live case / field case: real client problem in a competition or consulting project, with primary data collection.
• Interview case: orally delivered, interviewer-led (consulting style) or candidate-led, 15-30 minutes, usually requiring a guesstimate or a profitability diagnosis.
• Classification by content: strategy, marketing, operations, finance, HR/OB, ethics, and increasingly analytics/digital cases.

How the method works, and its pedagogy

• Three-stage learning cycle: individual preparation → small-group discussion → plenary class discussion led by the instructor through questioning (Socratic method), not lecturing.
• Instructor's role: opening question ("What should Mehta do on Monday?"), board plan, probing for evidence, and a closing synthesis - the student generates the content.
• Learning outcomes examined: diagnosis under ambiguity, use of frameworks as tools not templates, quantitative support, trade-off reasoning, persuasion, and listening/building on others' arguments (class participation is commonly 20-40% of the course grade in Indian B-schools).
• Advantages: develops judgement, tolerance for incomplete data, communication; bridges theory and practice; exposes many industries quickly; produces no single "model answer", so it rewards reasoning.
• Limitations: hindsight and survivorship bias in published cases; a static snapshot of a dynamic situation; no real consequences; vocal students dominate; weak at teaching procedural skills (double-entry book-keeping, LPP simplex); cases age quickly and Western cases may mislead on Indian institutions, labour law, distribution and price points; grading is subjective.

Analysing a case - the standard eight steps

1. Skim - read the first and last paragraphs, the exhibit titles and the assignment questions; identify the protagonist, the decision, the deadline and the industry (5-10% of time).
2. Read closely and mark - facts versus opinions versus assumptions; note dates, units, currency and footnotes to exhibits (footnotes carry the trap).
3. State the problem in one sentence - "Should X do A or B by when, given constraint C?" A wrong problem statement invalidates everything after it; distinguish symptom (sales down 12%) from problem (distributor margin uncompetitive) from cause (trade scheme changed in Q2).
4. Situation analysis - external (PESTLE, five forces, market size and growth, competitor moves) and internal (value chain, resources and capabilities, financials, culture, organisation); SWOT only as a *summary* of this work, never as the analysis itself.
5. Quantitative analysis - ratios and trends, contribution and break-even, incremental cash flows, NPV/IRR/payback, capacity and utilisation, customer lifetime value, sensitivity on the two variables that matter most. State every assumption in a visible list.
6. Generate alternatives - at least three, mutually exclusive and genuinely feasible (status quo counts as one); avoid the false binary the case author plants.
7. Define criteria and evaluate - criteria drawn from the protagonist's objectives (profit, cash, share, risk, timeline, people, legal/ethical, strategic fit), weighted; score alternatives, and show the arithmetic.
8. Recommend, plan and hedge - one choice stated unambiguously, then a time-phased action plan (0-30 days / 1-6 months / 6-18 months) with owners, costs and metrics, the risks with mitigation, and the contingency trigger ("if trial share is below 4% by week 12, revert to...").

Structuring tools

• Issue tree / logic tree: break the question into sub-questions until each is answerable with data; the standard profitability tree is Profit = Revenue − Cost → Revenue = Volume × Price → Volume = Market size × Share.
• MECE (mutually exclusive, collectively exhaustive): branches must not overlap and must cover everything - the single most-marked criterion in consulting case rounds.
• Hypothesis-driven analysis: start with a plausible answer, then test the few facts that would disprove it - far faster than boiling the ocean; attributed to the consulting "answer-first" approach.
• 80/20 (Pareto): find the 20% of SKUs, branches, customers or defects causing 80% of the problem before anything else.
• Framework fit: five forces for industry attractiveness; value chain for cost and differentiation; 4P/7P and STP for marketing cases; 7S for change and alignment; BCG/GE matrix for portfolio; Ansoff for growth options; DuPont for return decomposition; Kraljic/make-buy for sourcing. Use at most two, and only if they produce an insight the case needs.
• Root-cause tools: 5 Whys, fishbone (Ishikawa) for operations/quality cases, FMEA where risk is central.
• Qualitative screens: stakeholder map, ethics check (legality, company code, Companies Act 2013 s.166 director duties and the CSR obligation under s.135, SEBI LODR disclosure duties for listed-company cases), and feasibility against the four Labour Codes in force from 21 November 2025 for HR/IR cases.

Writing and presenting a case analysis

• Written exam answer (20-25 marks, ~60-75 minutes): problem statement (1-2 lines) → key facts/assumptions → analysis under 2-4 headings with one table or calculation → alternatives with evaluation → recommendation → action plan and risks. Answer the *questions asked*; do not retell the case narrative - narration earns almost no marks.
• Formal report: title page, executive summary (the recommendation and the numbers behind it, on one page), situation analysis, alternatives, criteria and evaluation, recommendation, implementation plan, risks, appendices with all computations and exhibit rework.
• Slide deck (case competition / client): 8-12 slides, action titles (a full sentence stating the finding - "Distributor ROI of 11% is below the 18% category norm", not "Distributor Analysis"), one message per slide, Pyramid Principle order (answer → supporting arguments → data), ghost-deck the storyline before building any chart.
• Oral presentation discipline: state the recommendation in the first 30 seconds; signpost structure; keep numbers rounded and defensible; reserve one-third of the time for Q&A; answer the question asked, then give the reason.
• Interview case etiquette: repeat the question back, ask 2-3 clarifying questions (scope, timeframe, objective, geography), ask for a moment to structure, lay out the structure aloud, drive to the next analysis, do arithmetic out loud and sanity-check magnitudes, state assumptions, and close with a synthesis plus risks and next steps even if time is short.

Key points

• Case method - decision-centred teaching and testing using a factual account of a real situation with no stated answer.
• Protagonist - the person whose chair you sit in; every recommendation must be executable *by them*.
• Problem statement - one sentence naming decision, decision-maker, constraint and deadline; the highest-leverage line in the answer.
• Symptom vs problem vs cause - sales fall is a symptom; the cause is what analysis must reach.
• Situation analysis - external plus internal scan; SWOT is its summary, not its substitute.
• Issue tree - top-down breakdown of the question into independently answerable parts.
• MECE - no overlap, no gaps; the standard by which consulting structures are graded.
• Hypothesis-driven - answer first, then test the facts that could break it; saves most of the time.
• Alternatives - at least three feasible, mutually exclusive options including status quo.
• Criteria - derived from the protagonist's objectives, weighted, stated before scoring.
• Decision matrix - weighted scoring of alternatives against criteria; makes judgement auditable.
• Quantitative support - contribution, break-even, incremental NPV, payback, sensitivity; a case answer without numbers rarely scores well.
• Assumption list - every unavailable figure assumed openly with a basis; hidden assumptions are penalised.
• Action plan - time-phased, with owner, cost and metric for each step.
• Contingency and risk - what could go wrong, how it is detected, and the trigger for reversing.
• Action titles - slide headings that state the finding as a sentence; the deck should be readable from titles alone.
• Pyramid Principle - recommendation first, then grouped supporting arguments, then data (Barbara Minto).
• Hindsight bias - judging the protagonist with information they did not have on the case date; a classic exam error.

Formulas and examples

Example 1 - Break-even and margin of safety in a launch case. A Pune snack firm plans a new ₹20 pack: variable cost ₹13/pack, annual fixed cost (plant lease, ASP, team) ₹2.80 crore. Expected year-1 volume 6,00,000 packs per month.

• Contribution = 20 − 13 = ₹7 per pack; CM ratio = 7/20 = 35%.
• Break-even volume = 2,80,00,000 / 7 = 40,00,000 packs/year = 3,33,333 packs/month.
• Expected volume = 6,00,000 × 12 = 72,00,000 packs → sales = ₹14.40 crore; break-even sales = 40,00,000 × 20 = ₹8.00 crore.
• Margin of safety = (14.40 − 8.00)/14.40 = 44.4%.
• Profit = 72,00,000 × 7 − 2,80,00,000 = 5,04,00,000 − 2,80,00,000 = ₹2.24 crore.
• Sensitivity: if volume falls 25% to 54,00,000 packs, contribution = ₹3.78 crore, profit = ₹0.98 crore - still positive, so the launch survives a quarter of volume shortfall. Recommend launch, with the break-even run-rate (3.33 lakh packs/month) as the month-4 review trigger.

Example 2 - Guesstimate: annual market for school backpacks in India. State every assumption.

• School-going children (classes 1-12) ≈ 25 crore (close to the UDISE+ enrolment order of magnitude).
• Share who buy a bag rather than reuse ≈ 60% → 15 crore buyers/year.
• Average replacement cycle 2 years → but the 60% already captures annual buyers, so annual units = 15 crore.
• Price split: 70% unorganised at ₹300, 30% branded at ₹900 → weighted price = 0.7×300 + 0.3×900 = 210 + 270 = ₹480.
• Market = 15 crore × ₹480 = ₹7,200 crore; branded slice = 4.5 crore × ₹900 = ₹4,050 crore.
• Sanity check: ₹7,200 crore on 25 crore children is ₹288 per child per year - plausible for a category with heavy unorganised supply. Flag that the single most sensitive assumption is the 60% buy rate.

Example 3 - Make-or-buy with incremental cash flows. A Coimbatore pump maker buys a casting at ₹1,450/unit, 40,000 units a year. In-house: machine ₹6.0 crore, 6-year life, variable cost ₹1,020/unit, incremental fixed cost ₹1.10 crore/year, cost of capital 12%; ignore tax and salvage for the exam version.

• Saving per unit = 1,450 − 1,020 = ₹430 → annual gross saving = 40,000 × 430 = ₹1.72 crore.
• Net annual cash flow = 1.72 − 1.10 = ₹0.62 crore.
• Payback = 6.00 / 0.62 = 9.7 years against a 6-year life → do not invest.
• PV check: 6-year annuity factor at 12% = 4.1114 → PV = 0.62 × 4.1114 = ₹2.55 crore; NPV = 2.55 − 6.00 = −₹3.45 crore. Breakeven volume for zero NPV needs annual flow of 6.00/4.1114 = ₹1.459 crore, i.e. units = (1.459 + 1.10)×1,00,00,000/430 ≈ 59,500 units/year. Recommendation: continue buying; revisit if volume crosses ~60,000 units or if the supplier raises price above ₹1,685 (which lifts saving to ₹665/unit: 40,000 × 665 = ₹2.66 crore − 1.10 = ₹1.56 crore > ₹1.459 crore).

Example 4 - Weighted decision matrix. A diagnostics chain must choose a Tier-2 expansion route. Criteria and weights: 3-year NPV 0.35, speed to market 0.20, capital intensity 0.20, brand control 0.15, execution risk 0.10.

• Own labs = 0.35×8 + 0.20×4 + 0.20×3 + 0.15×9 + 0.10×7 = 2.80+0.80+0.60+1.35+0.70 = 6.25.
• Franchise = 2.10+1.80+1.80+0.60+0.60 = 6.90; Acquire = 2.45+1.60+0.80+0.90+0.40 = 6.15.
• Recommend franchising, with brand control (its weakest score) addressed by mandatory NABL accreditation, standard SOPs, mystery audits and a quality clause permitting termination.

Example 5 - Diagnosing a margin fall with DuPont. FY25: PAT ₹48 crore, sales ₹800 crore, assets ₹600 crore, equity ₹300 crore. FY26: PAT ₹44 crore, sales ₹1,000 crore, assets ₹880 crore, equity ₹400 crore.

• FY25: margin 6.0%, asset turnover 1.333, equity multiplier 2.0 → ROE = 0.06 × 1.333 × 2.0 = 16.0% (check: 48/300 = 16.0%).
• FY26: margin 4.4%, asset turnover 1.136, equity multiplier 2.2 → ROE = 0.044 × 1.136 × 2.2 = 11.0% (check: 44/400 = 11.0%).
• Reading: revenue grew 25% but margin fell 160 bps and asset turnover fell 0.20 - growth was bought with discounting and with assets not yet productive; leverage masked part of the fall. The analysis should next split the margin decline between gross margin and ASP spend, and the turnover fall between receivables, inventory and new capacity - that is the issue tree the case answer should follow.

Where it is used

• Consulting recruitment and work: McKinsey, BCG, Bain, Kearney, ZS, EY-Parthenon and Big Four strategy arms screen almost entirely on cases; the same structuring is the daily method on client engagements.
• FMCG and retail leadership programmes: HUL UFLP, ITC, Nestlé, Marico, Tata Consumer and Reliance Retail use business cases and live case competitions (HUL L.I.M.E., ITC Interrobang, Mahindra War Room) as hiring and promotion filters.
• Banking, PE/VC and credit: investment committee and credit memos follow the same shape - situation, options, numbers, recommendation, risks and covenants; equity research initiating-coverage notes are evaluation cases.
• University examinations: compulsory case sections in Strategic Management, Marketing Management, HRM and Business Policy papers under UGC CBCS/AICTE-model MBA and PGDM curricula; CAT/XAT/GMAT-adjacent written-analysis rounds; CA and CS final papers carry case-scenario MCQs and descriptive cases.
• Corporate roles: product managers writing one-page decision memos, business analysts building option-vs-option models, HR business partners making restructuring proposals that must stand against the Labour Codes.
• Public sector and policy: IIM/ASCI and administrative-training cases on municipal services, PSU turnarounds and scheme design, where stakeholder and feasibility analysis dominates the arithmetic.

Interview questions

• Q: Walk me through how you would analyse a case in 20 minutes. A: Clarify the objective and scope, state the problem in one line, lay out a MECE structure, pick the branch with the biggest impact, do the arithmetic aloud with stated assumptions, and close with a recommendation, risks and next steps.
• Q: What is the difference between a symptom, a problem and a root cause? A: A symptom is the observable deterioration (sales down 12%); the problem is the managerial gap behind it (distributor ROI below category norms); the root cause is the specific change that created it (a trade scheme revision in Q2).
• Q: What does MECE mean and why do interviewers care? A: Branches of your structure must not overlap and must cover the whole problem; it shows you will neither double-count nor miss the driver that matters.
• Q: A case gives you no financial exhibits. How do you quantify anything? A: Build a guesstimate from a visible population down through penetration, frequency and price, state every assumption, and sanity-check the result per capita or against a known benchmark.
• Q: Why should a case answer always include the status quo as an alternative? A: It establishes the baseline against which incremental cash flows and risks are measured, and it prevents recommending action where inaction is cheaper.
• Q: How many frameworks should you use in one case? A: At most two, and only where each yields an insight the recommendation needs - a framework applied without a conclusion earns nothing.
• Q: What is hindsight bias in case analysis? A: Judging the protagonist using information that appeared after the case date; the answer must be defensible with what was known on that date.
• Q: Your recommendation and the numbers point in opposite directions. What do you do? A: Say so explicitly, identify which assumption drives the gap, run sensitivity on it, and choose on the stated criteria while naming the condition that would reverse the choice.
• Q: What makes a slide title good in a case deck? A: It is an action title - a full-sentence finding with the number in it - so that reading only the titles gives the whole argument.
• Q: How would you handle a case where the ethical and the profitable option differ? A: Treat legality and the company's code as screening criteria, not weighted ones, and discard options that fail them; for an Indian listed company also check Companies Act 2013 director duties and SEBI LODR disclosure obligations before costing the choice.
• Q: What are the main limitations of the case method? A: Static snapshots, hindsight and survivorship bias, no real consequences, subjective grading, and poor fit for teaching procedural skills.
• Q: How do you structure a profitability-decline case? A: Profit = revenue − cost; split revenue into volume × price (and volume into market size × share) and cost into fixed and variable, then test which branch moved using the exhibits, by segment and by period.

Common mistakes

• Retelling the case narrative instead of answering the question asked - summary earns almost no marks in Indian university papers.
• Naming the wrong problem (treating the symptom), which makes every later step irrelevant however good the arithmetic.
• Listing SWOT or five forces with no conclusion, or forcing a framework the case does not need.
• Giving only two alternatives because the case author framed a binary, and omitting the status quo.
• Recommending without numbers - no contribution, break-even, NPV or sensitivity - or showing numbers with hidden assumptions.
• Stopping at the recommendation: no owner, no timeline, no cost, no metric, no contingency trigger.
• Arithmetic and unit slips - mixing lakh with crore, monthly with annual figures, ignoring exhibit footnotes, or quoting a market size that fails a per-capita sanity check.
• Hedging ("management should consider various options") instead of committing to one defended choice.

Related topics

Business strategy: SWOT, PESTLE and Porter's five forces · Management consulting: problem solving and the consultant's role · Business research methods · Corporate strategy: growth, M&A and diversification · Strategy execution: balanced scorecard, OKRs and KPIs · Business ethics and CSR