In almost every business course, frameworks arrive with a kind of implicit authority. Porter's Five Forces. The BCG Matrix. SWOT. McKinsey's 7-S. They're taught as if applying them correctly produces insight, like a formula that outputs an answer when you fill in the variables.
I've come to believe that framing is backwards. Frameworks are not answer machines. They are thinking aids — scaffolding that helps you structure observation and conversation. The mistake isn't learning them. The mistake is trusting them to replace judgment.
What frameworks actually do well
Before I critique them, let me be fair about what they genuinely do well. A good framework forces completeness. SWOT analysis, for all its simplicity, stops a team from only talking about strengths and ignoring threats. The Five Forces stops strategists from only thinking about direct competitors and forces them to consider suppliers, buyers, substitutes, and new entrants.
That's real value. In a two-hour strategy session with a roomful of senior people, a framework is an agenda — a guarantee that certain questions get raised even if no one naturally thinks to raise them. That's not nothing. That's actually quite useful.
Frameworks also create shared vocabulary. When everyone on a team knows what "threat of substitution" means in the Porter sense, you can have faster, more precise conversations. The framework is a compression algorithm for accumulated strategic thinking. Why reinvent that vocabulary every time?
Where they fail
The failure mode is when the framework becomes the output rather than the input to thinking. I've sat in presentations where a team had done a thorough Five Forces analysis — rated each force as high, medium, or low — and declared the analysis done. Competitive rivalry: high. Threat of new entrants: medium. Bargaining power of suppliers: low. And… what does that tell us to do?
Nothing. The framework organized the landscape. It didn't tell you whether to enter the market, which segment to target, what capability to build, or where to price. Those decisions require judgment, contextual knowledge, and often empirical testing. The framework can't substitute for any of that.
SWOT is perhaps the most abused. It becomes a brainstorming exercise that produces a four-quadrant list of things people already knew, followed by a recommendation that conveniently favors whatever the team was already planning to do. The framework provided a surface of analytical legitimacy for a conclusion that was predetermined.
The 5-Whys problem
The 5-Whys is a root cause analysis technique from lean manufacturing. You ask "why" five times in succession to drill down from a symptom to a root cause. It's powerful in controlled manufacturing environments where cause-and-effect relationships are relatively deterministic.
In complex business or product contexts, it's often misleading. The chain of "whys" is not objectively determined — it reflects the mental model of whoever is answering. Two analysts can apply 5-Whys to the same problem and arrive at completely different root causes, both logically consistent, neither objectively correct. The framework gives the process a feeling of rigor without actually providing it.
This doesn't mean root cause analysis is useless — it means the tool doesn't substitute for domain expertise, empirical data, and genuine intellectual humility about how much you can know from reasoning alone.
How I use frameworks now
I still use frameworks. All the time. But I treat them as starting points and conversation anchors, not endpoints.
My process: apply the framework to surface the questions, then answer those questions with data and domain knowledge. SWOT gives me a list of questions. What are the actual threats? How material are they, and over what time horizon? What's the evidence? The SWOT boxes are headers, not conclusions.
I also try to be conscious of what each framework was designed for and where it breaks down. Porter's Five Forces was designed for industry-level competitive analysis of relatively stable markets. It was not designed for platform businesses, two-sided markets, or fast-moving technology sectors where the competitive set can change in eighteen months. Using it uncritically in those contexts can actively mislead.
The deeper lesson
The real skill in business analysis isn't knowing frameworks — it's knowing when to apply which framework, what questions it's good at surfacing, what it systematically misses, and when to set it aside entirely and reason from first principles.
That skill is harder to teach and harder to demonstrate on a slide deck. It accumulates through practice, through seeing frameworks misapplied, through watching smart people reach wrong conclusions because they trusted the structure of an analysis more than its substance.
Use frameworks. Learn them well. But wear them lightly. The scaffold is not the building.