Pete Buttigieg’s case advice: show how you think.

Thinking aloud does not mean broadcasting every thought. A listener needs to know where you are going and why.

Compare these two openings for a retailer considering Sunday opening:

“I'd look at customers, competitors, the company, costs, revenues and any other relevant factors.”

“I'd first estimate the extra contribution from Sunday sales, then subtract the staffing and operating costs. I'd also check how much of Sunday's demand would move from other days, because that would reduce the benefit.”

The second answer gives the interviewer something to evaluate. It identifies the decision, the economics and an assumption that could reverse the conclusion.

The categories in the first answer are not inherently wrong. They simply leave the important work unsaid. A structure becomes useful when its branches describe questions that can change the recommendation.

Use the structure to explain your approach to the specific problem. The interviewer should understand why each branch belongs.

Suppose the retailer expects $12,000 in Sunday sales. After product costs, 30% remains as contribution. Additional staffing and operating costs are $2,000.

You could calculate $1,600 and announce that Sunday opening is profitable. A clearer explanation is:

“At a 30% contribution margin, $12,000 of sales contributes $3,600. After the extra $2,000 operating cost, Sunday opening adds $1,600 before any effect on sales during the rest of the week.”

The final phrase matters. It preserves an assumption that the next question may challenge.

Now suppose 40% of Sunday sales would otherwise have occurred on Saturday, at the same margin. Only $7,200 of sales is genuinely additional. That contributes $2,160, leaving just $160 after the extra operating cost.

The recommendation should change. The initial proposal looked attractive; after allowing for shifted sales, the benefit is small enough that demand and cost assumptions deserve close attention.

You have shown your thinking by making the relationship visible, not by narrating each multiplication in unnecessary detail.

An issue tree can help you organise the work. It is not a performance you need to display perfectly.

For the Sunday example, a useful page might contain the objective, three questions and a small space for findings:

• How much demand is additional?
• What contribution does that demand generate?
• What extra operating costs or constraints arise?

As information arrives, write the implication beside the relevant question. If the answer shows that sales mostly shift from Saturday, do not continue mechanically through a long market checklist. Investigate the assumption that now drives the decision.

Keep key takeaways together on your page and carry units through the calculations. You will need both when you return to the client's decision.

Your notes should make the reasoning easier to manage. If maintaining a beautiful diagram distracts you from the interviewer's new information, simplify the page.

You do not need to produce the entire argument instantly. Ask for a moment to organise the approach, then return with a clear explanation.

If a question is ambiguous, clarify the part that affects the analysis. “Are we trying to maximise total weekly profit, or increase customer access while keeping profit stable?” could change the Sunday-opening recommendation.

Avoid using clarification as a way to postpone every decision. Once the objective and important constraints are clear, make a reasonable first move and explain it.

Give the interviewer enough visibility to work through the problem with you. Explain why you are taking the next step.

Ask a partner to change one assumption after your first recommendation. In the retailer example, they could reduce the shifted-sales estimate, increase staffing cost or say Sunday opening is needed to retain valuable customers.

Your response should identify what changed and update the relevant part of the analysis. You do not have to rebuild the entire structure from scratch.

For example: “If only 20% of Sunday sales moves from other days, incremental sales are $9,600. That produces $2,880 of contribution and $880 after the added operating cost. The case for opening is stronger, though I would still test demand before extending the schedule permanently.”

This is confident reasoning: a clear view that responds to evidence. Defending the first answer after its assumptions change is rigidity, not confidence.

The reported advice includes practising with a friend. Give that person a job more useful than saying whether you sounded confident: ask where they stopped understanding why your next analysis mattered.

Replay that moment. State the decision, the evidence you used and the implication in one or two sentences. Then try a fresh prompt so the improvement is not a memorised line from the Sunday example.

That is the scope of the lesson: make your reasoning followable while another person listens. For a fuller method, use our guide to structuring without a script. A spoken structure drill lets you test the same skill on a different problem.