The Winning 30-Minute Case Competition Strategy (Minute-by-Minute Breakdown)

You get 30 minutes. The clock starts. Your team of three looks at each other.

And then — almost every team makes the same mistake.

They spend the first 10 minutes debating what the problem actually is. Then they panic, rush the framework, skip the quantification, and present a recommendation they haven’t fully pressure-tested.

The teams that win case competitions — at IIM Bangalore’s Konsult, IIM Kozhikode’s Emerging Markets, or the national finals of HUL LIME — don’t wing it. They have a repeatable time allocation system they’ve practiced until it’s instinct.

Here it is.

The Classic Mistake: Over-investing in Problem Definition

The biggest time-waster in a 30-minute case is the first 5 minutes.

Most teams treat problem definition as a discussion. It becomes a debate. Everyone has a slightly different mental model of what’s being asked. By minute 8, you’ve burned through your buffer and haven’t put pen to paper.

Here’s the fix: problem definition is not a discussion — it’s a structured clarification process with a single output.

Your team lead reads the case prompt aloud once. Each person writes down: (1) what is being asked, (2) what success looks like, (3) one key assumption. Then you spend 90 seconds aligning. Done.

The Minute-by-Minute Playbook

0:00–5:00 — Intake and Orientation

What to do:

• Read the case prompt carefully (everyone individually)
• Note the key ask: Are you being asked for a strategy? A recommendation? A go/no-go decision?
• Identify: What data is given? What data is missing?
• Write the problem statement as one sentence

Output: One agreed-upon problem statement + list of what you know vs. what you need to figure out

Warning: Do NOT start building a framework yet. You’ll anchor too early.

5:00–12:00 — Build Your Issue Tree

What to do:

• One person drives, others contribute
• Build a MECE (Mutually Exclusive, Collectively Exhaustive) issue tree
• Identify the 2–3 most likely hypotheses given available data
• Assign branches to team members: “You own the revenue side, I’ll take cost structure”

Output: A clear issue tree on paper with 2–3 prioritized branches

“Your issue tree is your team’s shared mental model. If it’s not on paper and agreed upon by minute 12, you will present three different arguments at the end.” — Common advice from IIM Ahmedabad case prep seniors

12:00–18:00 — Apply Your Framework

What to do:

• Each person digs into their assigned branch
• Apply relevant frameworks — but fit the framework to the problem, not the problem to the framework
• Identify the 1–2 key insights per branch: What does the data tell you? What’s surprising?

Output: 2–3 structured sub-analyses, each with a “so what” conclusion

Frameworks to have ready:

• Revenue decline: Revenue = Volume × Price
• Market entry: Market attractiveness + Company capability
• FMCG: 4P (Product, Price, Place, Promotion) + STP
• Operations: Input → Process → Output

18:00–22:00 — Quantify Your Recommendation

This is the most skipped step. Don’t skip it.

What to do:

• Put numbers on your recommendation: market size, investment required, revenue uplift, payback period
• Even rough estimates with logical backing beat zero numbers
• Use Fermi estimation: “If we capture 5% of a ₹2,000 crore category, that’s ₹100 crore revenue…”
• Sanity check: Does the math make business sense?

Output: 2–3 key numbers that support your recommendation

22:00–27:00 — Crystallize Your Recommendation

What to do:

• One team member writes the final recommendation using SCR structure: Situation → Complication → Resolution
• One clear primary recommendation + 2 supporting pillars
• Define what “success” looks like in 90 days and 12 months

Output: A crisp 3-sentence recommendation + 90-day execution plan

27:00–30:00 — Q&A Prep

Most teams collapse here because they think the work is done. It isn’t.

What to do:

• Go around the room: each person throws one hard question
• Pre-agree on your biggest assumption (and your defense for it)
• Identify the one number judges will probe — and know it cold

Output: 3 anticipated Q&A points with rehearsed answers

What to Do If You Fall Behind

Behind by minute 15 (still on issue tree): Drop one branch entirely. Pick the two highest-impact branches and go deep on those. A focused 2-branch analysis beats a shallow 4-branch one every time.

Behind by minute 22 (haven’t quantified yet): Add one data point at the end of each recommendation: “We estimate this drives a 15–20% uplift in volume, based on comparable category launches.” Directional math is better than no math.

Behind by minute 28 (still refining recommendation): Stop refining. Go with what you have. A presented recommendation that’s 80% right beats a perfect one you never deliver.

How to Present With 2 Minutes of Prep

Sometimes the case is shorter — 15 or 20 minutes — or the format changes. Here’s the emergency version:

1. 30 seconds: Restate the problem in your own words
2. 60 seconds: Share your issue tree verbally (no slides)
3. 90 seconds: Lead with your recommendation, then explain your top 2 supporting reasons
4. 30 seconds: State your biggest assumption and one risk

That’s it. Clarity beats comprehensiveness when time is short.

A Template Your Team Can Use

Print this before your next practice round:

[0:00–5:00]   Problem statement: _______________________
[5:00–12:00]  Issue tree top nodes: ____________________
              Priority branches: ______________________
[12:00–18:00] Person A owns: __________________________
              Person B owns: __________________________
              Person C owns: __________________________
[18:00–22:00] Key number: ₹______ or _____%
[22:00–27:00] Recommendation (one sentence): ____________
              Pillar 1: _______, Pillar 2: _______, Pillar 3: _______
[27:00–30:00] Likely Q: ______, Our answer: _____________

Use this in every practice session until the structure is automatic.

Get Competition-Ready with CaseEdge

Time management in case competitions is a skill — and like all skills, it compounds with practice. CaseEdge gives you timed case prompts, guided issue tree builders, and structured recommendation templates so you can train your 30-minute clock instincts before competition day.

The teams that win aren’t smarter. They’ve just done it more times.