Hypothesis: this should be one of the first things you write down and tell the interviewer **once

you
take a minute to create your buckets and collect your thoughts. Bain is very much about hypothesis
driven analysis

Common bucketing scheme I used: first bucket orient yourself on

Jot Information down about the business (ask about company, competitors, customers,
industry), second bucket is where you do some financial analysis
the client which the (learn about the economic model) and third bucket is to your
interviewer will give you in discretion based on the case Bucket 1
>> see case in point or Victor Cheng for typical frameworks
the prompt HERE If the case is about entering a new market or launching a new Once you are done analysis in
product, the first bucket is almost always mostly focusing on the each bucket, make sure you
customer and competitor because you want to quantify or at
SYNTHESIZE before heading to
Usually at the bottom of this least understand the potential opportunity, Then second bucket
is thinking about the economics and business case for it (how the next bucket of analysis, aka
section is where the actual much it would cost to enter, what you should price it as etc.) summarize the main takeaways
Framework
ASK goes, the stuff above is and learnings of that analysis
usually important context Random other tips,
- better to talk more than less, so say whatever you are Bucket 2
thinking this way they can actually jump in and help
Make sure you don’t forget any numbers guide you if you're thinking down the wrong path.
given to you in the prompt, often they - They love case studies (duh), so if you have a
will be something you use in later hypotheses within buckets and its because you saw
analysis but a lot of people forget about another business similar go through the same thing,
Conclusion format:
them call it out. - Recommendation first, summarize the main
- DONT BE SCARED TO ASK FOR TIME TO THINK OR TO supporting points for that recommendation,
DO THE MATH IN SILENCE. It feels longer to you than include numbers whenever its relevant, (example:
it does to them. Better to take a minute to think than don’t raise prices because we found out the product is very elastic

-
to ramble unstructured-ly like a bum
If they ask you to list anything ever take a minute to
Bucket 3 and thus an increase in price of ‘a’ would reduce volume by ‘x’ thus
decreasing overall revenue by ‘y’)
construct some structured approach to then give them one next step [implementation
brainstorming
- Always prioritize. Prioritize analyses, prioritize lists piece] and a potential risk