Most strategy decks are built for the Fortune 500. Here are the five frameworks that survive contact with a 40-person company — and the ones to throw out.

The consulting industry has a dirty secret: most of its most celebrated frameworks were developed in, refined for, and validated against large enterprises. McKinsey’s 7-S model was popularized through research on Fortune 500 companies. Porter’s Five Forces was drawn from industries with defined competitive landscapes and measurable market share. The Balanced Scorecard emerged from work with Rockwater and Apple — not a 35-person professional services firm trying to figure out whether to hire a VP of Sales.

When SMB operators apply enterprise frameworks wholesale, they frequently get two outcomes: either the framework is too abstract to generate actionable decisions, or it produces analysis paralysis because the business lacks the data infrastructure the framework assumes.

This is not a failure of the frameworks. It is a failure of translation.

The Five That Transfer

1. Jobs to Be Done (JTBD)

Clayton Christensen’s framework — understanding what “job” a customer is “hiring” a product or service to do — transfers to SMBs almost perfectly because it requires no market data infrastructure, no competitive intelligence function, and no brand research budget. It requires conversations.

For a 40-person professional services firm, JTBD translates into a single discipline: talk to your last twelve clients who renewed and your last twelve who didn’t. Ask the same question to both groups: “What were you hoping we would help you accomplish that you couldn’t or wouldn’t do internally?” The gap between those two sets of answers is your strategy.

JTBD works at SMB scale because the data collection mechanism matches the business’s actual capacity.

2. The One Metric That Matters (OMTM)

Popularized in the lean startup movement, the OMTM discipline — identifying the single metric that best captures whether the business is moving in the right direction and subordinating other decisions to it — is arguably more valuable at SMB scale than enterprise scale.

Large companies can afford to track dozens of KPIs across functions, average out local optimization failures, and course-correct quarterly. A 40-person company operating on a 90-day cash horizon cannot. The OMTM framework forces the discipline of deciding what actually matters before you’re in a position where everything feels like it matters equally.

The common failure mode: companies pick an activity metric (calls made, proposals sent) rather than an outcome metric (qualified pipeline created, close rate on proposals over $50K). Choose the outcome.

3. The Value Chain Analysis

Porter’s full competitive strategy framework is largely untranslatable to SMBs. But the Value Chain Analysis — the exercise of mapping every activity the business performs and asking which create value for the customer and which merely exist because “that’s how we do it” — transfers cleanly.

At SMB scale, value chain analysis typically reveals two things: activities that consume significant labor and budget that customers do not value and would not pay for, and activities that customers would pay more for if they were executed more consistently or more visibly.

The ROI on a well-facilitated value chain session — two to four hours with the leadership team — is almost always positive within 90 days.

4. The Ansoff Matrix

Growth strategy distilled to a 2x2: existing products vs. new products, existing markets vs. new markets. Market penetration, market development, product development, diversification.

The Ansoff Matrix works for SMBs because it forces a conversation that most small companies avoid: are we growing by doing more of what we already do, or are we growing by doing something different? Those are fundamentally different resource allocation questions, and they require different organizational investments.

Most SMBs discover, when they map their actual growth activities against the matrix, that they are simultaneously pursuing market penetration and product development with the same under-resourced team. The matrix makes the cost of that choice visible.

5. Wardley Mapping (Situational Awareness)

The most underused framework on this list. Simon Wardley’s mapping methodology — plotting business activities along two axes (value chain position and evolutionary stage) — is particularly useful for companies making technology investment decisions.

For an SMB deciding whether to build custom software, license an enterprise platform, or use a commoditized SaaS tool, Wardley Mapping provides a principled basis for that decision. Activities in the “commodity” or “utility” stage of evolution are almost never worth building. Activities in the “genesis” or “custom” stage may be genuine competitive differentiators worth investing in.

The full methodology has a steep learning curve, but the core insight — that you should buy what is commodity and invest in what is genuinely differentiating — is actionable without mastering the entire framework.

The Ones to Leave Behind

OKRs at fewer than 50 people. The coordination overhead of a formal OKR process at sub-50 headcount almost always exceeds its value. If the leadership team can have a single conversation about what matters this quarter, an OKR process is a bureaucratic substitute for that conversation.

Net Promoter Score as a strategy input. NPS is a survey instrument. It tells you whether customers would recommend you. It does not tell you why, or what to do differently. Using NPS as a strategic KPI is using a speedometer as a navigation system.

The Business Model Canvas for execution. The Canvas is an excellent tool for articulating a business model concept to investors, partners, or new employees. It is a poor tool for execution planning, because it does not surface the sequencing, resource requirements, or dependencies that determine whether a business model can actually be implemented.

The Framework Selection Framework

The highest-order question to ask before applying any strategic framework to an SMB context: does this framework require data, infrastructure, or organizational capacity that this business does not currently have and is not planning to build?

If the answer is yes, either build what the framework requires or find a simpler framework that works with what you have.

Strategy that requires better data than you possess produces better-looking analysis than you can act on. That is not strategy. That is decoration.