Consulting Frameworks

You learned MECE. Then Porter's Five Forces. Then the 7S Model. Then the BCG Matrix. You have accumulated dozens of frameworks over your career, each one useful in a specific context — and you have no system for choosing between them.

“Consultants are trained to apply tried-and-tested methodologies. While these tools are valuable, their rigid application can limit opportunities to think outside the box.” 25% of consultants leave the industry within two years due to burnout. The answer is not another framework. It is a framework FOR frameworks — a meta-framework that tells you when each tool applies and when to abandon all of them.

The Framework Trap

Framework accumulation feels like skill development. Every new model you learn expands your toolkit. But there is a tipping point where more frameworks create less clarity. You sit in a client meeting with five possible lenses for the problem and no principled way to choose between them. The paralysis is not ignorance. It is abundance without organization.

The deeper problem is that frameworks address surface structure, not deep systems. MECE helps you organize a problem space. It does not help you determine whether you are solving the right problem. Porter's Five Forces maps competitive dynamics. It does not tell you whether competitive positioning is the actual bottleneck. Most coaching and consulting fails for the same reason — it works on the surface goal while the real constraint lives underneath.

Framework fatigue is the consultant's version of information overload. The more models you accumulate without integrating them into a coherent system, the harder each engagement becomes. You are not getting better. You are getting more cluttered.

The Meta-Framework: When to Use What

The solution is a schema about your schemas — a meta-framework that classifies your existing tools by problem type and builds selection rules. Instead of reaching for your favorite framework by default, you diagnose the problem first and let the diagnosis select the tool.

Start by inventorying what you actually know. Most consultants carry frameworks they learned in training that they have never used in practice, alongside informal heuristics they use constantly but have never named. The inventory makes the implicit toolkit explicit. Classify each framework by the type of problem it solves: competitive positioning, operational bottlenecks, organizational design, market entry, resource allocation.

Then build selection heuristics. “If the client problem shows symptoms of a bottleneck, use Theory of Constraints before reaching for a broader strategy framework.” “If the problem is ambiguous, map the system first — do not apply a framework until you understand the territory.” These rules eliminate analytical paralysis by giving you a decision process for choosing your analytical process.

Eli Goldratt's insight applies here: every system has exactly one bottleneck. The meta-framework is the tool for finding the bottleneck in the client's system before you decide which specialized framework to apply to it.

Beyond Frameworks: First Principles

• Inventory your frameworks. Catalog every model you use — the formal ones from training and the informal ones you have developed through experience. Classify each by problem type. Make the implicit toolkit explicit. You cannot organize what you have not named.
• Build selection rules. “If the client problem shows X, use framework Y.” These rules do not remove judgment — they focus it. Instead of choosing from thirty frameworks, you narrow to three based on the problem signature, then apply judgment within that shortlist. The rules eliminate the paralysis, not the thinking.
• Hold all models lightly. Every framework is wrong somewhere. Porter's Five Forces assumes stable industry boundaries. MECE assumes clean decomposition. The BCG Matrix assumes you can measure relative market share. The skill is not applying frameworks flawlessly. It is knowing where each one breaks down and adjusting for the distortion.
• Map the system when no framework fits. First-principles analysis is the consultant's ultimate fallback. When the client's problem does not map cleanly to any existing framework, abandon the frameworks entirely. Map the actual system — stakeholders, flows, constraints, feedback loops — and let the structure of the system reveal the intervention point.