Frameworks are scaffolding, not answers

Intuition

Beginners collect frameworks like trading cards and try to play one on every case. But frameworks are scaffolding, the temporary structure around a building under construction. Scaffolding helps you reach the work and keeps you organized, yet nobody confuses it with the building itself. The building is your tailored reasoning about this client's specific problem. Strong candidates use scaffolding lightly and take it down the moment it's in the way.

The paradox of this whole module: you learned the frameworks so that you can stop leaning on them.

Framework

How to hold frameworks correctly:

• Start from the objective, not the framework. Ask what decision the case serves, then build toward it, borrowing framework pieces only where they fit.
• Tailor ruthlessly. Keep the branches that matter for this problem; drop the ones that don't. A half-used framework that fits beats a complete one that doesn't.
• Never announce the name. Say "I'd look at the customer demand, our ability to deliver, and how rivals respond", not "I'll use the 3 Cs."
• Invent when nothing fits. Most real prompts need a custom tree. Frameworks are a vocabulary, not a script.

Worked Example

Prompt: "A symphony orchestra is losing its audience. What should it do?" A weak candidate forces Porter's Five Forces onto a non-profit and flounders. A strong one builds from scratch: "I'd look at who is leaving (segment the lost audience), why (substitutes, price, relevance), and what we can credibly offer (programming, venue experience, digital access)." That structure quietly uses customer and competitor thinking, but it's shaped to an orchestra, not pulled off a shelf. The interviewer sees thinking, not recall.

One more, in an operations setting: "A hospital ER has 4-hour wait times." The weak candidate gropes for a business framework that doesn't exist for this. The strong one builds from the physics of the problem: demand (arrivals, say 10 patients/hour at peak), capacity (throughput, 8 patients/hour across staffed bays), process (triage and handoff delays between the two). With arrivals exceeding throughput by 2 patients an hour, the queue grows by design, and each bucket points to a different fix. No framework name on earth was needed; just the objective, decomposed.

In the room

The opening sentence of your structure is where this lesson lives or dies. Say: "Given the goal is reversing the attendance decline, I'd look at who we're losing, why they're leaving, and what we can credibly change." Never say: "I'll apply the 3 Cs here." Same underlying thinking, opposite signal. When a framework genuinely fits, use its content and skip its name: "I'd want to understand whether this industry can support healthy margins at all, who holds the power over price?" That's Five Forces working incognito. And if your structure stops fitting mid-case, renovate aloud: "The data suggests this is an operational problem, not a demand problem, let me restructure." Adapting visibly is a strength signal, not a confession. The interviewer is scoring ownership: whether the structure sounds built for this client, or retrieved from a flashcard.

Pitfalls

• Picking the framework first and then bending the problem to fit it.
• Reciting framework names instead of building tailored buckets.
• Refusing to abandon a framework once it's clearly not fitting the case in front of you.