Strategy Framework Decision Map: Which Framework for Which Decision (2026)

Most people pick a strategy framework by name recognition — they reach for SWOT or Porter's Five Forces because those are the ones they remember, not because they fit the decision in front of them. That's backwards. The right starting point is the decision, not the framework.

This page maps the decision to the framework. It's built from our library of 30+ framework guides and nine head-to-head comparisons, so every recommendation links to a full explanation and, where two frameworks compete, to the head-to-head that settles it.

The Framework Decision Map

Find your decision in the left column; the framework on the right is the default starting point.

If you're trying to…	Use	And when it's close, compare
Order a backlog you can quantify	RICE	RICE vs ICE · RICE vs MoSCoW · RICE vs WSJF
Triage your own week	Eisenhower Matrix	—
Scan the macro environment	PESTEL	SWOT vs PESTLE · PESTEL vs Five Forces
Analyze an industry's structure	Porter's Five Forces	SWOT vs Five Forces
Assess a specific position	SWOT	SWOT vs Five Forces
Pick a growth path	Ansoff Matrix · BCG Matrix	Tesla Ansoff worked example
Understand what customers actually want	Jobs-to-be-Done	JTBD vs Personas
Surface what could kill a launch	Premortem	Premortem vs Postmortem
Decide how to decide (ordered vs complex)	Cynefin	—
Set quarterly goals vs track health	OKRs vs KPIs	—
Diagnose an org / post-merger fit	McKinsey 7S	—
Design or pivot a business model	Lean Canvas	Lean Canvas vs Business Model Canvas
Find the root cause of a problem	5 Whys · Pareto 80/20	—
Break an assumption-bound problem	First Principles · Reverse Brainstorming	—

Running a SWOT specifically? Our sister tool SWOTPal is the dedicated AI SWOT generator — free, no signup.

The Deciding-Axis Table

Here's the synthesis you won't find elsewhere: across our nine head-to-head comparisons, the choice between two similar frameworks almost never depends on the whole framework — it collapses to one deciding variable. Memorize the axis and you've memorized the choice.

When you're torn between…	The choice collapses to one question
RICE vs ICE	Is Reach knowable? Yes → RICE; no → ICE
RICE vs WSJF	Does delay have a cost? Yes → WSJF; no → RICE
RICE vs MoSCoW	Do you need a ranked order or just scope buckets? Order → RICE; scope → MoSCoW
Eisenhower vs RICE	Is the bottleneck your week or the team's roadmap? Yours → Eisenhower; team's → RICE
SWOT vs PESTLE	Specific position or macro environment? Position → SWOT; macro → PESTLE
SWOT vs Five Forces	Your situation or the industry's structure? Yours → SWOT; industry → Five Forces
PESTEL vs Five Forces	The whole market's weather or one industry's competitive ring? Market → PESTEL; industry → Five Forces
JTBD vs Personas	Do you need the job customers hire you for or a profile of who they are? Job → JTBD; profile → Personas
Premortem vs Postmortem	Are you before the decision or after the outcome? Before → Premortem; after → Postmortem

The pattern underneath all nine: similar-looking frameworks differ on a single axis — radius (macro vs micro), timing (before vs after), or unit (job vs person, order vs bucket). When two frameworks feel interchangeable, find the axis they disagree on; that axis is your decision.

How the jobs group

If the map is too granular, here are the five jobs every framework above does, in plain terms:

• Generate the options — what could we do? → SWOT, PESTEL, Five Forces, Ansoff, Blue Ocean
• Understand the customer — what do they actually need? → Jobs-to-be-Done
• Order the work — what do we do first? → RICE, Eisenhower, MoSCoW, WSJF
• De-risk the call — what could go wrong, and how do we even decide? → Premortem, Cynefin
• Set and track the target — what are we aiming at? → OKRs vs KPIs

A complete strategic cycle usually runs left to right: generate options, understand the customer, order the work, de-risk it, set the target. Reaching for an "order the work" tool (RICE) when you haven't done the "generate the options" job (SWOT/Five Forces) is the single most common framework mistake — you end up precisely ranking the wrong list.

When frameworks chain

The map's rightmost column hints at it, but the highest-leverage move is sequencing frameworks, not picking one:

• Market entry: PESTEL → Porter's Five Forces → SWOT — macro weather, then the industry ring, then your position inside it.
• Roadmap planning: Jobs-to-be-Done → RICE — clarify the demand, then rank the bets against it.
• Risky launch: Premortem → OKRs — surface what could fail, then set targets that account for it.

For worked, company-grounded chains, see the Decision Center and examples like the Tesla Ansoff Matrix and Nvidia BCG Matrix.

Use any of these on your phone

Want to fill in any framework with AI assistance? Framework List for iPhone & iPad — every framework on this map, guided. Free to start.

How this map was built

This isn't a generic listicle — every recommendation and every deciding axis is drawn from a full guide on this site, and the Deciding-Axis Table is a direct synthesis of our nine published head-to-head comparisons (linked inline above). When you disagree with a call, follow the link and check our reasoning against yours; the comparisons show the full trade-off, not just the verdict.