When Frameworks Fail: Building a Bespoke Structure
A CEO does not walk in saying, "Please apply Porter's Five Forces to my business." She says, "Growth has stalled in our best city, costs are rising, and our new product is confusing customers." The weak candidate reaches for a memorised framework; the strong candidate builds the structure the problem is asking for.
- Frameworks fail when the case has unusual economics, multiple objectives, unclear boundaries, or a decision that does not match a textbook template.
- A bespoke structure is a custom issue tree built from the client’s exact problem, decision, constraints and success metric.
- Start with the decision to be made, not the framework you remember.
- Build branches that are MECE: no overlap, no gaps.
- Use standard frameworks as raw material, not as the final answer.
- The best structures are hypothesis-led: each branch tests a reason why the problem may be happening or how the decision can be made.
- The most common mistake is naming a famous framework and forcing the case into it.
Big Picture: A Framework Is a Starting Point, Not a Cage
Think of a consulting framework like a map of a familiar city. It helps if the terrain matches. But when the client problem cuts across customers, operations, regulation, pricing and execution, you need to draw a custom map before you start walking.
Core Explanation: Why Standard Frameworks Break
Standard frameworks are powerful because they compress experience. The 3Cs help in market questions. Profitability trees help in margin decline. The 4Ps help in marketing mix decisions. But they break when the case is not really asking for that framework.
For example, "Should a food-delivery platform enter a smaller Indian city?" is not just a market-entry case. It may need demand density, restaurant supply, delivery economics, consumer frequency, competitive response, regulatory constraints and unit economics. A plain market-entry checklist can miss the heart of the answer.
If you need to sharpen the first move before structuring, revise defining the problem before solving it. A bad problem definition creates a bad structure even when the framework sounds impressive.
The Bespoke Structure Method: Build the Case Around the Decision
A bespoke structure is not random brainstorming. It is a disciplined issue tree built around one question: what must be true for this recommendation to be right?
The Anatomy of a Strong Bespoke Issue Tree
A good custom structure normally has four layers. The top is the decision. The second layer is the logic that determines the decision. The third layer is evidence. The final layer is action.
Here is the difference between a weak and strong structure for the same problem: "An Indian diagnostics chain is considering expanding into Tier-2 cities."
Notice the shift. The weak structure lists categories. The bespoke structure explains how the business would actually win or lose money.
Definitions You Should Be Able to Say Smoothly
- Framework: A reusable structure that organises analysis into logical buckets.
- Issue tree: A breakdown of a problem into smaller questions that can be tested independently.
- MECE: A structure with no overlap between branches and no important gap in coverage.
- Bespoke structure: A custom issue tree built for the client’s specific decision, economics and constraints.
- Hypothesis-led analysis: Testing the most likely explanation first, instead of analysing every bucket equally.
When to Abandon the Standard Framework
You do not abandon frameworks because you want to sound creative. You abandon them when they stop explaining the client’s reality.
For market-entry cases, you may still borrow from competitive landscape and barriers to entry, but the branches must be shaped around the exact business model and decision.
How to Build Branches That Feel MECE
The easiest way is to choose one clean basis of splitting. Do not mix customer types, cost heads, geographies and time periods in the same layer unless you are intentionally creating sub-branches.
A good trick: after you create branches, ask, "Could one data point belong to two branches?" If yes, your tree is overlapping. Then ask, "What could make the recommendation wrong that is not covered here?" If you find something, your tree has a gap.
Mini Case Study: IndiGo and the Operating Model Behind Low Cost
IndiGo shows why a generic airline profitability framework is not enough; the real structure must explain how operational choices create cost advantage and customer reliability.
Suppose the case prompt is: "An airline wants to improve profitability in India." A weak candidate draws a standard profit tree: revenue minus cost. That is not wrong, but it is too shallow. Airlines do not win only by cutting line-item costs; they win by designing an operating model where aircraft, crew, routes, maintenance and customer promises reinforce each other.
IndiGo’s model is a useful Indian example. Its investor communications emphasise a low-cost carrier model built around operational simplicity, punctuality, affordable fares and network reach (IndiGo Investor Relations). The primary driver is operating standardisation - especially a simplified fleet and repeatable turnaround processes. Supporting drivers include high aircraft utilisation, dense route planning, a no-frills service model, disciplined capacity deployment and brand trust around reliability.
A bespoke structure for this case would not stop at "reduce fuel cost" or "increase fares." It would ask: where is aircraft productivity leaking, where is network design suboptimal, where is the service promise creating avoidable cost, and where can revenue improve without damaging load or loyalty?
The lesson: a standard profit framework identifies the accounting symptom. A bespoke structure explains the operating cause. In interviews, that difference is visible immediately.
How AI Changes Building a Bespoke Structure
AI does not remove the need for structure. It raises the bar because anyone can ask a chatbot for "a market-entry framework." Your advantage is using AI to create, challenge and sharpen a structure that fits the exact case.
- AI can generate alternative issue trees quickly. Ask ChatGPT or Claude for three different structures: one based on P&L, one based on customer journey, and one based on unit economics. Then choose the one that best fits the decision.
- AI can stress-test MECE quality. Paste your structure and ask: "Which branches overlap? What important driver is missing? Which branch would you test first and why?"
- AI can simulate interviewer pressure. Use Perplexity or ChatGPT to convert a business headline into a live case prompt, then practise defending why your structure is custom rather than memorised.
Use NotebookLM for revision: upload your case notes and one company annual report, then ask, "Create a bespoke issue tree for a profitability, growth and market-entry case for this company. Then challenge the tree for MECE gaps." After that, practise the same structure aloud using AI as a mock interviewer.
Interview Relevance
"You have learnt many frameworks. Tell me about a situation where you would not use a standard framework, and show me how you would structure the problem instead."
In a live case, say: "I will use a custom structure rather than a standard framework because the decision depends on these specific economics." That one sentence signals maturity.
Common Mistake
The mistake: forcing a famous framework onto the case and then defending it because it sounds familiar. Why it costs you: the interviewer sees that you are recalling notes, not solving the client problem. One-line fix: start with the decision and success metric, then build only the branches needed to reach that decision.