Brainstorming in a Case Interview: Insider Guide (2026)

Last Updated on April 22, 2026

Brainstorming is where I see many candidates lose their consulting offers. In moments where the interviewer asks question such as, “What are all the reasons this plant might be underperforming?” and the candidate starts rattling off disconnected ideas without structure.

That one moment decides a lot. After 5 years at McKinsey and 700+ candidates coached to offers at MBB, I can tell you exactly what separates a strong brainstorm from a generic one, and how to build the skill before your interview.

This guide covers the method.

Key Takeaways

• Brainstorming questions in consulting case interviews test structured creativity, interviewers grade breadth, depth, MECE discipline, and insight, not idea count.
• Use a 4-step approach: clarify the question, take 60-120 seconds to structure, present top-down with numbered buckets, then prioritize with a hypothesis.
• Mind mapping, linking, and expansion generate ideas; the Pyramid Principle (Barbara Minto) communicates them cleanly in pressure situations.
• The biggest failure mode is idea-dumping without hierarchy, the fix is a MECE top layer of 3-4 buckets before any detail.
• Practice with isolated drills, not more full cases. 5-10 brainstorming reps in a row builds idea-generation muscle faster than grinding cases end to end.

What Brainstorming Questions Actually Test

Every major firm uses brainstorming, McKinsey, BCG, Bain, the Big 4, Oliver Wyman, Kearney, LEK, in-house consultancies. It shows up mid-case, not at the start (in most cases). A typical opener sounds like:

• “What are all the reasons a coffee chain might be losing market share?”
• “What levers could this hospital pull to reduce patient wait times?”
• “Beyond price, what could differentiate our product in this category?”

Strong answers achieve four things at once:

1. Can you generate ideas under pressure without freezing or going blank?
2. Can you organize them into a MECE structure, Mutually Exclusive, Collectively Exhaustive, instead of spraying random thoughts?
3. Can you go broad at the top and deep with two or three layers of sub-ideas under each bucket?
4. Can you bring insight, a non-obvious angle that shows you’re thinking like a consultant, not a case-prep book?

If you only deliver one of those four, you get a pass. If you deliver all four, you stand out. Most candidates deliver one or two and wonder why their scorecard came back “structured but generic.”

Brainstorming vs. Framework Questions: The Distinction That Matters

Candidates mix these up all the time. Both test structured thinking. Both produce a MECE tree. But the mental mode is different, and so is the interviewer’s scorecard.

Framework questions come at the start of a case. The interviewer wants you to build an analytical scaffolding for the whole problem.

“Our client is a European scooter startup entering urban markets. What would you analyze to size the opportunity?”

You answer with categories of analysis: market demand, competitive dynamics, infrastructure constraints, regulation, unit economics. You’re scoping the investigation.

Brainstorming questions come later, often after the core analysis is underway. The interviewer wants specific ideas, not categories of inquiry.

“We’ve sized the market. Now, what creative marketing plays could this scooter startup use to launch in urban Europe?”

Here you answer with concrete ideas: student partnerships, geofenced app promotions, university launch tours, gamified referral programs, commuter subscriptions. You’re generating solutions.

Both question types sit on the same spectrum: investigative (what’s causing the problem?) and prescriptive (what should we do about it?). The difference are the altitude and framing. Frameworks stay at 30,000 feet and target areas to analyze. Brainstorming drops to 5,000 feet and looks into concrete ideas.

For a fuller treatment of scaffolding the case itself, see the case interview frameworks guide.

The 4 Qualities of a Great Brainstorming Answer

A winning brainstorm has four traits. Miss one and you lose points, even if the ideas are decent.

1. Breadth

Cover the problem from multiple angles and fully. If the question is “why are sales declining?”, a one-dimensional answer focuses only on customer behavior. A broad answer covers customer, product, competition, channel, and macro factors. Three to five top-level buckets is the right range, fewer looks thin, more looks unstructured.

2. Depth

Each top-level bucket needs at least two or three sub-ideas underneath it, and ideally concrete examples at a third layer. A bucket called “product issues” is not an answer. “Product issues → quality decline (higher defect rate in new batches) + feature gap (competitor launched X last quarter) + packaging confusion (shelf visibility down)” is an answer that could be included in a C-level discussion.

3. MECE Structure

Mutually Exclusive: no overlap between buckets. Collectively Exhaustive: nothing important is missing. If your buckets are “usability issues” and “product issues,” the product affects usability, so they overlap, that’s a MECE violation. Tighten it to “demand-side” (customer, market, macro) and “supply-side” (product, pricing, channel, internal operations).

4. Insight

This is what separates interview-winning brainstorms from textbook ones. Insight means also including the non-obvious angle: the structural shift competitors are missing, the second-order consequence of a trend, the counter-intuitive hypothesis. It’s where your industry knowledge and business judgment show up. Without it, your answer reads like a bystander. With it, you read like a consultant.

A quick contrast. The question: “What reasons would cause machines to break down at different intervals across locations?”

Weak answer: “Maintenance issues, operator issues, machine age, and environmental factors.” No depth, no insight, four buckets thrown out without connective tissue.

Strong answer: “I’d break this down into four buckets. First, location factors: weather and climate (humidity, temperature) as well as positioning and access (where the machine sits and how easily staff can interact with it). Second, usage factors: how the machine is used, including use patterns (frequency, duration), type of users (trained vs. untrained), and storage conditions when not in use. Third, build quality: differences in materials (quality, suppliers, specs) and the production process (technique, quality control, factory standards). Fourth, maintenance: maintenance intervals (preventive vs. reactive), technician qualification, and spare parts quality (OEM vs. aftermarket). If I had to prioritize, I would start with usage and maintenance. If identical machines perform differently across locations, build quality is less likely the driver. I would first analyze usage patterns, operator behavior, and maintenance logs by location to identify inconsistencies.”

Same topic. Radically different performance.

3 Techniques to Generate Ideas Fast

Before we get to the 4-step approach for delivering the answer, you need the techniques that feed it. These are the three idea-generation methods I teach in our structuring and brainstorming drills program, and the ones I used myself at McKinsey.

Top-Down vs. Bottom-Up

Every brainstorm uses one or both directions.

• Top-down: Start with broad buckets, then drill into specifics. Best when the problem is general and you need to impose structure. Example: “reasons for declining profit” → split cleanly into revenue and cost, then break each down.
• Bottom-up: Start with specific ideas, then cluster them into categories. Best when the problem is narrow and concrete ideas come to mind first. Example: “how to attract Gen Z customers” → TikTok partnerships, in-app challenges, campus ambassadors, sustainability messaging, then cluster these into digital, community, and brand narrative.

In real interviews, strong candidates move between both. They might hit a top-level structure first, then generate bottom-up ideas inside each bucket.

At the top level, you can apply the same first-principles thinking used in frameworks, for example by breaking the problem down into components or analyzing it from a process perspective. For a deeper dive, see our framework creation guide.

Technique 1: Mind Mapping

Start with the problem at the center. Branch outward to related concepts, then branch each of those.

Example, “Revive a legacy snack brand”:

• Branch 1: Product → reformulation (organic, gluten-free, high-protein), size variants (multi-pack, single-serve), new SKUs (savory line extension)
• Branch 2: Marketing → influencer partnerships (fitness, food creators), sampling at gyms and yoga studios, nostalgic brand storytelling
• Branch 3: Distribution → DTC with subscription box, partnerships with health-food retailers, placement in corporate pantries

Mind mapping is the fastest technique when you have nothing on the page and 90 seconds on the clock.

Technique 2: Linking

Take two ideas and connect them into a third. This is where interview-winning insight comes from.

Example: Link “eco-friendly packaging” with “community wellness” → launch a packaging return program where customers earn product credit for recycling, tied to a broader wellness-meets-sustainability brand story. The idea didn’t exist in isolation; it emerged from connecting two unrelated buckets.

As a consulting interviewer, I watched strong candidates consistently use linking in the prioritization step at the end of a brainstorm. They’d say, “these two ideas actually reinforce each other, I’d sequence them together.”

Technique 3: Expansion

Take one idea and drill down until you’ve extracted every dimension.

Example: Start with “referral program.” Expand into: tiered rewards (discount for referrer, free product for referee, escalating benefits after N referrals), social mechanics (shareable links, milestone badges, leaderboards), integration surfaces (checkout flow, post-purchase email, in-app notifications), and measurement (attribution logic, CAC by channel, lifetime value uplift).

Expansion is how you add depth to a bucket that looks shallow. It’s also how you answer the dreaded follow-up: “What else?”

Combining All Three

Take the prompt “Make cities more liveable.”

Mind map to identify branches, transport, housing, public space, air quality, safety. Link transport and air quality to arrive at electrified public fleets with real-time congestion pricing. Expand “public space” into parks, third places, walkable mixed-use districts, and community events. You now have a layered, integrated answer instead of a flat list.

The 4-Step Approach to Answering in the Interview

This is the method I’ve refined across thousands of coaching hours. It works for McKinsey, BCG, Bain, Big 4, and any firm that runs interviewer-led or candidate-led cases.

Step 1: Clarify the Question

Paraphrase the question back in one sentence. This confirms understanding, buys you a few seconds to settle, and signals structure.

“So you’d like me to brainstorm the reasons our client’s manufacturing plants show different breakdown rates, is that right?”

If the scope is ambiguous, ask one clarifying question. Don’t overdo it. Interviewers are grading judgment, and over-clarification reads as stalling.

Step 2: Request Thinking Time

Ask for 60-120 seconds. McKinsey interviews typically allow around 2 minutes for a structured brainstorm; candidate-led formats (BCG, Tier-2 firms) expect 60-90 seconds. Don’t skip this, candidates who dive in immediately almost always produce shallow, disorganized answers.

Use the time deliberately:

1. Sketch 3-4 top-level buckets using whatever technique fits
2. Add 2-3 sub-ideas under each (you might also work bottom-up or combine different content creation techniques)
3. Circle the bucket where you’ll start and note the order

If you finish early, use the extra seconds to check for MECE violations, add insight-level ideas, or interdependencies.

Step 3: Present Top-Down with Numbered Signposting

Start with the top layer. Numbered buckets. Clear signposting.

“I’ve structured my answer around three areas. First, machine-side factors. Second, operator-side factors. Third, environmental factors. Let me walk through each.”

Then explore bucket one, finish it, and explicitly signpost the transition: “Moving to the operator side…” This mirrors how consultants communicate in real client meetings, which is exactly what the interviewer is testing.

For a deeper treatment of hierarchical communication, see the case interview communication guide.

Step 4: Prioritize and Integrate with the Case

After the list, don’t stop. Close with a hypothesis-driven prioritization:

“If I had to prioritize, I’d start with the operator-side factors (the what). If the same machine performs differently across sites, hardware variation is less likely to be the driver (the why). I’d want to pull the training records and maintenance logs by location as the first investigation step (the how).”

This step is where most candidates drop points. They finish the list and fall silent, waiting for the interviewer to react. Strong candidates close the loop, connect the brainstorm to the broader case, and propose the next analytical move. That’s the signal of consulting judgment.

When the Interviewer Pushes Back

You might hear “what else?” or “what would you add?” at least once. This isn’t a trap. It’s an invitation. Integrate their feedback into your existing structure rather than scrapping it:

“Good point, that fits under the environmental bucket. I’d add it as a fourth sub-idea alongside humidity and power stability.”

Never abandon your structure at the first pushback. Never dig in if their input genuinely reveals a gap. Read the signal and adapt.

Communicating Your Answer: The Pyramid Principle

The Pyramid Principle, developed by Barbara Minto at McKinsey in the 1970s, is the communication backbone of every consulting presentation. It’s also the cleanest way to deliver a brainstorm under time pressure.

The shape:

• Top: your key message or synthesis (conclusion-first)
• Middle: the 3-4 supporting categories
• Base: evidence, examples, and sub-ideas under each category

Applying It to Brainstorming

Take the prompt “How could a retailer increase revenue?”

Top (synthesis): “I see three main levers, expanding the product line, optimizing pricing, and strengthening the online presence.”

Middle (sub-buckets for each):

• Expand product line → eco-friendly SKUs, local-artisan collaborations, private-label expansion
• Optimize pricing → dynamic pricing on slow-movers, premium tier introduction, bundling strategy
• Strengthen online presence → SEO-driven content, retargeting ads, loyalty app with personalized offers

Base (specifics under each): For “eco-friendly SKUs,” you might specify recycled materials, reduced packaging, and certified-supplier sourcing.

Then close with prioritization: “Given the retailer’s existing brand strength and under-use customer data, I’d sequence online presence first, it has the shortest time to impact.”

Why This Works Under Pressure

The Pyramid Principle forces you to lead with the answer, which is exactly what interviewers (and real clients) want. Burying the synthesis at the end is the most common communication mistake in case interviews. Lead with the conclusion, support it top-down, and let the listener follow the hierarchy without effort.

Practice this in everyday writing, emails, Slack messages, meeting updates. Top point first, supporting reasons second, details third. After a few weeks it becomes the default, and it shows up naturally in interviews.

How to Practice Brainstorming (What Actually Builds the Skill)

Most candidates practice brainstorming by doing more full cases. That’s the wrong move. Brainstorming is a discrete skill, and it builds faster with isolated reps than with end-to-end case grinding.

1. Do Isolated Drills, Not More Full Cases

Run 5-10 brainstorming prompts back to back. 90 seconds to structure, 2-3 minutes to deliver out loud. Conduct a thorough debrief of your answer and compare it to the sample answer and other angles. This builds idea-generation speed and structural discipline faster than any full case.

This is the core of our structuring and brainstorming drills program, a 7-hour video course and 100 targeted prompts, designed to build the exact muscle the interview tests.

2. Practice Under Time Pressure

Use a visible timer. 90 seconds. Hard stop. Forcing yourself to deliver under constraint is the closest simulation to real interview conditions. Without pressure, you’ll over-engineer structures that fall apart when adrenaline hits.

3. Use Real Business Problems

Pull a Financial Times headline or a Harvard Business Review case. “A regional bank is losing deposits to neobanks; what are the drivers?” Practice with these instead of recycled textbook prompts. Real problems build real business judgment, which is where the “insight” quality of a strong answer comes from.

Industry fluency is the multiplier. If you don’t know how airlines make money, or what drives retail gross margin, every brainstorm will feel like guesswork. Our case interview industry cheat sheets are designed to close that gap quickly.

4. Get Real Feedback

Practice partners catch 20-40% of your weaknesses. A trained coach catches 100%. Most candidates I work with in 1-on-1 coaching are surprised how shallow, non-insightful they brainstorm and how many MECE violations they’d been repeating for weeks without noticing. Their practice partners have the same blind spot.

If coaching or paid programs are not in your budget, record yourself. Watch it back the next day. You’ll spot issues your present-tense brain missed.

5. Optimize Note-Taking for Speed

You have about 60 seconds of writing time before you have to start speaking. Use shorthand:

• P = Profit, R = Revenue, C = Cost, Q = Quantity, $ = Price
• Arrows for causation (→), pluses for increases (+), minuses for decreases (−)
• Single-word labels per sub-bucket

You’re not writing an essay. You’re writing a scaffold you can talk from. Research on interview performance shows candidates typically complete 70-80% of their answer structure before speaking and develop the remaining 20-30% live during delivery. Get comfortable thinking while presenting.

6. Build an Error Log

After every practice session, write down what went wrong. Three recurring failure modes I see:

• Shallow buckets: top layer is fine, but sub-ideas are vague
• MECE violations: overlap between categories and ideas
• No prioritization close: ideas are solid but there’s no so-what

Track yours for 20 sessions. Patterns will emerge. Fix one at a time.

A note on memorization: candidates sometimes memorize “the three drivers of customer satisfaction” or “the six reasons profitability declines.” Memorized lists don’t work on their own, interviewers spot them instantly. The memorized structures are a starting point you have to customize to the specific case. Airline passengers care about different satisfaction drivers than restaurant guests. Know the patterns, but adapt every time.

7. Embrace Creativity Alongside Structure

MECE is necessary, but it’s not sufficient. If every bucket in your structure is something the interviewer has already heard from the last 20 candidates, you’re graded as “structured but unoriginal.” The insight quality matters. Push yourself to include non-obvious angles in every brainstorm, a second-order effect, a counter-intuitive hypothesis, an analogy from a different industry.

10 Common Brainstorming Mistakes That Cost Offers

The first two mistakes, idea-dumping and skipping the Pyramid Principle, are where 80% of weak brainstorms fail. Fix those first. Everything else is incremental.

Frequently Asked Questions

How is brainstorming different from framework questions in a case interview?

Framework questions test your ability to scope an analysis; they come early in the case and produce broad categories of investigation. Brainstorming questions test your ability to generate specific ideas; they come mid-case and produce concrete options, causes, or solutions. Both require MECE structuring, but they sit at different altitudes.

What makes a brainstorming answer “broad” and “deep”?

Breadth means 3-5 top-level buckets that cover the problem from multiple angles. Depth means 2-3 sub-ideas under each bucket, with at least two concrete examples per sub-idea. A broad-but-shallow answer feels generic; a deep-but-narrow one feels incomplete. Great answers hit both.

What are investigative vs. prescriptive brainstorming questions?

Investigative questions ask “why”, “What are the reasons sales are declining?” They drive toward diagnosis. Prescriptive questions ask “what now”, “What could we do to reverse the decline?” They drive toward action.

Why is MECE important in brainstorming, and how do I apply it?

MECE (Mutually Exclusive, Collectively Exhaustive) ensures your buckets don’t overlap and don’t miss anything important. In brainstorming, it keeps your structure clean so the interviewer can follow the hierarchy. To apply it: after listing your top-level buckets, stress-test by asking “could any idea fit in two buckets?” (exclusivity) and “is there a category of ideas I’ve completely missed?” (exhaustiveness).

How does the Pyramid Principle apply to brainstorming?

Lead with the synthesis (3-4 top-level categories in one sentence), support with each category and its sub-ideas, then close with prioritization. This is the opposite of how most people naturally communicate, which is why it needs deliberate practice. Barbara Minto developed the principle at McKinsey; it’s the communication standard at every top-tier firm.

How do I know when to use top-down vs. bottom-up brainstorming?

Top-down works when the problem is broad and you need to impose structure, “reasons for declining profitability” splits cleanly into revenue and cost. Bottom-up works when specific ideas come to mind quickly and you cluster them after, “how to attract Gen Z” generates tactics first, then groups them into digital, community, and brand. Most strong answers use both thinking techniques within the same brainstorm.

How do I incorporate interviewer feedback during a brainstorm?

When the interviewer asks “what else?” or pushes back on an idea, don’t abandon your structure. Integrate their input into an existing bucket, or explicitly add it as a new bucket: “That’s a good add, I’d put it under the environmental factors bucket as a fourth sub-idea.” Treating the interaction as a conversation, not a test, is a strong signal of consulting judgment.

How do I get better at generating creative ideas quickly?

Three moves. First, use analogies from different industries, “how would a SaaS company solve this?” when the case is in retail. Second, think about second-order effects instead of first-order ones, not “what will customers do?” but “what will customers do that changes what suppliers do?” Third, practice lateral thinking with open-ended drills.

How important is industry knowledge for brainstorming?

Industry fluency is what separates textbook answers from consulting-grade answers. If you don’t know how airlines price tickets, or what drives retail gross margin, you’ll default to generic buckets every time. Build industry knowledge through sector reports, news reading, and targeted resources like our industry cheat sheets.

Is it okay to memorize brainstorming structures?

Memorize the thinking techniques, never the answers. Knowing that profitability splits into revenue and cost is useful. Reciting “the four drivers of customer satisfaction” verbatim in every case is a red flag, interviewers grade customization, not recall. Use memorized structures as starting points, then adapt them to the specific case context in front of you.

Brainstorm Like a Real Consultant, Not a Case-Prep Book

Brainstorming is where candidates either stall or stand out. The ones who stall rattle off disconnected ideas and watch their scorecard drop. The ones who stand out bring a MECE top layer, two or three layers of depth, at least one insight the interviewer hasn’t heard before, and a prioritization close that connects back to the broader case.

None of this is innate. It’s a trained skill, and the training method is specific: isolated drills under time pressure, real business problems instead of textbook prompts, an error log, and feedback from someone who’s actually been on the other side of the interview table.

If you want the same structured training that’s helped 700+ candidates land offers at McKinsey, BCG, Bain, and other top firms through 1-on-1 coaching, our Structuring for Frameworks and Brainstorming program covers the theory, the techniques, and the deliberate drills that build the muscle. For a full application-to-offer path, the Case interview Academy is the fastest way to close the gap.

Modern case prep is broken because it teaches memorization instead of skills. Brainstorming is one of the clearest examples, the candidates who practice 50 full cases without drilling the underlying skill keep making the same mistakes. Fix the skill. The offers follow.

About the author: Florian Smeritschnig spent 5 years at McKinsey as a Senior Consultant and has coached 700+ candidates to offers at MBB, tier-2 firms, the Big 4, and in-house consultancies over the past years. He is the author of The 1%: Conquer Your Consulting Case Interview, The 1%: Case Interview Workbook, and Consulting Career Secrets, all available on Amazon.