A framework can be clear on paper and hard to follow aloud. Your notes show indentation, arrows and space between branches. The interviewer hears a sequence of sentences.
Make that sequence carry the structure. Tell the listener the main questions, explain the important test inside each and say where you want to begin. They should understand the plan without reading your page.
You do not need more impressive vocabulary. You need to make the relationships between your ideas easier to hear.
Say what you are trying to find out
Consider a premium pet-food company that sells through veterinary clinics in Europe and is considering entering Japan. This is an illustrative prompt; the case would supply the market evidence.
A weak presentation might begin:
“First I'd look at the market, including size, growth, competitors, customers and trends. Then the company, with capabilities, brand, distribution, finance, people and suppliers. Then risks, like regulation, supply chain and competition.”
The candidate has named plenty of relevant topics. The interviewer still has to infer how they lead to an entry decision. Competition appears twice, while the link between the veterinary channel and the new market remains unexplained.
Before presenting, turn each branch into a question whose answer matters. “Customers” could become “Which pet owners would pay for this offer, and why would they choose it?” “Distribution” could become “Can we reach them through clinics, or do we need another route?”
That small change does much of the work of making a framework sound thoughtful.
Give the listener the main branches first
Here is a clearer version:
“I'd test three things: whether enough customers would choose this product, how we could reach them, and whether the entry economics work. On demand, I'd focus on owners willing to pay for a premium offer and what they use today. On the route to market, I'd test whether the company's veterinary-channel strength transfers or whether it needs a local partner. Then I'd compare contribution after channel and adaptation costs with the investment required. I'd start with the target customer and their alternatives, because that will shape both the offer and the distribution route.”
The opening sentence provides the structure. Each following sentence explains one branch. The last sentence identifies a starting point and its purpose.
The answer is specific because it uses the client's channel and premium positioning. It does not need to assert facts about Japanese customers that the case has not established.
Make both the plan and its reasoning audible. The interviewer should understand how your structure helps answer the client's question.
Give each branch enough detail to be useful
You are deciding how to investigate the case. You do not need to announce every possible question you might ask later.
For the demand branch, target customers, their alternatives and willingness to pay may be enough to establish the approach. You can explore detailed segments when you reach that analysis.
A useful editing test is to remove a detail and ask what the listener loses. Removing “willing to pay for a premium offer” loses an important test. Removing a list of five possible demographic cuts may lose very little at this stage.
Keep words that explain a mechanism. “Distributor fees could reduce the margin” does more work than “financial considerations”. “Clinic relationships may help us reach customers” does more work than “synergies”.
If your explanation remains long after you remove unnecessary detail, inspect the underlying structure. You may be combining several unrelated ideas in one branch or presenting the same issue twice.
Quick Structuring Drill
A maker of rapid electric-vehicle chargers wants to sell to retail park owners. You are presenting the demand and economics branches of your opening structure.
Which details belong in your opening structure, and which can wait?
Make the transitions explicit
Use short signposts and a small pause when you move between branches. Your listener should not have to work out whether you have started a new topic or added a detail to the current one.
Try:
“The second question is how we would reach those customers.”
That sentence is especially useful on a phone or video call, where the interviewer may never see your notes. Name the subject you are returning to instead of relying on “the second bucket.”
The same principle applies later in the case:
“We've established that customers would consider the product. I'd now test whether the distributor route leaves enough margin.”
The transition explains what you have learned and why the next analysis follows. It keeps the framework useful after the opening presentation.
Explain your priority without pretending to know the answer
“I'm going to start with the market” is a choice. Adding the reason makes it a judgment the interviewer can assess.
For the pet-food case, starting with customers makes sense if the offer and route depend on who will buy. But suppose the prompt instead says the product cannot legally be sold in its current form. The first question may be whether adaptation is feasible within the launch deadline.
Use the actual constraint to choose. You can say:
“Before estimating demand, I'd check whether the product can be adapted and approved within the deadline. If it cannot, the proposed launch timing won't work.”
A priority can rest on an uncertainty that could rule out the option. It does not require a confident prediction about which answer the interviewer has hidden in the case.
Quick Structuring Drill
A home-battery installer earns revenue only when a battery is fitted. First-year revenue is behind plan.
- Orders vs plan
- 12% above
- Fittings vs plan
- 20% below
- Crew wait time
- 11 weeks
Which stated priority best explains where you would start the analysis?
Respond naturally when the interviewer interrupts
If they ask you to be shorter, give the main questions and the first step:
“I'd assess demand, route to market and economics. I'd start with the target customer, since that determines the offer and channel.”
Then stop and let the interviewer steer. Do not restart the full explanation at a faster pace.
If they challenge a branch, explain what it is meant to test. If they tell you the issue is already resolved, use that information and move on. For example:
“If a distribution partner is already secured, I'll use those terms in the economics and focus the remaining feasibility work on product adaptation and supply.”
You are demonstrating that the structure responds to information. Finishing every prepared sentence is less useful than keeping the conversation aligned with the question.
Practise with a listener who cannot see your notes
Record one presentation, then ask someone to tell you the main questions and the starting point. Their summary is more informative than asking whether you sounded confident.
If they miss a branch, inspect the transition. If they remember topics but cannot explain why they matter, rewrite the branch as a question. If they remember every detail but cannot see the overall plan, move the overview earlier.
Check the explanation separately from the analysis. A sound structure still needs to be presented in a sequence the listener can follow.
Repeat the same presentation once after editing. Then use a new prompt so you practise the habit of organising the explanation, rather than memorising a speech.
Try Beauty Brand Retail Expansion, our Consumer / Beauty structure drill. It takes about four minutes. Give the main questions first, use the company's situation in the branches, and explain your first analysis.
Structure drill
Would your case structure convince an MBB interviewer?
Beauty Brand Retail Expansion
Present your approach aloud. Get feedback on how you break down the problem, prioritise your analysis and explain your structure.
If the branches themselves are still difficult to build, return to how to create a case framework. For an interviewer who challenges the approach, read how to handle pushback.
Frequently asked questions
Building the spoken structure
Why does my framework sound confusing when it looks clear on paper?
The interviewer hears a sequence of sentences, not your indentation and arrows, so the spoken order has to carry the structure. Tell the listener the main questions, explain the important test inside each and say where you want to begin. They should then understand the plan without seeing your page.
What is wrong with opening with market, company and risks?
Those are topics, not questions, and a long run of them buries the logic. Listing size, growth, competitors, capabilities, brand and regulation gives the interviewer nothing to assess. Instead, say what you are trying to find out, such as whether enough customers would choose the product.
Do I need more sophisticated vocabulary to sound structured?
You do not. Clarity comes from making the relationships between ideas audible, not from impressive terms. Phrasing each branch as a plain question, such as ‘how could we reach those customers?’, tells the listener why it matters. Labels without that link can make a framework harder to follow aloud.
How should I open the framework?
State the main branches before any detail. In the pet-food example: ‘I'd test three things: whether enough customers would choose this product, how we could reach them, and whether the entry economics work.’ Only then explain the key test inside each branch, such as whether the company's veterinary-channel strength transfers to Japan.
How much detail should each branch have?
Give enough detail to show how you will investigate, not every question you might ask later. For demand, target customers, their alternatives and willingness to pay may be enough to set the approach. Detailed segmentation can wait until you actually reach that analysis.
How do I decide which details to cut?
Remove a detail and ask what the listener loses. If the branch still conveys what you are testing and why, the detail was probably clutter. If removing it leaves the listener unsure how you would answer that question, put it back.
Signposting and setting priorities
How do I make it obvious that I've moved to a new branch?
Use a short signpost and a brief pause, such as ‘The second question is how we would reach those customers.’ The listener should never have to guess whether you have started a new topic or added detail to the current one. This matters most on phone or video calls, where the interviewer may never see your notes.
Is it enough to say which branch I'll start with?
Saying where you will start is not enough on its own, so add the reason. ‘I'm going to start with the market’ is a choice. Explaining why turns it into a judgement the interviewer can assess. In the pet-food case, starting with customers makes sense because the offer and route to market depend on who will buy.
What if the prompt reveals a constraint that changes the starting point?
Let the constraint reorder your priorities. If the product cannot legally be sold in its current form, the first question may become whether adaptation is feasible, rather than who the customers are. Explaining that shift shows judgement without pretending you already know the answer.
Interruptions and practice
What should I do if the interviewer asks me to be shorter?
Give the main questions and your first step, then stop. For example: ‘I'd assess demand, route to market and economics. I'd start with the target customer, since that determines the offer and channel.’ Let the interviewer steer from there rather than restarting the full explanation at a faster pace.
How should I respond if the interviewer challenges one of my branches?
Explain what the branch is meant to establish and how it bears on the decision, rather than simply repeating it. Keep the reply brief and specific to that branch, so the conversation stays on your approach instead of restarting the whole framework.
What is the best way to practise presenting a framework?
Record a presentation and ask someone who cannot see your notes to tell you the main questions and your starting point. Their summary tells you more than asking whether you sounded confident, because it shows what actually came across when the structure had to travel through speech alone.
My practice listener's summary was off. How do I fix it?
Match the gap to its cause. If they missed a branch, inspect the transition into it. If they recall topics but not why they matter, rewrite the branch as a question. If they remember every detail but cannot see the overall plan, move the overview earlier.