Keywords: what is a framework, when to use frameworks, framework vs first principles, mental models frameworks, cargo cult adoption frameworks, framework adoption lifecycle, evaluating frameworks, strategic frameworks, conceptual frameworks
Tags: #frameworks #mental-models #decision-making #strategic-thinking #first-principles
Every few years, a new framework sweeps through business schools, consulting firms, and management circles. Jobs-to-be-Done. The Lean Startup. OKRs. Design Thinking. Blue Ocean Strategy. JTBD. Wardley Maps. Each arrives with compelling case studies, high-profile endorsements, and the implicit promise that organizations applying this framework will think more clearly, decide better, and outperform those that do not.
Some organizations apply these frameworks and improve substantially. Others adopt the same framework and achieve nothing except new meeting vocabularies and expensive consultants. The difference rarely comes down to which framework was chosen. It comes down to whether the organization understood what a framework is, what it is for, and when it should be discarded.
What a Framework Actually Is
A framework is a structured set of concepts, categories, relationships, or principles that organizes thinking about a class of problems. Frameworks do not tell you what the answer is. They tell you what questions to ask, how to structure the problem, which variables are likely to matter, and which relationships to examine.
The word is used loosely to cover several distinct things:
Conceptual frameworks: Organized sets of concepts for understanding a domain. Porter's Five Forces is a conceptual framework for analyzing competitive dynamics — it names five categories of competitive pressure and claims these are the most important ones to assess.
Process frameworks: Step-by-step sequences for approaching a type of problem. Design Thinking (Empathize, Define, Ideate, Prototype, Test) is a process framework for creative problem-solving.
Analytical frameworks: Tools for categorizing and evaluating options. The BCG Growth-Share Matrix plots business units on two dimensions and recommends strategic choices for each quadrant.
Mental models: Simplified representations of how systems work. "Second-order thinking" is a mental model that reminds you to consider the consequences of consequences, not just immediate effects.
What all frameworks share is that they are abstractions. They sacrifice the full complexity of reality for structured, communicable patterns that are easier to apply quickly and consistently.
The cost of that abstraction is often invisible to users who have not examined the framework's assumptions. Every abstraction is also an exclusion — the variables a framework does not include are treated as unimportant, and that treatment may be incorrect in your specific context.
Why Frameworks Exist
Frameworks exist because expertise cannot always be transferred directly. When a skilled strategist analyzes a competitive situation, she draws on thousands of hours of pattern recognition: she has seen variations of this problem before, she has a sense of which variables typically drive outcomes, and she has intuitions about which options tend to work. That expertise is mostly tacit — it lives in her head, not in a document.
A framework is an attempt to extract some of that tacit expertise into an explicit, teachable structure. Michael Porter's Five Forces framework did not appear from nowhere; it emerged from Porter's extensive analysis of competitive dynamics across industries, documented in his 1979 Harvard Business Review article and expanded in Competitive Strategy (1980). The framework is a compression of those observations into a form that others can apply without Porter's full library of experience.
This is frameworks' central value: they are codified experience. They allow people who have not yet built deep domain intuition to benefit from the pattern recognition of those who have.
This is also their central limitation. The codification is always incomplete and always context-specific. Experience gets compressed in ways that necessarily discard detail — and the detail that gets discarded is often the detail that matters most in situations that differ meaningfully from those that generated the framework.
Research by Atul Gawande, reported in The Checklist Manifesto (2009), illustrates this dynamic in medicine. Checklists — a simple form of framework — demonstrably improve outcomes in surgical settings because they capture the collective wisdom about which steps get skipped under pressure. But Gawande is careful to distinguish checklist compliance from checklist understanding: surgeons who know why each step matters apply them more intelligently than those who follow them mechanically, particularly in edge cases the checklist designers did not anticipate.
"A good framework is like a checklist for the experienced: it ensures you do not forget important considerations. For the inexperienced, it is more valuable — it provides a map of a territory they have not yet explored."
The Framework Adoption Lifecycle
Frameworks follow a predictable cultural trajectory that affects how reliably they perform across contexts:
Phase 1: Emergence
A practitioner or researcher notices a pattern across multiple situations. They write a book, publish a paper, or give a talk. The framework is new, context-specific, and closely tied to its originator's specific experience. The caveats and qualifications that the creator knows intuitively are present but rarely foregrounded.
Phase 2: Validation
Early adopters apply the framework and find it useful in contexts similar to those that generated it. Case studies accumulate. The framework spreads within a specific domain. Feedback from early adopters refines the model, and the creator often publishes updated versions that acknowledge edge cases.
Phase 3: Popularization
Business press, consultants, and educators adopt the framework. It becomes simplified, sloganized, and detached from its original context. The nuances that made it valuable in Phase 1 get stripped out for accessibility. A concept that required a 400-page book to explain properly is reduced to a 2x2 matrix and a keynote slide.
Phase 4: Dogmatization
The framework is now taught as if it is universally applicable. Organizations adopt it not because they have evaluated its fit but because it is the current standard. Deviation from the framework requires justification; following it does not. Criticism of the framework is treated as a sign of naivete rather than informed skepticism.
Phase 5: Backlash
Practitioner evidence accumulates that the framework does not work in many contexts. A new framework emerges to replace it, usually addressing the predecessor's known failure modes. The cycle repeats.
Most widely-discussed business frameworks are somewhere in Phase 3 or 4. That does not make them useless, but it means the context-specificity that made them valuable has been obscured. Porter's Five Forces is genuinely useful for analyzing stable industrial markets; it was in Phase 1-2 when applied by sophisticated strategists who understood its limitations. By Phase 4, it was being applied to platform businesses and startup ecosystems where its core assumptions did not hold, and the analysis produced confidently wrong conclusions.
When Frameworks Add Value
Frameworks are most valuable in specific conditions:
Unfamiliar Territory
When you are solving a type of problem you have not encountered before, a framework from people who have faced similar problems provides efficient orientation. It tells you what categories of things matter, prevents you from forgetting critical considerations, and speeds up problem structuring.
A first-time product manager using Jobs-to-be-Done is likely to build better products than one who has never encountered the concept — not because JTBD contains magic, but because it focuses attention on user motivations rather than feature lists in a way that beginners might not naturally think to do. Clayton Christensen, who developed the framework with colleagues, described in Competing Against Luck (2016) how the most common failure mode in product development is building around product attributes rather than around the functional, social, and emotional jobs customers are trying to accomplish.
Group Alignment
Frameworks provide shared vocabulary. When a team needs to discuss a complex problem together, having common terms for the key concepts dramatically reduces ambiguity and miscommunication. "What does our Porter analysis say about supplier power?" is a more efficient starting point for a discussion than building the conceptual architecture from scratch each time.
Research by Edwin Hutchins on distributed cognition (1995) shows that teams sharing common representational systems — including frameworks — coordinate more efficiently and make fewer communication errors than teams that must negotiate terminology in real time. The benefit is especially pronounced under time pressure.
Preventing Cognitive Shortcuts
Under time pressure or cognitive load, people naturally skip steps. A framework operating as a checklist ensures important considerations are at least examined, even when conditions push toward hasty decisions.
Daniel Kahneman's dual-process theory, described in Thinking, Fast and Slow (2011), distinguishes between System 1 (fast, intuitive, automatic) and System 2 (slow, deliberate, analytical) thinking. Frameworks help activate System 2 thinking in situations where System 1's shortcuts would otherwise dominate. The checklist does not replace judgment — it creates a trigger to engage judgment where it might otherwise be bypassed.
Teaching and Onboarding
Frameworks are excellent pedagogical tools. They give newcomers structured ways to approach professional problems. A consulting firm that trains every analyst in a consistent problem-solving framework produces more consistent analytical output than one that relies entirely on each person developing intuition independently.
McKinsey's MECE (Mutually Exclusive, Collectively Exhaustive) principle, for instance, provides new consultants with a structural discipline for problem decomposition that takes experienced analysts years to develop through practice. The framework accelerates that development even if the analyst eventually internalizes and moves beyond its explicit application.
When Frameworks Constrain Thinking
Frameworks become liabilities in specific conditions:
When the Problem Does Not Fit the Framework's Assumptions
Every framework embeds assumptions about what the important variables are and how they relate. Porter's Five Forces assumes relatively stable industry structures; it was designed to analyze manufacturing and services industries in the 1970s and 1980s. Applied to platform businesses, digital markets, or network-effect dynamics, several of its categories become less meaningful while the most important competitive dynamics (ecosystem control, data advantages, switching costs) are underemphasized or absent.
A widely cited 2001 paper by Michael Rappa on digital business models explicitly noted that Porter's framework struggled to accommodate the competitive dynamics of internet platforms, where the competitive advantage often lies not in supplier or buyer power but in controlling the architecture through which all participants transact.
Using a framework in conditions where its assumptions do not hold produces analytical errors that feel rigorous because they follow the framework's structure. This is one of the most dangerous failure modes: the analysis is internally consistent, follows the methodology correctly, and is therefore trusted — while being systematically wrong because the framework was applied in conditions it was not designed for.
When You Are Expert Enough to Think From First Principles
First principles thinking means reasoning from fundamental truths about a situation rather than from patterns observed in similar situations. It requires more cognitive effort but produces solutions tailored to the actual specifics of the problem rather than to the category the problem superficially resembles.
For genuinely novel problems — situations that do not fit established patterns — first principles thinking typically outperforms framework application. Elon Musk's articulation of first principles thinking as "boiling things down to the most fundamental truths and then reasoning up from there" describes the process of setting aside analogical reasoning (including frameworks) to understand what is actually true about the specific situation.
Physicists routinely distinguish between analogical reasoning (this situation resembles one I've seen before, so I'll apply the same approach) and first principles reasoning (what are the fundamental constraints on this system, and what do they logically imply?). The former is faster; the latter is more powerful for genuinely novel problems. SpaceX's ability to dramatically reduce launch costs came not from applying aerospace industry frameworks — which all suggested that certain cost floors were structural — but from questioning the assumptions those frameworks embedded.
Experts in a domain often need frameworks less than beginners do, because they have internalized sufficient pattern recognition to substitute for explicit framework application. Insisting that an expert apply a framework they have effectively superseded can slow rather than improve their thinking.
When Framework Use Becomes Performative
A deeply problematic pattern occurs when frameworks are used to perform analytical rigor rather than to achieve it. This happens when:
- Slides are structured around framework categories whether or not those categories illuminate the specific situation
- Frameworks are cited to justify pre-determined conclusions
- Framework vocabulary is used to signal membership in a professional community rather than to communicate precisely
- Discussions focus more on whether the framework was applied correctly than on whether the framework is appropriate
Research by Matthew Stewart in The Management Myth (2009) documents how the consulting industry's framework-heavy methodology frequently serves the function of providing clients with the appearance of rigorous analysis rather than the substance of it. Frameworks become theatrical when their primary audience is not the decision-maker but the evaluator of the decision process.
When framework use is more about signaling competence to others than about actually improving decisions, it has become theatrical. The appearance of analysis substitutes for analysis itself.
Cargo Cult Framework Adoption
The most damaging form of framework misuse is cargo cult adoption — copying the practices associated with a framework without understanding the logic those practices serve.
The term comes from a remarkable anthropological phenomenon following World War II. During the war, U.S. and Japanese military forces built airstrips and supply facilities on Pacific islands. Local populations observed that the construction of runways, control towers, and radio equipment preceded the arrival of aircraft loaded with extraordinary goods — food, tools, medicine. After the war, when military operations ceased, some islander communities began constructing imitation runways, wooden control towers, and bamboo radio equipment, hoping to summon the cargo that had previously arrived.
They copied the visible form of the practices without understanding the causal mechanism (a global logistics network and military operations) those practices were embedded in. The imitations looked right but could not produce the outcome. Richard Feynman popularized the term "cargo cult science" in his 1974 Caltech commencement address to describe scientific-seeming investigations that copied the outward form of scientific method without its essential epistemic commitments.
Business organizations do exactly this with management frameworks:
Companies adopt OKRs because Google uses them, without understanding that OKRs work at Google partly because of Google's specific culture of radical transparency and high autonomy. Applied to hierarchical cultures where employees are not empowered to set their own goals meaningfully, OKRs become a rebranded performance review system. Christina Wodtke, in Radical Focus (2016), notes explicitly that OKRs fail in cultures where admitting you did not hit a target carries significant career risk — which is most corporate cultures.
Companies adopt agile ceremonies — standups, retrospectives, sprint planning — without changing their decision-making authority, staffing models, or product vision processes. The ceremonies happen; the software development improvements do not. Ron Jeffries, one of the original signatories of the Agile Manifesto, has written extensively about "Dark Agile" — the widespread practice of adopting agile vocabulary and ceremonies while preserving waterfall decision structures and command-and-control management.
Companies implement design thinking workshops for innovation without the operational follow-through, resource allocation, and risk tolerance that convert prototype insights into shipped products. The workshops feel innovative; the products do not change. Roger Martin, who wrote extensively about integrative thinking and design, observed in a 2019 interview that design thinking had become so broadly adopted that the term had largely been emptied of its original meaning.
In each case, the visible practices are adopted and the underlying logic is not, so the outcomes the framework was designed to produce do not materialize.
How to Evaluate a New Framework
When a new framework comes to your attention and you are considering adopting it, a rigorous evaluation asks:
1. What specific problem was this designed to solve? Every framework has an original problem. Understand it. Does your situation share the key characteristics of that original problem? The more specifically you can match the framework's origin context to your current context, the more reliably the framework will perform.
2. What evidence exists that it works? Are the supporting case studies cherry-picked successes, or is there systematic evidence of performance differences? Who funded the research? Are there documented failures? Tom Peters and Robert Waterman's In Search of Excellence (1982) identified 43 "excellent" companies through a framework-based analysis; within a decade, a third had become significantly less excellent, raising serious questions about the framework's predictive validity.
3. What assumptions does it embed? What does the framework assume to be true about the environment, the actors, the information available, and the relationships between variables? Which of those assumptions hold in your context?
4. What does it deliberately exclude? Every framework simplifies. What does this framework treat as unimportant? Are those things actually unimportant in your situation? This is often the most valuable question, because the excluded variables are precisely the ones that will not be considered if the framework dominates the analysis.
5. What would success look like? Can you articulate a clear causal path from applying this framework to better decisions or outcomes? If the pathway is vague, the framework is unlikely to produce measurable value.
6. Who is promoting it and why? Frameworks promoted by consultants who charge for implementation, authors selling books, and software companies building tools around them are subject to significant commercial interests. That does not make them wrong, but it means the evidence for their effectiveness has been curated by motivated parties. Phil Rosenzweig's The Halo Effect (2007) documents how business case studies systematically attribute success to the management practices being studied, while ignoring the role of luck, industry conditions, and survivorship bias.
A Framework for Using Frameworks
The following is a simplified decision process for framework use:
| Situation | Recommended Approach |
|---|---|
| Unfamiliar domain, low stakes | Apply established framework to structure initial thinking |
| Unfamiliar domain, high stakes | Use framework to orient, then pressure-test assumptions with first principles |
| Familiar domain, standard situation | Apply established framework as checklist, skip confirmed irrelevant steps |
| Familiar domain, novel situation | Set aside frameworks, reason from first principles, build new framework if pattern recurs |
| Group with mixed expertise | Framework as shared vocabulary; let experts modify where they have grounds to |
| Time pressure | Framework as rapid structure; acknowledge simplifications made |
| Evaluating a claim built on a framework | Audit the framework's assumptions before accepting the conclusion |
The Relationship Between Frameworks and Expertise
There is a developmental trajectory in how experts relate to frameworks, described in part by Stuart Dreyfus and Hubert Dreyfus's influential 1980 model of skill acquisition:
Novice stage: Frameworks provide essential scaffolding. Without them, beginners overlook critical considerations and get lost in complexity. Rules and procedures are followed explicitly.
Competent stage: Frameworks are applied consistently. The practitioner has enough experience to apply the framework correctly but not enough to know when to deviate. This stage can produce confident misapplication — the practitioner knows the framework well and applies it in situations where a more experienced person would recognize its limitations.
Proficient stage: The practitioner begins to see situations holistically rather than through the framework's categories. They perceive when a situation fits the framework and when it does not. Frameworks are applied with increasing judgment about their fit.
Expert stage: Frameworks become one tool among many. The expert applies frameworks when they fit, modifies them when they partially fit, and sets them aside when they do not. The expert's judgment about which situation is which is the expertise.
Master stage: Frameworks are internalized. The master may not consciously think in framework terms but implicitly considers the same factors the framework would highlight. They can also construct new frameworks when facing genuinely novel problems, which is how new frameworks enter the ecosystem in Phase 1.
The danger of framework-heavy organizations is that they prevent experts from operating as experts. When applying the prescribed framework is expected regardless of context, expert judgment — the most valuable professional asset — is systematically devalued. Worse, expertise is made invisible: the novice who applies the framework correctly looks the same as the expert who would have applied it correctly, modified it appropriately, or set it aside entirely.
Framework Pluralism vs. Framework Loyalty
A practical question for anyone building expertise in a domain is whether to develop deep mastery of one framework or broad familiarity with many. The research suggests that framework pluralism — holding multiple models and knowing when to apply each — produces better thinking than deep commitment to any single framework.
Charlie Munger, Warren Buffett's longtime business partner, articulated this principle in a series of talks and letters under the label of "mental models." His argument is that a toolkit of perhaps 80-100 mental models from multiple disciplines — economics, psychology, physics, biology, statistics — gives you the ability to approach any problem from multiple angles simultaneously. Where two or more mental models converge on the same conclusion, you have stronger grounds for confidence than any single model could provide.
The limits of this approach are real: shallow familiarity with many frameworks can produce the illusion of analytical power without its substance. A person who has read a summary of 50 frameworks but has never applied any of them in a consequential situation has not developed expertise — they have accumulated vocabulary. The Munger model works because he applied these frameworks through decades of consequential investment decisions, not because he read about them.
The resolution is to develop deep competence in a small number of frameworks highly relevant to your domain, while maintaining working familiarity with a broader set from adjacent disciplines. This combination enables both the reliable application of well-understood tools and the lateral thinking that comes from exposure to different analytical traditions.
Conclusion
Frameworks are powerful tools for efficient thinking in familiar problem domains, for aligning groups around shared vocabulary, and for helping beginners benefit from the codified experience of practitioners who have faced similar challenges. They are worth learning, worth applying, and worth teaching.
They are not universal solutions. They are not substitutes for understanding your specific situation. They are not automatically transferable from the context in which they were validated to any context that superficially resembles it.
The best thinkers know many frameworks well enough to apply them quickly and modify them appropriately. They also know enough about their specific situations to recognize when a framework is helping and when it is an obstacle — and they have the intellectual confidence to set it aside when that is the more rigorous choice.
A framework, at its best, is compressed wisdom made portable. At its worst, it is a cognitive cage that produces the appearance of analysis while blocking genuine understanding. The difference lies not in the framework itself but in the practitioner's relationship to it: whether they hold it loosely enough to question it, modify it, and abandon it when the situation demands.
A framework is a tool. The question is always whether it is the right tool for this specific job. Treating it as more than that is how frameworks become prisons.
Frequently Asked Questions
What is a framework in thinking and decision-making?
A framework is a structured set of concepts, categories, or principles that organizes thinking about a problem domain. Frameworks do not tell you what to do in a specific situation; they tell you what to consider, how to structure the problem, and which relationships are likely to matter. Examples include the BCG Growth-Share Matrix for portfolio strategy, the PDCA cycle for continuous improvement, and the Jobs-to-be-Done framework for product development.
When should you use a framework instead of thinking from scratch?
Frameworks are most valuable when you are in an unfamiliar domain where you have not yet built intuition, when working in a group that needs shared language and structure, when time pressure requires efficient rather than exhaustive analysis, or when you want to avoid forgetting important considerations. A good framework is essentially codified experience — the distilled pattern-recognition of people who have faced similar problems before.
What is cargo cult framework adoption?
Cargo cult adoption refers to copying the visible practices of a framework without understanding the underlying logic those practices serve. The term comes from post-WWII Pacific islanders who mimicked the rituals associated with military cargo deliveries hoping to summon the goods. In business, it manifests as companies adopting OKRs, agile ceremonies, or design thinking workshops because successful companies use them — without understanding why those practices work in specific contexts, which means they rarely transfer the underlying benefits.
What are the signs that a framework is not working for your situation?
Warning signs include: the framework's categories force-fit your actual situation awkwardly; discussions about the framework itself consume more time than discussions about the underlying problem; people use the framework's language to avoid rather than enable direct thinking; the framework was designed for conditions (company size, industry, era) significantly different from yours; or following the framework's prescriptions consistently produces recommendations that feel obviously wrong.
How do you evaluate whether a new framework is worth adopting?
Evaluate a framework by asking: What problem was it designed to solve, and is that my problem? What evidence exists that it works (case studies, research, track record)? What assumptions does it embed, and do those assumptions hold in my context? What does it deliberately ignore or simplify? Can I trace a clear path from using this framework to better decisions or outcomes? Frameworks that cannot answer these questions clearly are likely to become cargo cult practices.