Building an Initial Structure

This lesson teaches how to turn a case prompt into a customized initial structure that is relevant, complete enough, and easy for the interviewer to follow.

Why This Matters

The initial structure is one of the strongest signals in a case interview.

It shows whether you can:

• translate a business problem into logical parts
• organize ambiguity quickly
• choose a sensible analytical path

A weak structure makes the rest of the case harder. A strong one gives you a usable map.

What Good Looks Like

A good initial structure is not a long list of business words.

It is a practical decomposition of the client problem into the main drivers that should determine the answer.

The best structures are:

• case-specific
• logically organized
• easy to explain
• useful for prioritization

In the Interview

After clarifying the objective, take a brief pause and ask:

• what is the client really trying to decide?
• what are the major drivers of that answer?
• what branches are most useful for analyzing it?

Then present the structure in a concise, top-down way.

A Reliable Way to Do It

1. Start from the objective

A profitability problem and a market entry problem need different structures because the client is asking different questions.

2. Choose top-level branches that match the business logic

Examples:

• revenue vs costs
• market attractiveness vs client capabilities
• customer demand vs economics vs competition

3. Make the branches distinct

If two branches overlap heavily, the structure becomes messy.

4. Keep it short enough to be spoken clearly

A live interview is not a whiteboard workshop.

5. End with a first priority

A structure is much stronger if you say where you would start and why.

Example

Prompt:

“Our client is considering launching a new premium bottled tea.”

A weak structure:

• customers
• company
• competition
• product
• marketing

This may sound broad, but it does not yet feel tied to the decision.

A stronger structure:

• customer attractiveness: is there enough demand and willingness to pay?
• business economics: can the product generate attractive margins and scale?
• launch feasibility: does the client have the capabilities, channel access, and brand fit to launch well?

Then:

“I would start with demand and willingness to pay, because without customer pull the rest of the launch case is much less compelling.”

What Strong Candidates Do

A strong candidate:

• tailors the structure to the prompt
• uses branches that map to the business decision
• keeps the explanation concise
• prioritizes after structuring

What Weaker Candidates Tend to Do

A weaker candidate often:

• gives memorized frameworks
• uses too many branches
• uses vague labels
• stops after listing categories

Common Traps

Mistake 1: Generic frameworks

The interviewer wants to hear thinking, not category recital.

Mistake 2: Laundry-list structures

If your structure has too many top-level buckets, it becomes hard to use.

Mistake 3: Missing the real decision

A structure can be organized and still answer the wrong question.

Mistake 4: No prioritization

The interviewer should know where you want to go first.

Practice Prompt

Take this prompt:

“A bank wants to enter the SME lending market.”

Write a first-pass structure with three to four top-level branches and a one-sentence explanation of where you would start.

Example Response

A strong spoken structure might sound like this:

I would break this into three areas. First, market attractiveness: how large and profitable is the SME lending opportunity, and how competitive is it? Second, client capability: does the bank have the risk, distribution, and underwriting strengths needed to compete? Third, economics and risk: what returns could the client earn and what credit or operational risks might undermine them? I would start with market attractiveness and economics to determine whether this is even worth pursuing.

What to Remember

• A good initial structure is tailored to the case, not memorized from a list.
• It should break the client problem into clear, decision-relevant branches.
• Strong structures are concise, usable, and directional.
• Prioritization is part of a strong structure, not an optional extra.