# Framework — full content

> Inline content for the 100+ thinking frameworks, Academy guides, Blog posts, Examples, Compare entries, help articles, and Glossary terms. Use llms.txt for a links-only index.

## Frameworks

### 10/10/10 Rule
URL: https://frameworklist.com/frameworks/tententen
Category: decision

Implications in 10 min, 10 mo, 10 yr

**Best for:** Cool a hot decision

**When to use it.** Hot decisions where emotion is dominating reason — text, emails, conflicts.

**Why it works.** Time-shift breaks emotional grip; what feels existential now usually doesn't survive 10 months.

Source: Suzy Welch, “10-10-10” · 2009

---

### 12 Week Year
URL: https://frameworklist.com/frameworks/twelveweek
Category: goals

Treat each quarter as a year

**Best for:** Compress focus and execute

**When to use it.** Personal or small-team execution — compresses focus into a quarterly sprint.

**Why it works.** Quarterly cycles match human attention better than annual ones — execution stays urgent.

Source: Brian Moran & Michael Lennington · 2013

---

### 5 Whys
URL: https://frameworklist.com/frameworks/fivewhys
Category: root-cause

Ask why five times

**Best for:** Find the real root cause

**When to use it.** Operational problems — when symptoms keep recurring and you suspect a deeper cause.

**Why it works.** Forces causal depth past the first plausible answer; each 'why' usually surfaces something you'd otherwise miss.

Source: Sakichi Toyoda, Toyota Production System · 1930s

---

### 80/20 Life
URL: https://frameworklist.com/frameworks/eightytwentylife
Category: life

Which 20% drives 80% of life joy?

**Best for:** Audit time and relationships

**When to use it.** Personal time / relationship audit — which 20% of activity drives 80% of joy?

**Why it works.** Pareto applied to life often produces shockingly clear cuts; many activities can be dropped without loss.

Source: Pareto Principle, applied to life

---

### A3 Problem Solving
URL: https://frameworklist.com/frameworks/a3
Category: root-cause

One-page Toyota problem report

**Best for:** Structure root-cause work

**When to use it.** Toyota-style problem reports — one-page structured root cause + countermeasures + plan.

**Why it works.** One-page constraint forces clarity; if it doesn't fit, the analysis isn't done.

Source: Toyota Production System

---

### AIDA
URL: https://frameworklist.com/frameworks/aida
Category: communication

Attention, Interest, Desire, Action

**Best for:** Write persuasive copy

**When to use it.** Persuasive copy — landing pages, ads, sales emails — guides reader from attention to action.

**Why it works.** Maps to natural buyer psychology; ignoring any of the four steps usually loses the reader.

Source: E. St. Elmo Lewis · 1898

---

### Ansoff Matrix
URL: https://frameworklist.com/frameworks/ansoff
Category: strategy

Product × market growth options

**Best for:** Choose a growth direction

**When to use it.** Choosing a growth direction — penetrate the existing market, develop new products, enter new markets, or diversify.

**Why it works.** Names the four growth options explicitly so a team isn't unconsciously defaulting to one.

Source: Igor Ansoff, HBR · 1957

---

### Antifragility
URL: https://frameworklist.com/frameworks/antifragility
Category: mental-model

Some things gain from disorder

**Best for:** Design systems that grow under stress

**When to use it.** Designing systems and habits — make them gain (not just survive) under stress and disorder.

**Why it works.** Robustness avoids harm; antifragility extracts gain from the same disorder.

Source: Nassim Taleb, “Antifragile” · 2012

---

### Balanced Scorecard
URL: https://frameworklist.com/frameworks/balancedscorecard
Category: strategy

Financial, customer, internal, learning

**Best for:** Translate strategy into measures

**When to use it.** Translating strategy into measurable KPIs across financial, customer, process, and learning lenses.

**Why it works.** Resists vanity-metric drift by forcing 4 perspectives into the scorecard.

Source: Kaplan & Norton, HBR · 1992

---

### BCG Matrix
URL: https://frameworklist.com/frameworks/bcg
Category: strategy

Growth-share quadrants: stars, cows, dogs, question marks

**Best for:** Allocate across a portfolio

**When to use it.** Allocating capital across a multi-product portfolio when growth and market share differ across the lineup.

**Why it works.** Visual at-a-glance portfolio status; pushes you to fund stars, milk cash cows, and confront dogs.

Source: Bruce Henderson, BCG · 1970

---

### BHAG
URL: https://frameworklist.com/frameworks/bhag
Category: goals

Big Hairy Audacious Goal

**Best for:** Set a 10-year stretch goal

**When to use it.** Setting a 10-year stretch goal that forces strategy choices — only when leadership is ready to commit.

**Why it works.** 10-year framing forces honest strategy choices; most plans die because the goal was never that big.

Source: Jim Collins & Jerry Porras, “Built to Last” · 1994

---

### Black Swan Analysis
URL: https://frameworklist.com/frameworks/blackswan
Category: risk

Surface unknown-unknowns

**Best for:** Probe extreme rare events

**When to use it.** Stress-testing assumptions for catastrophic outliers your normal planning won't catch.

**Why it works.** Counterweight to base-rate thinking; reminds you that the worst events are often the unlisted ones.

Source: Nassim Taleb, “The Black Swan” · 2007

---

### Blue Ocean Strategy
URL: https://frameworklist.com/frameworks/blueocean
Category: strategy

Eliminate, reduce, raise, create

**Best for:** Find uncontested market space

**When to use it.** When a market is overcrowded and you want to redefine the value curve instead of beating competitors at their game.

**Why it works.** Forces value-curve thinking instead of incremental competition; the ERRC grid is concrete and testable.

Source: W. Chan Kim & Renée Mauborgne · 2005

---

### BLUF
URL: https://frameworklist.com/frameworks/bluf
Category: communication

Bottom Line Up Front

**Best for:** Lead with the answer

**When to use it.** Internal communication — Slack updates, status emails, leadership briefings.

**Why it works.** First-line answer shifts the workload from reader to writer, which is the right place for it.

Source: US Army, Field Manual · 1980s

---

### Bowtie Analysis
URL: https://frameworklist.com/frameworks/bowtie
Category: risk

Causes → event → consequences

**Best for:** Map preventions and mitigations

**When to use it.** Mapping causes, controls, and consequences around a critical risk event — common in safety-critical industries.

**Why it works.** Single picture of preventions, the event itself, and mitigations — rare clarity for risk reviews.

Source: Royal Dutch Shell · 1970s

---

### Build–Measure–Learn
URL: https://frameworklist.com/frameworks/bml
Category: business

Lean Startup feedback loop

**Best for:** Iterate toward validated learning

**When to use it.** Lean Startup product loops — validate riskiest assumptions with the smallest experiment.

**Why it works.** Tightens experiment cycles to the smallest learning unit; reduces capital burned per insight.

Source: Eric Ries, “The Lean Startup” · 2011

---

### Business Model Canvas
URL: https://frameworklist.com/frameworks/bmc
Category: business

Customers, value, channels, costs, revenue

**Best for:** Map a full business model

**When to use it.** Mapping a full business model on one page — useful for established businesses or teams aligning.

**Why it works.** Whole business on one page; gaps and inconsistencies between blocks become visible immediately.

Source: Alexander Osterwalder & Yves Pigneur · 2008

---

### Buy a Feature
URL: https://frameworklist.com/frameworks/buyfeature
Category: prioritization

Give users virtual money to spend

**Best for:** Surface real willingness to pay

**When to use it.** User research on willingness to pay — give participants virtual money to allocate to features.

**Why it works.** Real revealed preference data instead of stated preference, which lies in surveys.

Source: Luke Hohmann, “Innovation Games” · 2006

---

### Chesterton's Fence
URL: https://frameworklist.com/frameworks/chesterton
Category: mental-model

Don't remove what you don't understand

**Best for:** Pause before the rewrite

**When to use it.** Before removing or refactoring something — understand why it exists in the first place.

**Why it works.** Most fences are there for a reason that's not visible from where you're standing.

Source: G.K. Chesterton, “The Thing” · 1929

---

### Circle of Competence
URL: https://frameworklist.com/frameworks/circlecompetence
Category: mental-model

Know what you know — and don't

**Best for:** Stay inside your edge

**When to use it.** Knowing what's inside vs. outside your edge — stops you faking expertise you don't have.

**Why it works.** Acknowledging limits is rare and valuable; pretending breadth is how big mistakes get made.

Source: Warren Buffett & Charlie Munger

---

### Compounding
URL: https://frameworklist.com/frameworks/compounding
Category: mental-model

Small returns multiply over time

**Best for:** Choose long-term curves

**When to use it.** Long-term decisions — choose actions whose returns multiply over years vs. linear effort.

**Why it works.** Linear effort, exponential payoff — long-tenure decisions become asymmetric bets.

Source: Often attributed to Albert Einstein; popularized by Munger

---

### Cost-Benefit
URL: https://frameworklist.com/frameworks/costbenefit
Category: decision

Monetize costs vs. benefits over time

**Best for:** Justify or kill an investment

**When to use it.** Investments and projects where you can monetize both costs and benefits over a comparable horizon.

**Why it works.** Common $-denominated language unlocks finance and exec conversations that would otherwise stall.

Source: Jules Dupuit · 1848

---

### Crazy Eights
URL: https://frameworklist.com/frameworks/crazyeights
Category: innovation

8 sketches in 8 minutes

**Best for:** Force quantity over polish

**When to use it.** Forcing quantity in early ideation — 8 sketches in 8 minutes kills self-censorship.

**Why it works.** Time pressure kills self-editing; quantity of options outperforms quality at this stage.

Source: Jake Knapp, Google Ventures “Sprint” · 2016

---

### Current Reality Tree
URL: https://frameworklist.com/frameworks/currentreality
Category: root-cause

Logical tree of undesirable effects

**Best for:** Find the few core problems

**When to use it.** Theory-of-Constraints diagnosis — finding the few core problems behind many surface symptoms.

**Why it works.** Distinguishes core problems from symptoms — most teams fix many symptoms instead of one core.

Source: Eliyahu Goldratt, Theory of Constraints · 1984

---

### Customer Journey Map
URL: https://frameworklist.com/frameworks/journeymap
Category: business

Stages × actions × thoughts × pains

**Best for:** Find the broken touchpoints

**When to use it.** Service design — finding broken or surprising touchpoints in a multi-step customer journey.

**Why it works.** Multi-touchpoint visualization reveals friction at the seams between teams and steps.

Source: Service design tradition (Marc Stickdorn et al.)

---

### Cynefin Framework
URL: https://frameworklist.com/frameworks/cynefin
Category: decision

Clear, complicated, complex, chaotic, confused

**Best for:** Match approach to context

**When to use it.** Choosing the right approach for the situation — best practice, expert analysis, experiment, or stabilize-first.

**Why it works.** Stops you applying best-practice playbooks to genuinely complex situations.

Source: Dave Snowden, IBM · 1999

---

### DACI
URL: https://frameworklist.com/frameworks/daci
Category: decision

Driver, Approver, Contributor, Informed

**Best for:** Clarify decision roles

**When to use it.** Ambiguous decisions where it's unclear who decides, who informs, and who's just along for the ride.

**Why it works.** Cuts decision latency — most slow decisions are slow because no one knows who decides.

Source: Intuit · 2000s

---

### Decision Matrix
URL: https://frameworklist.com/frameworks/decmatrix
Category: decision

Options scored across criteria

**Best for:** Compare more than 2 options

**When to use it.** Comparing more than 2 options across multiple criteria — vendor selection, hiring, location decisions.

**Why it works.** Removes hidden criteria — what felt 'gut' becomes a defensible scored comparison.

Source: Stuart Pugh · 1981

---

### Decision Tree
URL: https://frameworklist.com/frameworks/tree
Category: decision

Branching outcomes and probabilities

**Best for:** Evaluate branching choices

**When to use it.** Branching choices with probabilistic outcomes — investments, build vs. buy, partner selection.

**Why it works.** Visualizes branching outcomes and forces probabilities to be made explicit.

Source: Operations research · 1950s

---

### Design Thinking
URL: https://frameworklist.com/frameworks/designthinking
Category: innovation

Empathize, define, ideate, prototype, test

**Best for:** Solve human-centered problems

**When to use it.** Solving human-centered problems where empathy and prototyping matter more than analysis.

**Why it works.** Empathy stage prevents premature solutioning; prototype + test stage prevents over-investment in untested ideas.

Source: IDEO / Stanford d.school · 2000s

---

### Designing Your Life
URL: https://frameworklist.com/frameworks/designingyourlife
Category: life

Prototype 3 alternative life paths

**Best for:** Choose with evidence, not theory

**When to use it.** Major life inflection points — instead of choosing one path, prototype several lives in parallel.

**Why it works.** Multiple prototypes reduce path-dependency; you can drop a life cheaply if you only invested 3 months.

Source: Bill Burnett & Dave Evans, Stanford · 2016

---

### Dichotomy of Control
URL: https://frameworklist.com/frameworks/dichotomy
Category: life

What you control vs. what you don't

**Best for:** Stop spending energy on noise

**When to use it.** Anxiety relief and energy allocation — separates what's worth your worry from what isn't.

**Why it works.** Stoic principle that has survived 1,900 years; energy spent on uncontrollable stuff is energy lost.

Source: Epictetus, “Enchiridion” · ~108 AD

---

### DMAIC
URL: https://frameworklist.com/frameworks/dmaic
Category: root-cause

Define, Measure, Analyze, Improve, Control

**Best for:** Six Sigma improvement loop

**When to use it.** Six Sigma and process improvement — when you need a measurable, controlled improvement loop.

**Why it works.** Measurement-led — improvements are tied to data, not opinion, which makes them durable.

Source: Six Sigma / Motorola · 1986

---

### Double Diamond
URL: https://frameworklist.com/frameworks/doublediamond
Category: innovation

Discover · Define · Develop · Deliver

**Best for:** Diverge then converge, twice

**When to use it.** Design or product projects that need to diverge then converge twice — once on the problem, once on the solution.

**Why it works.** Diverge-converge twice — most teams skip one diamond and end up solving the wrong problem well.

Source: UK Design Council · 2005

---

### Eisenhower Matrix
URL: https://frameworklist.com/frameworks/eisenhower
Category: prioritization

Urgent vs. important, four quadrants

**Best for:** Decide what to do now, later, delegate, drop

**When to use it.** Personal or team prioritization when urgency and importance are getting confused — clarifies what to do, schedule, delegate, or drop.

**Why it works.** Trades vague stress for explicit categories; what looked urgent often falls into delegate or drop.

Source: Dwight D. Eisenhower; popularized by Stephen Covey · 1989

---

### Empathy Map
URL: https://frameworklist.com/frameworks/empathymap
Category: business

Says, thinks, feels, does

**Best for:** Build a shared user portrait

**When to use it.** Building shared understanding of a target user across a team — feeds into design and copy.

**Why it works.** Quadrant structure forces depth on what's said vs. thought vs. felt vs. done — reveals contradictions.

Source: Dave Gray, XPLANE · 2008

---

### Energy Audit
URL: https://frameworklist.com/frameworks/energyaudit
Category: life

Track energy gained vs. drained

**Best for:** Redesign your week

**When to use it.** Optimizing your week — which activities energize vs. drain, and how to redesign accordingly.

**Why it works.** Energy is the constraint, not time — auditing it surfaces non-obvious schedule changes.

Source: Tony Schwartz, “Power of Full Engagement” · 2003

---

### Expected Value
URL: https://frameworklist.com/frameworks/expectedvalue
Category: decision

Σ probability × outcome

**Best for:** Choose under uncertainty

**When to use it.** Choosing under uncertainty when you can estimate probabilities and outcome values.

**Why it works.** Forces probabilities to be quantified instead of vibed; reveals when 'safe' choices are bad bets.

Source: Blaise Pascal · 1654

---

### Fault Tree
URL: https://frameworklist.com/frameworks/faulttree
Category: root-cause

AND/OR logic of failure paths

**Best for:** Reliability engineering

**When to use it.** Reliability and safety engineering — formal modeling of system failure paths.

**Why it works.** Probabilistic AND/OR logic catches compound failure paths human intuition routinely misses.

Source: H.A. Watson, Bell Labs · 1962

---

### First Principles
URL: https://frameworklist.com/frameworks/firstprinciples
Category: mental-model

Reduce to atomic truths, rebuild up

**Best for:** Question received wisdom

**When to use it.** When received wisdom or analogy is leading you astray — strip the problem to atoms and rebuild.

**Why it works.** Bypasses analogy and tradition; what survives reduction to atoms is rarely what people defend.

Source: Aristotle, “Posterior Analytics”; popularized by Elon Musk

---

### Fishbone Diagram
URL: https://frameworklist.com/frameworks/fishbone
Category: root-cause

Causes grouped under 6 Ms

**Best for:** Spread the search for causes

**When to use it.** Group problem solving — distributes the search for causes across 6 perspective categories.

**Why it works.** Six-category structure prevents the team from clustering around one favored cause.

Source: Kaoru Ishikawa, Univ. of Tokyo · 1968

---

### Flywheel
URL: https://frameworklist.com/frameworks/flywheel
Category: business

Self-reinforcing loop of growth

**Best for:** Design for compounding

**When to use it.** Strategic growth — designing for compounding loops instead of linear funnels.

**Why it works.** Designs for compounding instead of linear acquisition; loops outperform funnels at scale.

Source: Jim Collins, “Good to Great” · 2001

---

### FMEA
URL: https://frameworklist.com/frameworks/fmea
Category: risk

Failure modes & effects analysis

**Best for:** Engineering risk catalog

**When to use it.** Engineering and operations — surfacing failure modes before they reach customers.

**Why it works.** RPN scoring exposes the failure modes most worth eliminating, even when they're not the most visible.

Source: US Military / aerospace · 1949

---

### GE-McKinsey Matrix
URL: https://frameworklist.com/frameworks/gemckinsey
Category: strategy

Industry attractiveness × business strength

**Best for:** Decide invest, hold, harvest

**When to use it.** Multi-business-unit portfolio decisions where 2×2 BCG is too coarse — adds market attractiveness × business strength.

**Why it works.** More nuanced than BCG with 9-box resolution; better for larger portfolios.

Source: GE / McKinsey · 1970s

---

### Getting Things Done (GTD)
URL: https://frameworklist.com/frameworks/gtd
Category: prioritization

Capture, Clarify, Organize, Reflect, Engage

**Best for:** Manage workflow and reduce mental load

**When to use it.** Personal or team productivity when overwhelm comes from too many open loops — email, ideas, commitments — floating in memory instead of a trusted external system.

**Why it works.** Frees working memory by externalizing commitments; the 5-step workflow handles any input without special-case handling.

Source: David Allen · 2001

---

### GROW Model
URL: https://frameworklist.com/frameworks/grow
Category: goals

Goal, Reality, Options, Will

**Best for:** Coach toward action

**When to use it.** Coaching conversations — moving someone from stuck to action in 15–30 minutes.

**Why it works.** Structure protects coaching from devolving into advice-giving; almost-always ends with a 'will' commitment.

Source: Graham Alexander & John Whitmore · 1980s

---

### Hanlon's Razor
URL: https://frameworklist.com/frameworks/hanlon
Category: mental-model

Don't attribute to malice what stupidity explains

**Best for:** Defuse conflict, find truth

**When to use it.** Conflict de-escalation — assume process failure or oversight before assuming intent.

**Why it works.** Lower stakes by default reduces conflict velocity; usually the right read anyway.

Source: Robert J. Hanlon · 1980 (Murphy's Law book)

---

### Hooked Model
URL: https://frameworklist.com/frameworks/hooked
Category: business

Trigger, action, reward, investment

**Best for:** Design habit-forming products

**When to use it.** Designing habit-forming products — when retention depends on triggered, daily-use loops.

**Why it works.** Names the four loop steps so you can audit which one is missing in a low-retention product.

Source: Nir Eyal, “Hooked” · 2014

---

### How Might We
URL: https://frameworklist.com/frameworks/howmightwe
Category: innovation

Reframe problems as opportunities

**Best for:** Open up possibility space

**When to use it.** Reframing problems as opportunities — opens up the possibility space before narrowing.

**Why it works.** Reframes constraints as openings — the same problem suddenly has 10 angles instead of 1.

Source: Min Basadur · 1970s; popularized by IDEO

---

### ICE Score
URL: https://frameworklist.com/frameworks/ice
Category: prioritization

Impact × Confidence × Ease

**Best for:** Rank growth experiments

**When to use it.** Lightweight ranking of growth experiments where you don't have effort estimates yet.

**Why it works.** Lighter than RICE; good when you'd rather rank 30 things in 30 minutes than 5 things in an hour.

Source: Sean Ellis, GrowthHackers · 2010s

---

### Ikigai
URL: https://frameworklist.com/frameworks/ikigai
Category: life

Love, good at, world needs, paid for

**Best for:** Find purpose at intersection

**When to use it.** Career or life-direction decisions — finding overlap between love, skill, world need, and economic reality.

**Why it works.** Single picture of overlapping life dimensions; clarifies why some 'good' careers feel hollow.

Source: Mieko Kamiya · 1966; 4-circle by Marc Winn · 2014

---

### Jobs to be Done
URL: https://frameworklist.com/frameworks/jtbd
Category: business

Functional, social, emotional jobs

**Best for:** Understand why people hire your product

**When to use it.** Customer interviews — moves the conversation from features to the underlying job customers are hiring for.

**Why it works.** Decouples product from feature; the same job often connects competitors you didn't realize were adjacent.

Source: Clayton Christensen, HBS · 2003

---

### Kano Model
URL: https://frameworklist.com/frameworks/kano
Category: prioritization

Basic, performance, delight features

**Best for:** Tell delighters from must-haves

**When to use it.** Distinguishing must-be features from delighters — useful when customer expectations are non-linear.

**Why it works.** Reveals that not all features are interchangeable — delighters punch above their weight, must-be features punish absence.

Source: Noriaki Kano, Tokyo Univ. of Science · 1984

---

### KPI Tree
URL: https://frameworklist.com/frameworks/kpi
Category: goals

Cascading north-star → input metrics

**Best for:** Connect daily work to outcome

**When to use it.** Connecting strategic outcomes to daily inputs you can actually move — cascades from north star down.

**Why it works.** Cascade makes it impossible to spend a quarter without knowing why each input metric matters.

Source: Performance management standard

---

### Lateral Thinking
URL: https://frameworklist.com/frameworks/lateralthinking
Category: innovation

Provocations to break logic

**Best for:** Escape obvious solutions

**When to use it.** Breaking out of obvious solutions — provocations to escape default thinking.

**Why it works.** Provocations break logical chains your brain has rehearsed too many times.

Source: Edward de Bono · 1967

---

### Lean Canvas
URL: https://frameworklist.com/frameworks/lean
Category: business

One-page business model

**Best for:** Pressure-test a startup idea

**When to use it.** Pressure-testing a startup idea quickly — distilled from BMC for new ventures with unknowns.

**Why it works.** Faster than BMC and tuned to the unknowns of a startup — surfaces riskiest assumptions first.

Source: Ash Maurya, “Running Lean” · 2010

---

### Mandala Chart
URL: https://frameworklist.com/frameworks/mandalachart
Category: goals

One goal, 8 themes, 64 actions

**Best for:** Break one goal into 64 actions

**When to use it.** Turning one large, abstract goal into 64 specific, checkable actions — season plans, annual goals, skill acquisition.

**Why it works.** Forces you past the 8 obvious sub-goals into concrete actions; the grid is full only when every cell is filled, which exposes vague thinking.

Source: Yasuo Matsumura · 1979 (Mandala Chart); Ohtani's sheet is Harada Method OW64

---

### Margin of Safety
URL: https://frameworklist.com/frameworks/marginsafety
Category: mental-model

Build buffer for what you can't predict

**Best for:** Make robust commitments

**When to use it.** Plans and commitments under uncertainty — buffer for what you can't predict.

**Why it works.** Buffer turns 'plan met' from a coin flip into a high-probability outcome.

Source: Benjamin Graham, “Intelligent Investor” · 1949

---

### Maslow's Hierarchy
URL: https://frameworklist.com/frameworks/maslow
Category: life

Physical → safety → love → esteem → self-actualization

**Best for:** Diagnose unmet needs

**When to use it.** Diagnosing motivation problems on yourself or a team — what need is being missed?

**Why it works.** Diagnoses motivation in layers; 'team disengagement' often resolves to a missing belonging or esteem signal.

Source: Abraham Maslow, Psychological Review · 1943

---

### McKinsey 7S
URL: https://frameworklist.com/frameworks/mckinsey7s
Category: strategy

Strategy, Structure, Systems, Skills, Staff, Style, Shared values

**Best for:** Diagnose org alignment

**When to use it.** Diagnosing why a stated strategy is failing in execution — looks at structural and cultural alignment, not just plans.

**Why it works.** Catches misalignment between stated strategy and operational reality — diagnoses why plans don't land.

Source: Tom Peters & Robert Waterman, McKinsey · 1980

---

### Mind Map
URL: https://frameworklist.com/frameworks/mindmap
Category: innovation

Radial branching of associations

**Best for:** Brainstorm and organize

**When to use it.** Brainstorming and organizing — radial structure mirrors how associations naturally work.

**Why it works.** Radial structure scales with ideas without flattening hierarchy — easy to skim and re-enter.

Source: Tony Buzan · 1970s

---

### MoSCoW Method
URL: https://frameworklist.com/frameworks/moscow
Category: prioritization

Must, Should, Could, Won't

**Best for:** Scope a release

**When to use it.** Scoping a release — deciding what's must-have vs. nice-to-have under a deadline.

**Why it works.** Forces explicit Won't decisions, which is where most scoping discipline actually happens.

Source: Dai Clegg, Oracle UK · 1994

---

### North Star Metric
URL: https://frameworklist.com/frameworks/northstar
Category: goals

One metric that captures the value

**Best for:** Align the team on one number

**When to use it.** Aligning a team or company on one outcome metric that captures the value you create.

**Why it works.** One number is alignment leverage — disagreements get clearer when surfaced as proxy metrics.

Source: Sean Ellis, GrowthHackers · 2010s

---

### Occam's Razor
URL: https://frameworklist.com/frameworks/occam
Category: mental-model

Prefer the simplest explanation

**Best for:** Cut through tangled theories

**When to use it.** Diagnosing causes — prefer the simplest explanation that fits the evidence.

**Why it works.** Simplest fitting explanation is usually right; saves hours debating exotic causes.

Source: William of Ockham · 14th century

---

### OKR
URL: https://frameworklist.com/frameworks/okr
Category: goals

Objective + key results

**Best for:** Set measurable quarterly goals

**When to use it.** Setting measurable goals with clear key results — typically quarterly, especially in fast-moving teams.

**Why it works.** Couples ambition (objective) with measurability (KRs) so neither runs without the other.

Source: Andy Grove, Intel · 1970s; John Doerr · 1999

---

### OODA Loop
URL: https://frameworklist.com/frameworks/ooda
Category: decision

Observe, Orient, Decide, Act

**Best for:** Outpace the situation

**When to use it.** Reacting under uncertainty and pressure — competitor moves, incidents, fast-changing markets.

**Why it works.** Speed of iteration > model accuracy in fast environments — OODA bakes that into a loop.

Source: Col. John Boyd, USAF · 1976

---

### Pareto Analysis
URL: https://frameworklist.com/frameworks/pareto
Category: decision

80/20 vital few vs. trivial many

**Best for:** Focus where impact concentrates

**When to use it.** Concentrating effort on the vital few — support tickets, bugs, customers, features that drive 80% of impact.

**Why it works.** Most teams underestimate concentration; the 80/20 cut routinely halves where to focus.

Source: Vilfredo Pareto · 1896

---

### PDCA Cycle
URL: https://frameworklist.com/frameworks/pdca
Category: root-cause

Plan, Do, Check, Act

**Best for:** Iterative improvement

**When to use it.** Iterative improvement of any process — small, frequent cycles of plan-do-check-act.

**Why it works.** Frequent small loops outperform occasional big plans; baked into Toyota's compounding advantage.

Source: Walter Shewhart · 1939; W. Edwards Deming · 1950s

---

### Personal Kanban
URL: https://frameworklist.com/frameworks/kanban
Category: goals

To do · Doing · Done with WIP limits

**Best for:** Visualize and limit work

**When to use it.** Visualizing personal work in flight, especially when context switching is the problem.

**Why it works.** WIP limits make multitasking visible; most personal productivity gains come from simply lowering WIP.

Source: Jim Benson & Tonianne DeMaria Barry · 2011

---

### PESTEL Analysis
URL: https://frameworklist.com/frameworks/pestel
Category: strategy

Political, Economic, Social, Tech, Environmental, Legal

**Best for:** Scan the macro environment

**When to use it.** Macro-environment scans before long-horizon commitments — leases, expansions, multi-year strategy.

**Why it works.** Six-axis structure ensures you don't miss a category that quietly breaks the plan.

Source: Francis Aguilar, Harvard · 1967

---

### Pirate Metrics (AARRR)
URL: https://frameworklist.com/frameworks/aarrr
Category: business

Acquisition, Activation, Retention, Referral, Revenue

**Best for:** Diagnose a growth funnel

**When to use it.** Diagnosing a growth funnel — finding which stage is the real bottleneck.

**Why it works.** 5-stage funnel aligns growth, product, and marketing on which stage is actually broken.

Source: Dave McClure, 500 Startups · 2007

---

### Porter's Five Forces
URL: https://frameworklist.com/frameworks/fiveforces
Category: strategy

Industry rivalry, suppliers, buyers, entrants, substitutes

**Best for:** Assess industry attractiveness

**When to use it.** Assessing the structural attractiveness of an industry before entering, expanding within, or exiting it.

**Why it works.** Captures industry economics that founders often ignore; explains why some markets are structurally harder regardless of execution.

Source: Michael Porter, HBR · 1979

---

### Pre-mortem
URL: https://frameworklist.com/frameworks/premortem
Category: risk

Imagine the failure first

**Best for:** Surface risks before committing

**When to use it.** Before committing to a plan with high stakes — surfaces risks the team is too optimistic to see.

**Why it works.** Future failure framing surfaces risks people are too socially polite to raise in normal review.

Source: Gary Klein, HBR · 2007

---

### Pros / Cons
URL: https://frameworklist.com/frameworks/proscons
Category: decision

Two-column weighing

**Best for:** Quick binary decisions

**When to use it.** Quick binary decisions where the trade-offs aren't deep enough to justify a heavier framework.

**Why it works.** Lowest-friction decision tool; 5 minutes is often enough when stakes are bounded.

Source: Benjamin Franklin · 1772 (letter to J. Priestley)

---

### Pyramid Principle
URL: https://frameworklist.com/frameworks/pyramid
Category: communication

Answer, supporting points, evidence

**Best for:** Structure executive writing

**When to use it.** Executive memos and recommendations — answer first, then supporting points and evidence.

**Why it works.** Answer-first structure respects the reader's time; works in any medium where attention is short.

Source: Barbara Minto, McKinsey · 1973

---

### Regret Minimization
URL: https://frameworklist.com/frameworks/regretmin
Category: decision

Choose what you'd regret least at 80

**Best for:** Long-horizon personal calls

**When to use it.** Long-horizon personal decisions — career jumps, relocations, big bets where short-term calculus misleads.

**Why it works.** Long-term lens disarms short-term anxiety; people on their deathbed regret the same things.

Source: Jeff Bezos · 2010 (Princeton commencement)

---

### Reverse Brainstorming
URL: https://frameworklist.com/frameworks/reversebrain
Category: innovation

How could we cause the problem?

**Best for:** Find solutions by inversion

**When to use it.** Stuck on a problem — flip it, brainstorm how to make it worse, then invert solutions.

**Why it works.** Inverting the problem unlocks ideas you couldn't reach by approaching it directly.

Source: Generic creativity technique (Osborn lineage)

---

### RICE
URL: https://frameworklist.com/frameworks/rice
Category: prioritization

Reach × Impact × Confidence ÷ Effort

**Best for:** Rank features or initiatives

**When to use it.** Ranking a product or growth backlog of 5–30 candidates with comparable scope.

**Why it works.** Comparable scoring across heterogeneous items; fast enough that the team will actually use it.

Source: Sean McBride, Intercom · 2017

---

### Risk Matrix
URL: https://frameworklist.com/frameworks/riskmatrix
Category: risk

Probability × impact

**Best for:** Rank risks by severity

**When to use it.** Plotting a portfolio of project risks by likelihood and impact to focus mitigations.

**Why it works.** Visual prioritization stops the team from over-investing in low-impact risks.

Source: MIL-STD-882, US DoD · 1969

---

### Risk Register
URL: https://frameworklist.com/frameworks/riskregister
Category: risk

Logged risks with owner and status

**Best for:** Track open risks over time

**When to use it.** Project management — tracking open risks with owners and status over time.

**Why it works.** Cumulative log builds team memory — risks rarely die from one mention but rarely surface twice either.

Source: PMBOK / project management standard

---

### SCAMPER
URL: https://frameworklist.com/frameworks/scamper
Category: innovation

Substitute, combine, adapt, modify, put to other use, eliminate, reverse

**Best for:** Generate ideas from an existing thing

**When to use it.** Generating ideas from an existing product or process — checklist-driven creativity.

**Why it works.** Checklist exhausts the most common idea moves; rarely fails to produce a usable variant.

Source: Bob Eberle · 1971 (after Alex Osborn)

---

### Scenario Planning
URL: https://frameworklist.com/frameworks/scenario
Category: risk

Plan across 4 plausible futures

**Best for:** Stress test long-range bets

**When to use it.** Long-range planning when the future is uncertain along 2 key axes — typically used for 5+ year horizons.

**Why it works.** Tests strategy across multiple plausible futures; reveals brittle plans that only work in one.

Source: Pierre Wack, Royal Dutch Shell · 1970s

---

### Six Thinking Hats
URL: https://frameworklist.com/frameworks/sixhats
Category: innovation

Facts, feelings, risks, benefits, creativity, process

**Best for:** Run a balanced discussion

**When to use it.** Group decisions where one mode (skepticism, optimism, emotion) is dominating — rotates perspectives explicitly.

**Why it works.** Color-coded modes give shy team members permission to voice underrepresented perspectives.

Source: Edward de Bono · 1985

---

### SMART Goals
URL: https://frameworklist.com/frameworks/smart
Category: goals

Specific, Measurable, Achievable, Relevant, Time-bound

**Best for:** Sharpen vague goals

**When to use it.** Sharpening fuzzy goals — when you find yourself with a wish, not a goal.

**Why it works.** Five-letter checklist eliminates most bad goals at the writing stage.

Source: George Doran, Mgmt. Review · 1981

---

### Stacey Matrix
URL: https://frameworklist.com/frameworks/stacey
Category: decision

Certainty × agreement → simple, complicated, complex, chaotic

**Best for:** Pick a management approach from how much you know and agree

**When to use it.** Choosing a delivery approach — waterfall, expert-led, agile, or stabilize-first — from how much certainty and agreement a project has.

**Why it works.** Surfaces the political axis (agreement) that purely problem-focused models leave out.

Source: Ralph D. Stacey · 1996

---

### STAR Method
URL: https://frameworklist.com/frameworks/star
Category: communication

Situation, Task, Action, Result

**Best for:** Tell crisp behavioral stories

**When to use it.** Behavioral interviewing or storytelling — Situation, Task, Action, Result for crisp narrative.

**Why it works.** Concrete-result ending makes stories memorable and credible — the structure protects against rambling.

Source: Developmental Dimensions International · 1970s

---

### Story Mapping
URL: https://frameworklist.com/frameworks/storymap
Category: prioritization

User journey backbone with slices

**Best for:** Plan a release across user steps

**When to use it.** Slicing a release across the user journey when you need a coherent end-to-end first version.

**Why it works.** Keeps every release usable end-to-end; backbone prevents shipping disconnected feature sets.

Source: Jeff Patton · 2005

---

### STP Marketing
URL: https://frameworklist.com/frameworks/stp
Category: strategy

Segmentation, Targeting, Positioning

**Best for:** Define who you serve and how

**When to use it.** Defining who you serve and how — refining segmentation, targeting, and positioning before pricing or messaging.

**Why it works.** Disciplines marketing into sequence — segment, then target, then position — instead of jumping to messaging.

Source: Philip Kotler · 1969

---

### Strategy Diamond
URL: https://frameworklist.com/frameworks/diamond
Category: strategy

Arenas, vehicles, differentiators, staging, economic logic

**Best for:** Articulate a coherent strategy

**When to use it.** Articulating a coherent strategy on one page — arenas, vehicles, differentiators, staging, economic logic.

**Why it works.** All five facets must hang together; exposes incoherent strategies as a missing or contradictory facet.

Source: Hambrick & Fredrickson · 2001

---

### Stress Testing
URL: https://frameworklist.com/frameworks/stresstest
Category: risk

Push assumptions to breaking point

**Best for:** Find where the plan snaps

**When to use it.** Pre-launch validation — push assumptions to extreme conditions before reality does.

**Why it works.** Most plans break in obvious ways under stress; finding those before customers do is cheap.

Source: Banking regulation · post-2008

---

### SWOT Analysis
URL: https://frameworklist.com/frameworks/swot
Category: strategy

Strengths, Weaknesses, Opportunities, Threats

**Best for:** Evaluate a position or option

**When to use it.** Strategic decisions where internal capabilities and external forces both matter — entering markets, launching products, evaluating positions.

**Why it works.** Forces a balanced view across upside and downside in one glance; the 4-quadrant structure is stable enough to reuse and compare across decisions.

Source: Albert Humphrey, Stanford · 1960s

---

### T-Shirt Sizing
URL: https://frameworklist.com/frameworks/tshirt
Category: prioritization

XS, S, M, L, XL relative size

**Best for:** Estimate quickly without precision

**When to use it.** Estimating without false precision — early-stage roadmaps, pre-spec planning.

**Why it works.** Side-steps fake precision; correlation with reality is high enough for early planning.

Source: Agile community (XP / Scrum) · 2000s

---

### Three Horizons
URL: https://frameworklist.com/frameworks/threehorizons
Category: strategy

Today's core, emerging, long-term bets

**Best for:** Balance near and far innovation

**When to use it.** Balancing today's revenue with tomorrow's bets — when leadership is debating short- vs. long-term focus.

**Why it works.** Avoids the trap of all short-term firefighting or all moonshots — keeps both alive on the same page.

Source: Baghai, Coley & White, McKinsey · 1999

---

### TRIZ
URL: https://frameworklist.com/frameworks/triz
Category: innovation

40 inventive principles for contradictions

**Best for:** Resolve engineering trade-offs

**When to use it.** Engineering trade-offs — uses 40 inventive principles to resolve apparent contradictions.

**Why it works.** Patterns drawn from millions of patents; most engineering problems aren't actually new.

Source: Genrich Altshuller, USSR · 1946

---

### Value Chain
URL: https://frameworklist.com/frameworks/valuechain
Category: strategy

Primary and support activities

**Best for:** Find where value is created

**When to use it.** Auditing where in your operations value is actually created vs. where it leaks — useful for cost or differentiation strategy.

**Why it works.** Separates where value is created from where it's captured; helps locate the real moat.

Source: Michael Porter, “Competitive Advantage” · 1985

---

### Value Proposition Canvas
URL: https://frameworklist.com/frameworks/vpc
Category: business

Customer jobs, pains, gains × your offer

**Best for:** Sharpen product–market fit

**When to use it.** Sharpening product–market fit — explicitly aligning offer with customer jobs, pains, and gains.

**Why it works.** Concrete artifact for product–market fit conversations — moves the team off vibes.

Source: Alexander Osterwalder · 2014

---

### Value vs Effort
URL: https://frameworklist.com/frameworks/valueeffort
Category: prioritization

Quick wins, big bets, fillers, time sinks

**Best for:** Pick the easy wins fast

**When to use it.** Quick filtering of a backlog into quick wins, big bets, fillers, and time sinks.

**Why it works.** Surfaces quick wins that tend to get crowded out by glamorous big bets.

Source: Generic 2×2 prioritization (lean/agile)

---

### Values Clarification
URL: https://frameworklist.com/frameworks/values
Category: life

Identify core personal values

**Best for:** Make decisions consistent with self

**When to use it.** Periodic personal alignment — when decisions feel exhausting because you're not sure what you actually want.

**Why it works.** Articulated values let you say no consistently; without them every decision feels custom-evaluated.

Source: Schwartz / Rokeach value studies · 1970s–90s

---

### VRIO Framework
URL: https://frameworklist.com/frameworks/vrio
Category: strategy

Valuable, Rare, Inimitable, Organized

**Best for:** Test for sustainable advantage

**When to use it.** Pressure-testing whether a perceived strength is actually a sustainable competitive advantage.

**Why it works.** Distinguishes a temporary edge from a sustainable one — most claimed advantages fail one of the four tests.

Source: Jay Barney · 1991

---

### Wardley Mapping
URL: https://frameworklist.com/frameworks/wardley
Category: strategy

Position components on evolution axis

**Best for:** See where to play and how

**When to use it.** Deciding what to build, buy, or rent across a complex tech or supply stack.

**Why it works.** Maps evolution of components, not just snapshots — surfaces what to build vs. commoditize.

Source: Simon Wardley · 2005

---

### Weighted Decision Matrix
URL: https://frameworklist.com/frameworks/weightedmatrix
Category: decision

Decision matrix with criterion weights

**Best for:** When some criteria matter more

**When to use it.** Decision matrix when criteria carry different weight — formalize what you'd otherwise weigh by gut.

**Why it works.** When criteria don't matter equally, weights make priorities legible to stakeholders.

Source: Extension of Pugh matrix · 1980s

---

### Wheel of Life
URL: https://frameworklist.com/frameworks/wheeloflife
Category: life

Score 8 areas of life on 1–10

**Best for:** See where to invest energy

**When to use it.** Periodic life audit — see which areas are out of balance and need attention.

**Why it works.** Spider chart of imbalance is hard to argue with; usually one or two slices are obviously the bottleneck.

Source: Paul J. Meyer, Success Motivation Institute · 1960s

---

### WSJF
URL: https://frameworklist.com/frameworks/wsjf
Category: prioritization

Cost of delay ÷ job size

**Best for:** Sequence work in agile flow

**When to use it.** Sequencing work in agile programs where cost of delay matters more than effort alone.

**Why it works.** Cost of delay is real money in agile flow — WSJF makes that visible vs. effort-only ranking.

Source: Don Reinertsen, “Principles of Product Dev. Flow” · 2009

---

## Academy

### Ansoff Matrix Examples: 4 Growth Strategies (2026)
URL: https://frameworklist.com/academy/ansoff-matrix-examples
> The Ansoff Matrix maps growth into four strategies by risk. Here it is worked on real companies — Nvidia, Netflix, Apple, Amazon — with a placement test for your own bets.

The **Ansoff Matrix** sorts every growth idea into one of four strategies by asking two questions — is the *product* new, and is the *market* new — and then ranks those four boxes by rising risk. It's the fastest way to see whether a company's growth bets are concentrated in safe, familiar territory or stacked in the corner where most expensive failures live. This guide works the matrix on **real, current companies** — Nvidia's June 2026 Computex portfolio, Netflix, Apple, Amazon — rather than abstractions, because the framework only earns its keep when you can see a named company's actual choice inside it.

Economist Igor Ansoff introduced the model in a 1957 *Harvard Business Review* article, ["Strategies for Diversification."](https://hbr.org/1957/09/strategies-for-diversification) Nearly 70 years later it survives because the two-by-two is honest about one thing every growth deck tries to hide: **risk rises as you move away from what you already do.**

> **Want to run the matrix on your own company?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=ansoff-academy) fills in each quadrant with AI-assisted prompts. Free to start.

### Prefer to watch or listen?

<YouTube id="hXArZ5DQyss" title="Ansoff Matrix Examples: 4 Growth Strategies" />

<Spotify id="3CYvP1eILY9cd3ElwlXYGd" title="Ansoff Matrix Examples: 4 Growth Strategies — Framework podcast episode" />

## The four growth strategies

The two axes are **product** (existing vs. new) and **market** (existing vs. new). The four combinations are the four strategies — listed here from lowest to highest risk:

| Strategy | Product | Market | What it means | Relative risk |
|---|---|---|---|---|
| **Market Penetration** | Existing | Existing | Sell more of what you have to who you already serve | Lowest |
| **Product Development** | New | Existing | Build something new for your current customers | Moderate |
| **Market Development** | Existing | New | Take your current product to new customers or geographies | Moderate |
| **Diversification** | New | New | New product *and* new market at once | Highest |

The ordering is the whole point. Market Penetration leans on two known quantities; Diversification leans on neither. Everything Ansoff teaches flows from that single gradient.

## How to actually use it

1. **Define the unit of analysis.** One product line, one business unit, or the whole company — pick the altitude before you start, or moves will land in the wrong box.
2. **List the growth initiatives in play.** Real ones with budget behind them, not aspirations. Aim for 5–12.
3. **Place each one with the two-question test.** Is the customer new to us? Is the product new to us? The answers assign the quadrant deterministically (see the [Placement Test](#the-ansoff-risk-ladder-and-placement-test) below).
4. **Apply the adjacency discount.** A "new" product that reuses an existing moat — a brand, a distribution channel, a software platform — is less risky than a cold-start move into the same quadrant. Note it; don't ignore it.
5. **Map the portfolio, not the project.** The insight is rarely about one bet. It's about the *distribution* — how much of your capital and management attention sits in each quadrant.
6. **Read the imbalance.** If most of the spend is in Diversification while the core business is already under pressure, the matrix has done its job: it made the risk concentration visible.

## Worked example: Nvidia at Computex 2026

The clearest current example is Nvidia's June 1, 2026 Computex keynote, where Jensen Huang announced three things the press treated as separate product stories. Ansoff treats them as one portfolio decision:

| Initiative | Product new? | Market new? | Quadrant | Note |
|---|---|---|---|---|
| More Vera Rubin GPUs to hyperscalers | No | No | **Market Penetration** | CUDA lock-in; the cash engine |
| [Vera Rubin platform](https://nvidianews.nvidia.com/news/rubin-platform-ai-supercomputer), Spectrum-X to existing AI-cluster buyers | Yes | No | **Product Development** | Same customers, next-gen silicon |
| Sovereign-AI and enterprise build-outs | No | Yes | **Market Development** | Same accelerators, new buyers |
| [RTX Spark](https://www.tomshardware.com/laptops/nvidia-unveils-rtx-spark-superchip-at-computex-2026-new-platform-promises-to-turn-windows-into-an-agentic-ai-os-with-arm-cpu-blackwell-gpu-and-128gb-unified-memory) — a superchip for mainstream Windows PCs | Yes | Yes | **Diversification** | New product *and* new buyer |
| Isaac GR00T humanoid-robot reference | Yes | Yes | **Diversification** | Physical-AI: a wholly new market |

Read this way, the announcement is a *statement about where Nvidia is putting its riskiest chips*. The penetration and product-development quadrants do the cash-generating work; RTX Spark and GR00T sit in Diversification — the highest-risk box — even as the core business is already concentrated in AI compute. RTX Spark *looks* like Product Development because Nvidia already sells GPUs to PC makers, but the addressable buyer (the general Windows-PC owner) and the product category (an Arm+Blackwell PC SoC) are both new enough to land in Diversification — with an adjacency discount from CUDA and existing OEM relationships.

For the full quadrant-by-quadrant breakdown, see [Nvidia Ansoff Matrix 2026: the RTX Spark PC bet](/examples/nvidia-ansoff-matrix-2026). For a different company with the *same* center-of-gravity problem — its valuation thesis sitting in the riskiest quadrant — see [Tesla Ansoff Matrix Analysis 2026](/examples/tesla-ansoff-matrix).

## Ansoff Matrix examples by quadrant (real companies)

The four-quadrant set most readers are searching for — one well-known company per strategy:

| Strategy | Company | The move |
|---|---|---|
| **Market Penetration** | [Coca-Cola](https://www.coca-colacompany.com/) | More volume to existing buyers via promotion, pricing, and distribution reach — no new product, no new market |
| **Product Development** | [Apple](https://www.apple.com/apple-watch-series-10/) | New devices (Apple Watch, Mac, iPad) sold into the existing iPhone customer base |
| **Market Development** | [Netflix](https://ir.netflix.net/financials/quarterly-earnings/default.aspx) | The same streaming service taken country by country into new geographies |
| **Diversification** | [Amazon](https://aws.amazon.com/) | AWS — a new product (cloud compute) for a new market (enterprise IT), distinct from its retail origin |

Notice that the three "famous" cases (Coca-Cola, Apple, Netflix) lean on something the company already owns — a brand, a customer base, a service. Only Amazon's AWS was a genuine both-axes-new bet, and even then it reused Amazon's own data-center muscle. That reuse is the adjacency discount in action, and it's the part most Ansoff write-ups skip.

One placement is worth getting right, because almost every published Ansoff write-up gets it wrong: the **Apple Watch is Product Development, not Diversification**. It was a new product, but at launch it required an iPhone and was sold to Apple's existing customers through Apple's existing stores — one axis new, not two. **Vision Pro** is the genuine Apple diversification, and its outcome is what the bottom-right quadrant actually costs. The [Apple Ansoff Matrix example (2026)](/examples/apple-ansoff-matrix-2026) scores all four quadrants against Apple's fiscal Q3 2026 segment revenue and finds the results degrade in exactly the order Ansoff predicted — and, since September 2026, places the [$1,999 iPhone Duo](/examples/apple-ansoff-matrix-2026#the-iphone-duo-placing-a-move-before-its-outcome-exists) in Product Development with a pre-registered prediction to be scored on fiscal Q1 2027.

## The Ansoff Risk Ladder and Placement Test

Most explainers stop at "diversification is risky." That's directionally true and operationally useless. The **Ansoff Risk Ladder** turns the gradient into a usable diagnostic by pairing each quadrant with its specific failure mode and the adjacency discount that can move a bet down a rung:

| Rung | Quadrant | Why the risk | Dominant failure mode | What earns an adjacency discount |
|---|---|---|---|---|
| 1 (safest) | Market Penetration | Both known | Saturation — you run out of room | A still-underpenetrated segment |
| 2 | Product Development | Customer known | Build the wrong thing for a known customer | Strong existing customer-research loop |
| 3 | Market Development | Product known | Misread the new market's needs | A transferable distribution channel |
| 4 (riskiest) | Diversification | Neither known | Spread thin across two unknowns at once | A moat that travels — brand, platform, or channel |

**The Placement Test** assigns any initiative to a rung with two questions:

1. **Is the customer new to us?** (yes / no)
2. **Is the product new to us?** (yes / no)

No + No → Penetration. No + Yes → Product Development. Yes + No → Market Development. Yes + Yes → Diversification. Then apply the discount: if the "new" axis reuses an existing moat, the bet behaves like the rung *below* it. Nvidia's RTX Spark scores rung 4 on the test but earns a partial discount toward rung 2 because CUDA and the OEM relationships travel with it — which is exactly why it's a *defensible* diversification rather than a reckless one.

This is the lens to carry into a deeper portfolio tool. Where Ansoff tells you *which growth bets you're making*, [the BCG Matrix](/examples/nvidia-bcg-matrix) tells you *which existing units should fund them* — the two pair naturally, with Ansoff feeding the growth thesis and BCG allocating the cash.

## When NOT to use the Ansoff Matrix

- **Pure operational or pricing decisions.** Ansoff is about *direction* of growth, not execution. Use [RICE](/academy/rice-prioritization-framework) to rank features within a chosen direction.
- **Industry-structure questions.** "Is this market even attractive to grow into?" is a [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) question; Ansoff assumes you've already decided the market is worth entering.
- **Macro-environment scans.** Before placing a Market Development bet abroad, run a [PESTEL analysis](/frameworks/pestel) on the target geography — Ansoff won't surface the political or regulatory landmines.
- **Any question whose answer might be "do less."** All four cells are additions — neither axis has a value for *fewer* — so the matrix cannot return subtraction, and will not raise it. Ask the removal question separately, before you draw the grid. Worked on 37signals' 2014 decision to sunset every product but Basecamp in the [Ansoff Matrix Example: The Growth Move That Isn't on the Grid](/examples/ansoff-37signals-subtraction), which names this **the Fifth Cell**.

## Common mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Calling everything "Product Development" | New products feel safer than they are when sold to existing customers | Run the Placement Test on the *market*, not the org chart — a new buyer segment is Market Development even inside the same company |
| Ignoring the adjacency discount | Quadrants are treated as binary, so every diversification looks equally reckless | Ask what moat travels with the bet; a brand or platform that transfers lowers the real risk |
| Mapping projects, not the portfolio | Teams analyze one launch in isolation | Place *all* funded initiatives at once — the imbalance only shows in aggregate |
| Treating the matrix as a recommendation | The grid names risk; it doesn't tell you to avoid it | High-risk quadrants can be correct — the point is to fund them *knowingly*, with the core business healthy enough to absorb a miss |

## Related frameworks

- [Nvidia Ansoff Matrix 2026](/examples/nvidia-ansoff-matrix-2026) — the full worked deep-dive behind the example above
- [Tesla Ansoff Matrix Analysis 2026](/examples/tesla-ansoff-matrix) — a second company with its valuation thesis in the riskiest quadrant
- [FIFA Ansoff Matrix 2026: the World Cup growth bet](/examples/fifa-ansoff-matrix-2026) — a non-tech case running a move in all four quadrants inside one year
- [Ansoff Matrix (catalog entry)](/frameworks/ansoff) — the template to fill in for your own company
- [BCG Matrix worked on Nvidia](/examples/nvidia-bcg-matrix) — the portfolio-funding companion to Ansoff's growth lens
- [Ansoff Matrix vs BCG Matrix](/compare/ansoff-matrix-vs-bcg-matrix) — when to run each, and the Portfolio-to-Growth Handoff that connects them
- [Porter's Five Forces: a beginner's guide](/academy/porters-five-forces-beginners-guide) — for the "is this market attractive" question Ansoff skips
- [PESTEL](/frameworks/pestel) — the macro scan to run before any Market Development bet abroad

> Want to run this on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=ansoff-academy-footer) — fill in any framework with AI assistance.

## Sources

- [Igor Ansoff — "Strategies for Diversification," *Harvard Business Review* (1957)](https://hbr.org/1957/09/strategies-for-diversification) — the original framework
- [NVIDIA Newsroom — "Rubin platform in full production" (Computex, June 2026)](https://nvidianews.nvidia.com/news/rubin-platform-ai-supercomputer)
- [Tom's Hardware — "Nvidia unveils RTX Spark superchip at Computex 2026" (June 1, 2026)](https://www.tomshardware.com/laptops/nvidia-unveils-rtx-spark-superchip-at-computex-2026-new-platform-promises-to-turn-windows-into-an-agentic-ai-os-with-arm-cpu-blackwell-gpu-and-128gb-unified-memory)
- [Netflix — Investor Relations, quarterly earnings](https://ir.netflix.net/financials/quarterly-earnings/default.aspx) — international market-development history
- [Amazon Web Services](https://aws.amazon.com/) — the diversification reference case

---

### BCG Matrix Analysis: The Four Quadrants Explained
URL: https://frameworklist.com/academy/bcg-matrix-analysis-explained
> The BCG Matrix sorts a product portfolio into Stars, Cash Cows, Question Marks, and Dogs. Here's how the four quadrants work — with Apple's portfolio tracked across two consecutive quarters, so you can see a unit actually change boxes.

The **BCG Matrix** sorts every product or business unit a company owns into one of four boxes — Stars, Cash Cows, Question Marks, and Dogs — by asking two questions: how fast is its market growing, and how large is its share of that market. It's the fastest way to see, on one page, which parts of a portfolio *generate* cash and which parts *consume* it, so a leadership team can decide where to invest, where to harvest, and where to walk away. This guide works the matrix on a **real, current portfolio — Apple's, using its fiscal Q3 2026 segment revenue reported on July 30, 2026** — rather than an abstract one, and then re-runs it against the prior quarter so you can watch a business unit actually *change boxes*. That second reading is the part most explanations skip, and it's where the framework stops being a diagram and starts being a decision.

Bruce Henderson of the Boston Consulting Group introduced the model in a 1970 essay, ["The Product Portfolio."](https://www.bcg.com/publications/1970/strategy-the-product-portfolio) More than fifty years later it survives for one reason: it forces a diversified company to admit that **not every business unit deserves the same treatment** — and that the cash thrown off by yesterday's winners is what pays for tomorrow's.

> **Want to run the matrix on your own company?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=bcg-academy) fills in each quadrant with AI-assisted prompts. Free to start.

## The two axes: cash in, cash out

Every BCG quadrant is a combination of two measurements. Understanding what each axis is a *proxy for* is the whole game:

| Axis | What it measures | What it's a proxy for |
|---|---|---|
| **Market growth rate** (vertical) | How fast the unit's market is expanding, usually split high/low at ~10% | How much cash the unit **consumes** — fast-growing markets demand constant reinvestment to hold position |
| **Relative market share** (horizontal) | The unit's share divided by the largest competitor's share; 1.0 = tied with the leader | How much cash the unit **generates** — share leadership brings scale, lower costs, and pricing power |

The insight hidden in those two proxies: a unit's position tells you whether it is a net *source* or net *user* of cash. That's why the matrix is really a **cash-flow map** wearing the costume of a growth-share grid.

## The four quadrants

Cross the two axes and you get four boxes, each with a built-in prescription:

<BcgMatrix />

**How to read the grid.** Market growth rate runs up the vertical axis — high at the top, low at the bottom. Relative market share runs along the horizontal axis, and here the BCG convention trips people up: **high share sits on the left, not the right.** So the top-left box is the **[Star](/glossary/star)** (high growth, high share), the top-right is the **Question Mark** (high growth, low share), the bottom-left is the **[Cash Cow](/glossary/cash-cow)** (low growth, high share), and the bottom-right is the **Dog** (low growth, low share). Read left to right and you are moving from market leadership toward market weakness; read top to bottom and you are moving from a market that demands cash toward one that no longer does.

| Quadrant | Growth | Share | Cash profile | Default move |
|---|---|---|---|---|
| **Star** | High | High | Generates a lot, consumes a lot — roughly cash-neutral | **Invest** to hold the lead until growth slows |
| **[Cash Cow](/glossary/cash-cow)** | Low | High | Generates far more than it consumes | **Milk** — harvest the surplus to fund [Stars](/glossary/star) and Question Marks |
| **Question Mark** | High | Low | Consumes a lot, generates little | **Fund or kill** — concentrate behind a few, exit the rest |
| **Dog** | Low | Low | Roughly cash-neutral, ties up management attention | **Divest** unless it's strategically justified |

The lifecycle the matrix implies: today's **Question Mark**, if funded well, becomes tomorrow's **Star**; as its market matures, the Star settles into a **Cash Cow**; and a Cow whose market keeps shrinking eventually slides toward **Dog**. A healthy portfolio keeps that conveyor moving — which is exactly what the worked example below tests.

## How to run a BCG analysis in 6 steps

1. **Define the units.** List the products, brands, or business segments you'll place. They must be genuinely separate — different markets, ideally their own P&L. If you have one product, three quadrants will be empty and the exercise is trivial (run [Ansoff](/academy/ansoff-matrix-examples) instead).
2. **Pick the market for each.** A unit's "market" is a judgment call, and it changes the answer. Is Apple's Vision Pro competing in "headsets" (small, low-growth) or "spatial computing" (nascent, high-growth)? Name the market explicitly — the placement follows from it.
3. **Measure market growth.** Use the unit's *market* growth, not the unit's own revenue growth. A product can grow 20% in a flat market (that's share gain, not market growth) — conflating the two is the most common error.
4. **Measure relative share.** Divide the unit's share by the largest competitor's. Above 1.0 means you lead; well below means you follow.
5. **Plot and size the bubbles.** Place each unit; scale the bubble to its revenue so the picture shows where the money actually is, not just where each unit sits.
6. **Read the balance, then act.** A portfolio isn't healthy because it has a big Star — it's healthy because the Cows fund the Question Marks fast enough to replace the Star before its market fades. That balance test is the whole point (see [the Cash-Cow Dependency Test](#the-cash-cow-dependency-test) below).

## Worked example: Apple's portfolio in fiscal Q3 2026

Apple is the ideal BCG subject because, unlike a single-product startup, it runs five reported segments across markets at very different stages. In its [fiscal Q3 2026 results](https://www.apple.com/newsroom/2026/07/apple-reports-third-quarter-results/) (reported July 30, 2026), Apple posted **$109.4B in revenue, up 16% year over year**, with $29.8B in net income and a 50.1% gross margin. Here is where each segment lands:

| Segment | Q3 2026 revenue | Market growth | Relative share | Quadrant |
|---|---|---|---|---|
| **Services** | [$30.7B, +12% (record)](https://9to5mac.com/2026/07/30/apple-reports-q3-2026-earnings-109-4-billion-in-revenue-up-16/) | High | High (owns its ecosystem) | ⭐ **Star** |
| **iPhone** | [$54.3B, +22% (June-quarter record)](https://www.apple.com/newsroom/2026/07/apple-reports-third-quarter-results/) | Low (mature market) | High (premium leader) | 🐄 **Cash Cow** |
| **Mac** | [$10.4B, +29%](https://9to5mac.com/2026/07/30/apple-reports-q3-2026-earnings-109-4-billion-in-revenue-up-16/) | Negative (PC shipments −4.9%) | Rising but still follower (0.41) | 🐕→🐄 **Dog migrating to Cash Cow** |
| **Wearables, Home & Accessories** (contains Vision Pro) | $7.9B | High (spatial computing) | Low (unproven) | ❓ **Question Mark** |
| **iPad** | $6.2B | Low (declining tablet market) | High (category leader) | 🐄 **Cash Cow** (secondary) |

Read quadrant by quadrant:

- **Services is the Star.** It dominates the ecosystem it controls — the App Store, iCloud, Apple Music, AppleCare — at high margin, and it set another record. But note the deceleration: +12% this quarter against +16.3% last quarter. A Star whose growth is converging on the company average is a Star drifting toward Cash Cow. Not a problem yet; it is the thing to watch.
- **iPhone is the Cash Cow — and that's the risk.** At roughly **half of total revenue**, a single Cash Cow that large is a concentration flag, not a comfort. Last quarter this page read iPhone's +21.7% as a one-off product-cycle supercycle. Two consecutive quarters at ~+22% weakens that reading: this looks less like a spike and more like a genuinely elevated replacement cycle. The concentration risk is unchanged either way — the whole company still breathes on one product.
- **Mac is the segment that moved — see the migration table below.** Revenue grew 29%, the fastest of any segment.
- **Vision Pro is the Question Mark.** Apple folds it into "Wearables, Home & Accessories," which hides its economics — but strategically it is the classic high-growth, low-share, unproven bet the Cows are funding. It either graduates to a Star or gets quietly wound down. That's the fund-or-kill clock.
- **iPad is a smaller Cash Cow.** Apple leads a shrinking tablet market. It throws off cash and demands little reinvestment — milk it.

### The one segment that changed boxes

Last quarter this page placed Mac in the **Dog** quadrant: low market growth, minority share, kept only for the platform halo. One quarter later that placement no longer holds — and the reason is a clean demonstration of step 3 above (*measure the market's growth, not the unit's revenue growth*).

| Measure | Fiscal Q2 2026 | Fiscal Q3 2026 | Direction |
|---|---|---|---|
| Mac revenue | $8.4B, +5.7% YoY | **$10.4B, +29% YoY** | Accelerating hard |
| Global PC shipments | Growing (9 straight quarters) | **−4.9% YoY** (68.2M units) | Market turned negative |
| Mac unit shipments | +9.1% YoY | **+10.1% YoY** (6.7M units) | Outgrowing a shrinking market |
| Apple share of PC market | 8.5% (year-ago) | **9.9%** | +1.4 points |
| Relative share vs. Lenovo (largest competitor, 24.4%) | ~0.36 | **~0.41** | Moving left (toward share leadership) |

The naive read of "+29% revenue" is that Mac jumped up the growth axis. It did not — **the PC market shrank 4.9%, its [first decline after nine consecutive quarters of growth](https://9to5mac.com/2026/07/08/idc-apple-grows-mac-shipments-as-broader-pc-market-declines/)**. Mac stays *low* on the vertical axis. What actually changed is horizontal: Apple was the only major vendor to grow shipments, taking share from Lenovo, HP, and Dell and lifting relative share from roughly 0.36 to 0.41.

Low market growth plus *rising* relative share is the definition of a unit moving **from Dog toward Cash Cow**. Honesty about the number matters here: at 0.41, Mac is still a follower, not a leader — relative share must approach 1.0 before it is a true Cash Cow. Mac has not arrived. But the direction of travel reversed, and BCG's whole prescription depends on direction: you divest a Dog that is sinking and you fund a Dog that is climbing.

## The Cash-Cow Dependency Test

Here is the named diagnostic worth taking away — a three-question test for whether a portfolio is genuinely *balanced* or just has an impressive Star. A portfolio is healthy only if it passes all three:

| # | Question | Apple's answer (fiscal Q3 2026) |
|---|---|---|
| 1 | **Concentration** — does a single Cash Cow throw off more than ~half of total revenue? | **Still fails, but improving.** iPhone is 49.6% of Q3 revenue ($54.3B of $109.4B), down from 51.3% in Q2 — because Mac and Services grew, not because iPhone shrank. The company still rides one product cycle. |
| 2 | **Pipeline** — is at least one unit funded well enough to become the *next* Star before today's Cow fades? | **Passes.** Services already made the jump; Vision Pro is the next bet. |
| 3 | **Discipline** — is every Dog either strategically load-bearing or on a divestment clock? | **Passes, and the Dog is now climbing.** Mac was the justified-Dog exception; on Q3 share gains it is migrating toward Cash Cow. |

The test reframes what "a strong portfolio" means. Across our worked BCG deep-dives, the pattern holds: the [Nvidia BCG Matrix](/examples/nvidia-bcg-matrix) has the market's most dominant Star yet **fails** the concentration test just as Apple does — everything rides one market continuing to compound. The [SpaceX BCG Matrix](/examples/spacex-bcg-matrix-2026) passes concentration because its Cash Cow (Falcon 9) and Star (Starlink) are fused into a self-funding flywheel. And the [FC Barcelona BCG Matrix](/examples/barcelona-bcg-matrix-2026) is the cautionary case — a club with elite Stars but a *broken* Cash Cow, which is what forces the fire-sale of Question Marks. **The biggest Star doesn't make a portfolio safe; passing the Dependency Test does.**

## The Quadrant Migration Test

The Dependency Test judges a portfolio from one reading. This second diagnostic judges it from *two* — and it is the more useful of the pair, because **a quadrant is a position and strategy is a direction.** Apple's Mac is the proof: read once, it was a Dog worth keeping for the halo; read twice, it is a Dog climbing toward Cash Cow on share gain. Same box, opposite prescription.

Plot your units, wait a quarter or two, plot them again, and classify every unit that moved:

| Migration | Verdict | What it means | What to do |
|---|---|---|---|
| **Question Mark → Star** | ✅ Healthy | The bet won share while the market was still growing | Fund harder; the window is open |
| **Star → Cash Cow** | ✅ Healthy | The market matured on schedule and you held the lead | Start harvesting; redeploy the surplus |
| **Dog → Cash Cow** | ✅ Rare and valuable | Share gain in a flat or shrinking market — *Mac, fiscal Q3 2026* | Reinvest; you found leverage where nobody was looking |
| **Star → Question Mark** | ⚠️ Warning | You lost relative share while the market kept growing | Diagnose fast — this is the most expensive drift to ignore |
| **Cash Cow → Dog** | ⚠️ Warning | Share erosion in a mature market; the funding engine is failing | Everything downstream is at risk — see the [FC Barcelona case](/examples/barcelona-bcg-matrix-2026) |
| **Question Mark → Dog** | ⚠️ Terminal | The market stopped growing before you won share | Kill it; the fund-or-kill clock ran out |

Two rules fall out of the table:

1. **Read the arrows, not the boxes.** A unit sitting still in a good box and a unit sliding out of it look identical in a single snapshot. Most BCG analyses are drawn once and filed — which throws away the only signal that distinguishes a healthy Cash Cow from one two quarters into decline.
2. **Distinguish which axis moved.** A unit can migrate vertically (its *market* changed) or horizontally (its *share* changed), and the two demand opposite responses. Mac moved horizontally in a shrinking market — that is earned, durable, and worth funding. A unit that moves up only because its market got hot has earned nothing, and will slide back when the market cools.

The test also explains why the [Ansoff Matrix](/compare/ansoff-matrix-vs-bcg-matrix) is the natural next step: once you know *which direction* a unit is travelling, Ansoff tells you which growth move to make about it.

## When NOT to use the BCG Matrix

- **Single-product or early-stage companies.** With one line, three quadrants are empty. The matrix has nothing to balance — use [Ansoff](/compare/ansoff-matrix-vs-bcg-matrix) or [RICE](/academy/rice-prioritization-framework) instead.
- **When margins diverge from share.** BCG assumes high share means high profit. In businesses where a low-share niche player earns the best margins (luxury, specialist B2B), the matrix will mislabel your most profitable unit a Dog.
- **For deciding whether a market is worth entering at all.** BCG assumes you're already in the market. To judge the market's attractiveness first, step up a layer to [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces).

## Common mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Using *revenue* growth instead of *market* growth | Revenue growth is easy to pull; market growth takes research | Plot the market's growth. A unit growing 20% in a flat market is gaining share, not sitting in a high-growth market |
| Treating a big Star as proof of health | The Star is the most visible box | Run the [Cash-Cow Dependency Test](#the-cash-cow-dependency-test) — concentration and pipeline matter more than Star size |
| Divesting every Dog on principle | "Kill your Dogs" is the memorable rule | Keep a Dog that's load-bearing (a platform, a channel, a brand halo) — and check whether it's climbing. Apple's Mac was a halo Dog one quarter and a share-gaining Cash-Cow-in-waiting the next |
| Drawing it once and filing it | The matrix looks like a finished artifact | It's a snapshot; markets move. Re-run it every few quarters, especially after an earnings print, and run [the Quadrant Migration Test](#the-quadrant-migration-test) on what moved |
| Reading a revenue jump as a move up the growth axis | Revenue growth is the number in the press release; market growth isn't | Check the market first. Mac's +29% revenue happened while the PC market shrank 4.9% — that's a horizontal move (share), not a vertical one (growth) |
| Gaming the market definition | A narrow market makes any unit look like a leader | Name the market honestly before you measure share — the definition decides the quadrant |

## Want to go deeper

This page is the methodology; the worked deep-dives are where the four quadrants come alive on real portfolios. Start with the [Nvidia BCG Matrix Analysis 2026](/examples/nvidia-bcg-matrix) for a portfolio dangerously tipped behind one Star, the [SpaceX BCG Matrix Analysis 2026](/examples/spacex-bcg-matrix-2026) for a self-funding flywheel, the [FC Barcelona BCG Matrix](/examples/barcelona-bcg-matrix-2026) for what happens when the Cash Cow breaks, and the [Alphabet BCG Matrix 2026](/examples/alphabet-bcg-matrix-2026) for a Cash Cow (Search) being actively contested by AI-native rivals while it funds everything else. Then read [Ansoff Matrix vs BCG Matrix](/compare/ansoff-matrix-vs-bcg-matrix) to see how a portfolio *diagnosis* (BCG) hands off to a growth *prescription* (Ansoff) — the two frameworks are built to run back to back. And when your portfolio outgrows four boxes, [BCG Matrix vs GE-McKinsey Matrix](/compare/bcg-matrix-vs-ge-mckinsey-matrix) shows when to escalate from the fast 2×2 to the nine-box grid.

> Want to run this on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=bcg-academy) — fill in any framework with AI assistance.

## Sources

- [Bruce Henderson — "The Product Portfolio," BCG Perspectives (1970)](https://www.bcg.com/publications/1970/strategy-the-product-portfolio)
- [Apple Newsroom — "Apple reports third quarter results" (July 30, 2026)](https://www.apple.com/newsroom/2026/07/apple-reports-third-quarter-results/)
- [9to5Mac — "Apple reports Q3 2026 earnings: $109.4 billion in revenue, up 16%" (July 30, 2026)](https://9to5mac.com/2026/07/30/apple-reports-q3-2026-earnings-109-4-billion-in-revenue-up-16/)
- [MacRumors — "Apple Reports 3Q 2026 Results: $29.8B Profit on $109.4B Revenue" (July 30, 2026)](https://www.macrumors.com/2026/07/30/apple-3q-2026-earnings/)
- [9to5Mac — "IDC: Apple grows Mac shipments as broader PC market declines" (July 8, 2026)](https://9to5mac.com/2026/07/08/idc-apple-grows-mac-shipments-as-broader-pc-market-declines/)
- [Asymco — "Worldwide PC market update Q2 2026: IDC overall decline of 4.9%, Apple up 10%" (July 14, 2026)](https://asymco.com/2026/07/14/worldwide-pc-market-update-q2-2026-omdia-overall-decline-4-apple-up-16-idc-overall-decline-of-4-9-apple-up-10/)
- [MacRumors — "Apple Reports Record-Breaking 2Q 2026 Results: $29.6B Profit on $111.2B Revenue" (April 30, 2026)](https://www.macrumors.com/2026/04/30/apple-2q-2026-earnings/)
- [Variety — "Apple Q2 2026 Earnings: Services Revenue Hits Record $31 Billion" (2026)](https://variety.com/2026/digital/news/apple-earnings-march-2026-quarter-services-revenue-1236734606/)
- [Wccftech — "Apple Q2 2026 Earnings: iPhone Business Grows By 21.7%" (2026)](https://wccftech.com/apple-q2-2026-earnings-iphone-business-just-grew-by-21-7-in-a-single-quarter-services-outpace-mac-ipad-and-wearables-combined/)
- [Corporate Finance Institute — "BCG Matrix: Overview, Four Quadrants and Diagram"](https://corporatefinanceinstitute.com/resources/management/boston-consulting-group-bcg-matrix/)

---

### Burn Multiple: Formula, Benchmarks, and How to Calculate It
URL: https://frameworklist.com/academy/burn-multiple-formula-benchmarks
> The burn multiple formula (net burn ÷ net new ARR), David Sacks' original definition, the reset 2026 benchmarks, a real CrowdStrike FY2026 worked example, and the quadrant that tells you why your number is bad.

The burn multiple is the single number that separates efficient growth from expensive growth. It answers one question: **how many dollars of cash did you burn to add one dollar of recurring revenue?** Revenue growth alone can't answer that — a company can post triple-digit growth and still be a capital incinerator. The burn multiple normalizes growth by the cash that bought it.

This page is the formula, the original David Sacks definition, the benchmarks the 2026 market actually uses (they tightened), a real worked example using CrowdStrike's fiscal 2026 numbers, and a quadrant that diagnoses *why* a burn multiple is bad — because two companies can share the same score for opposite reasons.

> **Want capital efficiency on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a finance-metrics worksheet — drop in net burn and net new ARR, see the burn multiple and the benchmark band update live. Or start with the [Burn Rate](/glossary/burn-rate) and [Runway](/glossary/runway) glossary entries.

## The burn multiple formula

```
Burn Multiple = Net Burn / Net New ARR
```

Both inputs are measured over the same period — a quarter, or more commonly the trailing twelve months to smooth out lumpy bookings.

| Input | Definition | Common error |
|---|---|---|
| **Net burn** | Cash spent minus cash collected in the period | Using GAAP operating loss instead of *cash* burn |
| **Net new ARR** | New ARR + expansion ARR − churned ARR | Counting gross new ARR, ignoring churn and contraction |

The number reads as a price: a burn multiple of 2.0x means you paid $2 of cash for every $1 of net new annual recurring revenue. Lower is better — you want to manufacture recurring revenue as cheaply as possible.

## Who invented the burn multiple — and why it beats growth rate

[David Sacks](https://www.craft.co/), founder of Craft Ventures and an early PayPal and Yammer operator, popularized the burn multiple in a 2020 essay. His argument: **revenue growth is a vanity metric in isolation.** Any company can grow 200% by spending $4 to win $1 — the growth chart looks identical to a company growing 200% at $1.20 per dollar, but one is building a business and the other is lighting money on fire.

The burn multiple makes the two distinguishable. It is, in Sacks' framing, "the most holistic burn metric" because the numerator captures *all* spending inefficiency (bloated headcount, weak sales productivity, churn) and the denominator captures the only growth that compounds — net new ARR, after losses.

## How to calculate the burn multiple (5 steps)

1. **Pick the period and stick to it.** Use the same window — typically trailing twelve months — for both the burn and the ARR figure. Mixing a quarterly burn with an annual ARR number produces a meaningless ratio.
2. **Compute net burn from the cash flow statement, not the P&L.** Net burn is the actual cash that left the bank minus the cash that came in. For public companies, the clean proxy is negative free cash flow. A GAAP operating loss includes non-cash items (stock comp, depreciation) and excludes real cash movements (deferred revenue collections) — it is not net burn.
3. **Compute net new ARR after churn.** New logos plus expansion *minus* churned and contracted ARR. A company adding $5M of new ARR while losing $2M to churn produced $3M of net new ARR, not $5M.
4. **Divide.** Net burn ÷ net new ARR. If net burn is negative (the company is cash-generative), the burn multiple is negative — the best possible result.
5. **Read the trend, not the snapshot.** One efficient quarter can be a billings-timing artifact. Investors look for two to three consecutive quarters of improvement before they trust the number.

## Worked example: the 2026 efficiency reset, with real numbers

Most burn-multiple tutorials stop at a tidy hypothetical. Here is the actual market context — and a real, public, current company that shows where the bar has moved.

The 2026 funding environment did something specific to this metric. Per [CFO Advisors' 2026 benchmarks](https://cfoadvisors.com/blog/2026-burn-multiple-benchmarks-series-a-saas), the Series A **top-quartile threshold dropped from roughly 1.5x in 2025 to 1.2x in 2026**, with the median Series A company at 1.6x. The driver they name is AI-native startups: leaner teams converting capital into ARR faster, structurally resetting what investors consider "good."

At the top end, the reference companies have crossed below zero. Take [CrowdStrike's fiscal 2026](https://ir.crowdstrike.com/news-releases/news-release-details/crowdstrike-reports-third-quarter-fiscal-year-2026-financial):

| Metric | FY2026 value | Source |
|---|---|---|
| Net new ARR (full year) | ~$1.01B (record, first year over $1B) | [CrowdStrike IR](https://ir.crowdstrike.com/news-releases/news-release-details/crowdstrike-reports-third-quarter-fiscal-year-2026-financial) |
| Ending ARR | $5.25B (+24% YoY) | [CrowdStrike 8-K](https://www.sec.gov/Archives/edgar/data/0001535527/000153552726000022/crwd-20260603xex991.htm) |
| Free cash flow (full year) | ~$1.24B (+16% YoY) | [CrowdStrike 8-K](https://www.sec.gov/Archives/edgar/data/0001535527/000153552726000022/crwd-20260603xex991.htm) |

Net burn is *negative* free cash flow, so:

```
Burn Multiple = −$1.24B / $1.01B ≈ −1.2x
```

A negative burn multiple is the graduation certificate: CrowdStrike added more than a billion dollars of net new ARR while generating $1.24B of cash. It funds its own growth and consumes zero outside capital to do it. [Snowflake's Q1 fiscal 2026](https://www.snowflake.com/en/news/press-releases/snowflake-reports-financial-results-for-the-first-quarter-of-fiscal-2026/) tells the same story at a different scale — $996.8M of product revenue up 26%, with $183.4M of positive free cash flow.

The lesson for a private company benchmarking itself: the public comps are no longer burning at all. "We're at 2.0x and growing fast" was a fundable story in 2021. In 2026, with the top quartile at 1.2x and the bellwethers cash-positive, 2.0x is the number you have to *defend*, not celebrate.

(For the arithmetic on a company that is still burning: a startup with $6M of trailing net burn that added $3M of net new ARR after churn has a burn multiple of 2.0x — investable in a large market, but the trend needs to point down.)

## The 2026 burn multiple benchmarks

| Burn multiple | Interpretation | 2026 note |
|---|---|---|
| **< 0** | Cash-generative while still growing ARR — best-in-class | Where public bellwethers (CrowdStrike, Snowflake) now sit |
| **< 1.0x** | Excellent — each $1 burned makes more than $1 of net new ARR | Top-quartile Series A is now ~1.2x, near this |
| **1.0–1.5x** | Great — fundable from strength | Series A median is ~1.6x, so this beats the median |
| **1.5–2.0x** | Efficient — acceptable with strong (150%+) growth | The trend must point down |
| **2.0–3.0x** | Still investable in large markets — but defend it | Harder to raise on than it was in 2021 |
| **> 3.0x** | Broken go-to-market or pre-PMF burn | Requires a specific explanation |

Sources: [CFO Advisors — 2026 Series A burn multiple benchmarks](https://cfoadvisors.com/blog/2026-burn-multiple-benchmarks-series-a-saas), [Wall Street Prep — Burn Multiple (David Sacks)](https://www.wallstreetprep.com/knowledge/burn-multiple/).

## The Burn Multiple Quadrant: why two 3.0x companies need opposite fixes

Here is the diagnostic the benchmark tables miss. A burn multiple is a single number hiding two independent variables — how much you burn, and how much net new ARR you produce. **Two companies can both post 3.0x for completely opposite reasons, and the fix for one is poison for the other.** Plot net burn against net new ARR and the prescription becomes obvious:

| | **High net new ARR** | **Low net new ARR** |
|---|---|---|
| **Low net burn** | **Efficient compounder** — burn multiple < 1. Keep going; this is the goal. | **Starving** — burn looks fine but growth is dead. Fix: *invest more* into a working channel, don't cut. |
| **High net burn** | **Buying growth** — ~1.5–2x. Defensible if the market is huge and the multiple is trending down. | **Capital incinerator** — > 3x. The danger zone. Fix: *cut burn*, the GTM motion isn't converting. |

The quadrant turns the burn multiple from a grade into an instruction:

- A **3.0x from high burn + decent ARR** (top-right drifting down) is a **cost problem** — the growth is real but you're overpaying for it. Cut the burn.
- A **3.0x from modest burn + collapsing ARR** (bottom-left) is a **growth problem** — cutting burn further just accelerates the death spiral. You need to fix conversion, churn, or expansion.

**The Burn Multiple Quadrant's rule: never act on the ratio without decomposing it into its numerator and denominator first.** The same 3.0x means "stop spending" in one quadrant and "spend more, but better" in another. This is why a board should never set a blanket "get the burn multiple under 2.0x" target — it tells a starving company to starve faster.

## When the burn multiple misleads

The burn multiple is a powerful normalizer, but it has blind spots:

- **Early/pre-PMF companies.** Before product-market fit, burn pays for *building the product*, not buying growth. A pre-PMF startup will show an ugly burn multiple because the denominator is near zero — that's expected, not a red flag. Use it once a repeatable sales motion exists. See [Default Alive or Default Dead](/academy/default-alive-or-default-dead) for the trajectory read that fits earlier stages better.
- **Lumpy enterprise bookings.** A single $4M annual contract closing on the last day of the quarter swings the ratio violently. Always use trailing-twelve-month figures for enterprise-heavy companies.
- **It says nothing about profitability or margin.** The burn multiple measures conversion efficiency, not unit economics. Pair it with the [Rule of 40](/glossary/rule-of-40) at scale and with [unit economics](/glossary/unit-economics) — a great burn multiple on structurally unprofitable customers is a trap that closes later.
- **One-time cash events.** A tax refund, a litigation settlement, or a large deferred-revenue collection can flatter net burn for a quarter. Strip non-recurring cash movements before you divide.

## Common burn multiple mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Using GAAP operating loss as net burn | It's the easiest number to grab | Use negative free cash flow — actual cash that left the bank |
| Counting gross new ARR, not net | Churn is uncomfortable to subtract | Net new ARR = new + expansion − churned |
| Mixing a quarterly burn with annual ARR | Careless period matching | Same window for both; trailing twelve months is standard |
| Judging a pre-PMF company by it | The metric looks universal | Apply only once a repeatable sales motion exists |
| Setting a blanket target across the company | Treats the ratio as one variable | Decompose with the Burn Multiple Quadrant first |

## Related reading

The burn multiple is the efficiency vertex of Framework's startup-finance cluster — it's what tells you whether the burn behind your runway is *buying* anything:

- [How to Calculate Burn Rate](/academy/how-to-calculate-burn-rate) — how to get the numerator right, including the financing adjustment that keeps a capital raise from masking real burn
- [Burn Rate](/glossary/burn-rate) — gross vs net burn, the inputs the burn multiple normalizes
- [Cash Runway Formula](/academy/cash-runway-formula) — how long the cash lasts, and the Runway Triangle that pairs duration with this efficiency read
- [Default Alive or Default Dead](/academy/default-alive-or-default-dead) — the trajectory question for earlier-stage companies the burn multiple doesn't fit yet
- [Rule of 40](/glossary/rule-of-40) — the growth-plus-profit efficiency read at scale
- [Unit Economics](/glossary/unit-economics) — whether the ARR you're buying is profitable to serve
- [ARR / MRR](/glossary/arr-mrr) — the recurring-revenue figure in the denominator

When runway tightens and the quadrant says cut, the [RICE scoring method](/academy/rice-score-calculator-with-examples) is the standard tool for ranking which bets survive the budget.

---

> **Run your numbers**: Framework's iOS app keeps net burn, net new ARR, the burn multiple, and its benchmark band in one finance worksheet. [Get it on the App Store](https://apps.apple.com/app/id6765632580).

## Sources

- [Wall Street Prep — "Burn Multiple (David Sacks): Formula + Calculator"](https://www.wallstreetprep.com/knowledge/burn-multiple/)
- [CFO Advisors — "2026 Burn Multiple Benchmarks for Series A SaaS Startups"](https://cfoadvisors.com/blog/2026-burn-multiple-benchmarks-series-a-saas)
- [CrowdStrike — "Fourth Quarter and Full Year Fiscal 2026 Financial Results" (8-K)](https://www.sec.gov/Archives/edgar/data/0001535527/000153552726000022/crwd-20260603xex991.htm)
- [CrowdStrike Investor Relations — Fiscal 2026 results](https://ir.crowdstrike.com/news-releases/news-release-details/crowdstrike-reports-third-quarter-fiscal-year-2026-financial)
- [Snowflake — "Financial Results for the First Quarter of Fiscal 2026"](https://www.snowflake.com/en/news/press-releases/snowflake-reports-financial-results-for-the-first-quarter-of-fiscal-2026/)
- [Corporate Finance Institute — "Burn Multiple: How to Measure Capital Efficiency in SaaS"](https://corporatefinanceinstitute.com/resources/valuation/burn-multiple-capital-efficiency-saas/)

---

### Cash Runway Formula: How to Calculate It, With Examples
URL: https://frameworklist.com/academy/cash-runway-formula
> How to calculate cash runway — the formula, gross vs net burn, a real Lucid Motors Q1 2026 worked example, and the 2026 benchmarks investors actually use to judge it.

The cash runway formula is `cash on hand ÷ net monthly burn`. That division is the easy part. The hard part is knowing *which* cash, *which* burn, and whether the number you get actually describes how long you'll survive — or just how long you'd survive if nothing changed, which never happens.

This page is the formula, the gross-vs-net distinction most founders get wrong, a real worked example using Lucid Motors' Q1 2026 numbers, and the benchmarks investors are using to judge runway in a tight 2026 funding market.

> **Want runway on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a finance-metrics worksheet — drop in cash and burn, see runway and the thresholds below update live. Or start with the [Runway](/glossary/runway) and [Burn Rate](/glossary/burn-rate) glossary entries.

### Prefer to watch or listen?

<YouTube id="HtXRsL14W2s" title="Cash Runway Formula: How to Calculate It (Real Lucid 2026 Example)" />

<Spotify id="6PfwnzC5mnqn7ZxWeQaHdH" title="Cash Runway Formula — Framework podcast episode" />

## The cash runway formula

```
Cash runway (months) = Cash on hand / Net monthly burn
```

**Net burn** is cash going out minus cash coming in, in the same period. For a pre-revenue company, net burn equals gross burn — every dollar of spend is a dollar of depletion. For a revenue-generating company, collected cash offsets some of the spend, and runway stretches accordingly.

The single most common error is dividing by the wrong burn. There are two:

| Burn type | Definition | Runway it produces |
|---|---|---|
| **Gross burn** | Total monthly cash *outflow* — payroll, cloud, marketing, rent, everything | **Gross runway** — the worst case, assumes zero revenue |
| **Net burn** | Gross burn *minus* cash revenue collected that month | **Net runway** — the realistic case used in board decks |

Report both. Net runway is the number you plan around; gross runway is the number you stress-test against, because revenue can disappear faster than costs.

Getting the denominator itself right is a separate discipline — particularly when you derive burn from cash balances rather than a cash flow statement, because a capital raise inside the period makes burn look smaller or even negative. [How to Calculate Burn Rate](/academy/how-to-calculate-burn-rate) covers the four calculation methods and the financing adjustment, with Rivian's Q2 2026 numbers as the worked case.

## How to calculate cash runway (5 steps)

1. **Take cash on hand, not "total assets."** Use cash and liquid equivalents you can actually spend this quarter. Exclude restricted cash, receivables you haven't collected, and an undrawn credit line unless it's committed and accessible.
2. **Sum gross monthly burn.** Every cash outflow: fully-loaded payroll (including founders and execs), infrastructure, marketing, rent, software, taxes. One-time costs count toward depletion even if you label them "one-off."
3. **Subtract cash revenue actually collected.** Not GAAP revenue — *cash*. A SaaS company billing $120K annually upfront collects $120K in month one and $0 in months 2–12, even though it books $10K of revenue each month. Cash burn uses what landed in the bank.
4. **Divide cash by net burn.** That's net runway in months. Divide by gross burn for the worst-case gross runway.
5. **Check the trend, not just the snapshot.** Recompute burn for the last three months. If it's rising, your true runway is shorter than the latest single-month figure implies — see the worked example below for exactly this trap.

## Worked example: Lucid Motors, Q1 2026

Most runway tutorials use a tidy hypothetical startup. Here is a real, public, current one — and it shows why the trend matters more than the snapshot.

In its [Q1 2026 results](https://www.prnewswire.com/news-releases/lucid-announces-first-quarter-2026-financial-results-302763127.html), EV maker Lucid Group reported:

| Metric | Q1 2026 value | Source |
|---|---|---|
| Liquidity at quarter-end | ~$3.2B | [Lucid IR](https://ir.lucidmotors.com/news-releases/news-release-details/lucid-announces-first-quarter-2026-financial-results/) |
| Cash burned in the quarter | ~$1.44B | [Yahoo Finance](https://finance.yahoo.com/markets/stocks/article/lucid-q1-results-miss-estimates-cash-burn-expected-to-continue-as-product-ramp-expands-200534977.html) |
| Cash burned, same quarter prior year | ~$589.9M | [Yahoo Finance](https://finance.yahoo.com/markets/stocks/article/lucid-q1-results-miss-estimates-cash-burn-expected-to-continue-as-product-ramp-expands-200534977.html) |
| Capital raised April 14, 2026 | ~$1.05B | [PR Newswire](https://www.prnewswire.com/news-releases/lucid-announces-first-quarter-2026-financial-results-302763127.html) |

Run the formula. Convert the quarterly burn to monthly: $1.44B ÷ 3 ≈ **$480M/month** of net burn.

```
Cash runway = $3.2B / $480M per month ≈ 6.7 months
```

Roughly **two quarters of cash** at the Q1 pace. That is why Lucid announced a ~$1.05B raise on April 14 — $550M in convertible preferred from PIF affiliate Ayar, $300M in common stock, and a $200M investment from Uber. Pro forma, liquidity rises to ~$4.7B, which resets runway to:

```
Cash runway (pro forma) = $4.7B / $480M per month ≈ 9.8 months
```

Now the lesson the snapshot hides: a year earlier, Lucid burned **$589.9M** in the comparable quarter. Burn *more than doubled* year over year. If you'd calculated Lucid's runway off last year's burn rate, you'd have estimated more than twice the life it actually had. **Runway computed on stale burn is the single most dangerous number on a founder's dashboard** — and Lucid is the textbook case of why you recompute burn every quarter and read the direction, not just the level.

(Lucid is also a special case for a second reason, covered in "When the formula misleads" below: it's majority-backed by Saudi Arabia's Public Investment Fund, so its real survival question isn't the static formula — it's how long until the next sovereign injection.)

## The Runway Triangle: three numbers, not one

Here's the synthesis that ties Framework's finance cluster together. A runway figure in months is necessary but not sufficient. To know whether that runway is *real*, read it as a triangle of three numbers — duration, efficiency, and timing:

| Vertex | The number | Healthy in 2026 | What it catches |
|---|---|---|---|
| **Duration** | Net runway in months | 18+ (24–30 post-raise) | How long the cash lasts at current burn |
| **Efficiency** | [Burn Multiple](/academy/burn-multiple-formula-benchmarks) = net burn ÷ net new ARR | < 1.5 | Whether the burn is *buying* durable growth |
| **Timing** | Does runway clear the fundraise cycle? | Runway > ~23 months | Whether you'll be raising from strength or desperation |

A company can pass any one vertex and still die. Twenty-four months of runway with a Burn Multiple of 4.0 means you have time but you're setting money on fire — investors will see it. A best-in-class Burn Multiple with only 5 months of runway means you're efficient but about to run out before the next raise closes. **The Runway Triangle fails when any single vertex is red, even if the other two are green** — that's the diagnostic. Duration tells you *if* you survive; Efficiency tells you *whether you deserve to*; Timing tells you *whether the market will let you*.

This is why runway should never be reported as a lone number in a board deck. Pair it with the [Burn Multiple](/academy/burn-multiple-formula-benchmarks) (capital efficiency) and, at scale, the [Rule of 40](/glossary/rule-of-40) (growth-plus-profit balance). The three are complementary reads, not substitutes.

## 2026 benchmarks: what counts as a good runway now

The canonical target used to be a flat 18 months. The 2026 market moved it:

| Benchmark | 2026 figure | Source |
|---|---|---|
| Expected post-raise runway | 24–30 months | [The VC Corner](https://www.thevccorner.com/p/startup-cash-runway-model-2026) |
| Median fundraising cycle | ~23 months | [The VC Corner](https://www.thevccorner.com/p/startup-cash-runway-model-2026) |
| Seed SaaS median monthly burn | ~$80K | [The VC Corner](https://www.thevccorner.com/p/startup-cash-runway-model-2026) |
| Seed fintech median monthly burn | ~$120K | [The VC Corner](https://www.thevccorner.com/p/startup-cash-runway-model-2026) |
| Startup failures from cash depletion | 38% | [CB Insights, via Brex](https://www.brex.com/journal/startup-runway) |
| Survival edge of 12+ months runway | 3.5× better odds vs. under 6 months | [The VC Corner](https://www.thevccorner.com/p/startup-cash-runway-model-2026) |

The takeaway: because the median raise now takes ~23 months to come together, a runway under ~18 months puts you back in the market before your current round has had time to produce results. You raise from weakness, which is the worst time to raise.

## When the cash runway formula misleads

The formula is a snapshot of a moving system. Don't trust it blindly in three cases:

- **Burn is accelerating.** The Lucid case. Last period's burn understates next period's, so dividing by the trailing number overstates runway. Fix: use a forward-looking burn forecast with named hires and their start dates, not the trailing average.
- **A strategic backer can inject capital on demand.** For a PIF-backed Lucid, a Microsoft-backed lab, or a corporate-venture-funded subsidiary, the static formula is almost irrelevant — the real question is "how long until the next injection, and on what terms?" The cash-÷-burn number describes the floor, not the plan.
- **Revenue is ramping fast.** If net burn is shrinking 10–15% a month because collections are climbing, this month's net runway *understates* your life — you may cross into cash-flow-positive before you'd hit zero. Model the burn curve, not a flat line.

In all three, the move is the same: replace the single trailing number with a 3-statement forecast, and read it next to the [unit economics](/glossary/unit-economics) — because durable runway ultimately comes from each customer adding cash, not subtracting it.

## Common cash runway mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Dividing by gross burn but calling it net runway | Confuses the two burn types | Subtract collected cash first; report both runways |
| Counting GAAP revenue as cash | Annual-billed SaaS books revenue it hasn't collected | Use cash actually in the bank |
| Using last single month's burn | One quiet month flatters the number | Average the trailing three; check the trend |
| Treating an undrawn credit line as cash | It looks like available money | Only count committed, accessible facilities |
| Reporting runway as one lone number | Hides efficiency and timing risk | Use the Runway Triangle — duration + Burn Multiple + raise-cycle fit |

## Related reading

Runway is the survival metric, but it's downstream of the inputs Framework's finance glossary covers in depth:

- [Runway](/glossary/runway) — the thresholds (18 / 12 / 6 months) and what founders do at each
- [Default Alive or Default Dead](/academy/default-alive-or-default-dead) — the trajectory read on this same number: do you reach profit before the cash runs out?
- [Burn Multiple](/academy/burn-multiple-formula-benchmarks) — net burn ÷ net new ARR, the 2026 benchmarks, and the quadrant that diagnoses *why* a burn multiple is bad
- [How to Calculate Burn Rate](/academy/how-to-calculate-burn-rate) — the three burn formulas, the financing-adjusted method, and the Three-Number Burn Check
- [Burn Rate](/glossary/burn-rate) — gross vs net burn, the inputs behind the burn multiple
- [Unit Economics](/glossary/unit-economics) — whether each customer extends or shortens runway
- [Rule of 40](/glossary/rule-of-40) — the growth-plus-profit efficiency read at scale
- [Payback Period](/glossary/payback-period) — how fast CAC returns as cash, the lever that turns burn into runway

For prioritizing *what to cut* when runway tightens, the [RICE scoring method](/academy/rice-score-calculator-with-examples) is the standard tool for ranking which bets survive a budget cut.

---

> **Run your numbers**: Framework's iOS app keeps cash, burn, runway, and the Runway Triangle in one finance worksheet. [Get it on the App Store](https://apps.apple.com/app/id6765632580).

## Sources

- [Lucid Group — "Lucid Announces First Quarter 2026 Financial Results"](https://www.prnewswire.com/news-releases/lucid-announces-first-quarter-2026-financial-results-302763127.html)
- [Lucid Investor Relations — Q1 2026 financial results](https://ir.lucidmotors.com/news-releases/news-release-details/lucid-announces-first-quarter-2026-financial-results/)
- [Yahoo Finance — "Lucid Q1 results miss estimates; cash burn expected to continue"](https://finance.yahoo.com/markets/stocks/article/lucid-q1-results-miss-estimates-cash-burn-expected-to-continue-as-product-ramp-expands-200534977.html)
- [The VC Corner — "Startup Cash Runway Model 2026: Stay Funded Longer"](https://www.thevccorner.com/p/startup-cash-runway-model-2026)
- [Brex — "3 ways to extend your startup runway and reduce cash burn"](https://www.brex.com/journal/startup-runway)

---

### Covey Time Management Matrix: 4 Quadrants & Examples
URL: https://frameworklist.com/academy/covey-time-management-matrix
> Covey's Time Management Matrix explained: the 4 quadrants (Necessity, Quality, Deception, Waste), how to run it, and why Quadrant II stays empty.

The **Covey Time Management Matrix** is a 2×2 grid that sorts how you spend your time by two axes — urgency and importance — into four quadrants: **Necessity, Quality, Deception, and Waste**. Stephen Covey introduced it in *The 7 Habits of Highly Effective People* (1989), and its central claim is unusually specific for a productivity model: your effectiveness is determined almost entirely by how much time you spend in **Quadrant II** — the important work that is not yet urgent.

It shares its axes with the [Eisenhower Matrix](/frameworks/eisenhower), and the two are constantly confused. The difference is job, not shape: Eisenhower triages the tasks in front of you today, Covey diagnoses where your months are going.

> **Want to run the grid on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=covey-matrix) fills in an urgent/important grid with AI-assisted sorting, so you can map a week's calendar into quadrants in a couple of taps. Free to start.

<CoveyMatrix />

## The four quadrants, by what each one does to you

Covey's labels describe a quadrant's **nature** — what it is doing to your effectiveness — rather than the action you should take. That is the whole design. Naming Q3 "Deception" is an argument, not a category.

| Quadrant | Axes | Covey's name | What lives here | What it does to you |
|---|---|---|---|---|
| **Q1** | Urgent + Important | **Necessity** | Genuine crises, hard deadlines, escalations, emergencies | Unavoidable, but a permanently large Q1 means burnout and reactive drift |
| **Q2** | Not urgent + Important | **Quality** *(also Effectiveness or Leadership)* | Planning, prevention, documentation, relationships, learning, health | The only quadrant that compounds — and the only one nothing forces you to do |
| **Q3** | Urgent + Not important | **Deception** | Most interruptions, many meetings, broadcast messages, other people's priorities | Feels like Q1 while you're in it; produces exhaustion without progress |
| **Q4** | Not urgent + Not important | **Waste** | Trivia, doomscrolling, busywork, escape activities | Where you land when Q1 and Q3 have drained you — a symptom, not a cause |

The counterintuitive move is the relationship between Q1 and Q2. Covey argued Q1 is not reduced by getting better at Q1. It shrinks when Q2 grows, because prevention, planning and maintenance stop things from reaching crisis in the first place. A team that never has time to write documentation will keep having outages that demand heroics — and the heroics are what prevent the documentation.

## The Infinite Workday Quadrant Map

Covey published in 1989 and had no telemetry — only observation. Microsoft now publishes both survey research and anonymized Microsoft 365 usage signals at scale, which makes it possible to ask a question Covey couldn't: **which quadrant is actually growing?**

Mapping Microsoft WorkLab's [infinite workday](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday) findings onto Covey's grid produces a clear and slightly uncomfortable answer.

| Measured signal | Quadrant it lands in | Why |
|---|---|---|
| Interrupted every **2 minutes** by meetings, email or notifications | **Q3** | Interruption is urgency by definition; almost none of it is important |
| Mass emails (20+ recipients) up **7%** YoY while one-to-one threads fell **5%** | **Q3 growing, Q1/Q2 shrinking** | Broadcast is the signature of low-importance urgency; 1:1 threads are where real work is negotiated |
| **57%** of meetings are ad hoc, with no calendar invite | **Q3** | Unscheduled means unplanned, which usually means someone else's urgency |
| **50%** of all meetings fall in 9–11am and 1–3pm | **Q2 evicted** | Those are the two peak-focus windows; Q2 needs uninterrupted blocks and has been zoned out of them |
| PowerPoint edits spike **122%** in the final 10 minutes before a meeting | **Q1 manufactured by Q2 neglect** | Prep that should have been scheduled becomes a crisis at the deadline |
| Meetings after 8pm up **16%** YoY; **29%** back in the inbox by 10pm | **Q1/Q3 spillover** | The day didn't get longer because crises grew — it got longer because Q3 pushed everything else out |
| **48%** of employees and **52%** of leaders describe work as "chaotic and fragmented" | The subjective read | Fragmentation is the felt experience of Q3 saturation |

**The map's conclusion: the infinite workday is a Quadrant III problem that almost everyone misdiagnoses as a Quadrant I problem.** People finish these days genuinely depleted and describe them as firefighting. But the components that actually grew — broadcast messages, ad hoc meetings, after-hours pings — are urgent-but-not-important. Real crises did not multiply. Interruption did.

That distinction matters because the two have opposite treatments. A Q1 problem is solved by capacity: more people, better triage, faster response. A Q3 problem is made *worse* by all three, because faster response to interruption produces more interruption.

One honest caveat: "mass email up, 1:1 down" is a strong indicator of Q3 growth, not a proof of it — some broadcast messages carry genuinely important information, and Microsoft's data measures volume and timing rather than importance. The direction is well-evidenced; treat the quadrant assignment as a well-supported reading rather than a measured fact.

## Worked example: Microsoft's own diagnosis

The most useful case for this framework is the company that produced the data, because it also published what it concluded — and the conclusion is Covey's, arrived at independently.

Microsoft's [2026 Work Trend Index](https://www.microsoft.com/en-us/worklab/work-trend-index/agents-human-agency-and-the-opportunity-for-every-organization) (published 5 May 2026, based on 20,000 knowledge workers across 10 markets surveyed by Edelman Data x Intelligence between 18 February and 7 April 2026) found that **organizational factors — culture, manager support, talent practices — account for 67% of AI's real impact, against 32% for individual mindset and behaviour**. The report's summary line is blunt: *"In many cases, people are ready. The systems around them are not."*

Run that through the matrix:

- **The individual-willpower theory of Q2** says people fail to do important-not-urgent work because they lack discipline. If that were right, individual mindset would dominate the outcome.
- **Covey's actual theory** — the one most summaries drop — is that Q2 is a *systems* problem. He built the weekly planning ritual, the roles-first structure, and the "big rocks first" sequencing precisely because he did not think willpower survived contact with a calendar someone else controls.
- Microsoft's split puts organizational factors at **more than twice** the weight of individual ones. That is the strongest quantitative support Covey's systems claim has ever had, and it arrived 37 years after the book.

The same report found only **26% of AI users** say their leadership is clearly and consistently aligned on AI — a Q2 failure in its purest form. Alignment is important, has no deadline, and is therefore the first thing to be postponed indefinitely.

The practical read for a team: if your Q2 is empty, auditing individual habits is the low-yield intervention. Auditing meeting defaults, notification norms, and who is allowed to interrupt whom is the high-yield one.

## How to run the matrix in a week

Covey's matrix is a diagnostic before it is a planning tool, so run it on where your time *went* before you use it on where it should go.

1. **Log two weeks backwards, not forwards.** Export your actual calendar and pull your sent-message volume. Memory systematically under-reports Q3 because interruptions don't leave calendar entries — the 57% ad-hoc meeting figure exists precisely because those meetings are invisible in planning tools.
2. **Assign every block to a quadrant, and force the Q1/Q3 call.** For each item ask: *if this had been delivered a week late, what would have actually broken?* If the honest answer is "nothing, but someone would have been annoyed," it is Q3, not Q1. This single question does most of the work.
3. **Total the four quadrants as percentages.** Covey's rough target is a large Q2 and a small Q3; most knowledge workers who run this honestly find Q3 is their largest quadrant and are surprised by it.
4. **Find the Q3 generators, not the Q3 items.** Individual interruptions are symptoms. Look for the source: a channel with broadcast norms, a recurring meeting with no agenda, a default that makes you the escalation path. Cutting one generator removes dozens of items.
5. **Schedule Q2 into the peak windows first.** Since half of all meetings land in 9–11am and 1–3pm, Q2 work placed anywhere else competes with depleted attention. Book the blocks before the week fills, and treat them as immovable as a customer meeting.
6. **Re-run the audit after a month.** The measurable success signal is not "more Q2 hours" — it is **Q1 shrinking**, which is the delayed effect of Q2 prevention. If Q1 hasn't moved after a quarter, your Q2 blocks are being spent on disguised Q3.

## When the Covey Matrix isn't the right tool

- **When everything genuinely is on fire right now.** During an outage, a launch week or a funding crunch, a philosophy of long-term rebalancing is the wrong altitude. Use the [Eisenhower Matrix](/academy/eisenhower-matrix-urgent-vs-important) to triage and route today's list, then come back to Covey when the fire is out.
- **When the problem is workflow, not priorities.** If work is being dropped because it isn't captured anywhere, no quadrant model will help — that's a system-of-record problem. See [Eisenhower vs GTD](/compare/eisenhower-matrix-vs-gtd) for the prioritization-versus-workflow split.
- **When you need to rank comparable initiatives.** Covey has no scoring mechanism; it sorts by kind, not by value. For ranking a product backlog, a weighted model like [RICE](/frameworks/rice) or [MoSCoW](/compare/rice-vs-moscow) is the right instrument.
- **When you don't control your calendar.** For frontline, clinical, or shift-based roles, most of the day is externally assigned. The matrix still diagnoses accurately, but the lever sits with whoever designs the schedule — which is the systems point above, in its sharpest form.

## Common mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Labelling Q3 as Q1 | Urgency is loud and importance is silent, so the nervous system misclassifies in real time | Apply the one-week-late test in step 2 — "what would actually have broken?" |
| Treating Q2 as leftover time | Q2 is the only quadrant with no external deadline, so it's the only one that can be postponed forever | Schedule Q2 first, into peak-attention hours, before the week fills |
| Trying to fix Q3 with personal discipline | Q3 is generated by other people's systems and norms, not your habits | Cut generators, not items; Microsoft's 67%-vs-32% split is the evidence |
| Chasing Q4 as the villain | Q4 looks like the obvious waste, so it attracts the effort | Q4 is a symptom of Q1/Q3 depletion — it shrinks on its own when the others do |
| Measuring success as "more Q2 hours" | It's the visible number, so it's the one people track | Track Q1 shrinking instead; that's the delayed proof that Q2 prevention is working |
| Using Covey to sort a task list | It has the same grid as Eisenhower, so it looks like a task tool | Use [Eisenhower for triage](/compare/eisenhower-matrix-vs-covey-matrix), Covey for calendar diagnosis |

## Related frameworks

- [Eisenhower Matrix vs Covey Matrix](/compare/eisenhower-matrix-vs-covey-matrix) — the full head-to-head, including which to reach for at which altitude
- [Eisenhower Matrix explained](/academy/eisenhower-matrix-urgent-vs-important) — the four action quadrants and a 30-minute run-through
- [Eisenhower Matrix vs GTD](/compare/eisenhower-matrix-vs-gtd) — prioritization versus workflow
- [Eisenhower Matrix vs Impact/Effort Matrix](/compare/eisenhower-matrix-vs-impact-effort-matrix) — execution layer versus selection layer
- [Eisenhower Matrix catalog entry](/frameworks/eisenhower) — the diagram, template and iOS app

## Sources

- [Microsoft WorkLab — "Breaking down the infinite workday"](https://www.microsoft.com/en-us/worklab/work-trend-index/breaking-down-infinite-workday) — Microsoft 365 telemetry on interruption cadence, meeting distribution, and after-hours activity
- [Microsoft WorkLab — "2026 Work Trend Index: Agents, human agency, and the opportunity for every organization"](https://www.microsoft.com/en-us/worklab/work-trend-index/agents-human-agency-and-the-opportunity-for-every-organization) — published 5 May 2026; 20,000 knowledge workers across 10 markets, surveyed by Edelman Data x Intelligence, 18 February–7 April 2026
- Stephen R. Covey, *The 7 Habits of Highly Effective People* (Free Press, 1989) — Habit 3, "Put First Things First," where the matrix and the Quadrant II argument are introduced

---

### Cynefin Framework for PMP: matching project approach to context
URL: https://frameworklist.com/academy/cynefin-framework-for-pmp
> The Cynefin Framework appears in the PMP exam because it tells you which methodology to use. Here are the five domains, how to map a project to each, and a worked PMP-style scenario.

The Cynefin Framework (pronounced *ku-NEV-in*, from Welsh for "habitat") is one of the few PMP-relevant tools that tells you *what methodology to choose* rather than how to execute the one you've already picked. It was developed by Dave Snowden at IBM in 1999, published in the November 2007 *Harvard Business Review*, and incorporated into PMBOK Guide 7th Edition as the framework for matching project approach to context.

For the PMP exam, the question is rarely "what is Cynefin?" — it's "given this scenario, which domain applies and which approach does that imply?" This guide is structured around answering exactly that question.

> Want to apply Cynefin on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?mt=8) ships a Cynefin worksheet with the domain definitions built in.

### Prefer to watch or listen?

<YouTube id="dis_Tp-oGgE" title="Cynefin Framework for PMP: matching project approach to context" />

<Spotify id="38fhN6HIjPUNTjb3aY5PSO" title="Cynefin Framework for PMP — Framework podcast episode" />

## The five domains

Cynefin sorts every project situation into one of five domains. The first four describe the *nature* of cause and effect; the fifth is the state of not knowing which domain applies.

### 1. Clear (Obvious / Simple)

**Cause and effect**: known, repeatable, established.
**Decision approach**: sense → categorize → respond.
**Project management style**: waterfall, predictive.
**Examples**: payroll processing, regulatory filing, standard construction, ITIL operations.

In the Clear domain, best practices exist and apply. The PM's job is to recognize the pattern and follow the established procedure. Most operational work and routine project work lives here.

### 2. Complicated

**Cause and effect**: knowable, but requires expertise to analyze.
**Decision approach**: sense → analyze → respond.
**Project management style**: predictive with expert-driven planning; some hybrid methods.
**Examples**: building a bridge, designing an ERP rollout, running a clinical trial, implementing a major migration.

In the Complicated domain, there are multiple valid solutions, and finding the right one requires investigation and expertise. This is the natural home of traditional project management — work breakdown structures, critical-path analysis, expert estimation, gated approvals. Good practices exist here, but not single best practices.

### 3. Complex

**Cause and effect**: only knowable in retrospect.
**Decision approach**: probe → sense → respond.
**Project management style**: agile, scrum, iterative, hypothesis-driven.
**Examples**: launching a new product, entering a new market, leading organizational change, running early-stage R&D.

In the Complex domain, the system has too many interacting variables for any plan to survive contact with reality. You can't analyze your way to the answer; you can only run small probes, see what happens, and amplify what worked while damping what didn't. This is where agile methodologies earn their keep, because they're structured around exactly this loop.

### 4. Chaotic

**Cause and effect**: unclear or absent.
**Decision approach**: act → sense → respond.
**Project management style**: command-and-control, emergency response, crisis management.
**Examples**: cyberattack in progress, factory fire, public health emergency, sudden regulatory shutdown.

In the Chaotic domain, the priority is to stop the bleeding. You act first to stabilize, then sense what happened, then respond with a plan. Novel practices emerge here — what you learn becomes input to the next disaster.

### 5. Confused (Aporia / Disorder)

**Cause and effect**: not yet known which of the other four applies.
**Decision approach**: break the situation into smaller pieces and classify each one.

The Confused domain is the meta-domain. When a project feels overwhelming, it's usually because parts of it belong to different Cynefin domains and the team is trying to use one approach for all of them.

## How to map a project to a domain

Five diagnostic questions, asked of the project as a whole:

1. **Has anyone done this exact thing before, in this exact context?** → Clear
2. **Has anyone done a similar thing? Can experts analyze and plan it in advance?** → Complicated
3. **Is the outcome dependent on many interacting variables you can't fully model in advance?** → Complex
4. **Is the situation actively damaging value, with no time for analysis?** → Chaotic
5. **Different parts of the project answer differently to questions 1–4?** → Confused — break it apart

If you answer "Complex" to question 3 but find yourself building a 6-month Gantt chart, that's the misclassification PMs make most often. The Gantt is a Complicated-domain tool used on a Complex-domain problem; it will produce false confidence and a schedule that the actual work won't honor.

## A worked PMP-style scenario

Read this scenario and try to classify it before reading the analysis below.

> *Your company has acquired a smaller competitor with overlapping product lines, an incompatible CRM, and a strong but distinct engineering culture. The CEO wants integration completed in 9 months. Three workstreams have been identified: (a) consolidating the two CRMs onto one platform, (b) merging the product roadmaps, and (c) integrating the engineering teams into a single organization. Which Cynefin domain applies, and what approach would you recommend?*

**The Cynefin answer**: this is a Confused-domain situation that decomposes into three sub-projects in different domains.

- **CRM consolidation (Complicated)**: known cause-and-effect, requires expertise. Run as a traditional predictive project with a CRM specialist, a data migration plan, and gated approvals. Use a [RICE](/academy/rice-prioritization-framework)-style scoring matrix for the migration sequence if needed.
- **Product roadmap merge (Complex)**: depends on customer reaction, internal politics, and external competitive moves that can't be predicted. Run as iterative discovery — start with a 90-day hypothesis ("we believe X customers value Y; we'll test by Z"), measure, adapt. This is the wrong place for a 9-month Gantt.
- **Engineering culture integration (Complex, leaning Chaotic in early weeks)**: human systems are inherently complex. The first 30 days post-acquisition often have Chaotic moments (key engineers leaving) that need command-and-control response. After stabilization, treat as ongoing Complex work with retrospectives, embedded leaders, and slow merging of practices.

A PM who treats this as a single Complicated project — 9-month integrated Gantt with a CRM lead, a product lead, and an engineering lead all reporting to a steering committee — is using the wrong domain's tools for two of the three workstreams. The Gantt will hold for CRM and fall apart for the other two. The integration will look "on track" until month 7, when the Complex workstreams reveal they were never on the planned trajectory.

This is the most common PMP-relevant Cynefin pattern: a major program that the org wants to manage as one thing, but that the framework reveals to be three things requiring three approaches.

## When NOT to use Cynefin

- **For status reporting to executives** who want a single percent-complete number. Cynefin will tell you that 30% of the work is on a predictable timeline and 70% can't be percent-complete-estimated. That's the right answer; it's also the wrong message for a board meeting. Translate Cynefin's diagnosis into language stakeholders can act on, but don't try to make Cynefin produce a single number.
- **For small, single-team projects with clear deliverables**. The classification overhead is wasted; just pick agile or predictive based on requirements stability and ship.
- **In organizations actively hostile to "it depends" answers**. Cynefin's whole value is saying *match the approach to the context* — which means the answer is always *it depends*. Some organizations would rather have a single methodology applied uniformly than do the diagnostic work, and Cynefin will be politically rejected before it's analytically applied.

## Common mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Classifying Complex as Complicated | Complex feels uncomfortable; analysis feels safer | Ask "can a sufficiently expert person analyze this in advance with high confidence?" If no, it's Complex. |
| Skipping the Confused domain | Teams want a single classification | If different stakeholders disagree on domain, the project is Confused. Decompose first, classify second. |
| Treating Chaotic as Crisis Management Forever | Initial response feels effective | Chaotic is the *first 24 hours*. After stabilization, the situation moves to Complex. Continuing to act-sense-respond past stabilization burns the team out. |
| Mapping the framework once and never revisiting | Cynefin feels like a one-time diagnostic | Projects move between domains as they progress. A Complicated project hits a Complex sub-problem; a Chaotic stabilization moves into Complex; classify per phase, not per project. |
| Using Cynefin to justify what you were going to do anyway | Framework as decoration | If your Cynefin diagnosis happens to confirm every methodology choice you already preferred, you probably skipped step 2 ("analyze") in the Complicated domain or step 1 ("probe") in the Complex domain. |

## Cynefin and PMBOK 7 in practice

PMBOK 7 incorporated Cynefin specifically because the older lifecycle-based selection criteria (predictive vs. iterative vs. agile) didn't address *why* you'd choose one. Cynefin gives the *why*. In practice, the integration looks like this:

- **Clear and Complicated domains** → PMBOK predictive lifecycle, traditional WBS, EVM, gated approvals
- **Complex domain** → PMBOK adaptive/agile lifecycle, iterative delivery, hypothesis-driven planning, retrospectives
- **Chaotic domain** → not a steady-state lifecycle; emergency response patterns until stabilized into Complex
- **Confused domain** → decompose the project into pieces and apply the above to each piece

If you're studying for PMP, this mapping is what most scenario questions are testing. The question gives you the project context; you identify the Cynefin domain; you select the PMBOK lifecycle that matches.

## The Cynefin → PMBOK 7 Lifecycle Map

The mapping above is the actual diagnostic PMP scenario questions test. As a citable table:

| Cynefin domain | PMBOK 7 lifecycle | Scenario-language signals (PMP exam) | Primary artifact | Misclassification trap |
|---|---|---|---|---|
| **Clear** | Predictive (waterfall) | "standard process", "established procedure", "routine", "regulatory filing", "repeatable" | Checklist + WBS | Treating it as Complicated by over-analyzing — wastes effort on known-knowns |
| **Complicated** | Predictive with expert-driven analysis; some hybrid | "requires expertise", "multiple stakeholders", "subject-matter experts", "gated approvals", "ERP / migration / clinical trial" | Critical-path Gantt, EVM, expert review | Treating it as Complex — running sprints on work that has a knowable answer |
| **Complex** | Adaptive (agile / iterative) | "emergent requirements", "unclear outcomes", "new market", "organizational change", "innovation", "high uncertainty" | Hypothesis-driven backlog, sprints, retrospectives | **The most-tested trap on the PMP exam** — treating Complex as Complicated by building a 6-month Gantt for work that can only be probed |
| **Chaotic** | Emergency response (not a steady-state lifecycle) | "cyberattack", "factory fire", "outage", "public-health emergency", "immediate action required" | Incident command, rapid stabilization protocols | Continuing to act-sense-respond past stabilization — the situation moves to Complex after the first 24-72 hours |
| **Confused** | Decompose then apply the above per piece | "the team is overwhelmed", "different parts of the project look different", "stakeholders disagree on approach", "merger / integration with multiple workstreams" | A decomposition map (which sub-project belongs to which domain) | Trying to pick one lifecycle for the whole thing — the project is genuinely multi-domain and needs separate plans |

How to use the table on a PMP scenario question:

1. **Read the scenario for the signal-language column.** Most scenario questions plant 2-3 phrases that point at a specific Cynefin domain.
2. **Pick the domain.** Cross-reference to the lifecycle column.
3. **If the question asks "which approach?" — answer the lifecycle.** If it asks "what's the risk?" — answer the misclassification trap row.
4. **For multi-workstream scenarios (merger, transformation, large program)**, the answer is almost always Confused → decompose, even if the test offers Complicated as a distractor.

The Complex → Complicated misclassification (row 3 of the table) is the highest-yield exam pattern. PMP scenario questions deliberately mix Complex signals ("new product", "innovation", "first time", "uncertain market") with Complicated artifacts ("Gantt chart already built", "PMO requires a baseline schedule") to test whether the candidate defers to artifact-thinking or to context-thinking. The framework's answer is always context first.

## Related frameworks

- [Cynefin vs Stacey Matrix](/compare/cynefin-vs-stacey-matrix) — the Stacey Matrix diagnoses *why* a project is uncertain (knowledge gap or disagreement); Cynefin prescribes the response. Run them in sequence.
- [Premortem](/academy/how-to-run-a-premortem) — Cynefin's natural partner for Complex domain risk surfacing
- [Premortem vs Postmortem](/compare/premortem-vs-postmortem) — when to run each in the project lifecycle
- [Pareto Analysis (80/20 Principle)](/academy/pareto-analysis-80-20-principle) — the canonical analytical tool inside a Complicated-domain workstream
- [Reverse Brainstorming](/academy/reverse-brainstorming-solve-problems-backwards) — inversion-style risk surfacing for Complex problems where premortems are too heavyweight
- [RICE](/academy/rice-prioritization-framework) — for prioritizing inside a Complicated-domain backlog
- [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) — strategic-domain analysis that complements Cynefin's project-domain framing
- [JTBD](/academy/jobs-to-be-done-framework-explained) — Complex-domain discovery tool for new product workstreams

## Sources

- Snowden, D. & Boone, M. — "A Leader's Framework for Decision Making," *Harvard Business Review*, November 2007
- PMI — *PMBOK Guide, 7th Edition* (Cynefin appears in the "Tailoring" section)
- PMI Library — "Dancing in the Kaleidoscope" (2014 paper on leading complex projects)
- The Cynefin Co. — current canonical definitions and domain renames (Obvious → Clear, ~2014)

> Want to run Cynefin diagnostics on your real projects? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?mt=8) ships a Cynefin domain mapper with the diagnostic questions built in. Or open the [Cynefin catalog entry](/frameworks/cynefin) for the worksheet template.

---

### Default Alive or Default Dead: How to Tell Which You Are
URL: https://frameworklist.com/academy/default-alive-or-default-dead
> Paul Graham's default alive vs default dead test, the trajectory math behind it, and three real 2026 cases — Figma (alive), OpenAI (dead by design), Humane (dead by accident).

"Default alive or default dead?" is the single most useful question Paul Graham ever put to founders — and most can't answer it, which is the whole problem. It asks whether your startup, on its **current** growth and spending path, will reach profitability before the cash runs out. Not whether you *could* survive if you raised again. Whether you survive if you don't.

This page is the test, the trajectory math that separates it from a plain [runway](/glossary/runway) number, the named diagnostic for when default dead is actually fine, and three real 2026 cases that land on three different verdicts.

> **Want to run the numbers on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a finance worksheet — drop in cash, burn, and growth rate and see your profitability-vs-runway crossover. Or start with the [Cash Runway Formula](/academy/cash-runway-formula) and [Burn Rate](/glossary/burn-rate) explainers.

## What default alive and default dead mean

Paul Graham [coined the terms](https://www.paulgraham.com/aord.html) in a 2015 essay. The definitions are deceptively simple:

| State | Definition | The honest reading |
|---|---|---|
| **Default alive** | On current growth and burn, you reach profitability *before* cash runs out | You control your own survival; a raise is an accelerator, not a lifeline |
| **Default dead** | On current growth and burn, cash runs out *before* you reach profitability | Your survival depends on someone else saying yes — to a raise, an acquisition, or a backer's injection |

The word that does all the work is **default**. It means "if nothing changes." Founders constantly answer the *wrong* question — "could we survive?" — to which the answer is always yes, because you can always imagine a raise. Graham's question strips out the imagined rescue and asks what happens on the path you're actually on.

## Why this is not the same as runway

[Runway](/glossary/runway) is a snapshot: cash ÷ net burn, holding everything constant. Default alive is a **trajectory**: it asks whether your growth curve crosses your cost curve before the runway snapshot expires.

The difference is decisive, and a single example shows why. Take two startups, each with $2M in the bank and each burning $200K net per month. Both have an identical **10-month runway**.

| | Startup A | Startup B |
|---|---|---|
| Cash | $2M | $2M |
| Net burn (now) | $200K/mo | $200K/mo |
| Runway (static) | 10 months | 10 months |
| Monthly revenue growth | +15% | ~0% |
| Net burn in 6 months | shrinking toward zero | still $200K |
| **Verdict** | **Default alive** | **Default dead** |

Same runway, opposite fates. Startup A's revenue is climbing fast enough that net burn shrinks every month — it crosses into profit around month 8, before the cash is gone. Startup B's flat revenue means the 10-month runway is the whole story, and month 11 is a wall. **Runway tells you how long you have; default alive tells you whether that's long enough.** Reading runway without the growth rate is the most common way founders fool themselves into feeling safe.

## How to tell which you are (5 steps)

1. **Take current monthly revenue and its growth rate.** Use the trailing 3-month average growth, not a single hot month.
2. **Project revenue forward, month by month.** Compound the growth rate. Be honest that growth rates decay as you get bigger.
3. **Project expenses forward, including planned hires.** A hire you've committed to is a cost even before they start. This is where optimistic founders cheat.
4. **Find the crossover month** — the first month projected revenue exceeds projected expenses. That's your profitability date.
5. **Compare it to your runway.** If profitability lands before cash hits zero, you're default alive. If runway runs out first, you're default dead — and now you know by how much, which tells you how much to cut or raise.

Graham's essay ships a [calculator](https://www.paulgraham.com/aord.html) that does exactly this with a growth-rate slider. The output that matters isn't the date — it's the *gap*. A default-dead company that's two months short is a different problem from one that's two years short.

## The Default-Dead-by-Design Test

Here's the synthesis Graham's original essay gestures at but never names: **being default dead is not automatically a death sentence.** The world's most valuable private companies are default dead *on purpose*. What separates a legitimate strategy from a slow-motion failure is **intentionality plus a funded bridge**. Run any default-dead company through three yes/no questions:

| # | Question | Why it matters |
|---|---|---|
| 1 | **Did you choose to be default dead** to capture a market faster than profitability allows? | An accident you haven't noticed is the most dangerous state of all |
| 2 | **Is the bridge funded** — do you have committed capital or a backer who will fund the gap to profitability? | Intent without capital is just hope; the gap has to be someone's commitment |
| 3 | **Is the trajectory real** — is revenue actually growing fast enough that profitability is a *date*, not a *someday*? | A funded bridge to nowhere still ends at nowhere |

**Three yeses: default dead by design — a defensible strategy.** Two or fewer: you are default dead by *accident*, and the gap between you and the giants isn't ambition, it's that you skipped one of these and didn't notice. The test works because it isolates the only thing that makes outspending revenue survivable — **a deliberate choice backed by committed capital and a real growth curve** — from the thing that looks identical from the outside but kills you: drift.

## Three real cases, three verdicts

### Figma — default alive

By its [2025 IPO S-1](https://www.sec.gov/Archives/edgar/data/0001579878/000162828025033742/figma-sx1.htm), Figma was unambiguously default alive: FY2025 revenue of roughly **$1.06B** (growing ~40% year over year), **non-GAAP operating income of $129.5M** (a 12% margin), and **adjusted free cash flow of $242.7M** — a 23% margin. It held **$1.7B in cash** it did not need to touch, and posted a [Rule of 40](/glossary/rule-of-40) score of **74**, the second-highest among public cloud companies. Figma generates more cash than it spends. For a default-alive company, a raise (or in Figma's case, a public listing) is an accelerant, not oxygen — which is exactly why it could go public from a position of strength rather than need.

### OpenAI — default dead by design

OpenAI is the textbook case of passing all three Default-Dead-by-Design questions. It is nowhere near profitable: it expects to burn about **$8B in 2025**, [more than doubling to $17B in 2026](https://finance.yahoo.com/news/openais-own-forecast-predicts-14-150445813.html), on the way to a reported **$115B in cumulative burn through 2029**. That is default dead by any static reading. But (1) it is *deliberate* — outspending revenue to win the AI platform race; (2) the bridge is *funded* by some of the largest capital commitments in private-market history; and (3) the trajectory is *real* — annualized revenue crossed **~$12B in 2025**, roughly doubling inside the year, with cash-flow positivity targeted for **2029** on projected revenue above **$125B**. Three yeses. OpenAI is default dead and that is the plan, not the problem. The only thing that turns this strategy fatal is if the trajectory stalls before the bridge runs out.

### Humane — default dead by accident

Humane is the warning. The AI-hardware startup [raised about $230M](https://www.theverge.com/2025/2/18/24107959/hp-humane-ai-pin-acquisition) from backers including Sam Altman and Marc Benioff, shipped the AI Pin to scathing reviews in April 2024, and was sold to HP for **$116M in assets** in February 2025 with the device discontinued. It had capital — it failed question 3. There was no real trajectory: no retention, no organic pull, no growth curve bending toward profitability. A funded bridge to a market that wasn't there still ends where the market isn't. Money bought runway; it could not manufacture the trajectory that makes default dead survivable.

## When the question misleads

- **Pre-product-market-fit, the growth rate is noise.** Before [product-market fit](/glossary/product-market-fit), your revenue growth is too erratic to project — the crossover math is built on a number you don't really have. Get to PMF first; *then* the default-alive question becomes answerable. See [product-market fit examples](/academy/product-market-fit-examples).
- **A committed backer changes the question entirely.** For a sovereign-backed or strategically-backed company, the static math is almost beside the point — the real question is "how long until the next injection, and on what terms?" (the [Lucid case](/academy/cash-runway-formula) in our runway guide).
- **Decaying growth breaks naive projections.** Compounding a 15% monthly growth rate forward for two years produces a fantasy. Growth rates fall as you scale; model the decay or your "default alive" verdict is fiction.

## Common default-alive mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Answering "could we survive?" instead of "will we?" | You can always imagine a raise | Strip out the imagined rescue; ask what happens if you *don't* raise |
| Using runway without the growth rate | A runway number feels concrete and safe | Always read runway next to monthly growth — they're one question |
| Compounding today's growth rate forever | Optimism plus a spreadsheet | Decay the rate as revenue scales; sanity-check the 24-month figure |
| Excluding committed-but-unstarted hires from the burn forecast | They're "not costs yet" | A signed offer is a cost; put it in the projection |
| Assuming default dead means failing | The label sounds terminal | Run the Default-Dead-by-Design Test — intentional + funded + real trajectory is a strategy |

## Related reading

Default alive is the trajectory read on the same numbers Framework's finance cluster covers statically:

- [Cash Runway Formula](/academy/cash-runway-formula) — the static calculation, gross vs net burn, and the Runway Triangle
- [Runway](/glossary/runway) — the 18 / 12 / 6-month thresholds and what founders do at each
- [Burn Rate](/glossary/burn-rate) — gross vs net burn and the Burn Multiple
- [Rule of 40](/glossary/rule-of-40) — the growth-plus-profit efficiency read Figma scored 74 on
- [Product-Market Fit Examples](/academy/product-market-fit-examples) — why the default-alive question is unanswerable before PMF

When runway tightens and you're default dead by accident, [RICE scoring](/academy/rice-score-calculator-with-examples) is the standard tool for deciding which bets survive the cut. If the shortfall is structural rather than a spending problem, that's a [pivot-or-persevere decision](/decisions/pivot-or-persevere) — the chain tests whether the product, the job, or the market is what's actually default dead.

---

> **Run your trajectory**: Framework's iOS app keeps cash, burn, growth rate, and the profitability crossover in one finance worksheet. [Get it on the App Store](https://apps.apple.com/app/id6765632580).

## Sources

- [Paul Graham — "Default Alive or Default Dead?" (2015)](https://www.paulgraham.com/aord.html)
- [Figma, Inc. — Form S-1, FY2025](https://www.sec.gov/Archives/edgar/data/0001579878/000162828025033742/figma-sx1.htm)
- [Yahoo Finance — "OpenAI's own forecast predicts $14 billion loss in 2026 but $100 billion revenues by 2029"](https://finance.yahoo.com/news/openais-own-forecast-predicts-14-150445813.html)
- [Business Today — "OpenAI Raises Cash Burn Projection To US$115 Billion Through 2029"](https://www.businesstoday.com.my/2025/09/06/openai-raises-cash-burn-projection-to-us115-billion-through-2029/)
- [The Verge — "HP buys Humane, will discontinue the AI Pin"](https://www.theverge.com/2025/2/18/24107959/hp-humane-ai-pin-acquisition)

---

### Eisenhower Matrix Explained: 4 Quadrants, Examples & Template (2026)
URL: https://frameworklist.com/academy/eisenhower-matrix-urgent-vs-important
> Sort tasks into 4 quadrants by urgency and importance — with a free template, worked examples, and the common mistakes that make the matrix backfire. Updated for 2026.

The Eisenhower Matrix is a 2×2 grid that sorts every task on your plate by two questions: **is it urgent**, and **is it important**. The four quadrants imply four different actions — do, schedule, delegate, drop. The point of the matrix is not the sorting; it is the implied claim that **urgent and important are different things**, and that conflating them is how weeks evaporate.

The framing is named after Dwight D. Eisenhower, who told the Second Assembly of the World Council of Churches in 1954, "I have two kinds of problems, the urgent and the important. The urgent are not important, and the important are never urgent." He introduced the line as the words of **"a former college president,"** not his own — and the four-quadrant grid itself came later, from Stephen Covey in *The 7 Habits of Highly Effective People* (1989). See [the full provenance chain](/compare/eisenhower-matrix-vs-covey-matrix#the-eisenhower-matrix-provenance-chain) for the dated sources and why the commonly quoted "seldom urgent" wording is a later paraphrase.

> **Run the Eisenhower Matrix on your phone** — [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=eisenhower-academy) sorts your tasks into the four quadrants with AI assistance. Free to start.

## The four quadrants

<EisenhowerMatrix />

- **Important + Urgent → Do now.** Crises, deadlines today, a customer escalation. These are non-negotiable.
- **Important + Not Urgent → Schedule.** Strategy, planning, learning, deep work. The quadrant most people under-invest in, and the one with the highest long-run return.
- **Not Important + Urgent → Delegate.** Other people's priorities flowing through you. Most "asks" land here.
- **Not Important + Not Urgent → Drop.** Activities that feel productive but aren't. The mailing-list cleanup that has waited two years.

## How to run the matrix in 30 minutes

1. **List every open task, request, and meeting** you're currently carrying — somewhere between 15 and 50 items.
2. **Score "urgent" first.** Does missing the deadline produce a real consequence in the next 48 hours? If yes, urgent. If no, not urgent. Resist hedging.
3. **Score "important" second.** Does this advance a goal you've explicitly committed to this quarter? If you don't have explicit quarterly goals, you cannot do this step honestly — pause and write 2–3 goals first, then come back.
4. **Place each item in its quadrant.** Most lists collapse into 60% in "Important + Urgent" on the first pass. That's a warning sign about your week, not about the matrix.
5. **Schedule the Important + Not Urgent quadrant before anything else.** Block time for it on your calendar this week. If you don't, it will be eaten by everything else.
6. **Delegate or batch the Urgent + Not Important quadrant.** Push back where you can. Move what you can't push back into a single batched block.
7. **Delete the Not Important + Not Urgent quadrant.** Drop, archive, close, mark as won't-do. Acknowledge that doing them is choosing not to do the other quadrants.

## The common failure mode

The dominant failure mode is that **everything ends up in Important + Urgent**. This usually means the holder is reactive — every inbound feels critical because they haven't taken the time to define what's actually important upstream. The matrix doesn't help here; what helps is the prior step of pre-committing to 2–3 quarterly goals so "important" has a stable referent. Tasks that don't ladder to one of those goals can't be Important, no matter how loudly someone is asking for them.

The second failure mode is using the matrix once and never re-running it. The matrix decays fast — what was important on Monday may be obsolete by Friday. Re-run weekly. The act of re-sorting is often more valuable than the sorted output.

## When the matrix isn't the right tool

If your problem is **picking between strategic bets** (which market to enter, which product to build), the Eisenhower Matrix is the wrong instrument — try [SWOT](/frameworks/swot) or [RICE](/frameworks/rice) instead. The matrix is a *triage* tool for an existing list of work, not a *generation* tool for what should be on the list.

If your problem is **a team backlog with explicit estimates and customer impact**, RICE will give you a more defensible ranking. The Eisenhower Matrix is a personal tool by default — it works for teams only if everyone on the team shares the same definition of "important."

## Eisenhower vs RICE vs MoSCoW: when each prioritization framework wins

Three prioritization frameworks dominate day-to-day product and personal work, and teams routinely pick the wrong one because the choice is rarely articulated. The clean separation:

| | Eisenhower Matrix | [RICE](/frameworks/rice) | [MoSCoW](/frameworks/moscow) |
|---|---|---|---|
| **Question it answers** | What do I do *this week*? | Which feature ships *next*? | What's *in scope* for this release? |
| **Inputs needed** | Two yes/no judgments per item | 4 estimated numbers per item (Reach, Impact, Confidence, Effort) | One label per item (Must / Should / Could / Won't) |
| **Best for** | Personal triage, reactive weeks | Product backlog with shared estimates | Project scope negotiation with stakeholders |
| **Worst for** | Team backlogs where "important" is contested | Early discovery (numbers are guesses) | Ongoing prioritization (no recurring rhythm) |
| **Failure mode** | Everything ends up in Q1 | Estimates become political | Everything becomes a Must |
| **Time to apply** | 20–30 min weekly | 1–2 hours per cycle | 30–60 min per release |

**The decision in one line**: use **Eisenhower** when the bottleneck is *your* week, **RICE** when the bottleneck is *the team's* roadmap, **MoSCoW** when the bottleneck is *the stakeholders'* expectations.

See also the head-to-heads: [Eisenhower vs GTD](/compare/eisenhower-matrix-vs-gtd) for the prioritization-vs-workflow split, [Eisenhower vs Covey Matrix](/compare/eisenhower-matrix-vs-covey-matrix) for the triage-vs-invest split on the same grid, [Eisenhower vs Impact/Effort Matrix](/compare/eisenhower-matrix-vs-impact-effort-matrix) for the execution-vs-selection split, and [RICE vs MoSCoW](/compare/rice-vs-moscow) and [RICE vs ICE](/compare/rice-vs-ice) for the team-backlog choice.

## Related frameworks

- [Eisenhower Matrix — catalog entry & template](/frameworks/eisenhower) — the quick-reference grid with a reusable worksheet
- [Covey Time Management Matrix](/academy/covey-time-management-matrix) — the same axes used to diagnose where your *months* go, rather than to triage today
- [Eisenhower for an engineering manager's week](/examples/eisenhower-engineering-manager-week) — worked example showing how the matrix actually changes calendar decisions
- [GTD (Getting Things Done)](/frameworks/gtd) — the workflow system that pairs with Eisenhower for capture + prioritization
- [SWOT analysis](/academy/what-is-a-swot-analysis) — for picking *which* goal is important in the first place
- [RICE prioritization](/frameworks/rice) — for ranking a backlog with quantifiable inputs
- [MoSCoW](/frameworks/moscow) — a lighter alternative for requirement classification
- [Pareto analysis](/frameworks/pareto) — the 80/20 cousin of the matrix

Want to actually run one? [Open the Eisenhower Matrix tool →](/tools/eisenhower-matrix) (no sign-up needed).

---

### First Principles Thinking Examples, Scored Against Results
URL: https://frameworklist.com/academy/first-principles-thinking-with-examples
> First principles thinking examples from SpaceX, Tesla's batteries and Hyperloop, each scored against what actually happened, and where the method misleads.

**First principles thinking** is the practice of decomposing a problem into the underlying truths that can't be reduced further, then reasoning up from those truths instead of from analogies to other situations. The promise is that you arrive at conclusions that pure analogical thinking — "this is like X, so do Y" — can't reach, because analogies inherit other people's assumptions.

The idea is old (Aristotle named it; René Descartes formalized it). The modern fashion for it traces to Elon Musk's frequent retelling of how SpaceX brought launch costs down by refusing to accept that rockets had to cost what existing rockets cost.

## Why analogical thinking dominates

Most decisions, most of the time, run on analogy: *we hire like other companies hire, we price like the competitor prices, we structure the team like the last team we worked on*. Analogy is cheap. It works because most problems aren't new — and applying a known solution is faster than re-deriving one from scratch.

The cost is that you inherit assumptions baked into the analogy. If the original team had three founders and you have one, the structure won't fit. If your competitor's pricing is anchored to a customer profile that doesn't match yours, copying it will mis-price you. The errors are silent.

First principles thinking is what you reach for when **the cost of inherited assumptions is high enough that re-deriving is worth the effort**. That's not every decision — it's a specific kind.

## How to actually do it

The process is three steps, and the third is the one most people skip.

1. **State the problem in your own words.** Write down what you're trying to figure out. If you can't write a single sentence, you don't know the problem well enough yet.
2. **Decompose into atomic statements.** Break the problem into its components. Keep asking "is this *really* true, or is it true because someone said it is?" Keep going until you hit something verifiable — a physical law, a measurable cost, a logically necessary truth.
3. **Reason back up from the atoms.** Now construct your own answer using only the atoms, without re-importing the original framing. This step is where most people fail — they reach an atom, get tired, and just relax back into the original analogical answer.

## First principles thinking examples, scored against what happened

Most lists of first principles examples stop at the claim. Each example below adds what actually happened afterwards, because a decomposition is only as good as the outcome it predicted.

### Example 1: rocket costs (SpaceX)

The analogical answer: *rockets are expensive because rockets are expensive*. Launch was priced off the finished rockets incumbents sold, and competitors priced near each other.

First principles decomposition, in Musk's own words to [Wired in 2012](https://www.wired.com/2012/10/ff-elon-musk-qa/): "What is a rocket made of? Aerospace-grade aluminum alloys, plus some titanium, copper, and carbon fiber. Then I asked, what is the value of those materials on the commodity market? It turned out that the materials cost of a rocket was around two percent of the typical price."

The atomic truth: **the bill of materials does not justify the finished price**. The other 98% is engineering, manufacturing and historical institutional decisions, and all of those can in principle be changed. SpaceX's strategy is built on the gap between raw-material cost and market price.

**Score: right about the gap, and nobody expected to close it.** The 2% was never a target price. It showed that the price was not set by physics. That was enough to justify building rockets in-house instead of buying them. Fourteen years later that decision is the margin engine in [SpaceX's BCG matrix](/examples/spacex-bcg-matrix-2026): reusable Falcon 9 is the Cash Cow that funds Starship.

### Example 2: battery packs (Tesla)

The analogical answer, as Musk described it in a [2012 interview with Kevin Rose](https://www.startuparchive.org/p/elon-musk-explains-first-principles-thinking): battery packs are expensive and always will be, because that is what they have cost in the past, historically about **$600/kWh**.

First principles decomposition: ask "what are the material constituents of the batteries?" (cobalt, nickel, aluminium, carbon, polymer separators, a steel can), then price each one on the London Metal Exchange. His answer was about **$80/kWh**.

What happened, from BloombergNEF's annual survey:

| Year | Average pack price | Note |
|---|---|---|
| 2012 (Musk's prior) | ~$600/kWh | "historically", per the interview |
| 2012 (Musk's floor) | ~$80/kWh | raw materials at LME prices |
| 2022 | $151/kWh | **Up 7%**, the first increase since BNEF began tracking in 2010, driven by raw-material prices ([BNEF](https://about.bnef.com/insights/commodities/lithium-ion-battery-pack-prices-rise-for-first-time-to-an-average-of-151-kwh/)) |
| 2025 | $108/kWh average; **$81/kWh LFP**; $84/kWh in China | Down 8% on 2024, despite rising metal prices ([BNEF](https://about.bnef.com/insights/clean-transport/lithium-ion-battery-pack-prices-fall-to-108-per-kilowatt-hour-despite-rising-metal-prices-bloombergnef/)) |

**Score: right about the floor, but it was reached with different materials.** The 2025 LFP pack, the whole finished pack, sells within a dollar of what Musk said the raw materials alone cost in 2012. But LFP (lithium iron phosphate) contains no cobalt and no nickel, two of the metals his decomposition priced. BNEF credits "greater LFP adoption" for absorbing 2025's metal-price rise. The floor held because the industry changed the atoms the floor was built from. And the 2022 row shows that a commodity-priced floor moves with the commodity. It is also why [Tesla's VRIO analysis](/examples/tesla-vrio-analysis-2026) doesn't score cell hardware as the durable advantage: a cost floor the whole industry can reach isn't Rare.

### Example 3: Hyperloop (where the method misleads)

The analogical answer: high-speed rail between Los Angeles and San Francisco costs what high-speed rail costs, which is a lot.

The bottom-up alternative: the August 2013 [Hyperloop Alpha](https://www.tesla.com/sites/default/files/blog_images/hyperloop-alpha.pdf) paper built its cost from components (tubes, pylons, capsules, propulsion) and put the passenger line at **about $6 billion**.

What happened: in October 2016, [Hyperloop One's own leaked documents](https://www.forbes.com/sites/alexkonrad/2016/10/25/hyperloop-one-seeks-new-cash-amid-high-costs/) put a **107-mile** Bay Area loop at **$9-13 billion**, or $84-121 million per mile. That route is under a third of the LA-SF distance and costs up to twice the Alpha total. Hyperloop One [shut down on 31 December 2023](https://techcrunch.com/2023/12/21/hyperloop-one-shutting-down/) without building a commercial line.

**Score: wrong.** The components were priced reasonably. The error was which components got counted. Land, rights-of-way, permitting and safety certification are not materials, so a materials-first decomposition never lists them. In infrastructure they are most of the bill.

## The Fixed-Atoms Trap

Put the three scores side by side and one failure mode explains both surprises:

| Example | Floor from the decomposition | What happened | Why |
|---|---|---|---|
| SpaceX | Materials ≈ 2% of price | Gap real; floor never approached | Floor was used as evidence, not as a target |
| Tesla batteries | ~$80/kWh | Reached by 2025, via **different atoms** (LFP) | The bill of materials was negotiable |
| Hyperloop | ~$6B | 2016 estimate for a third of the distance: up to 2× that | The bill of materials was **incomplete** |

**The Fixed-Atoms Trap: a first-principles floor is a floor on the bill of materials you wrote down, not on the problem.** Decomposition treats the list of atoms as given and prices each one. It fails in two opposite directions. The list can be *negotiable* (the answer beats your floor by swapping an atom, as LFP did), or it can be *incomplete* (the answer blows through your floor because the biggest costs were never atoms, as with Hyperloop's land and permits).

Before you build on a first-principles number, run two checks:

1. **Could the bill of materials itself change?** If a different design removes an expensive input, your "floor" is only the floor for today's design.
2. **What on the real invoice is not a material?** Land, permission, certification, labour and liability don't show up on a commodity exchange. In a regulated or physical-infrastructure business they are often the largest line.

SpaceX passed both checks because the claim was only used to show the gap existed. Hyperloop failed the second. Tesla's floor passed on the price and failed the first check, which is why a correct $80 prediction still arrived by a route nobody in 2012 was pricing.

For the complementary failure, where the number *was* computable on day one and nobody computed it, see [Cydoc's shutdown and the Day-One Test](/examples/premortem-cydoc-shutdown).

## The trap

The trap is that **first principles thinking is expensive**, and most people apply it to problems that don't deserve the cost. You don't need to reason from first principles about whether to buy croissants or scones. You barely need it for what color the homepage button should be. The discipline is to identify which 5% of decisions are worth the cost — usually decisions that are hard to reverse, large in dollar terms, or strategically defining — and reserve first principles thinking for those.

Apply it to everything and you'll be slow and exhausted. Apply it to nothing and you'll be a fast-moving competitor of average ideas. This mismatch between a tool's cost and the decision's stakes is the same reason [most frameworks fail in practice](/blog/why-most-frameworks-fail) — they get reached for reflexively rather than where they earn their overhead.

## When first principles isn't the right tool

- **For triage**, use the [Eisenhower Matrix](/academy/eisenhower-matrix-urgent-vs-important). First principles on every email is paralysis.
- **For prioritization across many comparable options**, use [RICE](/academy/rice-prioritization-framework). First principles on each backlog item is overkill.
- **When you don't yet know the problem well enough**, talk to customers first. First principles thinking on the wrong question produces a beautifully-reasoned wrong answer.

## How to practice

Pick one decision you already made by analogy this quarter. Run it again from first principles. Compare the two answers. The point is not to redo the decision; it's to build the muscle of recognizing which 5% of decisions deserve the treatment.

## The Atomic Truth Test

The hardest part of first-principles thinking isn't the decomposition — it's knowing when you've stopped. Most "first principles" produced in strategy meetings are actually deeply-held prior assumptions in disguise, dressed up in confident language. The Atomic Truth Test is a named 4-question diagnostic for verifying you've reached an actual atomic truth.

For any claim you believe is a first principle, ask:

| # | Question | Why it works |
|---|---|---|
| 1 | **Could a smart 12-year-old argue with this?** | A genuine first principle is so basic that disagreement requires denying physics, math, or observable reality. If a curious non-expert could plausibly push back, you have a strong prior, not an atomic truth. |
| 2 | **Does it depend on any industry convention?** | If the claim contains phrases like "industry standard", "typically priced at", "best practice", "as everyone knows" — it's not a first principle. It's borrowed conventional wisdom. |
| 3 | **Has it survived 3 different framings?** | State the claim from three different reference frames (the customer's view, the supplier's view, the regulator's view). If the claim only makes sense in one frame, it's specific to that frame's assumptions. |
| 4 | **Can it be measured directly?** | A first principle is empirically grounded — material costs, physics constants, mathematical identities, observable behavior. If verifying it requires another expert opinion or another framework, it's a derived claim, not an atomic one. |

A claim that passes all four tests is an atomic truth you can safely build on. A claim that fails one or more is a prior assumption that needs further decomposition.

Worked example — Musk's battery first principle vs the conventional prior:

| Claim | Smart 12-year-old? | Industry convention? | Survives 3 framings? | Measurable directly? | Verdict |
|---|---|---|---|---|---|
| **"Battery packs cost $600/kWh and always will."** (2008 conventional) | Yes — "why?" — no good answer that doesn't appeal to history | Yes — heavily | No — only makes sense from the incumbent manufacturer's frame | No — requires industry "experts" to vouch | **Prior assumption in disguise** |
| **"The raw materials that go into a battery pack cost ~$80/kWh on the commodity market."** (first principle) | No — this is a physics/chemistry/commodity-market fact | No — independent of any industry convention | Yes — same answer from the materials supplier, the battery maker, or the EV builder | Yes — commodity exchange prices, publicly listed | **Atomic truth** |

The $80 figure was build-on-able. The $600 figure was not — it was a derived claim that depended on existing manufacturing processes, supply chains, and volume assumptions, all of which Tesla rebuilt over the following decade.

One correction to that verdict, visible only with hindsight: the $80 figure is a *measurement*, not a law. It is a commodity price, and commodity prices move. BloombergNEF's 2022 survey recorded the first-ever rise in pack prices, driven by raw materials. The atom that held was the chemistry. The price attached to it did not. Treat a commodity-priced first principle as atomic for the decision in front of you, and re-measure it before the next one. That is the gap [The Fixed-Atoms Trap](#the-fixed-atoms-trap) above is about.

The Atomic Truth Test is mostly used **to disqualify candidate first principles, not to discover them**. The discovery work is the decomposition (what the article above covers). The Test is the safety check before you commit a 5-year strategy to a foundation that turns out to be a prior assumption you never noticed.

Most teams trying first-principles thinking fail at question 2 — they decompose down to "industry standard" and stop, declaring it a first principle. The discipline is to keep going until the claim is independent of conventions. That's where the non-obvious answers come from.

> **Want to decompose a problem on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=first-principles-academy) walks you down to the atomic truths with AI-assisted prompts, then rebuilds the solution from them. Free to start.

## Related frameworks

- [Reverse brainstorming](/frameworks/reversebrain) — the mirror discipline: reason from the failure case backwards
- [Reverse Brainstorming](/academy/reverse-brainstorming-solve-problems-backwards) — the applied version of inversion thinking for problem-solving sessions
- [5 Whys](/frameworks/fivewhys) — a lightweight tool for decomposing a single observation
- [Premortem](/academy/how-to-run-a-premortem) — first-principles risk analysis
- [Decision tree](/frameworks/tree) — structured way to map the consequences once you've reached your atomic truths

Want to walk through a decision this way? [Start a canvas →](/sign-in) and use the First Principles framework template.

---

### How to Calculate Burn Rate: Formula and Real Examples
URL: https://frameworklist.com/academy/how-to-calculate-burn-rate
> How to calculate burn rate — the gross, net, and financing-adjusted formulas — with real Rivian and Lucid 2026 numbers and the trap that hides true burn.

Burn rate is how much cash a company consumes each month. Learning **how to calculate burn rate** takes about a minute — the formula is subtraction and division. What takes longer is knowing which of the three legitimate burn numbers you just produced, because they can point in opposite directions for the same company in the same quarter.

This page is the three formulas, the four ways people actually compute them and which one lies, a real worked example using Rivian's Q2 2026 figures — where cash *rose* $500M while the company burned — and the Lucid case from two weeks ago, where one burn rate produced three defensible runway answers and a 40% single-day stock crash.

> **Want burn on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a finance-metrics worksheet — drop in cash, spend, and collections and see gross burn, net burn, and runway update live. Or start with the [Burn Rate](/glossary/burn-rate) glossary entry for the short definition.

## The burn rate formula: three numbers, not one

```
Gross burn              = Total monthly cash outflow
Net burn                = Gross burn − Cash revenue collected
Financing-adjusted burn = (Δ Cash − Net financing inflows) ÷ Months
```

The first two are the standard textbook pair, covered in depth in the [Burn Rate glossary entry](/glossary/burn-rate). The third is the one almost nobody computes, and it is the one that decides whether you are reading a company correctly or backwards.

| Formula | Inputs it needs | The question it answers |
|---|---|---|
| **Gross burn** | Cash outflows only | What if revenue went to zero tomorrow? |
| **Net burn** | Outflows − collections | How fast is the bank balance actually falling? |
| **Financing-adjusted burn** | Cash balances + financing activity | Is this company's cash growth real, or did it just raise money? |

## Four ways to calculate burn rate — and which one lies

Most guides give you one method. In practice there are four, and they disagree. Knowing which one you're using is more important than the arithmetic.

| Method | How it works | Accurate when | How it fails |
|---|---|---|---|
| **1. Expense-summation** | Add every cash outflow for the month; subtract cash collected | You run the company and see the bank feed | Misses irregular outflows — tax payments, annual insurance, capex — if you only sum the recurring lines |
| **2. Cash-balance delta** | (Starting cash − ending cash) ÷ months | No financing, no asset sales in the period | **Silently nets financing against operations.** A raise makes burn look small or negative |
| **3. Cash-flow statement** | Operating cash flow + capital expenditures, from the filing | You have a full statement of cash flows | Only available quarterly for public companies, and lags the quarter by weeks |
| **4. Financing-adjusted** | (Δ Cash − net financing inflows) ÷ months | You have balance sheets plus disclosed financing | Produces a *floor* on burn, not a point estimate — undisclosed inflows push true burn higher |

Method 2 is the one in most search results, and it is the one that breaks. It is fine for a bootstrapped company with a quiet quarter. It is actively misleading for exactly the companies whose burn people most want to measure — the funded ones.

## How to calculate burn rate (6 steps)

1. **Fix the period.** A single month is noisy; hiring, tax payments, and annual renewals land in lumps. Use a trailing three-month average, and recompute it every month rather than reusing last quarter's figure.
2. **Sum gross burn from cash, not the P&L.** Every dollar that left the bank: fully-loaded payroll including founders, cloud and tooling, marketing, rent, taxes, and capex. Non-cash items — depreciation, stock compensation — are not burn. Cash that left for equipment is.
3. **Subtract cash actually collected.** Not booked revenue. A company billing $120K annually upfront collects $120K in month one and nothing for the next eleven, while its GAAP revenue reads a flat $10K a month. Burn uses the bank statement.
4. **Check whether any financing landed in the period.** Equity rounds, debt draws, convertible notes, milestone payments, grants, tax credits received in cash. This is the step that gets skipped.
5. **Adjust.** If you derived burn from cash balances, subtract net financing inflows from the change in cash before dividing. If you derived it from the expense list, confirm you didn't accidentally count a loan draw as revenue.
6. **State which number you produced.** Gross, net, or financing-adjusted. A burn rate quoted without its type is not a number, it's a vibe.

## Worked example: Rivian, Q2 2026 — cash went up, and the company burned

Most burn-rate tutorials use a tidy hypothetical. Here is a real, public, two-week-old one where the naive method doesn't just produce an imprecise answer — it produces an answer with the wrong sign.

In a [preliminary 8-K filed July 6, 2026](https://www.streetinsider.com/Corporate+News/Rivian+offers+Q2+2026+revenue+outlook,+cash+position+grows/26736525.html), Rivian disclosed:

| Metric | Figure | Date |
|---|---|---|
| Cash, equivalents, and short-term investments | ~$4.8B | March 31, 2026 |
| Cash, equivalents, and short-term investments | ~$5.3B | June 30, 2026 (estimated) |
| Change over the quarter | **+$500M** | Q2 2026 |
| Q2 revenue (preliminary range) | $1.55B–$1.65B | vs. $1.30B in Q2 2025 |
| Q1 2026 free cash flow (actual) | −$1,075M | [Q1 2026 filing](https://stockanalysis.com/stocks/rivn/financials/cash-flow-statement/) |

Run **method 2**, the cash-balance delta everyone reaches for first:

```
Monthly burn = ($4.8B − $5.3B) / 3 months = −$167M per month
```

A negative burn rate means the company generated cash. The conclusion off that arithmetic: *Rivian went cash-flow positive in Q2 2026, one quarter after burning $1.075B.*

That did not happen. In April 2026, Volkswagen's RV Tech joint venture cleared its winter-testing milestone, [triggering a $1 billion equity investment](https://riviantrackr.com/news/volkswagen-boosts-rivian-stake-to-15-9-following-joint-venture-milestone/) — 62,889,522 Class A shares at $15.90, lifting VW's stake to 15.9% and drawing down part of the $5.8B commitment VW made in 2024. That $1B is financing. It has nothing to do with whether Rivian's operations consume cash.

Run **method 4**:

```
Operating + investing cash flow ≈ Δ Cash − Net financing inflows
                                ≈ +$500M − $1,000M
                                = −$500M for the quarter
                                ≈ $167M per month of true burn
```

The naive answer was −$167M a month. The adjusted answer is +$167M a month. **The error wasn't a rounding difference — it was exactly twice the true burn, pointed the wrong way.** And because $1B is the financing we can *see*, $167M/month is a floor: if any other tranche, credit draw, or regulatory-credit sale landed in the quarter, real burn is higher still.

One honesty note that is itself a lesson: Rivian's audited statement of cash flows for Q2 2026 publishes July 30, 2026, the day after this page. Everything above is a reconciliation from preliminary balance-sheet figures. When you calculate burn from balance sheets rather than a cash flow statement, you are estimating — say so, and label the direction of the uncertainty.

## Worked example: Lucid, July 2026 — one burn rate, three defensible answers

Rivian shows the numerator going wrong. Lucid, two weeks ago, showed what happens when the *denominator* is ambiguous.

On July 14, 2026, Lucid stock [crashed more than 40% intraday and was halted twice](https://electrek.co/2026/07/14/lucid-lcid-bankruptcy-report-denied/) after a report claimed restructuring firm AlixPartners had advised the board to weigh a take-private or a Chapter 11 filing. Lucid's communications head Nick Twork called the rumors "completely false," said AlixPartners "has not recommended bankruptcy to management or the Board," and stated the company has "sufficient liquidity to carry its operations well into next year."

Both the panic and the denial can be arithmetically correct at the same time. Take Lucid's Q1 2026 burn — roughly $1.44B of free cash flow consumed, about **$480M a month** — and hold it constant. Now change only which cash figure you divide:

| Cash base used | Figure | Implied runway | The story it tells |
|---|---|---|---|
| Headline cash and equivalents | ~$714M | **~1.5 months** | Bankruptcy is weeks away |
| Total liquidity at Q1 close | ~$3.2B | **~6.7 months** | Tight, needs a raise this year |
| Pro forma liquidity after the April raise | ~$4.7B | **~9.8 months** | "Well into next year" |

The April raise is what separates row two from row three: ~$1.05B including $550M of convertible preferred from Saudi Arabia's PIF and $200M from Uber, plus a $500M PIF term-loan draw against roughly $2B of remaining undrawn capacity.

Nobody in that exchange was lying. The market read row one and the company read row three. A 40% drawdown is what it costs when a burn calculation's denominator is left unstated — which is the whole argument for the check below. For the full runway treatment and the 2026 benchmarks, see [Cash Runway Formula](/academy/cash-runway-formula).

## The Three-Number Burn Check

Here is the diagnostic that ties this together, and the one rule worth taking from this page. **A burn rate is not reportable until you can say which of three numbers it is.**

| # | Number | How to compute it | What it is for | How it lies |
|---|---|---|---|---|
| **1** | Gross burn | Total monthly cash outflow | Stress-testing a revenue collapse | Overstates danger for a company with durable collections |
| **2** | Net burn | Gross burn − cash collected | Runway, board reporting, planning | Hides capex and lumpy one-time outflows if lifted from the P&L |
| **3** | Financing-adjusted burn | (Δ Cash − net financing inflows) ÷ months | Reading a company from the outside | Only a floor — undisclosed inflows mean real burn is higher |

**The check has three passes:**

1. **Can you name the type?** If someone says "our burn is $400K," ask gross or net. If they can't answer, the number was never computed — it was remembered.
2. **Did any financing land in the period?** If yes and you used cash balances, number 3 is mandatory, not optional. Skip it and *every company that raised money last quarter looks like it stopped burning.* Rivian is the proof.
3. **Is the denominator stated?** Burn is half a survival claim. The other half is which cash base — headline cash, total liquidity, or pro forma liquidity. Lucid is the proof.

A burn figure that passes all three is a fact. One that passes none is the number that gets a company's stock halted twice in an afternoon.

## Calculating burn rate for a company you don't run

Most burn-rate content assumes you're the founder reading your own bank feed. Competitive analysis, investment diligence, and vendor risk checks all need the opposite skill — deriving burn from someone else's disclosures. The order of preference:

1. **Statement of cash flows, if it exists.** Operating cash flow plus capital expenditures gives you free cash flow, the cleanest public proxy for net burn. Rivian's Q1 2026: −$703M operating, −$372M capex, −$1,075M free cash flow. No estimation required.
2. **Balance sheet plus disclosed financing.** When only preliminary figures exist — as with Rivian's Q2 — use method 4 and treat the result as a floor.
3. **Net loss, as a last resort, with corrections.** GAAP net loss includes non-cash charges like stock compensation and depreciation, so it usually *overstates* cash burn; it also excludes capex, which usually *understates* it. For a hardware company like Lucid, whose Q1 2026 net loss was ~$1.03B against ~$1.44B of actual cash burn, the net loss understated the truth by roughly 40%.

The general rule: **the further you move from the cash flow statement, the more your burn estimate is a range**. Publish the range, not a false point estimate.

## When a burn rate calculation misleads

Even a correctly computed burn rate can produce the wrong decision:

- **Burn is accelerating.** A trailing average understates the next period. Lucid's Q1 2026 cash burn of ~$1.44B was more than double the ~$589.9M it burned in the same quarter a year earlier — anyone using the prior-year figure would have estimated more than double the real life remaining.
- **A strategic backer can inject on demand.** For a PIF-backed Lucid or a VW-backed Rivian, the static calculation describes a floor, not a plan. The real question is when the next tranche lands and what it costs in dilution.
- **Revenue is ramping.** If collections are climbing 10–15% a month, this month's net burn overstates next month's, and the company may cross into cash-generative before the cash runs out. Model the curve, not a flat line. That trajectory read has its own diagnostic — see [Default Alive or Default Dead](/academy/default-alive-or-default-dead).
- **The burn is buying something durable.** Burn is not automatically bad. A burn multiple below 1.0 means each dollar burned bought more than a dollar of new recurring revenue. See [Burn Multiple](/academy/burn-multiple-formula-benchmarks) for the efficiency read.

## Common burn rate calculation mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Using cash-balance delta after a raise | It's the fastest method and financing is invisible in it | Subtract net financing inflows first — the Three-Number Burn Check, pass 2 |
| Quoting gross burn as "our burn" | It's the number sitting in the expense report | Say gross or net every time |
| Using net loss as burn | It's the number on the income statement | Net loss includes non-cash items and excludes capex; use free cash flow |
| Averaging a single quiet month | One month with no hiring or tax payments flatters everything | Trailing three-month average, recomputed monthly |
| Treating undrawn credit as cash | It reads like available money | Count committed, accessible facilities separately; state the base |
| Mixing project burn rate with company burn rate | Same name, different metric | Project burn measures budget consumed vs. plan; keep them in separate reports |

## Related reading

Burn rate is the input; these are the reads built on top of it:

- [Burn Rate](/glossary/burn-rate) — the short definition, gross vs. net, and when to cut
- [Cash Runway Formula](/academy/cash-runway-formula) — cash ÷ burn, the Runway Triangle, and 2026 benchmarks
- [Burn Multiple](/academy/burn-multiple-formula-benchmarks) — net burn ÷ net new ARR, the capital-efficiency read
- [Default Alive or Default Dead](/academy/default-alive-or-default-dead) — whether growth outruns burn before cash runs out
- [Runway](/glossary/runway) — the 18 / 12 / 6-month thresholds and what founders do at each
- [Unit Economics](/glossary/unit-economics) — whether each customer extends or shortens runway
- [Rule of 40](/glossary/rule-of-40) — the growth-plus-profit efficiency read at scale

When burn forces a decision about *what to cut*, the [RICE scoring method](/academy/rice-score-calculator-with-examples) is the standard tool for ranking which bets survive the budget.

---

> **Run your numbers**: Framework's iOS app keeps cash, gross burn, net burn, and runway in one finance worksheet. [Get it on the App Store](https://apps.apple.com/app/id6765632580).

## Sources

- [StreetInsider — "Rivian offers Q2 2026 revenue outlook, cash position grows"](https://www.streetinsider.com/Corporate+News/Rivian+offers+Q2+2026+revenue+outlook,+cash+position+grows/26736525.html)
- [StockTitan — Rivian Automotive 8-K, filed July 6, 2026](https://www.stocktitan.net/sec-filings/RIVN/8-k-rivian-automotive-inc-de-reports-material-event-1cdd4ae7f366.html)
- [RivianTrackr — "Volkswagen Boosts Rivian Stake to 15.9% Following Joint Venture Milestone"](https://riviantrackr.com/news/volkswagen-boosts-rivian-stake-to-15-9-following-joint-venture-milestone/)
- [StockAnalysis — Rivian Automotive quarterly cash flow statement](https://stockanalysis.com/stocks/rivn/financials/cash-flow-statement/)
- [Electrek — "Lucid (LCID) stock halted, crashes 40% on bankruptcy report it denies"](https://electrek.co/2026/07/14/lucid-lcid-bankruptcy-report-denied/)
- [Lucid Group — "Lucid Announces First Quarter 2026 Financial Results"](https://www.prnewswire.com/news-releases/lucid-announces-first-quarter-2026-financial-results-302763127.html)
- [Yahoo Finance — "Lucid Q1 results miss estimates; cash burn expected to continue"](https://finance.yahoo.com/markets/stocks/article/lucid-q1-results-miss-estimates-cash-burn-expected-to-continue-as-product-ramp-expands-200534977.html)

---

### How to Do a PESTEL Analysis (6 Steps + Netflix 2026 Example)
URL: https://frameworklist.com/academy/how-to-do-a-pestel-analysis
> A PESTEL analysis scans the six external forces — Political, Economic, Social, Technological, Environmental, Legal — around a business. Here's how to run one, worked on Netflix's real 2026 macro-environment.

A **PESTEL analysis** scans the six external forces — **Political, Economic, Social, Technological, Environmental, and Legal** — that shape a company's future but sit outside its control. It's the tool you reach for when the question isn't "are we executing well?" but "what is the world about to do *to* us?" — a market entry, an annual strategy review, a big investment decision, or any moment where the macro-environment could make or break the plan. This guide runs the analysis on a **real, current company — Netflix, using its 2026 macro-environment and Q1 2026 numbers** — because a PESTEL only earns its keep when the six letters point at named, dated forces instead of textbook generalities.

The framework goes back to Harvard professor Francis Aguilar, who in his 1967 book *Scanning the Business Environment* laid out "ETPS" — the ancestor of today's acronym. More than fifty years later it survives because it does one thing no internal metric can: it forces a leadership team to look *outward*, at the forces they can't invoice, hire, or ship their way out of.

> **Want to run a PESTEL on your own company?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=pestel-academy) fills in each of the six factors with AI-assisted prompts. Free to start.

## The six factors: what each letter scans

Every PESTEL is a sweep across six categories of external force. The trap is treating them as six buckets to fill with trivia; the skill is knowing what *kind* of force lives in each:

| Letter | Scans | Ask this |
|---|---|---|
| **P — Political** | Government action and stability: trade policy, subsidies, taxation, political risk, state intervention | What might governments *do* that changes our economics? |
| **E — Economic** | Macro conditions: growth, inflation, interest rates, currency, consumer spending power | Which way is the money moving — and how exposed are we? |
| **S — Social** | Demographics, culture, values, behaviour, lifestyle shifts | How are the *people* we serve changing? |
| **T — Technological** | Innovation, automation, R&D, platform shifts, tech-driven disruption | What new capability could obsolete or supercharge us? |
| **E — Environmental** | Climate, sustainability, resource scarcity, physical-world constraints, ESG pressure | What does the planet — and pressure about it — demand? |
| **L — Legal** | Laws and regulation: compliance, labour law, IP, industry-specific rules, litigation | What are we *required* to do, or about to be? |

The two letters people get wrong are the pair that looks duplicated. **Political** is about what governments might *choose* to do (a policy that doesn't exist yet); **Legal** is about what the law *already requires* or is confirmed to require. A tariff being debated is Political; a directive with a compliance deadline is Legal.

## How to do a PESTEL analysis in 6 steps

1. **Define the scope and the decision.** A PESTEL for "should we enter Germany?" looks nothing like one for "should we keep raising prices?" Name the decision the scan feeds — otherwise you collect facts nobody will use. Write one sentence: *"This analysis informs [decision] by [date]."*
2. **Sweep each of the six letters.** Work them in order and list every external force you can find under each — no filtering yet. Pull from earnings calls, regulator announcements, industry reports, and news, not from memory. Aim for breadth here; you'll cut later.
3. **Score impact and likelihood.** This is the step most guides skip, and it's why most PESTELs die in a slide deck. Rate each force on **impact** (1–5: how much would it move our strategy?) and **likelihood** (1–5: how probable, within our planning horizon?). Multiply for a materiality score (see [the PESTEL Materiality Filter](#the-pestel-materiality-filter) below).
4. **Keep the material few.** A 30-factor list is noise. Keep the handful that score high on *both* axes — the forces both likely and consequential. Everything else goes on a watch list, not the strategy.
5. **Attach a response to each.** A force with no decision attached is trivia. For every material factor write the move: hedge it, exploit it, lobby against it, build for it, or explicitly accept the risk.
6. **Set a review date.** The macro-environment moves; a PESTEL is a snapshot, not a monument. Tie the re-run to a natural cadence — the next earnings print, the next budget cycle, the next regulatory deadline.

## Worked example: Netflix's PESTEL in 2026

Netflix is an ideal PESTEL subject because every one of the six letters is live for it at once — it sells culture across ~190 countries, so politics, currency, taste, technology, energy, and law all bear on it simultaneously. Here is the mid-2026 scan, grounded in its [Q1 2026 results](https://www.cnbc.com/2026/04/16/netflix-nflx-earnings-q1-2026.html) (reported April 2026: **$12.25B revenue, up 16% year over year**, at a record **32.3% operating margin**).

| Factor | What's live for Netflix in 2026 |
|---|---|
| **Political** | Content-investment pressure in the EU, where Netflix's Europe content chief has [warned regulation may one day "dictate not just how much we invest but what we make"](https://www.hollywoodreporter.com/business/business-news/netflix-europe-content-chief-ai-streaming-regulations-1236613649/); trade and data-localisation tensions across its ~190-country footprint |
| **Economic** | Ad revenue [on track to hit $3B in 2026 — roughly doubling year over year](https://almcorp.com/blog/netflix-ad-revenue-3-billion-2026-q1-earnings-2/) — as a hedge against subscriber-growth maturity; heavy FX exposure with most revenue earned outside the US; content spend competing for the same capital |
| **Social** | The decisive shift to ad-supported viewing — the ad tier reached [190M monthly active users and made up over 60% of Q1 sign-ups in ad markets](https://almcorp.com/blog/netflix-ad-revenue-3-billion-2026-q1-earnings-2/); attention now split with YouTube, TikTok, and gaming, not just other streamers |
| **Technological** | Generative AI in production — Netflix has [published guidelines allowing AI for early ideation but barring it from replicating copyrighted work or replacing union labour](https://cybernews.com/news/netflix-generative-ai-guidelines-content/); an ad-tech stack now serving [4,000+ advertisers, up 70% year over year](https://almcorp.com/blog/netflix-ad-revenue-3-billion-2026-q1-earnings-2/) |
| **Environmental** | Streaming's data-centre and delivery energy footprint; production-level carbon and sustainability reporting expectations rising with ESG scrutiny |
| **Legal** | The [EU AI Act's transparency rules take effect August 2026](https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai), requiring AI-generated content to be labelled; the EU's [Audiovisual Media Services Directive already mandates 30% European works](https://digital-strategy.ec.europa.eu/en/policies/audiovisual-media-services) in on-demand catalogues |

Scanned this way, the six letters produce roughly eighteen forces. That's the problem the next section solves: **a list of eighteen forces is not a strategy.** Which two or three actually change what Netflix should *do*?

## The PESTEL Materiality Filter

Here is the named method worth taking away — the step that separates a PESTEL that changes a decision from one that fills a slide. Score every force on two axes, multiply, and let the number tell you where to spend attention:

- **Impact (1–5)** — if this force plays out, how much does it move the strategy?
- **Likelihood (1–5)** — how probable is it inside our planning horizon?
- **Materiality = Impact × Likelihood.** Score **≥15 → Act now**, **8–14 → Monitor**, **under 8 → Park**.

Run Netflix's forces through it and the eighteen collapse to a short, rankable list:

| Netflix force (letter) | Impact | Likelihood | Materiality | Verdict |
|---|---|---|---|---|
| Shift to ad-supported viewing **(S)** | 5 | 5 | **25** | 🔴 Act now |
| Ad revenue doubling toward $3B **(E)** | 5 | 4 | **20** | 🔴 Act now |
| EU AI Act labelling, Aug 2026 **(L)** | 3 | 5 | **15** | 🔴 Act now |
| EU content-investment mandates **(P)** | 4 | 3 | **12** | 🟡 Monitor |
| Generative AI in production **(T)** | 4 | 3 | **12** | 🟡 Monitor |
| Streaming energy / ESG footprint **(E)** | 2 | 3 | **6** | ⚪ Park |

The filter does two things a plain PESTEL can't. First, it **ranks** — the ad-tier shift (25) and the ad-revenue ramp (20) clearly outrank the environmental footprint (6), so that's where the strategy conversation goes. Second, it **exposes the pairs that reinforce each other**: Netflix's top two forces are the same story from two letters — a Social behaviour shift (viewers accepting ads) enabling an Economic engine (ad revenue doubling). When two of your highest-materiality forces point the same way, that's not two risks to manage; it's one strategic bet to press. **The list is never the deliverable — the ranked, paired, responded-to *few* are.**

## When NOT to use a PESTEL

- **Internal or operational problems.** PESTEL only looks outward. If the question is about your own team, product, or process, it will return nothing useful — use [SWOT](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=pestel-academy) for the inward view, or [RICE](/academy/rice-prioritization-framework) to prioritise the work itself.
- **Competitive dynamics inside a defined market.** PESTEL scans the macro-environment *around* an industry, not the rivalry *within* it. For five-firms-fighting questions, step down a layer to [Porter's Five Forces](/compare/pestel-vs-porters-five-forces).
- **When you'll do nothing with it.** A PESTEL with no decision attached is a research assignment. If no choice depends on the answer, skip it — the scan is only worth its cost when a real decision is waiting on the other side.

## Common mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Listing forces without scoring them | Filling six buckets feels like finishing | Run the [Materiality Filter](#the-pestel-materiality-filter) — an unranked list can't guide a decision |
| Confusing Political with Legal | The two letters look like duplicates | Political = what a government *might* do (no law yet); Legal = what's *already required* or dated |
| Confusing market growth with company growth | It's the same trap SWOT users fall into | PESTEL scans forces you don't control — your own sales number isn't one of them |
| Treating it as a one-time deck | The output looks like a finished artifact | It's a snapshot; re-run it each earnings cycle or budget round as the environment moves |
| No response attached to any factor | The scan feels complete once the grid is full | Every material force gets a move — hedge, exploit, lobby, build, or explicitly accept |

## Want to go deeper

This page is the methodology; the worked deep-dives are where the six letters come alive on real companies. Start with the [Amazon PESTEL Analysis 2026](/examples/amazon-pestel-analysis-2026) for a company where the Political and Legal letters dominate, the [Apple PESTEL Analysis 2026](/examples/apple-pestel-analysis-2026) for supply-chain and trade exposure scanned factor by factor, and the [Nike PESTEL Analysis 2026](/examples/nike-pestel-analysis-2026) for a consumer brand where the Social and Environmental letters carry the weight. To see the method run on a whole economy rather than a firm, the [PESTEL Analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) applies it to the United States and introduces the **Load-Bearing Force Test** — the diagnostic for when one force is structurally holding up the other five, which is the case the Materiality Filter's ranking logic cannot handle on its own. The [PESTEL Analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) runs the same country-level scan on the counterparty and introduces the **Reversal Test** — count the policies a government has *withdrawn* during the scan window, not just the ones it has introduced, because a high reversal count tells you how little today's policy baseline predicts tomorrow's. The [PESTEL Analysis of France (2026)](/examples/france-pestel-analysis-2026) completes the country set and introduces the **Ballast Test** — during the scan window, list which policy commitments survived every change of government and which did not, because the separator is usually the constitutional instrument a commitment depends on rather than its importance. It is the inverse of the Reversal Test: Canada's instability generalises across cells, France's is confined to the two that route through parliament. The [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026) adds a fourth shape and the one that most directly corrects the scoring step of the method above: it introduces the **Disbursement Gap** - for each cell, record the date the policy was enacted and the date money or effect actually reaches the economy, and score the interval rather than the announcement. Germany in 2026 has substantive enacted policy in all six cells and a federal infrastructure fund that had released roughly 28% of its 2026 budget by April, which is why scoring the announcement produces the wrong answer. The [PESTEL analysis of the European Union (2026)](/examples/europe-pestel-analysis-2026) is the fifth and the only one whose subject is not a state; it introduces the **Competence Test** - for each cell, write down whether the lever is an exclusive Union competence, a shared one, or a national one, and score the cell only at the level that can pull it. Six of the EU's ten load-bearing 2026 facts sit at Union level and four at national level, and the split runs *through* the Economic, Technological and Environmental letters rather than between them, which is why a "Europe" score for those cells is an average of markets that share no government. The [PESTEL analysis of China (2026)](/examples/china-pestel-analysis-2026) is the sixth and introduces the **Two-Ledger Test** - for each cell, write the production reading (exports, industrial output, factory-gate prices) and the household reading (retail, housing, consumer prices, births) side by side, score them separately, and route each to the decision it governs, because in 2026 the two carry opposite signs inside the same NBS release: exports +17.8% against retail +0.6% in July, producer prices +5.0% for means of production against −0.5% for consumer goods in August. It extends the Competence Test's question from *which government holds the lever* to *which economy the cell describes*. The [PESTEL analysis of India (2026)](/examples/india-pestel-analysis-2026) is the seventh and introduces the **Imported-Cell Test** - for each cell, ask whether the government being scanned can move the reading; score domestic cells on the government's plan and imported cells on the foreign actor's calendar, and never average the two. India in September 2026 has the strongest domestic column in the series (GDP +7.8%, real fixed investment +11.9%, deficit 4.3%) and three adverse imported cells set in the Strait of Hormuz, Washington and the Pacific - a $115.98 crude basket, the Graham Act's up-to-100% tariff authority signed 18 September, and a monsoon 14% below normal. The [PESTEL analysis of Mexico (2026)](/examples/mexico-pestel-analysis-2026) is the eighth and introduces the **Entrant Test** - score each cell twice, for a firm already operating in the country and for one deciding whether to arrive, and sort the cells by whether an entrant can design around them. The [PESTEL analysis of Argentina (2026)](/examples/argentina-pestel-analysis-2026) is the ninth and introduces the **Lock-In Ladder** - for each cell, find the legal instrument holding it (announcement, executive policy, ordinary law, law plus a stability contract, treaty) and score it past the next election only from the top two rungs. Argentina's Q2 2026 growth came from mining (+16.4%) and agriculture (+6.9%) while manufacturing (−2.1%) and household consumption (−2.4%) shrank, which lines up with the rungs each sector can reach. The [PESTEL analysis of Japan (2026)](/examples/japan-pestel-analysis-2026) is the tenth and introduces the **Repricing Test** - score each cell once at the cost of money its policy was designed for and once at the government's own current planning rate, and act only on the cells whose score flips. Japan's FY2027 budget requests assume a 3.8% long-term rate and put debt service at a record ¥36.64 trillion, about a quarter of all requests, while the Bank of Japan sits at 1.25%. The cells that look strongest in 2026 (fiscal expansion under a 316-seat majority, subsidised chips, new renewable capacity) are the ones that depend on cheap borrowing, and the ones that do not (the cyber law, the 15% US tariff cap, the labour shortage) score the same at any rate. Then read [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) to see when to scan the whole macro-environment versus the rivalry inside one market — the two frameworks answer different questions and are built to run in sequence. The [PESTEL framework overview](/frameworks/pestel) collects every PESTEL resource in one place.

> Want to run this on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=pestel-academy) — fill in any framework with AI assistance.

## Sources

- [Francis Aguilar — *Scanning the Business Environment* (Macmillan, 1967)](https://www.hbs.edu/faculty/Pages/profile.aspx?facId=6484) — the "ETPS" origin of the framework
- [CNBC — "Netflix (NFLX) earnings Q1 2026" (April 16, 2026)](https://www.cnbc.com/2026/04/16/netflix-nflx-earnings-q1-2026.html)
- [ALM Corp — "Netflix Ad Revenue Is on Track to Hit $3 Billion in 2026: What Q1 Earnings Reveal" (2026)](https://almcorp.com/blog/netflix-ad-revenue-3-billion-2026-q1-earnings-2/)
- [The Hollywood Reporter — "Netflix Euro Content Chief Outlines Approach to AI, Regulation" (2026)](https://www.hollywoodreporter.com/business/business-news/netflix-europe-content-chief-ai-streaming-regulations-1236613649/)
- [Cybernews — "Netflix publishes first generative AI guidelines" (2026)](https://cybernews.com/news/netflix-generative-ai-guidelines-content/)
- [European Commission — "AI Act: Regulatory framework for AI"](https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai)
- [European Commission — "Audiovisual Media Services Directive"](https://digital-strategy.ec.europa.eu/en/policies/audiovisual-media-services)

---

### How to Run a Premortem: Free Template + 45-Minute Agenda
URL: https://frameworklist.com/academy/how-to-run-a-premortem
> A free premortem template to copy, plus the 45-minute agenda to run it: assume the project failed, work back to the causes, and add the row most templates miss.

A **premortem** is a structured pre-launch exercise where you assume the project has failed and work backwards to identify what would have caused the failure. The premise sounds gimmicky and the execution takes 45 minutes; the output regularly catches problems that would otherwise surface six months in, when they're 10× harder to fix. For a blow-by-blow of one in action, see this [premortem on a product launch that almost shipped broken](/examples/premortem-product-launch).

Gary Klein first published the technique in his 2004 book *The Power of Intuition*, then popularized it in a two-page September 2007 *[Harvard Business Review](https://hbr.org/2007/09/performing-a-project-premortem)* column. The research he cited — [Mitchell, Russo and Pennington (1989)](https://onlinelibrary.wiley.com/doi/abs/10.1002/bdm.3960020103) — found that imagining a future event has already happened ("prospective hindsight") produced roughly **30% more reasons**. It is worth being precise about that number, because Klein's own column describes it as a 30% gain in the ability to *correctly identify* reasons, and the study measured quantity rather than accuracy. See [the full provenance chain and the 30% Gap](/frameworks/premortem) for why the distinction changes how you should run the session.

The mechanism is simple: when you ask "what could go wrong," people stay diplomatically optimistic; when you ask "given that we failed, what happened," people get specific.

> **Just need the template?** Copy the [premortem template below](#the-premortem-template), or [fill in the free online premortem worksheet](/tools/premortem): no sign-up, and it runs in the browser.

## When to run one

The window for a premortem is **after a plan is concrete enough to fail and before the team has emotionally committed to executing it**. Specific moments:

- A week before launching a new product, feature, or marketing campaign
- At the start of a multi-quarter initiative, before the kickoff meeting
- When a partnership or acquisition is in the late stages of due diligence
- After a strategy decision is made but before the budget is locked
- Before a hire who will shape a function (head of sales, first PM)

Skip premortems for reversible decisions or routine work — the overhead is wasted. Save them for the bets where the cost of failure is high and the timeline is long.

## How to run one in 45 minutes

1. **Set the frame, then stop talking** (5 min). Open with: "It is 12 months from now. Our project has failed. We are doing the postmortem. Spend the next 10 minutes writing down, individually, everything that went wrong." Then stop. Do not soften, do not list examples — every example you give narrows what people are willing to imagine.
2. **Silent writing** (10 min). Everyone writes their own list. No talking. The silence matters: it removes the social pressure to converge on the loudest opinion, which is the failure mode of an open brainstorm. Senior people should write fewest examples first, junior people loudest, to counter the seniority bias.
3. **Round-robin readout** (15 min). Each person reads one item from their list. Capture each on a sticky note or doc. Loop until everyone has read everything. Don't debate yet.
4. **Cluster and prioritize** (10 min). Group sticky notes by underlying cause. Three or four clusters will dominate — those are the real risks. The clusters often surprise even the people who wrote the notes, because no individual person wrote the cluster, the *group* did.
5. **Decide what to do** (5 min). For each top cluster: do we mitigate now, monitor with a tripwire, or accept and document the risk? Assign an owner to each.

The total exercise should never exceed 60 minutes. If the team can't surface real risks in 45 minutes, the problem isn't the time — it's that the team isn't safe enough to be honest, and fixing that is upstream of any framework.

## The premortem template

Copy this into a doc or spreadsheet before the session. Each row maps to a step of the agenda above, so the facilitator fills it in as the meeting runs rather than writing it up afterwards.

| Field | What goes in it | Filled at step | Example |
|---|---|---|---|
| **Failure statement** | One sentence, dated, written as fact | 1 | "It is April 2027. The pricing change shipped and net revenue fell." |
| **Silent lists** | Each person's raw causes, unedited, one per line | 2 | 6-12 items per person |
| **Clustered causes** | The 3-4 groups the readout produces, named by the underlying cause | 3-4 | "Renewal shock", "Sales had no fallback" |
| **Likelihood × impact** | 1-5 each, scored by the group, not the facilitator | 4 | 4 × 5 |
| **Response** | Mitigate now, set a tripwire, or accept and document | 5 | Tripwire: churn above 3% in any renewal cohort |
| **Owner** | One named person per cluster | 5 | Head of RevOps |

The first five rows are the premortem as Klein described it. The template needs one more row, because of what the method can't produce.

### The Calculator Row

A premortem generates *stories* about how the project failed. It is good at that, and it is how the method catches the social, organisational and execution risks a risk register misses. It is structurally bad at one thing: a number that is already wrong on day one. Nothing "goes wrong" in that case. The plan works as designed and the design can't pay for itself, so there's no failure story for anyone to write down.

So add one row that is filled in with a calculation instead of an imagined cause:

| Field | What goes in it |
|---|---|
| **Calculator Row** | The plan's single load-bearing number (margin per customer against the cost to acquire or onboard one, payback period, or runway at planned burn), computed before the session and written as a result, not a risk |

**Worked on a real shutdown.** Rachel Draelos ran the health AI company Cydoc from April 2018 to August 2025 and published a nine-cause postmortem in February 2026. Six of her nine causes are the kind a premortem finds easily: no early customer discovery, no sales owner, a solo-founder structure. The cause that ended the company was a pricing decision: the product sold at roughly what it cost to run, leaving about **$30 a month** of margin against a **$4,000-$6,000** integration cost per practice, which is around **11 years to break even** on each customer. No silent-writing round produces that sentence. A Calculator Row filled in on day one does, in one line. The full replay, and the **Day-One Test** this row puts into practice, is in [the Cydoc premortem example](/examples/premortem-cydoc-shutdown).

If the Calculator Row comes back fine, the session runs as normal. If it comes back broken, cancel the premortem and fix the plan: the team would be imagining failure causes for a plan whose arithmetic has already failed.

## What makes a premortem actually work

**Psychological safety is the precondition.** If the team can't say "the founders disagreed about strategy and the team felt it," the premortem will surface only safe risks (the build will be late) and miss the real ones (the founders disagree about strategy and the team feels it). A premortem in a team without safety is theater.

**The facilitator should not contribute.** If the facilitator writes their own risks, the team anchors on those. The facilitator's only job is to keep the silence, run the readout, and refuse to soften what's said.

**Write down the dissent.** Even if a risk doesn't make the top cluster, save it. Six months from now, when one of those bottom-of-list risks becomes the actual failure mode, you'll want the record.

## Common failure modes

- **The facilitator leads with examples.** Killed the exercise before it started — every subsequent answer is a variant of the example.
- **One senior person dominates the readout.** Switch to a written round-robin to neutralize.
- **The output is filed and forgotten.** Add the top 3 clusters to the project's weekly review until they're either resolved or accepted.
- **The team treats it as a vote of no-confidence.** Frame the exercise as "the project will succeed *because* we ran this," not "we're checking whether to cancel."

## When a premortem isn't enough

Premortems surface known unknowns — risks the team can imagine. They don't surface unknown unknowns. And there is a third gap that is neither: **facts that are already true and are therefore not risks at all.** A premortem asks you to explain a future failure, so it recruits story-shaped causes; an inverted unit economic has no story, because nothing goes wrong — the plan works as designed and the design cannot pay for itself. See the [Pre-mortem Example: The Failure a Premortem Cannot Catch](/examples/premortem-cydoc-shutdown) for a case where a premortem would have caught six of nine eventual causes and structurally missed the one that ended the company, and for the **Day-One Test** that covers the gap. For genuinely novel work (new market, new technology), pair the premortem with a pre-parade (the imagined-success counterpart, run identically but from a win) and a [stress test](/frameworks/stresstest) to widen the aperture. When the worry is specifically the tail risk nobody modelled, [Black Swan](/frameworks/blackswan) is the lens that names it.

If you find the same risks every time you run a premortem on every project, the team has a systemic problem upstream of any single project — fix that first.

## The 90/60/30 Premortem Cadence

Most premortem advice treats it as a one-shot meeting at the start of a project. That model leaks: risks identified at kickoff stop being tracked once execution starts, and risks that emerge mid-execution have no formal venue to surface. The 90/60/30 Cadence is a named alternative — three premortems scheduled at fixed pre-launch checkpoints, each with a deliberately different shape.

The rhythm:

| Checkpoint | Meeting shape | What you're looking for | Output |
|---|---|---|---|
| **90 days before launch** | Broad risk surface — full team + 2 outside skeptics, 90 minutes, no constraints on what counts as a risk | Strategic and structural risks: wrong target customer, wrong scope, wrong timing, missing capabilities, unrealistic timeline | A long, messy list. 20-40 candidate risks clustered into 5-7 themes. Most of these never get acted on individually — but the clustering tells you what *type* of project this is. |
| **60 days before launch** | Narrowed list with mitigations — execution leads only, 60 minutes, focused on the 90-day output | Which of the 90-day risks are now real, which were noise, and which are still hypothetical | A list of 5-8 risks with a named owner and a specific mitigation each. The 60-day meeting is where the project plan actually changes. |
| **30 days before launch** | Final reality check + monitoring assignments — full team back, 45 minutes, tight agenda | Which risks are now mitigated, which are accepted (we'll live with them), which are still uncontrolled. Plus: anything that emerged in the last 30 days that nobody anticipated. | A go/no-go-conditioned launch checklist. Each remaining risk has a category: "mitigated", "accepted", "monitored", or "blocker". Blockers stop the launch. |

Why three checkpoints, not two or four:

- **One** is the standard advice and fails for the reason above — the meeting becomes ceremonial
- **Two** (kickoff + pre-launch) miss the mid-execution drift where risks shift category
- **Three** matches the natural arc of a 90-day project: discovery (Day 1-30), execution (Day 31-60), final commit (Day 61-90). One premortem per phase forces the team to actually re-read its own analysis.
- **Four or more** becomes meeting overhead; the team starts defending instead of surfacing

What changes between the meetings:

- **Attendance**: full team → execution leads only → full team. The 60-day narrowing prevents social pressure from over-extending the list; the 90- and 30-day broadness prevents the execution leads from rationalizing.
- **Time**: 90 → 60 → 45 minutes. The shape of the meeting forces the appropriate level of detail at each stage.
- **Question prompt**: "what would make this fail?" → "of these, which are now real?" → "what hasn't been mitigated, and what's the plan?"

Tools and post-meeting protocol:

- The 90-day list goes into the project's risk tracking doc, organized by cluster
- The 60-day mitigations become explicit line items in the project plan, with owners
- The 30-day output becomes the launch checklist, with go/no-go authority for each blocker

For projects shorter than 90 days, compress proportionally: a 30-day project gets premortems at Day 1, Day 15, and Day 25. The shape — broad → narrow → final-check — stays the same.

For longer projects (multi-quarter initiatives), the Cadence runs at the start of each quarter rather than at fixed days. Most teams find that the 90/60/30 pattern transfers cleanly: a one-year initiative gets premortems at Q1-kickoff, Q2-narrowing, and Q3-final-check, with Q4 reserved for execution against an already-locked plan.

For when to choose this versus the lighter-weight cousin, see [Reverse Brainstorming](/academy/reverse-brainstorming-solve-problems-backwards) and [Premortem vs Postmortem](/compare/premortem-vs-postmortem).

> **Running a premortem before your next launch?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=premortem-academy) ships the premortem worksheet — imagine the failure, list the causes, assign the mitigations, all on one screen. Free to start.

## Related frameworks

- [Premortem — catalog entry & template](/frameworks/premortem) — the quick-reference worksheet for running one
- [Cynefin Framework for PMP](/academy/cynefin-framework-for-pmp) — premortems are the Complex-domain partner; Cynefin tells you when to reach for one
- [Premortem vs Postmortem](/compare/premortem-vs-postmortem) — when to run each in the project lifecycle
- [Reverse Brainstorming](/academy/reverse-brainstorming-solve-problems-backwards) — inversion-thinking cousin of the premortem; lighter, generates options not just risks
- [SWOT analysis](/academy/what-is-a-swot-analysis) — broader strategic surface for the same question
- [FMEA](/frameworks/fmea) — heavier-weight industrial cousin of the premortem
- [Risk matrix](/frameworks/riskmatrix) — for ranking the premortem's output by likelihood × impact
- [Reverse brainstorming](/frameworks/reversebrain) — inversion, the mental model underneath premortems, run as a workshop
- [Premortem for a SaaS launch](/playbooks/premortem-for-saas-launch) — industry playbook applying the premortem to a product launch

Want to run one right now? [Open the free premortem template →](/tools/premortem) and start writing.

---

### Jobs-to-be-Done Examples: 8 Real Companies (2026)
URL: https://frameworklist.com/academy/jobs-to-be-done-examples
> Eight worked Jobs-to-be-Done examples from real companies — Duolingo, Netflix, Slack, Uber and more — mapped to functional, emotional and social jobs, plus how to write your own JTBD statement from one.

The best way to learn **Jobs-to-be-Done** is not to define it again — it's to see the framework applied to products you already use. Below are **eight worked Jobs-to-be-Done examples from real companies**, each mapped to the job the product is *actually* hired for, followed by a template for turning any of them into a JTBD statement for your own product. If you want the theory first, start with our [JTBD framework explained](/academy/jobs-to-be-done-framework-explained) guide; this page is the examples.

The reason examples matter more than definitions here is that JTBD's whole point is a reframe: [customers don't buy products, they hire them for a job](/glossary/jtbd). You only feel that reframe when you watch a familiar product stop being "a language app" and start being "a way to feel productive for five minutes." That shift — from product category to job — is the entire skill.

> **Want to run JTBD on your own product?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=jtbd-examples-academy) walks you through the situation, motivation, and outcome for each job with AI-assisted prompts. Free to start.

## The three types of jobs every example has

Before the examples, the one distinction that makes them readable. Every job a customer hires a product for sits in one of three layers — and strong products serve all three at once.

| Job layer | What it is | The question it answers |
|---|---|---|
| **Functional** | The practical task to get done | "What am I literally trying to accomplish?" |
| **Emotional** | How the customer wants to feel | "How do I want this to make me feel — or stop feeling?" |
| **Social** | How the customer wants to be perceived | "What does using this say about me to others?" |

The classic mistake in reading a JTBD example is stopping at the functional layer. "People hire Instagram to share photos" is the functional job and it explains almost nothing. The emotional job (feel like my life is interesting) and the social job (be seen as someone with taste) are what actually drove the growth. Keep all three in view for every example below.

## The Three-Layer Job Map: 8 real companies

Here is the citable version — eight products you know, each decomposed into its functional, emotional, and social job. Read down any column to see a pattern; read across any row to see why a single product beats competitors that only serve one layer.

| Company | Functional job | Emotional job | Social job |
|---|---|---|---|
| **Duolingo** | Practice a language in spare minutes | Feel productive, not guilty, about downtime | Be seen as someone who's "learning Spanish" |
| **Netflix** | Fill unstructured free time with something watchable | Stop the anxiety of "what do I even put on" | Have something to talk about tomorrow |
| **Slack** | Keep team communication in one searchable place | Feel on top of work, not buried in email | Look responsive and organized to the team |
| **Uber** | Get from A to B without owning a car | Remove the anxiety of hailing, waiting, haggling | Signal you can afford convenience |
| **Spotify** | Have the right music for any moment | Match or shift my mood on demand | Show identity through playlists and Wrapped |
| **Notion** | Store notes, docs, and tasks in one system | Feel like my "second brain" isn't leaking | Be the person with the beautiful workspace |
| **LinkedIn** | Find a job or a hire | Feel career-secure and in-demand | Be seen as a credible professional |
| **ChatGPT** | Get a usable draft or answer fast | Feel capable at things I'm not expert in | Appear more productive than my peers |

I call this the **Three-Layer Job Map** — the discipline of never accepting a one-line "they hire it to X" example until all three layers are named. It's the fastest way to spot which layer your own product is under-serving. Most products win on functional and lose on emotional or social; the map makes that gap visible in one row.

## Worked example: what Duolingo is really hired for (Q1 2026)

The single most instructive JTBD example right now is Duolingo, because its own numbers prove the point. In its [Q1 2026 results](https://www.fool.com/earnings/call-transcripts/2026/05/04/duolingo-duol-q1-2026-earnings-transcript/), daily active users grew **21% year over year to 56.5 million** — the first quarter in company history above 55 million — while revenue rose **27% to $292 million** ([Duolingo 10-Q, Q1 2026](https://www.stocktitan.net/sec-filings/DUOL/10-q-duolingo-inc-quarterly-earnings-report-e6bc1fce9982.html)).

Here's the tell. If people hired Duolingo to *become fluent*, its retention would track course completion — and course completion is famously low. It doesn't. Retention tracks the **streak**. The functional job ("learn Spanish") is real but weak; the durable job is emotional and behavioral: *feel productive during idle minutes without the guilt of scrolling, and don't break the chain.*

Everything in the product is built for that real job, not the stated one:

| Feature | Stated job it serves | Real job it serves |
|---|---|---|
| Daily streak counter | Track learning progress | Create loss-aversion so skipping a day *hurts* |
| Streak Freeze | Forgive a missed lesson | Remove the anxiety that one slip ruins the habit |
| Leaderboards / leagues | Motivate practice | Add a social job — being seen keeping up |
| Push notifications | Remind you to study | Re-trigger the habit loop at the same time daily |

Third-party case studies estimate the Streak Freeze feature alone cut churn by about **21% for at-risk users**, and that users who reach a 7-day streak are roughly **3.6× more likely to stay engaged** ([Trophy — Duolingo gamification case study, 2026](https://trophy.so/blog/duolingo-gamification-case-study)). Those are habit-formation numbers, not education numbers. A team that ran a JTBD interview and heard "I want to feel like I did something with my commute" would build exactly this product. A team that believed the functional job would keep adding grammar features and wonder why nobody finished the course.

The lesson that generalizes: **when a product's retention doesn't match its stated purpose, the real job is hiding one layer down.** Find it and you find the roadmap.

## How to write a JTBD statement from an example

Examples are only useful if you can convert one into a statement for your own product. Use the canonical template:

> **When** [situation], **I want to** [motivation], **so I can** [expected outcome].

Watch it fill for three of the examples above:

- **Duolingo** — *When I have a few idle minutes and feel like I'm wasting them, I want to do something that feels productive, so I can end the day without guilt.*
- **Slack** — *When a decision is scattered across email threads and DMs, I want one searchable place my whole team can see, so I can stop re-explaining context.*
- **Uber** — *When I need to get somewhere and don't want to drive or wait, I want a ride to arrive on demand, so I can stop worrying about the logistics of getting there.*

The test for your own statement is falsifiability: five real customers should be able to **confirm or reject it**. "When I'm busy, I want to be productive, so I can succeed" passes no test — it could never be wrong, so it's not a job. For the full interview structure that produces these statements, see the [JTBD framework explained](/academy/jobs-to-be-done-framework-explained) walkthrough.

## B2B examples work differently: stack the jobs

Consumer examples have one hero job. **B2B examples have a stack**, because the buyer is a committee and each member hires the product for a different job. Collapsing them into the end user's job is the most common way B2B JTBD analysis goes wrong.

Take Figma as a worked B2B example:

| Buyer role | The job they hire Figma for | Layer |
|---|---|---|
| **Designer (end user)** | Design without version chaos or file handoffs | Functional |
| **Design lead** | Keep the whole team working on one live canvas | Functional + emotional |
| **Procurement / IT** | SSO, audit logs, and a defensible security posture | Functional (compliance) |
| **VP who signs off** | Look like they backed the modern, safe standard | Social |

A B2B pitch that only speaks to the designer's job loses the deal in procurement; one that only speaks to compliance never gets the designers to adopt it. This is why B2B JTBD work maps every role's job before writing a single feature. It's also where JTBD hands off to other artifacts — once the jobs are clear, see [JTBD vs personas](/compare/jtbd-vs-personas) for who to build for and [JTBD vs user stories](/compare/jtbd-vs-user-stories) for how to spec it.

## Common mistakes when copying a JTBD example

Borrowing an example is smart; borrowing it wrong is the fast path to a roadmap that misses. The three failures below account for most of it.

| Mistake | Why it happens | Fix |
|---|---|---|
| **Stopping at the functional job** | It's the easiest layer to name and feels "objective" | Force the emotional and social layers — that's where growth lives |
| **Copying the example's *solution*, not its *job*** | Duolingo's streak worked, so every app bolts on a streak | Extract the job (fight guilt over idle time), then design *your* solution for it |
| **Writing an unfalsifiable statement** | Generic feels safe and applies to everyone | If five customers couldn't reject it, it's a slogan, not a job |

For a fuller worked case, our [JTBD applied to Instagram Stories](/examples/jtbd-instagram-stories) example runs the same three-layer analysis on a single feature launch.

## Sources

- [The Motley Fool — "Duolingo (DUOL) Q1 2026 Earnings Call Transcript"](https://www.fool.com/earnings/call-transcripts/2026/05/04/duolingo-duol-q1-2026-earnings-transcript/)
- [StockTitan — "Duolingo (NASDAQ: DUOL) 10-Q, Q1 2026 quarterly earnings report"](https://www.stocktitan.net/sec-filings/DUOL/10-q-duolingo-inc-quarterly-earnings-report-e6bc1fce9982.html)
- [Trophy — "Duolingo Gamification Strategy: A Full Case Study (2026)"](https://trophy.so/blog/duolingo-gamification-case-study)
- [Harvard Business School Online — "The Jobs to Be Done Framework & Real-World Examples"](https://online.hbs.edu/blog/post/jobs-to-be-done-examples)

## Related

- [Jobs-to-be-Done framework explained](/academy/jobs-to-be-done-framework-explained) — the definition, the interview structure, and the statement template
- [JTBD vs personas](/compare/jtbd-vs-personas) — which lens to use when
- [JTBD vs user stories](/compare/jtbd-vs-user-stories) — how JTBD hands off to specs
- [JTBD applied to Instagram Stories](/examples/jtbd-instagram-stories) — a single-feature worked example

---

### Jobs-to-be-Done Framework: Definition, Template & Examples (2026)
URL: https://frameworklist.com/academy/jobs-to-be-done-framework-explained
> JTBD says customers don't buy products — they hire them for a job. The framework's definition, the JTBD statement template, and worked examples from B2B SaaS, consumer apps, and AI products.

**Jobs-to-be-Done** ([JTBD](/glossary/jtbd)) is a framework that reframes what people buy. Instead of asking "what features should this product have?", JTBD asks "what job is the customer hiring this product to do?". The product is incidental; the *job* is the durable unit of customer demand. Get the job right and you understand the market.

The framing was developed by Clayton Christensen and colleagues at Harvard Business School, building on earlier work by Tony Ulwick. The canonical example: McDonald's wanted to sell more milkshakes. Years of customer surveys produced incremental tweaks (thicker, sweeter, more flavors) and no growth. When researchers asked instead "what job were buyers *hiring* the milkshake to do?" they discovered ~40% of milkshakes were bought before 8am — commuters used them as a one-handed, slow-to-finish, mildly entertaining solution to a boring drive. That job — *make my morning commute less dull* — competed with bagels, bananas, and boredom itself, not with other milkshakes.

## The core moves

JTBD's contribution is three reframings:

1. **Customers don't buy products; they hire solutions for jobs.** A drill is hired to make a hole in a wall. A spreadsheet is hired to think through a decision. A self-help book is hired to feel like you're making progress on a problem you're not yet ready to act on.
2. **The unit of competition is the job, not the product category.** Your milkshake competes with bananas. Your CRM competes with spreadsheets and post-it notes. Your meditation app competes with a glass of wine.
3. **The job is stable; the solutions change.** People have been hiring something to "communicate quickly with a distant friend" for centuries (letters → telegraph → telephone → SMS → WhatsApp). The job is the same. The hired solutions change as technology lets them be better-served.

## When to use JTBD

- **Defining a new product**: forces you to articulate the customer's actual goal rather than your assumed feature list
- **Repositioning** an existing product whose growth has stalled despite good execution — usually means the wrong job is being targeted
- **Identifying real competitors** before market research overstates the obvious ones and misses the actual substitutes
- **Customer-interview design**: gives you a question structure (when did you last hire X? what were you trying to accomplish? what almost stopped you?) that produces sharper insights than "what features do you want?"

Skip JTBD when you're optimizing within a well-defined job (e.g., faster checkout, better latency). It's a framing tool, not an optimization tool.

## How to actually use it

The lightweight version (good for most teams): run **5–8 interviews** with recent buyers using the JTBD interview structure, then synthesize.

1. **Pick a recent purchase, narrow the window.** "Tell me about the last time you bought/used this — when was it, what triggered it?" Specific recent events produce concrete answers; abstract questions produce abstract answers.
2. **Walk the timeline backwards from purchase.** First thought → first search → first comparison → decision → first use → reaction. The triggering event is rarely what people first say; keep going further back.
3. **Identify what they hired the product to do.** Listen for the goal, not the activity. "I bought a Notion subscription" is the activity. "I wanted to stop feeling like my second brain was leaking out my ears" is the job.
4. **Identify what almost stopped them.** Anxieties about switching, habits they had to break, social signals they were worried about. These tell you the *friction* attached to your job.
5. **Cluster across interviews.** When 5+ interviews independently surface the same job, you have signal. When jobs vary widely, your product is being hired for multiple jobs and you're under-serving each.

## The trap

The trap is treating JTBD as a category of language rather than a discipline of research. Teams adopt the vocabulary ("our job is to help users feel productive") without actually doing the interviews. The result is a more impressive-sounding version of the same feature list.

The corrective: **never write a "job" you didn't hear in an actual customer's words**. The McDonald's milkshake job wasn't generated by a strategy offsite. It came from a researcher noticing that 40% of purchases happened pre-8am and asking those buyers why.

## What JTBD reveals that feature lists hide

Two examples from real engagements:

- **A B2B SaaS team** thought they competed with three other SaaS products. JTBD interviews revealed their real competition was Excel + an internal champion's heroism. Their pricing, sales motion, and onboarding all needed to change — they were positioned against software-savvy decision-makers but were actually being evaluated by spreadsheet-savvy operators.
- **A consumer mobile app** had years of stagnant retention. JTBD interviews showed half the users were hiring it to *feel productive while procrastinating something harder*. The team had been optimizing the "actually be productive" job. Once they accepted what users were really hiring it for, the redesign was obvious — and retention jumped.

## JTBD vs Personas vs User Stories: pick the right artifact

Teams routinely confuse these three because they all "describe the customer." They don't — they describe different layers of the same problem, and using the wrong one produces predictable failures:

| | Jobs-to-be-Done | [Personas](/glossary/icp) | User Stories |
|---|---|---|---|
| **What it describes** | A *job* the customer is trying to make progress on | A *type* of customer with attributes | A *feature* a user wants and why |
| **Format** | "When [situation], I want to [motivation], so I can [outcome]" | Named profile + demographics + goals + pain points | "As a [role], I want [feature], so that [benefit]" |
| **Best used for** | Defining what business you're in; finding non-obvious competitors | Marketing segmentation; design empathy artifacts | Backlog grooming; sprint planning |
| **Worst used for** | Sprint-level feature decisions | Strategic positioning (personas hide jobs) | Discovery (you're already assuming the feature) |
| **Stable over time?** | Yes — jobs change slowly | Decays as the market evolves | Each story is disposable |
| **When you'd write it** | Quarterly or before a pivot | Annually or for a new market entry | Every sprint |

**The sequencing rule**: JTBD comes *first*, personas come *second*, user stories come *last*. Skipping to user stories without a clear job is how teams ship features for problems no one is paying to solve. Jumping from personas to features (without the job in between) is how teams build "what someone like Maya wants" without checking whether Maya is actually trying to *do* anything with it.

Framework's [JTBD vs Personas compare page](/compare/jtbd-vs-personas) goes deeper on the first two, including when personas remain the right tool despite JTBD's broader reach. For the last rung — turning a job into shippable increments — see [JTBD vs user stories](/compare/jtbd-vs-user-stories), which lays out the Job-to-Story Ladder from strategy to sprint ticket.

## When JTBD isn't the right tool

- **Highly commoditized purchase decisions** where the job is obvious and the buyer cares about a single dimension (price, speed). JTBD reveals nothing new.
- **Greenfield exploration** with no product yet. JTBD requires that *something* be getting hired — you need real buyers to interview. For pre-product exploration, use [First Principles](/academy/first-principles-thinking-with-examples) instead.
- **Tactical UX decisions.** JTBD operates at the level of "what business should we be in"; it's the wrong granularity for "should this button be left or right of the form."

> **Want to write job statements on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=jtbd-academy) fills in the JTBD template with AI-assisted prompts — situation, motivation, expected outcome. Free to start.

## Related frameworks

- [Jobs-to-be-Done examples: 8 real companies](/academy/jobs-to-be-done-examples) — Duolingo, Netflix, Slack, Uber and more, each mapped to its functional, emotional, and social job
- [JTBD applied to Instagram Stories](/examples/jtbd-instagram-stories) — worked example of JTBD on a real consumer product launch
- [SWOT analysis](/academy/what-is-a-swot-analysis) — pair when you need to map JTBD insight onto strategic position
- [Kano Model](/frameworks/kano) — once the job is right, Kano classifies which features satisfy vs delight vs dissatisfy
- [Lean Canvas](/frameworks/lean) — operationalizes a JTBD insight into a testable business model
- [Five Forces](/academy/porters-five-forces-beginners-guide) — useful counterweight: JTBD looks customer-out; Five Forces looks industry-in
- [JTBD for healthcare & digital health](/playbooks/jtbd-for-healthcare) — industry playbook for the category where the buyer is rarely the user
- [Product-Market Fit Examples (2026)](/academy/product-market-fit-examples) — once the job is defined, this scores whether real products actually fit it

Want examples? [The full JTBD entry →](/frameworks/jtbd) has worked applications across consumer, B2B SaaS, and services.

---

### McKinsey 7S Framework: Hard and Soft Elements Explained
URL: https://frameworklist.com/academy/mckinsey-7s-framework-hard-soft-elements
> The McKinsey 7S Framework sorts seven organizational elements into Hard S's (Strategy, Structure, Systems) and Soft S's (Shared Values, Skills, Style, Staff). Here's how the split works, why it matters for execution, and a worked example.

The McKinsey 7S Framework's most quoted feature is the seven S's themselves — Strategy, Structure, Systems, Shared Values, Skills, Style, Staff — but its most useful feature is the split between **Hard** and **Soft** elements. Three of the seven are Hard: tangible, directly controllable by management, and visible in formal documents. Four are Soft: cultural, capability-based, and impossible to change by memo. The diagnostic value of the framework lives almost entirely in that asymmetry.

This guide explains the Hard/Soft split, why it exists, how to score a real organization across the seven elements, and a named diagnostic (the **Hard-Soft Asymmetry Rule**) for catching the most common misalignment 7S surfaces in modern transformations.

> Want to run a 7S diagnostic on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?mt=8) ships a 7S worksheet with all seven elements and the Hard/Soft scoring grid built in.

### Prefer to watch or listen?

<YouTube id="f8GMWWmxzok" title="McKinsey 7S Framework: Hard and Soft Elements Explained" />

<Spotify id="2vYPrUj4A7QIrDnipB7DBC" title="McKinsey 7S Framework: Hard vs Soft Elements — Framework podcast episode" />

## The Hard and Soft split: where it came from

The framework was developed in 1978-1980 by McKinsey consultants Tom Peters, Robert Waterman, Richard Pascale, and Anthony Athos. Its first formal publication was Waterman, Peters, and Julien Phillips's 1980 *Business Horizons* paper "[Structure Is Not Organization](https://tompeters.com/docs/Structure_Is_Not_Organization.pdf)" — and the title itself is the thesis. The authors had observed that strategy programs led by Hard-S analysis alone (re-org the structure, redesign the systems, restate the strategy) consistently underdelivered. The Four Soft S's existed precisely to name what was missing.

The seven were chosen because they all began with S (the "atomic mnemonic" rationale Peters has since admitted) — but the Hard/Soft split was the substantive contribution. Without it, 7S would be a checklist. With it, the framework forces the recognition that **management can command three elements and can only cultivate four**, and that strategy execution depends on whether the cultivated four catch up to the commanded three before the program's window closes.

## The three Hard S's

The Hard elements are the parts of the organization that show up in formal documents and reporting lines.

| Element | What it is | How management changes it | Typical timescale to shift |
|---|---|---|---|
| **Strategy** | The plan for competitive advantage, the markets served, the bets being placed | Strategy review, board approval, communication cascade | 3-12 months to articulate, 12-36 to execute |
| **Structure** | The organizational chart — reporting lines, divisions, business units, functions | Re-org announcement, role redefinitions, span-of-control changes | 3-9 months to reorganize, 12-24 to settle |
| **Systems** | The processes, workflows, information flows, IT, compensation, performance review | Process redesign, new tools, new metrics | 6-18 months per major system |

### Strategy

The plan for how the organization wins. Markets, customers, value proposition, competitive positioning, and the resource allocation that follows from those choices. In 7S, Strategy is treated as one of seven inputs, not the dominant input — a deliberate choice by the authors, who wanted to push back on the strategy-first orthodoxy of late-1970s corporate planning.

What "high alignment" looks like for Strategy: a one-page articulation that a frontline employee can repeat, a clear set of choices about what the organization will *not* do, and resource allocation that visibly tracks the stated priorities. The framework treats unstated trade-offs as the most common Strategy failure mode.

### Structure

The formal organizational chart — who reports to whom, how groups are organized (by function, by product, by geography, by customer segment), and how decision rights flow. Structure is the most visible Hard element and the one organizations are quickest to change when they want to *appear* to be transforming.

The 7S diagnostic question for Structure: does the chart support the Strategy, or is it a legacy of a previous Strategy? Functional structures support deep expertise and integration; divisional structures support speed and accountability; matrix structures support complexity but at coordination cost. None is right in the abstract — the right one is the one that matches the current Strategy.

### Systems

The processes by which work gets done. Information systems, financial reporting, performance management, hiring, onboarding, decision-making routines, compensation, planning cycles, customer interactions. Systems are the slowest Hard element to change — partly because they're the most embedded in daily work, partly because they encode learned behaviour that survives policy changes.

The 7S diagnostic question for Systems: which Systems were designed for the previous Strategy and are now compounding misalignment? In post-merger integration work, the answer is usually "most of them" — which is why M&A integration playbooks devote so much time to Systems convergence.

## The four Soft S's

The Soft elements are the parts of the organization that don't show up in org charts but determine whether the Hard S's actually function.

| Element | What it is | How management influences it | Typical timescale to shift |
|---|---|---|---|
| **Shared Values** | The core beliefs and culture — what the organization actually rewards and protects | Founder example, executive selection, decision precedents | 3-7+ years; often a leadership generation |
| **Skills** | The collective capabilities the organization is known for | Hiring strategy, training investment, project assignments | 2-5 years |
| **Style** | The leadership and management style — how decisions get made, how disagreement is handled | CEO and executive-team modelling, removal of misaligned leaders | 2-5 years |
| **Staff** | The composition of the workforce — seniority, demographics, talent mix | Hiring, retention, promotion, performance management | 2-5 years; faster at small scale |

### Shared Values

The cultural foundation — what the organization actually believes is worth doing, even when no one is watching. Sometimes called "Superordinate Goals" in the original 1980 paper. Shared Values sit at the centre of the model because they influence every other element: a privacy-centric Shared Value reshapes Strategy (what products are even considered), Structure (how data flows across teams), Systems (what's logged and what isn't), Skills (what engineers are hired for), Style (how leaders talk about trade-offs), and Staff (who self-selects in or out).

Shared Values is the slowest element to shift because it's the cumulative output of every prior decision the organization has reinforced. A new CEO can announce new values; only the precedents that follow over the next 3-7 years determine whether they stick.

### Skills

The distinctive capabilities the organization is known for. Not individual skills (those are Staff) but the *collective* skill profile that gives the organization its competitive identity — Apple's vertical integration, Disney's storytelling, McKinsey's analytical rigour, Toyota's manufacturing systems. Skills are what's left when individual employees leave; they're embedded in routines, methods, and shared know-how.

The 7S diagnostic question for Skills: which Skills did the previous Strategy require, and which does the new Strategy require? A pivot from hardware-led to services-led typically requires Skills in subscription analytics, customer success, and content acquisition that the hardware-era organization didn't need to develop. Skills lag Strategy by years.

### Style

The dominant management and leadership style — top-down or consensus, fast or deliberate, public-facing or restrained, conflict-confronting or conflict-avoidant. Style is set primarily by the CEO and executive team and reinforced by who gets promoted. It's the element most often denied (every leadership team claims a balanced Style) and most observable from outside (employees, customers, and analysts all read Style consistently).

Style matters because it determines which kinds of decisions get made well. A top-down Style makes scaled execution efficient and makes Complex-domain exploration brittle. A consensus Style enables broad alignment and slows urgent decisions. Neither is right in the abstract; the right Style is the one that matches the Strategy.

### Staff

The composition of the workforce — total headcount, seniority distribution, demographic mix, talent profile, retention patterns. Staff is sometimes treated as a synonym for Skills, but the framework keeps them separate: Skills are the *collective capability*, Staff is the *individual composition*. An organization can have strong Skills with a thinning Staff (institutional knowledge embedded in too few people), or strong Staff with weak Skills (talented individuals without organizational scaffolding).

The 7S diagnostic question for Staff: does the current composition match what the Strategy will require in 24-36 months? Hiring lags Strategy by 12-18 months even on aggressive timelines; performance management and retention decisions take longer. The Staff element is where the cultural-lag of the Soft S's is most concretely measurable.

## The Hard-Soft Asymmetry Rule

The single most useful artefact this guide adds to the standard 7S explanation is the diagnostic rule below, which names the most common failure mode in 7S-style transformations.

> **The Hard-Soft Asymmetry Rule.** In any 7S-style transformation, Hard elements (Strategy, Structure, Systems) can be realigned within 6-18 months. Soft elements (Shared Values, Skills, Style, Staff) take 3-7 years, and Shared Values can take a leadership generation. If the transformation's success window doesn't accommodate this asymmetry, the program will fail not in Hard-S execution but in the Soft-S lag that opens 12-24 months in — when the new Strategy is structurally in place but the cultural, capability, and people composition required to operate it haven't caught up.

How to use the rule:

1. **Score current state** of all seven elements on a 1-5 scale relative to the *new* Strategy you're targeting (not the old one)
2. **Identify which Hard S's need to shift** to support the new Strategy. Project how long each shift takes.
3. **Identify which Soft S's need to shift** to support the new Strategy. Project how long each shift takes.
4. **Compare timescales.** If your Soft-S shifts require 3-7 years and your transformation has a 24-month window, you have an asymmetry problem. Either extend the window, narrow the Strategy, or design Soft-S work to start *before* the Hard-S work — not after.
5. **Re-score every 6 months.** The 18-month mark is when the asymmetry compounds; missed targets at month 18 are usually Soft-S debt that the Hard-S work has revealed.

The rule applies most sharply in:

- **Post-merger integration** — Hard S's (combined entity Structure, consolidated Systems) can be set in 12-18 months; Skills, Style, and Staff convergence takes 3-5 years. Most "failed mergers" are Asymmetry failures.
- **Digital transformations** — new Systems can be deployed in 12-24 months; the Skills, Style, and Staff to actually *use* them at scale takes 3-5 years. Most "stalled digital transformations" are the same.
- **Strategic pivots** in mature companies — new Strategy can be announced and Structure adjusted in 12 months; the Skills and Shared Values to execute the pivot take a full leadership generation.

## How to actually run a 7S diagnostic

The framework was designed as a structured group conversation, not a one-person analytical exercise. The standard workflow:

1. **Define the strategic question.** What decision is this 7S meant to inform? "Are we aligned to execute Strategy X?" or "Where will integration of Acquisition Y break first?" or "What needs to shift for digital strategy Z to land?"
2. **Recruit a cross-functional group.** 6-12 people who collectively see Hard and Soft elements from multiple vantage points. Pure executives over-score Hard S's; pure frontline employees over-score Soft S's. A mix is essential.
3. **Score each element 1-5 against the target state.** Independent scoring first (no group anchoring), then discussion. The discussion is the deliverable, not the average.
4. **Surface the misalignments.** Which elements are 4-5 (well-aligned to target) and which are 1-2 (drifted from target)? The gap is the diagnostic.
5. **Apply the Hard-Soft Asymmetry Rule** (above). For each misaligned Soft S, project the shift timeline. Compare against the program window. Re-plan the program if the asymmetry doesn't close in time.
6. **Pick the load-bearing element to shift first.** It's usually a Soft S, because the Hard S's tend to shift faster once chosen and the Soft S's are the bottleneck.
7. **Re-score at 6, 12, and 18 months.** The first re-score should show Hard S's moving; the 18-month re-score is when Soft-S drift either confirms or undoes the program.

## A worked example: Apple in 2026

For a full 7S analysis of a real company in 2026, the [Apple McKinsey 7S Analysis 2026](/examples/apple-mckinsey-7s-analysis-2026) walks through how 7S scored the Hard S's (Strategy, Structure, Systems — world-class and aligned) and the Soft S's (Shared Values, Skills, Style, Staff — three of the four had drifted relative to the new AI-services Strategy) in May 2026. The Apple case is a clean illustration of the Hard-Soft Asymmetry: the Strategy is set, the Structure largely supports it, the Systems are being upgraded — and the Skills, Style, and Staff in frontier ML are the lagging elements that determine whether the strategy actually executes over 2026-2028.

It is also the best available test of what the asymmetry predicts a company will *do* about a Soft-S gap. The page was [re-scored in September 2026](/examples/apple-mckinsey-7s-analysis-2026#re-scored-in-september-2026-which-ss-actually-moved), after John Ternus replaced Tim Cook as CEO, and the answer was not the one the May analysis expected: the elements that moved were mostly Hard — a consolidated Structure, a Systems contract with Google for the frontier model — while the Soft-S gap was routed around rather than closed. That is the asymmetry operating in reverse: when the Soft S's take 3-7 years and the strategy needs a result in one, the organization buys. The [Buy-or-Become Test](/examples/apple-mckinsey-7s-analysis-2026#the-buy-or-become-test) on that page names the pattern and the dependency it creates.

Two other worked examples in the Framework library, chosen to show 7S in different contexts:

- [Apple PESTEL Analysis 2026](/examples/apple-pestel-analysis-2026) — same company, different lens. PESTEL scans the macro environment 7S can't see. Use both side-by-side.
- [Tesla VRIO Analysis 2026](/examples/tesla-vrio-analysis-2026) — VRIO scores the company's resources against the market; 7S scores the same company's elements against the strategy. Two different alignment questions on the same firm.

## When NOT to use 7S

- **For pure financial decisions.** 7S is an organizational alignment diagnostic, not a financial model. If the question is "should we invest in X market?" use [Porter's Five Forces](/academy/porters-five-forces-beginners-guide), VRIO, or NPV analysis — not 7S.
- **For very small organizations.** Below ~50 people, the seven elements collapse into 2-3 (the founder is the Style, the Strategy, and the Shared Values). Use a simpler diagnostic — [SWOT](/frameworks/swot) or [Lean Canvas](/frameworks/lean) — until scale makes the seven distinct.
- **In real time during a crisis.** 7S is a deliberate group exercise. In a Chaotic-domain situation (see [Cynefin](/academy/cynefin-framework-for-pmp) for the domain definitions), stabilize first and run 7S after.
- **As a one-time snapshot.** 7S without re-scoring at 6-18 months is decoration. If you're not willing to re-score, don't bother with the first scoring either.

## Common mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Scoring only Hard S's | They're easier to assess; documents exist | Force Soft-S scoring with concrete behavioural evidence ("name three decisions in the last 6 months that demonstrate this Style") |
| Treating Shared Values as a slogan, not a behaviour | Marketing language has corrupted "values" | Score Shared Values by what gets rewarded and punished, not by what's on the website |
| Letting executives score the Soft S's | They have a vested interest in scoring high | Mix executives, middle managers, and frontline staff in scoring; surface the gap between the scores as a finding |
| Using the framework to confirm a decision already made | Framework as decoration | If the 7S scoring happens to confirm everything you wanted to do, you didn't run it independently — redo with adversarial-minded participants |
| Skipping the re-score at 18 months | Initial scoring feels sufficient | Calendar the re-score at the kickoff. The 18-month re-score is the one that reveals whether the Hard-Soft Asymmetry was closed or not. |
| Confusing Skills with Staff | Both are people-related | Skills = collective capability that survives turnover; Staff = individual composition. A team can lose Staff and retain Skills if the routines are robust. |

## Related frameworks

- [McKinsey 7S framework catalog entry](/frameworks/mckinsey7s) — the canonical seven elements with worksheet template
- [Apple McKinsey 7S Analysis 2026](/examples/apple-mckinsey-7s-analysis-2026) — full worked diagnostic on a real $3T company
- [PSG McKinsey 7S: the post-Mbappé team-first reset](/examples/psg-mckinsey-7s-2026) — the cleanest soft-S case: maxed hard S's for a decade, won only after the soft S's realigned
- [SpaceX–Cursor Acquisition: a McKinsey 7S Integration Analysis (2026)](/examples/spacex-cursor-mckinsey-7s-2026) — 7S on a live $60B M&A deal where the hard S's align and all the risk sits in Staff and Style
- [Cynefin Framework for PMP](/academy/cynefin-framework-for-pmp) — matching project approach to context; complements 7S's organizational-alignment lens
- [JTBD framework explained](/academy/jobs-to-be-done-framework-explained) — for the customer-side of the Strategy element
- [Porter's Five Forces beginner's guide](/academy/porters-five-forces-beginners-guide) — industry-level analysis for the external context 7S doesn't cover

> Run 7S on your phone with the diagnostic prompts built in: [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?mt=8) ships the seven-element worksheet plus the Hard-Soft Asymmetry Rule scoring grid.

---

### OKR Examples for Product Teams: Outcomes, Not Outputs
URL: https://frameworklist.com/academy/okr-examples-for-product-teams
> Six outcome-based OKR examples for product teams across discovery, activation, retention and growth — plus the Output Smell Test that kills roadmap-disguised key results.

**Most OKR examples for product teams are secretly roadmaps.** "Launch the new onboarding flow," "ship dark mode," "release the API v2" — these read like goals but they're a to-do list with a quarterly deadline. A real product OKR commits to a *change in user behavior*, not a list of things you'll build. The difference decides whether OKRs focus your team or just decorate your roadmap.

This page gives you six outcome-based OKR examples — one per product focus area — a named diagnostic for catching the roadmap-in-disguise problem, and a worked example grounded in a real company's current priorities. If you also need the OKR-vs-KPI distinction first, start with [OKRs vs KPIs](/academy/okrs-vs-kpis-difference).

## What makes a product OKR different

Every OKR has two parts. The **Objective** is one qualitative, inspiring sentence — the change you want. The **Key Results** are 3–5 quantitative measures that, if hit, mean the Objective happened. The trap unique to product teams is that we live next to the roadmap, so our Key Results drift toward *what we'll ship* instead of *what will change*.

| | Output Key Result (weak) | Outcome Key Result (strong) |
|---|---|---|
| What it measures | Work the team controls | Behavior the work is meant to change |
| Example | "Ship the redesigned checkout" | "Raise checkout completion from 61% to 75%" |
| Risk | You can hit it and change nothing | You can only hit it if the product actually improved |
| Who recognizes it | The team | The CFO, the board, the user |

The rule: **a Key Result you can fully achieve by shipping something nobody adopts is an output, not an outcome.** Outputs belong on the roadmap. Outcomes belong in the OKR.

## The Output Smell Test

Before any Key Result goes on your quarterly list, run it through these three yes/no questions. The first time you smell an output, rewrite it.

| # | Question | A "Yes" (or "No" on #3) means → |
|---|---|---|
| 1 | Could you fully hit this KR by shipping something **nobody uses**? | **Output.** The KR measures delivery, not impact. |
| 2 | Does the KR **name a feature** or use a build/ship/launch/release verb? | **Output.** You've written a roadmap item with a date. |
| 3 | If you hit it, would a number the **CFO or your North Star already tracks** move? | If **No** → **Output.** No outcome is connected to it. |

**Two or more output flags → rewrite the KR as the metric the feature is supposed to move.** Most product teams running this on their proposed quarter find a third to half of their Key Results are outputs wearing an OKR costume — usually because someone wanted the visibility of an OKR for work that should just live on the roadmap.

| Output KR (fails the Smell Test) | Rewritten as an outcome KR |
|---|---|
| Launch the new referral feature | Raise referral-sourced signups from 12% to 25% |
| Ship the onboarding redesign | Increase Day-1 activation from 32% to 50% |
| Release the mobile push system | Lift DAU/MAU ratio from 0.22 to 0.30 |
| Build the self-serve upgrade flow | Grow self-serve conversion from 4% to 9% |

The output column isn't *wrong* — those things may genuinely need building. They just belong on the roadmap that *serves* the OKR, not in the OKR itself.

## Six OKR examples for product teams

Product OKRs cluster into six focus areas. Here is one outcome-based example per area — copy the shape, swap in your own baselines.

### 1. Discovery & research

> **Objective:** Replace opinion-driven bets with evidence-driven ones.
> - **KR1:** Raise the share of roadmap items with a validated problem statement from 40% → 85%.
> - **KR2:** Achieve ≥8% click-through on the fake-door test for the next major bet (kill it below that).
> - **KR3:** Cut the average idea→validated-or-killed cycle from 6 weeks to 3.

Note KR3 is an outcome (decision speed), not "run 30 interviews" (an output). The number of interviews is how you *get there*, not the result.

### 2. Activation & onboarding

> **Objective:** Get new users to first value before they lose interest.
> - **KR1:** Increase Day-1 [activation](/glossary/activation) rate from 32% → 50%.
> - **KR2:** Reduce median [time-to-first-value](/glossary/time-to-value) from 9 minutes to under 4.
> - **KR3:** Cut onboarding-stage support tickets per 1,000 signups from 60 to 25.

### 3. Engagement

> **Objective:** Make the product a daily habit, not a monthly visit.
> - **KR1:** Lift the [DAU/MAU](/glossary/dau-mau) ratio from 0.22 → 0.30.
> - **KR2:** Increase 4-week adoption of the core workflow from 41% → 60%.

### 4. Retention

> **Objective:** Keep the users we worked hard to activate.
> - **KR1:** Improve Week-8 [retention](/glossary/retention) of the Jan–Mar cohort from 28% → 38%.
> - **KR2:** Reduce voluntary monthly [churn](/glossary/churn) from 4.1% → 2.8%.

### 5. Growth & acquisition

> **Objective:** Turn the product itself into the growth channel.
> - **KR1:** Raise the [viral coefficient](/glossary/viral-coefficient) (k-factor) from 0.35 → 0.6.
> - **KR2:** Increase the share of new signups from in-product referral from 12% → 25%.

### 6. Quality & reliability (as a fix-it OKR)

> **Objective:** Stop reliability from capping growth.
> - **KR1:** Cut p95 load time on the core flow from 3.1s → 1.5s.
> - **KR2:** Raise the crash-free session rate from 99.2% → 99.8%.

Quality usually lives as a [KPI](/glossary/kpi) — a permanent floor — but when a reliability problem is actively *capping* the business, promoting it to an OKR for one quarter is correct. (For why most reliability metrics shouldn't be OKRs, see [OKRs vs KPIs](/academy/okrs-vs-kpis-difference).)

## Worked example: Duolingo's stated 2026 priority as OKRs

Duolingo is a useful real case because its leadership is unusually public about what it's optimizing. On its **Q1 2026 earnings call**, management framed the year around a deliberate shift toward **engagement and teaching quality over aggressive monetization**, while reporting **daily active users up 21% year over year** (with guidance for roughly 20% DAU growth through 2026), **revenue of $292 million**, and **adjusted EBITDA of about $83 million (~29% margin)**. Crucially, the call highlighted that the **DAU/MAU ratio keeps rising**, which is the engagement signal a "habit, not a visit" Objective targets.

Duolingo hasn't published its internal OKRs — but its *stated public priorities* translate cleanly into the OKR shape, and that translation is the point:

| Stated priority (real, Q1 2026 call) | Translated into an OKR Key Result | Output trap to avoid |
|---|---|---|
| Engagement & habit over monetization | Lift DAU/MAU ratio by 2 points this quarter | "Ship the new streak-freeze feature" |
| Teaching quality / learning outcomes | Raise measured lesson-completion-per-DAU by 8% | "Launch 3 new AI-tutored lesson types" |
| Sustain ~20% DAU growth | Hold quarter-over-quarter DAU growth ≥ 5% in Asia | "Localize the app for 4 new markets" |

The left column is real and [cited below](#sources). The middle column is illustrative — it shows how a public priority becomes a *missable, quantified* commitment. The right column is what those KRs would look like if a product team let the roadmap write the OKRs: each output could ship in full while the engagement number went nowhere. Run every middle-column KR through [the Output Smell Test](#the-output-smell-test) and they pass; run the right column through it and all three flag on question 2.

## When NOT to use OKRs for a product team

- **Pre-product-market-fit.** When you don't yet know the right metric, OKRs create false precision. Defer formal OKRs until you have a stable [North Star Metric](/glossary/north-star-metric). (See [product-market-fit examples](/academy/product-market-fit-examples).)
- **For pure prioritization within a quarter.** OKRs set direction; they don't rank a backlog. Use [RICE](/academy/rice-prioritization-framework) to order the work that *serves* the OKR.
- **For permanent health metrics.** Uptime, gross margin, and NPS-floor are KPIs, not quarterly bets. Putting them in OKRs wastes a slot — the [Quarter-End Test](/academy/okrs-vs-kpis-difference#the-quarter-end-test-a-60-second-okr-vs-kpi-diagnostic) catches these.

## Common product-OKR mistakes

| Mistake | Why it happens | Fix |
|---|---|---|
| Key Results are shipped features | The team lives next to the roadmap | Run the Output Smell Test; rewrite each KR as the metric the feature moves |
| Too many Objectives | Everything feels important | Cap at 1–3 Objectives; a single sharp Objective beats three diffuse ones |
| Sandbagged targets | Comp is tied to OKR score | Decouple pay from OKRs; aim for 70%-achievable stretch |
| KRs nobody owns | OKRs set top-down, dropped on teams | Each KR has a named owner who helped set the target |
| "Maintain X" Key Results | Confusing state-maintenance with change | Move guardrails to KPIs; OKRs are for *change* only |

## Related

- [OKRs vs KPIs: 7 key differences](/academy/okrs-vs-kpis-difference) — when a metric belongs in an OKR vs a dashboard
- [OKR examples from Google's early years](/examples/okr-google-classic-objective) — the 20M→50M→111M Chrome OKR, the canonical stretch shape
- [OKR framework](/frameworks/okr) — full catalog entry with structure and history
- [OKRs (glossary)](/glossary/okrs) · [North Star Metric](/glossary/north-star-metric) · [Activation](/glossary/activation)
- [RICE prioritization](/academy/rice-prioritization-framework) — how to order the work that serves each Objective
- [OKR vs SMART Goals](/compare/okr-vs-smart-goals) — when to use a stretch OKR vs a must-hit SMART goal
- [OKR vs MBO](/compare/okr-vs-mbo) — how OKRs evolved from Management by Objectives, and when the older model still wins

Product OKRs work best when you write them down, share them publicly, and review them weekly. [Open the canvas →](/sign-in) to draft your quarter, or run them on your phone with [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580).

## Sources

- [The Motley Fool — "Duolingo (DUOL) Q1 2026 Earnings Transcript"](https://www.fool.com/earnings/call-transcripts/2026/05/04/duolingo-duol-q1-2026-earnings-transcript/)
- [TIKR — "Duolingo Q1 2026 Earnings: DAUs Hit 21% Growth, EBITDA Margin Reaches 29%"](https://www.tikr.com/blog/duolingo-q1-2026-earnings-daus-hit-21-growth-ebitda-margin-reaches-29)
- [John Doerr — *Measure What Matters* (What Matters)](https://www.whatmatters.com/) — OKR origin and the output-vs-outcome principle
- [Marty Cagan / SVPG — "Outcomes Over Output"](https://www.svpg.com/outcomes-over-output/) — the product-management framing of why Key Results should be outcomes

---

### OKRs vs KPIs: 7 Key Differences with Examples (2026)
URL: https://frameworklist.com/academy/okrs-vs-kpis-difference
> OKRs set ambitious quarterly direction; KPIs track ongoing health. 7 concrete differences with worked examples — and the compensation rule most teams get wrong.

**OKRs and KPIs answer different questions.** OKRs ask *"what change are we trying to create this quarter?"*. KPIs ask *"is the business healthy?"*. Teams that blur the two end up either inflating routine metrics into "goals" or burning quarterly ambition on whatever happens to be measurable — and both failure modes are common.

The shortest version of the difference: **OKRs are about change; KPIs are about state**. An OKR has a beginning and an end; a KPI is monitored indefinitely. The same metric can appear in both, but it plays a different role.

## OKR in one paragraph

An **[OKR](/glossary/okrs)** (Objective and Key Results) is a quarterly or annual goal statement made of two parts: an Objective (one ambitious, qualitative sentence describing the change you want) and 3–5 Key Results (specific, measurable outcomes that, if achieved, mean the Objective is done). The format was developed by Andy Grove at Intel in the 1970s, then transplanted to Google by John Doerr in 1999. The structure is meant to force the team to commit to *outcomes*, not activities — "ship the redesign" is an activity; "increase weekly active accounts to 50,000" is a Key Result.

## KPI in one paragraph

A **[KPI](/glossary/kpi)** (Key Performance Indicator) is an ongoing metric that signals the health of a business function. Revenue, gross margin, churn rate, [NPS](/glossary/nps), on-time delivery, customer support response time. KPIs are reviewed continuously (weekly, monthly) and have target ranges rather than target end-states. A KPI rarely belongs to a quarter — it belongs to the operating model.

## The crucial difference

| | OKR | KPI |
|---|---|---|
| Time horizon | Quarter or year | Ongoing |
| What it measures | A *change* you're trying to create | A *state* you're trying to maintain |
| Ambition | Stretch (60–70% achievement = success) | Operational (you want to hit it) |
| Owned by | A team or person committing to a goal | The function responsible for the metric |
| Lifecycle | Set, pursue, retire | Monitor indefinitely |

The same metric — say, "monthly active users" — can be a KPI (we monitor it every week to ensure the product is healthy) **and** a Key Result for a quarter (we're committing to grow it by 20% this Q3). The metric is the same; the *context* and *commitment* are different.

## The two confusion patterns

**Pattern 1: OKRs that are actually KPIs.** A team sets an OKR like "achieve 99.5% uptime this quarter." Uptime is an operational standard the SRE team should hold *every* quarter. It's a KPI. Setting it as an OKR means the team has wasted one of its 3–5 quarterly commitments on something that should be a permanent floor. Real OKRs would commit to specific changes — "reduce mean time to recovery from 25 min to 10 min" or "migrate the 3 highest-traffic services off legacy infra."

**Pattern 2: KPIs that masquerade as OKRs.** Often you'll see a quarter's OKRs that include "maintain NPS above 50" or "keep churn under 3%." Same problem in reverse — a *state-maintenance* metric is being treated as the team's quarterly bet. The team will hit it (because it's already true), call the quarter a success, and have changed nothing.

<Callout title="The diagnostic question">
At the end of the quarter, will the world be measurably different because we did this? If yes, it's an OKR. If no — it's a KPI, and shouldn't take up an OKR slot.
</Callout>

## The Quarter-End Test: a 60-second OKR vs KPI diagnostic

The single-question test above catches the most common confusion, but it's hard to apply when the candidate metric *could* go either way. Run the metric through the four questions below in order. The first **No** classifies it.

| # | Question | If No → |
|---|---|---|
| 1 | Will this metric have a *different value* at the end of the quarter than it does today? | It's a **guardrail KPI**, not an OKR. State-maintenance metrics never belong on the OKR list. |
| 2 | Would hitting the proposed target *change behavior* somewhere in the company — someone has to do new work, ship something new, or stop something old? | It's a **vanity KPI**. If the number moves without anyone doing anything, you're reporting weather, not setting a goal. |
| 3 | Is the target *uncomfortable* — a stretch the team can reasonably miss and still call the quarter a success at 70%? | It's an **operational target**. By Andy Grove's design, anything you're confident you'll hit isn't OKR-shaped. |
| 4 | Can a third party verify whether it was achieved without you explaining context? | It's a **soft commitment**. Convert it to a measurable Key Result before it goes on the list. |

**Four Yes answers = real OKR.** Any single No demotes it. Most teams running this test on their proposed quarterly OKRs find that 30–50% of the list is actually KPIs in disguise — usually because someone wanted the visibility of an OKR for work that should just be monitored on a dashboard.

**The compensation corollary**: if a metric passes the four-question test (i.e., it's a true OKR), tying compensation to it sabotages the ambition mechanism. Pay against the KPIs that survived question 3, not the OKRs that didn't.

## A worked example: Google Chrome's OKR vs its KPIs

The cleanest real illustration is Google Chrome. When Sundar Pichai's team launched the browser in 2008, its **OKR** was a stretch: the Objective was to build the best browser, with a Key Result defined as **7-day active users**. John Doerr documents the progression in *[Measure What Matters](https://www.whatmatters.com/)*: a target of **20 million** users for 2008 (missed), reset to **50 million** for 2009 (missed again), then **111 million** for 2010 — finally hit. That is the classic OKR shape: ambitious, time-boxed, genuinely missable, and retired once achieved.

Chrome's **KPIs** were entirely different metrics: **page-load speed** and **crash-free rate**. Those were never quarterly bets — they were continuously monitored health metrics that had to stay good *every* week, the operating floor the whole "Chrome is fast" positioning depended on. Same product, two metric types: the user-count goal *changed* and was retired; the speed and stability metrics held a *state* indefinitely.

| Metric | Type | Why |
|---|---|---|
| 7-day active users (20M → 50M → 111M) | **OKR Key Result** | A change the team committed to over a set period; stretch; retired once hit |
| Page-load speed | **KPI** | Monitored continuously; a permanent floor, never "done" |
| Crash-free rate | **KPI** | Operational health the product can't regress on in any quarter |

Run each row through [the Quarter-End Test](#the-quarter-end-test-a-60-second-okr-vs-kpi-diagnostic) above and they classify cleanly — the user-count target answers "Yes" to all four questions; speed and stability fail question 1 (you want them *unchanged-or-better*, not different).

## How OKRs and KPIs fit together

In a well-run system, they form layers:

1. **KPIs** establish the operating floor. The dashboard you check weekly.
2. **OKRs** allocate the team's discretionary energy on top of that floor. The 2–3 things that, this quarter, you're going to *change*.
3. When a KPI drops below acceptable, an OKR is set to fix it. ("Reduce customer support response time from 18h to 6h.")
4. When a new initiative succeeds, the new behavior often becomes a KPI for the next quarter. (Acquisition rate is now a metric you monitor, not a bet you're making.)

The flow is: KPI → triggers → OKR → if successful → new KPI.

## When neither is the right tool

- For **personal task triage**, OKRs and KPIs are both too heavyweight. Use the [Eisenhower Matrix](/academy/eisenhower-matrix-urgent-vs-important).
- For **strategic positioning**, you want a [SWOT](/academy/what-is-a-swot-analysis) or [Porter's Five Forces](/frameworks/fiveforces) — OKRs presume the strategy is set; they don't help you find one.
- For **early-stage startups** where the right metric isn't yet known, OKRs can create false precision. Defer formal OKRs until the team has a stable [North Star Metric](/frameworks/northstar).

> **Want your OKRs somewhere other than a spreadsheet?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=okr-academy) keeps objectives, key results, and the metrics that back them in one worksheet. Free to start.

## Related frameworks

- [OKR examples for product teams](/academy/okr-examples-for-product-teams) — six outcome-based examples across discovery, activation, retention, and growth, with the Output Smell Test
- [OKR](/frameworks/okr) — full catalog entry with structure and examples
- [KPI Tree](/frameworks/kpi) — how to decompose a North Star into operational KPIs
- [SMART Goals](/frameworks/smart) — the older, simpler goal-setting cousin
- [OKR vs SMART Goals](/compare/okr-vs-smart-goals) — stretch-by-design vs achievable-by-design, and the Stretch-vs-Commit Test for choosing
- [OKR vs MBO](/compare/okr-vs-mbo) — the framework OKRs evolved from, and the Transparency-and-Stretch Test for when MBO still fits
- [Balanced Scorecard](/frameworks/balancedscorecard) — the institutional KPI framework that OKRs partially replaced

OKRs work best when you write them down, share them publicly, and review them weekly. [Open the canvas →](/sign-in) to draft your first one.

---

### Pareto Analysis: the 80/20 principle, applied
URL: https://frameworklist.com/academy/pareto-analysis-80-20-principle
> Roughly 80% of outcomes come from 20% of causes. Pareto Analysis is the discipline of finding which 20% — and then doing something different with it.

**Pareto Analysis** is the practice of separating the small fraction of inputs that produce the large fraction of outputs, then reallocating attention accordingly. The underlying observation — *roughly 80% of effects come from 20% of causes* — was named by the management consultant Joseph Juran after Italian economist Vilfredo Pareto, who in 1896 noticed that 80% of Italy's land was owned by 20% of the population.

The exact 80/20 split is folklore; the real claim is that in most real-world systems, **the distribution of inputs to outputs is not flat**. A few inputs disproportionately matter. The analysis is the work of finding those few.

## The core insight

If you list 100 customers by revenue, the top 20 will often produce 80% of the total. If you list 100 bugs by user impact, a handful will dominate. If you list 100 features by usage, a small subset will get most of the use. The shape recurs across customers, bugs, features, sales reps, blog posts, time spent — almost any input-output relationship in a real business.

The temptation, given this observation, is to **drop the bottom 80%**. Pareto Analysis is more subtle than that. The right response depends on whether the bottom 80% is *worth keeping*, *should be improved*, or *should be cut*. The analysis tells you the distribution; the decision is yours.

## When to use Pareto Analysis

- **Diagnosing where revenue / cost / effort / attention is actually going** before making allocation decisions
- **Triaging a long list** of bugs, support tickets, feature requests, or customer accounts
- **Auditing time use** at the personal level (which 20% of activities produce 80% of weekly progress?)
- **Pre-cut analysis** before reducing scope: which 20% of features will keep 80% of users happy?

Skip Pareto when the distribution is genuinely flat — e.g., compliance items where each one must be done regardless of relative impact. The principle is descriptive, not always applicable.

## How to actually run one in 30 minutes

1. **Pick one outcome.** Revenue. Time. Bug count. Customer support hours. Pick a single number you're trying to understand.
2. **List the inputs that contribute to it.** Customers (for revenue), tasks (for time), tickets (for support hours), features (for usage). Get the full list — incompleteness corrupts the rest.
3. **Quantify the contribution of each.** This is the step people skip. Without numbers, you'll over-weight whichever input is *vivid* (the noisy customer) rather than whichever is *large* (the silent profitable one).
4. **Sort descending and compute cumulative percentage.** Top input, top 2, top 5, top 10 ... at what point have you accounted for 80% of the outcome? That's your "20%" cohort (the actual percentage will vary — sometimes 5%, sometimes 35%).
5. **Look at the 20% explicitly.** What do they share? What pattern produces them? Why are they outliers? Pattern-finding here is where the strategic insight lives.
6. **Decide differently for the 20% than for the 80%.** Double down on the 20%? Replicate what produced them? Cut the 80% to free up attention? The whole point of the analysis is that the same allocation rule probably should not apply to both groups.

## Worked example: support ticket triage

A team gets 300 support tickets a month. They feel overwhelmed and want to hire.

Pareto run:
- Categorize all 300 tickets by underlying root cause (~15 unique causes)
- Sort by frequency
- Top finding: **4 root causes account for 220 of the 300 tickets (73%)**

Decision: don't hire another support rep — fix 4 product issues. Estimated outcome: ticket volume drops to ~80/month, current team is fine. The hiring decision and the product roadmap are now linked, not separate.

Without the analysis, the team would have hired and grown the support cost forever.

## What Pareto Analysis is good at

- **Converting "we're overwhelmed" into a tractable list of the few things that matter.** The output is usually a small number you can act on.
- **Pre-empting the "treat everything equally" failure mode.** Most organizations default to treating all customers / bugs / features the same. Pareto reveals when that's destroying value.
- **Compounding over time.** The 20% identified this quarter is usually the 20% next quarter, with drift. Once you know who they are, you can structurally re-org around them (dedicated account managers for top customers, dedicated bug-bash time for top failure modes).

## What Pareto Analysis is bad at

- **Quality-of-output decisions.** The 80/20 logic doesn't tell you whether a feature is *good*, only whether it's *used*. Use [Kano](/frameworks/kano) for satisfaction analysis.
- **Truly equal distributions.** Some inputs really do contribute roughly equally — Pareto on these produces a flat curve and no useful insight.
- **One-time decisions.** Pareto rewards recurring decisions where the distribution stays roughly stable. For a unique decision, it's overkill.
- **Politically loaded cuts.** Knowing the bottom 80% is low-impact doesn't tell you whether you can cut it. Customers in the bottom 80% may still represent strategic relationships, regulatory commitments, or future expansion.

## The 80/20 trap

The biggest abuse: applying 80/20 as a slogan rather than an analysis. "We should focus on the 20%" gets said in meetings; few people then go list the actual inputs and quantify them. The discipline is the math, not the phrase.

The second abuse: using 80/20 to justify a cut you'd already decided to make. If the analysis confirms a pre-existing conclusion, re-check whether the input list was complete and the quantification honest.

## Pareto vs RICE vs MoSCoW: when 80/20 wins

The most common prioritization mistake isn't picking a bad framework — it's picking *any* framework before checking whether your input set fits the framework's assumptions. Pareto, RICE, and MoSCoW are the three workhorse prioritization tools, and each fits a specific input shape. Mixing them up wastes time and produces worse rankings than no framework at all.

The decision matrix:

| Dimension | **Pareto** (80/20) | **RICE** | **MoSCoW** |
|---|---|---|---|
| Input set size | Large (50+ items) | Medium (10-50 items) | Small (5-20 items) |
| What you measure | One dominant outcome dimension | Four roughly-equal dimensions (Reach × Impact × Confidence ÷ Effort) | Stakeholder-driven categorical buckets (Must / Should / Could / Won't) |
| Output shape | Heavy-tailed distribution → "the 20% that matters" | Numerical ranking | Four buckets |
| Decision the team needs | Allocate attention differently between head and tail | Sequence specific items from highest to lowest | Reach political alignment on what's in scope |
| Time to run | 30-60 min once you have the data | 60-90 min per scoring session | 60-90 min stakeholder workshop |
| Wins when | One dimension genuinely dominates (revenue, defects, support volume) | All four RICE dimensions are real and meaningful | Stakeholder politics matter more than the math |
| Fails when | Distribution is flat (no real heavy tail) | Items aren't comparable on the four dimensions; teams fake Confidence | Stakeholders can't actually agree; "Won't" gets used to dump work |

The decision rule:

- **Use Pareto** when your input set is large (50+ items), one outcome dimension dominates the analysis, and the question is "where should the team's attention go?" — not "in what sequence should we execute?"
- **Use RICE** when your input set is medium (10-50 items), the four dimensions (Reach, Impact, Confidence, Effort) all genuinely vary across items, and you need a *sequence* not just a head/tail split. Apply the [RICE Confidence Discount](/academy/rice-prioritization-framework) to keep the C input honest.
- **Use MoSCoW** when your input set is small (5-20 items), the conversation is fundamentally political (stakeholders need to be heard, not just optimized), and the output is a scope agreement rather than a ranked list.

A worked example — **same 200-item product backlog, three different outcomes**:

| Framework applied | Output | Time | When this is the right answer |
|---|---|---|---|
| **Pareto** on the 200 items by quarterly revenue contribution per feature | "12 features (6%) produce 78% of revenue. Build the next iteration of those; deprioritize new work on the other 188." | 45 min | When the question is "where to focus", not "what order to build" |
| **RICE** on the same 200 items | 200-item ranked list. Top 8 items have RICE > 50; next 30 have RICE 20-50; the rest are < 20 and won't be built this year. | 6-8 hours across multiple sessions | When the team needs an actual build sequence and the four dimensions are meaningful |
| **MoSCoW** on the same 200 items | 18 Must, 35 Should, 60 Could, 87 Won't. Stakeholders sign off on Must + Should as scope. | 3-hour cross-functional workshop | When stakeholder alignment matters more than analytical precision; pre-launch scope-setting |

All three outputs are *correct*. They're answering different questions. The mistake is running RICE on a 200-item set (impossibly heavy), or Pareto on 8 items (no heavy tail), or MoSCoW with no stakeholders present (just relabeled gut feel).

**The chained workflow** that mature product teams converge on:

1. **Pareto** on the full corpus (200 items) → identify the 20% that matters
2. **RICE** on the 20% (~40 items) → sequence them
3. **MoSCoW** on the top RICE-ranked 20 → get stakeholder sign-off for the actual launch scope

This is the synthesis only Framework's library, with all three pages cross-linked, can publish. Each framework fits where it fits; the value is the sequencing, not picking a single winner.

For the deeper dives, see [RICE prioritization framework](/academy/rice-prioritization-framework), [RICE vs MoSCoW](/compare/rice-vs-moscow), and the [MoSCoW framework catalog](/frameworks/moscow).

> **Want to find your vital few on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=pareto-academy) ranks causes by contribution and draws the cumulative line where 80% lands. Free to start.

## Related frameworks

- [Eisenhower Matrix](/academy/eisenhower-matrix-urgent-vs-important) — adjacent triage tool for personal task lists; Pareto for inputs-to-outputs
- [RICE prioritization](/academy/rice-prioritization-framework) — explicit scoring approach when you have many comparable items
- [MoSCoW](/frameworks/moscow) — coarser bucket-based alternative for requirement classification
- [First Principles](/academy/first-principles-thinking-with-examples) — when 80/20 reveals a surprising 20%, first-principles asks *why* that distribution exists

Open the [Pareto catalog entry →](/frameworks/pareto) for the worksheet template and worked examples.

---

### Porter's Five Forces: a beginner's guide
URL: https://frameworklist.com/academy/porters-five-forces-beginners-guide
> Five forces decide whether a market is worth competing in. Read them right and you avoid markets that look attractive but aren't. Here's how to actually run the analysis.

**Porter's Five Forces** is a structured way to evaluate the long-term profit potential of any market by examining five competitive pressures: rivalry among existing competitors, threat of new entrants, threat of substitutes, bargaining power of suppliers, and bargaining power of buyers. The premise is that a market's long-run profitability is determined less by who plays well within it and more by the *structure* of the market itself.

The framework was introduced by Michael Porter in *Competitive Strategy* (1980) and has since become the default analytical lens for strategy MBA programs, M&A diligence, and corporate planning. Its persistence is not nostalgia — the underlying claim, that industry structure constrains achievable returns, has held up across four decades of empirical study.

## The five forces

- **Rivalry among existing competitors.** How fiercely do current players compete? High rivalry compresses margins. Signals: many roughly-equal competitors, slow industry growth, high fixed costs, low switching costs, undifferentiated products.
- **Threat of new entrants.** How easy is it for new players to show up? Easy entry caps your pricing power. Signals: low capital requirements, no patents or network effects, undeveloped distribution.
- **Threat of substitutes.** Could buyers solve their problem a different way? A substitute is not a competitor with the same offering — it's a different offering that solves the same job. (For cinema: streaming, books, restaurants, sleep.)
- **Bargaining power of suppliers.** Can your inputs squeeze you? High supplier power = compressed margins. Signals: few suppliers, switching cost to alternate suppliers, supplier brand needed for your credibility.
- **Bargaining power of buyers.** Can your customers squeeze you? High buyer power = compressed margins. Signals: concentrated buyers, undifferentiated product, low switching cost.

The *combined* strength of these five determines what return is achievable in the long run, regardless of which firm you are within the industry. Five strong forces → low returns for everyone. Five weak forces → high returns for almost anyone.

## When to use Five Forces

- Evaluating **whether to enter** a new industry or geographic market
- Deciding whether to **double down or exit** a struggling business
- **Investment due diligence** on a private company in an unfamiliar industry
- **Strategic re-set** at the start of a new CEO's tenure or after a major market shift

Skip Five Forces for tactical decisions (which feature to ship, which copy variant to test). It's a long-run, market-structure tool. Using it on weekly decisions is overkill.

## How to actually run one in 90 minutes

1. **Define the industry boundary explicitly.** "Software" is too broad; "vertical SaaS for veterinary clinics" is sharp enough. A bad boundary corrupts every subsequent answer.
2. **Score each force separately** — High / Medium / Low. Don't average; that hides the analysis. Each force gets its own slide or row.
3. **For each force, list 2–4 specific signals you observed.** "High rivalry" isn't an analysis; "high rivalry: 6 competitors at >$10M ARR, no clear leader, growth is flat at 5%/yr" is.
4. **Look for the dominant force.** Often one of the five matters far more than the others. In airlines, supplier power (oil, planes, pilots) and rivalry dominate; the other three are afterthoughts. Name the dominant force out loud.
5. **Conclude with the structural verdict.** Is this an industry where strong execution can produce attractive returns, or one where even great players struggle? Don't soften the answer.
6. **Decide what to do.** Enter? Exit? Reposition to dodge the dominant force? The framework only earns its 90 minutes if it produces a decision.

## What Five Forces is good at

- **Surfacing why a market is structurally good or bad,** independent of who's currently in it. Many talented teams have entered structurally bad markets and wondered why they couldn't make money. Five Forces would have warned them.
- **Differentiating attractive-looking markets from genuinely attractive ones.** A market with high growth but five weak forces in the wrong direction (concentrated buyers, easy entry, substitutes) will still compress to low returns.
- **Pointing at the right strategic levers.** If supplier power is the dominant problem, your strategy is upstream (vertical integration, alternative inputs). If buyer power is the problem, your strategy is downstream (differentiation, switching costs).

## What Five Forces is bad at

- **Predicting disruptive change.** The framework assumes a relatively stable industry structure. Tech-driven markets change the rules of who counts as a competitor, supplier, and buyer. Use it as a snapshot, re-run when the picture shifts.
- **Capturing non-economic dynamics** — regulation, government action, social-license-to-operate. Porter himself later added a "complementors" dimension some practitioners include as a sixth force.
- **Telling you *what to do* in a fragmented market.** Five Forces diagnoses structure; it doesn't generate positioning options. Pair with a [SWOT](/academy/what-is-a-swot-analysis) or [Blue Ocean](/glossary/blue-ocean) exercise to move from diagnosis to action.

## Worked example: vertical SaaS for veterinary clinics (sketched)

- **Rivalry: medium.** 4–5 competitors, none dominant, growing 25%/yr — competition is real but not yet a knife fight.
- **Entrants: high.** Low capital, no network effects, building a competing product takes 18 months and $3M.
- **Substitutes: medium.** Many clinics still use Excel + paper. Some use general-purpose practice-management tools.
- **Supplier power: low.** Cloud infra is commoditized.
- **Buyer power: medium-high.** Buyers are independent clinic owners — small but cost-conscious; long sales cycles.

Verdict: structurally OK but vulnerable. The dominant risk is new entrants. A winning strategy here is to build defensible network effects (e.g., a marketplace component connecting clinics with referral specialists) before competitors arrive.

For a full company example, see our worked [Porter's Five Forces on Netflix in 2026](/examples/netflix-porters-five-forces) — same model, applied to a real industry with public financial data. For a current news-pegged read, see [Nvidia at $5T: the AI chip industry through Five Forces](/blog/ai-chip-five-forces-nvidia-5-trillion).

## The Five Forces 5-Year Outlook Table

Standard Five Forces analyses produce a *snapshot* — five labels and a verdict. The 5-Year Outlook Table is a named extension that converts the snapshot into a *predictive* diagnostic by adding two columns: the direction the force is moving in, and the specific signal that would flip it within 24-36 months. It's the value-add gap most beginner guides leave open.

The scoring grid:

| Force | Current Strength (1-5) | Direction (24-36mo) | Tipping Signal — what would flip it |
|---|---|---|---|
| Rivalry | 1 (low) — 5 (knife fight) | ↑ ↓ → | The specific market event that would change the score |
| New entrants | 1 — 5 | ↑ ↓ → | What entry barrier change would shift it |
| Substitutes | 1 — 5 | ↑ ↓ → | The customer-behavior or technology shift that would matter |
| Supplier power | 1 — 5 | ↑ ↓ → | The supplier-market change that would flip the balance |
| Buyer power | 1 — 5 | ↑ ↓ → | The buyer-concentration or alternative-source shift |

Worked example — **SaaS infrastructure (cloud databases, observability, CI/CD)** in 2026:

| Force | Strength | Direction | Tipping Signal |
|---|---|---|---|
| **Rivalry** | 4 — high; multiple well-funded competitors per category | → | Mass consolidation would drop this; AI-bundled offerings from hyperscalers (AWS / Azure / GCP) are starting to do this |
| **New entrants** | 3 — moderate; open-source has lowered entry cost, but enterprise sales is a moat | ↓ | AI-generated competitor products from a $50M seed round could re-raise entry; watch for new categories appearing in 6 months that didn't exist in 2024 |
| **Substitutes** | 4 — high and rising; LLM-native tooling (Cursor, v0, Claude-as-CI) substitutes for traditional dev infra in some workflows | ↑ | The substitution wave is just starting; watch for the first SaaS infra category to lose 20%+ of its expansion revenue to LLM-native alternatives |
| **Supplier power** | 5 — very high; foundation-model providers (Anthropic, OpenAI) and GPU suppliers (Nvidia) extract a large share of value | ↑ | Watch for second-source model providers reaching production quality; Meta's Llama and open-source models reaching parity would drop this to 3 |
| **Buyer power** | 3 — moderate; enterprise buyers have alternatives but switching cost is high | ↑ | Procurement consolidation in 2026-2027 (CFOs demanding fewer vendors) is increasing buyer power |

**Dominant force**: Supplier power (5) — foundation model and GPU costs are the largest determinant of margins for AI-native SaaS in 2026.

**5-year structural verdict**: SaaS infrastructure margins are likely to compress over 2026-2028 unless companies either (a) build proprietary models that bypass foundation-model suppliers, or (b) develop network effects strong enough to retain pricing power despite supplier squeeze. The dominant strategic lever is upstream — model differentiation or vertical integration — not the typical SaaS playbook of downstream sales-and-marketing investment.

Why the table format matters: AI engines (Perplexity, ChatGPT, Gemini, Claude) cite tables verbatim and don't cite prose at the same rate. Forcing the analysis into the 4-column grid produces a citable artifact instead of a 2,000-word essay AI can't quote cleanly. It also forces the analyst to identify the *signal* that would change each verdict — without that column, the analysis can't be re-evaluated 18 months later.

For a full company-level application of this grid, see [Microsoft Porter's Five Forces Analysis 2026](/examples/microsoft-porters-five-forces-analysis-2026) and [Netflix Porter's Five Forces in 2026](/examples/netflix-porters-five-forces). For the grid applied to the business of football — supplier power, new entrants, and the Super League — see [Real Madrid Porter's Five Forces: the Super League play](/examples/real-madrid-porters-five-forces-2026).

> **Want to score the five forces for your own industry?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=five-forces-academy) walks each force with AI-assisted prompts and keeps the scorecard in one place. Free to start.

## Related frameworks

- [SWOT analysis](/academy/what-is-a-swot-analysis) — pair with Five Forces; SWOT covers internal capability, Five Forces covers external structure
- [PESTLE](/frameworks/pestel) — adds political, economic, social, technological, legal, environmental forces for macro context. See [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) for exactly which to run when, and how to chain them outside-in.
- [Value Chain](/frameworks/valuechain) — Porter's other major framework; decomposes a single firm into activities to find advantage sources
- [Blue Ocean Strategy](/frameworks/blueocean) — counterpoint: instead of competing in a tough five-forces industry, find a new uncontested market

## Worked examples

- [Tesla Porter's Five Forces Analysis 2026](/examples/tesla-porters-five-forces-2026) — run against the July 22, 2026 Q2 earnings, where all five forces moved against the company at once
- [Netflix Porter's Five Forces](/examples/netflix-porters-five-forces) — a case where substitutes, not rivalry, are the binding force
- [Microsoft Porter's Five Forces Analysis 2026](/examples/microsoft-porters-five-forces-analysis-2026) — enterprise software structure
- [Nvidia at $5 trillion: moat or mirage](/blog/ai-chip-five-forces-nvidia-5-trillion) — the AI chip industry

Want the catalog entry with examples? [Read the full Porter's Five Forces entry →](/frameworks/fiveforces).

---

### Product-Market Fit Examples (2026): Wins, Fails, Scored
URL: https://frameworklist.com/academy/product-market-fit-examples
> Product-market fit examples scored against one repeatable test — Cursor, Superhuman, Slack (passed) vs Quibi and Humane's AI Pin (failed). Run the same test on your own product.

**Product-market fit examples are usually taught the wrong way.** Almost every list you'll find walks through the same six winners — Dropbox, Airbnb, Uber, Netflix, the iPhone, Slack — and tells you a story about each. The problem with a story is that you can't run it on your own product. You finish reading and you still don't know whether *you* have product-market fit.

So this page does it differently. We take real cases — recent and classic, **wins and failures** — and score every one against the same three-signal test. The examples become useful only when you can see *why* each passed or failed on a repeatable yardstick, because that yardstick is the thing you can actually apply to yourself.

## The test behind every example: the PMF Trifecta

[Product-market fit](/glossary/product-market-fit) isn't a vibe. It shows up as three measurable signals that must all point the same way — what our glossary calls the **PMF Trifecta**:

1. **The Sean Ellis test** — survey your users and ask how they'd feel if they could no longer use the product. **40%+ answering "very disappointed"** is the working threshold. Below it, you're still searching.
2. **Retention-curve flattening** — plot cohort retention over time. Without fit, the curve decays toward zero. With fit, it *flattens* — a core of users keeps coming back indefinitely.
3. **Organic pull** — growth that happens *without* paid acceleration. Word-of-mouth, inbound demand, waitlists. If you stop spending and growth stops too, that's a paid funnel, not fit.

Any one signal alone is a false positive. Hype creates organic-looking buzz with no retention. A clever onboarding flow can fake early retention with no organic pull. **Fit is all three at once.** That's the lens for everything below.

## Product-market fit examples, scored

| Case (year) | Sean Ellis ≥40% | Retention flattens | Organic pull | Verdict |
|---|---|---|---|---|
| **Cursor / Anysphere** (2024–26) | — (not public) | ✅ 70% of Fortune 1000, heavy seat expansion | ✅ $0→$100M ARR with no marketing | **Textbook PMF** |
| **Superhuman** (2019) | ✅ **58%** | ✅ | ✅ invite-list demand | **Passes** |
| **Slack** (2014) | — | ✅ | ✅ ~8k→500k DAU in a year | **Passes** |
| **Quibi** (2020) | ❌ | ❌ mass churn after free trials | ❌ no word-of-mouth | **False PMF** |
| **Humane AI Pin** (2024) | ❌ | ❌ returns reportedly outpaced sales | ❌ scathing reviews | **False PMF** |

The pattern is the point: the winners pass on the signals you can't buy (retention, organic pull); the failures had everything money *can* buy (funding, talent, launch volume) and still missed all three.

## The wins

**Cursor (Anysphere) — the clearest recent example.** The AI code editor hit **$100M ARR by January 2025**, the fastest any SaaS company has reached that milestone, reportedly with no marketing spend ([TechCrunch](https://techcrunch.com/2025/06/05/cursors-anysphere-nabs-9-9b-valuation-soars-past-500m-arr/)). It then went **0 to $2B ARR in about three years** — the fastest B2B scaling on record — with more than 1M daily users and roughly 70% of the Fortune 1000 on the platform ([The Next Web](https://thenextweb.com/news/cursor-anysphere-2-billion-funding-50-billion-valuation-ai-coding)). When demand pulls that hard without being pushed, all three Trifecta signals are firing at once.

**Superhuman — the textbook measurement case.** Superhuman is famous precisely because founder Rahul Vohra published the actual machinery: he ran the Sean Ellis survey, found **58%** of users would be "very disappointed" without the product (above the 40% bar), then systematically grew that number before scaling ([First Round Review](https://review.firstround.com/how-superhuman-built-an-engine-to-find-product-market-fit/)). It's the rare example where you can see the score, not just the story.

**Slack — organic pull at scale.** Slack grew from roughly 8,000 to 500,000 daily active users inside its first year, almost entirely through word-of-mouth inside teams that then pulled in other teams. That viral, team-to-team pull is organic-growth fit in its purest form.

## The failures (where the lesson actually lives)

**Quibi — funding is not fit.** Quibi raised about **$1.75 billion** and launched a mobile-only short-form streaming service in April 2020 at $5–8/month. It shut down roughly **six months later** ([WSJ](https://www.wsj.com/articles/quibi-is-shutting-down-barely-six-months-after-going-live-11603416171)). It had capital and a star-studded team — and zero of the three signals: no one was "very disappointed" to lose it, free-trial users churned en masse, and there was no organic pull in a world of free video.

**Humane's AI Pin — hype is not fit.** Humane raised **$230 million** (backers included Sam Altman and Marc Benioff) and shipped the AI Pin in April 2024 to scathing reviews — one prominent reviewer called it among the worst products he'd ever tested. By February 2025, HP bought the company's assets for **$116 million** and the device was discontinued ([TechCrunch](https://techcrunch.com/2025/02/18/humanes-ai-pin-is-dead-as-hp-buys-startups-assets-for-116m/); [Fortune](https://fortune.com/2025/02/19/hp-humane-deal-ai-pin-shutting-down/)). Its 2024 cousin, the Rabbit R1, drew near-identical "underbaked" reviews on the same AI-gadget hype wave. Pre-orders and press are not retention.

## Why the usual examples mislead you

The standard listicle has a survivorship-bias problem: it only shows winners, so you absorb *what fit looks like in hindsight* but never learn *how to tell fit from its imposters in the moment.* Quibi and Humane both looked, at launch, like they had momentum — capital, coverage, a launch spike. The Trifecta is what separates a launch spike from fit: a spike doesn't flatten the retention curve and doesn't produce organic pull. Pairing the wins with the fails on the same scorecard is the only way the pattern becomes legible.

## Common mistakes reading PMF examples

| Mistake | Why it happens | The fix |
|---|---|---|
| Treating big funding as proof of fit | Rounds make headlines; retention doesn't | Score retention + organic pull, ignore the raise (Quibi: $1.75B, dead in 6 months) |
| Mistaking launch buzz for fit | Press and pre-orders feel like demand | Wait for the *second* cohort's retention, not the launch spike (Humane) |
| Copying a winner's tactic, not its signal | "Slack grew by word-of-mouth, so we'll do referrals" | Word-of-mouth was the *symptom* of fit, not the cause — fix fit first |
| Reading only success stories | Listicles are survivorship-biased | Always score at least one failure against the same test |

## Run the test on your own product

You don't need a famous example — you need the three readings on your own users:

1. **Run the Sean Ellis survey** — one question, "how would you feel if you could no longer use [product]?" Target 40%+ "very disappointed."
2. **Plot cohort retention** — does it flatten, or decay to zero? A flat tail is the single hardest signal to fake.
3. **Cut paid acquisition for a week** — does growth continue? That's your organic-pull reading.

If you're still searching for fit, the upstream work is usually demand definition — see [Jobs-to-be-Done](/academy/jobs-to-be-done-framework-explained) for nailing the job your product is hired to do, and the [product-market fit glossary entry](/glossary/product-market-fit) for the full PMF Trifecta definition. When the test comes back marginal, the harder call is whether to change course at all — walk the [pivot-or-persevere decision chain](/decisions/pivot-or-persevere), which starts with this same PMF read before touching the product. To keep the right metrics in view once you're scaling, the [OKRs vs KPIs](/academy/okrs-vs-kpis-difference) split keeps retention as a health KPI rather than a vanity goal.

> Want to pressure-test your own product against frameworks like this? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships with 100+ models and AI assistance to work through each one.

## Related

- [Product-market fit (glossary)](/glossary/product-market-fit) — the PMF Trifecta definition in full
- [Jobs-to-be-Done framework explained](/academy/jobs-to-be-done-framework-explained) — define the demand before you test for fit
- [OKRs vs KPIs](/academy/okrs-vs-kpis-difference) — keep retention as a KPI, not a vanity OKR
- [Browse all frameworks](/frameworks) — the full library

---

### Reverse brainstorming: solve problems backwards
URL: https://frameworklist.com/academy/reverse-brainstorming-solve-problems-backwards
> Stuck on a problem? Instead of asking how to solve it, ask how to cause it. Reverse brainstorming surfaces the obstacles your regular thinking refuses to see.

**Reverse brainstorming** is a technique for solving stuck problems by inverting the question: instead of asking *how do we achieve X*, ask *how could we guarantee the opposite of X*. The list of "ways to fail" you produce tends to surface obstacles, blind spots, and assumed constraints that a straightforward "how to succeed" brainstorm would have missed.

The technique is rooted in the older Charlie Munger maxim of **inversion**: "Invert, always invert. Many hard problems are best solved when they are addressed backward." Munger borrowed the discipline from the 19th-century mathematician Carl Gustav Jacob Jacobi, who famously said that for hard problems, *man muss immer umkehren* — one must always invert.

## Why backwards thinking works

Forward brainstorming ("how do we improve retention?") activates everyone's existing assumptions about what's possible. The group converges on familiar ideas because the familiar shapes the search space.

Backwards brainstorming ("how could we *destroy* retention?") suspends the familiar. The mind has fewer rehearsed answers to the inverted question, so it generates fresh ones. And inverted answers point at causes the forward question would have left invisible — the small daily frictions, the silently-accumulating dissatisfactions, the things we already know but haven't been willing to name.

The output of a reverse brainstorm is rarely "do the opposite of these failure ideas". It's "the failure ideas reveal what was actually broken that we kept not seeing".

## When to use it

- The team has been **stuck on the same problem for weeks** and is recycling the same proposed solutions
- A project has **clearly visible symptoms but unclear root causes** (revenue is flat, users are churning, morale is dropping — but everyone has a different theory)
- You're about to **double down on a strategy** and want one last filter to catch what could undermine it
- A **pre-launch sanity check** when a [premortem](/academy/how-to-run-a-premortem) feels too heavy

Skip reverse brainstorming for problems with clear root causes (where 5 Whys works), or for routine optimization (where the answer is in the data).

## How to actually run one in 45 minutes

1. **State the goal clearly** (5 min). "Increase signup conversion from 8% to 12% by end of Q3." Get the team to read the goal aloud, then write it on the wall in plain view.
2. **Invert the goal** (2 min). "How could we *guarantee* signup conversion drops to 4%?" or "What would absolutely kill conversion?" Write the inverted goal in bigger letters than the original. Resist softening — the inversion only works if it's bracing.
3. **Silent generation: 10 minutes** of individual writing. Each person lists every way they can think of to cause the failure. No discussion, no judging, no sorting. Quantity over quality.
4. **Round-robin read-out** (15 min). Each person reads one item from their list. Capture each on a sticky note. Continue until exhausted. Encourage absurd answers — they often unblock obvious ones the group was too polite to say.
5. **Cluster and translate** (10 min). Group the failure-causes by underlying theme. Each cluster becomes a candidate problem area for the *real* (forward) work.
6. **Decide what to do** (5 min). For the top 2–3 clusters, identify a concrete action that addresses the cause. The action need not be the literal inverse of the failure cause — usually it's a different intervention informed by what the failure cause revealed.

## What makes a reverse brainstorm actually work

**Permission to be uncomfortable.** The good answers to "how could we destroy this" often name things people have noticed but kept polite about. The facilitator's job is to make it socially safe to say them.

**Silent writing first.** If you go straight to open discussion, the highest-status person in the room defines the search space. Silent writing protects the divergent phase from premature convergence.

**Don't translate too early.** It's tempting to immediately map each "failure cause" to its "fix". Resist. Let the failure causes accumulate; the patterns only become visible at scale.

**Re-read the original goal at the end.** After 30 minutes of imagining failure, the team can lose sight of what success was supposed to be. Reading the original goal back grounds the closing decisions.

## A worked example

A product team's goal: "Make the new onboarding flow drive 60% activation within 7 days."

Inverted: "How could we make sure activation stays below 20%?"

The first 5 minutes of silent generation surfaced answers like:
- "Don't let the user do anything useful in their first session"
- "Send 4 transactional emails on day one"
- "Make the first action require a credit card"
- "Hide the value proposition behind a 6-step setup wizard"

By minute 20 the answers got sharper:
- "Show them what other people built before they've built anything themselves"
- "Make the empty state feel like work, not progress"
- "Force them to invite teammates before they've experienced value"

The team's actual onboarding had *three* of these patterns. The forward question ("how do we improve activation?") had been live for two months and produced incremental ideas. The inverted question, in 30 minutes, produced a redesign brief.

> **Want to run a reverse brainstorm on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=reverse-brainstorming-academy) flips the question for you and collects the inversions, then turns them back into fixes. Free to start.

## Related ideas

Reverse brainstorming is one application of the broader principle of **inversion** — solving by characterizing what you *don't* want and working backwards. Related forms:

- [Premortem](/academy/how-to-run-a-premortem) — the project-level version: assume the project failed and ask what caused it
- [5 Whys](/frameworks/fivewhys) — narrower: walk one observed problem back to its root
- [First Principles](/academy/first-principles-thinking-with-examples) — orthogonal: instead of inverting, decompose to atoms and rebuild
- [SWOT](/academy/what-is-a-swot-analysis) — the Threats quadrant is a mini-inversion baked into a broader framework

The common thread: when forward thinking is stuck, ask the inverse. Failure modes are often easier to see clearly than success paths.

[Open the Reverse Brainstorming entry →](/frameworks/reversebrain) for the worksheet template.

---

### RICE Prioritization Framework: Score & Rank Your Backlog (2026)
URL: https://frameworklist.com/academy/rice-prioritization-framework
> RICE scores ideas by Reach × Impact × Confidence ÷ Effort, turning subjective debate into a defensible ranked list. Here's how to use it without faking the numbers.

**RICE** is a prioritization framework that ranks ideas by computing a single score from four inputs: **R**each, **I**mpact, **C**onfidence, and **E**ffort. The formula is `(Reach × Impact × Confidence) / Effort`, and the output is a ranked list defensible enough to share in a planning meeting without an hour of debate.

> Looking for the calculator with worked examples? See [RICE score calculator: the formula with 3 worked examples](/academy/rice-score-calculator-with-examples).

RICE was published by Sean McBride at Intercom in 2016 as the framework Intercom's product team actually used. The format caught on because it converts the soft "this feels important" conversation into specific, comparable numbers — without pretending to be more precise than it is. (If you're not sure RICE is even the right tool for your decision, start with [how to pick a framework in the first place](/blog/framework-to-pick-a-framework).)

> **Score your backlog on your phone** — [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=rice-academy) computes RICE scores with AI-assisted inputs. Free to start.

## The four inputs

- **Reach** — how many people the change affects in a defined time period. Customers per quarter, signups per month, daily active users touched per week. Pick the unit once and use it for every idea in the comparison.
- **Impact** — how much it changes things *per person* when it lands. Intercom uses a 5-point scale: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal. The bins are deliberately coarse to prevent fake precision.
- **Confidence** — how sure you are about the Reach and Impact estimates. 100% = strong evidence, 80% = some evidence, 50% = gut feel. Anything below 50% means the score is mostly noise.
- **Effort** — total person-months to ship. Sum across roles. Use the same unit for every idea.

The score is `(Reach × Impact × Confidence) / Effort`. Higher = better.

## How to actually use it

1. **List 10–30 ideas.** Don't bother below 10; the ranking is meaningless with too few. Don't go above 30 in one session; the team gets fatigued and starts rubber-stamping.
2. **Score Reach with concrete numbers, not relative scales.** "Affects 8,000 users per quarter" beats "high reach." Look up the actual numbers from analytics rather than guessing.
3. **Score Impact discreetly per idea, not relatively.** Don't peek at other ideas' impact scores until you've scored this one independently. Relative scoring drifts toward the middle.
4. **Score Confidence honestly.** If you've never tested anything like this, you're at 50%, not 90%. The whole point of the C term is to penalize beautiful-but-speculative ideas.
5. **Estimate Effort with two people.** Solo estimates are systematically optimistic. Pair-estimating cuts the systematic bias in half.
6. **Compute the score, then read the ranked list.** Don't tweak the inputs to make a favored idea win — that's the failure mode RICE was designed to prevent.

## What RICE is good at

- **Cross-functional planning meetings** where engineering, design, and product are arguing about which feature to build next. RICE gives everyone the same vocabulary.
- **Quarterly roadmap selection** when you have more ideas than capacity. The Effort denominator forces honest cost accounting.
- **Documenting the *why* of a prioritization decision** for a stakeholder who wasn't in the room. The spreadsheet is the artifact.

## What RICE is bad at

- **Highly novel work** where Confidence is below 50% for everything. The output is too noisy to be useful — use a [premortem](/academy/how-to-run-a-premortem) instead to surface what you don't know.
- **Strategic positioning** ("should we enter this market"). Use a [SWOT](/academy/what-is-a-swot-analysis) or [Porter's Five Forces](/frameworks/fiveforces) at that level; RICE assumes the market is already chosen.
- **Ideas with externalities** — a project that unblocks 10 other projects has a Reach RICE can't capture in one number. Add a side column for dependencies and read both.

## The "I cheated the scores" failure mode

The most common abuse of RICE: someone has an idea they want to win, and they inflate Reach or Impact until the score comes out right. Two practices defend against this:

- **Calibrate against a known winner.** Pick one feature you already shipped and know was successful. Score it with RICE. Every new idea has to be compared to *that* baseline — Reach and Impact in the same units, scaled to the same scale.
- **Separate the scoring from the deciding.** The person who advocates for an idea should not be the same person who scores it. Get a second set of eyes on Reach, Impact, and Confidence before computing.

If a team can't score the same ideas the same way twice, the team doesn't yet have the shared context to use RICE — and that's a real signal worth listening to.

## When to graduate from RICE

Once a team has used RICE for 4–6 quarters and has a real history of "we scored this X and the actual outcome was Y," the team will know which terms it systematically over- or under-estimates. At that point, replace RICE with a custom scoring rubric that reflects what the team has actually learned. RICE is the training-wheels version; the customized rubric is the bicycle.

## The RICE Confidence Discount

The single most common failure mode in real RICE practice is **Confidence inflation**: teams default the C input to 0.80 on every item, which neutralizes the math because everything gets the same multiplier. The Confidence Discount is a named correction: every quarter, score the *actual delivery outcomes* of last quarter's RICE-ranked items, and compute a team-specific Confidence multiplier from the gap between predicted and actual Impact × Reach.

The protocol:

1. **Pull last quarter's RICE-scored items that actually shipped.**
2. **Re-score Impact and Reach with hindsight.** What did each item actually deliver?
3. **Compute the ratio of actual-to-predicted (Impact × Reach) for each item.**
4. **Take the median ratio across all items.** This is your team's Confidence Discount.
5. **Multiply next quarter's Confidence inputs by this discount.** A team scoring everything at 0.80 might find their median ratio is 0.75 — meaning their true Confidence baseline is closer to 0.60, and items they think are "80% confident" are actually behaving like "60% confident reporting at 80% out of habit."

A worked re-calibration on a 5-item shipped batch:

| Item | Predicted Impact × Reach | Actual | Ratio |
|---|---|---|---|
| Onboarding redesign | 1.0 × 8,000 = 8,000 | 0.5 × 5,000 = 2,500 | 0.31 |
| Search filter v2 | 0.5 × 12,000 = 6,000 | 0.5 × 9,000 = 4,500 | 0.75 |
| Notification opt-in | 0.25 × 20,000 = 5,000 | 0.25 × 18,000 = 4,500 | 0.90 |
| AI-assistant launch | 2.0 × 4,000 = 8,000 | 1.0 × 3,500 = 3,500 | 0.44 |
| Mobile checkout fix | 1.0 × 15,000 = 15,000 | 1.0 × 14,000 = 14,000 | 0.93 |

Median ratio: **0.75**. The team's stated Confidence numbers should be multiplied by 0.75 next quarter. Items the team scores at 0.80 actually behave like 0.60. The ranking shifts accordingly — items that depend heavily on Impact estimates (which historically miss harder) drop relative to items dominated by Reach (which historically lands closer). After 2-3 quarters of re-calibration, most teams converge on a stable team-specific Confidence baseline somewhere in the 0.55-0.70 range.

Why this works: it makes Confidence an *empirical* input rather than a self-report. The biggest wins from RICE come not from the formula itself but from teams learning *which kinds of items they systematically over-confident on*. Confidence ratios near 0.30-0.40 (the AI-assistant launch row above) flag categories of work where the team is consistently wrong — a structural learning, not just a single-item correction.

Compare the alternatives at [RICE vs ICE](/compare/rice-vs-ice) (when Reach is too hard to estimate at all) and [RICE vs MoSCoW](/compare/rice-vs-moscow) (when scoring itself is too heavy for the team's stage). Teams running SAFe often reach for [WSJF (Weighted Shortest Job First)](/glossary/wsjf) instead, which divides cost of delay by job size rather than weighing Reach and Impact separately — see the full head-to-head at [RICE vs WSJF](/compare/rice-vs-wsjf).

## Related frameworks

- [Pareto Analysis (80/20 Principle)](/academy/pareto-analysis-80-20-principle) — for spotting the 20% of items that drive 80% of value before scoring everything in the backlog
- [RICE vs MoSCoW](/compare/rice-vs-moscow) — when to bucket scope vs when to score
- [RICE vs ICE](/compare/rice-vs-ice) — the Reach term, and when dropping it is the right call
- [ICE Score](/frameworks/ice) — the lighter cousin (Impact × Confidence × Ease), useful when Reach is hard to estimate
- [MoSCoW](/frameworks/moscow) — categorical alternative when scoring is too heavy
- [Weighted decision matrix](/frameworks/weightedmatrix) — for choosing between *options* rather than ranking *features*
- [Kano Model](/frameworks/kano) — pair with RICE when classifying feature *types* matters more than score
- [RICE for SaaS teams](/playbooks/rice-for-saas) — industry playbook: tuning Reach and Confidence for recurring-revenue roadmaps
- [RICE for agency teams](/playbooks/rice-for-agency) — industry playbook: scoring client work when Effort is billable hours

Want to try it? [Open the RICE entry →](/frameworks/rice) for the catalog template, or sign in to use it in the canvas with your real backlog.

---

### RICE score calculator: the formula, explained with 3 worked examples
URL: https://frameworklist.com/academy/rice-score-calculator-with-examples
> How to actually compute a RICE score — the formula, the 5-point Impact scale, the 50/80/100% Confidence rule, and three full worked examples with real numbers.

The RICE formula is `(Reach × Impact × Confidence) / Effort`. Pasted into a spreadsheet, that's a calculator. But the formula is the easy part — the hard part is **picking honest numbers for the inputs** so the output isn't theatre.

This page is the calculator, the rules for each input, and three full worked examples with the arithmetic showing.

> **Want to run RICE on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a RICE worksheet with the scoring rules built in — fill in your features, see the ranking. Or try the [live RICE example](/frameworks/rice) on the framework page first.

### Prefer to watch or listen?

<YouTube id="Cx3PxGcKd6Q" title="RICE score calculator: the formula explained with 3 worked examples" />

<Spotify id="42IKgenO4C8cneCU6HBcld" title="RICE score calculator — Framework podcast episode" />

## The formula (and what each input really means)

```
RICE = (Reach × Impact × Confidence) / Effort
```

Higher score = higher priority. The four inputs are not interchangeable — each one has a specific definition and a specific scale. Mixing them up is the most common way RICE goes wrong.

| Input | What it measures | Unit / Scale |
|---|---|---|
| **Reach** | How many people the work affects in a defined time period | Real count (users / customers / events) per quarter |
| **Impact** | How much it moves the metric *per person* when it lands | Fixed 5-point scale: 3 / 2 / 1 / 0.5 / 0.25 |
| **Confidence** | How sure you are about Reach and Impact | 100% / 80% / 50% only |
| **Effort** | Total person-months across everyone involved | Real number (sum of all roles' time) |

The two "real number" inputs (Reach, Effort) want actual counts. The two scaled inputs (Impact, Confidence) use **deliberately coarse buckets** to prevent fake precision.

## The Impact scale

| Score | Meaning | Example |
|---|---|---|
| **3** | Massive | A retention fix that lifts engaged-user rate by 20%+ |
| **2** | High | A new feature that moves a top metric by 5–15% |
| **1** | Medium | A solid improvement to an existing flow |
| **0.5** | Low | A small win, noticeable but not category-changing |
| **0.25** | Minimal | A polish that users may not notice |

If you find yourself wanting 1.5 or 2.5, you are pretending the framework is more precise than it is. Pick a bucket.

## The Confidence rule

| Score | Meaning | Evidence |
|---|---|---|
| **100%** | Strong evidence | Quantitative data + tested hypothesis |
| **80%** | Some evidence | Qualitative signal + one supporting data point |
| **50%** | Gut feel | Opinion + analogy to other work |

Anything below 50% means the score is noise. If your Confidence is < 50%, **the idea isn't ready to prioritize** — it's a research item, not a roadmap item.

## How to calculate a RICE score (5 steps)

1. **Define the one metric you're prioritizing against.** Active users? Revenue? Tickets-deflected? RICE only compares apples to apples. One backlog = one metric.
2. **Estimate Reach in real units for a fixed period.** "8,000 users per quarter," not "lots of people." Pick the period (usually a quarter) and stick to it for every item.
3. **Pick Impact from the 5-point scale.** Don't invent values. If you can't decide between 2 and 3, pick 2 (the formula rewards being conservative).
4. **Pick Confidence from one of three values: 100%, 80%, or 50%.** Be honest about evidence. Confidence is where most teams lie to themselves.
5. **Estimate Effort as total person-months.** Sum across roles: 2 engineers × 2 months + 1 designer × 0.5 months = 4.5 person-months.

Then `(R × I × C) / E`, sort descending, look at the top quartile.

---

## Worked example 1: A B2B SaaS Q3 backlog

A team running a $50K MRR B2B SaaS product is choosing between four candidates for Q3. Each is sized roughly the same — bigger than a bug fix, smaller than a strategic pivot.

| Item | Reach (users/Q) | Impact | Confidence | Effort (PM) | RICE Score |
|---|---|---|---|---|---|
| Onboarding redesign | 6,000 | 2 | 95% (round to 100%) | 3 | **(6000 × 2 × 1.0) / 3 = 4,000** |
| AI recommendation v2 | 8,000 | 3 | 80% | 6 | **(8000 × 3 × 0.8) / 6 = 3,200** |
| Mobile redesign | 12,000 | 2 | 90% (round to 80%) | 10 | **(12000 × 2 × 0.8) / 10 = 1,920** |
| Export-to-CSV | 3,000 | 1 | 100% | 2 | **(3000 × 1 × 1.0) / 2 = 1,500** |

**Ranking**: Onboarding redesign > AI recommendation v2 > Mobile redesign > Export-to-CSV.

The interesting result: Mobile redesign has the highest Reach (12,000) but ranks third because Effort is 10 person-months. RICE is doing what it's supposed to do — punishing big swings unless the Reach × Impact justifies the cost.

The team's gut said "ship Mobile because it touches the most users." RICE says: not at that effort multiplier. Either cut Mobile's scope (lower Effort) or rank it lower.

For a fully written-up version of this exact scenario, see the [RICE on a real SaaS Q3 backlog](/examples/rice-saas-q3-backlog) example.

---

## Worked example 2: Growth experiments competing for one engineer-week

Growth teams often have one engineer-week to allocate among 5 experiments. Reach is the daily user count touching each surface, Effort in person-weeks.

| Experiment | Reach (users/day) | Impact | Confidence | Effort (PW) | RICE Score |
|---|---|---|---|---|---|
| Pricing page A/B test | 2,500 | 1 | 80% | 0.5 | **(2500 × 1 × 0.8) / 0.5 = 4,000** |
| Email re-engagement campaign | 8,000 | 0.5 | 50% | 0.25 | **(8000 × 0.5 × 0.5) / 0.25 = 8,000** |
| Onboarding tooltip tweaks | 1,200 | 0.5 | 100% | 0.5 | **(1200 × 0.5 × 1.0) / 0.5 = 1,200** |
| Referral incentive bump | 600 | 2 | 50% | 1 | **(600 × 2 × 0.5) / 1 = 600** |
| New homepage hero | 4,000 | 1 | 50% | 1 | **(4000 × 1 × 0.5) / 1 = 2,000** |

**Ranking**: Email re-engagement (8,000) > Pricing A/B (4,000) > Homepage hero (2,000) > Onboarding tweaks (1,200) > Referral bump (600).

The Email campaign wins despite a low Impact (0.5) and gut-feel Confidence (50%), because Reach is huge and Effort is a quarter-week. This is RICE telling you: **with very low effort, even modest expected value beats higher-stakes bets.** Ship the cheap experiment first; the data improves Confidence for everything downstream.

---

## Worked example 3: Engineering platform investments

Platform teams hate RICE because Reach is awkward (your "users" are other engineers) and Impact lacks revenue language. Here's how to do it honestly.

The trick: define Reach as the count of internal users (engineers) affected, and define Impact in terms of saved time or prevented incidents.

| Investment | Reach (engineers) | Impact | Confidence | Effort (PM) | RICE Score |
|---|---|---|---|---|---|
| Faster CI pipeline | 40 | 2 | 80% | 4 | **(40 × 2 × 0.8) / 4 = 16** |
| Deploy automation | 40 | 1 | 100% | 2 | **(40 × 1 × 1.0) / 2 = 20** |
| New observability stack | 40 | 3 | 50% | 12 | **(40 × 3 × 0.5) / 12 = 5** |
| Dependency upgrade tooling | 25 | 0.5 | 100% | 1 | **(25 × 0.5 × 1.0) / 1 = 12.5** |

**Ranking**: Deploy automation > Faster CI > Dependency tooling > Observability stack.

The Observability stack has the highest Impact (3) but the lowest Confidence (50%) and biggest Effort (12 PM) — it's a high-stakes bet without evidence. RICE puts it last not because it's a bad idea, but because the team should reduce uncertainty before committing 12 person-months.

If the team can run a 1-week spike (Confidence → 80%) and confirm the value, the score becomes `(40 × 3 × 0.8) / 12 = 8` — moving it ahead of Dependency tooling but still behind Deploy. Confidence is the most leveraged input in RICE.

---

## When NOT to use RICE

RICE earns its keep when you have a backlog with **20–30 comparable items** and a team that keeps relitigating priority. It is the wrong tool when:

- **You have fewer than 5 candidates.** With that few, the ranking is noisy. Use [RICE vs ICE](/compare/rice-vs-ice) or pros/cons.
- **The items aren't comparable in scope.** Don't mix three-day fixes with six-month epics — the spread destroys the math.
- **You're choosing between strategic directions.** RICE is a tactical tool. For "should we enter market X?" use [Ansoff Matrix](/frameworks/ansoff) or [Five Forces](/frameworks/fiveforces).
- **Confidence is below 50% for most items.** That means you're prioritizing research, not work. Run discovery first.

## Common mistakes

| Mistake | Fix |
|---|---|
| Inventing Impact values like 1.5 or 2.5 | Pick a bucket. The coarseness is the point. |
| Treating Confidence as "how much I like the idea" | Confidence is about *evidence*, not preference. Be honest. |
| Comparing Reach across different time periods | Pick one period (usually quarter) and use it for everything. |
| Estimating Effort in calendar time instead of person-time | A 2-month project with 3 people is 6 person-months. |
| Sorting and shipping the top item with no discussion | The score is a starting point, not a verdict. The team's job is to spot which scores feel wrong and find the input that's lying. |

## RICE vs other prioritization frameworks

RICE has a Reach term that simpler frameworks like [ICE](/frameworks/ice) leave out. If you can quantify Reach with data, RICE produces more defensible rankings. If you can't, ICE is faster.

For a side-by-side comparison with worked examples, see [RICE vs ICE: which prioritization framework to use](/compare/rice-vs-ice). If you're scoping a fixed-deadline release rather than ranking an open backlog, the right comparison is [RICE vs MoSCoW](/compare/rice-vs-moscow). For larger enterprise contexts with SAFe, see [WSJF](/frameworks/wsjf).

## The original source

RICE was published in 2017 by Sean McBride at Intercom as the framework Intercom's product team actually used internally. The format caught on because it converts vague debate into specific numbers without pretending to be more precise than its inputs.

---

> **Run RICE on your team's backlog**: Framework's iOS app ships a RICE worksheet preloaded with the scoring rules above. [Get it on the App Store](https://apps.apple.com/app/id6765632580). Or use the web version with [the full live example](/frameworks/rice) on the framework page.

---

### Strategy Framework Decision Map: Which Framework for Which Decision (2026)
URL: https://frameworklist.com/academy/strategy-framework-decision-map
> A map of which strategy framework fits which decision — prioritization, growth, risk, customers, goals — with the single deciding question for each pairing, synthesized from 30+ framework guides.

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.** (For the fast two-minute version of that triage, see [the framework I use to pick a framework](/blog/framework-to-pick-a-framework); for why frameworks so often disappoint even when correctly chosen, see [why most frameworks fail](/blog/why-most-frameworks-fail).)

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](/academy/rice-prioritization-framework) | [RICE vs ICE](/compare/rice-vs-ice) · [RICE vs MoSCoW](/compare/rice-vs-moscow) · [RICE vs WSJF](/compare/rice-vs-wsjf) |
| Triage your own week | [Eisenhower Matrix](/academy/eisenhower-matrix-urgent-vs-important) | — |
| Scan the macro environment | [PESTEL](/frameworks/pestel) | [SWOT vs PESTLE](/compare/swot-vs-pestle) · [PESTEL vs Five Forces](/compare/pestel-vs-porters-five-forces) |
| Analyze an industry's structure | [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) | [SWOT vs Five Forces](/compare/swot-vs-five-forces) |
| Assess a specific position | [SWOT](/academy/what-is-a-swot-analysis) | [SWOT vs Five Forces](/compare/swot-vs-five-forces) |
| Pick a growth path | [Ansoff Matrix](/frameworks/ansoff) · [BCG Matrix](/frameworks/bcg) | [Tesla Ansoff worked example](/examples/tesla-ansoff-matrix) |
| Understand what customers actually want | [Jobs-to-be-Done](/academy/jobs-to-be-done-framework-explained) | [JTBD vs Personas](/compare/jtbd-vs-personas) |
| Surface what could kill a launch | [Premortem](/academy/how-to-run-a-premortem) | [Premortem vs Postmortem](/compare/premortem-vs-postmortem) |
| Decide how to decide (ordered vs complex) | [Cynefin](/academy/cynefin-framework-for-pmp) | [Cynefin vs Stacey Matrix](/compare/cynefin-vs-stacey-matrix) |
| Set quarterly goals vs track health | [OKRs vs KPIs](/academy/okrs-vs-kpis-difference) | — |
| Diagnose an org / post-merger fit | [McKinsey 7S](/academy/mckinsey-7s-framework-hard-soft-elements) | — |
| Design or pivot a business model | [Lean Canvas](/frameworks/lean) | [Lean Canvas vs Business Model Canvas](/compare/lean-canvas-vs-business-model-canvas) |
| Find the root cause of a problem | [5 Whys](/frameworks/fivewhys) · [Pareto 80/20](/academy/pareto-analysis-80-20-principle) | — |
| Break an assumption-bound problem | [First Principles](/academy/first-principles-thinking-with-examples) · [Reverse Brainstorming](/academy/reverse-brainstorming-solve-problems-backwards) | — |
| Choose a career or life direction | [Ikigai](/frameworks/ikigai) · [Wheel of Life](/frameworks/wheeloflife) | Score the eight life areas first — if the dissatisfaction isn't actually work, Ikigai will send you to fix the wrong thing |

> **Running a SWOT specifically?** Our sister tool [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=decision-map) 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](/academy/what-is-a-swot-analysis), [PESTEL](/frameworks/pestel), [Five Forces](/academy/porters-five-forces-beginners-guide), [Ansoff](/frameworks/ansoff), [Blue Ocean](/frameworks/blueocean)
- **Understand the customer** — what do they actually need? → [Jobs-to-be-Done](/academy/jobs-to-be-done-framework-explained)
- **Order the work** — what do we do first? → [RICE](/academy/rice-prioritization-framework), [Eisenhower](/academy/eisenhower-matrix-urgent-vs-important), [MoSCoW](/frameworks/moscow), [WSJF](/glossary/wsjf)
- **De-risk the call** — what could go wrong, and how do we even decide? → [Premortem](/academy/how-to-run-a-premortem), [Cynefin](/academy/cynefin-framework-for-pmp)
- **Set and track the target** — what are we aiming at? → [OKRs vs KPIs](/academy/okrs-vs-kpis-difference)

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](/frameworks/pestel) → [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) → [SWOT](/academy/what-is-a-swot-analysis) — macro weather, then the industry ring, then your position inside it.
- **Roadmap planning**: [Jobs-to-be-Done](/academy/jobs-to-be-done-framework-explained) → [RICE](/academy/rice-prioritization-framework) — clarify the demand, then rank the bets against it.
- **Risky launch**: [Premortem](/academy/how-to-run-a-premortem) → [OKRs](/academy/okrs-vs-kpis-difference) — surface what could fail, then set targets that account for it.

For worked, company-grounded chains, see the [Decision Center](/decisions) and examples like the [Tesla Ansoff Matrix](/examples/tesla-ansoff-matrix) and [Nvidia BCG Matrix](/examples/nvidia-bcg-matrix).

## Use any of these on your phone

> Want to fill in any framework with AI assistance? [Framework List for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=decision-map) — 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.

---

### What is a SWOT analysis?
URL: https://frameworklist.com/academy/what-is-a-swot-analysis
> SWOT is a 2×2 grid that surfaces a position's internal strengths and weaknesses alongside external opportunities and threats. Here is how to run one in 5 steps.

> **Need to actually run a SWOT?** [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-redirect) is the dedicated AI SWOT tool — free, no signup.

A SWOT analysis is a structured way to evaluate any strategic position by listing its **Strengths, Weaknesses, Opportunities, and Threats** in a 2×2 grid — the four-part shorthand defined in our glossary entry for [SWOT](/glossary/swot). Strengths and weaknesses are *internal* — they describe what the team or product already has under its control. Opportunities and threats are *external* — they describe what the world is doing around the position.

<SwotMatrix />

The framework was developed by Albert Humphrey at Stanford Research Institute in the 1960s as part of a long study on why corporate planning was failing. Today it is the most-used starting point for strategy work because it forces a balanced view across upside and downside in a single glance.

## When to use a SWOT

Reach for a SWOT when you are evaluating a position where both internal capabilities and external forces matter. Common moments:

- Deciding whether to enter a new market
- Launching a new product or feature
- Evaluating a partnership or acquisition
- Onboarding into a new role and getting your bearings
- Re-planning at the start of a quarter

Skip SWOT when you already know the answer — it is a structuring tool, not a deciding tool.

## How to run one in 5 steps

1. **Define the position.** A SWOT is always *of* something specific. "SWOT of the company" is too vague; "SWOT of shipping AI features now vs. after a brand revamp" is sharp enough to fill in.
2. **List 3–5 entries per quadrant.** Resist filling every quadrant equally. If you can only find one threat, that itself is the insight.
3. **Pressure-test internal vs. external.** A weakness is something you control and could fix. A threat is something outside your control. Mixing them is the most common error.
4. **Pair quadrants for action.** Strengths + Opportunities = bet here. Weaknesses + Threats = defend or exit. Strengths + Threats = pre-empt. Weaknesses + Opportunities = invest to unlock.
5. **Write one paragraph of synthesis.** A SWOT is incomplete until you can say out loud what the picture means.

## Common pitfalls

The classic failure mode is treating SWOT as a static document. Capabilities shift, markets shift — a SWOT done last quarter is already drifting. Re-run it whenever the underlying question reopens.

The second failure mode is using SWOT to justify a decision you already made. If you find yourself stretching to fill the "Weaknesses" quadrant, the analysis is post-hoc and worth less than the time it took. For a worked example of an honest SWOT done under real pressure, see [how Netflix used SWOT in 2007](/blog/how-netflix-used-swot-2007) to weigh its DVD business against the leap into streaming.

> **Want frameworks beyond SWOT on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=swot-academy) fills in any of 100+ frameworks with AI assistance. For SWOT specifically, [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-academy-ios) is the dedicated tool.

## Related frameworks

- [PESTLE](/frameworks/pestel) extends SWOT's external view with political, economic, social, technological, legal, and environmental forces.
- [Porter's Five Forces](/frameworks/fiveforces) goes deeper on competitive dynamics where the threats quadrant is dominant.
- [VRIO](/frameworks/vrio) refines the strengths quadrant by asking which capabilities are actually rare and hard to imitate.

## SWOT playbooks by industry

The four cells stay the same, but the load-bearing inputs change by industry. These playbooks tune the prompts inside each quadrant:

- [SWOT for SaaS](/playbooks/swot-for-saas) — retention, expansion, and platform risk
- [SWOT for e-commerce](/playbooks/swot-for-ecommerce) — SKU-level unit economics and channel-algorithm risk
- [SWOT for agencies](/playbooks/swot-for-agency) — utilization, talent leverage, and client concentration
- [SWOT for healthcare](/playbooks/swot-for-healthcare) — payer mix, clinical staffing, and regulatory framing
- [SWOT for EdTech](/playbooks/swot-for-edtech) — the buyer/user split and procurement-cycle reality

Want to actually fill one in? [Open the SWOT canvas →](/frameworks/swot)

---

## Blog

### Nvidia at $5T: the AI chip industry through Five Forces
URL: https://frameworklist.com/blog/ai-chip-five-forces-nvidia-5-trillion
> Nvidia's $5 trillion market cap and Q1 2026 beat looked like an unbreakable moat. Five Forces says the moat is real but the cracks are forming in three places investors aren't tracking.

![Macro photograph of a green circuit board showing transistors and traces](https://images.unsplash.com/photo-1518770660439-4636190af475?auto=format&fit=crop&w=1600&q=80)

Last Wednesday Nvidia reported Q1 FY27 revenue of around $79 billion, beating Wall Street's $78.8B consensus and confirming the 75% year-on-year growth analysts had been pricing in. The stock pushed Nvidia's market cap past $5 trillion. CNBC ran a headline about the "five layer cake" of AI infrastructure Nvidia now owns. The narrative is that the moat is unprecedented.

It is unprecedented. It's also narrower than the headlines suggest. The framework that surfaces this is the oldest one in the strategy textbook: Porter's [Five Forces](/academy/porters-five-forces-beginners-guide). Run cleanly on the AI chip industry today, it shows that two forces are pushing in Nvidia's favor — and three are pushing the other way harder than the stock price would imply.

### Prefer to watch or listen?

<YouTube id="FqTJqtQ1NB8" title="Nvidia at $5T: the AI chip industry through Five Forces" />

<Spotify id="101dkbTHNWNll4t7UeOCct" title="Nvidia at $5T: the AI chip industry through Five Forces — Framework podcast episode" />

## The four numbers that frame the analysis

Before applying the framework, put the current state on the table:

| Metric | Value | Direction vs. 12 months ago |
|---|---|---|
| Nvidia data-center GPU market share | 88–92% | Down from ~95% |
| Hyperscaler 2026 capex (AMZN, GOOG, META, MSFT combined) | $635–670B | Up from ~$420B |
| Nvidia Q1 FY27 revenue / YoY growth | $79B / +75% | Up from $26B (FY26 Q1) |
| Market cap | $5T (May 2026) | Up from $2.6T |
| Foundry concentration (leading-edge nodes) | TSMC sole-source for Blackwell/Hopper | Unchanged |
| HBM3e suppliers | SK Hynix + Samsung (duopoly) | Tightened from 3-supplier market |
| H200 export status to China | Cleared for ~10 firms (May 14, 2026) | Reversal of 2024 restrictions |

These numbers are what the Five Forces analysis has to explain. Two of them (share, market cap) tell the bull story. The others tell a different one.

## Five Forces scorecard for the AI chip industry, May 2026

| Force | Direction for Nvidia | Current strength | What flips it |
|---|---|---|---|
| Threat of new entrants | ✅ Helping | Low | A non-CUDA toolchain reaching parity with vLLM/PyTorch |
| Buyer power | ✅ Helping (currently) | Weak — supply binding | TSMC 2nm capacity unlocks (12–18mo) |
| Supplier power | ❌ Hurting | High & permanent | Vertical integration (unlikely) |
| Threat of substitutes | ❌ Hurting | Rising fast in inference | Custom ASICs hit >40% of hyperscaler cycles |
| Competitive rivalry | ❌ Hurting | Intensifying from inside customers | Hyperscaler custom silicon scales |
| *Sixth force (complementors)* | ✅ Helping | Strong but fragile | A 12-month perf gap on competitor silicon |

Two helping, three hurting, one fragile-helping. The next sections walk each one.

## The two forces helping Nvidia

**Threat of new entrants: low but not for the reason people think.** Building a competitive AI accelerator now requires 3+ years of design, billions in NRE, mature foundry access, and — the hard part — a software ecosystem. CUDA is the moat people name. The deeper moat is the customer's switching cost: every research lab, every fine-tuning pipeline, every PyTorch optimization has been written against Nvidia's instruction set. OpenAI is reportedly exploring its own chip; even if it ships in 2027, the question isn't whether the silicon is good but whether OpenAI's own teams can refactor a decade of CUDA-coupled code. New entrants face a wall that's mostly software, not mostly fab.

**Buyer power: structurally moderate, currently weak.** Hyperscalers control the buyer side, and four customers placing $635B in orders should have crushing leverage. They don't, because demand currently outstrips Nvidia's TSMC allocation. When supply is the binding constraint, the seller sets the price. This force is the one most likely to flip — buyer power inverts the moment supply catches up, and 2027 capacity additions at TSMC suggest that moment is 12–18 months out.

## The three forces working against Nvidia

![Photograph of a data center server hall with blue lighting](https://images.unsplash.com/photo-1558494949-ef010cbdcc31?auto=format&fit=crop&w=1600&q=80)

**Supplier power: high and structurally permanent.** Nvidia's bottleneck isn't its own engineering — it's TSMC's leading-edge node capacity and SK Hynix's HBM3e output. TSMC sets prices for the 3nm and 5nm processes that Blackwell needs; SK Hynix and Samsung set HBM prices; ASML sets the lithography prices upstream of that. Nvidia is a massive customer of all three, but a customer nonetheless. Margin compression from this side is a 2026–2027 story analysts haven't priced in cleanly.

**Threat of substitutes: rising fast in inference.** The substitute story is what's most under-tracked. As generative AI moves from training (where Nvidia is unmatched) to inference (where price-per-query dominates), the workload shifts toward specialized inference chips and custom ASICs. AWS Trainium, Google TPU, Microsoft Maia, and the new wave of inference-only startups (Groq, Cerebras, SambaNova at the high end; smaller players at the edge) all undercut Nvidia on tokens-per-dollar for production workloads. Nvidia's Blackwell roadmap addresses this, but the structural advantage isn't there — generic GPU silicon was never the right shape for inference economics.

**Competitive rivalry: intensifying from inside the customer base.** This is the force most strategists miss. The classical reading of competitive rivalry asks about AMD, Intel, and pure-play challengers. The real rivalry now comes from Nvidia's own customers: every hyperscaler with a custom silicon program is, simultaneously, Nvidia's largest customer and its largest competitor. The technical term is *vertical encroachment* — your buyer is also building your product.

### Hyperscaler custom silicon programs (May 2026)

| Hyperscaler | Custom chip | Current status | Implication for Nvidia |
|---|---|---|---|
| Google | TPU v6 ("Trillium") | Shipping at scale, ~60% of Gemini training | Already substituting at the highest-value workload |
| Amazon (AWS) | Trainium 2 / Inferentia 3 | GA on Bedrock, Anthropic committed | Substituting on inference economics |
| Microsoft | Maia 100 (training) + Cobalt 100 (general) | First-party Azure workloads | Hedging on training; inference next |
| Meta | MTIA v2 | Internal recommender + ranking at scale | Lower visibility but real volume |
| OpenAI | Reported Broadcom partnership | Targeted for 2026–27 | The most-watched 2027 catalyst |

Five Forces classically treats supplier and competitor as different actors. In AI chips, they're the same companies wearing two hats — and the buyer side of those companies funds the development of the competitor side.

## The hidden term: ecosystem lock-in (Sixth Force)

Porter's original framework had five forces. Andrew Grove later proposed a sixth — *complementors* — and the AI chip industry is where it earns its keep. Nvidia's CUDA ecosystem is the textbook complementor moat: every framework, every research paper, every fine-tuning pipeline that exists today was written assuming Nvidia hardware. The moat isn't transistor density. It's the 50,000 PhDs whose code runs on green silicon by default.

The vulnerability of the complementor moat is that it's a one-way ratchet. As long as Nvidia ships new generations on a 2-year cadence, the ratchet holds. The day there's a 12-month gap where a competitor is meaningfully ahead on price-per-query — even briefly — the ratchet starts to slip, because researchers will rewrite once and then keep writing on the new platform.

## The counter-argument

The bull case isn't subtle: Blackwell is shipping, Rubin (the next architecture) is on schedule, every hyperscaler keeps raising 2026 capex, and Nvidia's gross margins are *expanding* into the supply crunch. By every quarterly metric, the moat is widening, not narrowing.

That's all true, and it's also what supplier power looks like before it flips. The 2026 numbers are Nvidia's victory lap; the 2027 numbers will be the test.

### Three signals to watch

| Signal | Threshold | What it means if breached |
|---|---|---|
| TSMC 2nm allocation distribution | Equal first-wave access for AMD or hyperscalers | Supplier power has shifted; Nvidia loses pricing premium on next node |
| Inference revenue mix at AWS / Google / Azure | >40% of AI cycles on internal silicon | Substitute force has hardened in the highest-volume workload |
| Major framework first-class non-Nvidia inference (vLLM, JAX, PyTorch internals) | Parity benchmarks publicly cited | Complementor ratchet has slipped — researchers will rewrite |

If any one of these flips, the 88–92% share figure that anchors the bull case will start compressing within 4 quarters. If all three flip, the compression accelerates.

## What this means for product and strategy people

If you're running a product that *uses* AI chips (any SaaS, any model-dependent business), the implication is to assume your unit economics will improve over the next 36 months as substitute and supplier forces compress Nvidia's pricing power. Don't lock in 3-year compute contracts at 2026 prices.

If you're building a product that *competes* with Nvidia in any part of the stack, the window is the next 18 months. Substitutes win the inference market segment-by-segment, not all at once. Pick a workload — long-context inference, low-latency edge serving, vector retrieval at scale — and own it before the broader market consolidates.

If you're evaluating the stock, Five Forces says the moat is real but mis-priced. The market is buying the unprecedented 88% share number. The framework asks the better question: which of the five forces is most likely to move first, and how soon?

## The framework view

Five Forces wasn't designed for fast-moving tech industries; it was built for stable industrial competition. But its discipline — name the five pressures, score each one, look for asymmetries — surfaces what individual quarterly earnings calls can't. The headlines about Nvidia's Q1 are about one quarter of growth. The framework is about which forces will define the next ten quarters, and three of them are pushing the wrong way for the bull case.

Strategic frameworks like this aren't predictive. They're diagnostic. Apply [Five Forces](/academy/porters-five-forces-beginners-guide) to your own industry the same way: name each force, write the current state in one sentence, then find the one that's most likely to move next.

> **Want to run Five Forces on your own industry?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=nvidia-five-forces-blog) walks each force with AI-assisted prompts and keeps the scorecard in one place. Free to start.

## Sources

- [SiliconANGLE — "Five takeaways from Nvidia's earnings, and what they mean for the AI industry"](https://siliconangle.com/2026/05/21/five-takeaways-nvidias-earnings-mean-ai-industry/) — May 21, 2026
- [CNBC Daily Open — "Nvidia aims to have its 'five layer cake' of AI and eat it too"](https://www.cnbc.com/amp/2026/05/21/cnbc-daily-open-nvidia-earnings-ai-five-layer-cake.html) — May 21, 2026
- [Intellectia.ai — "NVIDIA Hits $5 Trillion Market Cap on Soaring AI Chip Demand"](https://intellectia.ai/blog/nvidia-5-trillion-market-cap-ai-chip-demand-2026) — 2026
- [Intellectia.ai — "NVIDIA Earnings Preview May 2026: AI Chip Leader Faces High Expectations"](https://intellectia.ai/blog/nvidia-earnings-preview-may-2026) — May 2026
- [StartupHub.ai — "Broadcom and Nvidia lead AI chip surge as US clears H200 exports"](https://www.startuphub.ai/ai-news/ai-stocks-daily/2026/ai-stocks-2026-05-14) — May 14, 2026
- [PatentPC — "The AI Chip Market Explosion: Key Stats on Nvidia, AMD, and Intel's AI Dominance"](https://patentpc.com/blog/the-ai-chip-market-explosion-key-stats-on-nvidia-amd-and-intels-ai-dominance) — 2026
- [Octopus Competitive Intelligence — "NVIDIA's Emerging Challenges: A Dive into the Future of AI Dominance"](https://www.octopusintelligence.com/nvidias-emerging-challenges-a-dive-into-the-future-of-ai-dominance/)
- [Pestel-analysis.com — "Porter's Five Forces of NVIDIA"](https://pestel-analysis.com/products/nvidia-five-forces-analysis)

*Cover photo: [Alexandre Debiève on Unsplash](https://unsplash.com/photos/FO7JIlwjOtU). Inline server-room photo: [Taylor Vick on Unsplash](https://unsplash.com/photos/M5tzZtFCOfs).*

## Related

- [Porter's Five Forces — beginner's guide](/academy/porters-five-forces-beginners-guide)
- [Five Forces applied to the airline industry](/examples/five-forces-airline-industry)
- [Netflix Five Forces case study](/examples/netflix-porters-five-forces)
- [Nvidia BCG Matrix analysis](/examples/nvidia-bcg-matrix)
- [Tesla Ansoff Matrix](/examples/tesla-ansoff-matrix)
- [Amazon PESTEL 2026 — the macro view on the hyperscaler buyer](/examples/amazon-pestel-analysis-2026)

---

### The framework I use to pick a framework
URL: https://frameworklist.com/blog/framework-to-pick-a-framework
> There are 100+ thinking frameworks in the library. Three questions get you to the right one in under two minutes, every time.

The most common message I get from people using FrameworkList is some variation of: *"I don't know which one to use."* The library has 100+ frameworks. Browsing the catalog top-to-bottom is the wrong way to find the right one — you'll spend longer choosing than thinking.

After several years of doing this, the procedure I actually use is three questions. Two minutes. Yes, this is a framework for picking a framework, and yes, I have noticed the recursion.

## Question 1: What kind of work is this?

Frameworks live in five buckets:

- **Triage** — sorting a pile of stuff you already have. Eisenhower, MoSCoW, Pareto.
- **Prioritization** — ranking options by some criteria. RICE, ICE, Weighted decision matrix, Kano.
- **Decision** — choosing between specific alternatives where the answer matters. Pros/Cons, Decision tree, Regret minimization, Cost-benefit, 10/10/10.
- **Strategy** — figuring out what to *be doing* over a longer horizon. SWOT, Five Forces, BCG Matrix, Blue Ocean, Wardley, JTBD.
- **Diagnosis** — understanding what's actually going on. 5 Whys, Fishbone, OODA, Cynefin, First Principles.

If you can name the bucket in under 30 seconds, you've eliminated 80 frameworks. If you can't name the bucket, you don't yet know what kind of problem you have — that's a useful thing to notice. Spend the next 10 minutes writing down what you're trying to do until you can.

## Question 2: How reversible is the decision?

This is the question that surprises people.

- **Low-stakes, easily reversible** — use the simplest framework that gives you a defensible answer. Pros/Cons, ICE. Don't overthink. The cost of being wrong is small, the cost of deliberation is real.
- **High-stakes, hard to reverse** — use something heavier and pair it with a premortem. SWOT or Five Forces *and* a premortem. The cost of being wrong is huge; the cost of deliberation is rounding error against that.
- **Strategically defining** — use the multi-framework approach. SWOT to map, Premortem to stress-test, Decision matrix to choose, OKRs to commit. Reversibility close to zero; deliberation should match.

The mistake people make: they apply the same framework weight regardless of stakes. Either they over-deliberate routine decisions (six hours of SWOT for which CRM to buy) or under-deliberate strategic ones (a fast Pros/Cons for which market to enter).

Match the framework's weight to the decision's weight.

## Question 3: Will other people need to see the answer?

A solo thinker can use any framework. The artifact is for them.

But the moment you need to *share* the result with stakeholders, partners, or your team, half the frameworks fall out. Some produce great solo output but bad meeting artifacts (5 Whys reads as a stream of consciousness). Some produce great meeting artifacts but require facilitation (Six Thinking Hats works in person, falls flat in Slack).

If you'll need to share, prefer frameworks that produce **structured, one-page visual outputs**. SWOT, RICE, Eisenhower, BCG, Lean Canvas, Decision matrix. These all collapse to a single image you can drop in a doc.

If you won't need to share, you have full freedom. Use the one that fits your own thinking style.

## The procedure end to end

1. **Name the bucket** (triage / prioritization / decision / strategy / diagnosis).
2. **Score reversibility** (easily reversible / hard to reverse / strategically defining).
3. **Decide on shareability** (just for me / for the team).

That's three answers. The intersection of those three almost always points to one or two frameworks. Open the [library](/frameworks), look at those, pick the one whose example matches your situation closest, run it.

## Examples I run a lot

I'll save you the trouble of reading the matrix. These are the frameworks I personally reach for most:

- **"Should I do X this week?"** — [Eisenhower Matrix](/tools/eisenhower-matrix). 60 seconds.
- **"Which of these 15 features ship next quarter?"** — [RICE](/academy/rice-prioritization-framework). 90 minutes with the team.
- **"We're about to make a big bet. What could go wrong?"** — [Premortem](/academy/how-to-run-a-premortem). 45 minutes.
- **"Should we enter this market?"** — [SWOT](/academy/what-is-a-swot-analysis) + [Five Forces](/frameworks/fiveforces) in sequence. Two sessions, a week apart.
- **"I cannot tell what is wrong with this team."** — [5 Whys](/tools/5-whys), then [Fishbone](/frameworks/fishbone) if 5 Whys runs out of road.
- **"There are three options and each one branches again."** — [Decision Tree](/frameworks/tree). Worth the 30 minutes only when the branches carry different probabilities, not just different opinions.
- **"Pivot or keep going?"** — not one framework but a chain: the [pivot-or-persevere decision page](/decisions/pivot-or-persevere) sequences three of them.

If you're new to the library, those five cover ~70% of the decisions you'll face. The other 95 frameworks become useful as you get more specific. For the full lookup — every decision mapped to its framework, plus the single deciding question for each close call — see the [Strategy Framework Decision Map](/academy/strategy-framework-decision-map).

## When none of this helps

Sometimes the answer to "which framework should I use" is *none of them*. The problem isn't underspecified or stuck — it's just hard, and a framework won't make it easier. And even when you pick the right one, the framework only structures the conversation — it doesn't hand you the answer, which is [why most frameworks fail](/blog/why-most-frameworks-fail) the teams that expect otherwise. In those cases, the right move is to talk to someone who has solved the same problem before. Frameworks are a way to think clearly when you're alone with the problem. A 30-minute call with someone who's been there is faster and better when it's available.

If you'd like to compare notes, the welcome email is from a real address. Reply to it.

— King Mark

> **Want the whole catalog on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=pick-a-framework-blog) ships 100+ frameworks with AI-assisted prompts — pick one, fill it in, keep it. Free to start.

---

### How Netflix used SWOT before the streaming pivot — a closer look
URL: https://frameworklist.com/blog/how-netflix-used-swot-2007
> Before Reed Hastings bet the company on streaming in 2007, the leadership team ran a SWOT that named the threat almost everyone else missed. A look at what they put in each quadrant, and why most teams do the exercise wrong.

> **Want to run your own SWOT?** [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-redirect) is the dedicated AI SWOT tool — free, no signup.

In 2007, Netflix had 6 million subscribers, a DVD-by-mail business that was actually profitable, and a stock price that had tripled since 2003. By any normal measure, the company was winning. That was the year Reed Hastings and the leadership team decided to launch streaming — a product so technically immature that they couldn't ship full-length movies at acceptable quality without buffering. The decision looked premature to most observers. We now know it was barely in time.

What's less well-documented is that the call wasn't a hunch. It came out of a strategic-planning cycle that included a SWOT analysis sharp enough to name what almost every competitor was refusing to see. I've spent some time digging through interviews, shareholder letters, and oral histories from that period. Here's what I think their SWOT actually looked like — and what most teams running SWOT today still get wrong by comparison.

## Reconstructing Netflix's 2007 SWOT

This is reconstructed from public statements, not leaked from a real document. But the alignment between what they said publicly and what they did is tight enough that I'd bet a meal the actual analysis looked something close to this.

**Strengths**
- Largest subscriber base in DVD-by-mail (6M, growing)
- Best-in-class recommendation algorithm (Cinematch had been live for ~7 years)
- Brand association with "movies at home" rather than "DVDs"
- Negative working capital (subscribers paid monthly; DVD acquisitions amortized over years)

**Weaknesses**
- Cost structure dependent on physical distribution centers and USPS
- Catalog rights tied to physical media — streaming rights would have to be re-negotiated
- Customer habit anchored to a slow loop (queue → mail → watch → return)
- No infrastructure for video delivery at scale

**Opportunities**
- Broadband penetration crossing 50% of US households for the first time
- Cost of bandwidth dropping ~30% per year
- Studios increasingly worried about piracy — receptive to legal streaming partners
- Mobile and connected-TV devices on a 3–5 year arrival timeline

**Threats**
- Blockbuster's "Total Access" hybrid offer was bleeding Netflix's growth in 2006–07
- Walmart had quietly exited DVD-by-mail and could re-enter at any time
- The threat *almost everyone else missed*: **once bandwidth and rights made streaming viable, the DVD-by-mail business model would be replaced — not improved — by streaming**. The question was who would replace it. If Netflix didn't, Apple, Amazon, or a studio direct-to-consumer play would.

## The quadrant most companies fill in wrong

The fourth bullet under Threats is the key. Most teams write Threats as variants of "our competitors are getting better". The vast majority of SWOT documents I've seen do exactly that. Threats becomes a list of *other companies*.

Netflix's leadership wrote a threat that was *about themselves*: the model that was making them money was the model that was about to die. The threat wasn't an external actor — it was an internal addiction to a profitable but doomed mode of operation.

This is the SWOT pattern almost nobody gets right on the first pass. The threats that actually kill companies are usually the strengths-going-stale, not the competitors. By 2010, Blockbuster's Total Access was irrelevant. By 2013, the DVD-by-mail business was a footnote. By 2020, it was *embarrassing* to remember Netflix used to mail discs. The threats that materialized were exactly the ones in the bottom-right of that 2007 quadrant.

## What they actually did with the analysis

A SWOT is decoration unless it produces actions. Public statements suggest Netflix made three:

1. **Split the company mentally.** They explicitly framed streaming as a separate business with separate metrics, even though it shared a brand and a subscriber base. This let them tolerate streaming's lower margins and worse content selection without comparing it unfavorably to the DVD business.
2. **Invest aggressively in the Opportunities quadrant.** They bet on broadband faster than the broadband market itself was betting. They struck rights deals with studios on terms that looked unfavorable at the time and absurd later.
3. **Accept short-term pain for the threats quadrant.** When they later split off DVD-by-mail as "Qwikster" in 2011, it was a botched execution of a correct strategic instinct — the DVD business was a dying asset that needed structural separation. They paid for the botched execution; the stock dropped 60% in three months. They paid for it anyway.

The 2007 SWOT didn't make those choices easy. It made them legible.

## What this teaches teams running SWOT today

Three lessons I keep coming back to from this case:

**Threats are mostly internal.** Write threats from the inside out. What is true about your current strengths that could become a liability? What is the model dependency that could go from oxygen to lead weight? Competitors are usually the smallest threat on the list.

**Opportunities should require betting.** A real opportunity is one where you'd need to act *before* the evidence is overwhelming. If the opportunity is so obvious that everyone agrees, the window has likely already closed. Netflix bet on broadband while broadband was still a coin flip.

**The output is a *decision*, not a slide.** Most SWOTs I've seen end in a filed Notion page. Netflix's ended in a multi-year, multi-billion-dollar capital allocation. The artifact you produce in the meeting room is a stake in the ground; what matters is whether you act on it.

If you're about to run a SWOT this week, I'd suggest reading the [Academy guide](/academy/what-is-a-swot-analysis) for the structure, then [open the worksheet](/tools/swot) and write your own. Spend longer than feels reasonable on the Threats quadrant — especially the threats from your own strengths going stale. That's where the analysis earns its keep.

— King Mark

> **Want frameworks beyond SWOT on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=netflix-swot-blog) fills in any of 100+ frameworks with AI assistance. For SWOT specifically, [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=netflix-swot-ios) is the dedicated tool.

## Related

- [Netflix through Porter's Five Forces](/examples/netflix-porters-five-forces) — the same company, structural rather than situational: what the streaming industry lets Netflix keep
- [SWOT vs Five Forces](/compare/swot-vs-five-forces) — why the 2007 threats quadrant kept collapsing into industry structure, and which tool actually holds it
- [SWOT vs PESTLE](/compare/swot-vs-pestle) — broadband adoption was a macro force, not a company property; PESTLE is where it belongs
- [The SWOT framework page](/frameworks/swot) — the catalog entry and worksheet template
- [Why most frameworks fail](/blog/why-most-frameworks-fail) — the filed-Notion-page failure mode this case avoided

---

### Meta Muse through Jobs-to-be-Done: what a personal agent gets hired for
URL: https://frameworklist.com/blog/meta-muse-jobs-to-be-done
> Meta's Muse hit 2.5M US downloads in two weeks. Jobs-to-be-Done shows which jobs people will actually hand a personal agent, and why shopping isn't one yet.

![A woman holding an iPhone outdoors in daylight](https://images.unsplash.com/photo-1522125670776-3c7abb882bc2?auto=format&fit=crop&w=1600&q=80)

On September 8 Meta launched [Muse](https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/), a personal AI agent that "doesn't just answer questions, it actually does the work": it sends email, books travel, fills in forms and negotiates for you, and keeps working after you close the app. Two weeks later it had passed 2.5 million US downloads. Most coverage has asked what Muse *can* do. The more useful question is the one [Jobs-to-be-Done](/academy/jobs-to-be-done-framework-explained) asks of any product: what will people actually **hire** it to do, and what will they keep doing themselves?

The first month of evidence gives a clear answer. Muse gets hired for jobs where checking its work is cheap and nobody on the other side has to agree to deal with a bot. It stalls on the jobs Meta advertised most loudly: buying, haggling, and anything that needs a third party's consent.

## Where Muse stands one month in

| Metric | Value | Source |
|---|---|---|
| Launch | Sept 8, 2026, US only, adults 18+ | Meta; Tech Insider |
| Surfaces | iOS, Android, muse.ai, WhatsApp; Mac client Sept 17 | Meta; Tech Insider |
| Pricing | Free · Power $20/mo · Maximum $100/mo | Meta help center via Tech Insider |
| Downloads | 2.5M+ US by Sept 23 (downloads, not active users) | Sensor Tower via LA Times |
| App Store rank | No. 1 free app in the US, ahead of ChatGPT, about a week in | PPC Land |
| Amazon | Blocked Muse from Amazon.com on Sept 20 | PPC Land; PYMNTS |
| Shopify | Shop Pay agentic checkout on all Shopify stores, announced Sept 21 | PYMNTS |
| Small business | Muse for Small Business, 15 app connectors, Sept 29 | Engadget |

## Why Jobs-to-be-Done is the right lens

JTBD says people don't buy products, they *hire* them to make progress in a specific situation, and they *fire* whatever they were using before. For a personal agent, the competing hires are concrete: doing it yourself, a human assistant, a single-purpose app (a travel site, a bill-negotiation service), or just not doing the task.

That framing matters because Muse's pitch is a capability list, while hiring decisions are made job by job. Someone who would happily let Muse draft a packing schedule may never let it spend $300 on their behalf. The question is not "can the agent do this?" but "is handing this job over cheaper than doing it?"

## The Check-Cost Test

A job only moves to a personal agent when it passes two gates:

1. **Check cost.** Verifying the agent's result must cost less than doing the job yourself. A schedule you can read in ten seconds passes. A purchase you have to re-verify (right item, right seller, right price, returnable) often doesn't.
2. **Counterparty consent.** If the job runs through someone else's system (a retailer, a seller, a service provider), that party has to accept an agent on the other side. Your own Gmail and Google Docs always do. Amazon, as of September 20, does not.

Fail either gate and people keep doing the job themselves, however capable the model is. Here are CNN's eight hands-on tasks from its September 23 test, scored against both gates:

| Task (CNN test) | Check cost | Counterparty consent | Outcome |
|---|---|---|---|
| Day-by-day packing schedule for a move | Low: read it | None needed (your own plan) | **Worked** |
| Email a friend about a trip | Low: read before sending | Your own Gmail | **Worked** |
| Turn restaurant tips into a Google Doc | Low | Your own Docs | **Worked** |
| Date-night ideas | **High**: two places had been closed for years, so every suggestion needs checking | None needed | Partly failed |
| Shop on Amazon | — | **Refused** | Blocked |
| Shop on Target | Medium | **Checkout blocked** automated clicks | Partly failed |
| Order shampoo | Medium | **Seller required a professional license number** | Stalled |
| Haggle on Facebook Marketplace | High: it's your reputation in the chat | **Can't message sellers directly** | Drafted a message for the user instead |

The pattern is the finding. All three successes pass both gates. Every failure fails at least one, and four of the five failures stop at the counterparty gate, not the model. Muse's limits in its first month were mostly other companies' decisions.

![A person writing a list by hand in a notebook](https://images.unsplash.com/photo-1484480974693-6ca0a78fb36b?auto=format&fit=crop&w=1600&q=80)

## The jobs Muse is actually being hired for

Read through JTBD, the hires that survive both gates share one shape: **"get this off my mind, and let me press send."** That is a planning-and-preparation job, not an execution job. It covers:

- **Coordination:** schedules, trip plans, packing lists, and turning scattered inputs (a saved recipe reel, a friend's restaurant list) into one usable artifact. Meta's own launch example of turning an Instagram recipe into a grocery list is exactly this job.
- **Drafting:** emails, follow-ups and negotiation messages that you approve before they go. Even where Muse can't act (Marketplace), the draft is still worth hiring for.
- **Watching:** tracking something over time and coming back when it changes. This is the one capability that genuinely fires a competitor, because no human assistant watches a price for three weeks for free.

Muse's own design already concedes this. A separate "Sentinel" agent has to approve anything that reaches the internet, and Muse asks before sending email or buying. In JTBD terms, Meta built a product whose safe default is *drafter with permission*. That is the job users are hiring it for, so the safety design and the demand point the same way.

## The counter-argument: the gates will open

The strongest objection is that the counterparty gate is temporary. One day after Amazon's block, Shopify and Meta announced agentic checkout with Shop Pay on all Shopify stores, and Shopify CEO Tobias Lütke wrote that the company was "partnering deeply with Muse." Checkout goes through Link by Stripe with one-time card numbers. Muse for Small Business connects to Shopify, Stripe, QuickBooks, Notion and eleven other apps. Consent is being negotiated, deal by deal.

That's right, and it sharpens the test rather than retiring it. Watch these signals:

| Signal | What it would mean | Gate it moves |
|---|---|---|
| Amazon lifts the block or signs a deal | The largest US counterparty consents | Counterparty |
| Marketplace lets Muse message sellers | Peer-to-peer jobs open up | Counterparty |
| Muse publishes return/dispute rates on agent purchases | Buyers can price the risk of an error | Check cost |
| Meta reports *active* users, not downloads | Hires are sticking, not just trials | Neither: it's the outcome |

Even when every retailer opens up, buying stays a high check-cost job for anything you care about. Expect agent shopping to grow first where errors are cheap and returns are easy: repeat purchases, groceries, commodity items. Expect it to grow last where taste or trust matters.

## What this means if you build or buy agents

- **For users:** hand Muse the jobs you'd happily delegate to a new assistant on their first day: plans, drafts, lists, reminders. Keep the jobs where a mistake costs money or reputation until you've seen its error rate.
- **For builders:** your agent's addressable market is the set of jobs that pass both gates, not the set it is technically able to attempt. Lowering check cost (clear diffs, audit trails, one-tap approval) grows that market faster than adding capabilities.
- **For retailers:** the consent gate is now a strategic choice. Amazon and Shopify made opposite bets in the same 48 hours.

There is one job a general agent doesn't attempt at all: deciding *what* to do in the first place. That's a different hire, and it's the one we compare in [Meta Muse vs Framework's Decision Agent](/vs/meta-muse-alternative).

## Related

- [Jobs-to-be-Done, explained](/academy/jobs-to-be-done-framework-explained) — the framework behind this piece
- [Jobs-to-be-Done examples](/academy/jobs-to-be-done-examples) — the hire/fire lens on well-known products
- [JTBD applied to Instagram Stories](/examples/jtbd-instagram-stories) — another Meta product through the same lens
- [JTBD vs personas](/compare/jtbd-vs-personas) — when to use which
- [The JTBD framework page](/frameworks/jtbd)

## Sources

- [Meta — "Introducing Muse: The World's First Personal AI Agent Built for Everyone" (Sept 8, 2026, updated Sept 30)](https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/)
- [Superpower Daily — "CNN tries Meta's Muse agent and finds useful plans but stalled purchases" (Sept 23, 2026), summarising CNN's hands-on test](https://superpowerdaily.com/posts/cnn-tries-meta-s-muse-agent-and-finds-useful-plans-but-stalled-purchases)
- [CNN — "Meta says its Muse AI agent can do things for you. I put it to the test" (Sept 23, 2026)](https://www.cnn.com/2026/09/23/tech/meta-muse-ai-agent)
- [Tech Insider — "Meta Launches Muse AI Agent: $20 and $100 Tiers" (downloads per Sensor Tower via the LA Times; tiers per Meta's help center)](https://tech-insider.org/meta-muse-personal-ai-agent-launch-2026/)
- [PPC Land — "Amazon blocks Meta's Muse AI agent from shopping on its site" (Sept 2026)](https://ppc.land/amazon-blocks-metas-muse-ai-agent-from-shopping-on-its-site/)
- [PYMNTS — "Shopify Brings Shop Pay Checkout Solution to Meta's Muse AI Agent" (Sept 22, 2026)](https://www.pymnts.com/commerce/ecommerce/2026/shopify-brings-shop-pay-checkout-solution-to-metas-muse-ai-agent/)
- [Engadget — "Meta's Muse agent has some new skills targeting small businesses" (Sept 29, 2026)](https://www.engadget.com/2271498/meta-now-has-a-version-of-muse-just-for-small-businesses/)

*Cover photo: [Paul Hanaoka on Unsplash](https://unsplash.com/photos/HbyYFFokvm0). Inline photo: [Glenn Carstens-Peters on Unsplash](https://unsplash.com/photos/RLw-UC03Gwc).*

---

### Welcome to the FrameworkList blog
URL: https://frameworklist.com/blog/welcome-to-the-blog
> Why we are starting a blog about thinking frameworks, and what to expect.

This is the first post on the FrameworkList blog. Over the next few months we will be writing about how to actually use the 100+ thinking frameworks in the catalog — not just what they are.

## What we will write about

Three flavors of posts:

- **Field reports** — how a specific team used a specific framework, what worked, what did not.
- **Comparisons** — when to reach for SWOT vs. PESTLE, OKRs vs. KPIs, RICE vs. ICE.
- **Anti-patterns** — the ways frameworks quietly mislead, and how to notice.

We are aiming for one post per week, written by [King Mark](/about/authors/king-mark). If a topic interests you, the [Academy](/academy) is where the deeper teaching pieces live; the blog is for opinions and field notes.

## What you can do today

Open the [framework library](/frameworks) and pick one you have not used in a while. Try it on the most ambiguous decision currently on your desk. We would love to hear what happened — reply to the welcome email or drop us a line.

> **Want the catalog on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=welcome-blog) ships 100+ strategy and decision frameworks with AI-assisted prompts. Free to start.

## Where to start

One of each flavor, so you can see what we mean:

- **Field report** — [Netflix's 2007 SWOT, reconstructed](/blog/how-netflix-used-swot-2007): an analysis that ended in a multi-billion-dollar capital allocation rather than a filed page
- **Comparison** — [RICE vs ICE](/compare/rice-vs-ice), [OKRs vs KPIs](/academy/okrs-vs-kpis-difference), [SWOT vs PESTLE](/compare/swot-vs-pestle)
- **Anti-pattern** — [Why most frameworks fail](/blog/why-most-frameworks-fail), and [how to pick one in the first place](/blog/framework-to-pick-a-framework)

If you'd rather start from a decision than a framework, the [Decision Center](/decisions/pivot-or-persevere) chains two or three of them into one founder-grade call.

---

### Why most frameworks fail (and how to use them anyway)
URL: https://frameworklist.com/blog/why-most-frameworks-fail
> A framework is a structured prompt for a conversation, not a machine that produces answers. Treat it as the second and it will disappoint you reliably.

I have watched a lot of teams adopt a framework, use it earnestly for two quarters, and then quietly abandon it. The frameworks are not the problem. The teams are not the problem. What's wrong is the unspoken expectation that a framework is supposed to *give you the answer*.

It isn't. A framework is a structured prompt for a conversation. It tells you what to think *about*, in what order, with what vocabulary. The conversation still has to happen, and the answer still has to come from the people in the room.

## What goes wrong

The most common failure pattern: the team picks a framework, fills it in, and stops. The grid is filled. The cells are populated. There is an artifact. The Notion page is "done." Then someone asks what the team is going to *do differently* as a result of the analysis, and there is silence.

This is the "filled grid, no decision" problem. It's the failure mode of every framework I've ever seen — SWOT, OKRs, RICE, Eisenhower, Premortem, all of them. The artifact gets confused with the outcome. The team feels productive because they completed the framework, but completing the framework was never the point.

The point was supposed to be the *conversation that the framework forced* — the one where someone said "actually, that threat in the bottom-right quadrant is the only thing that matters, and we should drop quadrant three entirely." That conversation didn't happen because nobody felt obligated to say what the filled grid implied. The grid was treated as the work.

## The thing frameworks actually do well

What frameworks are good at is **making it socially safe to say the unspoken thing**. In a SWOT, the threat quadrant exists, and therefore someone has to fill it. That fact gives an introverted team member permission to write down the threat that everyone has been quietly noticing but nobody has named. Without the framework, the conversation never lands there.

That's the lift. The framework provides a sanctioned slot for the awkward sentence. It moves the awkward sentence from "thing I might bring up if it feels right" to "thing the meeting's structure is asking for." That changes who is willing to say it.

If the team is already willing to say everything, the framework adds nothing. (You will sometimes see very high-trust founding teams skip frameworks entirely. They're not being undisciplined — they don't need the scaffolding, because the conversations they need already happen.)

If the team is reactive, polite, or seniority-bound, the framework can be the difference between a strategy decision and a feel-good meeting.

## How to use a framework so it works

Three habits, easy to state and hard to do:

**1. Always end the exercise with "so what."** When the framework is filled, ask out loud: "given what we just wrote down, what are we going to do differently next week?" If the answer is "nothing," the framework didn't help. That's fine — the failure to reach an action is information. Don't pretend you arrived somewhere you didn't.

**2. Time-box the filling and over-allocate the discussing.** The most common time allocation is 80% on filling cells, 20% on talking about what the cells mean. Invert it. Fifteen minutes filling, forty-five minutes talking.

**3. Re-run.** A framework's output is stale in 4–8 weeks. Anyone using a quarterly SWOT in week 11 of the quarter is using a museum piece. Schedule the re-run on the calendar before you put the artifact away.

## The other failure mode

The opposite failure: a team uses too many frameworks for too many decisions. Every meeting starts with picking a framework. Every email reply involves a 2×2. This is framework-cosplay — it looks like rigor and it produces nothing.

A framework should appear when a decision is **stuck** or **stakes-dependent enough to warrant the meta-conversation**. For routine work, just decide. The cost of a framework is real (60 minutes of three people's attention), and most decisions don't justify it.

The right rule of thumb: if you can defend the choice in two sentences without help, skip the framework. If you can't, that's the signal the framework is earning its overhead.

## The third failure mode: not knowing where it came from

There's a quieter one worth naming. A framework arrives with an origin story attached, the story turns out to be wrong, and the wrong story changes how people use the tool.

The [Ikigai diagram](/frameworks/ikigai) is the cleanest case. The four-circle Venn chart is captioned "ancient Japanese concept" almost everywhere it appears. It isn't one — it was drawn by a Spanish astrologer in 2011 as a diagram of *purpose*, and a blogger swapped the centre word to *ikigai* in 2014. The Japanese word, as Mieko Kamiya used it in 1966, describes a felt sense that life is worth living, with no conditions attached. The diagram describes an intersection you have to qualify for by being paid, skilled, and needed.

Those are different claims, and the mix-up has consequences: people run the chart, find an empty centre, and conclude something is wrong with their life — when all they've found is that four independent conditions rarely coincide. Same picture, and a totally different reading depending on whether you know the provenance.

The check is cheap. Before you rely on a framework, find out who built it and what question they built it to answer. If the answer is "nobody seems to know," that is itself a finding.

## Why we built this anyway

We have 100+ frameworks in the [library](/frameworks). Knowing that most teams will use most of them badly is part of why I think a library matters — and it's the same conviction behind [why we started this blog](/blog/welcome-to-the-blog) in the first place. The wrong assumption is that the right framework solves the problem; the right assumption is that the right *vocabulary* makes the conversation possible. A library of vocabulary is what a library of frameworks actually is.

Use them like that and they earn their keep. Use them as answer-vending machines and they will let you down, exactly as you described. (If the problem is just *which* one to pick, the [Strategy Framework Decision Map](/academy/strategy-framework-decision-map) lays out the choice by decision type, and [the framework I use to pick a framework](/blog/framework-to-pick-a-framework) is the two-minute triage I actually run.)

— King Mark

P.S. The framework I reach for most often, by far, is the [premortem](/academy/how-to-run-a-premortem). It produces actions more reliably than any other. Worth knowing well.

> **Want frameworks that stay attached to a decision?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=why-frameworks-fail-blog) keeps every canvas next to the choice it was made for. Free to start.

---

## Examples

### Alphabet BCG Matrix 2026 (Before the Q2 Earnings)
URL: https://frameworklist.com/examples/alphabet-bcg-matrix-2026
> A worked BCG Growth-Share Matrix of Alphabet's portfolio going into its July 22, 2026 Q2 earnings — Search as the Cash Cow under AI siege, Google Cloud as the Star, Waymo and consumer Gemini as Question Marks, and what the $180–190B capex must prove.

On **July 22, 2026, Alphabet reports Q2 earnings** — the first megacap read of a season the whole market is framing around one question: is Big Tech's AI capital spending starting to pay off? Amazon, Microsoft, Alphabet, and Meta have collectively committed up to ~$725B in 2026 capex, and Alphabet alone raised its full-year guidance to **$180–190B**. Numbers that large stop being an expense line and start being a portfolio bet. The cleanest lens on that bet is the one the [BCG Growth-Share Matrix](/frameworks/bcg) was built for: segment by segment, which units generate the cash, which units consume it, and is the money moving the portfolio in the right direction?

## Position being analyzed

Going into Q2, Alphabet is a company throwing off enormous cash from one mature engine and pouring it into three high-growth bets at once. Here is the portfolio in its most recent reported quarter (Q1 2026):

| Metric (Q1 2026) | Value | Direction vs. 12 months ago |
|---|---|---|
| Consolidated revenue | $109.9B | ▲ up 22% |
| Google Search & other ads | $60.4B | ▲ up 19% |
| YouTube ads | $9.9B | ▲ up 11% |
| Google Cloud | $20B | ▲ up 63% |
| Cloud backlog | ~$462B | ▲ nearly doubled sequentially |
| Other Bets operating loss | ~$2.1B (quarter) | ▼ wider (FY2025 loss $7.51B) |
| FY2026 capex guidance | $180–190B | ▲ raised from $175–185B |

The strategic question the matrix addresses: is the portfolio balanced so the Cash Cow can fund the growth units long enough for the Question Marks to become Stars — and is the Cash Cow itself safe?

## The four quadrants

| Quadrant | Definition | Alphabet 2026 entries |
|---|---|---|
| **Stars** | High share, high growth | Google Cloud; YouTube (secondary, maturing) |
| **Cash Cows** | High share, low market growth | Google Search & Advertising, Android/Play/Maps |
| **Question Marks** | Low/uncertain share, high growth | Waymo, consumer Gemini, DeepMind science (Isomorphic) |
| **Dogs** | Low share, low growth | Legacy Other Bets (Verily-adjacent, discontinued moonshots) |

## Cash Cow: Google Search & Advertising

Search advertising is the [Cash Cow](/glossary/cash-cow), and after every reorg and rebrand it is still the reason the rest of the portfolio can exist. Three facts fix its position:

1. **Dominant share** — Google holds well above 90% of global search, the definition of a high-relative-share position.
2. **Cash generation** — $60.4B in a single quarter (Q1 2026), the overwhelming majority of Alphabet's operating cash flow, funding Cloud's build-out and Other Bets' losses.
3. **Maturing market** — the search-advertising *market* grows in the low-to-mid single digits; Alphabet's 19% comes from share gains, pricing, and early AI monetization layered on a mature base, not from market expansion.

The BCG discipline question for a Cash Cow is not "is it growing?" but "is management harvesting it without starving it — and is anything threatening the herd?" And here is where Alphabet's matrix is more interesting than Nvidia's or SpaceX's: **this is a Cash Cow under siege.** Gemini reached ~900M monthly active users and ChatGPT crossed 1B, and AI Mode inside Search itself crossed 1B users — the query, the atomic unit of the cash cow, is being contested for the first time in two decades. Alphabet's counter is to fuse Gemini *into* Search (AI Overviews reach 2B+ users monthly) so the cow defends itself. Whether that defense holds is the single most important thing the July 22 report will signal.

## Stars: Google Cloud

Google Cloud is the unambiguous Star. It grew **63% to $20B** in Q1 2026, its backlog nearly doubled to ~$462B, and AI-solution revenue rose ~800% — high market growth *and* a large, rising share of a market it is now firmly third in and closing. Crucially, Cloud is where the capex most directly lands: the same data-center and TPU spending that inflates the $180–190B guidance is the thing selling out Cloud capacity (Alphabet has repeatedly said demand is running ahead of supply). A Star is supposed to consume cash while it grows into its lead; Cloud is doing exactly that, and it is the segment whose economics most cleanly justify the build-out.

YouTube ($9.9B ad revenue, +11%) is a secondary Star drifting toward Cash Cow — dominant share, but growth decelerating into the low teens as the format matures.

## Question Marks: Waymo and consumer Gemini

This is where the capex bet gets speculative and where BCG earns its keep.

**Waymo** is the textbook Question Mark: an enormous, high-growth market (autonomous transport) where Alphabet's *share of rides* is still negligible, funded through the loss-making Other Bets segment ($7.51B loss in 2025, up from $4.44B in 2024). But it is scaling on a steep curve — **500,000 paid rides a week across 10+ U.S. cities** as of early 2026, a target of roughly **1M rides a week by year-end**, expansion into ten new metros plus **London** as a first international market, and a **$126B** private valuation after its February 2026 round. BCG's rule for a Question Mark is binary — commit fully or divest — and Alphabet has committed.

**Consumer Gemini** (the standalone assistant, distinct from Gemini-in-Search) is the other Question Mark: 900M MAU is high growth, but leadership of the consumer-AI market is genuinely contested against a larger ChatGPT. High growth, uncertain share — the Question Mark box exactly.

## Dogs: the disciplined, mostly-empty corner

Alphabet's Dogs quadrant is thin, and that is a good sign. The company has a long record of *killing* weak lines — Stadia, Google+, dozens of graveyard projects — rather than nursing them, and the 2015 Alphabet reorg exists partly to make loss-making bets visible enough to cut. What remains in "Other Bets" is better read as early Question Marks (Isomorphic's drug discovery, Verily-adjacent health) than as true Dogs. The absence of a bloated Dogs quadrant is a quiet marker of portfolio discipline most conglomerates lack.

## The Capex-to-Quadrant Test

Here is the named diagnostic the matrix produces — the thing worth quoting going into July 22. A snapshot of quadrants is static; what matters with a $180–190B capex bill is whether the money is *moving* each unit up the matrix. For each portfolio unit, ask: **what is the capex buying, and what single Q2 2026 metric would confirm the unit is climbing rather than stalling?**

| Portfolio unit | Current quadrant | What the 2026 capex is buying | The Q2 metric that proves it's working |
|---|---|---|---|
| **Google Cloud** | Star | Data-center + TPU capacity to clear the $462B backlog | Cloud revenue growth holding ≥40% *and* operating margin expanding |
| **Search & Ads** | Cash Cow (under siege) | Gemini-in-Search to defend the query | Search ad revenue still growing double digits — no click erosion |
| **Waymo** | Question Mark | Fleet + city expansion toward 1M rides/week | Rides/week trajectory + a narrowing Other Bets loss per ride |
| **Consumer Gemini** | Question Mark | Model + inference compute to win share vs ChatGPT | MAU growth *and* evidence of paid conversion, not just free reach |

The test's discipline: capex is only rational if it moves a unit toward a higher-value quadrant. Spending that keeps a Cash Cow from being disrupted (Search) is defensive and necessary; spending that turns a Question Mark into a Star (Cloud, already done; Waymo, in progress) is the offensive case for the whole $725B industry wager. The failure mode the test surfaces is spending that merely holds a Question Mark in place — high burn, no quadrant movement. That is the line item to watch on July 22.

## Key takeaway

The BCG matrix on Alphabet in mid-2026 says this is a **well-balanced portfolio with a single concentrated risk**: one Cash Cow funds everything, and it is precisely the unit AI-native search is contesting. Cloud is a genuine Star that the capex clearly justifies; Waymo is a credible, fully-funded Question Mark on a steep scaling curve; the Dogs quadrant is disciplined and thin. The model's warning is not imbalance — it's *dependency and timing*. If Gemini-in-Search defends the query, the flywheel spins and the Question Marks get the capital they need to become Stars. If AI answers erode Search monetization faster than Alphabet replaces it, the cash thins at the worst possible moment. Re-run this matrix the morning after July 22 — the Q2 print is the next data point on which way the dependency breaks.

## Want to go deeper

New to the model? Read [BCG Matrix Analysis: The Four Quadrants Explained](/academy/bcg-matrix-analysis-explained) for the full methodology and the Cash-Cow Dependency Test — which Alphabet's Search-funds-everything structure stresses harder than most portfolios. For the contrast case, the [Nvidia BCG Matrix Analysis 2026](/examples/nvidia-bcg-matrix) shows a portfolio with one Star so dominant it tips the matrix out of balance — the mirror image of Alphabet's one-Cash-Cow dependency. And the [SpaceX BCG Matrix Analysis 2026](/examples/spacex-bcg-matrix-2026) frames the same four quadrants as a funding *flywheel*, the pattern Alphabet is trying to keep spinning. To see how a portfolio diagnosis hands off to a growth prescription, read [Ansoff Matrix vs BCG Matrix](/compare/ansoff-matrix-vs-bcg-matrix); for when four boxes aren't enough, [BCG Matrix vs GE-McKinsey Matrix](/compare/bcg-matrix-vs-ge-mckinsey-matrix). To run a BCG on a company you care about, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) walks you through all four quadrants with AI assistance.

---

### Amazon PESTEL Analysis 2026
URL: https://frameworklist.com/examples/amazon-pestel-analysis-2026
> A working PESTEL analysis of Amazon in 2026 — antitrust pressure, AWS capex peaking, AI shopping, robotics, climate compliance, and the de minimis loophole closing. Six macro forces shaping the next 24 months.

![Photograph of a data center server hall with blue lighting](https://images.unsplash.com/photo-1558494949-ef010cbdcc31?auto=format&fit=crop&w=1600&q=80)

Amazon in 2026 is three businesses pretending to be one company. The retail marketplace is a low-margin volume engine being squeezed from below by Temu and Shein and from above by Walmart's online grocery push. AWS is a high-margin engine that's slowing as its hyperscaler customers build their own silicon. Advertising is the fastest-growing segment by margin contribution and the one almost no one talks about. A single framework that picks one of these as "the" Amazon misses the company.

PESTEL is the right tool for that. It's a macro-environment scan, not an industry analysis, and it forces you to score six forces — Political, Economic, Social, Technological, Environmental, Legal — against the company as a whole. Run cleanly on Amazon in May 2026, it reveals that five of the six forces are tightening while only one (Technological) is unambiguously pushing in Amazon's favor.

### Prefer to watch or listen?

<YouTube id="hal2zbJ4JMk" title="Amazon's 5-vs-1 Problem: A 2026 PESTEL Analysis" />

<Spotify id="46EkTuhUM1pDp3BszdnPLg" title="Amazon's 5-vs-1 Problem: A 2026 PESTEL Analysis — Framework podcast episode" />

## Position being analyzed

Mid-2026: the FTC antitrust trial is in pre-trial motions, the EU Digital Markets Act has been in enforcement for two years, AWS just had its slowest growth quarter since 2019, Amazon Haul is six months into its Temu-counter launch, and the Anthropic partnership has committed Amazon to a multi-year Trainium silicon roadmap. The strategic question PESTEL helps with: which macro force is most likely to bend the 2027–2028 trajectory?

| Metric | Value | Direction vs. 12 months ago |
|---|---|---|
| AWS Q1 2026 revenue / YoY growth | ~$29B / +17% | Down from +20% |
| AWS 2026 capex commitment | $100–110B | Up from ~$75B |
| Retail operating margin (TTM) | ~6.2% | Up from ~5.0% |
| Advertising revenue run-rate | ~$60B annualized | Up from ~$50B |
| Active warehouse robots (fulfillment fleet) | 950,000+ | Up from ~750,000 |
| EU DMA fines paid + reserved (cumulative) | ~€1.2B | Up from ~€400M |
| FTC antitrust case stage | Pre-trial motions, trial set 2027 | Advanced from discovery |

## PESTEL scorecard for Amazon, May 2026

| Force | Direction for Amazon | Strength | What flips it |
|---|---|---|---|
| **Political** | ❌ Hurting | High | FTC settlement vs. structural breakup |
| **Economic** | ❌ Hurting | Medium | Fed rate cuts + capex cycle peak |
| **Social** | ❌ Hurting | Medium-High | Labor union outcomes + Temu fatigue |
| **Technological** | ✅ Helping | High | Trainium reaches H100-class price/performance |
| **Environmental** | ❌ Hurting | Rising | Grid + water permits in VA / OR / IE |
| **Legal** | ❌ Hurting | High & continuous | DMA structural-separation order |

Five red, one green. The green is the only one Amazon controls. The reds are the operating environment.

## Political — the regulatory pincer

The political force on Amazon in 2026 is a pincer: the US side is FTC v. Amazon (filed 2023, pre-trial 2026, trial 2027), with the agency seeking structural remedies around marketplace self-preferencing and Buy Box practices. The EU side is the Digital Markets Act, under which Amazon was designated a gatekeeper in 2023 and which has been in active enforcement since 2024. The cumulative EU fines and reserves are now ~€1.2B and growing; the FTC trial is binary but distant.

A second political vector is trade. The Trump administration's 2025 closure of the de minimis loophole (the rule that allowed cross-border parcels under $800 to clear without duty) raised landed costs for Temu, Shein, and Amazon's own low-price Haul service. The naive read is that this helps Amazon by hurting Temu; the PESTEL read is that it raises the cost basis for the entire low-price marketplace and forces Amazon's third-party seller base to absorb or pass on the cost. India's CCI continues to investigate marketplace structure, and the UK CMA's cloud market review concluded with remedies that constrain AWS's egress fee practice.

## Economic — capex peak meets growth slowdown

Two coupled economic forces. The first: AWS growth has decelerated from the high-20s percent range in 2022–23 to ~17% in Q1 2026, while the hyperscaler capex bill has gone the other direction. Amazon committed to $100–110B in 2026 capex, most of it for AI infrastructure, against a cloud business growing in the high-teens. The cash flow math works because the retail business is finally profitable and advertising is throwing off ~$60B at very high incremental margins — but it works on those two segments funding the AWS bet, not on AWS funding itself.

The second economic force is consumer. US consumer spending in 2025–26 has been mixed, with Prime membership growth saturating domestically and international Prime growth carrying the headline number. Operating margin recovery in retail (from ~3% in 2023 to ~6% in 2025) was the bull story; the next leg requires either continued cost discipline or volume growth, and neither is guaranteed in a Temu/Shein price war.

## Social — labor, returns to office, marketplace fatigue

Three social pressures, two organizational and one external.

**Labor.** The Amazon Labor Union won recognition at the Staten Island JFK8 warehouse in 2022; the contract negotiation has been protracted, with ALU-affiliated organizing now active at facilities in Albany, Garner (NC), and Schertz (TX). The NLRB caseload involving Amazon has expanded. The 2025 mandate of five-day return-to-office for corporate employees produced visible attrition at the senior IC and L7 levels.

**Marketplace trust.** Reviews fraud, counterfeit product enforcement, and the proliferation of low-quality private-label and third-party listings have driven a measurable customer perception decline (ACSI scores). Amazon Haul launched in 2024 as the Temu counter and is itself a contributor to the perception problem — cheap, fast, lightly curated.

**Ethical consumerism.** Climate concern + labor concern + monopoly concern combine into a "switch from Amazon" sentiment that's hard to measure but persistent in survey data, particularly among the 25–34 cohort.

## Technological — the one force pushing in Amazon's favor

This is the green cell on the scorecard, and it's earned.

**AWS Trainium silicon.** The Anthropic partnership (deepened in 2025) commits significant Anthropic training workload to AWS Trainium 2, which is Amazon's strongest demonstration that custom silicon can compete with Nvidia on the workloads that matter. If Trainium 3 reaches H100-class price/performance, the AWS gross-margin equation changes materially.

**Generative AI shopping.** Rufus (Amazon's AI shopping assistant) has been rolled out broadly in 2025–26 and is the first AI shopping interface with the catalog scale to actually work. Conversion lift data is not public but the engagement signal is meaningful.

**Fulfillment robotics.** Sequoia, Proteus, and the 2025 humanoid pilots (Digit) have pushed the active robot fleet past 950,000 units. Each unit of automation compresses retail's cost-to-serve and is part of why operating margin has held up against wage pressure.

**Amazon Leo (formerly Project Kuiper).** The satellite broadband constellation is not yet in commercial service. Amazon's Q2 2026 release put it at nearly 400 satellites, "enough to begin initial satellite internet service this year", and the FCC waived its July 2026 half-constellation milestone after Amazon cited a rocket shortage. Leo is a Diversification play in Ansoff terms. In PESTEL terms it's a Technological positive that is still being built, and our [Amazon VRIO analysis](/examples/amazon-vrio-analysis-2026#the-rivals-invoice) explains why launch capacity, not money, sets its pace.

The Technological force does not by itself outweigh the other five. It does mean that Amazon enters the political and legal headwinds with a thicker product moat than competitors.

## Environmental — the constraint that bites the data center plan

The Climate Pledge commitment (net-zero by 2040) is on track in scope 1+2 emissions, primarily through renewable-energy purchases at scale. The harder story is in scope 3 and in the physical-constraint dimension of the data center build-out.

AWS's 2026 capex is largely data centers; data centers need power, water, and permits. Virginia (Loudoun County), Oregon (Umatilla County), and Ireland (Dublin) — three of Amazon's largest data center clusters — are all in active conflict with local utilities or municipalities over additional grid capacity, water rights, or building moratoria. The Environmental force is starting to act as a Political and Legal force, which is the kind of coupling PESTEL is designed to surface.

## Legal — DMA enforcement is the continuous story

The FTC case is binary and slow. The DMA is continuous and immediate. As a designated gatekeeper, Amazon must comply with self-preferencing prohibitions, interoperability requirements, and data-use restrictions across the marketplace and Marketplace-affiliated services. Each year brings new compliance reporting, new audit cycles, and new fines for shortfalls. Cumulative DMA-related expense is now ~€1.2B and structurally rising.

Two other legal vectors: privacy (state-level US laws plus EU GDPR follow-through audits on Amazon Advertising's ad-targeting practices), and worker classification (delivery service partner driver classification lawsuits in California, Washington, and the EU). None individually is a quarter-mover; collectively they are part of the rising legal-expense base.

## Key takeaway

PESTEL on Amazon in 2026 reveals a five-versus-one asymmetry. Five forces — Political, Economic, Social, Environmental, Legal — are all tightening at the same time. Only Technological is unambiguously helping. The framework's discipline is to refuse the "but AWS is a moat" reflex and force the question: if five of six macro forces are pushing the wrong way, the company's strategic margin for error is small even if the moat holds. The next 24 months will be decided not by AWS Bedrock product velocity but by which of those five forces bends Amazon's operating model first — a DMA structural remedy, a Loudoun County permit denial, a Trainium roadmap miss, or a Temu-induced marketplace margin collapse. PESTEL doesn't predict which; it forces you to track all of them rather than only the one that's currently in the news cycle.

## Want to go deeper

New to the method? Start with [How to Do a PESTEL Analysis](/academy/how-to-do-a-pestel-analysis) — the six factors, a 6-step process, and the Materiality Filter for ranking forces. Or read more about the [PESTEL framework](/frameworks/pestel) and browse other [strategy framework examples](/examples). For PESTEL applied to a market rather than a single company, see the [World Cup 2026 PESTEL analysis](/examples/world-cup-2026-pestel-analysis) — the six forces scanned across a three-country host economy. For a case where one force dominates all the others, see the [Nike PESTEL analysis (2026)](/examples/nike-pestel-analysis-2026) — how a single tariff shock cascades through the whole grid. For the industry view of the AWS / Nvidia / hyperscaler story, see our [AI chip industry Five Forces breakdown](/blog/ai-chip-five-forces-nvidia-5-trillion). For Amazon's growth-strategy lens, the [Ansoff Matrix](/frameworks/ansoff) is the natural pairing — Kuiper, Trainium, and Anthropic each map onto a different Ansoff quadrant.

To run a PESTEL analysis on a company you're tracking, [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each of the six forces.

For Amazon's SWOT counterpart, see our sister site [SWOTPal's Amazon SWOT analysis](https://swotpal.com/examples/amazon?utm_source=frameworklist&utm_medium=referral&utm_campaign=pestel-amazon) — a dedicated AI SWOT tool, free for the basic workflow.

*Cover photo: [Taylor Vick on Unsplash](https://unsplash.com/photos/M5tzZtFCOfs).*

---

### Amazon VRIO Analysis 2026: The Rival's Invoice
URL: https://frameworklist.com/examples/amazon-vrio-analysis-2026
> A VRIO analysis of Amazon in 2026. Seven resources scored on Q2 numbers, and why Amazon Leo must buy SpaceX rockets to catch up with Starlink.

In January 2026 Amazon told the FCC it could not put about 1,616 Amazon Leo satellites in orbit by its 30 July deadline, and blamed a "near-term shortage of available rockets." In the same month it disclosed that it had bought ten more Falcon 9 launches [from SpaceX](https://www.cnbc.com/2026/01/30/amazon-asks-fcc-to-extend-satellite-limit-as-it-buys-more-spacex-rides.html), the company whose Starlink network Leo exists to compete with. That makes October 2026 a useful moment to run a VRIO analysis of Amazon. Amazon is usually the incumbent that rivals cannot copy, and here it is the one doing the copying, so the analysis can look at imitation from both sides.

VRIO scores a company's resources one by one. For each it asks whether the resource is **V**aluable, **R**are, costly to **I**mitate, and whether the firm is **O**rganized to capture its value. Most Amazon VRIO write-ups answer the imitability question by assertion ("competitors would struggle to match Amazon's scale"). This page uses a checkable signal instead: who has to buy from whom. That is the anchor, [The Rival's Invoice](#the-rivals-invoice).

## Position being analyzed

The numbers below come from Amazon's [Q2 2026 results](https://www.sec.gov/Archives/edgar/data/0001018724/000101872426000024/amzn-20260630xex991.htm) unless noted. Amazon reports Q3 in late October 2026.

| Metric | Q2 2026 | vs Q2 2025 |
|---|---|---|
| Net sales | $200.6bn | +20% (from $167.7bn) |
| Operating income | $27.5bn | +43% (from $19.2bn) |
| North America sales / operating income | $116.2bn / $9.1bn | +16% / from $7.5bn |
| International sales / operating income | $42.2bn / $1.7bn | +15% / from $1.5bn |
| AWS sales / operating income | $42.2bn / $16.6bn | +37% (fastest in 18 quarters) / from $10.2bn |
| Advertising services revenue | $19.8bn | Reported growth varies by source |
| Property and equipment purchases, trailing 12 months | $173.0bn gross | from $107.7bn |
| Free cash flow, trailing 12 months | **−$7.6bn** | from +$18.2bn |
| Non-operating income, mostly from the Anthropic stake | $53.4bn pre-tax | One quarter |
| Q3 2026 guidance | Sales $197–202bn, operating income $22.5–26.5bn | +9% to 12% sales growth |

The Amazon Leo timeline, from Amazon's filings and the [FCC waiver](https://www.benton.org/headlines/fcc-grants-kuipers-request-extend-or-waive-interim-milestone):

| Date | Event |
|---|---|
| Jul 2020 | Amazon says it will invest $10bn in Project Kuiper, a 3,236-satellite constellation |
| Dec 2023 | Buys 3 Falcon 9 launches from SpaceX, on top of more than $10bn of launch contracts with ULA, Arianespace and Blue Origin |
| 12 Nov 2025 | Project Kuiper renamed Amazon Leo |
| Jan 2026 | Asks the FCC for 24 more months on the half-constellation milestone. Discloses 10 more Falcon 9 and 12 more New Glenn launches |
| Apr 2026 | Agrees to buy Globalstar for [$11.57bn](https://www.fierce-network.com/wireless/amazon-acquire-globalstar-1157-billion), with an Apple agreement to move iPhone and Apple Watch satellite features to Amazon Leo. Closing expected in 2027 |
| 5 Jun 2026 | FCC waives the July 2026 milestone. Satellites launched after it lose spectrum priority until 1,618 are launched, or until 30 Oct 2027 if Amazon certifies 1,618 have been built |
| Q2 2026 | Nearly 400 satellites in orbit, "enough to begin initial satellite internet service this year" |

## VRIO applied, resource by resource

### 1. Fulfillment and delivery network: sustained advantage ✅

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | It is what makes the North American store profitable: $9.1bn of Q2 operating income on $116.2bn of sales, up from $7.5bn a year earlier |
| **Rare** | Yes | No other US retailer runs a parcel network of comparable density that it also sells to third-party sellers |
| **Inimitable** | Yes | The network was built over two decades of capex and is tied to warehouse locations near population centres. A rival with money still has to buy the land and wait for permits |
| **Organized** | Yes | Fulfillment by Amazon and Prime turn the network into fees and retention, not just lower costs |

### 2. AWS at scale: sustained advantage ✅

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | $42.2bn of revenue and $16.6bn of operating income in one quarter: a 39% margin, and more than half of Amazon's operating income |
| **Rare** | Yes | Three providers operate at this scale, and AWS is the largest |
| **Inimitable** | Yes | See The Rival's Invoice below. Rivals of Amazon's other businesses still buy from it |
| **Organized** | Yes | It is reported as its own segment, and AI workloads come in through Bedrock and Trainium |

### 3. Trainium custom silicon: temporary advantage ⏳

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | The chips business passed a $25bn annual run rate in Q2, and Anthropic and OpenAI have made multi-year, multi-gigawatt commitments |
| **Rare** | Yes | Only two hyperscalers sell in-house AI training silicon at this volume: Amazon and Google |
| **Inimitable** | No | Google's TPU shows it can be done. Microsoft and Meta are building their own chips |
| **Organized** | Yes | It is sold through AWS, so every chip comes with a cloud contract |

### 4. Advertising on first-party purchase data: sustained advantage ✅

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | $19.8bn of advertising revenue in Q2 2026 |
| **Rare** | Yes | Google and Meta know what people search for and look at. Amazon also knows what they bought, and it shows the ad on the page where they buy |
| **Inimitable** | Yes | The data comes from the store, so copying it means building the store first |
| **Organized** | Yes | Sponsored products sit inside search results and Prime Video carries ads by default |

### 5. The capital budget: competitive parity ⚖️

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | $173bn of property and equipment in 12 months, mostly for AI |
| **Rare** | No | Microsoft, Alphabet and Meta are each spending on the same order of magnitude |
| **Inimitable** | — | Not reached |
| **Organized** | — | Not reached |

A budget that every rival also has is the cost of staying in the race, not an advantage. And it has a price: trailing free cash flow went from +$18.2bn to **−$7.6bn**.

### 6. The Anthropic stake: owned, not operated ⚠️

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | It produced most of $53.4bn of pre-tax non-operating income in Q2 |
| **Rare** | Yes | Only Amazon and Google own large stakes in Anthropic |
| **Inimitable** | Yes | The stake can't be bought again at the same price |
| **Organized** | Partly | The gain appears below the operating line. Amazon captures the operating value only where Anthropic's commitments run on AWS and Trainium |

VRIO's fourth question exists for this case. A resource can pass the first three tests and still be an unused advantage if the company isn't organized to turn it into operating profit. Most of what the stake earned in Q2 is a mark-to-market gain, not AWS revenue.

### 7. Amazon Leo: competitive disadvantage ❌

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | Broadband for places without fibre, plus the Apple satellite-feature deal that comes with Globalstar |
| **Rare** | No | Starlink already has about 26 times as many satellites in orbit and more than 12 million subscribers |
| **Inimitable** | — | Not reached: Amazon is the imitator |
| **Organized** | Yes | Amazon is spending and launching heavily, and Globalstar adds spectrum and an anchor customer |

### Scorecard

| Resource | V | R | I | O | Result |
|---|---|---|---|---|---|
| Fulfillment and delivery network | ✅ | ✅ | ✅ | ✅ | Sustained advantage |
| AWS at scale | ✅ | ✅ | ✅ | ✅ | Sustained advantage |
| First-party ad data | ✅ | ✅ | ✅ | ✅ | Sustained advantage |
| Trainium silicon | ✅ | ✅ | ❌ | ✅ | Temporary advantage |
| Capital budget | ✅ | ❌ | — | — | Competitive parity |
| Anthropic stake | ✅ | ✅ | ✅ | Partly | Unused advantage |
| Amazon Leo | ✅ | ❌ | — | ✅ | **Competitive disadvantage** |

## The Rival's Invoice

VRIO's third question, "is it costly to imitate?", is usually answered with adjectives. Amazon in 2026 offers a better signal, because it sits on both sides of the same supplier relationship.

> **The Rival's Invoice:** if copying a rival's resource requires buying an input from that rival, the resource is costly to imitate for a reason money cannot fix, because the rival controls the price and the pace of your catch-up. Read in reverse, if rivals have to buy an input from you, that input is very likely your inimitable resource.

| Who pays whom | The input | What it shows |
|---|---|---|
| **Amazon pays SpaceX** | 3 Falcon 9 launches bought in Dec 2023, 10 more disclosed in Jan 2026 | Launch capacity is the input under Starlink that Amazon can't build on its schedule. Leo is at a disadvantage |
| **OpenAI pays AWS** | A [$38bn, seven-year infrastructure agreement](https://www.aboutamazon.com/news/aws/aws-open-ai-workloads-compute-infrastructure) | OpenAI is the main partner of Microsoft, AWS's largest cloud rival, and still buys AWS capacity. AWS is the advantage |
| **Netflix pays AWS** | Its streaming runs on AWS | Netflix competes with Prime Video and still rents Amazon's infrastructure. See our [Netflix Five Forces](/examples/netflix-porters-five-forces) on why that gives Amazon some leverage |
| **Apple will pay Amazon Leo** | iPhone and Apple Watch satellite features, under the Globalstar agreement | Amazon used an $11.57bn acquisition to get an invoice it can send, not just one it pays |

The SpaceX row is the one that matters for Leo. Amazon has the money: it pledged $10bn in 2020, its launch contracts alone exceed that, and Globalstar adds $11.57bn. It still missed its FCC milestone, and its own filing named rockets, not money, as the reason. The table below puts the gap in numbers.

| | Amazon Leo | Starlink |
|---|---|---|
| Satellites in orbit | Nearly 400 (Q2 2026) | About 10,400 (June 2026) |
| Subscribers | Initial service due to start in 2026 | More than 12 million (June 2026) |
| Who launches them | ULA, Arianespace, Blue Origin, **and SpaceX** | SpaceX |
| FCC half-constellation milestone (about 1,616 by 30 Jul 2026) | Missed, waived on 5 Jun 2026 | Not applicable |

This is related to the [Auction Test](/examples/netflix-vrio-analysis-2026#the-auction-test) on our Netflix page, but it reads a different number. The Auction Test reads the price a firm refused to pay for a resource. The Rival's Invoice reads who a firm has to pay to get one. Netflix decided it could substitute for what it was bidding on. Amazon can't substitute for launch capacity. It can only wait for Blue Origin to reach cadence or keep paying SpaceX.

### Pre-registered: the launch rate, not the budget, sets Leo's pace

| | |
|---|---|
| **Placement** | Amazon Leo stays a competitive disadvantage while launch capacity, not money, is the constraint |
| **Prediction** | Amazon Leo has launched **fewer than 1,618** satellites by 30 October 2027, so it regains spectrum priority by certifying satellites as built, not as launched |
| **Falsifier** | 1,618 or more Leo satellites launched by 30 October 2027 |
| **Scored on** | Amazon's Q3 2027 release and the public Leo launch record (late October 2027) |

## Where this misleads

- **Buying from a rival is not always a weakness.** Apple bought displays from Samsung for years without losing anything that mattered. The test only bites when the input is scarce, and launch capacity was scarce: Amazon's own FCC filing said so.
- **The invoice can shrink.** Blue Origin is owned by Jeff Bezos, and Amazon has booked 12 more New Glenn launches. If New Glenn reaches a high launch rate, Amazon stops depending on SpaceX and the Leo row could move to parity. The score above is a snapshot.
- **Paying AWS doesn't mean AWS can't be copied.** OpenAI also buys from Microsoft and others. The AWS row shows that AWS is hard to avoid, not that it is the only option.

## Signals to watch

| Signal | Resource | Date |
|---|---|---|
| AWS growth vs Q2's 37%, and Q3 operating income vs the $22.5–26.5bn guidance | AWS, capital budget | Q3 2026 release, late Oct 2026 |
| Trailing free cash flow turning positive again | Capital budget | Each quarterly release |
| Amazon Leo commercial service starting, and first paying customers | Amazon Leo | Promised for 2026 |
| New Glenn launches carrying Leo satellites | Amazon Leo (fewer invoices to SpaceX) | 2026–27 |
| FCC approval and closing of Globalstar | Amazon Leo | Expected 2027 |
| Leo satellites launched by 30 Oct 2027 | The pre-registered prediction | 30 Oct 2027 |

## Key takeaway

VRIO on Amazon in 2026 finds three moats (fulfillment, AWS and first-party ad data), a capital budget that has become the cost of entry rather than an advantage, and one area where Amazon is the imitator. Amazon Leo is not short of money: Amazon's launch contracts alone exceed the $10bn it pledged in 2020, and Globalstar adds $11.57bn. It is short of rockets, and some of those rockets come from the rival it is chasing. **When a VRIO analysis can't settle imitability by argument, follow the invoices.** A resource your rivals have to pay you for is hard to imitate. A resource you can only build by paying a rival is one you are still behind on.

> Want to run VRIO on your own company's resources? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=amazon-vrio-example) walks the four questions with AI assistance.

## Related

- [VRIO framework](/frameworks/vrio): the four questions and how to score them
- [Netflix VRIO Analysis 2026](/examples/netflix-vrio-analysis-2026): The Auction Test, which reads the price a company refused to pay for a resource
- [Tesla VRIO Analysis 2026](/examples/tesla-vrio-analysis-2026): the same framework on a company whose moats are industrial
- [Amazon PESTEL Analysis 2026](/examples/amazon-pestel-analysis-2026): the macro forces around the same company
- [SpaceX BCG Matrix 2026](/examples/spacex-bcg-matrix-2026): Starlink seen from SpaceX's side

If you came here looking for a SWOT, our sister site [SWOTPal has an Amazon SWOT analysis](https://swotpal.com/examples/amazon?utm_source=frameworklist&utm_medium=referral&utm_campaign=vrio-amazon).

---

### Ansoff Matrix Example: The Growth Move That Isn't on the Grid
URL: https://frameworklist.com/examples/ansoff-37signals-subtraction
> In 2014 Jason Fried killed every product but Basecamp and renamed the company. The Ansoff matrix has four cells and none of them is the one he chose.

![Photograph of a single wooden chair alone in an empty room, lit by low sun through a window](https://images.unsplash.com/photo-1632429966927-12c46c16f130?auto=format&fit=crop&w=1600&q=80)

The [Ansoff matrix](/frameworks/ansoff) is usually taught as a menu. Four cells, pick one, each with a risk rating attached. It is a good menu, and the site has worked it on [Apple](/examples/apple-ansoff-matrix-2026), [Nvidia](/examples/nvidia-ansoff-matrix-2026) and [Tesla](/examples/tesla-ansoff-matrix).

This is a Decision Replay, so the question is different: take a real, dated, publicly announced growth decision with a known outcome, run the matrix on it, and see whether the matrix could have produced the answer.

Here it could not — and not because the answer was hard. Because **the answer is not on the grid.**

## The decision

On **5 February 2014**, Basecamp's tenth birthday, Jason Fried announced that 37signals would sell, shut down or spin off every product it made except Basecamp, and rename the entire company after the survivor. Highrise (CRM), Campfire (chat) and Backpack went; Ta-da List and Writeboard had already been in maintenance mode since 2012.

His stated reason at the time:

> "We do our best work when we're all focused on one thing."

Eight years later he described the step himself, in a post announcing that they were undoing the name:

> "About 8 years ago in 2014 we decided to go all-in and focus on just one product moving forward. That product was Basecamp, our biggest hit. To eliminate any doubt about our newfound focus, we renamed the entire company."

## What was on the table in January 2014

| | |
|---|---|
| Core product | **Basecamp** — ten years old, market-leading in SMB project management |
| Other live products | Highrise (CRM), Campfire (chat), Backpack |
| Already sunset | Ta-da List, Writeboard (maintenance mode since 2012) |
| Market | Small businesses and teams — broadly the *same* market for every product |
| Ownership | Private, profitable, no outside growth mandate |
| Constraint Fried names | Attention. Not capital, not market size |

Note the third row, because it determines where everything sits on the grid: Highrise, Campfire and Backpack were **new products sold into the existing market**. That is textbook **product development**. 37signals in early 2014 was a company already occupying two Ansoff cells at once.

## Running the matrix

| Cell | What it would have meant in 2014 | Ansoff's conventional read |
|---|---|---|
| **Market penetration** — Basecamp, existing market | Sell more Basecamp to more small teams | Lowest risk. Do this first. |
| **Product development** — new products, existing market | Keep building Highrise, Campfire, Backpack | Already in flight |
| **Market development** — Basecamp, new markets | Take Basecamp upmarket to enterprise, or into new geographies | Never seriously pursued |
| **Diversification** — new products, new markets | Something unrelated, for someone else | Never on the table |

Four options. Now compare them against what actually happened.

**None of the four is "sell Highrise, shut Campfire, and put the entire company on Basecamp."**

The closest cell is market penetration, and it is not the same thing. Penetration says *sell more of the existing product*. It is silent on whether you keep the other three. A company can pursue penetration on Basecamp and keep Highrise running — indeed that is exactly what 37signals had been doing. The 2014 decision was not "do penetration." It was **"stop doing product development, and free the attention."**

That move has no cell. Look at the axes: **products — existing or new; markets — existing or new.** Neither axis has a value for *fewer*. Every one of the four cells is an addition. The matrix is structurally incapable of returning subtraction as an answer, because subtraction is not a coordinate on it.

## The Decision Replay

| What the framework says | What they actually did | What actually happened |
|---|---|---|
| Four growth options, ranked by risk. The lowest-risk recommendation is **market penetration** — push Basecamp harder into the SMB market — while product development continues in parallel. Nothing in the output suggests removing anything. | On 5 Feb 2014 sold, sunset or spun off every product but Basecamp, and renamed the company Basecamp to make the commitment unambiguous. | Basecamp remained the core business through the focused years. In 2018 they began work on new email ideas, launched **HEY** in early 2020, and on **3 May 2022** Fried renamed the company back to **37signals** — *"We aren't a one product company anymore. We're two. Basecamp and HEY."* |

The sequence, in Ansoff's own vocabulary: **penetration → (subtraction) → penetration → product development.**

Three of those four steps are on the grid. The one that isn't is the one that made the last one possible — and that is the claim worth testing rather than asserting, so here is Fried's own framing of the difference between 2014 and 2022. In 2014 the company had to *leave things behind* to focus. In 2022 he describes a company that can **"do many things at once without leaving anything behind."**

That is a statement about capacity, and capacity is what the focused years bought.

## The Fifth Cell

> **The Fifth Cell — every quadrant of the Ansoff matrix is an addition, because neither of its axes has a value for "fewer." Before using the matrix to choose a growth direction, ask the subtraction question separately: what would we remove, and what would that free? The matrix cannot raise this question, and it will never appear in its output, so it has to be asked outside the tool.**

Two things make this more than a pedantic observation.

**First, Ansoff is used as a menu, and menus imply completeness.** Nobody opens a 2×2 thinking "these are four of the five things I could do." The visual form of a completed grid is an argument that the option space has been covered. It has not.

**Second, subtraction is frequently the enabler of the cells that *are* on the grid.** The 37signals path is the clean illustration: the product-development move that produced HEY came *after* eight years in which the company deliberately did less. A 2014 planning session that ran Ansoff and picked from its four options would have kept Highrise and Campfire alive, kept the attention split, and arrived at 2020 as a weaker company — while having followed the framework correctly.

The practical version is one line added to the front of any Ansoff session:

1. **Before opening the matrix:** what could we stop doing, and what would that free up?
2. **Then open the matrix**, and read its four cells as *growth* options rather than as the full option set.
3. **Check whether the answer to (1) is a precondition for the cell you picked in (2).** If the cell you want requires attention you do not have, the fifth cell comes first.

## Where this misleads

**Ansoff never claimed to cover shrinkage, and criticising a growth matrix for not modelling divestment is partly unfair.** Igor Ansoff built it in 1957 to answer *how do we grow*, and it answers that. The failure mode is in the usage, not the design — but the usage is near-universal, and a tool that is always used as a complete option menu should be evaluated as one.

**37signals is close to a best case for subtraction, and most companies are not.** Private, profitable, no investors, no board demanding a growth rate, and two founders with enough public standing to absorb the reputational cost of killing shipped products. A venture-backed company at the same juncture usually cannot choose the fifth cell at all — not because it is wrong, but because the capital structure forbids it. Read the finding as "the matrix cannot express this option," not as "you should take it."

**Subtraction also kills companies, and we mostly hear the survivors.** For every focus story that worked there are firms that cut the line that would have carried them. Nothing here says removal is safe; the claim is only that it is an option the grid cannot show you.

**We do not actually know that the subtraction caused the later capacity.** Eight years is long, HEY's success has many parents, and Fried is an interested narrator of his own company's history. The sequence is documented and the causal link is his account of it, not a measured result.

## Now run yours

1. **Ask the subtraction question first, in writing, before anyone draws the grid.** What would we stop, and what would it free — people, attention, support load, roadmap?
2. **Then run the matrix** on the four growth cells, honestly labelling which ones you are *already* in. Most companies occupy two and only notice one.
3. **Test the pairing.** If the cell you want needs attention that only subtraction can free, sequence it: fifth cell first, growth cell second.

> Want to map your own growth options? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships an Ansoff worksheet with AI assistance alongside 100+ other frameworks.

## Want to go deeper

- [Ansoff Matrix](/frameworks/ansoff) — the four cells, the risk ordering, and how to place an option
- [Ansoff matrix examples](/academy/ansoff-matrix-examples) — the method run across several companies
- [Apple Ansoff Matrix (2026)](/examples/apple-ansoff-matrix-2026) — a company occupying three cells at once
- [Pre-mortem Example: The Failure a Premortem Cannot Catch](/examples/premortem-cydoc-shutdown) — another Decision Replay where the framework's *structure* is the finding
- [Pros and Cons Example: 9 Pros, 5 Cons, and the One That Decided It](/examples/proscons-cto-to-ic) — a replay where the framework is right and still does no work

*Cover photo: [Andrea De Santis on Unsplash](https://unsplash.com/photos/A78L3bSyBdc).*

---

### Anthropic Business Model Canvas (2026 IPO Edition)
URL: https://frameworklist.com/examples/anthropic-business-model-canvas
> A worked Business Model Canvas of Anthropic as it files confidentially for a 2026 IPO — the enterprise-API revenue engine, the Amazon/Google cloud-partner paradox, and the three blocks the S-1 has to prove.

On **June 1, 2026, Anthropic confidentially filed for an IPO** at a roughly **$965 billion valuation** — larger than Tesla, larger than OpenAI's last private mark, and just below Meta — with bankers at Goldman Sachs, JPMorgan, and Morgan Stanley reportedly steering toward an **October 2026 Nasdaq listing** that could raise more than $60B ([Fortune](https://fortune.com/2026/06/01/anthropic-confidentially-files-ipo-965-billion-valuation/)). Because the S-1 is confidential, the numbers below are the best available private estimates, not audited figures — and they matter, because an IPO forces a private company to justify a business model in public.

The cleanest lens for that is the **[Business Model Canvas](/frameworks/bmc)** — Alexander Osterwalder's nine-block map of how a company creates, delivers, and captures value. Most "Anthropic business model canvas" pages online are auto-generated templates with generic bullets. This one is grounded in the actual mid-2026 numbers and the strategic question the IPO raises: *is this a durable business or a subsidized science project?* The canvas gives a surprisingly clear answer — this is an **enterprise-API business**, not a consumer chatbot.

## The position being analyzed: the IPO-moment numbers

Anthropic's headline story is growth that is almost hard to write down. Estimates of annualized revenue diverge because the company is scaling faster than sources can re-measure, so treat these as a range, not a point.

| Metric | Value | Note |
|---|---|---|
| Confidential IPO filing | June 1, 2026 | Targeting ~October 2026 Nasdaq listing |
| Valuation | ~$965B | May 2026 Series H-1; > Tesla, < Meta |
| Annualized revenue (end 2024) | ~$1B | Starting point of the run |
| Annualized revenue (end 2025) | ~$9B | ~9× in one year |
| Annualized revenue (mid-2026) | ~$30–44B (est.) | Sources diverge; growth outpaces measurement |
| API share of revenue | ~72% | Pay-per-token developer calls |
| Claude.ai subscriptions | ~13% | Consumer + team seats |
| Enterprise share of revenue | ~80% | Versus ~40% for OpenAI |
| Customers paying >$1M/yr | 500 → 1,000+ | Feb 2026 to April 2026 |

Sources: [Sacra](https://sacra.com/c/anthropic/), [FutureSearch](https://futuresearch.ai/anthropic-financial-forecast/), [Contrary Research](https://research.contrary.com/company/anthropic). The single most important row is the revenue mix — it determines every other block on the canvas.

## The Business Model Canvas applied

### Customer Segments
Primarily **enterprises and developers**, not consumers. The dense concentration is in data- and compliance-heavy industries — legal, healthcare, financial services — where long context windows, privacy handling, and reliability are mission-critical. A secondary consumer/prosumer segment buys Claude.ai subscriptions, but at ~13% of revenue it is a lead-generation and brand surface more than a profit center. The ~80% enterprise weighting is the defining fact of the whole canvas.

### Value Propositions
**Frontier capability with a safety guarantee.** Anthropic sells three things at once: models competitive at the capability frontier (Claude), a differentiated safety and reliability posture (Constitutional AI, "honest and harmless" behavior), and enterprise-grade operational trust (long context, data handling, predictable behavior under load). For a bank or hospital deciding which model to embed, "safe and auditable" is not marketing — it is the procurement checklist.

### Channels
Three delivery surfaces: the **developer API** (the revenue engine), the **Claude.ai** consumer/team app, and **deep cloud integrations** via **Amazon Bedrock** and **Google Vertex AI**. The cloud channels are strategically double-edged — they put Claude one click away inside the environments where enterprises already buy compute, but they route a meaningful slice of revenue and the customer relationship through partners.

### Customer Relationships
Mostly **self-serve and usage-based** at the developer tier, shifting to **high-touch enterprise** relationships at the top of the market. The land-and-expand motion is visible in the numbers: customers paying over $1M/year doubled from ~500 in February 2026 to over 1,000 by April. That is the classic infrastructure relationship — usage compounds as the customer's own product grows.

### Revenue Streams
**Pay-per-token API (~72%)**, **Claude.ai subscriptions (~13%)**, and **everything else (~15%)** including **Claude Code**, which reportedly passed $1B in annualized revenue within six months of launch ([Contrary Research](https://research.contrary.com/company/anthropic)). This is usage-based infrastructure revenue, not seat-based SaaS — it grows with customers' consumption rather than headcount, which is why the top line can 9× in a year.

### Key Resources
The **frontier models themselves**, the **research talent** (Anthropic was founded in 2021 by former OpenAI leaders), the **safety/alignment IP** (Constitutional AI), and — critically — **contracted compute capacity**. In a frontier-model business, access to GPUs/TPUs at scale is a balance-sheet-level resource, and Anthropic's is largely sourced through its cloud partners.

### Key Activities
**Model training and research, safety/alignment work, and inference at scale.** The activity that quietly dominates is turning research into reliable, low-latency, high-availability inference — the difference between a demo and a business a bank will route production traffic through.

### Key Partnerships
**Amazon (~$4B, AWS Bedrock)** and **Google (~$2B, Vertex AI)** anchor this block. They supply capital, compute, and distribution simultaneously. That triple dependency is the model's greatest strength *and* its most acute risk — see the named insight below.

### Cost Structure
**Compute-dominated and capex-heavy.** Training frontier models and serving billions of tokens is enormously expensive, and at Anthropic's growth stage costs plausibly still outrun revenue. The IPO thesis is not "already profitable" — it is "usage-based revenue is scaling toward the cost curve fast enough that the crossover is credible."

## Key takeaway: the Cloud-Partner Paradox and the IPO-Readiness Read

The named insight the canvas surfaces is the **Cloud-Partner Paradox**: the same two companies that fund Anthropic (Amazon, Google), supply its compute, and distribute Claude to enterprises are also building models that compete with it. No other block on the canvas carries this much coupled upside and downside. It is simultaneously the reason Anthropic could scale revenue 9× in a year and the single sentence a cautious S-1 reader will circle.

Read as an IPO document, the nine blocks are not equally load-bearing. Here is the **IPO-Readiness Read** — which blocks are settled and which the S-1 actually has to defend:

| BMC block | S-1 question it must answer | Read |
|---|---|---|
| Revenue Streams | Is the growth durable or a spike? | ✅ Strong — usage-based, land-and-expand |
| Customer Segments | Concentrated in a few whales? | 🟡 Watch — enterprise weighting cuts both ways |
| Value Propositions | Is "safety" a real moat vs. price? | 🟡 Watch — must show it drives procurement |
| Key Partnerships | What if Amazon/Google turn rival? | 🔴 Decides it — the Cloud-Partner Paradox |
| Cost Structure | When does compute cost cross revenue? | 🔴 Decides it — the path-to-profit story |
| Channels | Own the customer, or rent it via clouds? | 🟡 Watch — channel = partner = risk |

The three blocks that decide the IPO are **Key Partnerships, Cost Structure, and — as the hinge between them — the enterprise Revenue mix.** Everything else is a strength. If you only read three rows of Anthropic's eventual public canvas, read those.

For contrast, the same nine-block exercise on OpenAI produces a consumer-weighted mirror image (more subscription, less API concentration), which is why the two IPOs will be judged on different risks — a point [FourWeekMBA](https://fourweekmba.com/ai-spacex-openai-anthropic-ipo-business-models-2026/) makes across all three of 2026's AI-adjacent offerings.

> Want to map your own company on the same nine blocks? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) fills in any framework — including the Business Model Canvas — with AI assistance.

## Related

- [Business Model Canvas](/frameworks/bmc) — the nine-block framework used here
- [Lean Canvas vs Business Model Canvas](/compare/lean-canvas-vs-business-model-canvas) — which canvas fits which stage of company
- [Lean Canvas](/frameworks/lean) — Ash Maurya's startup-stage adaptation
- [Nvidia BCG Matrix Analysis 2026](/examples/nvidia-bcg-matrix) — a portfolio-lens read of the other AI-boom bellwether

*Figures are private estimates compiled from the sources above; Anthropic's S-1 was confidential at the time of writing and no audited financials were public.*

---

### Apple Ansoff Matrix Example 2026: four quadrants, scored
URL: https://frameworklist.com/examples/apple-ansoff-matrix-2026
> Worked Apple Ansoff Matrix example: iPhone 17 penetration, India expansion, Vision Pro diversification — and which quadrant the $1,999 iPhone Duo lands in.

![Close-up of a printed circuit board, the hardware layer underneath every Apple growth bet](https://images.unsplash.com/photo-1518770660439-4636190af475?auto=format&fit=crop&w=1600&q=80)

Most **Apple Ansoff Matrix examples** on the web are still working from 2015. They place the Apple Watch in Diversification, cite the 2007 iPhone as the great new-market bet, and stop. That version of the exercise is tidy, and it teaches the wrong lesson, because every quadrant in it succeeded — which makes Ansoff look like a labelling exercise rather than a risk model.

Apple's fiscal 2026 is a much better teacher. In the quarter ended June 27, 2026, the company ran all four quadrants simultaneously and got four visibly different outcomes — and those outcomes line up almost exactly with the risk ordering [Igor Ansoff proposed in 1957](https://hbr.org/1957/09/strategies-for-diversification). One quadrant set records in every geography on earth. Another had its production line switched off.

> **Want to run the matrix on your own company?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=ansoff-apple) fills in each quadrant with AI-assisted prompts. Free to start.

## Position being analyzed

Apple reported fiscal Q3 2026 on July 30, 2026: revenue of **$109.4 billion, up 16%** year over year, net income of **$29.8 billion**, and diluted EPS of **$2.02, up 29%**. Gross margin reached **50.1%** against 46.5% a year earlier, though roughly two percentage points of that came from tariff refunds ([MacRumors](https://www.macrumors.com/2026/07/30/apple-3q-2026-earnings/)).

The segment detail is what makes the Ansoff read possible, because each line maps cleanly onto a quadrant:

| Segment | FY26 Q3 revenue | YoY | Share of total |
|---|---|---|---|
| iPhone | $54.25B | +22% | 49.6% |
| Services | $30.74B | +12% | 28.1% |
| Mac | $10.35B | +29% | 9.5% |
| Wearables, Home & Accessories | $7.88B | +6% | 7.2% |
| iPad | $6.19B | −6% | 5.7% |
| **Total** | **$109.42B** | **+16%** | **100%** |

Source: [TelecomLead](https://telecomlead.com/smart-phone/apple-q3-2026-revenue-jumps-16-to-109-4-bn-as-iphone-mac-services-and-china-drive-growth-127024). Apple set June-quarter records for total revenue, EPS, iPhone, Mac and Services. Services was the one soft spot against expectations, landing under the $31.22B consensus ([Yahoo Finance](https://finance.yahoo.com/markets/stocks/articles/apple-q3-2026-earnings-beat-211056445.html)).

The strategic question Ansoff helps with: Apple is growing 16% at a $430B annual run rate — but *which kind* of growth is it, and what happens when the cheapest kind runs out?

## Market Penetration: the iPhone 17 into an installed base Apple already owns

Existing product, existing market — the lowest-risk quadrant, and by far Apple's largest. iPhone revenue of **$54.25B (+22%)** came from selling the iPhone 17 family to people who already own iPhones, through channels Apple already controls. It set June-quarter records in *every* geographic segment.

Most of Services belongs here too. iCloud, the App Store commission, Apple Music and Apple TV+ are ways of extracting more revenue from the same installed base — the definition of penetration. At $30.74B, Services is Apple's second-largest line and its highest-margin one.

Together these two lines are roughly **78% of Apple's revenue**, and they sit in the quadrant Ansoff considers safest. This is the single most important fact about Apple's growth strategy, and it is invisible without the framework.

## Product Development: new hardware, same customers

New product, existing market. Mac, iPad and Wearables all live here: Apple designs new devices and sells them to the people already inside the ecosystem.

The quadrant's mixed result in Q3 2026 is instructive. **Mac hit a June-quarter record at $10.35B, up 29%.** **Wearables grew 6% to $7.88B.** But **iPad fell 6% to $6.19B** — the only major category to decline. Same quadrant, same customers, same channel, and one of the three still shrank. Product Development is medium-risk precisely because the customer relationship does not guarantee the product lands.

### The Apple Watch correction

This is where most published Apple Ansoff examples go wrong. They put the 2015 Apple Watch in **Diversification**. It belongs in **Product Development**.

Run the two-question placement test. *Is the product new?* Yes — Apple had never sold a watch. *Is the market new?* No. The launch Watch required an iPhone to set up and function; it was sold to Apple's existing customers, through Apple's existing stores, on the strength of Apple's existing brand. New product plus existing market is Product Development by definition.

The error matters because it is flattering. Classifying the Watch as Diversification implies Apple has repeatedly won in the highest-risk quadrant and makes the bottom-right box look survivable. The 2026 data shows what a real diversification looks like.

## Market Development: India, the adjacency-discounted bet

Existing product, new market. Apple's India build-out is the textbook case, and it is working.

Annual India sales **crossed $10 billion for the first time** in the 12 months through March, up from roughly $9 billion ([Bloomberg](https://www.bloomberg.com/news/articles/2026-08-04/apple-s-india-sales-top-10-billion-on-widening-retail-push)). Apple opened a Mumbai store in February 2026, taking its official count to **six**, and now runs **five iPhone factories** in the country. To reach buyers at Indian price points it leans on no-cost EMI financing, card cashback up to ₹15,000 and trade-ins ([MacDailyNews](https://macdailynews.com/2026/08/07/apple-expands-retail-footprint-and-financing-options-to-capture-surging-iphone-demand-in-india/)).

Ansoff calls this higher-risk than penetration, and in the abstract it is. But India carries a large **adjacency discount**: the product is finished, the brand arrived decades before the stores did, and the supply chain is already local. Only the market is genuinely new. That is why a quadrant nominally riskier than Product Development is currently outperforming iPad.

## Diversification: Vision Pro, and what the bottom-right quadrant actually costs

New product, new market — the highest-risk quadrant. Vision Pro qualifies on both axes without argument: a spatial computer is a product category Apple had never shipped, and there was no existing base of Apple headset buyers to sell it to.

The outcome is the most honest data point in this entire analysis. Vision Pro shipped roughly **390,000 units in its 2024 launch year**, fell to **under 100,000 in 2025**, and IDC estimated just **45,000 units in the holiday quarter**. Assembler Luxshare halted production. Apple cut Vision Pro digital advertising by **more than 95%** in the US and UK. Availability stayed frozen at **13 countries** with no expansion planned ([MacRumors](https://www.macrumors.com/2026/01/02/vision-pro-still-failing-to-catch-on/), [IDC via Slashdot](https://apple.slashdot.org/story/26/01/01/189219/idc-estimates-apple-shipped-just-45000-vision-pros-last-quarter)).

Vision Pro revenue is not broken out; it is folded into the $7.88B Wearables, Home & Accessories line, where it is small enough to be invisible. The company that just set records in four other categories could not make its one true diversification work — with the world's strongest consumer brand, unlimited capital, and seven years of development behind it.

## The Revenue-Weighted Ansoff Test

Here is the original synthesis worth taking away, and it generalises past Apple. The standard Ansoff exercise stops at placement: sort the moves into four boxes and declare the bottom-right one risky. That is a claim nobody checks. **The Revenue-Weighted Ansoff Test** checks it — place each move, then attach the revenue and growth it actually produced, and ask whether the outcomes track Ansoff's risk ordering.

| Quadrant | Apple's FY2026 move | Revenue attached | Result | Ansoff risk rank |
|---|---|---|---|---|
| **Market Penetration** | iPhone 17 + Services to the installed base | $85.0B combined (78% of revenue) | Records in every geography | 1 — lowest |
| **Product Development** | Mac, iPad, Wearables to existing customers | $24.4B combined | Mixed: Mac +29%, iPad −6% | 2 |
| **Market Development** | India — same products, new market | >$10B annual, double-digit growth | Six stores, five factories, working | 3 |
| **Diversification** | Vision Pro — new product, new market | Not broken out; immaterial | Production halted, ads cut 95% | 4 — highest |

Read the outcome column top to bottom. It degrades in exactly the order Ansoff predicted in 1957: the safest quadrant carries the most revenue and the cleanest results, and the riskiest carries almost none and the worst. That is not a coincidence engineered by hindsight — it is one company, one fiscal year, four bets running in parallel with the same brand, capital and talent behind each.

The test is worth running on any company you analyse, because it converts Ansoff from a sorting exercise into a falsifiable one. When the outcomes *don't* track the risk ordering, that is the interesting finding — it usually means an adjacency discount is doing more work than the quadrant label admits, which is precisely what India is doing for Apple right now.

## The iPhone Duo: placing a move before its outcome exists

Everything above is scored on results that are already in. On **9 September 2026** Apple gave the framework a live test with no outcome yet: the **iPhone Duo**, its first foldable — a **5.4-inch outer and 7.6-inch inner display, 5.2 mm unfolded, 254 g, A20 Pro, from $1,999 for 256 GB**, pre-orders 16 October and in stores 23 October ([MacRumors](https://www.macrumors.com/roundup/iphone-duo/)). It was introduced alongside the iPhone 18 Pro at $1,199 and Pro Max at $1,299, with no standard iPhone 18 on the stage ([Fox Business](https://www.foxbusiness.com/technology/apple-unveils-first-foldable-iphone-iphone-18-pro-lineup-new-watches-annual-launch-event)), and it is the first product launched under **John Ternus, CEO since 1 September** after Tim Cook's move to executive chairman ([MacRumors](https://www.macrumors.com/2026/08/31/tim-cook-steps-down-as-apple-ceo-tomorrow/)).

The headline reads like Vision Pro's did — *Apple ships a new form factor* — which is exactly why it is worth placing carefully. Run the same two-question test that corrected the Watch.

*Is the product new?* Yes, without argument. Apple has never shipped a folding display, and at $1,999 the Duo is the first iPhone priced above a MacBook Air.

*Is the market new?* This is where the honest work is, because there are two candidate answers and they land in different boxes:

| Candidate market | Who is in it | Quadrant it implies |
|---|---|---|
| **Apple's installed base**, top price tier | Existing iPhone owners trading up from a $1,199 Pro | Product Development |
| **The foldable category** | Samsung **64%**, Huawei 15%, Motorola 7%, Honor 6% of Q3 2025 shipments ([Counterpoint via GSMArena](https://www.gsmarena.com/cr_samsung_breaks_record_for_most_foldable_smartphone_shipments_in_q3-news-70550.php)) — Apple at zero | Market Development, or Diversification |

Ansoff's market axis is about **customers**, not competitors' product categories. The Duo runs iOS, sells through Apple's own stores, syncs to the same iCloud, Watch and AirPods, and asks nothing new of its buyer except the price. Its natural purchaser is someone who already owns an iPhone. That is the Watch test again: new product, existing market — **Product Development**, one axis new. Anyone who calls the Duo a diversification is making the same flattering error the Watch has attracted for a decade, and it matters more this time because the bottom-right box has a fresh, expensive comparison sitting in it.

### Why the Duo is not Vision Pro

| | Vision Pro (2024) | iPhone Duo (2026) |
|---|---|---|
| Product new? | Yes — spatial computer | Yes — foldable |
| Market new? | **Yes** — no existing base of Apple headset buyers | **No** — existing iPhone owners, existing channel |
| Quadrant | Diversification | Product Development |
| Replaces something the buyer already owns? | No — an addition | Yes — the buyer's current iPhone |
| Category growth outside Apple | Negligible | **+20% in 2026** while smartphones overall fall **−13.9%** ([IDC](https://www.idc.com/resource-center/blog/worldwide-smartphone-market-to-decline-13-9-in-2026-as-memory-crisis-and-us-iran-war-constrain-growth/)); Counterpoint puts it at +21% ([Counterpoint](https://counterpointresearch.com/en/insights/samsung-to-retain-lead-as-global-foldable-market-set-for-21percent-yoy-growth)) |

The last two rows are the strategic content. Vision Pro was an *addition* into a market that did not exist; the Duo is a *substitute* aimed at the one segment of Apple's own core market that is still growing, in a year IDC calls the steepest contraction in smartphone history. Same "new form factor" headline, different quadrant, and Ansoff says the outcomes should differ by the width of the risk ladder. (The row-five distinction — foldables up 20% inside a market down 13.9% — is the same denominator problem worked on the [Star quadrant page](/glossary/star): pick the wrong market and the same device changes box.)

### The Pre-Registered Quadrant

The Revenue-Weighted Ansoff Test scores placements *after* the outcome is known, which is safe and slightly cheap — hindsight makes every quadrant look obvious. The Duo is the chance to do the harder version. **The Pre-Registered Quadrant** writes four things down before the first quarter reports: the placement, what the placement predicts, what result would prove it wrong, and the date it gets scored.

| | Entry, written 16 September 2026 |
|---|---|
| **Placement** | Product Development (new product, existing market) |
| **Prediction** | The Duo shows up in the foldable share tables in its first full quarter, ahead of Motorola (7%) and Honor (6%) — an outcome no Apple Diversification has ever produced (Vision Pro never entered any share table). iPhone segment revenue grows in fiscal Q1 2027 despite a shrinking smartphone market, because a $1,999 substitute lifts mix even if units are flat. |
| **Falsifier** | If, after two full quarters, Apple's foldable share sits below Honor's 6%, the market axis was new after all — the $1,999 tier behaved as a separate market, not a trade-up path — and the correct placement was Diversification. |
| **Scored on** | Apple fiscal Q1 2027 results (late January 2027) and the Q4 2026 foldable shipment reports from Counterpoint and IDC. |

If the placement holds, the Watch correction generalises: Apple's new form factors are Product Development whenever they sell into the base, and Diversification only when — as with Vision Pro — there is no base to sell into. If it fails, the failure is more interesting than the success, because it would mean price alone can move a product across Ansoff's market axis, which the 1957 paper does not contemplate. Either way the page will report the score, not quietly re-place the move.

## Key takeaway

Apple in fiscal 2026 is a company earning 78% of its revenue from the lowest-risk quadrant on the Ansoff Matrix, extending competently into a new geography, and having quietly retreated from its only genuine diversification. That is not a criticism — it is a description of a mature, extraordinarily profitable operator harvesting an installed base it spent twenty years building.

But it is also the question the framework exists to force. Market Penetration works until the installed base saturates. Product Development works until the ecosystem runs out of adjacent devices — iPad's −6% is an early signal of what that looks like. Market Development in India has perhaps a decade of runway. Diversification is the only quadrant that creates a genuinely new S-curve, and it is the one Apple's 2026 numbers show it stepping back from. Ansoff does not resolve that tension. It just makes sure the tension is visible on one page, in four boxes, instead of being lost in a segment table.

The iPhone Duo is Apple's first answer under a new CEO, and it is a telling one: not a second diversification, but a Product Development move into the only growing pocket of the market it already owns. Whether that is enough is the question the pre-registered entry above will score in January.

## Want to go deeper

New to the model? Start with [Ansoff Matrix examples: the 4 growth strategies](/academy/ansoff-matrix-examples), which walks all four quadrants and the placement test used above on real companies. You can also browse the [Ansoff Matrix framework page](/frameworks/ansoff) or the full library of [strategy frameworks applied to real companies](/examples).

For the same lens on operators with the opposite risk profile — both anchoring their valuation to the *riskiest* quadrant — see the [Nvidia Ansoff Matrix 2026](/examples/nvidia-ansoff-matrix-2026) and the [Tesla Ansoff Matrix analysis](/examples/tesla-ansoff-matrix). For a non-tech operator running all four quadrants at once, see the [FIFA Ansoff Matrix 2026](/examples/fifa-ansoff-matrix-2026).

Ansoff also says nothing about which moves to *stop* — all four of its cells are additions. For a case where the winning move was removal and therefore off the grid entirely, see the [Ansoff Matrix Example: The Growth Move That Isn't on the Grid](/examples/ansoff-37signals-subtraction).

Ansoff tells you which growth moves are risky; it says nothing about which ones to fund. That is the BCG Matrix's job, and the hand-off between the two is laid out in [Ansoff Matrix vs BCG Matrix](/compare/ansoff-matrix-vs-bcg-matrix) — worth reading alongside [BCG Matrix analysis explained](/academy/bcg-matrix-analysis-explained), which works Apple's same fiscal Q3 2026 onto the growth-share grid. For Apple through a third lens, see the [Apple McKinsey 7S analysis 2026](/examples/apple-mckinsey-7s-analysis-2026) and the [Apple PESTEL analysis 2026](/examples/apple-pestel-analysis-2026).

For Apple's SWOT counterpart, see our sister site [SWOTPal's Apple SWOT analysis](https://swotpal.com/examples/apple?utm_source=frameworklist&utm_medium=referral&utm_campaign=ansoff-apple) — a dedicated AI SWOT tool, free for the basic workflow.

*Cover photo: [Alexandre Debiève on Unsplash](https://unsplash.com/photos/FO7JIlwjOtU).*

---

### Apple McKinsey 7S Analysis 2026
URL: https://frameworklist.com/examples/apple-mckinsey-7s-analysis-2026
> A worked McKinsey 7S analysis of Apple in 2026, re-scored after John Ternus replaced Tim Cook as CEO — Strategy, Structure, Systems, Shared Values, Skills, Style, Staff. Which of the seven S's actually moved, and why the Gemini deal is a Systems answer to a Skills gap.

![Photograph of a Post-it whiteboard covered in handwritten notes, evoking the kind of cross-functional organizational analysis the 7S framework supports](https://images.unsplash.com/photo-1454165804606-c3d57bc86b40?auto=format&fit=crop&w=1600&q=80)

Apple in 2026 has stated strategy clarity. Services revenue at $100B+ run-rate. Apple Intelligence as the AI execution path. Vision Pro as the long-bet hardware platform. India-and-Vietnam manufacturing diversification. The strategy is legible, and the financial numbers continue to look healthy. The McKinsey 7S framework asks a sharper question: is the *whole organization* — strategy, structure, systems, shared values, skills, style, staff — configured to execute that strategy? Or are some of the seven elements drifting in ways that will compress the strategy's outcomes over the next two to three years?

Run cleanly on Apple in May 2026, 7S surfaced an organization whose Hard S's (Strategy, Structure, Systems) were world-class and tightly aligned, while two of the four Soft S's (Skills and Staff in frontier ML) had drifted relative to what the AI-services strategy requires. The framework's contribution is the diagnostic — not a prescription, but a structured map of which elements would need to change for the stated strategy to actually land.

**This page was re-scored on 17 September 2026**, sixteen days after [John Ternus replaced Tim Cook as CEO](https://www.apple.com/newsroom/2026/04/tim-cook-to-become-apple-executive-chairman-john-ternus-to-become-apple-ceo/). The May analysis is kept intact below as the "before"; the [September re-score](#re-scored-in-september-2026-which-ss-actually-moved) at the end grades it element by element and names the pattern — [The Buy-or-Become Test](#the-buy-or-become-test) — that the four months in between revealed.

## Position being analyzed

Mid-2026: Apple Intelligence has shipped on iPhone 16/17 lines with on-device + Private Cloud Compute architecture, Services revenue continues low-double-digit growth, the DOJ antitrust trial is in pre-trial motions, the EU Digital Markets Act has reshaped App Store economics, Vision Pro is in its second product generation with sub-$2,000 pricing, India accounts for ~25% of iPhone assembly, and the AI talent war has accelerated with OpenAI, Anthropic, Google DeepMind, and Meta AI offering comp packages reportedly 2-4x Apple's historical scale. The strategic question 7S helps with: which of the seven elements is most likely to compress the AI-services strategy's outcomes if it doesn't shift?

| Element | Current state | Direction |
|---|---|---|
| iPhone unit growth | Low single digits | Slowing |
| Services revenue YoY | +13% | Stable |
| Apple Intelligence rollout coverage | iPhone 15 Pro+; iPhone 16+ | Expanding |
| Senior ML hires (publicly known) | < 20 from frontier-lab peers | Below peer level |
| App Store take rate (EU effective) | 22-26% | Down from 30% |
| India assembly share | ~25% | Up from ~14% |
| Vision Pro unit volume | Low millions cumulative | Below initial trajectory |

## McKinsey 7S applied

The 7S model distinguishes between **Hard S's** (Strategy, Structure, Systems) — concrete, top-down-controllable — and **Soft S's** (Shared Values, Skills, Style, Staff) — cultural and capability-based, slow to shift. The framework's diagnostic value comes from scoring both groups and surfacing misalignment. For the underlying split — why three Hard and four Soft, where the asymmetry comes from, and how to read it — see the [McKinsey 7S Framework: Hard and Soft Elements](/academy/mckinsey-7s-framework-hard-soft-elements) explainer.

### Strategy (Hard) — clear, premium, services + on-device AI

Apple's 2026 strategy is the most legible it has been in years:

1. **Defend the iPhone installed base** through gradual upgrade incentives (Apple Intelligence as the latest one)
2. **Grow services** as the primary revenue contributor (App Store, advertising, Apple TV+, Apple Care, payments, cloud)
3. **Bet on Apple Intelligence** as a long-cycle on-device + private-cloud AI platform
4. **Diversify manufacturing** away from concentrated China exposure
5. **Pursue Vision Pro** as optionality on a future spatial-computing category
6. **Maintain premium positioning** — Apple does not chase low-end share

The strategy is internally coherent. The risk to it is execution on AI and the regulatory headwinds on App Store economics — both surfaced in the other elements below.

### Structure (Hard) — functional org, tightly held

Apple operates a functional organization: design, engineering, operations, software, services, hardware engineering all report to the CEO rather than being grouped by product line. This is unusual at Apple's scale — most companies > $100B revenue use divisional structures. The functional model was put in place by Steve Jobs and rebuilt by Tim Cook into the modern operating system that produced everything from M-series silicon to AirPods to Apple Pay.

The Structure is genuinely world-class for the categories Apple competes in today. The 7S question for 2026 is whether it can support a *platform-level* capability like frontier AI. Historically, Apple's services org has been the awkward exception that required organizational workarounds. Frontier AI is even more cross-cutting — it has to be in every product simultaneously. The May read was that the Structure might need to evolve toward something like the "VP of AI Platform" elevation that Operations got when Cook took over from Jobs.

*September 2026 note:* it evolved, but in the other direction. On 1 December 2025 Apple announced that John Giannandrea, the SVP who had run a standalone ML and AI Strategy organization since 2018, would retire in spring 2026; Amar Subramanya joined as VP of AI **reporting to Craig Federighi**, leading "Apple Foundation Models, ML research, and AI Safety and Evaluation", and "the balance of Giannandrea's organization will shift to Sabih Khan and Eddy Cue" ([Apple Newsroom](https://www.apple.com/newsroom/2025/12/john-giannandrea-to-retire-from-apple/)). On 20 April 2026, the same day the CEO succession was announced, Johny Srouji became Apple's first **Chief Hardware Officer**, combining Hardware Engineering (Ternus's old org) with Hardware Technologies ([Apple Newsroom](https://www.apple.com/newsroom/2026/04/johny-srouji-named-apples-chief-hardware-officer/)). The current [leadership page](https://www.apple.com/leadership/) lists no SVP of Hardware Engineering and no AI executive at all. The functional Structure survived the CEO change; the number of functions reporting to the CEO shrank.

### Systems (Hard) — supply chain + App Store + Apple Silicon roadmap

Apple's operational Systems are textbook. The supply chain — Cook's legacy, now run by COO Sabih Khan — moves roughly $400B of annual revenue through a functional org that HBR described in 2020 as organized "by expertise, not by product" ([HBR](https://hbr.org/2020/11/how-apple-is-organized-for-innovation)). The App Store is a global payments and distribution System in its own right. The Apple Silicon roadmap (M3 / M4 / M5) ships on near-clockwork annual cadence, and the OS release train delivers iOS, macOS, watchOS and visionOS on the same September beat every year.

Two Systems pressures show up in 7S:

- **The App Store take-rate System** is under active legal pressure (DOJ, EU DMA, UK CMA, Japan, Korea). The Systems are being forced to evolve — alternative payment processors, third-party marketplaces, sideloading in some markets — and that evolution is changing the revenue economics, not just the technical implementation.
- **The ML training infrastructure System** is the one Apple has historically *under-invested* in relative to peer labs. Apple ships world-class consumer ML; it does not (publicly) operate world-class research infrastructure at the frontier scale of Google DeepMind or Meta AI. This is the Systems element that 7S would flag as needing investment to support the Strategy. *September 2026 note:* Apple's answer was not to build it. On 12 January 2026 Apple and Google announced a multi-year partnership under which Gemini models and cloud technology underpin "the next generation of Apple Foundation Models" — Apple's statement: "After careful evaluation, we determined that Google's technology provides the most capable foundation for Apple Foundation Models" ([TechCrunch](https://techcrunch.com/2026/01/12/googles-gemini-to-power-apples-ai-features-like-siri/)). The deal is non-exclusive, and the widely reported ~$1B-a-year figure comes from prior press reports rather than either company. The frontier-scale System now exists — it is rented.

### Shared Values (Soft) — privacy, design excellence, secrecy

The cultural foundation. Apple's three durable Shared Values:

1. **Privacy as a product feature** — not lip service; the on-device Apple Intelligence architecture exists because of this value
2. **Design excellence** — the rare hardware company where industrial design has CEO-level attention
3. **Secrecy** — product roadmaps, technical decisions, and personnel moves are not publicly previewed

These values produced the modern Apple. They are also in tension with the AI-services strategy:

- Privacy *constrains* the cloud LLM architecture that would close the AI-quality gap fastest
- Design excellence *slows* the rapid-iteration cadence frontier AI requires
- Secrecy *repels* the academic-publish-and-collaborate culture that frontier ML researchers prefer

The 7S framework forces the acknowledgment that Shared Values are not infinitely malleable — and that the AI strategy is sometimes in direct conflict with values Apple cannot abandon without breaking other parts of the business.

### Skills (Soft) — hardware-software integration; ML talent gap

Apple's Skills are exceptional in:

- **Vertical integration** — hardware-software co-design unmatched in the industry
- **Supply chain operations** — the entire industry copies Cook's playbook
- **Custom silicon design** — Apple Silicon team is world-class
- **Consumer ML deployment** — shipping ML to billions of devices at scale

The Skills *gap*, surfaced by 7S, is in **frontier ML research at scale**. Apple has talented ML engineers; it does not (publicly) have the density of frontier-research staff that OpenAI, Anthropic, Google DeepMind, or Meta AI have built. This isn't a moral judgment — it's an observation that Skills required to *deploy* ML are different from Skills required to *advance* ML, and Apple's stated strategy now requires both.

### Style (Soft) — from an operations CEO to a hardware-engineer CEO

*This element was written in May 2026 about Tim Cook and re-scored in September 2026 for John Ternus.*

Tim Cook's leadership Style was operations-driven, consensus-built within a small executive team, and externally restrained. Product decisions were top-down once made; deliberation preceded commitment. The Style produced extraordinary operational excellence and product polish.

It also produced friction with the modern AI research culture, and the May analysis listed three specific points:

- Frontier ML researchers want to **publish openly** — Apple's Style resists
- Frontier ML researchers want **iteration on weekly cycles** — Apple's Style is annual
- Frontier ML researchers respond to **public technical reputation** — Apple's Style is anti-celebrity

Style is the hardest element to shift, and on 1 September 2026 Apple changed the person who sets it. John Ternus is a mechanical engineer who joined Apple's product design team in 2001, became VP of Hardware Engineering in 2013 and SVP in 2021, and led the hardware for iPad, AirPods, Mac, Apple Watch and every iPhone generation since ([Apple Newsroom](https://www.apple.com/newsroom/2026/04/tim-cook-to-become-apple-executive-chairman-john-ternus-to-become-apple-ceo/)). Cook's own description — "the mind of an engineer, the soul of an innovator" — is a Style statement: the centre of gravity moves from the supply chain to the product. His first public act as CEO was the 9 September launch of the iPhone 18 Pro and the [iPhone Duo](/examples/apple-ansoff-matrix-2026#the-pre-registered-quadrant), not an operations or services announcement. Cook remains as executive chairman, engaging "with policymakers around the world" — the externally-facing half of the old Style stays with the old CEO.

The honest re-score is that **none of the three frictions above is relieved by a hardware-engineer CEO**. Hardware engineering is the most secretive organization inside Apple, the one most bound to an annual product cadence, and the one least oriented toward public technical reputation. If the May diagnosis had been "Apple needs a Style that frontier researchers will work under", Ternus is a step *away* from it, not toward it. What actually relieved the tension is in the Systems element: once the frontier model is licensed from Google, Apple no longer needs a research culture that can produce one. The Style could stay exactly as it was — and, under a hardware CEO, it will.

### Staff (Soft) — composition reflects pre-AI-era priorities

Apple's Staff composition was optimized over two decades for hardware-software integration, supply chain operations, and consumer ML deployment. It was *not* optimized for the frontier ML talent war that emerged from 2020 onward.

The Staff element is the most concrete and the most slow-to-change. In May the observable fact was that Apple had not made the kind of marquee frontier-lab hire that Microsoft, Meta and Google were making, while senior ML departures from Apple were being reported.

7S doesn't prescribe a fix — it diagnoses the misalignment. Staff is the element where the gap between strategy and execution capability was most concrete in mid-2026.

*September 2026 note:* the one senior hire that did happen is exactly the shape the May "signals to watch" table asked for — Amar Subramanya, formerly corporate vice president of AI at Microsoft and, before that, sixteen years at Google ending as head of engineering for Gemini Assistant ([Apple Newsroom](https://www.apple.com/newsroom/2025/12/john-giannandrea-to-retire-from-apple/)). Read alongside the Gemini deal, the hire is not a frontier-research bet; it is an integration bet — Apple recruited the person who ran engineering on the model it is now licensing. The wider executive team also turned over: Cook, Giannandrea and Luca Maestri out or moved; Ternus, Srouji, Subramanya, CFO Kevan Parekh and General Counsel Jennifer Newstead in; the M&A chief dropped from the leadership page ([9to5Mac](https://9to5mac.com/2026/09/01/john-ternuss-first-day-as-apple-ceo-heres-the-latest/)). That is more Staff change at the top in nine months than Apple saw in the previous nine years — almost none of it in the frontier-research segment the May analysis was watching.

## Counter-argument

The bull view: Apple's 7S has been quietly evolving for years. Apple Silicon was a multi-year, multi-element transformation that worked. Services growth required exactly the kind of cross-element coordination 7S is built to surface, and Apple delivered it. The AI strategy is a 5-7 year program, and Apple's track record on long-cycle bets (Apple Silicon, Apple Watch, AirPods, Vision Pro hardware engineering) is excellent.

7S doesn't refute this — it raises the bar of evidence. Each historical transformation succeeded because Apple shifted *multiple* S's in coordination. The framework's contribution is to ask: which S's have Apple actually shifted for AI, and at what pace? The honest answer in May 2026 was: Strategy (yes), Systems (partially), Skills (slowly), Style (not yet), Staff (insufficiently). Three out of seven elements actively shifting is not the same as a full 7S realignment. The September re-score below changes that count — but not in the way the May page predicted.

## Signals to watch (next 18 months)

| Signal | Element | Why it matters | Status, Sept 2026 |
|---|---|---|---|
| Senior ML hires from frontier labs (public moves) | Staff + Skills | The most concrete leading indicator | **Fired** — Subramanya (ex-Google Gemini, ex-Microsoft AI) as VP of AI, Dec 2025 |
| Apple AI research publications + presence at NeurIPS / ICML | Style | Whether the secrecy-vs-research-culture tension is being resolved | **Moot** — the frontier model is now licensed; the tension no longer has to be resolved |
| Apple Intelligence consumer perception vs cloud LLMs | Strategy execution | Whether the on-device bet is converting | **Redefined** — Google confirmed a Gemini-based Siri for 2026 ([MacRumors](https://www.macrumors.com/2026/04/22/google-gemini-powered-siri-2026/)); the bet is now hybrid, not on-device |
| App Store take rate trajectory in EU + UK | Systems | Whether the regulatory-driven Systems evolution stabilizes | Open |
| Vision Pro 2 unit volume + sub-$2k variant adoption | Strategy | Whether the long-bet Hardware-S delivers commercial scale | Open — the Duo, not Vision Pro, was the September headline |
| Apple Intelligence rollout to non-iPhone product lines | Structure | Whether the cross-cutting AI capability is being organized | **Fired** — organized by dissolution: models under Software, the rest under Operations and Services |
| Apple Silicon AI accelerator generational improvement | Systems + Skills | The technical-execution proof point | Open — Srouji now owns silicon *and* the devices it goes into |

## Re-scored in September 2026: which S's actually moved

The May analysis made a falsifiable claim: for the AI Strategy to execute, **at least three elements would have to change, and they would be Soft ones — Skills, Style and Staff.** Four months and one CEO later, here is the element-by-element grade.

| Element | May 2026 read | What happened (dated) | Sept 2026 re-score |
|---|---|---|---|
| **Strategy** (Hard) | Aligned: services + on-device AI | Unchanged in substance; the AI leg is now "Apple Foundation Models on Gemini" rather than in-house frontier models (12 Jan 2026) | **Aligned — one leg re-sourced** |
| **Structure** (Hard) | Aligned; might need a standalone AI elevation | Standalone AI org dissolved into Software / Operations / Services (1 Dec 2025); Hardware Engineering + Hardware Technologies merged under a Chief Hardware Officer (20 Apr 2026); M&A dropped as a direct report (Sept 2026) | **Moved — consolidated, the opposite of elevation** |
| **Systems** (Hard) | Aligned except ML training infrastructure, flagged as under-invested | Frontier model and cloud capacity licensed from Google, multi-year, non-exclusive (12 Jan 2026) | **Moved — gap closed by purchase, not build** |
| **Shared Values** (Soft) | Privacy + design + secrecy, in tension with frontier AI | Apple says privacy standards hold under the Gemini partnership; secrecy untouched | **Unchanged — and now less tested, because the research culture no longer has to live inside Apple** |
| **Skills** (Soft) | Gap in frontier ML research at scale | No evidence of an internal frontier-research build-out; integration skills prioritized (Subramanya hire) | **Gap not closed — outsourced** |
| **Style** (Soft) | Cook: operations-driven, secretive, annual | Ternus: hardware-engineer CEO from 1 Sept 2026; Cook to executive chairman | **Moved — but away from the research-friendly Style May said was needed** |
| **Staff** (Soft) | Under-recruited in frontier ML | One frontier-lab VP hired; five of the top-tier executive seats turned over in nine months | **Moved at the top, not in the segment diagnosed** |

Count the rows marked *moved*: Structure, Systems, Style, Staff — four elements, of which **two are Hard**. The May prediction that the change would come through Skills, Style and Staff was wrong on Skills entirely, right on Style and Staff only in the trivial sense that the names changed. The realignment came through the Hard S's — which, in hindsight, is the least surprising thing a company with world-class Hard S's could do. Apple used the elements it is best at to route around the elements it is weakest at.

### The Buy-or-Become Test

The general pattern is worth naming, because it is the most common way a 7S diagnosis gets "resolved" without the organization changing.

> **When 7S surfaces a Soft-S gap, check whether the company closed it by *becoming* — shifting Style, recruiting Staff, building Skills — or by *buying* — converting the gap into a Systems contract or a Strategy partnership. Buying is faster, leaves the culture intact, and is therefore the default for any company whose Shared Values conflict with the culture shift becoming would require. The cost is a dependency that the original 7S read never scored, because it did not exist yet.**

Apply it to Apple:

| Question | Answer |
|---|---|
| Was the Soft-S gap real? | Yes — the May diagnosis stands; Apple did not build frontier research capacity |
| Did Apple *become*? | No. Style moved toward hardware, not research; the AI org was dissolved, not elevated |
| Did Apple *buy*? | Yes. A multi-year, non-exclusive Gemini licence for Apple Foundation Models |
| Which Shared Value made buying preferable? | Secrecy — the publish-openly culture a frontier lab needs is the one Apple has never tolerated |
| What is the new, unscored risk? | A Hard-S dependency on a direct competitor for the capability the Strategy is built on. 7S has no cell for "supplier concentration on a rival"; it has to be carried as a Strategy caveat |

The test's value is that it separates two things the framework's own vocabulary blurs: **alignment** (all seven S's pointing the same way) and **self-sufficiency** (the S's belonging to you). Apple in September 2026 is *more aligned* than in May and *less self-sufficient*. A 7S score that reports only the first will read the Gemini deal as a clean win. Report both.

For the mirror image, a company that tried to buy, priced the gap, and then chose to become, see [The Auction Test on Netflix's Warner Bros. bid](/examples/netflix-vrio-analysis-2026#the-auction-test).

The next test of this page is Ternus's first full product cycle: if the 2027 lineup ships with in-house foundation models displacing Gemini, Apple "became" after all and this section is wrong. The falsifier is concrete and dated — the same discipline as the [pre-registered quadrant](/examples/apple-ansoff-matrix-2026#the-pre-registered-quadrant) on the Ansoff page.

## Key takeaway

The Apple McKinsey 7S story in 2026 is that the Hard S's (Strategy, Structure, Systems) are aligned and world-class, while two of the four Soft S's (Skills, Staff) have drifted relative to the AI-services strategy, and a third (Style) creates structural friction with the modern frontier-ML culture. The Shared Values element is the load-bearing constraint — privacy and design excellence are genuine differentiators, but they also bound the AI-quality strategy in ways most analyst coverage doesn't acknowledge.

The framework's contribution is to refuse the "Apple just needs to ship better AI" simplification and ask which of the seven elements would have to change for the AI Strategy to actually execute. The answer is at least three (Skills, Style, Staff), and the three that need to change are exactly the ones that are slowest to shift. The strategic outcome over 2026-2028 will be set largely by how quickly Apple is willing — and able — to move on those three.

In May, the single variable to track was senior ML hiring from frontier labs. As of September that indicator has fired once and been overtaken by a bigger move: Apple licensed the frontier model instead of hiring the people who build them. **The single variable to track now is the share of Apple Foundation Models that runs on Apple's own weights versus Google's** — because that number, not the hiring count, is what tells you whether Apple bought its way to alignment or is on its way to becoming aligned.

*Cover photo: [Patrick Perkins on Unsplash](https://unsplash.com/photos/3wylDrjxH-E).*

> **Want to run 7S on your own org?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=apple-7s-example) walks all seven elements — the three hard, the four soft — with AI-assisted prompts. Free to start.

## Related

- [McKinsey 7S Framework: Hard and Soft Elements](/academy/mckinsey-7s-framework-hard-soft-elements) — the underlying split + the Hard-Soft Asymmetry Rule
- [McKinsey 7S framework](/frameworks/mckinsey7s) — the seven elements + how to score them
- [PSG McKinsey 7S: the post-Mbappé team-first reset](/examples/psg-mckinsey-7s-2026) — 7S on a football club; the clean soft-S vs hard-S case
- [SpaceX–Cursor Acquisition: a McKinsey 7S Integration Analysis (2026)](/examples/spacex-cursor-mckinsey-7s-2026) — 7S on an M&A deal; the soft-S retention risk in a $60B acquihire
- [Apple PESTEL Analysis 2026](/examples/apple-pestel-analysis-2026) — same company, macro-environment lens
- [Tesla VRIO Analysis 2026](/examples/tesla-vrio-analysis-2026) — resource-based view on a different company
- [Microsoft Porter's Five Forces Analysis 2026](/examples/microsoft-porters-five-forces-analysis-2026) — industry-level analysis for contrast
- [Amazon PESTEL Analysis 2026](/examples/amazon-pestel-analysis-2026) — multi-segment macro analysis

---

### Apple PESTEL Analysis 2026
URL: https://frameworklist.com/examples/apple-pestel-analysis-2026
> A working PESTEL analysis of Apple in 2026 — DOJ antitrust trial, China-India manufacturing pivot, Apple Intelligence rollout, EU DMA enforcement, App Store legal headwinds, and the 2030 carbon-neutrality commitment. Six macro forces shaping the next 24 months.

![Photograph of an Apple Store interior with glass facade and minimalist product displays](https://images.unsplash.com/photo-1491933382434-500287f9b54b?auto=format&fit=crop&w=1600&q=80)

Apple in 2026 looks healthy on the surface. Services revenue keeps growing, the installed base keeps expanding, and the iPhone still prints cash. But the operating model that produced those numbers — a vertically integrated hardware leader monetizing a captive software ecosystem at a 30% take rate — is being attacked from six different directions at once. The PESTEL framework was built for exactly this case: a macro-environment scan that scores forces a company *cannot* control, in contrast to a Porter's analysis of forces within its industry.

Run cleanly on Apple in May 2026, PESTEL surfaces an awkward truth — five of the six forces are tightening, and the one that's neutral (Technological) is a coin-flip because the on-device AI bet is racing against cloud-LLM improvement curves Apple doesn't set.

## Position being analyzed

Mid-2026: the DOJ App Store antitrust trial is in pre-trial motions, the EU DMA has been in active enforcement for two years, Apple Intelligence has shipped on the iPhone 16/17 line but consumer perception lags ChatGPT and Gemini, India assembly accounts for an estimated 25% of iPhone output and rising, Vision Pro is a niche product still searching for its mainstream moment, and the 2030 carbon-neutral commitment is on its hardest milestone yet (Scope 3 supply-chain emissions). The strategic question PESTEL helps with: which macro force is most likely to bend Apple's 2027–2028 trajectory?

| Metric | Value | Direction vs. 12 months ago |
|---|---|---|
| Services revenue / YoY growth | ~$26B/Q / +13% | Stable from +14% |
| iPhone revenue / YoY growth | ~$70B/Q / +2% | Down from +6% |
| Installed base (active devices) | 2.3B+ | Up from ~2.2B |
| India share of iPhone assembly | ~25% | Up from ~14% |
| App Store take rate (effective, post-DMA) | ~22-26% (EU); 27% (US small business) | Down from ~30% (pre-DMA EU) |
| 2030 carbon-neutral progress | Scope 1+2 ~95%; Scope 3 ~38% | Scope 3 slow |
| DOJ antitrust case stage | Pre-trial motions, trial 2027 | Advanced from filing 2024 |

## PESTEL applied

### Political — DOJ + US-China decoupling

The Political force is two stories braided together. The first is *United States v. Apple Inc.* — the DOJ's 2024 monopoly case alleging Apple uses its smartphone monopoly to suppress competition in messaging, smartwatches, and digital wallets. The trial timeline now points to 2027, which means 2026 is the "discovery + motions" year where settlement pressure is highest. A consent decree that opens up iMessage, NFC, and the App Store API would be a material change to the services margin profile.

The second is the US-China decoupling pressure on assembly. China export controls on rare earths, US tariffs on Chinese-assembled electronics, and Beijing's domestic-tech push (the "Apple ban" inside Chinese state enterprises) all push Apple to diversify. India is the relief valve, Vietnam is the secondary one, and the cost of the move is the binding constraint on speed.

### Economic — slowing premium upgrade cycle, services compensating

The premium smartphone segment is mature. Consumers in developed markets are holding phones longer (4+ years average), enterprise refresh cycles have stretched, and emerging market growth slowed when prices crossed $800. iPhone revenue growth is now in the low-single-digits and is being offset by services and a quietly massive advertising business inside the App Store and Apple TV+. The risk: if services growth normalizes from +13% to high-single-digits while iPhone stagnates, the overall growth narrative gets thin.

The Vision Pro headset, still selling at roughly the rate of the original Apple Watch in year two, is the product line Apple needs to convert from R&D burden to growth driver. The 2026 question is whether Vision Pro 2 with a sub-$2,000 price reframes the category or remains a luxury demo.

### Social — AI literacy moving faster than Apple's cadence

The Social force is the most uncomfortable for Apple. Consumer expectations of AI capability have been reset weekly by ChatGPT, Gemini, and Claude — every cloud LLM ships material improvements on a 4-8 week cadence. Apple's product cadence is annual. Apple Intelligence shipped strong on-device privacy properties but feels behind on the conversational capability consumers now expect, and the lag is measured in months, not quarters.

The countervailing Social force is privacy positioning, which is still genuinely strong with users who care about it (paying customers in developed markets) and a real differentiator in B2B and education channels. The brand equity hasn't moved, but it's being asked to absorb more weight.

### Technological — on-device AI moat vs cloud-LLM improvement curve

The Technological force is the coin flip. Apple Silicon (M4, M5) remains the best consumer compute platform shipping today, and the neural engine plus unified memory architecture genuinely supports on-device AI that competitors can't replicate on commodity hardware. That's a durable moat.

The challenge is that the *user-facing* AI experience is judged against cloud models — and cloud models will always have more parameters, fresher data, and the ability to ship improvements continuously. Apple's bet is that for the majority of consumer AI tasks, on-device + private + free is sufficient. That bet is plausible but unproven. If it works, Apple owns a defensible position. If it doesn't, the iPhone becomes a thin client for someone else's model.

### Environmental — Scope 3 is the binding milestone

Apple's 2030 carbon-neutral commitment is the most credible such commitment from a hyperscaler-adjacent company. Scope 1 (direct emissions) and Scope 2 (purchased electricity) are nearly complete. Scope 3 — the supply chain — is at roughly 38% and is the hard part. Aluminum smelting, chip fabrication (TSMC), and shipping account for most of what's left.

The Environmental force is also coupled to the Political and Economic forces: the India manufacturing pivot is *worse* for Scope 3 in the near term because grid intensity in Indian states is higher than the Chinese coastal regions Apple is moving away from. This is the kind of cross-force coupling PESTEL exists to surface.

### Legal — EU DMA is the largest active legal lever

The EU Digital Markets Act has been in enforcement since 2024. Apple has been required to open the App Store to alternative payment processors, support third-party app marketplaces in the EU, and disclose self-preferencing in search rankings. The effective EU take rate has dropped from 30% to a contested 22-26% (depending on which fees survive litigation). Annual EU fines and reserves are now in the low billions of euros and rising.

The DMA matters more than the DOJ case in 2026 because it's already operative — the App Store revenue impact is hitting the books today, while the DOJ outcome is 18-24 months out. Other regions (UK, Japan, South Korea) are watching and modelling the EU approach. The Legal force compounds: every successful EU action increases the political pressure for similar action elsewhere.

## Counter-argument

The bull case is straightforward: the iPhone installed base is still growing, services is still a $100B+ run-rate business with category-leading margins, and Apple Intelligence is a multi-year program that will look better in 2028 than in 2026. The DOJ case is slow and may settle on terms Apple can absorb. The DMA fines are real but bounded as a percentage of revenue. Vision Pro is early but optionality.

PESTEL doesn't refute this — it forces the question of *which force compresses the bull case first*. If services growth slows from 13% to 8% (a plausible Economic + Legal outcome), the headline growth story changes from "Apple is becoming a services company" to "Apple is a slow-growing services company." That re-rating is what the framework warns about.

## Signals to watch (next 18 months)

| Signal | Force | Why it matters |
|---|---|---|
| DOJ settlement terms or trial start | Political/Legal | The binary outcome that re-prices the services multiple |
| EU effective take rate | Legal | Forward indicator for UK / Japan / Korea action |
| Apple Intelligence consumer NPS vs cloud LLMs | Technological/Social | Tells you if the on-device bet is converting |
| iPhone average selling price | Economic | Detects whether the upgrade cycle is reactivating |
| India assembly cost per unit | Political/Economic | The decoupling tax landing on COGS |
| Scope 3 emissions trajectory | Environmental | The 2030 commitment's binding constraint |
| Vision Pro 2 unit volume | Economic | Whether the category exists outside enthusiasts |

## Key takeaway

The Apple PESTEL story isn't that any single force breaks the company. It's that five forces are tightening simultaneously, the one neutral force (Technological) is a contested bet, and the company's strategic narrative ("Apple is becoming a services company") depends on a take rate the Legal force is actively dismantling. PESTEL's contribution is the *cross-force coupling* view that no single industry analysis captures — and the picture it paints in May 2026 is that Apple isn't broken, but the operating model that produced the last decade's returns is being renegotiated piece by piece.

The framework doesn't tell you what Apple should do. It tells you what to watch — and the answer is that the App Store take rate is the single metric that compresses the most other forces simultaneously. If you only have time to track one number, track that one.

*Cover photo: [Laurenz Heymann on Unsplash](https://unsplash.com/photos/L3HZ-0jVQRY).*

> **Want to run PESTEL on your own market?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=apple-pestel-example) scans all six macro factors with AI-assisted prompts and scores each one. Free to start.

## Related

- [How to Do a PESTEL Analysis](/academy/how-to-do-a-pestel-analysis) — the 6-step method + the Materiality Filter for ranking the six forces
- [PESTEL framework](/frameworks/pestel) — the full template and quadrant definitions
- [Apple McKinsey 7S Analysis 2026](/examples/apple-mckinsey-7s-analysis-2026) — same company, internal-alignment lens; re-scored in September 2026 after the Cook → Ternus CEO change
- [McKinsey 7S Framework: Hard and Soft Elements](/academy/mckinsey-7s-framework-hard-soft-elements) — explainer for the Hard/Soft split + the Hard-Soft Asymmetry Rule
- [Amazon PESTEL Analysis 2026](/examples/amazon-pestel-analysis-2026) — a sibling analysis where the macro forces look very different
- [Nike PESTEL Analysis (2026)](/examples/nike-pestel-analysis-2026) — a sibling analysis where one force (tariffs) dominates the whole grid
- [Porter's Five Forces beginner's guide](/academy/porters-five-forces-beginners-guide) — when to use Five Forces *instead of* PESTEL
- [Netflix Porter's Five Forces Analysis 2026](/examples/netflix-porters-five-forces) — an industry-bounded analysis for contrast

---

### PESTEL Analysis of Argentina (2026): which reforms are locked
URL: https://frameworklist.com/examples/argentina-pestel-analysis-2026
> A PESTEL analysis of Argentina in 2026: inflation at 1.7% a month, poverty back up to 32.3%, a tied 2027 runoff, and the Lock-In Ladder for Milei's reforms.

![The Obelisco de Buenos Aires towering over 9 de Julio Avenue](https://images.unsplash.com/photo-1589909202802-8f4aadce1849?auto=format&fit=crop&w=1600&q=80)

Argentina's monthly inflation fell to **1.7%** in August 2026, the lowest reading in 14 months. Two weeks later INDEC published the other number: **32.3%** of people in its urban survey were poor in the first half of the year, up from **28.2%** six months earlier. Between those two releases, the economy posted its first quarterly contraction since 2024.

Most PESTEL analyses of Argentina would score those cells and stop. That misses the main question about Argentina in 2026. The reforms of 2024-26 are large: a new labour law, a rewritten glacier law, a 30-year investment regime and a trade treaty with the EU. The country votes again on **24 October 2027**, and the polls show a tied runoff. A score for each cell means little until you know how easily the next government could undo it.

A [PESTEL analysis](/frameworks/pestel) scans six external macro forces: Political, Economic, Social, Technological, Environmental and Legal. It asks whether each one favours the decision in front of you. This is the ninth country page in the series. The [USA](/examples/usa-pestel-analysis-2026) had one force holding up the other five. [Canada](/examples/canada-pestel-analysis-2026) had one force rewriting them. [China](/examples/china-pestel-analysis-2026), [India](/examples/india-pestel-analysis-2026) and [Mexico](/examples/mexico-pestel-analysis-2026) had cells that split by ledger, by who can move them and by when you committed. Argentina's cells split by **what holds them in place**.

## Position being analyzed

The decision this analysis is built for: **a company deciding in late 2026 whether to commit capital in Argentina whose payback runs past the October 2027 election.** That covers most capital: a mine, a plant, a distribution network, a hiring plan.

| Indicator | Latest reading | As of |
|---|---|---|
| Monthly inflation, August 2026 | **1.7%** (core 1.8%, regulated prices 2.2%) | INDEC, 10 September 2026 |
| Inflation, year on year / year to date | **33.5% / 21.3%** | INDEC |
| GDP, Q2 2026 | **−0.6%** q/q, first contraction since 2024; **+2.0%** y/y | INDEC, 17 September 2026 |
| Private consumption, Q2 2026 | **−2.4%** q/q | INDEC |
| Unemployment, Q2 2026 | **7.9%** (from 7.8%) | INDEC |
| Poverty / extreme poverty, H1 2026 | **32.3% / 7.5%** (from 28.2% / 6.3% in H2 2025) | INDEC, 24 September 2026 |
| RIGI projects approved | **23**, worth **US$49.77bn**; US$159.48bn under evaluation | Economy Ministry, 2 October 2026 |
| 2026 primary surplus target (IMF programme) | **1.4% of GDP**, cut from 2.2% | IMF third review, mission from 21 September 2026 |
| Exports to the US, January-July 2026 | **~US$6bn, +38%** | Buenos Aires Times, 31 August 2026 |
| Head-to-head poll, 2027 | **Peronism 35.9% / La Libertad Avanza 35.1%** | The Rio Times, September 2026 |

## Political — a stable government with a tied election ahead

The government passed its two hardest bills in the first half of 2026: the labour reform in February and the glacier reform in April. It also ratified the EU-Mercosur trade agreement by 69 votes to 3 in the Senate. On legislation, 2026 was Milei's strongest year.

His ratings are moving the other way. In September 2026 Zuban Córdoba found **61.8%** of respondents viewed him negatively (16-19 September), AtlasIntel for Bloomberg found **58%** disapproval, and Universidad de San Andrés found **61%**. He still leads first-round voting intention because the opposition is divided. In a straight two-way contest, one poll had Peronism at **35.9%** and his party at **35.1%**.

**Score: favourable to new commitments today, and a coin toss for anything that has to survive October 2027.** This is the cell that changes the value of every other cell, which is why the ladder below exists.

## Economic — falling inflation, contracting output

Inflation has come down, and that part of the stabilisation is real. Monthly inflation has gone from double digits in late 2023 to **1.7%** in August 2026. The peso floats inside an exchange-rate band launched in April 2025, and since January 2026 the band's limits have been adjusted each month for inflation.

Output did not follow. GDP fell **0.6%** in the second quarter, the first quarterly contraction since 2024. The quarter's composition is the key finding in this cell:

| Q2 2026 | Change | Contribution to the 2.0% annual growth |
|---|---|---|
| Mining | **+16.4%** | **+0.62 points** |
| Agriculture and livestock | **+6.9%** | **+0.81 points** |
| Manufacturing | **−2.1%** | **−0.30 points** |
| Private consumption (q/q) | **−2.4%** | — |
| Gross fixed capital formation (q/q) | **−0.8%** | — |
| Exports (q/q, seasonally adjusted) | **+2.5%** | — |

The economy grew in the export sectors that earn dollars and shrank in the ones that sell to Argentine households. The IMF programme has also loosened: the 2026 primary surplus target was cut from **2.2%** of GDP to **1.4%** before the third review mission arrived in September.

**Score: favourable for export projects priced in dollars; adverse for anything that depends on domestic demand.**

## Social — poverty is rising again

INDEC's 24 September release showed the first rise in poverty under Milei: **32.3%** of people in the urban survey, about **9.7 million**, were poor in the first half of 2026, up from **28.2%**. Extreme poverty rose from **6.3%** to **7.5%**. The poverty line is set by the cost of a basic basket, and that basket rose faster than headline inflation while household incomes stopped catching up.

The labour market shows the same split. Unemployment rose to **7.9%**, formal private employment fell for **13 consecutive months** through June, and industry lost **4.5%** of its registered jobs over twelve months. About **45%** of employed people work informally.

**Score: adverse, and it feeds the Political cell directly.** For a business, a falling poverty rate after 2024 was part of the case that the reforms would win a second mandate. The rise in 2026 weakens that case.

## Technological — a large plan with no legal framework yet

The headline project is Stargate Argentina: a **US$25 billion**, up-to-**500MW** AI data centre in Patagonia, announced in October 2025 as a letter of intent between OpenAI and Sur Energy. The regime it would need is not law yet. The **Súper RIGI**, which offers 30-year stability, a 15% income tax rate and full duty exemption to projects of at least **US$1 billion** in industries Argentina does not yet have (AI, semiconductors, data centres, batteries, copper refining), passed the Chamber of Deputies **130-106** on 24 June 2026. In September it stalled in the Senate committee, where UCR, PRO and dissident Peronist senators demanded changes on local-supplier content.

**Score: neutral today. The best-known technology project in the country is on the lowest rung of the ladder below.**

## Environmental — the glacier law moved the decision to the provinces

The 2010 Glacier Law banned mining in glacier and periglacial zones. The 2026 reform, passed by the Senate **40-31** in February and the Chamber of Deputies **137-111** on 9 April, lets each province decide which of Argentina's roughly 17,000 glaciers and ice bodies have a "relevant water function" and keeps protection only for those. That opens Andean copper projects such as BHP and Lundin's **US$18 billion** Vicuña, Glencore's El Pachón and First Quantum's Taca-Taca. The government projects **US$165 billion** of mining exports by 2035.

The reform is being challenged in court. FARN, the Asociación Argentina de Abogados/as Ambientalistas and Greenpeace filed what they call the largest collective lawsuit in the country's history. They cite a 2019 Supreme Court precedent that glacier protection is a federal responsibility.

**Score: favourable for miners, but held by a law under constitutional challenge, so it is not settled.**

## Legal — two new laws, one regime, one treaty

| Change | In force | What it does | What holds it |
|---|---|---|---|
| **Labour Modernisation Law (Law 27,802)** | Published 6 March 2026; fully in force from 8 May after an injunction was lifted | Cheaper and more predictable dismissals, an "hours bank" trading overtime pay for time off, wages payable in dollars, 75% minimum service in essential sectors during strikes, a 1-2.5% payroll severance fund from 1 November 2026 | Ordinary law; constitutionality not yet ruled on; the CGT has appealed to the ILO |
| **Glacier Law reform** | Passed 9 April 2026 | Provinces decide which glaciers keep protection | Ordinary law; collective constitutional challenge filed |
| **RIGI** | Since the 2024 Ley Bases | 30-year tax, customs and FX stability for qualifying projects | Law plus a 30-year stability commitment enforceable by international arbitration |
| **EU-Mercosur interim trade agreement** | Provisionally applied from 1 May 2026 | Tariff cuts and preferential access with the EU | Treaty; Argentina ratified 26 February 2026 |
| **US-Argentina reciprocal trade agreement (ARTI)** | Signed 5 February 2026; **not yet ratified** | US tariffs removed on 1,675 Argentine products; 100,000-tonne beef quota | Signature only; in late August USTR asked for it to be sent to Congress |

**Score: favourable on paper.** The scores vary much more by the right-hand column than by the middle one, and that is the anchor of this analysis.

## PESTEL scorecard for Argentina, September 2026

| Force | Score for a commitment that ends before October 2027 | Score for one that runs past it | The fact that sets it |
|---|---|---|---|
| **Political** | Favourable | **Uncertain** | Head-to-head poll 35.9% vs 35.1% |
| **Economic** | Favourable for exporters, adverse for domestic demand | Same, if the band and the surplus survive | Q2: mining +16.4%, manufacturing −2.1%, consumption −2.4% |
| **Social** | Adverse | Adverse, and a political risk | Poverty 28.2% → 32.3% |
| **Technological** | Neutral | Neutral until the Súper RIGI passes | Súper RIGI stalled in the Senate |
| **Environmental** | Favourable for mining | Depends on the courts | Glacier reform under collective challenge |
| **Legal** | Favourable | **Depends on the instrument** | Law vs RIGI contract vs treaty |

## The Lock-In Ladder

The second column of the scorecard says "depends" in most rows. That means the six forces are the wrong unit for Argentina in 2026. The useful unit is the **instrument**: what kind of legal act holds the reform, and what it would take to undo it.

> **The Lock-In Ladder: for each cell that matters to your decision, find the instrument holding it and place it on one of five rungs. The rung tells you what a change of government can do to it. Score the cell for the full length of your commitment only from rungs 3 and 4.**

| Rung | Instrument | Argentine examples, 2026 | What a new government can do |
|---|---|---|---|
| **0. Announcement** | Letter of intent, half-passed bill | Stargate Argentina (LOI, Oct 2025); Súper RIGI (Deputies only) | Nothing needs undoing; it was never binding |
| **1. Executive policy** | Central bank or ministry decision, decree | The FX band; the primary surplus target; a signed but unratified treaty such as ARTI | Change it on day one |
| **2. Ordinary law** | Act of Congress | Labour Law 27,802; the glacier reform | Repeal with a congressional majority, or lose in court without any election |
| **3. Law plus contract** | Stability commitment with international arbitration | RIGI: 23 projects, US$49.77bn, 30 years | Breach it, and face arbitration claims |
| **4. Treaty in force** | Ratified international agreement | EU-Mercosur interim agreement, applied since 1 May 2026 | Withdraw, at a diplomatic and trade cost |

Put the Q2 GDP table next to this one and they line up. The sector that grew fastest, mining (+16.4%, which in INDEC's accounts includes oil and gas), is the one with a rung-3 instrument behind it: most of the approved RIGI money is in Vaca Muerta oil and gas. The newest approval, Pluspetrol and GyP's **US$12.24 billion** Bajo del Choique–La Invernada project on 2 October, sends more than **92%** of its output abroad. Agriculture's growth comes mostly from the harvest. But its export channel now runs on a rung-4 treaty with the EU and a 38% rise in sales to the US. The sectors that shrank, manufacturing and household consumption, depend on rung-1 and rung-2 policies and cannot buy a higher rung: RIGI requires at least **US$200 million** per project in most sectors.

That is the finding. **Argentina's reform is real, but only large projects can lock it in.** A company can make its own exposure as secure as the instrument it qualifies for, and most companies only qualify for rungs 1 and 2.

This is close to the [Ballast Test](/examples/france-pestel-analysis-2026) used for France, which sorts commitments by the instrument they depend on. It differs in two ways. First, **the order of the rungs depends on who the threat is.** In France the threat was a hung National Assembly, so executive programmes and commercial contracts survived and ordinary laws did not. In Argentina the threat is a new president with a new congressional majority, so executive policy is the *weakest* rung, the one France found strongest. Rank the instruments against the actor who could reverse them, not in general. Second, the Ballast Test looks back at what survived. The Ladder looks forward, and in Argentina a higher rung can be bought: RIGI turns a rung-2 exposure into a rung-3 one for any project above the threshold.

### How to use the ladder on your own decision

1. **List the three cells your payback depends on.** For a mine: the glacier law, the FX regime, export taxes. For a consumer brand: the band, real wages, import rules.
2. **Find each cell's instrument.** "The government's policy" is not an answer; find the decree, law, contract or treaty.
3. **Shorten the commitment to the date a rung-1 or rung-2 cell can change.** For Argentina in 2026 that is the 10 December 2027 inauguration, or a court ruling, whichever comes first.
4. **Or buy a higher rung.** If the project is large enough, structuring it inside RIGI turns a rung-2 exposure into a rung-3 one. That is what the US$49.77 billion of approvals are doing.

### One prediction, written down before the data

| | |
|---|---|
| **Placement** | Argentina, late 2026: favourable for rung-3 and rung-4 capital, uncertain past October 2027 for everything else |
| **Prediction** | RIGI approvals keep rising through the campaign and pass **US$60 billion** before the 24 October 2027 first round, whatever the polls show, while INDEC's gross fixed capital formation does **not** grow for two consecutive quarters before the vote |
| **Falsifier** | Either RIGI approvals stall below US$60 billion by the vote (investors do not trust the rung-3 lock against a change of government), or investment grows for two straight quarters (capital outside RIGI is not waiting for the election) |
| **Scored on** | The RIGI committee's cumulative tally before 24 October 2027, and INDEC's Q2 2027 GDP release (September 2027) |

## Counter-argument: Argentina has broken locks before

The strongest objection to rung 3 is Argentina's own record. Argentina has been the respondent in more ICSID arbitration cases than any other country (**59**, ahead of Venezuela's 56). Most of them came from the emergency legislation of the 2001-02 crisis, when the government broke contracts, including stability commitments, that foreign investors had relied on. A 30-year promise from Buenos Aires has failed before.

That is correct, and it changes what the ladder claims. The rungs do not say whether a reform *can* be undone. Every rung can. They say what undoing it **costs** and who pays. Undoing a rung-1 policy costs nothing. A rung-2 law needs a majority or a judge. Breaking a rung-3 contract creates arbitration claims, and Argentina has paid such claims before. Withdrawing from a rung-4 treaty costs access to a 450-million-person market. The 2001-02 crisis shows that Argentina will pay those costs in a crisis. A normal change of government in 2027 is not one. A Peronist government in 2028 could reverse a decree in an afternoon. Breaking a RIGI contract would mean a new series of arbitration cases while it tries to borrow abroad.

The second objection is that the 2026 data say nothing about 2027. That is why the prediction above is dated. If capital outside RIGI starts flowing before the vote, the ladder was too cautious, and the prediction says how that will show.

## Key takeaway

On headline numbers, Argentina in September 2026 looks like a country whose stabilisation worked and whose recovery stalled. Inflation is at 1.7% a month, 23 large projects are approved, and two hard reforms became law. Output fell, consumption fell, and poverty rose by four points in six months. The scan changes when you ask what holds each reform. Growth is concentrated in the sectors that could buy a 30-year contract or export under a treaty. The sectors that rely on executive policy or ordinary law are the ones contracting, and the election that could change those policies is tied.

**If your project is large enough for RIGI, Argentina's environment is favourable and largely locked in until 2056. If it is not, score every cell twice, before and after October 2027, and size the commitment to the shorter one.**

The three releases that will update this analysis at least cost are September's inflation figure (13 October), INDEC's Q3 GDP (December, which shows whether Q2 was a dip or a turn), and the Senate's vote on the Súper RIGI, which would move Stargate Argentina from rung 0 to rung 3.

> Want to run a PESTEL on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a PESTEL worksheet with all six forces and AI assistance for the scan.

## Want to go deeper

- [PESTEL framework](/frameworks/pestel): the six forces, and how to score them
- [How to do a PESTEL analysis](/academy/how-to-do-a-pestel-analysis): the step-by-step method
- [PESTEL analysis of Mexico (2026)](/examples/mexico-pestel-analysis-2026): the other large Latin American economy, where the risk is a US review rather than a domestic vote, and the Entrant Test
- [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026): a commodity exporter facing the same US tariff policy, and the Reversal Test
- [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026): another scan where a vote sets the value of the reforms, and the Two-Clock Score
- [PESTEL analysis of Europe (2026)](/examples/europe-pestel-analysis-2026): the other side of the EU-Mercosur agreement
- [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026): the market behind the 38% export jump, and the Load-Bearing Force Test
- [PESTEL analysis of Japan (2026)](/examples/japan-pestel-analysis-2026): a supermajority government with no election due, where the variable is the price of money, and the Repricing Test
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces): when the macro scan is the wrong tool

*Cover photo: [Nestor Barbitta on Unsplash](https://unsplash.com/photos/QhQ4WgX77G0).*

---

### FC Barcelona BCG Matrix: the economic levers gamble
URL: https://frameworklist.com/examples/barcelona-bcg-matrix-2026
> A BCG Matrix analysis of FC Barcelona — how a club with elite assets but a broken cash engine sold its Question Marks and mortgaged its Cash Cow to survive, and bet the rebuilt Camp Nou rebuilds it.

This is the final entry in our [World Cup 2026 strategy series](/series/world-cup-2026) — the business of football read through strategy frameworks. We've used Ansoff for [FIFA](/examples/fifa-ansoff-matrix-2026) and [Manchester City](/examples/manchester-city-ansoff-matrix-2026), Porter's Five Forces for [Real Madrid](/examples/real-madrid-porters-five-forces-2026), and McKinsey 7S for [PSG](/examples/psg-mckinsey-7s-2026). FC Barcelona gets the fourth and final framework: the BCG Matrix — because Barça's story is a question of *portfolio* and *cash allocation*, which is exactly what BCG was built to analyse.

The puzzle: Barcelona owns some of the most valuable assets in world football — La Masia, a global brand, Lamine Yamal — and yet spent years unable to register players under LaLiga's salary cap. How does a club this rich run out of money? BCG answers it: Barça's problem isn't its assets. It's that its Cash Cow stopped producing enough cash to fund the rest of the portfolio.

## Position being analyzed

Barcelona's [salary cap rose €81m to €432.8m in 2025](https://sports.yahoo.com/articles/official-barcelona-salary-cap-rises-135000021.html), largely on the back of returning to a rebuilt stadium — but it still sits €329m behind Real Madrid's €761m, with an actual wage bill estimated above €500m. To keep operating it pulled its now-famous "economic levers," selling future revenue and stakes in its own ventures. The strategic question BCG answers: which of Barça's units are worth funding, which are being sold, and is the core engine being rebuilt fast enough? The matrix turns "Barça is broke" into a precise portfolio diagnosis.

## Barça's BCG Portfolio Under the Levers

The citable core: each unit placed in the matrix, with what Barça did to it under financial duress.

| Unit | BCG quadrant | Why | What the levers did to it |
|---|---|---|---|
| **La Masia youth core** (Yamal, Cubarsí) | **Star** | High growth, high share — elite output at low cost | Protected — the asset keeping the team competitive cheaply |
| **Women's team** | **Star** | Dominant share in a fast-growing market | Invested in; long-term value builder |
| **Men's 1st team — broadcast/matchday/brand** | **Cash Cow** | High share, mature market; the historic cash engine | Future revenue partly *pre-sold* to raise cash |
| **Barça Studios / Vision / "Barça Media"** | **Question Mark** | High-growth digital media, uncertain share | Stakes sold — 49% of Studios (~€180m), 29.5% of Vision (€120m) |
| **Legacy high-cost wage bill** | **Dog** | Low growth, low return on cost | The drain the levers were pulled to cover |

## The broken Cash Cow

In BCG's original logic, the Cash Cow funds everything else: a mature, high-share unit throws off cash that pays for Stars and Question Marks. Barça's Cash Cow — the men's team's broadcast, matchday, and global commercial revenue — is genuinely high-share, but two things broke it. First, the wage bill (the Dog) grew faster than the Cow's output, so there was nothing left to allocate. Second, the club spent ~900 days away from a demolished Camp Nou during reconstruction, gutting the matchday portion of the Cow precisely when it needed cash most. A Cash Cow that doesn't cover its own herd is the core of Barça's crisis.

## Selling the Cow's future milk

With the Cow underproducing, Barça did something BCG treats as a last resort: it monetised its other quadrants early. The "economic levers" sold **future Cash Cow revenue** (slices of broadcast income) and **stakes in the Question Marks** — roughly 49% of [Barça Studios (~€180m) and 29.5% of Barça Vision (€120m)](https://www.sportbusiness.com/news/barcelona-re-sells-economic-lever-to-raise-e120m-plans-us-flotation-of-barca-media/), with a planned ~$1bn "Barça Media" US listing. In portfolio terms this is coherent only as a bridge: you're pulling tomorrow's cash into today, which lowers future income. It buys survival, but it deepens the hole unless the Cow is rebuilt. That is the whole gamble.

## Rebuilding the Cow: the €1.5bn Camp Nou

The other half of the strategy is the [€1.5bn Spotify Camp Nou rebuild](https://newsroom.spotify.com/2025-11-24/camp-nou-redesign-fc-barcelona/), reopened in November 2025 with a 4-0 win over Athletic Club, [licensed to 62,652 and heading toward ~105,000](https://www.catalannews.com/sports/item/fc-barcelona-gets-licence-to-expand-camp-nou-capacity-to-62652). President Laporta calls it "our most important avenue for revenue growth" — ticketing, hospitality, sponsorship activation, global events, with Spotify's shirt deal running to 2030 and stadium naming to 2034. In BCG terms, after pre-selling the Cow's future milk to survive, Barça is reinvesting in the Cow's *capacity* so it produces more cash going forward. The Stars — La Masia above all — are what keep the team winning cheaply while the Cow is rebuilt.

## Key takeaway

The BCG Matrix turns Barcelona's crisis from "rich club, somehow broke" into a precise portfolio story. The assets were never the problem: the Stars (La Masia, the women's team) are elite and cheap, and the brand is world-class. The problem was a Cash Cow that stopped covering a Dog-sized wage bill, worsened by two years exiled from its stadium. Barça's response — the economic levers — is a portfolio bridge: sell the Cow's future milk and stakes in the Question Marks to fund the present, and bet the rebuilt Camp Nou restores the Cow before the pre-sold revenue and the wage bill catch up. It is a genuine gamble with a clear failure mode (a timing mismatch) and a clear safety net (the academy). BCG's contribution is to make the bet legible: this isn't financial trickery, it's a high-stakes cash-allocation wager — and the new stadium's revenue ramp is the number that decides it.

## Want to go deeper

This is the closing analysis of the [World Cup 2026 strategy series](/series/world-cup-2026). Read more about the [BCG Matrix framework](/frameworks/bcg), see it applied to a very different portfolio in the [Nvidia BCG Matrix analysis](/examples/nvidia-bcg-matrix), or browse [strategy framework examples applied to real companies](/examples). For the rest of the football series, see [Real Madrid Porter's Five Forces](/examples/real-madrid-porters-five-forces-2026) (Barça's great rival, read through industry structure), the [PSG McKinsey 7S](/examples/psg-mckinsey-7s-2026), and the [Manchester City Ansoff Matrix](/examples/manchester-city-ansoff-matrix-2026). To run a BCG analysis on an organisation you're tracking, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each quadrant.

For FC Barcelona's SWOT counterpart, see our sister site [SWOTPal's FC Barcelona SWOT analysis](https://swotpal.com/examples/fc-barcelona-swot-analysis?utm_source=frameworklist&utm_medium=referral&utm_campaign=bcg-barcelona) — a dedicated AI SWOT tool, free for the basic workflow.

---

### PESTEL Analysis of Canada (2026): the reversal economy
URL: https://frameworklist.com/examples/canada-pestel-analysis-2026
> A PESTEL analysis of Canada in 2026 — a collapsed trade negotiation, seven withdrawn federal policies in 18 months, and a population that is now shrinking.

![Photograph of a container ship loaded with stacked shipping containers at a port terminal](https://images.unsplash.com/photo-1670121180530-cfcba4438038?auto=format&fit=crop&w=1600&q=80)

Most country PESTELs on Canada could have been written in 2015 and reprinted every year since: stable parliamentary democracy, resource-rich open economy, high immigration, multicultural society, strong rule of law, ambitious climate policy. Every clause in that sentence is either now wrong or has been materially reversed. The population is falling. The consumer carbon tax has been repealed. The oil and gas emissions cap has been abandoned. And on 21 August 2026 the trade relationship the entire "open economy" claim rests on stopped functioning.

[PESTEL](/frameworks/pestel) scans six external macro forces — Political, Economic, Social, Technological, Environmental, Legal — around an entity. Run on Canada in late August 2026, it produces a shape that is different from the [one-force concentration visible in the United States](/examples/usa-pestel-analysis-2026): not one cell carrying the others, but one cell *rewriting* the others. Four of Canada's six forces have had a major federal policy withdrawn from them in the last eighteen months, and the withdrawals point the same direction.

## Position being analyzed

The decision this analysis is built for: **should a firm treat current Canadian federal policy as a stable planning baseline for the next three to five years?** That is the question a market-entry, capital-allocation, or supply-chain decision actually turns on, and it is the question the standard "politically stable country" boilerplate answers wrongly.

| Indicator | Latest reading | As of |
|---|---|---|
| Real GDP, quarterly | **0.0%** (Q1 2026), after -0.2% in Q4 2025 | 29 May 2026 |
| Bank of Canada policy rate | **2.25%** — sixth consecutive hold | 15 Jul 2026 |
| CPI, year over year | **3.0%** (2.2% excluding gasoline) | 17 Aug 2026 |
| Unemployment rate | **6.4%** — lowest since July 2024 | 7 Aug 2026 |
| Population | **41,417,056**, down 55,025 (-0.1%) in the quarter | 17 Jun 2026 |
| Merchandise exports | **$77.5B** in June — a record month | 4 Aug 2026 |
| US tariff action | **50%** on ~$28B of Canadian goods | 21 Aug 2026 |
| CAD per USD | **1.3760** | 21 Aug 2026 |

Two things in that table are in obvious tension: record exports and a 50% tariff wall. That tension is roughly the whole analysis — the June export record predates the August rupture, and the question is which number describes 2027.

## Political — the force that is rewriting the other five

Canada is governed by Prime Minister Mark Carney's Liberals, who reached a [majority in April 2026](https://www.cbc.ca/news/politics/byelection-liberal-conservatives-carney-majority-government-9.7161054) through by-election wins and floor crossings. Domestic political stability, in the conventional sense, is high. It is also almost irrelevant to the Political cell, because the binding political constraint on Canada is not made in Ottawa.

Two events define it:

**The USMCA joint review, 1 July 2026.** The United States declined to renew the agreement in its current form. The precise USTR language was that *"the United States did not agree to renew the USMCA in its current form. As a result, the USMCA is not renewed."* This is widely misread as termination. It is not — [under Article 34.7, the agreement still runs its 16-year term to 1 July 2036](https://www.whitecase.com/insight-alert/usmca-2026-joint-review-united-states-declines-extend-agreement-triggering-annual), and declining extension instead triggers *annual* joint reviews until the parties agree otherwise. The practical effect is worse than it sounds and better than the headlines: North American trade rules are intact, but their planning horizon has gone from eleven years to one.

**The negotiation collapse, 21 August 2026.** Carney [suspended talks and recalled Canada's negotiators](https://www.pm.gc.ca/en/news/statements/2026/08/21/statement-prime-minister-carney-canada-us-trade-negotiations), citing "last-minute changes in the U.S. proposed terms" that were "unfair, uneconomic, and called into question the reliability of any deal." The US moved to impose 50% tariffs on approximately $28 billion of Canadian goods, effective that midnight. (News coverage generally cites a $20 billion scope; the figure above is from the Prime Minister's own statement — worth noting the discrepancy rather than picking one silently.) Canada's response, [announced the following day](https://www.pm.gc.ca/en/news/speeches/2026/08/22/prime-minister-carney-delivers-remarks-canada-us-trade-negotiations): dollar-for-dollar matching tariffs on steel, dairy, appliances, agricultural equipment, pulp and paper and electronics, effective the Tuesday after Labour Day — 8 September 2026.

For a PESTEL, the important property of this cell is not its severity but its *transmission*. Canadian federal fiscal policy, energy policy, digital taxation and broadcast regulation have all moved in the last eighteen months in ways that are legible only as responses to this relationship. That is what the [Reversal Test](#the-reversal-test) below counts.

## Economic — stalled, not shrinking, with investment as the tell

The headline growth numbers are weak but not alarming. Real GDP was [unchanged at 0.0% in Q1 2026](https://www150.statcan.gc.ca/n1/daily-quotidien/260529/dq260529a-eng.htm) after a 0.2% contraction in Q4 2025. Monthly data improved through the spring — [GDP rose 0.3% in May with an advance estimate of 0.2% for June](https://www150.statcan.gc.ca/n1/daily-quotidien/260731/dq260731a-eng.htm), and industry-side data pointed to roughly 0.8% growth in Q2. The Bank of Canada's July projection puts 2026 growth at **0.7%**, recovering to 1.8% in 2027 and 2028.

Inflation is the reason the Bank has stopped cutting. [CPI rose 3.0% year over year in July](https://www150.statcan.gc.ca/n1/daily-quotidien/260817/dq260817a-eng.htm), up from 2.8% in June, driven almost entirely by gasoline at +25.7%. Excluding gasoline, inflation was 2.2% for a third consecutive month, and shelter inflation was just 1.3%. The Bank has [held at 2.25% for six consecutive decisions](https://www.bankofcanada.ca/2026/07/fad-press-release-2026-07-15/), with the next scheduled for 2 September 2026.

The labour market is the surprise: [unemployment fell to 6.4% in July](https://www150.statcan.gc.ca/n1/daily-quotidien/260807/dq260807a-eng.htm), a third consecutive monthly decline and the lowest since July 2024, on employment growth of 75,000. Note the interaction with the Social cell — an unemployment rate can fall because employment rose *or* because the labour force shrank, and Canada is currently doing both.

The number that actually carries information about the trade rupture is business capital investment, which **fell 0.7% in Q1 2026 for a fifth consecutive quarterly decline.** Interest rates have come down substantially; investment kept falling anyway. That is the signature of uncertainty rather than cost of capital, and it was already true four months before the August collapse.

## Social — a country that has stopped growing

This is the cell where Canada has genuinely changed character, and most PESTELs on Canada still describe the opposite.

Canada's population [fell by 55,025 (-0.1%) in Q1 2026 to 41,417,056](https://www150.statcan.gc.ca/n1/daily-quotidien/260617/dq260617a-eng.htm) — a third consecutive quarterly decline. The mechanism is deliberate: non-permanent residents fell by 117,879 (-4.4%) in the quarter to 2,558,562, and permanent resident admissions fell 20.2% year over year to 83,149. This follows the 2026-2028 Immigration Levels Plan, which [holds permanent admissions at 380,000 per year](https://www.pbo-dpb.ca/en/publications/RP-2526-025-S--demographic-implications-2026-2028-immigration-levels-plan--implications-demographiques-plan-niveaux-immigration-2026-2028) — roughly 20% below the 484,000 admitted in 2024.

Underneath the policy number is a structural one that gets almost no coverage: **natural increase in Q1 2026 was -155.** More deaths than births. Canada has no organic population growth. Every unit of labour force expansion from here is an immigration policy decision, which means a lever that used to be a growth accelerator is now the entire growth mechanism.

Housing, the pressure that drove the immigration cuts, has responded — modestly. The [national average home price was $674,819 in July 2026](https://stats.crea.ca/en-ca/), up just 0.2% year over year, with the MLS Home Price Index down 3.3% year over year. Flat nominal prices against 3.0% CPI is a real-terms decline of roughly 3%. It is affordability improvement by stagnation, not by supply.

## Technological — a large strategy against a thin research base

Canada launched [**AI for All**, a five-year national AI strategy, on 4 June 2026](https://www.pm.gc.ca/en/news/news-releases/2026/06/04/prime-minister-carney-launches-ai-all-canadas-new-national-artificial). Its stated targets: an additional **$200 billion** of economic growth and **250,000** new AI-related jobs over five years, and raising AI adoption from "just over 12%" today to **60% by 2034**. It is backed by the [Canadian Sovereign AI Compute Strategy](https://ised-isde.canada.ca/site/ised/en/canadian-sovereign-ai-compute-strategy), a roughly $2 billion five-year commitment covering compute access, infrastructure build, and public supercomputing.

The strategy should be read against the base it starts from. Canada's R&D intensity was [**1.81% of GDP in 2022**, against an OECD average of 2.73%](https://www150.statcan.gc.ca/n1/daily-quotidien/241203/dq241203c-eng.htm) — the most recent intensity ratio Statistics Canada has published in that comparison. Getting adoption from 12% to 60% is not primarily a compute problem; it is a business-investment problem, and business investment has declined for five straight quarters.

This cell also contains the clearest single instance of the reversal pattern. Canada's 3% digital services tax — a genuine revenue measure and a genuine US irritant — was [rescinded, retroactively, with the CRA required to refund all payments with interest](https://www.pwc.com/ca/en/services/tax/publications/tax-insights/canada-digital-services-tax-act-2025.html). The original announcement, in June 2025, was explicitly made in anticipation of a trade arrangement with the United States. That arrangement is the one that collapsed on 21 August.

## Legal — a regulatory retreat, and a vacuum where AI law should be

Two threads matter, and they run opposite ways.

**Broadcast and streaming regulation is being dismantled mid-flight.** On 21 May 2026 the CRTC issued regulations requiring streaming services to contribute 15% of annual Canadian revenues. On 3 June the responsible Minister directed the CRTC to review that decision. Then, in [a letter to the Federal Court of Appeal dated 17 July 2026](https://www.michaelgeist.ca/2026/07/starting-over-court-filing-confirms-the-crtcs-streamer-contribution-decisions-are-dead-with-a-full-online-streaming-act-reset-to-come/), the Department of Justice advised that *"the Government's intention is to eliminate the base contribution requirement on streaming services and to provide government funding to replace those contributions."* Under two months from regulation to abandonment. The Online Streaming Act has been identified by USTR as a services trade barrier and a USMCA-review topic — the timing is not incidental.

**Privacy and AI law is a vacuum.** Bill C-27 died on prorogation in January 2025, taking the Consumer Privacy Protection Act and the Artificial Intelligence and Data Act with it. Canada [continues to operate under PIPEDA, enacted in 2000, with no federal AI statute in force](https://iapp.org/news/a/what-2026-may-bring-for-canada's-privacy-reform-efforts). The AI for All strategy promises new legislation; as of late August 2026 no successor bill has been confirmed as tabled. For a firm deploying AI systems in Canada, the planning-relevant fact is that the rules do not exist yet and will not be grandfathered.

## Environmental — systematically de-risked

Canada's climate policy in 2026 is the most-changed cell relative to any pre-2025 description, and it moved in one direction.

- **Consumer carbon pricing: gone.** Fuel charge rates were set to zero effective 1 April 2025, and [Bill C-4 received royal assent on 12 March 2026](https://www.parl.ca/DocumentViewer/en/45-1/bill/C-4/royal-assent), repealing Part 1 of the *Greenhouse Gas Pollution Pricing Act*.
- **Industrial carbon pricing: softened, not removed.** A [new federal trajectory took effect 15 May 2026](https://icapcarbonaction.com/en/news/canada-publishes-new-carbon-price-trajectory): $95/tonne in 2026, $100 in 2027, **$115 in 2030**, $130 in 2035. The 2021 pan-Canadian schedule had 2030 at **$170**. Roughly a third of the 2030 stringency was removed.
- **Oil and gas emissions cap: abandoned.** The [27 November 2025 Canada-Alberta memorandum of understanding](https://www.pm.gc.ca/en/news/backgrounders/2025/11/27/canada-alberta-memorandum-understanding) states that *"Canada will not implement the Oil and Gas Emissions Cap."* Note the precise status: the federal government has committed not to implement it, and the draft regulations were never finalized — this is a political commitment, not a completed repeal.
- **Export capacity: expanding.** On 2 July 2026 Canada and Alberta [advanced a proposed one-million-barrel-per-day west coast pipeline](https://www.pm.gc.ca/en/news/news-releases/2026/07/02/canada-and-alberta-advance-west-coast-pipeline-project-proposal-and), with Pembina as private investor and Trans Mountain Corporation leading development, alongside the Pathways carbon capture project targeting 16 million tonnes per year of reductions.

The physical environment, meanwhile, is having a comparatively better year. As of [18 August 2026 Canada had recorded 4,793 wildfires and 4.1 million hectares burned](https://www.newswire.ca/news-releases/the-government-of-canada-provides-an-update-regarding-the-2026-wildfire-season-august-update-811903208.html) — *more* fires than by the same date in 2025 (4,584) but far less area burned (7.7 million hectares), and below the five-year average.

The strategic read: Canada has decided that carbon policy is a competitiveness variable rather than a fixed constraint, and is trading emissions stringency for export capacity. Anyone modelling Canadian energy or heavy industry on the 2021 policy schedule is modelling a country that no longer exists.

## PESTEL scorecard for Canada, August 2026

| Force | Direction | Strength | What would flip it |
|---|---|---|---|
| **Political** | Sharply negative | Dominant | A resumed negotiation before the 8 Sept retaliation date; or a USMCA extension agreed at a future annual review |
| **Economic** | Weakly negative | Moderate | Q2 GDP printing at or above the ~0.8% industry-side estimate, plus business investment ending its five-quarter decline |
| **Social** | Negative, structural | Moderate | An upward revision to immigration levels — the only available lever, since natural increase is negative |
| **Technological** | Positive, unproven | Low so far | Business investment turning, which is what converts an adoption target into adoption |
| **Environmental** | Positive for industry | Moderate | A federal reversal *back* toward stringency, or Alberta's frozen industrial price colliding with the TIER recognition commitment |
| **Legal** | Mixed | Low | A successor privacy/AI bill actually tabled; a final decision on streaming contributions |

## The Reversal Test

Most country PESTELs count what a government has *introduced*. That biases the scan toward whichever party is in power and toward whatever was announced most recently. The more informative count is the opposite one.

> **The Reversal Test.** When scanning a country, count the significant policies **withdrawn, repealed, suspended, or abandoned** during the scan window. A high reversal count concentrated in a short period means the country's policy environment is being set, at least partly, outside its own borders — which means Political is not one of six independent forces. It is the channel through which an external force reaches the other five. Treat every remaining policy in the scan as provisional at the same rate.

Canada's count, over the eighteen months to August 2026:

| Date | Policy withdrawn | PESTEL force | Proximate driver |
|---|---|---|---|
| 1 Apr 2025 | Consumer carbon fuel charge zeroed (repealed by Bill C-4, 12 Mar 2026) | Environmental | Affordability |
| 29 Jun 2025 → 26 Mar 2026 | Digital services tax rescinded, retroactively, with refunds plus interest | Legal / Technological | US trade |
| 27 Nov 2025 | Oil and gas emissions cap — commitment not to implement | Environmental | Energy competitiveness |
| 2026–2028 plan | Permanent resident admissions cut to 380,000/yr, ~20% below 2024 | Social | Housing and services |
| 14 Apr 2026 | Federal fuel excise tax suspended through 7 Sept 2026 | Economic | Affordability |
| 15 May 2026 | Industrial carbon price for 2030 cut from $170 to $115/tonne | Environmental | Industrial competitiveness |
| 17 Jul 2026 | Online Streaming Act base contribution to be eliminated | Legal | US trade |

**Seven reversals, spanning four of the six PESTEL forces.** Three trace directly or indirectly to the trade relationship; the rest trace to cost-of-living and competitiveness pressures that the same relationship intensifies.

The finding that makes this diagnostic worth running, rather than merely descriptive: **the reversals did not buy the deal.** The digital services tax was rescinded in explicit anticipation of a US trade arrangement. The streaming levy — a named USTR irritant — was abandoned in July. Six weeks later, on 21 August, the negotiation collapsed and 50% tariffs landed anyway. A planner who had treated each withdrawal as a de-risking event would have concluded the relationship was stabilising, right up to the point it broke.

That is the practical output. It is not that reversals are bad policy — several are defensible on their own terms. It is that **a high reversal count is a measure of how little the current policy baseline predicts the future one**, and it should be applied symmetrically: the same volatility that removed the carbon tax and the DST can remove the AI strategy, the immigration plan, and the pipeline commitment.

## Counter-argument: isn't this just responsive government?

The strongest objection is that a democracy adjusting policy in the face of a tariff war and an affordability crisis is functioning correctly, and that calling it "reversal" smuggles in a judgement. Fair — and the test is deliberately built to avoid that judgement. It does not ask whether each reversal was correct. It asks how many there were.

The second objection is more serious: seven items in eighteen months might simply reflect a change of government, with a new Prime Minister clearing out a predecessor's agenda. That is partly true and it does not rescue the baseline. Whether volatility comes from external pressure or from a transition, the planning implication is identical — the policy in force today is a poor predictor of the policy in force in 2029. And two of the seven (the streaming contribution and the industrial price trajectory) reverse decisions made by *this* government, some within two months of being issued.

The honest limitation: the Reversal Test is a one-sided count. It has no denominator. A country that introduces thirty policies and withdraws seven is in a different position from one that introduces seven and withdraws seven, and this analysis does not build the introduction column. Read it as a volatility indicator, not as a direction-of-travel indicator.

## Key takeaway

Canada in August 2026 fails the "stable planning baseline" test that most country PESTELs implicitly grant it — not because its institutions are unstable, but because its policy is being reset from outside. The Political cell is not one of six forces; it is the transmission channel, and the evidence is that four of the other five cells have had a major federal policy removed from them in eighteen months.

For a firm making a three-to-five-year Canadian commitment, the operational conclusion is specific: **anchor the decision on things the Reversal Test cannot touch** — geography, resource endowment, the existing installed base, and the physical export infrastructure now being built — and treat carbon pricing, immigration levels, digital taxation, and sector-specific levies as provisional inputs with roughly an eighteen-month half-life. The two dates that will most cheaply update this analysis are 28 August 2026, when Statistics Canada publishes Q2 GDP, and 8 September 2026, when Canada's retaliatory tariffs are scheduled to take effect.

> Want to run a PESTEL on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a PESTEL worksheet with all six forces and AI assistance for the scan.

## Want to go deeper

- [PESTEL framework](/frameworks/pestel) — the six forces, and how to score them
- [How to do a PESTEL analysis](/academy/how-to-do-a-pestel-analysis) — the step-by-step method
- [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) — the same scan on Canada's counterparty, with a different pathology
- [PESTEL analysis of France (2026)](/examples/france-pestel-analysis-2026) — the inverse finding, and the Ballast Test: instability confined to the cells that route through parliament
- [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026) — the Disbursement Gap: six cells with enacted policy and a €500bn fund running at 28% of its own 2026 schedule
- [PESTEL analysis of the European Union (2026)](/examples/europe-pestel-analysis-2026) — six cells governed by different governments, and the Competence Test: score each cell only at the level that holds the lever
- [PESTEL analysis of China (2026)](/examples/china-pestel-analysis-2026) — six cells that each return two readings with opposite signs, and the Two-Ledger Test: score the production reading and the household reading separately and route each to the decision it governs
- [PESTEL analysis of Mexico (2026)](/examples/mexico-pestel-analysis-2026) — the other USMCA partner after the 1 July non-renewal, and the Entrant Test: score each cell for a firm already operating there and for one deciding whether to arrive
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) — when the macro scan is the wrong tool
- [PESTEL analysis of the 2026 World Cup host economy](/examples/world-cup-2026-pestel-analysis) — Canada as a co-host, at the event level

*Cover photo: [Nathan Cima on Unsplash](https://unsplash.com/photos/MHXJ9p64Jw8).*

---

### PESTEL Analysis of China (2026): the two-ledger economy
URL: https://frameworklist.com/examples/china-pestel-analysis-2026
> A PESTEL analysis of China in 2026 — exports up 17.8% while retail grows 0.6%, a 7.5% US overcapacity tariff, 7.92 million births, and the Two-Ledger Test.

![The Lujiazui financial district skyline reflected in the Huangpu River, seen from the Bund in Shanghai](https://images.unsplash.com/photo-1545893835-abaa50cbe628?auto=format&fit=crop&w=1600&q=80)

Every PESTEL of a country makes a second silent assumption, after the one about government: that the economy behind each cell is one economy. If exports are strong, households are usually doing fine. If producer prices are rising, consumer prices are usually rising too. Score the Economic cell once and you have scored it for everyone who trades with the country.

China in September 2026 is where that assumption fails, and it fails inside single statistical releases. In July, exports grew **17.8%** year on year and retail sales grew **0.6%**. In August, the producer price index rose **3.8%** overall — and the part of it that measures consumer goods *fell* **0.5%**. The same month, the same index, opposite signs. Ten days from now Xi Jinping is due at the White House for a summit whose agenda is, on the American side, precisely that gap: a planned **7.5%** tariff on Chinese goods for "excess capacity," which is the production ledger, priced by the country that has been absorbing it.

A [PESTEL analysis](/frameworks/pestel) scans six external macro forces — Political, Economic, Social, Technological, Environmental, Legal — and asks whether each is favourable or adverse. For China the honest answer to every one of the six is *for whom?* This page is the sixth in a country series. The [USA](/examples/usa-pestel-analysis-2026) showed one force holding up the other five; [Canada](/examples/canada-pestel-analysis-2026) one force rewriting them; [France](/examples/france-pestel-analysis-2026) cells splitting by constitutional instrument; [Germany](/examples/germany-pestel-analysis-2026) six cells that were all early; the [European Union](/examples/europe-pestel-analysis-2026) six cells governed by different governments. China shows something none of those can: **six cells that each return two readings, and the two readings carry opposite signs.**

## Position being analyzed

The decision this analysis is built for: **a firm deciding, for 2026-27, whether China is a market to sell into, a supply base to buy from, or a competitor to price against — and why the same scan should give a different answer to each.**

That is the live question because the two halves of the Chinese economy have decoupled from each other, and the policy response on both sides of the Pacific is aimed at the decoupling itself. Beijing's 2026 Government Work Report commits to "thoroughly address rat race competition" — the anti-involution campaign — through "production regulation, standard-based guidance, pricing law enforcement, and quality supervision." Washington's answer is a Section 301 investigation into excess capacity whose findings are due before 24 September. Both are trying to make Chinese producers make less and charge more. Neither has yet moved the household numbers.

| Indicator | Latest reading | As of |
|---|---|---|
| GDP growth, Q1 / Q2 / H1 2026 | **5.0% / 4.3% / 4.7%** — Q2 the slowest since end-2022 | NBS, 15 July 2026 |
| 2026 GDP growth target | **4.5–5%**, down from "around 5%" | Government Work Report, 5 March 2026 |
| Exports, July / Jan–Jul 2026 | **+17.8% / +14.0%** (yuan terms) | NBS, 17 August 2026 |
| Retail sales, July 2026 | **+0.6%** | NBS, 17 August 2026 |
| Fixed-asset investment / real-estate investment, Jan–Jul | **−6.7% / −19.2%** | NBS, 17 August 2026 |
| PPI, August 2026 — means of production / consumer goods | **+5.0% / −0.5%** (headline +3.8%) | NBS, 10 September 2026 |
| CPI, August 2026 (target ~2%) | **+0.8%**, core 1.0% | NBS, 10 September 2026 |
| Urban unemployment / youth (16–24) unemployment, July | **5.2% / 17.9%** | NBS; Caixin, 20 August 2026 |
| Births / deaths, 2025 | **7.92m / 11.31m** — population −3.39m to 1.405bn | NBS, 19 January 2026 |
| Deficit target 2026 | **~4% of GDP, 5.89 trillion yuan** | Government Work Report |
| Defence budget 2026 | **1.9096 trillion yuan, +7%** | Finance Ministry, 5 March 2026 |
| US tariff on Chinese goods, second-term Section 301 | **12.5%** (July), **+7.5%** planned → ~20% | Business Today, 25 August 2026 |

## Political — a plan for production, a summit about it

The domestic political calendar delivered exactly what it was expected to. The **15th Five-Year Plan** for 2026-2030 was approved on **12 March 2026** at the National People's Congress, and the Government Work Report of 5 March set the year's targets: GDP growth of **4.5-5%**, "while striving for better in practice"; a surveyed urban unemployment rate of around 5.5%; over 12 million new urban jobs; CPI of around 2%; a **3.8%** cut in carbon dioxide emissions per unit of GDP. The plan itself is long on direction and short on numbers — the one hard commitment is an average annual increase of **at least 7%** in nationwide R&D spending, unchanged from the 14th plan — and analysts reading the draft targets put the implied 2026-30 growth rate closer to **4% than 5%**. The defence budget rose **7%** to **1.9096 trillion yuan**, slightly below the previous year's increase.

Read those targets against the two ledgers and a pattern appears. R&D, the priority industries — new energy, materials, aerospace, the "low-altitude economy," quantum, biomanufacturing, hydrogen, AI, 6G — and technological self-reliance are all *production* commitments. The household commitments are real but smaller: **250 billion yuan** of ultra-long special treasury bonds earmarked for consumer-goods trade-in programmes, out of 1.3 trillion issued; the childcare subsidy; a free year of preschool. The plan is a plan for the ledger that is already running hot.

The external calendar is the same story from the other side. The **Busan** meeting of 30 October 2025 produced a truce: the US fentanyl tariff cut to **10%** from 10 November, the reciprocal-tariff pause extended to **10 November 2026**, China's new rare-earth export controls paused for a year and its retaliatory measures suspended to **31 December 2026**. The **Beijing** summit of 14-15 May 2026 added a commitment to buy at least **$17 billion** of US agricultural goods a year in 2026, 2027 and 2028, an initial 200 Boeing aircraft, and a Board of Trade — but **no extension of the truce**, with the Treasury Secretary saying the US was "not in a rush." The **Washington** summit on **24 September** will convene with a 7.5% overcapacity tariff either published or pending, and with China having added **10 US entities**, including the rare-earth miners MP Materials and USA Rare Earth, to its own export-control list in June.

**Score: favourable for the production ledger — the plan, the R&D floor and the defence line all serve it; adverse for anyone selling *to* it, because the summit agenda is about making China's producers less competitive, not its households richer.**

## Economic — one release, two economies

The Economic cell is where the split is not a metaphor but a table.

Growth is decelerating within the target band: **5.0%** in the first quarter, **4.3%** in the second — the slowest quarter since the end of 2022 and below the 4.48% consensus — for **4.7%** in the first half. But the first-half composition is the point. Industrial value added rose **5.4%**; exports rose **13.4%** and imports **22.1%**. Retail sales of goods and services rose **2.7%**; fixed-asset investment fell **5.7%**; real-estate development investment fell **18.0%**. By July the divergence had widened rather than closed: exports **+17.8%** in the month, industrial output +4.5% with high-tech manufacturing at **+13.8%** — against retail sales at **+0.6%**, fixed-asset investment **−6.7%** year to date and real estate **−19.2%**. The housing market underneath that investment line is still repricing: **68 of the 70** cities the NBS surveys recorded month-on-month falls in new-home prices in July, and second-hand prices in the four first-tier cities were down between roughly **2% and 4.7%** year on year.

| Reading, July / August 2026 | Production ledger | Household ledger |
|---|---|---|
| Output | Industrial value added **+4.5%**; high-tech manufacturing **+13.8%** | Retail sales **+0.6%** |
| Demand | Exports **+17.8%** (July) | Fixed-asset investment **−6.7%**; real estate **−19.2%** (Jan–Jul) |
| Prices | PPI means of production **+5.0%**; mining **+17.8%** (August) | PPI consumer goods **−0.5%**; food **−2.3%**; CPI **+0.8%** |
| Labour | Urban unemployment 5.2% | Youth (16–24) unemployment **17.9%** |

The price line is the sharpest tell because it comes from a single index. The August PPI was **+3.8%** year on year, its Jan-Aug average +2.0%, which on its face ends the producer deflation that had defined 2023-25. But the means-of-production component was **+5.0%** — mining and quarrying **+17.8%**, raw materials +6.7% — while consumer goods were **−0.5%**, with food −2.3%, clothing −1.2% and daily-use articles −0.8%. The purchasing-price index, what factories pay for inputs, was **+5.8%**, with nonferrous metals +19.8% and fuel and power +9.8%. That is not pricing power returning to Chinese industry. It is an input-cost shock — the [Strait of Hormuz closure](/examples/europe-pestel-analysis-2026) that raised fuel prices worldwide — landing on a production sector that still cannot pass costs through to a consumer sector whose prices are falling. Consumer inflation at **0.8%** against a target of "around 2%" says the same thing from the other end.

Fiscal policy is aimed at the gap: a deficit of **around 4% of GDP, 5.89 trillion yuan**, up 230 billion on 2025; general public expenditure projected to pass **30 trillion yuan** for the first time; **1.3 trillion yuan** of ultra-long special treasury bonds plus 300 billion to recapitalise the large state banks; **4.4 trillion yuan** of local-government special-purpose bonds. Whether it reaches the household ledger is the question the monthly retail print keeps answering.

**Score: favourable, high volatility on the production ledger — output and export growth are strong but the tariff and input-cost exposure is acute; adverse, low volatility on the household ledger — the numbers are weak and have been weak for long enough to be structural.**

## Social — the ledger that only has one side

The Social cell is the exception that proves the test, because it has no production reading at all.

On **19 January 2026** the National Bureau of Statistics reported a population of **1.40489 billion** at end-2025, down **3.39 million** — the fourth consecutive annual decline and the largest yet. Births fell to **7.92 million** from 9.54 million in 2024, a **17%** drop in a single year and the lowest of the modern era, against **11.31 million** deaths. The birth rate was **5.63 per 1,000**; the total fertility rate fell to about **0.96**. People aged 60 and over were **23%** of the population, **323.38 million**; those 65 and over were **15.9%**.

The labour market that this population enters is the household ledger's weakest line. The urban surveyed unemployment rate rose to **5.2%** in July from 5.0% in June. The rate for 16-to-24-year-olds excluding students rose to **17.9%**, up three points in a month as the graduating class entered the market — the highest July reading in three years. Per-capita disposable income grew **5.2%** in nominal terms in the first half, which against 1.0% inflation is a real gain; the retail print says households are saving it.

The policy response is genuine and, by the standards of this cell, fast. The Government Work Report records that **over 30 million** children under three benefited from the nationwide childcare subsidy launched in 2025, that a year of free preschool reached **14 million** children, and that the 15th plan's public-wellbeing indicators lead with "building a childbirth-friendly society." None of it changes the 2026 number. A birth cohort is a sixteen-year lead indicator of a labour force and a twenty-five-year lead indicator of a consumer base, and the 2025 cohort is the smallest one modern China has produced.

**Score: adverse, low volatility — and entirely a household-ledger fact, which is why it is the one cell where a buyer's scan and a seller's scan agree.**

## Technological — where the production ledger wins outright

Technology is the cell where the production reading is strongest and the household reading is nearly irrelevant, and the 2026 record is a sequence of dated events.

On **24 April 2026** DeepSeek released the **V4** series — a Pro model and a lightweight Flash — with support for both Nvidia GPUs and **Huawei Ascend** NPUs, and with V4-Flash adapted for "more than eight AI chip architectures, including those from Huawei, Hygon and Moore Threads." China Daily's own framing was a "symbolic break from Nvidia reliance" and a break "with a long-standing pattern in which Chinese developers have relied almost exclusively on Nvidia's CUDA ecosystem for training and inference." A frontier Chinese lab shipping a frontier model on domestic silicon is what technological self-reliance looks like when it stops being a plan line and becomes a product.

The state's side of the ledger is the **at least 7%** annual R&D floor in the 15th plan, unchanged from the 14th, and a report that R&D spending had reached **2.8% of GDP** in 2025 while technology-contract transactions grew 10.8%. High-tech manufacturing output growing **13.8%** in July, 8.5 points faster than industry overall, is the same commitment measured in factories. New-energy vehicle output exceeded **16 million units** in 2025 and charging facilities passed 20 million.

The household reading of the same cell is the EV price war. BYD's average price reduction across its models rose to **10%** in March 2026, its highest, nearly a year after regulators met the industry's leaders to urge an end to "involutionary" competition. That is what over-capacity in a cell looks like from the consumer side: the best deal in the world on a car, paid for by margins the producers cannot sustain — which is why the state's anti-involution campaign treats a strong production reading as a problem to be regulated rather than a result to be celebrated.

**Score: strongly favourable on the production ledger, with the volatility now sitting in Washington's export-control decisions rather than in China's own capability.**

## Environmental — the ledger where China's exports and its emissions point the same way

Two things share this cell and, unusually for this scan, both are production-ledger facts that favour China.

The first is the emissions trajectory. Carbon Brief's analysis of **2 September 2026** found China's CO2 emissions **fell 1%** in the second quarter of 2026 after rising 2% in the first, leaving them up marginally for the half but **below their 2023-24 peak**. For the first time, the decline was driven by *oil*: oil demand fell **9%** overall and **16%** in transport, as the electric-vehicle fleet grew **33%** year on year, charging volumes rose 60%, and electric trucks took more than **45%** of new truck sales — with the Hormuz fuel-price shock accelerating an electrification that was already under way. Power-sector emissions rose 3.0% in the half because of curtailed wind and solar, a distribution problem rather than a capacity one.

The second is the target set. China's 2035 NDC, submitted **3 November 2025**, commits to cutting economy-wide net greenhouse-gas emissions by **7-10% from peak**, raising non-fossil energy to **over 30%** of consumption, and expanding wind and solar capacity to **3,600 gigawatts** — Climate Action Tracker rates it "highly insufficient." The 15th plan translates the pledge into a **17%** cut in CO2 per unit of GDP over 2026-30 and the 2026 target into **3.8%**. Both are intensity targets, and an economy whose growth is coming from high-tech manufacturing and exports rather than construction hits intensity targets almost by default: a 19.2% fall in real-estate investment is a large cut in cement and steel demand that no climate policy had to order.

That is the connection to the rest of the scan. The same shift that empties the household ledger — households not buying homes — is what lets the Environmental cell turn favourable, and the same products that fill the production ledger — EVs, solar, batteries — are the ones the anti-involution campaign is trying to make scarcer and the overcapacity tariff is trying to keep out.

**Score: favourable, low volatility — and one of the two cells where China's producers, China's climate targets and the household slowdown all point the same way.**

## Legal — the state legislating against its own production ledger

Almost every legal change of the past year is the state trying to move value from the first ledger to the second, by rule.

The **Anti-Unfair Competition Law** revision, adopted **27 June 2025** and in force from **15 October 2025**, expanded the law from 33 to 41 articles and introduced, for the first time, an offence of abusing a "relative dominant position" — large firms that impose unreasonable payment terms on or withhold payment from smaller suppliers can now be penalised without proof of market dominance — alongside a prohibition on platforms forcing merchants to sell below cost. The **Price Law** amendment released for comment in late July 2025, the first in **27 years**, adds "involution-style" competition and algorithmic price discrimination to the definition of unfair pricing, with the food-delivery platforms as the named target. And the Government Work Report's language for 2026 is "pricing law enforcement" as one of four instruments against rat-race competition.

The other axis is data and security. The amended **Cybersecurity Law**, approved **28 October 2025** and effective **1 January 2026**, is the first major revision of the 2017 law: it adds a dedicated AI-governance clause, raises the general fine cap for critical-infrastructure operators from **RMB 1 million to RMB 10 million** and for content-control breaches twentyfold to the same level, and extends its reach to "any activities by overseas parties that harm China's cybersecurity." Export-control enforcement tightened in parallel: controls on dual-use exports involving certain Japanese entities from **January 2026** (scored from Tokyo's side in the [PESTEL analysis of Japan](/examples/japan-pestel-analysis-2026)), the June addition of ten US entities to the control list, and MOFCOM Announcement No. 26 of **24 June 2026** creating a public reporting channel for strategic-mineral export violations from 1 July.

For the two ledgers the direction is unambiguous. The competition-law changes are meant to raise prices, protect suppliers and stop the production ledger from destroying its own margins. The data and export-control changes are meant to make the production ledger a national asset rather than a global one. Nothing in the year's legislation makes it easier to sell to a Chinese household; a great deal of it makes it harder to compete with a Chinese factory on price.

**Score: adverse for foreign sellers and competitors alike, low volatility — the direction of legislation has been consistent for eighteen months.**

## PESTEL scorecard for China, September 2026

| Force | Production ledger | Household ledger | The single fact that sets it |
|---|---|---|---|
| **Political** | Favourable | Adverse | 15th plan's one hard number is a 7% R&D floor; the 24 Sept summit is about overcapacity |
| **Economic** | Favourable, high volatility | Adverse, low volatility | Exports +17.8% vs retail +0.6% (July); PPI +5.0% vs −0.5% (August) |
| **Social** | — | Adverse | 7.92m births vs 11.31m deaths; youth unemployment 17.9% |
| **Technological** | Strongly favourable | Neutral | DeepSeek V4 on Huawei Ascend (24 April); high-tech output +13.8% |
| **Environmental** | Favourable | Favourable | Q2 CO2 −1% on a 9% oil-demand drop; real estate −19.2% |
| **Legal** | Adverse (competition + export rules) | Neutral | AUCL in force 15 Oct 2025; Cybersecurity Law fines ×10 from 1 Jan 2026 |

Read the left column alone and China in 2026 is the most favourable production environment in the world with a tariff problem. Read the right column alone and it is a shrinking, ageing, deflating consumer market. Both are true, both are current, and a single "Economic: neutral" score is the average of two readings that describe no decision anyone is making.

## The Two-Ledger Test

Country scans assume one economy behind six cells. China is the case that breaks the assumption, and it suggests a routing step the standard method skips:

> **The Two-Ledger Test — for each PESTEL cell, write the production reading (what the country makes, exports, invests in and charges at the factory gate) and the household reading (what its people earn, spend, borrow, bear and are born into) side by side, and score them separately. Then route each reading to the decision it governs: the production ledger answers "should I buy from, or compete against, this country?"; the household ledger answers "should I sell into it?" A cell whose two readings carry opposite signs is not neutral. It is two cells.**

The test is countable because the National Bureau of Statistics publishes both ledgers in the same releases:

| Cell | Production reading | Household reading | Spread |
|---|---|---|---|
| Economic — demand | Exports **+17.8%** (July) | Retail sales **+0.6%** (July) | **17.2 pts** |
| Economic — prices | PPI means of production **+5.0%** (Aug) | PPI consumer goods **−0.5%** (Aug) | **5.5 pts** |
| Economic — investment | High-tech manufacturing output **+13.8%** (July) | Real-estate investment **−19.2%** (Jan–Jul) | **33 pts** |
| Prices — inputs vs. shelf | Purchasing prices **+5.8%**; fuel and power +9.8% | CPI **+0.8%**; food −1.4% | **5.0 pts** |
| Technological | Frontier model on domestic chips | BYD discounts at a record **10%** | opposite sign |
| Social | — | Births −17% in one year; fertility ~0.96 | one-sided |

Four of the six cells carry a measurable spread and in every one the production reading is the higher. Only the Social cell is one-sided, and only the Environmental cell has both readings pointing the same way — because a household ledger that stops buying apartments is what makes a production ledger's intensity targets easy.

### What the two governments are doing about it

The sharpest illustration of the test is that the two largest economies in the world are running policy against the *same* ledger from opposite sides. Beijing's anti-involution campaign — the Government Work Report's pledge to "thoroughly address rat race competition," the competition-law and Price Law changes, the capacity regulation "in key industries" — is an attempt to shrink the production ledger's volume and raise its prices, so that margins and wages can flow to the household ledger. Washington's Section 301 overcapacity investigation, due to report before 24 September, is an attempt to stop the United States absorbing the production ledger's surplus at the prices it currently charges: a **12.5%** Section 301 tariff already in place from July, **7.5%** more planned, a **20%** ceiling that Beijing has said is consistent with the truce.

Both would, if they worked, close the spread in the table above. Neither has yet. Exports accelerated from 13.4% in the first half to 17.8% in July; retail decelerated from 2.7% to 0.6%. A firm reading the scan in September 2026 should treat the spread as the environment and the two campaigns as the volatility around it.

## Counter-argument: isn't this just the old "exports versus domestic demand" story?

The strongest objection is that China has always been an export-led economy with under-consuming households, and that economists have been writing about "rebalancing" since at least 2007. If the imbalance is twenty years old, why does the scan need a new step for it?

Because the standard story is about *levels* and the test is about *signs*. Rebalancing was a claim that consumption was too small a share of GDP — a share that could be 38% or 40% while both halves still grew together and both halves still saw rising prices. What the 2026 releases show is the two halves moving in **opposite directions** inside the same month and the same index: the production side accelerating and reflating, the household side decelerating and deflating. A level imbalance lets you score the Economic cell once and add a caveat. A sign divergence does not, because the caveat is now the score.

The honest bound on the Two-Ledger Test is that it is a *routing* instrument, not a forecasting one. It does not tell you whether the spread will close, or which government's campaign will close it. It tells you which reading your decision depends on — and that if you are selling into China you have been reading the wrong column of every headline about Chinese growth for a year.

## Key takeaway

China in September 2026 scores as the strongest production environment in the world — exports up 17.8%, high-tech output up 13.8%, a frontier model on domestic chips, emissions below peak — attached to a consumer market growing at 0.6%, deflating at the shelf, ageing at 23% over sixty and producing its smallest birth cohort on record. Every one of those is current, every one is from the same statistical agency, and no single score describes both.

**Decisions that depend on China as a supplier or a competitor should be made on the production ledger, and the risk to price is the 24 September summit and the 10 November and 31 December truce deadlines.** Decisions that depend on China as a market should be made on the household ledger, and the risk is that the anti-involution campaign lifts factory prices before it lifts wages — which is exactly the sequence the August PPI already shows.

The two readings that will most cheaply update this analysis are the outcome of the Washington summit on 24 September, which will set whether the overcapacity tariff is 7.5% or something else, and the August activity data due in mid-September, which will show whether July's 0.6% retail print was a floor or a step.

> Want to run a PESTEL on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a PESTEL worksheet with all six forces and AI assistance for the scan.

## Want to go deeper

- [PESTEL framework](/frameworks/pestel) — the six forces, and how to score them
- [How to do a PESTEL analysis](/academy/how-to-do-a-pestel-analysis) — the step-by-step method
- [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) — one force holding up the other five, and the Load-Bearing Force Test
- [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) — one force rewriting the other five, and the Reversal Test
- [PESTEL analysis of France (2026)](/examples/france-pestel-analysis-2026) — cells splitting by constitutional instrument, and the Ballast Test
- [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026) — six cells that are all early, and the Disbursement Gap
- [PESTEL analysis of the European Union (2026)](/examples/europe-pestel-analysis-2026) — six cells governed by different governments, and the Competence Test
- [Apple PESTEL analysis (2026)](/examples/apple-pestel-analysis-2026) — the China exposure scanned from the other side, one company at a time
- [PESTEL analysis of India (2026)](/examples/india-pestel-analysis-2026) — six cells of which three are set abroad, and the Imported-Cell Test: tag each cell by who can move it, and never average a domestic reading with an imported one
- [PESTEL analysis of Japan (2026)](/examples/japan-pestel-analysis-2026) — the neighbour on the receiving end of China's 2026 rare-earth and dual-use controls, and the Repricing Test
- [PESTEL analysis of Mexico (2026)](/examples/mexico-pestel-analysis-2026) — the market whose up-to-50% tariffs on non-FTA imports from 1 January 2026 are aimed at Chinese inputs, and the Entrant Test
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) — when the macro scan is the wrong tool

*Cover photo: [Freeman Zhou on Unsplash](https://unsplash.com/photos/oV9hp8wXkPE).*

---

### Eisenhower Matrix applied to an engineering manager's week
URL: https://frameworklist.com/examples/eisenhower-engineering-manager-week
> A worked example: 18 things on an EM's plate, sorted by urgency × importance, with the actions that follow each quadrant.

The Eisenhower Matrix is simple in theory and routinely abused in practice. Most managers I've watched run it produce a list where 90% of items end up in "Important + Urgent". This worked example shows what an honest run looks like.

> **Run the Eisenhower Matrix on your phone** — [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=eisenhower-em-example-hero) sorts your week into the four quadrants with AI assistance. Free to start.

## The setup

A real engineering manager (anonymized) at a mid-size SaaS company, working through Monday morning planning. Carrying 18 items across her desk:

1. Q3 OKR review with VP today at 4pm
2. PR review for a senior eng's refactor PR (sitting 3 days)
3. 1:1 with struggling junior eng tomorrow morning
4. CTO Slack: "got a sec to discuss the platform migration"
5. Compliance training overdue (auto-reminder #3)
6. Hiring panel debrief for two candidates
7. Incident retro from last Thursday's outage
8. Team's planning poker session Wednesday
9. New laptop request for new hire arriving Monday
10. Vendor invoice approval ($2k, due Friday)
11. Spec review for upcoming feature (eng wants feedback today)
12. Recurring "all-hands" presentation prep for next week
13. Team budget reforecast (quarterly)
14. Direct report's promotion case write-up (target: end of quarter)
15. Slack channel cleanup (15 stale channels)
16. Conference invite to evaluate (talk slot offered)
17. Coffee with peer EM in another org (postponed twice already)
18. Self-development reading: just-published book on platform engineering

## The sort

The manager scored each item on (a) urgency = real consequence in 48 hours? and (b) importance = ladders to her quarterly goals? Goals were: ship platform migration milestone 1, retain the struggling junior, hire 2 senior engineers.

### Important + Urgent — Do now

- Item 1 (OKR review at 4pm) — non-negotiable
- Item 7 (incident retro) — engineering culture depends on doing these promptly
- Item 11 (spec review blocking eng today) — unblocks team

### Important + Not Urgent — Schedule

- Item 3 (1:1 with struggling junior) — central to "retain junior" goal
- Item 6 (hiring debrief) — central to "hire 2 senior" goal
- Item 14 (promotion write-up) — important to direct report's career
- Item 4 (CTO Slack about platform migration) — looks reactive, actually important; book proper time
- Item 8 (planning poker Wednesday) — team velocity, not urgent until Wednesday

### Not Important + Urgent — Delegate

- Item 2 (PR review) — sr eng can pair with another sr; not the manager's bottleneck
- Item 9 (laptop request) — delegate to IT directly
- Item 10 (invoice) — finance team has the workflow
- Item 5 (compliance training) — 15 min, do it during a low-energy slot but don't elevate

### Not Important + Not Urgent — Drop

- Item 15 (Slack channel cleanup) — no one cares; archive in batch later if free
- Item 12 (all-hands prep) — wait until Friday; over-prepping a 10-min talk is waste
- Item 16 (conference invite) — pass this round
- Item 17 (peer coffee) — keep on the calendar at low cadence, don't agonize
- Item 18 (reading the book) — important for *career*, not this *week*; schedule in personal time
- Item 13 (budget reforecast) — has 2 weeks; not this week

## What this run revealed

Two things the manager learned:

**Items 4 and 6 had been re-categorized for weeks.** Item 4 (CTO platform conversation) had been pushed off because it didn't feel "urgent". Item 6 (hiring debrief) had been postponed twice. Both were Important + Not Urgent items — exactly the ones the matrix predicts get ignored without explicit scheduling.

**The Drop quadrant was bigger than expected.** The manager had been treating items 12, 15, 16, 17, 18 as low-priority *but still on the list*. The matrix forced an explicit "drop" decision, which felt uncomfortable until she said it out loud: *"these are things I would do if I had infinite time. I don't."*

## Decisions made in 30 minutes

- 4pm OKR review: prepared in 15 min between meetings.
- Tuesday 9am: 1:1 with junior, focus on whether scoping was the issue (not skill).
- Wednesday: 90 min blocked specifically for the CTO platform conversation prep. Marked unmovable.
- PR review delegated to sr eng pairing partner.
- Compliance training: 15 min at 4:45pm after OKR review.
- Items 15, 16, 18 explicitly cancelled. The list ended at 14 items, not 18.

## Lessons that generalize

- **The discomfort of "drop" is the matrix doing its job.** A 4-quadrant matrix where the bottom-right is empty hasn't been used honestly.
- **Important + Not Urgent is the quadrant most managers under-invest in.** This run identified two such items that would have continued to slip without explicit scheduling.
- **30 minutes is the right time budget.** Going longer doesn't sharpen the analysis; it usually produces more reasons to keep items rather than drop them.

## Run your own

[Open the Eisenhower Matrix worksheet →](/tools/eisenhower-matrix), or read the [full Academy guide](/academy/eisenhower-matrix-urgent-vs-important) for the methodology.

> **Want to run this week's triage on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=eisenhower-em-example) sorts your tasks into the four quadrants with AI assistance — including the drop quadrant most people skip. Free to start.

## Related

- [Eisenhower Matrix vs Impact/Effort Matrix](/compare/eisenhower-matrix-vs-impact-effort-matrix) — when the second axis should be effort instead of urgency
- [Eisenhower Matrix vs GTD](/compare/eisenhower-matrix-vs-gtd) — a triage grid vs a full workflow system for the same week
- [Eisenhower Matrix vs the Covey Matrix](/compare/eisenhower-matrix-vs-covey-matrix) — the Quadrant II framing this run's under-investment finding comes from
- [The Eisenhower framework page](/frameworks/eisenhower) — catalog entry and worksheet
- [RICE on a real SaaS backlog](/examples/rice-saas-q3-backlog) — what triage looks like once the items are features rather than a week's tasks

---

### PESTEL Analysis of the European Union (2026): who holds the lever
URL: https://frameworklist.com/examples/europe-pestel-analysis-2026
> A PESTEL analysis of Europe in 2026 — a Hormuz energy shock, two ECB rate hikes, a 15% US tariff ceiling, and the cells where Brussels holds the lever versus the 27 capitals.

![Row of European Union flags in front of the Berlaymont building in Brussels](https://images.unsplash.com/photo-1594810205183-18a8b0ce6c13?auto=format&fit=crop&w=1600&q=80)

Every PESTEL of a country makes one silent assumption: that there is a government at the other end of each cell. Score the Political force and you are scoring a cabinet. Score the Economic force and there is a finance ministry and a central bank that answer to the same electorate. The six cells may disagree with each other, but they are all *about the same state*.

The European Union is the one subject for which that assumption is false, and September 2026 is the month that makes the failure visible. The forces that moved most this year — a Strait of Hormuz closure that reset the inflation outlook, two ECB rate rises, a tariff deal with Washington, a sixteen-month deferral of the AI Act, a carbon border tax going live, a migration regime switching on — were all pulled from Brussels or Frankfurt. The forces where the money actually sits — fiscal stimulus, defence procurement, wages, energy mix — were pulled, or not pulled, in twenty-seven capitals.

[PESTEL](/frameworks/pestel) scans six external macro forces — Political, Economic, Social, Technological, Environmental, Legal — around an entity and asks whether each is favourable or adverse. For the EU that question has a prior one: *favourable according to whom, and adverse at which level?* This page is the fifth in a country series, and it is the first where the subject is not a country. The [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) found one force holding up the other five. [Canada](/examples/canada-pestel-analysis-2026) found one force rewriting the other five. [France](/examples/france-pestel-analysis-2026) found the cells splitting by constitutional instrument, and [Germany](/examples/germany-pestel-analysis-2026) found six cells that were all early. The EU shows something none of those can: **six cells governed by different governments.**

## Position being analyzed

The decision this analysis is built for: **a firm deciding whether to treat "Europe" as one market for a 2026-27 capital, hiring or pricing decision — and, if not, which parts of the scan it can settle once and which it has to settle twenty-seven times.**

That is the live question because the 2026 shocks arrived at Union level and the 2026 responses are split. A scan that treats the EU as a state overstates what Brussels can do about the two cells it does not control, and understates how fast it can move on the four it does.

| Indicator | Latest reading | As of |
|---|---|---|
| EU real GDP growth, 2026 / 2027 forecast | **1.1% / 1.4%** (euro area 0.9% / 1.2%) | Commission, 21 May 2026 |
| Euro-area HICP inflation, 2026 / 2027 / 2028 | **3.0% / 2.5% / 2.1%** | ECB staff, September 2026 |
| ECB deposit facility rate | **2.50%**, after +25bp on 11 June and +25bp on 10 September | 10 September 2026 |
| Strait of Hormuz seaborne oil / LNG flows | **−15% / −20%** | Commission, spring 2026 |
| EU gas storage fill | **57.1%** — lowest on record for the date | 1 August 2026 |
| US tariff ceiling on most EU goods | **15%** all-inclusive; steel and aluminium still 50% | applied from 1 July 2026 |
| EU general government deficit / gross debt | −3.5% of GDP (2026) / **85.3%** (2027) | Commission, spring 2026 |
| SAFE defence loans disbursed | **~€8.4bn of a €150bn cap (~5.6%)** | 12 August 2026 |
| CBAM certificate price, Q2 2026 | **€75.28 / tCO₂e** | published 6 July 2026 |
| EU population, 1 January 2026 | **452.0 million**, +705,756 on the year | Eurostat |

## Political — a Council that got its unanimity back

The single largest political fact in the EU's 2026 is a national election, which is the first hint that the Political cell does not belong wholly to Brussels.

On **12 April 2026** Hungary's Tisza party under Péter Magyar defeated Viktor Orbán's Fidesz, taking **141 of 199 seats on 53.2% of the list vote** against Fidesz's 52 seats on 38.61% — a two-thirds majority and the end of a sixteen-year government. The Magyar government took office on **13 May 2026**. For the Union the significance is arithmetical rather than ideological: the European Council decides sanctions, enlargement, foreign policy and the next long-term budget by unanimity, and for most of the previous decade one member state's veto was the binding constraint on all four. That constraint was removed by 3.3 million Hungarian voters, not by any EU institution.

The institutional layer is running on a slower clock. The Commission's proposal for the **2028–2034 budget** — almost **€2 trillion, or 1.26% of gross national income** — was tabled on 16 July 2025; on **16 June 2026** the Council adopted partial negotiating positions on its two biggest new instruments, the national and regional partnership plans and the **European Competitiveness Fund**, while Parliament is pushing for roughly **€200 billion more**. The regulation must be adopted unanimously by all 27 and consented to by Parliament, on a timetable that runs to 2028.

And the member-state layer is where the volatility lives. France's fiscal position and Germany's three September state elections are the Political cells of the [France](/examples/france-pestel-analysis-2026) and [Germany](/examples/germany-pestel-analysis-2026) pages, and they are not repeated here, because that is the point: they are not the Union's Political cell. They are inputs to it.

**Score: favourable at Union level, high volatility at member-state level — and the two do not net.**

## Economic — one central bank, twenty-seven treasuries, one war

The Economic cell is the one where the split is clearest, because the euro area has exactly one monetary policy and no fiscal policy.

The monetary half moved decisively. The ECB **raised all three key rates by 25 basis points on 11 June 2026** — its first increase in three years — taking the deposit facility rate to **2.25%** from 17 June, and stated plainly that "the war in the Middle East is generating inflation pressures." It held on 23 July and **raised again on 10 September**, to a deposit rate of **2.50%** and a main refinancing rate of 2.65%. The September staff projections that accompanied the second hike put headline inflation at **3.0% in 2026, 2.5% in 2027 and 2.1% in 2028**, with 2027 and 2028 both revised up from June, and core inflation at 2.5%, 2.6% and 2.3%.

Growth is not the problem. The Commission's **21 May 2026 Spring forecast** cut EU growth to **1.1% for 2026 and 1.4% for 2027** (euro area 0.9% and 1.2%) from the autumn's 1.2% and 1.4%, and lifted inflation by a full point to 3.1% and 2.4% (euro area 3.0% and 2.3%). By September the ECB kept 2026 at 0.9% but revised 2027 up to **1.4%**, noting the euro area had proven "more resilient to the effects of the conflict in the Middle East than previously expected." Unemployment sits near **6.0%** for the EU and is projected to drift down to 5.9% by 2028.

| Forecaster | Euro-area GDP 2026 | Euro-area GDP 2027 | Euro-area inflation 2026 | 2027 |
|---|---|---|---|---|
| European Commission, spring (21 May 2026) | 0.9% | 1.2% | 3.0% | 2.3% |
| ECB staff, September 2026 | 0.9% | **1.4%** | 3.0% | **2.5%** |

The fiscal half is not a Union number at all. The Commission's aggregate — a deficit of **3.5% of GDP in 2026 and 3.6% in 2027**, gross debt rising from 82.8% in 2025 to **85.3% in 2027** — is the sum of twenty-seven budgets that Brussels can surveil but not write. The ECB is explicit about where the impulse comes from: defence and infrastructure spending, "primarily from Germany," adds about **0.5 percentage points cumulatively to growth over 2025–28**, and the fiscal stance loosens by about 0.5 points of GDP in 2026 before tightening in 2027–28. Whether that German money arrives on schedule is the subject of the [Disbursement Gap](/examples/germany-pestel-analysis-2026) on the Germany page — it was running at 28% of its 2026 budget by April — and nothing at Union level can accelerate it.

**Score: adverse on inflation, neutral on growth, and the lever is split — monetary policy is exclusive to the ECB, fiscal policy is not the Union's to score.**

## Social — the cell the Union barely governs

The EU's population reached **452.0 million on 1 January 2026**, up 705,756 on the year, and every unit of that growth was migration: natural change is negative and has been for years. The median age was **44.9 years** on 1 January 2025; the old-age dependency ratio was **33.4%** at the last full reading. In 2024 almost six million people immigrated to EU countries, 4.2 million of them from outside the Union.

Those are Union-wide numbers, and they describe a Union-wide problem. The instruments that act on it are almost entirely national. Employment, social policy, pensions, minimum wages and labour law are areas where the treaties give the EU a coordinating or supporting role and the member states the decisive one — which is why the [Germany page](/examples/germany-pestel-analysis-2026) can cite a **€13.90** statutory minimum wage and a 22.7% skilled-labour shortage as live costs, and this page cannot cite a European equivalent, because there is none.

The one Social instrument the Union does hold switched on this year. The **Pact on Migration and Asylum**, ten binding legislative acts adopted in 2024, started applying in all member states on **12 June 2026** after a two-year transition, with common screening at the border, faster asylum and return procedures, and a solidarity mechanism between states under pressure. It is a genuine Union competence and a genuine change — and it governs the *procedure* for the arrivals, not the labour market they arrive into.

**Score: adverse, low volatility — and almost entirely outside the Union's reach.**

## Technological — a regulation the Union moved, and a fund it has not yet built

Technology is the cell where the EU's reputation and its 2026 record diverge most.

The reputation is for regulating. The record this year is for *deferring*. The **AI Act**'s high-risk obligations were due on 2 August 2026. On **16 June 2026** the European Parliament endorsed the Digital Omnibus on AI by **423 votes to 57 with 174 abstentions**, and the Council gave final approval on **29 June**: stand-alone high-risk systems under Annex III — hiring tools, credit scoring, biometric identification — now have until **2 December 2027**, and AI embedded in regulated products under Annex I until **2 August 2028**. The Article 50 transparency duties still applied from 2 August 2026; the watermarking obligation on providers moved to 2 December 2026. A sixteen-month change to the continent's flagship technology law, made in one legislative cycle, with no national parliament involved.

The investment side is the opposite story. The proposed **European Competitiveness Fund** exists as a Council negotiating position of 16 June 2026 inside a budget that does not start until 2028. Until then, technology investment in Europe is national money — Germany's €500 billion fund lists research and development among its *weakest* areas of progress — and private money that the ECB describes as constrained by "the past appreciation of the euro and higher US tariffs."

**Score: neutral — favourable on regulatory clarity, which the Union controls; unrealised on capital, which it does not.**

## Environmental — the shock nobody chose, and the price only Brussels sets

Two things share this cell in 2026 and they are governed at opposite levels.

The shock is the **Strait of Hormuz**. The war that began on **28 February 2026** with US and Israeli strikes on Iran led to the strait being declared closed on **4 March**; a US naval blockade of Iranian ports ran from **13 April to 29 May**; a memorandum to end the war was signed on **17 June**, Iran re-closed the strait on 20 June, and the ceasefire collapsed on **8 July** after attacks on commercial vessels. As of September shipping remains severely disrupted. Before the crisis roughly **25% of the world's seaborne oil and 20% of its LNG** transited the strait; the Commission's spring forecast put the cut to flows at about **15% and 20%**, with gas prices up **50%** and crude up **65%** between 27 February and 29 April. Brent peaked at $126. By **20 August** Dutch TTF gas was back above **€65/MWh**, its highest since March, up about 130% on the year, and EU storage had reached only **57.1% on 1 August** — the lowest reading for that date on record — against a 90% target that the Union has already allowed to be met anywhere between 1 October and 1 December.

Where the lever sits is the instructive part. The storage target is a Union regulation. The joint purchasing platform is a Union instrument. But **Article 194 of the treaty reserves each member state's choice of energy mix to that member state** — so the exposure to Hormuz LNG is a national fact that varies from a coal-and-nuclear Poland to a gas-dependent Italy, and the Union can set a fill level without being able to change what is being filled.

The price the Union *does* set is carbon. The **Carbon Border Adjustment Mechanism** entered its definitive phase on **1 January 2026**. The Commission published the first official certificate price on 7 April — **€75.36 per tonne** for Q1 — and **€75.28 for Q2** on 6 July, tracking the EU ETS, where allowances traded around €82 at the end of August. Certificate sales open on **1 February 2027** and the first surrender, covering 2026 imports, is due by 30 September 2027. Every importer of steel, cement, aluminium, fertiliser, hydrogen or electricity into the Union is now accruing a 2026 liability at a price no national government can alter.

**Score: adverse, high volatility on energy — with the exposure national and the carbon price exclusively Union.**

## Legal — the cell where 2026 moved fastest

Almost everything that changed in the EU's legal environment this year changed at Union level, on Union timetables.

The largest is trade. The Turnberry political agreement of July 2025 capped most US tariffs on EU goods at an all-inclusive **15%** in exchange for EU tariff elimination on most US industrial goods and twenty agricultural quotas. Then on **20 February 2026** the US Supreme Court held **6-3** that the IEEPA tariffs were unlawful. The US replaced them with a 15% Section 122 tariff on 24 February, which expired by statute on **24 July** and was replaced by Section 301 duties of 10 to 12.5% for most economies — and through all of that, EU goods stayed where the deal put them. Council and Parliament struck the implementing agreement on **20 May 2026**; the regime applied from **1 July 2026** and runs to the end of 2029, with autos at 15% instead of the 25% Section 232 rate other exporters pay, steel and aluminium still at **50%**, and a clause allowing the Commission to suspend the EU's concessions if the US is still charging above 15% on EU steel and aluminium derivatives on **31 December 2026**.

Add the AI Act deferral, CBAM's definitive phase, the Migration Pact's entry into application, and the ECB's two decisions, and the pattern is unmistakable: the Union's legal cell in 2026 is a list of dated, enacted, continent-wide changes, each made by an institution that did not need to ask a national parliament. That is what an exclusive or Union-level competence *looks like* in a scan — fast, uniform, and binding on 452 million people at once.

**Score: favourable on predictability, low volatility — the cell where the Union is most like a state.**

## PESTEL scorecard for the European Union, September 2026

| Force | Direction | Volatility | The single fact that sets it | Who holds the lever |
|---|---|---|---|---|
| **Political** | Favourable (Union) / volatile (states) | High | Hungary's 12 April election restored Council unanimity; MFF talks run to 2028 | Both — and they do not net |
| **Economic** | Adverse on inflation | High | Two ECB hikes to 2.50%; 3.0% inflation; deficit 3.5% of GDP | **Monetary: Union. Fiscal: 27 states** |
| **Social** | Adverse | Low | 452.0m people, median age 44.9, growth only by migration; Pact live 12 June | **States**, except the Pact |
| **Technological** | Neutral (unrealised) | Low | AI Act high-risk deadlines moved to Dec 2027 / Aug 2028 by a 423-57 vote | Regulation: Union. Capital: states |
| **Environmental** | Adverse | **High** | Hormuz −15% oil / −20% LNG; storage 57.1% on 1 Aug; CBAM at €75.28/t | **Exposure: states (Art. 194). Carbon price: Union** |
| **Legal** | Favourable | Low | 15% US tariff ceiling from 1 July; steel/aluminium clause due 31 Dec 2026 | **Union** |

Read the direction column alone and the EU looks like a normal, mildly adverse macro environment with an inflation problem. Read the last column and a different structure appears: **the favourable cells are the ones Brussels controls, and the adverse cells are the ones it does not.**

## The Competence Test

Country scans assume one government behind six cells. The EU is the case that breaks the assumption, and it suggests a prior question the standard method skips:

> **The Competence Test — for each PESTEL cell, write down whether the lever is an exclusive Union competence, a shared one, or a national one, before scoring the cell. Score it only at the level that can actually pull it. Then count: the cells the Union holds are the ones a "Europe" scan can settle once; the rest must be settled per country, and a Europe-level score for them is an average that describes no market you can enter.**

The treaties make this countable. Article 3 TFEU gives the Union *exclusive* competence over the customs union, competition rules, monetary policy for the euro area and the common commercial policy. Article 4 makes the internal market, environment, energy and transport *shared*. Article 6 leaves industry, education and health as areas where the Union may only *support*, and employment and social policy sit with the member states under Union coordination. Article 194(2) reserves the energy mix to each state by name.

| Cell | The 2026 fact | Instrument | Level |
|---|---|---|---|
| Legal — trade | 15% US ceiling from 1 July 2026 | Common commercial policy | **Exclusive** |
| Economic — monetary | +25bp on 11 June, +25bp on 10 September | ECB | **Exclusive (euro area)** |
| Environmental — carbon | CBAM definitive phase, €75.28/t | ETS / CBAM regulations | **Union** |
| Technological — regulation | AI Act deadlines deferred by one vote | Regulation | **Union** |
| Social — asylum procedure | Migration Pact applies from 12 June 2026 | Ten Union acts | **Union** |
| Political — unanimity | Hungary's election on 12 April 2026 | A national ballot | **National** |
| Economic — fiscal | Germany's €500bn fund, 28% deployed by April | 27 budgets | **National** |
| Technological — capital | Competitiveness Fund starts 2028 at the earliest | Next MFF, unanimity | **National until agreed** |
| Environmental — exposure | Who burns Hormuz LNG | Article 194(2) energy mix | **National** |
| Social — labour market | Wages, pensions, labour law | Coordination only | **National** |

Six of the ten load-bearing facts are Union-level. Four are national. The split does not run along the six letters — it runs *through* three of them, which is why the scorecard above has to score Economic, Technological and Environmental twice.

### What the Union's own money says

The sharpest illustration of the test is the instrument built specifically to move a national competence with Union money. The **SAFE** regulation, adopted **27 May 2025**, offers up to **€150 billion** in long-maturity loans for joint defence procurement, on the basis of national plans. Nineteen states are in; Germany opted out. Ministers approved the first plans on 11 February 2026. As of **12 August 2026** approximately **€8.4 billion had actually been disbursed, across six countries — about 5.6% of the cap**, with Poland alone allocated €43.7 billion.

That is the Germany page's Disbursement Gap operating at Union scale, and it is not a coincidence. Defence procurement is national. The Union can lend the money; it cannot buy the equipment, and the lending is only as fast as twenty-seven procurement systems. Wherever Brussels tries to act inside a national competence, expect the Union-level number to be an appropriation and the national-level number to be the disbursement — and expect them to differ by an order of magnitude in year one.

## Counter-argument: doesn't the Hormuz shock prove the levels don't matter?

The strongest objection is that the biggest force in this scan — an energy shock that reset inflation, rates, storage and growth in a single quarter — hit every member state simultaneously and was chosen by none of them. If the most important thing in the environment ignores the competence split, why organise the scan around it?

Because the *response* did not ignore it. The shock arrived once; the levers that answered it were pulled at different levels and at different speeds. The ECB moved within fifteen weeks and twice. The storage regulation flexed its deadline. The carbon price did nothing, because it is not designed to. And the national energy mixes — the variable that determines whether a 20% LNG cut is a crisis or an inconvenience for a given country — did not move at all, because they cannot inside one quarter. A firm pricing 2027 energy costs for a plant in Italy and one in Poland is not pricing "Europe's" Hormuz exposure; it is pricing two national exposures under one Union storage rule and one Union carbon price. The shock was common. The scan still is not.

The honest bound on the Competence Test is that it is a *routing* instrument, not a scoring one. It does not tell you whether a cell is favourable. It tells you which government's next decision will change the score — and, for the cells that route to twenty-seven capitals, which of the [country pages](/examples/france-pestel-analysis-2026) to open next.

## Key takeaway

The European Union in September 2026 scores as a mildly adverse macro environment with a 3.0% inflation problem, a 2.50% deposit rate rising, a 15% tariff ceiling that survived a Supreme Court ruling, and a technology law whose deadlines just moved by sixteen months. Every one of those is a Union-level fact, uniform across 452 million people, and fast — which is why the four cells Brussels controls all moved in 2026.

The two forces where the money and the exposure sit did not move at Union level, because they cannot. **Decisions that depend on trade terms, the cost of capital, carbon pricing or regulatory timetables can be made once, for the whole Union, on the numbers above.** Decisions that depend on fiscal stimulus, labour cost, energy mix or defence demand cannot — they need the [France](/examples/france-pestel-analysis-2026) and [Germany](/examples/germany-pestel-analysis-2026) scans, and the twenty-five that this site has not written yet, because a Europe-level score for those cells is an average of markets that do not share a government.

The two readings that will most cheaply update this analysis are the ECB's 29 October decision, which will show whether September's hike was the second of two or the second of several, and 31 December 2026, when the steel-and-aluminium clause in the US deal either fires or lapses.

> Want to run a PESTEL on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a PESTEL worksheet with all six forces and AI assistance for the scan.

## Want to go deeper

- [PESTEL framework](/frameworks/pestel) — the six forces, and how to score them
- [How to do a PESTEL analysis](/academy/how-to-do-a-pestel-analysis) — the step-by-step method
- [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) — one force holding up the other five, and the Load-Bearing Force Test
- [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) — one force rewriting the other five, and the Reversal Test
- [PESTEL analysis of France (2026)](/examples/france-pestel-analysis-2026) — cells splitting by constitutional instrument, and the Ballast Test
- [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026) — six cells that are all early, and the Disbursement Gap
- [PESTEL analysis of China (2026)](/examples/china-pestel-analysis-2026) — six cells that each return two readings with opposite signs, and the Two-Ledger Test: score the production reading and the household reading separately and route each to the decision it governs
- [PESTEL analysis of India (2026)](/examples/india-pestel-analysis-2026) — the Competence Test's question asked across a border: three of India's six cells are set in Washington, the Strait of Hormuz and the Pacific, and the Imported-Cell Test scores them on those actors' calendars
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) — when the macro scan is the wrong tool

*Cover photo: [Guillaume Périgois on Unsplash](https://unsplash.com/photos/0NRkVddA2fw).*

---

### FIFA Ansoff Matrix 2026: the World Cup growth bet
URL: https://frameworklist.com/examples/fifa-ansoff-matrix-2026
> A worked Ansoff Matrix of FIFA's growth strategy, pegged to the first 48-team World Cup kickoff (June 11, 2026) and its four-quadrant portfolio of bets.

The Ansoff Matrix is a deliberately simple framework — two axes, four quadrants, risk rising as you move from selling what you already have to who you already have (upper-left) toward new products for new markets (lower-right). That simplicity makes it the right lens for FIFA in June 2026. The [2026 World Cup kicks off on June 11](https://en.wikipedia.org/wiki/2026_FIFA_World_Cup) across the United States, Canada, and Mexico — the first 48-team, 104-match tournament — and the coverage treats it as one giant event. Ansoff treats it as one move out of four, and immediately surfaces what the match-schedule headlines miss: FIFA is running all four growth strategies at the same time.

## Position being analyzed

FIFA enters the 2026 World Cup on the most lucrative commercial cycle in its history. Its [revised 2023–2026 budget targets roughly $13B in revenue](https://www.sportsvalue.com.br/en/the-2026-fifa-world-cup-will-be-the-most-lucrative-in-history-with-revenues-expected-to-exceed-us-10-9-billion/) — a ~72% jump on the Qatar-2022 cycle — with the 2026 tournament alone accounting for around $8.9B. But the more interesting story for a strategist is that the World Cup is no longer FIFA's only product. In the same 12-month window it ran a brand-new 32-team Club World Cup, split from its decades-long video-game partner to build its own gaming ecosystem, and is pushing its flagship into football's biggest under-converted market. The strategic question Ansoff helps with: is this a balanced growth portfolio, or is FIFA spreading risk across four quadrants faster than it can manage?

## The four quadrants

| Quadrant | Definition | Risk | FIFA 2025–2026 entries |
|---|---|---|---|
| **Market Penetration** | Existing product, existing market | Low | A bigger World Cup — 104 matches (up from 64), 48 teams, premium US ticketing/hospitality, sold-out sponsorship |
| **Market Development** | Existing product, new market | Medium | Hosting in the USA (11 host cities) — football's largest under-converted market; 48 teams activating new national fanbases |
| **Product Development** | New product, existing market | Medium-High | The expanded 32-team **Club World Cup** (US, 2025); FIFA+ free streaming for existing fans |
| **Diversification** | New product, new market | High | **FIFA Rivals** (web3 mobile game) and a **Netflix-exclusive FIFA simulation** — FIFA's own games for 1.8B gamers |

## Market Penetration: a bigger World Cup

The unglamorous quadrant that funds everything else. The 2026 World Cup is FIFA's existing flagship sold to its existing audience — the difference is quantity. The field grows from 32 teams to 48, the match count from 64 to [104 matches over 39 days](https://www.aljazeera.com/sports/2026/5/7/whats-the-full-match-schedule-groups-and-format-for-world-cup-2026), and the US venues unlock premium ticketing and hospitality at a scale Qatar's smaller stadiums could not. Broadcast and marketing inventory rise with the match count. None of this requires a new customer or a new product — it is selling more of the known thing to the known audience. Ansoff scores it low-risk, and at ~$8.9B it is the cash engine underwriting the other three quadrants.

## Market Development: cracking North America

The same product, aimed at new buyers. Men's football is under-monetised in the United States relative to the NFL, NBA, and MLB — and the US is the largest, most commercially sophisticated sports market on earth. Staging the World Cup across [11 US host cities, plus Mexico and Canada](https://en.wikipedia.org/wiki/2026_FIFA_World_Cup), is FIFA taking its existing product into that market to convert casual attention into durable demand ahead of a US-centric commercial decade. The 48-team format compounds it: more nations qualify, so more national fanbases — many of them first-timers — are activated as new audiences. Same product, new markets: textbook medium-risk Market Development.

## Product Development: the Club World Cup

This is the quadrant that grew the most quietly. The expanded **32-team Club World Cup** — up from a seven-team afterthought — [debuted in the United States in 2025](https://footballbenchmark.com/w/fifa-club-world-cup-2025-breaking-down-the-billion-dollar-prize-money-and-its-impact-on-clubs), with Chelsea beating Paris Saint-Germain 3–0 in the final. It is a brand-new flagship product (a club mega-event FIFA owns directly) sold to FIFA's *existing* market of football fans, and it pulled in roughly $2.1B in income against a $1B prize pool. New product, known audience, known channel — the medium-high-risk Product Development quadrant. The risk Ansoff makes visible: a second summer mega-event can cannibalise sponsor budgets and fan attention from the World Cup itself rather than enlarging the pie — which is exactly the debate now running about whether the tournament justified its slot.

## Diversification: FIFA's own games

This is where the Ansoff lens earns its keep, because it forces the analyst to call FIFA's gaming push what it is: highest risk. When the [~30-year EA Sports partnership ended in 2022](https://www.gamespot.com/articles/first-post-ea-fifa-game-is-out-now-with-a-web3-marketplace/1100-6532381/), FIFA stopped collecting a licence cheque and started owning the product. **FIFA Rivals**, built by Mythical Games, is an arcade mobile title with a blockchain-based marketplace that has already passed 2.5M downloads; a **Netflix-exclusive FIFA simulation** from Delphi Interactive [launches in summer 2026](https://gamingonphone.com/news/fifa-goes-multi-game-with-new-digital-football-strategy-ahead-of-fifa-world-cup-2026), timed to the World Cup; and FIFA is assembling a multi-game ecosystem with Roblox, Epic, Konami, and SEGA aimed at an estimated 1.8B "football-loving gamers."

Why is this Diversification rather than Product Development? On both axes it is new. The product is new — FIFA has never operated as a games publisher/orchestrator; it licensed its name. And the market is new — digital-native gamers, web3 collectors, and Netflix subscribers are a different audience with different buying behaviour from the broadcast-and-ticket football fan. New product axis *and* new market axis put it in the lower-right quadrant, against entrenched incumbents (EA's now-independent *EA Sports FC*, Konami's *eFootball*) and an unproven web3 monetisation model.

## The 12-Month Four-Quadrant Sprint

Here is the original synthesis worth keeping. Most companies move through the Ansoff Matrix one quadrant at a time, over years — the way Nvidia climbed it rung by rung from 1999 to 2026. FIFA is doing something rarer and riskier: executing a move in *all four quadrants inside a single 12-month window*, from the Club World Cup in June 2025 to the Netflix game in summer 2026.

| Date | Move | Ansoff quadrant | Risk |
|---|---|---|---|
| Jun–Jul 2025 | 32-team Club World Cup, hosted in the US (~$2.1B income) | Product Development | Medium-High |
| Ongoing 2025–26 | FIFA Rivals web3 game (2.5M+ downloads); multi-game ecosystem | Diversification | High |
| Jun 11 2026 | 48-team, 104-match World Cup begins (~$8.9B) | Market Penetration | Low |
| Jun–Jul 2026 | Same World Cup converting the US/North American market | Market Development | Medium |
| Summer 2026 | Netflix-exclusive FIFA simulation launches | Diversification | High |

The sprint is what makes FIFA's risk appetite legible — and what makes it dangerous. The low-risk Market Penetration quadrant (the World Cup) is generating the cash and attention; the two Diversification bets (gaming) are the ones with no proven playbook. Ansoff doesn't say "stop" — it says *check the proportion*. As long as the World Cup cash engine throws off ~$8.9B, FIFA can underwrite two simultaneous gaming bets and a second mega-event. If the Club World Cup proves to dilute rather than add, the matrix flags that the Product Development quadrant — not the splashy Diversification one — is where the portfolio first springs a leak.

## Key takeaway

The Ansoff Matrix on FIFA in 2026 reveals an organisation that has quietly stopped being a tournament operator and become a four-quadrant growth portfolio. Market Penetration (a bigger World Cup) and Market Development (cracking the US) remain the center of gravity and the cash engine — low-to-medium risk, selling a known product to known and adjacent audiences. But the genuinely new bets — the Club World Cup in Product Development and the post-EA gaming ecosystem in Diversification — both live in the higher-risk half of the matrix, and FIFA launched them in the same year. The framework's contribution is to label that clearly and force the proportionality question: is the ~$8.9B World Cup engine generating enough cash and management bandwidth to underwrite a second mega-event *and* a from-scratch games business at once? Ansoff doesn't answer it — the post-tournament accounts will. But the model makes sure the question gets asked, instead of getting lost in the match-schedule coverage.

## Want to go deeper

This analysis anchors our [World Cup 2026 strategy series](/series/world-cup-2026) — the business of football read through frameworks; see also the [Manchester City Ansoff Matrix: the multi-club growth bet](/examples/manchester-city-ansoff-matrix-2026), the club-level mirror of the same portfolio logic, and the [World Cup 2026 PESTEL analysis](/examples/world-cup-2026-pestel-analysis), which zooms out from FIFA's growth bet to the macro forces on the USA/Canada/Mexico host economy. New to the model? Start with [Ansoff Matrix examples: the 4 growth strategies](/academy/ansoff-matrix-examples), which walks all four quadrants on real companies. Read more about the [Ansoff Matrix framework](/frameworks/ansoff), or browse other [strategy framework examples applied to real companies](/examples). For the same lens on companies anchoring their valuation to the riskiest quadrant, see the [Nvidia Ansoff Matrix analysis 2026](/examples/nvidia-ansoff-matrix-2026) and the [Tesla Ansoff Matrix analysis 2026](/examples/tesla-ansoff-matrix) — both, like FIFA, are layering Diversification bets on top of a concentrated core. To run an Ansoff analysis on an organisation you're tracking, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each quadrant.

For FIFA's SWOT counterpart, see our sister site [SWOTPal's FIFA SWOT analysis](https://swotpal.com/examples/fifa-swot-analysis?utm_source=frameworklist&utm_medium=referral&utm_campaign=ansoff-fifa) — a dedicated AI SWOT tool, free for the basic workflow.

---

### Porter's Five Forces applied to the US airline industry
URL: https://frameworklist.com/examples/five-forces-airline-industry
> Why airlines have been a structurally bad business for decades — the analysis Buffett famously got wrong twice. A worked Five Forces.

If Five Forces ever earns its keep, it's by warning you off industries that look promising but are structurally bad. Airlines are the textbook case — Warren Buffett famously called them "a value trap" and bought in twice anyway. The analysis below is the one that would have warned him both times.

## Position being analyzed

**The US passenger-airline industry as an investment / strategic destination.** Whether for an investor evaluating airline stocks, a new entrant considering a launch, or a legacy player deciding which routes to defend.

## Force 1 — Rivalry among existing competitors: HIGH

- 4 major carriers (American, Delta, United, Southwest) plus 4–6 mid-sized regionals.
- Slow industry growth (~3–5% per year ex-shocks).
- Fixed costs are enormous — planes, gates, crew. Once a flight is scheduled, marginal cost of an extra seat sold is near zero. This creates relentless pressure to drop prices to fill seats.
- Switching cost for customers is zero — they buy based on price + schedule on Google Flights.
- The product is essentially undifferentiated (everyone gets you to the same destination at the same speed).

This combination — high fixed costs, undifferentiated product, zero customer switching cost, slow growth — is the textbook recipe for ruinous price competition. Margin compression is structural.

## Force 2 — Threat of new entrants: MEDIUM-HIGH

- Capital requirements are high (a 737 is ~$100M+) but largely *financeable* via aircraft lessors.
- Pilot supply has been a real constraint post-COVID, but the binding constraint is solvable.
- Slot availability at major hubs is the real barrier — and explains why legacy carriers fortify hub airports.
- New-entrant precedent: JetBlue, Spirit, Frontier all launched in the past 25 years; some thrived briefly before getting absorbed or going bankrupt.

The entry barrier is real but not insurmountable. Every decade or so a new player shows up.

## Force 3 — Threat of substitutes: LOW (for now)

- For trips under 4 hours, driving is a substitute (60–70% modal share for trips under 300 miles).
- For business travel, video conferencing is a partial substitute (post-COVID shift was real but levelled).
- For long-haul international, no real substitute exists.

This is the only quadrant where airlines have an advantage — and even here the trajectory is uncertain (high-speed rail in markets where it exists; remote work for business travel).

## Force 4 — Supplier power: HIGH

- **Boeing + Airbus**: effectively a global duopoly on commercial airframes. Pricing power is structural; lead times for new airframes are years.
- **Oil**: jet fuel is a commodity but represents 20–30% of operating costs and is volatile. Airlines hedge but never fully escape oil-price exposure.
- **Labor**: pilots and mechanics unionized, bargaining position strong, especially post-COVID when industry was rebuilding capacity.
- **Airports**: in major hubs, the airport itself extracts a meaningful share of unit economics via gate fees, landing fees, ground services.

Four powerful supplier categories all extracting margin. This is the second structurally damaging force.

## Force 5 — Buyer power: HIGH (consumer); MEDIUM (business)

- **Leisure travelers**: extremely price-sensitive, no loyalty, choose primarily on price + schedule. Aggregators like Google Flights and Kayak amplify their power.
- **Business travelers**: less price-sensitive, but corporate travel departments increasingly negotiate centrally. Loyalty programs are management's defense.
- The airline can't price-discriminate cleanly because the same plane carries both types of buyer.

## Verdict

**Three of five forces are strongly negative; one is medium; one is the only positive.** Long-run profitability for the industry as a whole is approximately zero across decades — a result Buffett's investing partner Charlie Munger noted explicitly in 2007.

The strategic implications:

- **For investors**: stay out of the industry as a category. Individual companies occasionally outperform via execution but the structural drag is constant.
- **For incumbents**: defend hub fortresses (raises Force 2 cost for new entrants), invest in loyalty programs (raises customer switching cost), differentiate via product (premium cabins, route network).
- **For new entrants**: pick a strategy that explicitly evades the dominant forces — ultra-low-cost (Spirit / Ryanair model attacks the demand side), or premium niche (private aviation attacks the rivalry-from-substitutes angle).

## Run your own

The full Five Forces methodology is in the [Academy guide →](/academy/porters-five-forces-beginners-guide). For a tech-industry counterpart, see [Nvidia at $5T: the AI chip industry through Five Forces](/blog/ai-chip-five-forces-nvidia-5-trillion). For a SWOT pairing on a specific airline, [start a canvas →](/sign-in).

> **Want to score the five forces for your own industry?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=five-forces-airline-example) walks each force with AI-assisted prompts and keeps the scorecard in one place. Free to start.

## Related

- [Netflix through Porter's Five Forces](/examples/netflix-porters-five-forces) — an industry where one force, not three, does the damage
- [Microsoft's Five Forces 2026](/examples/microsoft-porters-five-forces-analysis-2026) — the opposite structural result: forces that compound in the incumbent's favor
- [Tesla's Five Forces 2026](/examples/tesla-porters-five-forces-2026) — a capital-intensive industry like aviation, scored on current numbers
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) — fuel prices and route regulation are macro forces, not industry structure
- [SWOT vs Five Forces](/compare/swot-vs-five-forces) — why "the industry is bad" isn't a weakness of any one airline

---

### PESTEL Analysis of France (2026): the ballast economy
URL: https://frameworklist.com/examples/france-pestel-analysis-2026
> A PESTEL analysis of France in 2026 — four prime ministers in two years, a live one-notch split between rating agencies, and an industrial programme none of the churn has touched.

![Photograph of two nuclear cooling towers releasing steam at night beside a dark river](https://images.unsplash.com/photo-1591200834528-4050ce99fe78?auto=format&fit=crop&w=1600&q=80)

The standard PESTEL of France writes itself, and it is wrong in an interesting way. Political: unstable, four prime ministers, ungovernable Assembly. Economic: stagnant, over-indebted, downgraded. Social: strikes, protests, an unpopular retirement age. Conclusion: a difficult, high-risk market. Every one of those clauses is defensible on its own, and the analysis they add up to would have told you to avoid the country that is currently building Europe's largest AI compute base on the cheapest low-carbon electricity on the continent.

The error is not in any single cell. It is in the assumption that the cells move together. [PESTEL](/frameworks/pestel) scans six external macro forces — Political, Economic, Social, Technological, Environmental, Legal — around an entity, and the implicit expectation is that a country in political crisis will show that crisis propagating outward. France in September 2026 does not do that. It splits.

This is a third distinct shape in the country series. The [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) found one force structurally holding up the other five. The [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) found one force *rewriting* the other five. France shows neither: it shows two forces churning violently while two others sit completely still, with a clean, identifiable mechanism separating them.

## Position being analyzed

The decision this analysis is built for: **should a firm treat French political instability as a reason to discount a multi-year industrial or energy commitment in France?**

That is the live question, because the headline evidence for "yes" is overwhelming and the answer is still mostly no. Getting there requires scanning the six cells separately rather than letting the loudest one set the score.

| Indicator | Latest reading | As of |
|---|---|---|
| Prime ministers since snap elections | 4 | Sept 2026 |
| Real GDP growth, 2026 forecast | 0.7% (Banque de France: 0.5%) | June 2026 |
| Public deficit target | 5% of GDP | end-2026 |
| Public debt trajectory | 121% of GDP by 2027 | 2026 forecast |
| Sovereign rating | A+ (Fitch, S&P) / Aa3 (Moody's) | Aug 2026 |
| Unemployment rate | rising to ~8.3% | 2026 |
| Statutory retirement age | frozen at 62y 9m | 1 Sept 2026 |
| Nuclear power committed to data-centre co-location | 3 GW | 2026 |

## Political — churn at the top of a system that keeps running

France has had four prime ministers since President Macron called snap legislative elections in June 2024, and the reason is arithmetic rather than scandal: the elections returned an Assembly divided into three roughly equal blocs, none able to form a working majority. Michel Barnier and François Bayrou were both brought down by budgets, and Sébastien Lecornu inherited the same problem.

He solved it the only way the constitution allows. The 2026 budget took roughly four months of deadlock, required Article 49.3 — which passes a bill without a vote — three times, and then had to survive the censure motions that 49.3 automatically invites. It did, on **2 February 2026**. The left-led motion from La France Insoumise, the Greens and the communists reached **260 of the 289 votes** needed to bring the government down. The National Rally's separate motion drew **135**. The margin was 29 votes, and the reason it existed at all was that the Socialist Party abstained in exchange for budgetary concessions.

Two things follow, and they point in opposite directions. The government is one defection away from falling, and the 2027 presidential election — for which Macron is term-limited — will make every subsequent budget harder. But the budget also *passed*, with a military spending increase in it, which is not what an ungovernable state looks like.

**Score: adverse, high volatility.**

## Economic — weak, expensive, and not disorderly

The forecasts have converged on a genuinely poor number. INSEE, the OECD and the IMF cluster around **0.7% growth in 2026**, down from 0.9% in 2025, with 2027 barely better at 0.8%. The Banque de France is more pessimistic still at **0.5%**. The proximate cause is external: conflict in the Middle East pushed energy prices up, the resulting inflation is eroding household purchasing power, and business investment is being held back by uncertainty.

The fiscal position is the harder problem. The deficit target is **5% of GDP** for 2026 — a target, not an achievement, and one that assumes consolidation continues and energy support stays contained. Debt was 113.2% of GDP in 2024 and is projected to reach **121% by 2027** and keep rising toward 122% by 2028, diverging from the euro-area average. The European Commission's assessment is blunt about the arithmetic: the fiscal stance tightens by roughly 1.5% of GDP over 2026-27, and that is **not enough to stabilise the debt ratio**.

What this cell is not is a crisis. France borrows at manageable spreads, the budget passed, and the deficit is falling. It is a slow, compounding deterioration with no visible mechanism for reversing it — which is a different risk with a different time constant.

**Score: adverse, low volatility.**

## Social — the cell where the political churn actually landed

If you want to see what the hung parliament cost, this is where to look.

Macron's 2023 pension reform — raising the retirement age toward 64 — was his flagship structural reform and the most politically expensive thing he did. In **November 2025** the National Assembly voted overwhelmingly to suspend it, and the suspension was carried in the 2026 social security budget adopted that December. It was the concession that bought the Socialist Party's abstention and kept the government alive.

The suspension became operative for pensions taking effect from **1 September 2026** — the day before this analysis was written. It freezes the statutory retirement age at **62 years and 9 months**. The direct cost is **€400 million in 2026** and **€1.8 billion in 2027**. France's public auditor has estimated that making the suspension permanent would cost around **€20 billion a year — roughly 0.5% of GDP — by 2035**, and add 3 to 4 percentage points of GDP to public debt over the decade.

Underneath it, the labour market is softening: unemployment is rising toward **8.3% in 2026** from 7.9% in late 2025.

Note the coupling that PESTEL makes visible and a SWOT would hide: the Social cell did not deteriorate for social reasons. It deteriorated because it was the only cell with something valuable enough to trade for parliamentary survival — and the cost lands in the Economic cell.

**Score: adverse, high volatility.**

## Technological — the cell that never got the memo

Across the same two years, four governments, and three rating actions, France has become the centre of European AI.

Mistral AI, founded in 2023, was valued at €11.7 billion in its September 2025 Series C and was reported in mid-2026 to be in talks to raise around €3 billion at roughly a **€20 billion valuation** — a figure reported as in-negotiation rather than closed, and worth treating as such. In March 2026 it secured $830 million specifically for data-centre expansion in the Paris area. France has attracted around **€109 billion in private AI investment commitments**, and the state's endorsement has been unusually direct, up to and including Macron publicly recommending Mistral's Le Chat over ChatGPT.

The most telling item is the **EDF–Mistral partnership signed on 28 May 2026**: a five-year agreement applying AI to EPR2 reactor engineering, maintenance and construction, with the explicit condition that data remains EDF's property on sovereign cloud or EDF-owned infrastructure. That is the state-owned nuclear utility and the national AI champion contracting with each other on digital-sovereignty terms — an arrangement that requires no parliamentary majority whatsoever.

**Score: favourable, low volatility.**

## Environmental — a structural advantage measured in terawatt-hours

France's nuclear fleet is the reason the Technological cell is possible, and it is the country's least contested asset.

At the World Nuclear Energy Summit in Paris in March 2026, Macron said France had exported **90 terawatt-hours** of decarbonised electricity in the previous year — surplus low-carbon power, sold abroad, in a continent where power is the binding constraint on AI buildout. EDF has committed **3 GW at nuclear sites for data-centre co-location**, which is the specific thing hyperscalers cannot get in most of Europe, and its long-term pricing arrangement carries a **€70/MWh ceiling** for nuclear output from 2026.

Two honest qualifiers. The **ARENH** procurement mechanism, which has governed third-party access to nuclear output for over a decade, ends in **2026**, and the transition to what replaces it is a live commercial question. And the **EPR2** new-build reactors do not come online until the **2030s**, while the data-centre commitments want power this decade. France's advantage over that gap rests on the existing fleet's output and lifetime extensions, not on new capacity.

**Score: favourable, low volatility.**

## Legal — stable domestically, loosening at the EU level

The domestic layer is the familiar one: a 35-hour statutory workweek, and comprehensive statutory coverage of overtime, annual leave, sick leave, parental leave and sabbaticals. It is rigid, it is priced into every French labour cost model, and it has not changed.

The layer that moved is European, and it moved in France's favour. The **EU AI Act's transparency obligations under Article 50 became applicable on 2 August 2026**, with systems placed on the market before that date given until 2 December 2026 to comply. But the high-risk obligations, originally due the same day, were deferred: the **AI Act Omnibus** — politically agreed 7 May 2026, published in the Official Journal 24 July, in force **27 July 2026** — pushes provider and deployer obligations for standalone Annex III high-risk systems to **2 December 2027**, and for AI embedded in products under Annex I to **2 August 2028**.

For a country staking an industrial strategy on AI, an eighteen-month regulatory reprieve at the exact moment of buildout is a material tailwind — and one delivered entirely outside the French parliament.

**Score: neutral-to-favourable, low volatility.**

## PESTEL scorecard for France, September 2026

| Force | Direction | Volatility | The single fact that sets it |
|---|---|---|---|
| **Political** | Adverse | **High** | Four PMs since June 2024; budget survived censure by 29 votes |
| **Economic** | Adverse | Low | Debt to 121% by 2027; tightening insufficient to stabilise it |
| **Social** | Adverse | **High** | Pension reform suspended, effective 1 September 2026 |
| **Technological** | Favourable | Low | EDF–Mistral five-year AI partnership, 28 May 2026 |
| **Environmental** | Favourable | Low | 3 GW nuclear committed to data-centre co-location |
| **Legal** | Neutral/favourable | Low | AI Act high-risk obligations deferred to Dec 2027 / Aug 2028 |

Read the **volatility** column rather than the direction column and the structure jumps out. The two high-volatility cells are Political and Social. The four low-volatility cells include both adverse ones and both favourable ones. Instability in France is not distributed across the scan — it is concentrated in exactly two places.

## The Ballast Test

Most country scans treat a change of government as a shock to the whole grid. It usually is not. The useful question is narrower, and it is countable:

> **The Ballast Test — during the scan window, list the policy commitments that survived every change of government, and the ones that did not. The survivors are your planning baseline. The casualties are your risk register. Then find what separates the two lists, because it is almost never importance.**

France between June 2024 and September 2026 is close to a controlled experiment: same country, same external environment, four governments.

| Commitment | Survived all four governments? | Instrument it depends on |
|---|---|---|
| EPR2 nuclear new-build programme | **Yes** | State-owned utility, multi-decade contracts |
| France 2030 / AI investment agenda | **Yes** | Executive programme, private capital |
| EDF 3 GW data-centre co-location, €70/MWh ceiling | **Yes** | Commercial contract |
| Military spending increases | **Yes** — increased in the 2026 budget | Executive priority, cross-bloc support |
| EU-level obligations (AI Act, deficit procedure) | **Yes** | Supranational law |
| 2023 pension reform (retirement age to 64) | **No** — suspended | **Ordinary legislation, needs the Assembly** |
| Barnier government | **No** — fell on a budget | **Confidence of the Assembly** |
| Bayrou government | **No** — fell on a budget | **Confidence of the Assembly** |
| The original deficit trajectory | **No** — repeatedly slipped | **Annual finance bill, needs the Assembly** |

The separator is not sector, not importance, and not popularity. **Everything in the casualty list required a parliamentary majority. Nothing in the survivor list did.** France's hung Assembly is a precise instrument: it can destroy a pension reform and two governments, and it has no mechanism at all for touching EDF's commercial contracts, a state investment programme, or a supranational directive.

That is what makes the standard read wrong. "Political instability" is not a scalar that discounts every French commitment equally. It discounts, sharply, anything whose delivery route passes through the Assembly — statutory reform, tax rates, social policy, the deficit path. It barely touches anything delivered through the executive, a state-owned enterprise, a commercial contract, or Brussels.

The Ballast Test is the inverse of the [Reversal Test introduced in the Canada analysis](/examples/canada-pestel-analysis-2026). Canada's scan counted what a government had *withdrawn* and found the reversals clustered in four of six cells — a country where the policy baseline is unreliable across the board. France's scan counts what *survived* and finds the survivors clustered by constitutional instrument. Same six cells, same question, opposite finding: Canada's instability generalises and France's does not.

The [Argentina analysis](/examples/argentina-pestel-analysis-2026) runs the same instrument sort forward instead of back, as the **Lock-In Ladder**, and finds the ranking inverted: when the threat is a new president rather than a hung Assembly, executive policy is the weakest instrument, not the strongest.

### The split notch

There is a second, smaller finding that most France commentary flattens, and it bears directly on the test above.

The usual summary is that France was downgraded three times in about a year. That count is defensible — **Fitch** cut France from AA− to A+ on **12 September 2025**, **S&P** followed to A+ on **18 October 2025**, and **DBRS** also cut — but stating it as a bare count implies unanimity that does not exist. **Moody's did not downgrade.** On **24 October 2025** it *affirmed* France at **Aa3** — the equivalent of AA−, one notch above A+ — and changed only the outlook to negative. Fitch subsequently affirmed A+ with a **stable** outlook on **28 August 2026**.

So France carries a live one-notch split: AA−-equivalent at Moody's, A+ at Fitch and S&P. The split is not noise, because Moody's said what would resolve it. Its outlook could return to stable, it wrote, if the difficulties in France's legislative institutions **prove temporary**, or if there is a **resumption of pension reforms**.

Those are the two conditions, and they map exactly onto the two high-volatility cells in the scorecard. One of them has since been decided: the Assembly did not resume pension reform, it suspended it, effective 1 September 2026. The optimistic case now rests entirely on the first condition — on the hung parliament being a passing phase rather than the shape of French politics through 2027 and beyond.

## Counter-argument: doesn't the fiscal cell eventually reach the ballast?

The strongest objection to everything above is that the wall between the two groups is not permanent, only slow. Debt heading to 121% of GDP with an insufficient consolidation path does eventually constrain state investment capacity, and France 2030, EPR2 and EDF's balance sheet are all ultimately state-adjacent. On a long enough horizon, the Economic cell does reach the ballast.

That is correct, and it is the right reason to bound the claim rather than abandon it. Three things bound it. First, the transmission is slow — fiscal deterioration reaches an already-contracted 3 GW co-location commitment over years, not budget cycles. Second, the direction of travel in the ballast cells is currently *favourable*, and rising: AI capital is arriving, not leaving. Third, the deficit is falling even in this parliament, which is weak evidence that the constraint binds gradually rather than abruptly.

The honest formulation is that the Ballast Test tells you which commitments are exposed to the *next two years* of French politics, not which are exposed forever. It is a horizon-scoping tool, and the horizon it scopes is the one most market-entry and capital-allocation decisions actually run on.

## Key takeaway

France in September 2026 fails the test most country PESTELs implicitly apply — "is this a politically stable place to commit capital?" — and passes the test that actually matters, which is narrower: *is the specific thing I am committing to exposed to the instability?*

For a firm weighing a multi-year French commitment, the operational conclusion is specific. **Anchor on what the Ballast Test shows surviving** — the nuclear fleet's output and its contracted pricing, EDF's co-location capacity, the AI capital base, EU-level regulatory timelines — and treat as provisional anything delivered by statute: tax rates, social charges, retirement age, sector levies, and the deficit path they fund. A power purchase agreement with EDF and an assumption about French payroll taxes in 2029 are not the same class of risk, and the standard "political instability" discount prices them identically.

The two dates that will most cheaply update this analysis are the passage of the 2027 budget — the first to be negotiated under the shadow of the presidential election — and the resolution of the ARENH successor arrangement, which determines whether the €70/MWh nuclear ceiling survives the mechanism that produced it.

> Want to run a PESTEL on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a PESTEL worksheet with all six forces and AI assistance for the scan.

## Want to go deeper

- [PESTEL framework](/frameworks/pestel) — the six forces, and how to score them
- [How to do a PESTEL analysis](/academy/how-to-do-a-pestel-analysis) — the step-by-step method
- [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) — one force holding up the other five
- [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) — one force rewriting the other five, and the Reversal Test
- [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026) — six cells that all contain enacted policy, and the Disbursement Gap that dates when each one lands
- [PESTEL analysis of the European Union (2026)](/examples/europe-pestel-analysis-2026) — six cells governed by different governments, and the Competence Test: score each cell only at the level that holds the lever
- [PESTEL analysis of China (2026)](/examples/china-pestel-analysis-2026) — six cells that each return two readings with opposite signs, and the Two-Ledger Test: score the production reading and the household reading separately and route each to the decision it governs
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) — when the macro scan is the wrong tool

*Cover photo: [Nicolas HIPPERT on Unsplash](https://unsplash.com/photos/C82jAEQkfE0).*

---

### PESTEL Analysis of Germany (2026): the disbursement economy
URL: https://frameworklist.com/examples/germany-pestel-analysis-2026
> A PESTEL analysis of Germany in 2026 — a €500bn fund 28% disbursed, and September state elections that put the 2027 tranche itself back in political play.

![Photograph of an unfinished steel building frame beside a tower crane against a blue sky](https://images.unsplash.com/photo-1527335988388-b40ee248d80c?auto=format&fit=crop&w=1600&q=80)

Germany in 2026 is the rare country scan where nothing important is missing. Ask what the state is doing about stagnant growth and there is a €500 billion answer with a name, a legal basis and a line in the budget. Ask about the energy costs that have been driving chemical and steel production offshore and there is a subsidised industrial tariff, approved by Brussels, live since January. Ask about defence and there is a constitutional amendment written specifically to get the spending out from under the borrowing limit.

Every cell has its policy. The scan still comes out badly, and the reason is not in any cell's *content*. It is in each cell's **date**.

[PESTEL](/frameworks/pestel) scans six external macro forces — Political, Economic, Social, Technological, Environmental, Legal — around an entity, and the standard way of scoring it asks whether each force is favourable or adverse. That question produces a misleading answer for Germany, because most of the favourable forces are appropriations whose effects are scheduled for a future the political cell may not reach intact.

This is a fourth distinct shape in the country series. The [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) found one force structurally holding up the other five. The [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) found one force rewriting the other five. The [PESTEL analysis of France (2026)](/examples/france-pestel-analysis-2026) found the cells splitting into two groups by constitutional instrument. Germany shows something none of those do: six cells that are all, in a specific and measurable sense, **early**.

## Position being analyzed

The decision this analysis is built for: **should a firm treat Germany's announced fiscal and industrial-policy turn as a reason to commit capital in 2026, or wait?**

That is the live question because the announcement is enormous, genuinely funded, and roughly two-thirds undelivered against its own schedule. A scan that scores the policy scores a "yes." A scan that scores the delivery does not.

| Indicator | Latest reading | As of |
|---|---|---|
| Real GDP growth, 2026 forecast | **0.6% to 1.4%** depending on forecaster | mid-2026 |
| Infrastructure fund 2026 budget deployed | **~€11bn of €40bn (28%)** | April 2026 |
| Infrastructure fund 2026 milestones achieved | **26 of 107** | end May 2026 |
| Infrastructure fund 2025 disbursement | ~€24bn against €37.2bn planned | full-year 2025 |
| Total government investment, 2026 | €126.7bn — a record, +10% year on year | 2026 budget |
| New federal borrowing, 2026 | >€180bn, more than triple 2024 | 2026 budget |
| AfD / CDU-CSU national polling | ~28-29% / ~20% | September 2026 |
| Coalition seat share on current polling | ~37.9% | mid-2026 |
| AfD, Saxony-Anhalt / Mecklenburg-Vorpommern | **43.8% / 38.2%** — first in both | 6 / 20 Sept 2026 |
| CDU, Mecklenburg-Vorpommern | **4.9% — below the threshold, zero seats** | 20 Sept 2026 |
| Infrastructure fund plan in the draft 2027 budget | €54.9bn — the budget the SPD now wants reopened | draft of 6 July 2026 |
| Statutory minimum wage | €13.90 per hour | 1 January 2026 |
| Firms reporting skilled-labour scarcity | 22.7% — a five-year low | 2026 |

## Political — a governing majority that polling no longer reproduces

The Merz cabinet took office on 6 May 2025 as a CDU/CSU–SPD grand coalition following the February 2025 federal election, and it holds a working Bundestag majority. The problem is that the majority is a fact about February 2025 and increasingly not a fact about the country.

National polling now puts the **AfD first at roughly 28-29%**, against about **21% for the CDU/CSU**, with the SPD in the low teens. On those numbers the two governing parties together would take around **37.9% of seats** — not a majority. Nothing forces an election, so this does not threaten the government's survival directly. What it does is raise the political cost of every slow, unglamorous administrative decision the fiscal programme depends on.

When this scan was first published on 4 September, the immediate test was three weeks long and about to start. It has now run. **Saxony-Anhalt voted on 6 September**: the AfD took **43.8%** and 39 of 83 seats, three short of a majority, and the CDU fell to **17.2%**, its worst result in the state, losing every constituency. **Mecklenburg-Vorpommern voted on 20 September**: the AfD won again with **38.2%** against **35.5%** for the governing SPD, and the CDU took **4.9%** — below the 5% threshold, and so no seats at all. The same day in **Berlin**, Die Linke came first with **25.7%**, ahead of the CDU on **18.8%**. Merz called the Mecklenburg-Vorpommern result a "disaster" and said he would stay.

Earlier in the 2026 cycle, Baden-Württemberg had returned roughly **18.8%** for the AfD, close to double its **9.7%** in 2021. Every other major party maintains the *Brandmauer*, a refusal to govern with the AfD, and the original version of this section predicted that strong AfD results would therefore produce harder coalition arithmetic at Land level rather than AfD-led governments. That held. In Saxony-Anhalt the AfD's 39 seats face a hypothetical four-party bloc of exactly 39, the CDU has said it will sit in opposition, and the five BSW seats decide which way it breaks. The scan was less right about where the pressure would go next; see [the Two-Clock Score](#scored-the-september-elections-and-the-two-clock-score) below.

That matters for the rest of this scan for one concrete reason: the federal states are the delivery mechanism for a large share of the infrastructure fund.

**Score: adverse, high volatility.**

## Economic — the forecasters are further apart than the thing they disagree about

The 2026 growth forecasts do not cluster. They split, cleanly, into two camps:

| Forecaster | 2026 real GDP growth |
|---|---|
| Deutsche Bundesbank | **0.6%** |
| European Commission | **0.6%** |
| IMF | 1.1% |
| ifo Institute | **1.4%** (raised 0.6pp from June) |
| Goldman Sachs | **1.4%** |

The spread is **0.8 percentage points**. The fiscal expansion that the optimistic camp is counting is generally estimated to contribute **about 0.3 points** to 2026 growth.

Sit with that arithmetic, because it is the whole German story in one line. **The disagreement between forecasters is roughly two and a half times larger than the stimulus they are disagreeing about.** They are not arguing over the size of the package — that number is legislated and public. They are arguing over whether it shows up, and how much of the rest of the economy moves in anticipation of it.

The appropriations themselves are not in doubt. Total government investment for 2026 is budgeted at **€126.7 billion**, the highest in German history and about 10% above 2025. New federal borrowing in 2026 is expected to exceed **€180 billion** — more than triple the 2024 level and the highest since the pandemic.

**Score: adverse, high volatility — and the volatility is measurement volatility, not economic volatility.**

## Social — the labour market that stayed tight through a stagnation

The German labour market has spent four years refusing to behave like the economy attached to it. Even with growth at or near zero, **22.7% of German businesses report a shortage of skilled workers** — and the notable thing is that this is a *five-year low*. Four years of stagnation has taken the shortage from acute to merely severe.

The statutory minimum wage rose to **€13.90 per hour on 1 January 2026**, which by Destatis figures leaves only Luxembourg and the Netherlands with higher monthly minimums in the EU, and employers pay roughly **20% on top of gross salary** in social contributions for pensions, health, unemployment and care. The demographic direction underneath is the familiar one: an ageing population, continuing urbanisation, and older cohorts carrying more of the discretionary spending.

For a firm doing a siting analysis this is the cell that is *not* early. The labour cost and labour scarcity are both live now, in full, with no phase-in.

**Score: adverse, low volatility.**

## Technological — the cell where the money is slowest

Germany's technological position in 2026 is the infrastructure story in miniature. New process technology is being deployed in manufacturing; ICT skills shortages persist and constrain the rate at which it can be. And when the Finance Ministry's monitoring report ranked where the fund's progress was weakest, **research and development appeared alongside energy infrastructure and transport** at the bottom of the progress and impact indicators.

That is the least surprising finding in the report and the most consequential. R&D disbursement is the part of the programme whose effects arrive latest even when it runs on time; delay there compounds against a delivery horizon that already sits beyond the current parliament.

**Score: neutral, low volatility — favourable on paper, unrealised.**

## Environmental — a real price cut with a three-year expiry

The industrial electricity price is the cleanest single illustration of the pattern in this scan, and it is genuinely good news, so it is worth stating both halves precisely.

Electricity-intensive firms — steel, chemicals, automotive — have argued for three years that they cannot compete with power costs close to double those in the United States, and the wholesale price has not returned to its pre-2022 level. The government's response became eligible on **1 January 2026**: a subsidised rate targeting roughly **5 euro cents per kWh** for qualifying firms. It cleared European Commission state-aid review on **16 April 2026**, carries a volume of about **€3.8 billion**, and runs **2026 to 2028**.

Every one of those facts is favourable. Two of them are also the problem. The scheme needed sixteen months from commitment to state-aid clearance, and it expires in three years — so a firm making a twenty-year siting decision is being offered a three-year price. Set against that, wholesale power fell about 6.7% and renewables reached roughly 55% of generation, which is a structural improvement that does not expire in 2028.

**Score: favourable, low volatility — with a stated end date.**

## Legal — the enabling act arrived a year before the rules

Germany's legal cell in 2026 is unusual because the headline event was deliberately *enabling*: in **March 2025** the parties agreed to amend the constitutional debt brake, exempting defence spending above a threshold from the borrowing limit and creating the €500 billion infrastructure and climate fund alongside a €100 billion defence fund. That is a rare thing — a country loosening its own fiscal constitution on purpose, and doing it by constitutional amendment rather than by emergency clause, which makes it durable.

Then the second-order legal detail, which is where the money actually went missing. The **administrative rules governing how the federal states draw down their share of the fund were only finalised at the end of 2025**. The constitutional change was complete in March 2025; the instrument that let a Land actually requisition money was complete roughly nine months later. Clean Energy Wire's summary of the government report is direct about the consequence: because of the change of government and the absence of legal requirements for state-level spending in 2025, only a few months of that year could effectively be used to disburse anything.

**Score: favourable, low volatility — and it is the cell that created the gap in all the others.**

## PESTEL scorecard for Germany, September 2026

| Force | Direction | Volatility | The single fact that sets it |
|---|---|---|---|
| **Political** | Adverse | **High** | AfD first in two of three September Land elections; SPD now wants the 2027 budget reopened |
| **Economic** | Adverse | **High** | 0.8pp forecast spread around a ~0.3pp fiscal impulse |
| **Social** | Adverse | Low | €13.90 minimum wage plus ~20% employer contributions, live now |
| **Technological** | Neutral (unrealised) | Low | R&D among the weakest progress areas in the fund's own report |
| **Environmental** | Favourable | Low | ~5 ct/kWh industrial tariff, EU-approved 16 April 2026, ends 2028 |
| **Legal** | Favourable | Low | Debt brake amended March 2025; Länder drawdown rules only end-2025 |

Read the direction column alone and Germany looks like a country with four problems and two advantages. Read it beside the dates in each section and a different structure appears: **every adverse cell is in effect today, and every favourable cell has a delivery date in the future.**

## The Disbursement Gap

Country scans habitually score a policy on the day it is announced. For most countries most of the time that is a tolerable approximation, because enactment and effect are close together. Germany in 2026 is the case that breaks the approximation, and it suggests a sharper question:

> **The Disbursement Gap — for each PESTEL cell, write down two dates: when the policy was legally enacted, and when money or effect actually reaches the economy. Score the cell on the interval between them, not on the announcement. Then check the interval against the political clock, because a commitment that lands after the government that made it is a different asset from one that lands before.**

Germany makes this countable in a way most scans do not, because the government publishes the delivery data itself.

| Commitment | Enacted | Effect reaching the economy | Gap |
|---|---|---|---|
| Debt brake amendment / €500bn fund | March 2025 | Länder drawdown rules finalised **end-2025** | ~9 months before money could move at all |
| Fund disbursement, 2025 tranche | 2025 budget | **~€24bn spent against €37.2bn planned** | ~35% of the year's tranche undelivered |
| Fund disbursement, 2026 tranche | 2026 budget | **~€11bn of €40bn by April; 26 of 107 milestones by end May** | ~72% of the year's budget still unreleased at the one-third mark |
| Industrial electricity price | Coalition commitment, 2025 | Eligible 1 Jan 2026; **EU state-aid clearance 16 April 2026** | ~16 months, and the scheme expires 2028 |
| €100bn defence fund | March 2025 | Multi-year procurement cycles | Years |
| Minimum wage €13.90 | Legislated 2025 | **1 January 2026, in full** | **Zero** |
| Skilled-labour shortage (22.7% of firms) | — | **Now** | **Zero** |

The pattern is not subtle once the column exists. **Every cost in the German scan has a gap of zero. Every benefit has a gap measured in quarters or years.** A firm evaluating Germany on the 2026 policy package is being asked to pay the wage bill, the social contributions and the labour scarcity immediately, in exchange for infrastructure, energy and R&D benefits that the government's own monitoring report shows running at roughly a quarter to two-thirds of schedule.

This is also what resolves the forecast split rather than merely describing it. The Bundestag appropriated a number; the Bundesbank is forecasting the delivery rate and the ifo Institute is forecasting the appropriation. Both are internally consistent. They are answering different questions, and the Finance Ministry's 28% is the first hard evidence on which question was the right one — at least for the first third of 2026.

### Why the gap is procedural, not fiscal

The distinction matters for anyone deciding whether to wait, because procedural gaps close and fiscal gaps do not.

Nothing in the German shortfall is a funding problem. The money exists, is borrowed, and sits outside the debt brake by constitutional amendment. The stated causes are all administrative: a change of government consumed most of the 2025 window, the Länder drawdown rules were finished nine months after the enabling amendment, and the weakest-performing categories — energy infrastructure, transport, R&D — are precisely the ones with the longest German planning-permission and procurement chains.

That is a genuinely more optimistic diagnosis than "the stimulus failed," and it has a testable implication: **procedural gaps produce catch-up, so the 2027 tranche should over-deliver relative to its own budget if the diagnosis is right.** If it does not, the constraint was never the paperwork.

## Scored: the September elections, and the Two-Clock Score

This scan named its own test when it was published on 4 September: three state elections inside the month. All three have now been held, so the claims can be scored rather than left to age.

| What the 4 September scan said | What happened | Verdict |
|---|---|---|
| Strong AfD results would mean harder coalition arithmetic, not AfD-led governments | AfD first in Saxony-Anhalt (43.8%) and Mecklenburg-Vorpommern (38.2%); no party offered it a coalition; Saxony-Anhalt deadlocked at 39 seats to 39 | **Right** |
| Mecklenburg-Vorpommern polling had the AfD first at ~36% | 38.2%, first | **Right**, and slightly understated |
| An outright AfD majority in Saxony-Anhalt was being seriously discussed | 39 of 83 seats, three short | **Did not happen**, narrowly |
| The risk is not that the government falls but that it spends its term managing its own survival | Merz at ~14% approval; open talk of replacing him or a confidence vote; he is staying | **Right so far** |
| Political risk falls on the *back half* of the €500bn programme; the 2026 and 2027 tranches are "probably" safe | Within days the SPD called for the 2027 budget, which carries the fund's €54.9bn plan for next year, to be reopened | **Wrong about timing** |
| The appropriations themselves are not in doubt | Still true of the €500bn total, which is constitutional; **no longer true of the 2027 annual plan**, which passes with the budget | **Partly wrong** |

The last two rows are the useful ones, because they are one mistake. The Disbursement Gap measures a single clock: how long money takes to get from the budget line to the economy. The original scan then compared that clock to one political date, the 2029 federal election. The mistake was treating the political clock as though it only resets at a federal election. In Germany it resets every time the coalition has to pass a budget, and the next one was only months away.

> **The Two-Clock Score — for each favourable PESTEL cell, write down two dates: when the money reaches the economy (the delivery clock), and the next date on which the government that appropriated it must win a vote to keep it (the political clock). If the political date comes first, score the cell on the vote, not on the delivery schedule.**

Applied to Germany as of 23 September 2026:

| Commitment | Delivery clock | Next political date | Which comes first |
|---|---|---|---|
| €500bn fund, total | 2030s, by constitutional amendment | A two-thirds majority to repeal it | **Delivery** — the total is safe |
| Fund, 2026 tranche (€40bn) | Running at ~28% by April | Already appropriated | **Delivery** — a disbursement question only |
| Fund, 2027 tranche (€54.9bn) | Calendar 2027 | **The 2027 budget vote, now contested** | **Political** |
| Industrial electricity price | Live since January, ends 2028 | Already approved by the EU | **Delivery** |
| Pension and care reforms | Legislation promised by end-2026 | Reopening demanded by the SPD | **Political** |

The upshot for a firm is narrower than "Germany got riskier". The scan's six directions do not change. What changes is that **one specific item, the 2027 tranche, has moved from a timing question to a political one**, and a firm that was pricing 2027 infrastructure demand on the draft budget's €54.9 billion should now treat that figure as provisional until the budget passes. The constitutional total and the 2026 money are unaffected.

## Counter-argument: isn't a slow start exactly what a ten-year programme looks like?

The strongest objection to everything above is that the fund is a multi-year programme being judged on its first sixteen months, and that front-loaded appropriation with back-loaded delivery is the normal shape of infrastructure spending everywhere. Twenty-eight percent by April with a December year-end is not obviously behind; large public works ramp.

That objection is largely right on the economics and it is why the diagnosis above is "gap," not "failure." What it does not dispose of is the political clock. Germany's programme runs to the 2030s and the coalition that created it is polling below the party it excludes, with a federal election due in 2029 and, as of September, AfD wins in two of the three Land elections held this month. Delivery risk in a country with Germany's administrative capacity is genuinely low over a decade. The question a firm actually faces is narrower: **does the benefit arrive inside the horizon of the government that appropriated it?** The original answer here was "probably yes" for the 2026 and 2027 tranches. The September results have already cut that to the 2026 tranche alone, as scored above. For the back half of a €500 billion programme, it is still a bet on a 2029 coalition nobody can currently name.

The honest bound on the Disbursement Gap, then, is that it is a *timing* instrument rather than a *credibility* instrument. It does not tell you the money is fake. It tells you which of your own decisions can be made on the appropriation and which need to wait for the disbursement.

## Key takeaway

Germany in September 2026 fails the test that country scans implicitly apply — "is the macro environment favourable?" — and the failure is entirely a timing artefact. Six cells, six substantive enacted policies, and a scorecard where every adverse force is live today and every favourable force has a future delivery date attached, running at roughly 28% of its own 2026 schedule as of April.

For a firm weighing German exposure, the operational conclusion follows directly from the gap column. **Decisions whose costs land in 2026 — hiring, wage bills, siting anything labour-intensive — should be priced on the adverse cells, which are fully in effect.** Decisions that consume the benefits — energy-intensive production, infrastructure-dependent logistics, R&D co-investment — should be priced on the *disbursement* rate, not the appropriation, and should treat the three-year expiry on the industrial electricity price as the binding date rather than the 2030s horizon of the fund.

The original version named two readings that would update this analysis most cheaply. The September Land results are in and are scored above. They left the six directions unchanged, but they moved the 2027 tranche from a timing question to a political one. What remains is the Finance Ministry's next monitoring report, which will show whether the 28% closed over the second half of 2026, and the **2027 budget vote**, which decides whether €54.9 billion of next year's fund plan survives as drafted.

> Want to run a PESTEL on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a PESTEL worksheet with all six forces and AI assistance for the scan.

## Want to go deeper

- [PESTEL framework](/frameworks/pestel) — the six forces, and how to score them
- [How to do a PESTEL analysis](/academy/how-to-do-a-pestel-analysis) — the step-by-step method
- [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) — one force holding up the other five, and the Load-Bearing Force Test
- [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) — one force rewriting the other five, and the Reversal Test
- [PESTEL analysis of France (2026)](/examples/france-pestel-analysis-2026) — cells splitting by constitutional instrument, and the Ballast Test
- [PESTEL analysis of the European Union (2026)](/examples/europe-pestel-analysis-2026) — six cells governed by different governments, and the Competence Test: score each cell only at the level that holds the lever
- [PESTEL analysis of China (2026)](/examples/china-pestel-analysis-2026) — six cells that each return two readings with opposite signs, and the Two-Ledger Test: score the production reading and the household reading separately and route each to the decision it governs
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) — when the macro scan is the wrong tool

*Cover photo: [Jacek Dylag on Unsplash](https://unsplash.com/photos/nhCPOp4A2Xo).*

---

### Ikigai Career Example: The Four Circles Pointed at Google
URL: https://frameworklist.com/examples/ikigai-turning-down-google
> A real career decision replayed through the Ikigai diagram — Alice Bentinck turned down Google in her own published account, and three of the four circles said she was wrong.

![Photograph of a forest path splitting into two trails between trees](https://images.unsplash.com/photo-1429743305873-d4065c15f93e?auto=format&fit=crop&w=1600&q=80)

Almost everything written about the [Ikigai diagram](/frameworks/ikigai) demonstrates it on a person who does not exist. The four circles are drawn, a hypothetical teacher or designer is placed at the centre, and the intersection resolves neatly, because the example was constructed backwards from the answer.

This is the opposite. It takes one real career decision, published by the person who made it, replays it through the four circles using **only the information available at the time** — and the diagram gets it wrong.

That is more useful than another clean example. A framework you have only ever seen succeed is not a framework you know how to use.

## The decision

In October 2015, Alice Bentinck published a short essay on Medium titled ["Why I turned down Google and so should you."](https://medium.com/@Alicebentinck/why-i-turned-down-google-and-so-should-you-c1420dc72825) It is a first-person account, under her own name, of a decision she had made some years earlier on leaving McKinsey & Co.

She opens by saying she already knew what she wanted:

> "When I was leaving McKinsey & Co, I knew that I wanted to build a startup... I knew that building a startup was a way for me to get intense satisfaction from my career.
>
> But instead of founding a startup, I got a job."

Then she lists the three things that pulled her the other way — and they are the three that pull almost everyone:

1. **"I was told that startups fail."** Her peers' response to her wanting to found a company was that most startups fail.
2. **"It felt risky to leave a prestigious company."** It gave her social approval, from peers and future employers.
3. **The Google offer.** "My peers kept on telling me how lucky I was — 'think of the free food!'"

Her answer to the third one is the sentence the whole replay turns on:

> "I wasn't excited by the job at Google. I wanted to build a startup, so why would I invest time doing anything other than that?"

Her own summary: *"I left McKinsey, turned down Google and created Entrepreneur First with my co-founder Matt Clifford."*

## What she actually knew at the time

This table contains no hindsight. It is the state of the decision as her essay describes it — which is the only fair input for a replay.

| Input | Google offer | The unstarted company |
|---|---|---|
| Compensation | Market-leading, immediate | **£0** |
| Evidence she could do it | An offer in hand from Google, plus McKinsey | None yet — no company, no product |
| Co-founder | n/a | **Not yet found** |
| Peer verdict | "Think of the free food" | "Most startups fail" |
| Social proof | High, immediate | None |
| Her own stated enthusiasm | **"I wasn't excited by the job"** | "Intense satisfaction from my career" |
| Downside if wrong | Leave and take another job | Unemployed, with a failed venture attached |

## The four circles, run on that table

The [framework page](/frameworks/ikigai) defines the fourth circle precisely, and the precision matters here: *what the market currently pays you, **today, not hypothetically***.

| Circle | Google | The unstarted company |
|---|---|---|
| **What you love** | ✗ — "I wasn't excited by the job" | ✓ |
| **What you're good at** | ✓ — they made her an offer | ✓ — McKinsey-trained, but unproven at this |
| **What the world needs** | ~ arguable | ~ arguable |
| **What you can be paid for** | **✓✓ — decisively** | **✗ — it pays nothing, today** |

Score it the way the diagram is drawn — four co-equal circles converging on one intersection — and **Google wins three-to-one with one tie.**

The diagram would not even have flagged this as close. Google sits squarely in the pair-quadrant the framework page already names: **Profession**, the overlap of *good at* and *paid for*, described there as *"Competent and well compensated. Also hollow — the burnout quadrant."* The diagram knows that quadrant is a trap. Its own scoring still walks into it, because three ticks beat one.

## The Decision Replay

| What the framework says | What she actually did | What actually happened |
|---|---|---|
| **Take the Google offer.** Three of four circles favour it, including the one that is unambiguous. The alternative satisfies exactly one circle and fails the pay circle by the framework's own strict definition. | Turned down Google. Founded **Entrepreneurs First** with Matt Clifford in 2011 — a "talent investor" backing people before they have a company, a team, or an idea. | EF raised **$200M at a $1.3B valuation** in 2026. Companies built through it are worth **$16bn**, up from $3bn at its 2021 raise, across **600+ companies**. Bentinck is now CEO. |

The diagram was not marginally wrong. It was wrong in the direction of the safe, legible, well-compensated option — which is the direction a framework is supposed to protect you *from*.

## The Hygiene Circle

Here is the part that makes this more than an anecdote. Bentinck, in the same essay, reaches for a framework to explain her decision — and **it isn't Ikigai.**

She notices that when people describe what is good about a big-company job, they name sleep pods and free food, and she asks the obvious question:

> "If these are the best parts of your job, why are none of them to do with the actual work?
>
> These are peripheral benefits. These are hygiene factors. They stop you from being dissatisfied, but do they give you deep job satisfaction?"

That is [Frederick Herzberg's two-factor theory](https://www.simplypsychology.org/herzbergs-two-factor-theory.html), from *The Motivation to Work* (1959) and the 1968 *Harvard Business Review* article "One More Time: How Do You Motivate Employees?" — the most reprinted article in HBR's history. Herzberg's claim is that job factors fall into two categories that are **not opposites**:

| | Examples | What it can do |
|---|---|---|
| **Hygiene factors** | Salary, working conditions, company policy, supervision, perks | Remove dissatisfaction. **Cannot create satisfaction.** |
| **Motivators** | Achievement, recognition, responsibility, the work itself, growth | Create satisfaction. Their absence does not create dissatisfaction. |

Now lay that over the four circles, and the asymmetry is impossible to miss:

> **The Hygiene Circle — three of Ikigai's four circles are motivators and one is a hygiene factor, but the diagram draws all four the same size. "What you can be paid for" is a threshold, not a score. Ask it as a yes/no — does this option clear my floor? — and then make the decision on the other three. The moment you let it vote, a factor that by Herzberg's evidence cannot produce satisfaction is outranking three that can.**

Run Bentinck's decision that way and it resolves in one line. Does the unstarted company clear her floor? She was leaving McKinsey with a Google offer in hand — her downside was another job. **Yes, it clears.** Then decide on love, skill and need — where the startup wins on the circle she describes as producing "intense satisfaction," and Google loses on the one she names outright.

Same four circles, same inputs, opposite answer. The only thing that changed is that one circle stopped being allowed to vote.

## Where this misleads

Three limits, and they are load-bearing rather than decorative.

**This is a survivorship case.** Most people who turn down a Google offer do not build a company worth $1.3B, and the ones who do not are not writing essays. The Hygiene Circle does **not** say take the risk. It makes a much narrower claim: pay should not be the *reason* the decision goes either way, because it cannot produce satisfaction in either direction. That is compatible with staying.

**A threshold you cannot afford to set is not a threshold.** Bentinck's floor was unusually cheap to clear — McKinsey optionality is itself a form of safety, and "my downside is another good job" is not most people's downside. For someone with dependants, a visa tied to an employer, or no savings, the pay circle genuinely *is* the decision, and no reframing changes that. The Hygiene Circle applies above the floor, not to people standing on it.

**Herzberg is contested.** The two-factor split came from critical-incident interviews with accountants and engineers in Pittsburgh. Vroom (1964) and House and Wigdor (1967) argued the result reflects **attribution bias** — people credit themselves for their satisfactions and blame conditions for their dissatisfactions — which would make the clean separation an artifact of the interview method rather than a feature of work. The theory has also been criticised for generalising from individualist, middle-class, professional settings. Treat the hygiene/motivator split as a useful lens with real empirical baggage, not as settled fact.

And one about the diagram itself, which the [framework page](/frameworks/ikigai) documents at length: the four-circle Venn is not Japanese. It was drawn by Andrés Zuzunaga in 2011 as a model of *purpose*, and Marc Winn swapped the centre word to *ikigai* on 14 May 2014. Bentinck's essay is from October 2015 — seventeen months after the diagram went viral, and she still didn't reach for it. That is a data point in its own right.

## Now run yours

The replay above is only useful if you do it on your own fork. Three steps, in order:

1. **Write the "what you actually know" table first**, before any framework. Two columns, and be honest about the empty cells — the unstarted option is *supposed* to have blanks.
2. **Ask the pay circle as a yes/no.** Does the weaker-paying option clear your actual floor — not your current salary, your floor? If no, stop; the decision is made and no framework will unmake it. If yes, the circle has done its job and is now out of the discussion.
3. **Decide on the remaining three**, weighted by which one you would most regret being wrong about.

For step 1 and step 3, the [free Pros and Cons worksheet](/tools/pros-and-cons) is the fastest way to get both columns out of your head and onto something you can look at — it runs in the browser with no signup.

> Want the four circles on your phone, with AI help filling them in? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships an Ikigai worksheet alongside 100+ other frameworks.

## Want to go deeper

- [Ikigai framework](/frameworks/ikigai) — the four circles, the pair-quadrants, and the full provenance chain for the diagram
- [Pros and Cons](/frameworks/proscons) — the right tool once the pay circle is settled and you are choosing on the other three
- [Regret Minimization](/frameworks/regretmin) — the framework for step 3, when the deciding question is which mistake you could live with
- [Pre-mortem](/frameworks/premortem) — run before you commit: assume the choice failed, and work backwards to why
- [Pre-mortem Example: The Failure a Premortem Cannot Catch](/examples/premortem-cydoc-shutdown) — the other Decision Replay, on a startup shutdown with a published nine-cause postmortem
- [Pros and Cons Example: 9 Pros, 5 Cons, and the One That Decided It](/examples/proscons-cto-to-ic) — a replay where the framework returns the right answer for the wrong reason

*Cover photo: [Jens Lelie on Unsplash](https://unsplash.com/photos/u0vgcIOQG08).*

---

### PESTEL Analysis of India (2026): six cells, three imported
URL: https://frameworklist.com/examples/india-pestel-analysis-2026
> A PESTEL analysis of India in 2026 — 7.8% growth, a rupee at 96, a $104 crude basket, the Graham Act's 100% tariff threat, a 14% monsoon deficit, and the Imported-Cell Test.

![The Bandra-Worli Sea Link bridge crossing the Arabian Sea in Mumbai under an overcast sky](https://images.unsplash.com/photo-1552133457-ce1d2d33cdfb?auto=format&fit=crop&w=1600&q=80)

Every PESTEL of a country makes a silent assumption about *who is holding the pen*. Score the Political cell and you are scoring the government; score the Economic cell and you are scoring the economy that government runs. The six cells have one author, and the reader's job is to judge how well the author is writing.

India in September 2026 is where that assumption breaks. The government in New Delhi is, by any reading of its own cells, writing well: GDP grew **7.8%** in April-June, real fixed investment rose **11.9%**, the deficit is on a **4.3%** glide path with capital spending up **11.5%**, the central bank has been able to sit at **5.25%** for four meetings, and the first digital census, the four labour codes and the data-protection rules are all in their first year. Then look at the three readings most likely to decide the year — a crude basket at **$115.98**, a rupee at a record **96** per dollar, a US law signed **two days ago** authorising **100%** tariffs on the largest buyer of Russian oil, which is India — and none of them was written in India. The war that set the oil price is in the Strait of Hormuz. The tariff is in Washington. The monsoon, **14%** below normal, is an El Niño in the Pacific.

A [PESTEL analysis](/frameworks/pestel) scans six external macro forces — Political, Economic, Social, Technological, Environmental, Legal — and asks whether each is favourable or adverse. For India the honest first question is not *favourable or adverse?* but *set where?* This page is the seventh in a country series. The [USA](/examples/usa-pestel-analysis-2026) showed one force holding up the other five; [Canada](/examples/canada-pestel-analysis-2026) one force rewriting them; [France](/examples/france-pestel-analysis-2026) cells splitting by constitutional instrument; [Germany](/examples/germany-pestel-analysis-2026) six cells that were all early; the [European Union](/examples/europe-pestel-analysis-2026) six cells held by different governments; [China](/examples/china-pestel-analysis-2026) six cells that each return two readings. India shows something none of those can: **a country whose domestic cells and imported cells carry opposite signs, and whose government controls only the first set.**

## Position being analyzed

The decision this analysis is built for: **a firm deciding, for 2026-27, whether to expand in India, source from India, or price India as a market — and which of the six cells it should actually be watching.**

That is the live question because the domestic reading and the imported reading have diverged further in the last three weeks than at any point in the series. On 31 August the statistics ministry reported the fastest quarterly growth of any major economy. On 9 September the Indian crude basket touched $115.98. On 15 September the rupee breached 96 intraday. On 18 September the President of the United States signed the Graham Act. A scan that averages those into "India: favourable, some headwinds" has thrown away the only information a decision needs — which of the two is going to move first, and who moves it.

| Indicator | Latest reading | As of |
|---|---|---|
| Real GDP growth, Q1 FY 2026-27 (Apr–Jun) | **7.8%** (nominal 10.3%); RBI had forecast 7.0% | MoSPI, 31 August 2026 |
| Gross fixed capital formation, real / nominal | **+11.9% / +20.4%** | MoSPI, 31 August 2026 |
| Manufacturing / construction / agriculture GVA | **+9.2% / +7.7% / +3.6%** | MoSPI, 31 August 2026 |
| Repo rate | **5.25%**, held 6–0 for a fourth meeting; last cut December 2025 | RBI, 5 August 2026 |
| RBI FY27 forecasts | Growth **6.7%**, inflation **5.0%** | RBI, 5 August 2026 |
| CPI inflation, August 2026 | **4.82%**, highest since Dec 2024; food and beverages 5.95% | MoSPI, September 2026 |
| Fiscal deficit target FY27 / capital expenditure | **4.3% of GDP** (RE FY26 4.4%) / **₹12.22 lakh crore, +11.5%** | Union Budget, 1 February 2026 |
| US reciprocal tariff on Indian goods | **18%** under the 6 February joint statement; Russian-oil tariff eliminated from 7 February | White House; Morgan Lewis |
| Graham Act | Signed **18 September 2026**; up to **100%** on top-5 Russian-energy buyers; 180-day reviews; **5 years** | Business Today / GTRI, 19 September 2026 |
| Russian crude share of India's imports | **50.83%** in July 2026, a record; ~30.3% across FY26 | Tech Times, 20 September 2026 |
| Indian crude basket | **$115.98** on 9 September; September average $104.09 vs $90.19 in August | Business Today, 10 September 2026 |
| Rupee | **~95.96 per dollar**, record low, breached 96 intraday | Business Standard, 15 September 2026 |
| FPI equity outflows, 2026 to date | **₹2.45 trillion**, vs ₹1.66 trillion in all of 2025 | Business Standard, 20 September 2026 |
| Southwest monsoon, 1 June–7 September | **14% below normal**; southern peninsula −27% | IMD via Business Standard, 8 September 2026 |
| Youth (15–29) unemployment, Q1 FY27 | **15.9%**, from 15.0% and 14.6% a year earlier | PLFS via The Policy Edge |

## Political — a government that won its elections and a tariff it cannot vote on

The domestic reading is the most stable in the series. The May 2026 state elections, counted on **4 May**, returned the ruling party stronger than it went in: the BJP won **202 of 294** seats in West Bengal, a state it had never governed, and **82 of 126** in Assam for a third term; Kerala changed hands from the Left to the Congress-led UDF; Tamil Nadu elected the actor Vijay's two-year-old TVK with **109 of 234** seats, an upset that displaced both Dravidian parties. For a firm scanning the Political cell that is an unusually clear signal — a central government with no electoral reckoning until 2029, a widened footprint in the states, and a budget already passed for the year.

The imported reading is the opposite, and it arrived in two acts. The first was the trade deal. The **6 February** joint statement set a US reciprocal tariff of **18%** on Indian goods and recorded India's intention to purchase **$500 billion** of US energy, aircraft, precious metals, technology and coking coal over five years; the White House's own account of the deal, in Morgan Lewis's summary, "includes India's commitment to stop purchasing Russian oil," and the separate 25% tariff imposed over Russian oil was eliminated from **7 February**. Indian officials, the same summary notes, avoided confirming the Russian-oil element. The Commerce Minister said on **15 September** that the first phase of the agreement was "about 99 percent" done.

The second act was the Graham Act. Passed by the House **262–159** on 16 September and signed on **18 September**, it authorises the president to impose tariffs of up to **100%** on imports from the five largest buyers of Russian crude and gas, with the USTR to name the countries within 30 days, a normal 180-day window for purchasers to reduce buying, reassessment every 180 days, and a five-year life. India is the largest of the five. Its Ministry of External Affairs replied within a day that it remains committed to "ensuring energy security for its 1.4 billion people"; the Global Trade Research Initiative advised New Delhi not to "sacrifice its energy security or make permanent trade concessions in exchange for temporary tariff relief." Neither the rate nor the product coverage had been announced as of 20 September.

**Score: favourable on the domestic reading — a government with mandate, majority and a passed budget; adverse and unresolved on the imported reading, because the number that matters is a percentage the USTR has thirty days to propose.**

## Economic — the fastest large economy, priced in a currency it does not set

The domestic release of 31 August is the strongest in the series. Real GDP grew **7.8%** in the first quarter of 2026-27, against **6.9%** a year earlier and the RBI's **7.0%** forecast; nominal growth was 10.3%. The composition is what a growth economist would order: real gross fixed capital formation up **11.9%** (20.4% nominal), private consumption up **7.1%**, manufacturing GVA up **9.2%**, construction **7.7%**, financial, real-estate and professional services in double digits, agriculture a modest **3.6%**. The Union Budget of 1 February backs it with **₹12.22 lakh crore** of capital expenditure, up 11.5%, inside a deficit path of **4.3%** of GDP — a full percentage point of consolidation over two years without cutting capex. The RBI, which cut to **5.25%** in December 2025, has been able to hold there through four meetings, describing itself on 5 August as "neither dovish nor hawkish," and raised its full-year growth forecast to **6.7%**.

The imported release is the same month's other headlines. The US-Iran war that began on **28 February** and the IRGC's closure of the Strait of Hormuz on **27 March** to vessels serving the US, Israel and their allies lifted the Indian crude basket from $90.19 in August to a September average of **$104.09** and a peak of **$115.98** on 9 September; India imports roughly **88%** of its crude, half of it from the Middle East. The rupee, which had already passed 92 in March as foreign investors pulled about $8 billion from equities in that month alone, reached a record **95.96** on 15 September and breached **96** intraday; FPIs have withdrawn **₹2.45 trillion** from Indian equities in 2026 so far, more than the ₹1.66 trillion of the whole of 2025. Consumer inflation, at **4.82%** in August, is up from 4.45% in July and at its highest since December 2024 — inside the RBI's 2–6% band, but moving the wrong way for a central bank that had planned to be finished. HSBC now puts 2026 Brent at **$90** on average, Goldman **$85** for December with **$120** if shipping attacks intensify.

Notice which of the two readings the RBI can act on. It can hold rates against domestic overheating; it cannot cut the price of a barrel in the Gulf of Oman. Its intervention in the rupee — nearly daily in spot and forward markets, with net forward dollar sales that approached **$100 billion** in the spring — is described by traders as managing volatility rather than defending a line, which is the honest description of a central bank whose problem is imported.

**Score: strongly favourable on the domestic reading — 7.8% with investment leading; adverse on the imported reading, and the adverse one is the one that moves week to week.**

## Social — a census counting 1.4 billion people, and a labour market that is not absorbing the young ones

Two domestic facts define the cell, and they pull in different directions. The first is the **Census 2027**, India's first fully digital enumeration and the first to count caste since 1931. Phase one, the houselisting, runs from **1 April to 30 September 2026** and had been completed in 23 states and union territories by mid-June; phase two, the population count, is scheduled for **February 2027**. For any firm that sells, hires or lends by geography, the next eighteen months will replace demographic estimates that are fifteen years old with measured data, and the caste count in particular will reshape reservation, welfare targeting and, in time, the delimitation of parliamentary seats.

The second fact is the labour market the census will describe. Youth unemployment in the 15–29 bracket rose to **15.9%** in April-June 2026, from 15.0% in the preceding quarter and 14.6% a year earlier, with the female youth rate around **20.7%** against roughly 14.6% for men. A 7.8% economy with rising youth unemployment is not a contradiction; it is the composition of the 31 August release — investment- and services-led growth in an economy whose largest employer, agriculture, grew 3.6% and whose harvest is in trouble. The 2026 monsoon has been **14%** below normal to 7 September and **27%** below in the southern peninsula, and kharif sowing was trailing the previous year by **3.88 million hectares** in late July.

The cell has an imported reading too, and it is the price of food: the food-and-beverage component of August CPI ran at **5.95%**, above the headline, with a deficient monsoon still to show up in the autumn harvest.

**Score: mixed — a once-in-a-generation improvement in the data any firm will plan on, set against a youth labour market that the growth number is not reaching.**

## Technological — where the domestic cell wins outright

The Technological cell is the one where the domestic reading and the imported reading finally agree, because the government has spent several years importing the capability rather than the product. The **Tata–PSMC fab at Dholera**, a ₹91,000 crore, 28-nanometre, 50,000-wafers-a-month facility, is due to produce India's first domestically fabricated chip by **December 2026**; Micron's assembly-and-test plant in Sanand is the front end of the same policy. The financial, real-estate, IT and professional services group was the fastest-growing part of the economy in the June quarter at around **12%**, and the GDP release's own methodology note records the statistics ministry moving to double deflation for manufacturing — a technical change, but one that makes the manufacturing number more credible to the foreign investors currently leaving.

The imported reading is that the fab's equipment, its process and its partner are Taiwanese, and that the first chip is a milestone, not a supply chain. It remains favourable because, unlike the oil price, it is a dependency India has chosen and is paying down on a published schedule.

**Score: favourable on both readings — the one cell where the government's plan and the outside world's calendar point the same way.**

## Environmental — an El Niño the government can forecast and cannot change

This is the purest imported cell in the scan. The India Meteorological Department forecast below-normal rainfall for August and for the second half of the season on the strength of a strengthening El Niño, and the outturn has matched: **14%** below normal cumulatively to 7 September, **27%** below across the southern peninsula, individual districts in Haryana at deficits of **53–59%**. The USDA's August assessment found that the July recovery in rainfall had failed to lift planting, with total kharif acreage **3.88 million hectares** behind the previous year. None of this is a policy; all of it is a price — for food, for rural demand, for the reservoir levels that feed the rabi season and for the hydro and thermal balance of the grid in a year when the alternative fuel costs $104 a barrel.

The domestic reading is that India has become better at *reading* the cell — the IMD's below-normal call was made in advance and was right — without acquiring any ability to move it. That is the definition of an imported cell.

**Score: adverse, and entirely outside the government's control; the one lever it holds is the response, not the rain.**

## Legal — three regimes in force at home, one treaty and one statute waiting abroad

The domestic Legal cell is the busiest in the series and, unusually, on schedule. The four labour codes — wages, industrial relations, social security, and occupational safety — took effect on **21 November 2025**, and the central rules under all four were notified on **8 May 2026**; the remaining work is at state level, where each state must notify its own inspection procedures, registers and forms, so a multi-state employer is complying with one law and several rulebooks. The Digital Personal Data Protection Rules, notified in November 2025, are in a "build and test" year that ends in **November 2026**, when the Data Protection Board is expected to move from soft enforcement to supervision. Both are the kind of change a foreign firm's legal team can plan against: dated, published, and enforced by a regulator whose name is known.

The imported reading has two entries and neither has a date. The **EU–India trade agreement**, concluded at Hyderabad House on **27 January 2026** and the largest either side has ever negotiated, went to the Council for signature in September; legal scrubbing, member-state approval and Indian parliamentary ratification put entry into force at **2027–28**. And the Graham Act, already scored under Political, is also a Legal reading — a statute with a five-year life, a 180-day review clock and an unannounced rate, whose every trigger sits with the USTR.

**Score: favourable on the domestic reading — three regimes in force, all dated; unresolved on the imported reading, because the two instruments that will most change India's trade law in 2027 are being drafted in Brussels and Washington.**

## PESTEL scorecard for India, September 2026

| Force | Domestic reading | Imported reading | Set where | The single fact that sets it |
|---|---|---|---|---|
| **Political** | Favourable | Adverse, unresolved | Washington | Graham Act signed 18 Sept; USTR has 30 days to propose a rate up to 100% |
| **Economic** | Strongly favourable | Adverse | Strait of Hormuz | GDP +7.8% vs crude basket $115.98 (9 Sept) and rupee 96 (15 Sept) |
| **Social** | Mixed | Adverse | Pacific / Gulf | Youth unemployment 15.9%; food inflation 5.95% with a 14% monsoon deficit |
| **Technological** | Favourable | Favourable | Dholera / Hsinchu | First Tata–PSMC chip due December 2026 |
| **Environmental** | — | Adverse | Pacific | El Niño; monsoon −14% to 7 Sept, −27% in the south |
| **Legal** | Favourable | Unresolved | Brussels / Washington | Labour-code rules 8 May; DPDP soft phase ends Nov; EU FTA to Council in Sept |

Read the domestic column alone and India in 2026 is the strongest country in this series: fast, investing, consolidating, legislating on schedule. Read the imported column alone and it is a net oil importer in a Hormuz war, with a record-low currency, a tariff sword with a thirty-day fuse and a failed monsoon. Both columns are true and current. What they are not is *averageable* — and the reason is in the third column.

## The Imported-Cell Test

Country scans assume the government being scanned is the author of every cell. India is the case that shows how much of a scan can be written elsewhere, and it suggests a tagging step the standard method skips:

> **The Imported-Cell Test — for each PESTEL cell, write the reading and then ask one question: can the government being scanned move this number? If yes, the cell is domestic; score it on the government's plan and its record of delivery. If no, the cell is imported; write down *who can* move it and *when their next decision falls*, and score it on that actor's calendar, not this government's. Never average a domestic reading with an imported one. A country whose imported cells are adverse is not a badly run country; it is a country whose risk is denominated in someone else's decisions, and the scan should say whose.**

The test is countable because every imported reading in this scan has a named author and a dated next move:

| Cell | Imported reading | Who can move it | Next dated move |
|---|---|---|---|
| Political / Legal | Up to 100% tariff on Russian-energy buyers | USTR under the Graham Act | Country list and proposed rates within **30 days of 18 Sept**; 180-day reduction window; review every 180 days |
| Economic — oil | Crude basket $115.98 peak, $104 average | The US-Iran war; Hormuz traffic | Ceasefire collapsed **8 July**; mines cleared **25 Aug**; no settlement dated |
| Economic — currency | Rupee ~96, FPI −₹2.45tn YTD | US rates and yields; oil | Fed calendar; oil |
| Economic — trade | 18% reciprocal rate; phase one "99%" done | US Trade Representative | Signature of phase one, undated |
| Environmental / Social | Monsoon −14%; kharif −3.88m ha | El Niño | Rabi sowing October–November; reservoir levels |
| Legal | EU–India FTA | Council of the EU; Indian Parliament | Council signature decision, autumn 2026; entry into force 2027–28 |

Six imported readings, six named authors, and not one of them is in New Delhi. Set against that, the domestic readings — the budget, the rate, the codes, the census, the fab — have one author and every one of them has been delivered on or near its stated date. That asymmetry is the finding. It also explains why India's own scan for the same year would look nothing like this one: New Delhi is scoring the cells it holds, and holding them well.

### The contradiction the test makes visible

The sharpest illustration is that two of India's imported cells are fighting each other. The **Political** cell, set in Washington, wants India off Russian oil — that was the price of the 25% tariff's removal on 7 February and it is the whole purpose of the Graham Act. The **Economic** cell, set in the Strait of Hormuz, has made Russian oil the largest supply India can reach without a mine-swept shipping lane: the Russian share of imports rose from about 30% across the last financial year to a record **50.83%** in July, even as the Russian discount narrowed from **$77** a tonne in April to **$10.60** in June — India paid nearly full price for the barrels, because the alternative was no barrels. The government is not defying its trade partner; it is complying with the more urgent of two foreign decisions. A scan that scores India's Russian-oil purchases as a *domestic* political choice — the reading most Western coverage adopts — has mis-tagged the cell and will predict the wrong response to the Graham Act. India will diversify at the speed Hormuz allows, not at the speed the USTR's 180-day clock demands; the Oil Minister's list of alternatives (Guyana, Brazil, Canada, Suriname, Namibia) is a list of longer voyages, not of cheaper oil.

## Counter-argument: doesn't every open economy have imported cells?

Yes, and the test is not that India has them. It is that India's are the ones most likely to move the year, while its domestic cells are the ones most likely to hold — and the standard scan cannot represent that, because it produces one score per cell. Germany's scan in this series had six domestic cells that were all *early*; the European Union's had cells held by different governments *inside the union*; the United States' had one domestic force holding up five. None had three adverse cells authored by governments and weather systems the scanned government does not sit in. Compare Canada, whose imported cell — US trade policy — was so dominant that the [Reversal Test](/examples/canada-pestel-analysis-2026) had to count how many of Ottawa's own policies it had forced into withdrawal. India's government has withdrawn nothing. It has delivered everything on its list, and its year will still be decided by a barrel, a tariff and a rain gauge.

The honest limit of the test is timing. An imported cell can turn favourable as fast as it turned adverse — the crude basket fell from $115.98 to about $104 within ten days, and a durable Hormuz settlement would take the oil, the rupee, the inflation print and the Graham Act's urgency down together. The test does not predict that; it tells you whose calendar to watch for it.

## Key takeaway

India in September 2026 scores as the strongest domestic environment in this country series — 7.8% growth with investment leading, a consolidating budget that still raises capex, a central bank on hold, labour and data regimes in force, a census under way and a fab a quarter from first silicon — attached to three imported readings that are all adverse and all set elsewhere: a Hormuz-priced barrel, a Washington-drafted tariff with a thirty-day fuse, and a Pacific El Niño.

**Decisions that depend on India's domestic execution — hiring, building, selling to a growing middle — should be made on the domestic column, and the risk to them is small and dated.** Decisions that depend on India's external price — the rupee, the fuel bill, the tariff on what leaves the country — should be made on the imported column, and the risk is large, undated, and not New Delhi's to resolve.

The two readings that will most cheaply update this analysis are the USTR's country list and proposed rates under the Graham Act, due within thirty days of 18 September, and the October rabi-sowing data, which will show whether a 14% monsoon deficit became a harvest deficit.

> Want to run a PESTEL on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a PESTEL worksheet with all six forces and AI assistance for the scan.

## Want to go deeper

- [PESTEL framework](/frameworks/pestel) — the six forces, and how to score them
- [How to do a PESTEL analysis](/academy/how-to-do-a-pestel-analysis) — the step-by-step method
- [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) — one force holding up the other five, and the Load-Bearing Force Test
- [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) — one force rewriting the other five, and the Reversal Test
- [PESTEL analysis of France (2026)](/examples/france-pestel-analysis-2026) — cells splitting by constitutional instrument, and the Ballast Test
- [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026) — six cells that are all early, and the Disbursement Gap
- [PESTEL analysis of the European Union (2026)](/examples/europe-pestel-analysis-2026) — six cells governed by different governments, and the Competence Test
- [PESTEL analysis of China (2026)](/examples/china-pestel-analysis-2026) — six cells that each return two readings, and the Two-Ledger Test
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) — when the macro scan is the wrong tool

*Cover photo: [Vikram on Unsplash](https://unsplash.com/photos/B_ufwLFEZPE).*

---

### PESTEL Analysis of Japan (2026): pricing the end of zero
URL: https://frameworklist.com/examples/japan-pestel-analysis-2026
> A PESTEL analysis of Japan in 2026: a 316-seat LDP, the BOJ at 1.25%, 10-year JGBs at 3.055%, and the Repricing Test for the cells that flip as rates rise.

![Tokyo Tower lit at dusk above the Minato skyline](https://images.unsplash.com/photo-1513407030348-c983a97b98d8?auto=format&fit=crop&w=1600&q=80)

On 18 September 2026 the Bank of Japan raised its policy rate to **1.25%**, the highest since 1995, and the yen fell. Six days later the 10-year government bond yield reached **3.055%**, its highest since September 1996. Three weeks before that, the Finance Ministry had published its FY2027 budget requests. They assume a **3.8%** long-term interest rate and put debt service at a record **¥36.64 trillion**.

Japan has never needed a PESTEL analysis that treats the price of money as a variable, and this year it does. For thirty years the country's policies were designed in a world where the government, companies and households could borrow at close to zero. In 2026 most of the headline cells look stronger than they have in a decade: a supermajority government, three years of 5% pay rises, the world's largest nuclear plant back online. The question for each of those cells is whether the score still holds once borrowing costs what the government's own budget now assumes.

## Position being analyzed

The decision this analysis is built for: **a company deciding in late 2026 whether to commit capital in Japan that will be financed, priced or sold in yen for five years or more.** That covers a plant, a hiring plan, a joint venture, or a consumer business that depends on Japanese household spending.

| Indicator | Latest reading | As of |
|---|---|---|
| BOJ policy rate | **1.25%** (from 1.0%; vote 7-2) | BOJ, 18 September 2026 |
| 10-year JGB yield | **3.055%**, highest since September 1996 | 24 September 2026 |
| FY2027 assumed long-term rate in budget requests | **3.8%** (FY2026: 3.0%) | Finance Ministry, August 2026 |
| FY2027 budget requests / debt service | **¥143.07tn / ¥36.64tn**, both records | Finance Ministry, 4 September 2026 |
| Core CPI excluding fresh food, August | **+1.7%** y/y | Statistics Bureau, 17 September 2026 |
| GDP, Q2 2026 (revised) | **+0.4%** q/q, **+1.4%** annualised; consumption flat, capex −0.9% | Cabinet Office, 8 September 2026 |
| 2026 shunto pay rise | **5.01%** (4.69% at unions under 300 members) | Rengo final tally, 3 July 2026 |
| Japanese population, 1 Jan 2026 | **119,736,483**, below 120 million for the first time in 42 years | Internal Affairs Ministry, 29 July 2026 |
| Lower-house seats, LDP | **316 of 465** (two-thirds is 310) | General election, 8 February 2026 |

## Political — a supermajority with a bond market attached

The February snap election gave the LDP **316** seats, the most any single party has won since the war and more than the two-thirds needed to override the upper house. Prime Minister Sanae Takaichi governs with Nippon Ishin no Kai as junior partner and opened the autumn Diet session on **5 October** with a speech promising "responsible, proactive fiscal policy", including long-term investment in priority economic-security areas managed through separate special accounts.

The constraint on this government is not the opposition. It is the budget arithmetic: the FY2027 requests total **¥143.07 trillion**, and **¥36.64 trillion** of that, about **25.6%**, is debt service. That is **4.1 times** the Defence Ministry's record **¥8.84 trillion** request.

Abroad, the dispute with China that began with Takaichi's **7 November 2025** remarks on Taiwan has not been resolved. Beijing issued a travel advisory a week later, stopped seafood imports, and in 2026 restricted exports of dual-use items and rare earths to Japan. On 5 October Takaichi called China an "important neighbor" and pledged stable relations without withdrawing the remarks.

**Score: favourable on domestic stability. The mandate is strong, but debt service limits how much of it can be spent.**

## Economic — the rate went up, the yen went down

The BOJ has now raised rates six times since leaving negative rates in March 2024, and the September move was the shortest gap between hikes in that cycle. Two of the nine board members voted against it. The yen, which had fallen to nearly **164** per dollar in July, weakened again after the decision instead of strengthening. US rates were rising too, so the gap between US and Japanese rates did not narrow.

The real economy is weak enough that the hike is not about overheating:

| Q2 2026 (revised) | Change |
|---|---|
| GDP, quarter on quarter | **+0.4%** |
| GDP, annualised | **+1.4%** (first estimate +1.1%) |
| Private consumption | **flat** |
| Business investment | **−0.9%** |
| Net exports, contribution | **+0.5 points** |

Core inflation was **1.7%** in August, below target, so the real policy rate is still slightly negative (1.25% − 1.7% ≈ **−0.45 points**). The bond market is the outlier: a **3.055%** 10-year yield is **1.8 points** above the policy rate. Daiichi Life Research expects the BOJ to keep hiking toward **2.0%** by June 2027 and core inflation to exceed **3%** around the turn of the year as the weaker yen feeds into import prices.

**Score: adverse for anyone borrowing long in yen, mixed for exporters.** The weak yen still helps exporters, but they no longer get cheap money as well.

## Social — record low births, record high wage settlements

Japanese-national births fell to **671,236** in 2025, the lowest since records began in 1899, with a total fertility rate of **1.14**. The Japanese population fell **916,744** in a year to **119.7 million**. Foreign residents reached a record **4,031,159**, up **9.62%**, as employers recruit abroad to fill vacancies.

The labour shortage shows up in pay. Rengo's final 2026 tally was **5.01%**, the third year in a row above 5%, and **4.69%** at smaller unions. For an employer this is the cell with the clearest direction: labour is scarce and getting more expensive every year.

The rate rise also divides households by age. Nippon.com, using Mizuho estimates, put the September hike's effect at **+¥23,000** a year in mortgage interest for borrowers in their 30s and **+¥21,000** a year in interest income for households aged 70 and over. Mizuho expects a net gain of about **¥400 billion** nationwide, which is small compared with how differently it lands on each age group.

**Score: adverse for labour cost, and divided for consumer demand.** Older households with savings gain, younger households with mortgages pay more, and a consumer business needs to know which of the two it sells to.

## Technological — state-financed chips

The flagship is Rapidus, the state-backed attempt to mass-produce **2-nanometer** logic chips in Chitose, Hokkaido, by 2027. In February it closed a **¥267.6 billion** round, **¥100 billion** from the government's IPA and **¥167.6 billion** from 32 private companies. The government injected another **¥150 billion** on 5 June. The FY2027 requests add an uncapped special investment category worth about **¥12 trillion** for strategic sectors - the budget-side counterpart of the investment framework in her October speech.

**Score: favourable for suppliers to subsidised sectors, but the subsidies are financed by borrowing.** In 2023 a yen of subsidy funded by a JGB cost almost nothing to carry. In 2026 it carries the rate in the table above.

## Environmental — the restart is cheap, the new build is not

Tepco restarted **Kashiwazaki-Kariwa Unit 6**, at **1,356 MW** part of the world's largest nuclear plant, on **21 January 2026**. The US Energy Information Administration estimates the unit can displace about **1.3 million tonnes** of LNG imports a year, which matters more when a weak yen makes every imported tonne dearer. The Seventh Strategic Energy Plan (February 2025) targets **40-50%** renewables, about **20%** nuclear and **30-40%** thermal power by FY2040, and a **73%** cut in greenhouse-gas emissions from FY2013 levels.

The two halves of that plan respond differently to rates. A restart uses a reactor whose capital was spent decades ago, so higher rates barely affect it and a weak yen makes it more valuable. Offshore wind, new transmission and new reactors are mostly upfront capital, and their cost per kilowatt-hour moves with the cost of financing.

**Score: favourable for restarts and for anything that saves imported fuel; harder for the new capacity the 2040 target depends on.**

## Legal — a tax cut, a cyber law and a tariff cap

| Change | Status | What it does | Exposed to the price of money? |
|---|---|---|---|
| **Food consumption tax cut** | Cabinet-approved 5 August 2026; bill in the autumn Diet | 8% → 1% on food for two years from April 2027; revenue gap about **¥10tn** | **Yes**, it is deficit-financed until 2029 |
| **Active Cyber Defense law** | In force from **1 October 2026** | Police and SDF may access and disable attacking servers; tighter cooperation with ~250 critical-infrastructure operators in 15 sectors | No |
| **US-Japan trade agreement** | In force since 2025 | US tariffs on Japanese goods capped at **15%** in exchange for a **$550bn** investment envelope selected by Washington | No |
| **China export controls** | 2026 | Restrictions on dual-use items and rare earths exported to Japan | No |

**Score: neutral to favourable.** Only one of the four rows depends on interest rates, and it is the largest one.

## PESTEL scorecard for Japan, September 2026

| Force | Score | The fact that sets it |
|---|---|---|
| **Political** | Favourable, with less fiscal room than the seat count suggests | 316 seats; debt service 25.6% of requests |
| **Economic** | Adverse for yen borrowers, mixed for exporters | BOJ 1.25%, 10-year 3.055%, yen weaker after the hike |
| **Social** | Adverse on labour cost; divided on demand | Births 671,236; shunto 5.01%; hike gains for over-70s, costs for 30s |
| **Technological** | Favourable for subsidised sectors | Rapidus ¥150bn; ¥12tn special category |
| **Environmental** | Favourable for restarts, harder for new build | KK-6 back online; 40-50% renewables by FY2040 |
| **Legal** | Neutral to favourable | Food tax cut; cyber law; 15% tariff cap |

## The Repricing Test

Look at the right-hand column of the Legal table and the scorecard has a pattern. The cells that have improved most since 2023 are the ones that rely on someone borrowing cheaply: the government (tax cut, subsidies, strategic investment), households (mortgages) and energy developers (new capacity). The cells that do not rely on cheap borrowing (the cyber law, the tariff cap, the China dispute, the labour shortage) score the same whatever rates do.

> **The Repricing Test: for each cell, write two scores. Score it once at the cost of money the policy was designed for, and once at the government's own current planning rate. Act on the cells whose score flips. Score the rest normally.**

Use the government's planning rate, not the market spot rate and not your own forecast. It is published, it is what the budget is built on, and the people running the policy chose it themselves. For Japan's FY2027 budget that rate is **3.8%**, built by adding a margin of about 1.1 points to market rates.

| Cell | Designed-for cost of money | Score then | Score at the 3.8% planning rate | Flips? |
|---|---|---|---|---|
| Political: fiscal expansion under a supermajority | ~0% JGB yields (2016-2022) | Favourable: no budget limit | Constrained: ¥36.64tn interest, 25.6% of requests | **Yes** |
| Legal: food tax cut, ¥10tn over two years | Deficit financing assumed cheap | Favourable for consumer demand | Illustrative carry: ¥10tn × 3.8% ≈ **¥380bn a year** while the debt is outstanding | **Partly** |
| Technological: Rapidus and the ¥12tn special category | Subsidies funded at near-zero cost | Favourable | Still favourable for recipients, costlier for the state | **Partly** |
| Social: household balance sheets | Savers earned nothing, borrowers paid nothing | Neutral across ages | Split: over-70s +¥21,000, 30s −¥23,000 a year | **Yes**, it becomes an age question |
| Environmental: new renewable and grid build-out | Cheap project finance | Favourable | Harder: cost moves with financing | **Yes** |
| Environmental: reactor restarts | Capital already sunk | Favourable | More favourable with a weaker yen | No, it improves |
| Legal: cyber law, tariff cap, China controls | Independent of rates | As scored | As scored | No |

Read the "Flips?" column and the 2026 analysis changes. Japan's strongest-looking cells are the ones most exposed to rates. Its least-changed cells (security law, trade rules, the labour shortage) are the ones a business can plan around regardless of what the BOJ and the bond market do next.

The test is related to two earlier ones in this series. The [Entrant Test](/examples/mexico-pestel-analysis-2026) for Mexico and the before-and-after-the-election scorecard for [Argentina](/examples/argentina-pestel-analysis-2026) also score each cell twice. The difference is what changes between the two scores. In Mexico it is who you are (already there, or arriving). In Argentina it is the date (before or after a change of government). In Japan nobody changes and no election is due. **The input that changed is the price of money,** and it changed for every cell at once.

### How to use the test on your own decision

1. **List the three cells your payback depends on.** For a manufacturer: labour cost, energy cost, the yen. For a consumer brand: real wages, the food tax cut, mortgage costs.
2. **Find what each cell assumes about borrowing.** A tax cut paid for by deficits, a subsidy, a mortgage-financed housing market and a project-financed wind farm all assume cheap borrowing. A tariff cap does not.
3. **Re-score the borrowing-dependent cells at the government's own planning rate.** For Japan in 2026, that is 3.8%.
4. **Size the commitment to the re-scored version.** If the plan only works at the rates that existed before 2024, it relies on conditions the Finance Ministry has stopped assuming.

### One prediction, written down before the data

| | |
|---|---|
| **Placement** | Japan, late 2026: the government is acting as though its budget is unconstrained, and its own interest-rate assumption says it is not |
| **Prediction** | Debt service takes a **larger** share of the FY2028 budget requests than the **25.6%** it takes in FY2027, and the food tax cut still starts in April 2027 as approved |
| **Falsifier** | Debt service's share of the FY2028 requests falls below 25.6% (rates eased or the planning rate was cut), or the food tax cut is delayed or scaled back before April 2027 (the bond market forced a retreat) |
| **Scored on** | The Finance Ministry's FY2028 budget-request totals (published around early September 2027) and the consumption-tax rate on food in April 2027 |

## Counter-argument: Japan has had high debt for decades

The strongest objection is that predictions of a Japanese debt crisis have been wrong for thirty years. Japan's public debt is about **207%** of GDP according to the IMF. Most of it is held at home, much of it by the BOJ, and the average interest rate on the outstanding stock rises slowly because old bonds mature over many years. A 3% 10-year yield changes only the bonds issued from now on.

All of that is correct, and the test does not predict a crisis. It does not say Japan cannot pay. It says the government's own budget now assumes 3.8%, so a plan that only works at 0% is inconsistent with the government's own planning. The slow rise in average cost is the reason to start now: debt service at ¥36.64 trillion is already a record before most of the stock has been refinanced at the new rates.

The second objection is that the yen fell after the hike because of US rates, not Japanese fiscal policy. That may be right. The test does not depend on it. The Finance Ministry's 3.8% assumption was set in August, before the hike and before the yield reached 3%.

## Key takeaway

On headline numbers, Japan in September 2026 is in better shape than it has been for years. The government has a supermajority, wages are rising faster than prices, and a nuclear restart is cutting fuel imports. What changed is the cost of borrowing. The BOJ is at 1.25% and rising, the 10-year bond is above 3%, and the government's own budget assumes 3.8%. The cells that improved most since 2023 are the ones that depend most on cheap borrowing.

**If your Japan plan depends on the government spending more, households borrowing more or project finance staying cheap, re-score it at 3.8% before you commit. If it depends on labour scarcity, energy security or trade rules, the 2026 scan holds whatever the rate does.**

The releases that will update this analysis at least cost are the BOJ's 18-19 December meeting (whether the policy rate reaches 1.5%), the autumn Diet's vote on the food tax bill before 12 December, and the Cabinet Office's Q3 GDP estimate in November.

> Want to run a PESTEL on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a PESTEL worksheet with all six forces and AI assistance for the scan.

## Want to go deeper

- [PESTEL framework](/frameworks/pestel): the six forces, and how to score them
- [How to do a PESTEL analysis](/academy/how-to-do-a-pestel-analysis): the step-by-step method, with every country worked example in one place
- [PESTEL analysis of China (2026)](/examples/china-pestel-analysis-2026): the Two-Ledger Test, and the export-control dispute from Beijing's side
- [PESTEL analysis of Argentina (2026)](/examples/argentina-pestel-analysis-2026): the Lock-In Ladder, scoring each reform by the instrument that holds it
- [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026): the Disbursement Gap and the Two-Clock Score, for a government also borrowing to invest
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces): when to scan the macro environment and when to scan one market

*Cover photo: [Louie Martinez on Unsplash](https://unsplash.com/photos/IocJwyqRv3M).*

---

### JTBD analysis: what job is Instagram Stories hired to do?
URL: https://frameworklist.com/examples/jtbd-instagram-stories
> Instagram Stories grew to 500M daily users in three years. JTBD analysis explains why — it wasn't competing with feed posts. It was competing with sleep.

Instagram launched Stories in August 2016 — a near-direct copy of Snapchat's signature feature. Within three years, Stories had ~500M daily users, surpassing Snapchat's entire app. Most product post-mortems credited "execution speed" and "distribution advantage". JTBD analysis suggests something more specific.

## The forward question that didn't work

Pre-launch, Instagram's product team had been wrestling with a long-observed problem: **engagement on the main feed was declining despite user count growing**. Users opened the app, scrolled briefly, and closed. The feature pipeline reflected the obvious question: *how do we get users to post more content to feed?* Filters, editing tools, prompts to post — all incremental, all unsuccessful.

## The JTBD reframe

Looking at the same observation through a jobs lens, the team identified a different question: **what job were users actually using Instagram to do?**

The answer was uncomfortable: by 2016, users were no longer "hiring" Instagram to *share their best moments with friends* — they were hiring it to *fill empty moments and feel connected without obligation*. Specifically:

- 5-minute waits (elevator, line, between meetings)
- Lonely evening hours
- Procrastination breaks
- Pre-sleep wind-down

The job had drifted away from production (posting) toward consumption (scrolling). The team had been optimizing the wrong side.

## What competed for this job

Once the job was named correctly, the competitive set changed:

- **YouTube** (long-form filler)
- **Snapchat** (lightweight, low-effort posting)
- **Reddit / Twitter** (scrolling feeds)
- **Sleep** — for the bedtime usage moment, sleep is genuinely a competitor

Instagram's feed format was actually a poor fit for the job: feed posts felt high-stakes (they stay forever, get publicly liked or not), so users posted less, so consumers had less to consume, so engagement decayed. A doom loop.

## The Stories design as JTBD answer

Stories addressed each pain point of the job, not the original "share your best moments" pitch:

- **24-hour expiration** removed the long-term-record anxiety → users posted casual content they'd never have posted to feed
- **Full-screen, swipe-through** matched the empty-moment consumption pattern (scrollable, ambient)
- **No public like count** removed the social comparison friction
- **Tap-to-skip** respected the user's attention budget — they could exit any individual story instantly

The result: users posted ~10× more content to Stories than to feed (per Instagram's 2019 data), and consumers had more to consume, which kept the app open longer. The doom loop reversed.

## What this teaches

**Most "engagement problems" are job problems in disguise.** If you're tuning the UX of the wrong job, you can ship beautifully-designed features that don't move metrics.

**The competitive set you assume is usually the one your product *was* designed for, not the one it's currently being hired for.** Instagram's competitive analyses pre-2016 focused on Facebook and Twitter — peer social networks. The actual competition for the user's evening 20 minutes was Snapchat, YouTube, and (genuinely) sleep.

**JTBD reframing doesn't tell you what to build — but it tells you what to stop building.** Once the team accepted the job had shifted, dozens of in-flight features got cancelled because they served the wrong job.

## Run your own JTBD analysis

The full methodology is in the [Academy guide →](/academy/jobs-to-be-done-framework-explained), and [8 more real-company JTBD examples →](/academy/jobs-to-be-done-examples) show the same three-layer analysis on Duolingo, Slack, Uber and others. To structure a JTBD analysis for your own product, [open the canvas →](/sign-in).

> **Want to write job statements on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=jtbd-stories-example) fills in the JTBD template with AI-assisted prompts — situation, motivation, expected outcome. Free to start.

## Related

- [Meta Muse through Jobs-to-be-Done](/blog/meta-muse-jobs-to-be-done) — the same hire/fire lens on Meta's personal AI agent
- [JTBD vs Personas](/compare/jtbd-vs-personas) — why Instagram's persona work missed the job shift entirely
- [JTBD vs user stories](/compare/jtbd-vs-user-stories) — the artifact that captures "stop building this," and the one that can't
- [Jobs-to-be-Done examples](/academy/jobs-to-be-done-examples) — the same three-layer analysis on Duolingo, Slack, and Uber
- [Anthropic's Business Model Canvas](/examples/anthropic-business-model-canvas) — where the job statement lands once it becomes a value proposition
- [The JTBD glossary entry](/glossary/jtbd) — the one-line definition and the misuse to avoid

---

### Manchester City Ansoff Matrix: the multi-club growth bet
URL: https://frameworklist.com/examples/manchester-city-ansoff-matrix-2026
> A worked Ansoff Matrix of Manchester City and City Football Group — how a 13-club, five-continent network is a textbook Market Development engine, read at the 2026 World Cup moment.

This is part of our [World Cup 2026 strategy series](/series/world-cup-2026) — the business of football read through strategy frameworks while the [first 48-team World Cup](/examples/fifa-ansoff-matrix-2026) plays out across the USA, Canada, and Mexico. The tournament is where the players become global stars; the clubs are where the business of football actually compounds. And no club has turned football into a growth *system* more deliberately than Manchester City.

The Ansoff Matrix — two axes, four quadrants, risk rising as you move from selling what you have to who you have toward new products for new markets — is the right lens, because City's real strategy isn't on the pitch. Manchester City is the product; **City Football Group (CFG) is the growth strategy.**

## Position being analyzed

Manchester City is the reigning core of [City Football Group, the world's leading private multi-club owner](https://www.cityfootballgroup.com/clubs) — **13 clubs across five continents, with more than 1 billion followers** connected to the network. The club itself posts [€838m in revenue, the highest of any English club](https://www.deloitte.com/uk/en/about/press-room/deloitte-football-money-league.html) and second globally only to Real Madrid (€1.05bn) in the 2025 Deloitte Football Money League. The strategic question Ansoff helps with: when City spends, is it buying a better team (penetration), or buying access to new markets and new products (development and diversification)? The answer reframes the whole "petro-club just buys trophies" narrative.

## The four quadrants

| Quadrant | Definition | Risk | Manchester City / CFG entries |
|---|---|---|---|
| **Market Penetration** | Existing product, existing market | Low | Winning the Premier League; €838m revenue; Etihad/Puma commercial deals; stadium expansion |
| **Market Development** | Existing product, new market | Medium | The CFG network — Melbourne City, New York City FC, Mumbai City (divested 2025), Montevideo City, Girona, Palermo and more |
| **Product Development** | New product, existing market | Medium-High | Manchester City Women; City+ content; Etihad Campus experience; academy & coaching products |
| **Diversification** | New product, new market | High | Selling CFG's data, sports-science and operations know-how *as a service* to clubs outside the family |

## Market Penetration: win more, sell more

The low-risk quadrant that funds everything else. City's penetration play is the obvious one: keep winning the Premier League so matchday, broadcast, and commercial revenue compound, and keep deepening sponsorship (Etihad, Puma) and stadium capacity. At €838m, City already converts on-pitch dominance into the highest revenue of any English club. None of this requires a new product or a new market — it is selling more of elite men's football to the people and broadcasters already buying it. Ansoff scores it low-risk, and it is the cash base the network is built on.

## Market Development: the real engine

This is where City's strategy actually lives, and where the Ansoff lens is most clarifying. CFG's [13-club network](https://en.wikipedia.org/wiki/City_Football_Group) — Melbourne City (Australia), New York City FC (USA), Montevideo City Torque (Uruguay), Girona (Spain), Palermo (Italy), Lommel (Belgium), and others — is not a collection of trophies. It is the *same product* (an elite football-operations model: data-led recruitment, sports science, a unified playing philosophy, a shared commercial playbook) replicated in *new geographic markets*. Existing product, new market — textbook medium-risk Market Development.

The [December 2025 divestment of Mumbai City](https://en.wikipedia.org/wiki/City_Football_Group), after six years, is the proof the model is run as a portfolio: Market Development means pruning a market that no longer fits, not just adding flags to a map. The network gives City three things a single club can't have — new revenue and fanbases in growth markets, a global player-development and loan pipeline, and a diversified regulatory/competitive footprint.

## Product Development: adjacencies for existing fans

New products sold to the fanbase City already owns. **Manchester City Women**, the **City+** streaming and content product, the **Etihad Campus** matchday-and-tourism experience, and academy/coaching offerings are all new lines aimed largely at the existing Manchester and global City support. New product, existing market — the medium-high-risk quadrant. The risk here is demand depth and execution, not whether the market exists; these fans are already in the building.

## Diversification: know-how as a service

This is the quadrant where the Ansoff lens earns its keep, because it forces an honest call: City's *genuinely* new-product-new-market bet is small. The clearest example is exporting CFG's analytics, sports-science, and club-operations expertise *as a service* to clubs outside the family — a new product (consulting/data, not football matches) sold to a new market (rival or unaffiliated clubs). It is high-risk and unproven at scale, and notably City has kept it modest. The Ansoff read is therefore reassuring on risk: unlike [Tesla](/examples/tesla-ansoff-matrix) or [Nvidia](/examples/nvidia-ansoff-matrix-2026), City is *not* betting its future on the riskiest quadrant.

## The Multi-Club Flywheel

Here is the original synthesis worth keeping. The reason CFG's Market Development scales where most multi-club projects stall is that each new club isn't a standalone bet — it feeds a flywheel that lowers the cost and risk of the *next* market entry.

| Flywheel stage | What it does | Ansoff quadrant it strengthens |
|---|---|---|
| Buy/build a club in a new market | Adds revenue, fanbase, regulatory foothold | Market Development |
| Plug in the shared model | Data, scouting, sports science, playing philosophy — amortised, not rebuilt | Market Development (lowers entry cost) |
| Move players & coaches across the network | Loans, development, value creation across borders | Market Penetration (better core squad) + Development |
| Sell network-wide commercial & content | One sponsor sells across 13 markets; City+ scales | Product Development |
| Package the know-how | Operations/data as a service to outside clubs | Diversification |

The flywheel is why City's diversification risk stays low: it grows mostly by *replicating a proven model in new markets* (medium risk) rather than *inventing new products for new markets* (high risk). The danger the model hides isn't a single bad acquisition — it's **integration**. A 13-club network only beats 13 separate clubs if scouting, players, data, and commercial deals actually flow across borders. When they stop flowing, the network is just a holding company, and the Market Development thesis quietly converts back into 13 unrelated Market Penetration bets.

## Key takeaway

The Ansoff Matrix on Manchester City reveals that the club's growth story is badly misread as "rich owners buying trophies." The trophies are Market Penetration — real, low-risk, cash-generating, but not the strategy. The strategy is **Market Development at industrial scale**: City Football Group takes one elite operating model and replicates it across 13 markets on five continents, with Product Development adjacencies (women's football, content) layered on the home fanbase and only a small, deliberate Diversification toe in the water. Ansoff's contribution is to relocate the question from "did City overpay for a striker?" to "is the network integrating well enough to justify itself?" The Mumbai City exit shows the portfolio is actively managed. The next test is whether the flywheel keeps spinning — or whether 13 clubs slowly drift back into being 13 clubs.

## Want to go deeper

This analysis is part of the [World Cup 2026 strategy series](/series/world-cup-2026). New to the model? Start with [Ansoff Matrix examples: the 4 growth strategies](/academy/ansoff-matrix-examples), read more about the [Ansoff Matrix framework](/frameworks/ansoff), or browse [strategy framework examples applied to real companies](/examples). For the governing body's version of the same portfolio logic, see the [FIFA Ansoff Matrix 2026: the World Cup growth bet](/examples/fifa-ansoff-matrix-2026); for the same series read through an industry-structure lens, see the [Real Madrid Porter's Five Forces: the Super League play](/examples/real-madrid-porters-five-forces-2026). For companies betting far more heavily on the riskiest quadrant, see the [Nvidia](/examples/nvidia-ansoff-matrix-2026) and [Tesla](/examples/tesla-ansoff-matrix) Ansoff analyses. To run an Ansoff analysis on an organisation you're tracking, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each quadrant.

For Manchester City's SWOT counterpart, see our sister site [SWOTPal's Manchester City SWOT analysis](https://swotpal.com/examples/manchester-city-swot-analysis?utm_source=frameworklist&utm_medium=referral&utm_campaign=ansoff-mancity) — a dedicated AI SWOT tool, free for the basic workflow.

---

### PESTEL Analysis of Mexico (2026): record FDI, no new money
URL: https://frameworklist.com/examples/mexico-pestel-analysis-2026
> A PESTEL analysis of Mexico in 2026: USMCA not renewed, a record FDI half that is 88.5% reinvested profit, new investment down 13.4%, and the Entrant Test.

![Modern skyscrapers rising above the green canopy of Chapultepec forest in Mexico City](https://images.unsplash.com/photo-1760076000027-b4391b83850b?auto=format&fit=crop&w=1600&q=80)

Mexico reported its best foreign-investment half-year on record in September 2026: **US$34.97 billion**, up 2.1%. That is the number most PESTEL analyses of Mexico would put in the Economic cell, and on that number the cell scores favourable.

The same release says something else. **88.5%** of that record was profit that companies already operating in Mexico chose to reinvest there. New investment, meaning money from firms putting capital into Mexico for the first time or opening new operations, was **US$2.726 billion**, down **13.4%** from US$3.149 billion a year earlier. Banxico's balance-of-payments measure of net FDI fell **11.7%**. The firms already in Mexico are still committing capital. New arrivals have slowed.

A [PESTEL analysis](/frameworks/pestel) scans six external macro forces: Political, Economic, Social, Technological, Environmental and Legal. It asks whether each one favours the decision in front of you. For Mexico in 2026 the answer depends on whether you already have a plant there, more than on what you do or where you sell. This is the eighth country page in the series. The [USA](/examples/usa-pestel-analysis-2026) had one force holding up the other five, [Canada](/examples/canada-pestel-analysis-2026) one force rewriting them, and [China](/examples/china-pestel-analysis-2026) and [India](/examples/india-pestel-analysis-2026) had cells that split by ledger and by who can move them. Mexico's cells split by **when you committed**.

## Position being analyzed

The decision this analysis is built for: **a manufacturer or investor deciding in late 2026 whether to build new capacity in Mexico now, expand what it already has there, or wait for the 1 July 2027 USMCA review.**

That is the live question because of what happened on 1 July 2026. The three governments met for the agreement's first required joint review, and Mexico and Canada both supported extending it. The United States Trade Representative's statement was two sentences long: *"The United States did not agree to renew the USMCA in its current form. As a result, the USMCA is not renewed."* The agreement did not lapse. It stays in force to **1 July 2036**, with preferential tariffs, rules of origin and dispute settlement unchanged, but it is now reviewed **every year** rather than every six. US-Mexico bilateral rounds have covered auto rules of origin, steel and aluminium, economic security, agriculture, labour, the environment and regulatory compatibility.

| Indicator | Latest reading | As of |
|---|---|---|
| USMCA status | **Not renewed**: in force to 2036, reviewed annually; next review 1 July 2027 | USTR, 1 July 2026 |
| GDP growth, Q1 / Q2 2026 (year on year) | **0.2% / 2.1%**; Q2 **+1.4%** q/q (flash 1.5%), best since Q4 2020 | INEGI, 24 August 2026 |
| Share of Q2 q/q growth from World Cup spending | **~two-thirds** | Banco Base, 30 July 2026 |
| Policy rate | **6.50%**, third straight hold | Banxico, 24 September 2026 |
| Inflation, 1H September (headline / core) | **3.42% / 3.79%** | INEGI via Reuters, 24 September 2026 |
| FDI, H1 2026 | **US$34.97bn, +2.1%**: a record | Economy Ministry, 1 September 2026 |
| …of which reinvested earnings / new investment | **88.5% / 7.8%**; new investment **US$2.726bn, −13.4%** | Economy Ministry |
| Net FDI (balance-of-payments basis), H1 2026 | **US$24.81bn, −11.7%** | Banxico |
| Remittances, H1 2026 / full-year 2025 | **US$30.76bn, +3.1% / US$61.79bn, −4.6%** | Banxico |
| Auto exports to the US, Q1 2026 | **US$38.1bn, −11.3%** | US Commerce data via El Economista |
| Public-sector borrowing requirement, 2026 est. / 2027 budget | **4.1% / 3.9% of GDP**; April had promised 3.5% | Paquete Económico 2027, 8 September 2026 |
| Population / total fertility rate | **130.9m**, growing 0.7% / **1.2** | INEGI Intercensal Survey 2025 |

## Political — an agreement that is now reviewed every year

The domestic political picture is the most stable it has been in years. President Claudia Sheinbaum's coalition passed the 40-hour-week reform unanimously, carried Mexico's own tariff law 281-24, and delivered a 2027 budget on schedule. Whatever else is uncertain about Mexico, nobody is waiting to find out who governs it.

The uncertainty comes from the United States, in four specific ways:

- **USMCA's annual review.** The agreement is unchanged, but every 1 July from now to 2036 is a date on which the United States can ask for more. A plant whose payback period runs four or seven or ten years now runs through that many reviews.
- **Section 232.** The Supreme Court's 20 February 2026 ruling ended the IEEPA tariffs, including the 25% fentanyl tariff on non-compliant Mexican goods. It left Section 232 untouched. Mexican-built vehicles still pay **25% on their non-US content**. Rules of origin for autos are on the agenda of the bilateral rounds.
- **The 1944 Water Treaty.** The 2020-25 delivery cycle closed in October 2025 with Mexico still owing just over **865,000 acre-feet**, almost half its five-year obligation. Under US pressure, Mexico committed in February 2026 to deliver at least **0.35 million acre-feet a year** and to produce a plan for the arrears.
- **Mexico's own China tariffs,** which a Political cell has to count as partly a US event. The tariffs of up to 50% on non-FTA imports that took effect on 1 January 2026 were designed under visible pressure over Chinese goods entering the US through Mexico, and they are the measure Mexico can point to in every review.

**Score: domestically favourable and low-volatility; externally adverse and now volatile on an annual cycle. The external half is what sets the price of new capital.**

## Economic — a strong quarter driven by a one-off

The second quarter was the strongest since 2020: **+1.4%** quarter on quarter and **+2.1%** year on year, after 0.2% in the first quarter. But Banco Base's Gabriela Siller attributed about **two-thirds** of the quarterly growth to World Cup spending (construction in April and May, then retail and services during the tournament) and expected a quarter-on-quarter contraction in Q3. The IMF's forecast for 2026 as a whole is **1.2%**. The [World Cup 2026 PESTEL](/examples/world-cup-2026-pestel-analysis) published in June called Mexico the tournament's relative winner among the three hosts, because a smaller economy turns the same event into a bigger share of GDP. Q2 agrees. The Q3 number will show how much of that was pulled forward rather than added.

Monetary policy is on hold rather than loosening. Banxico kept its rate at **6.50%** on 24 September, unanimously and for the third meeting in a row, and stated that Mexican rates should not mechanically follow the Fed. Headline inflation picked up to **3.42%** in the first half of September, driven by a 22.8% two-week jump in tomato prices. Core inflation eased to **3.79%**, inside Banxico's 3% ± 1 point range.

The fiscal side changed direction on 8 September. The 2027 economic package cuts federal support for Pemex's debt payments to **81.1 billion pesos**, from 263.5 billion this year, a reduction of nearly 70%, on the expectation that Pemex runs a financial surplus of about 95 billion pesos. Yet the broad deficit target came in at **3.9% of GDP**, not the 3.5% promised in April, with debt rising to **55% of GDP** and the 2027 growth assumption cut to 1.5-2.5%.

And then there is investment, which is where the cell splits:

| Investment measure, H1 2026 | Value | Change |
|---|---|---|
| Total FDI (Economy Ministry) | US$34.97bn | **+2.1%**, record |
| Reinvested earnings | ~US$30.9bn (88.5%) | up |
| New investment | US$2.726bn (7.8%) | **−13.4%** |
| Inter-company accounts | 3.7% | — |
| Net FDI (Banxico, balance-of-payments) | US$24.81bn | **−11.7%** |

**Score: favourable for firms already in Mexico, which are reinvesting at record levels. Neutral-to-adverse for new entrants, and the drop in new money is the market's own reading of that.**

## Social — fewer workers coming, and a shorter week by law

INEGI's 2025 Intercensal Survey counted **130.9 million** people, growing at **0.7%** a year, the slowest rate in two decades. It put the total fertility rate at **1.2 children per woman**, down from 1.9 in 2019, and as low as 0.8 in Mexico City. The median age rose from 29 in 2020 to **32**. For a country whose nearshoring pitch rests partly on a young, cheap workforce, this changes the long-run reading: the workforce exists today, but the cohorts entering it after 2040 are being born now, and there are fewer of them.

The second Social shift is legislated. Mexico amended its constitution in March 2026 to reduce the maximum working week from **48 to 40 hours** with no loss of pay, phased in over 2027-2030 (46, 44, 42, then 40 hours). The secondary law took effect on 1 May 2026 and requires electronic time records. For a factory running continuous shifts, that adds up to a 17% cut in hours per worker at the same wage.

Remittances, which support household consumption in large parts of the country, recovered after their first fall in more than a decade. They fell **4.6%** to US$61.79 billion in 2025, then rose **3.1%** to US$30.76 billion in the first half of 2026. That was despite a new **1% US tax** on cash-funded transfers from 1 January. Transfers funded from bank accounts and cards are exempt.

**Score: neutral now, adverse over time. The demographic trend is slow but has already started.**

## Technological — demand for power is outrunning the grid

The technology story in Mexico in 2026 is mostly about data centres, and data centres are mostly about electricity. National operational data-centre capacity went from **115 MW** in 2024 to **235 MW** in 2025 and **279 MW** in 2026, and Querétaro holds about **72%** of it. Hyperscaler commitments continue. The constraint is the grid run by the state utility CFE, which according to September reporting has not expanded fast enough to serve new industrial loads in northern Mexico. Firms describe constraints on grid connection, power quality and clean-energy contracts, and often need private backup generation.

On the policy side, the Kutsari semiconductor-design programme launched under Plan México in February 2025, with hubs in Puebla, Jalisco and Sonora and a target of 3,000 trained engineers by 2030. It is a design programme, not a fab. The Economy Ministry has discussed AI-supercomputer manufacturing with Nvidia, but those talks had not become committed capacity by September.

**Score: favourable for firms already connected to the grid; adverse for a new site that needs megawatts in the next two years.**

## Environmental — water and power in short supply

Two environmental constraints matter to an investor, and both are about supply rather than regulation.

**Water.** The drought behind the 1944 treaty arrears is the same drought that affects industrial water in Mexico's northern manufacturing belt. Mexico ended the last treaty cycle almost 50% short. Its 2026 commitment of at least 0.35 million acre-feet a year to the US comes from the same Rio Grande basin that Chihuahua, Coahuila, Nuevo León and Tamaulipas draw on. Texas Public Radio summarised the situation in February: both sides are running out of water.

**Power.** The grid constraint in the Technological cell is also an environmental one. A plant that cannot get a clean-energy contract and runs on backup generation has a worse emissions profile than one that can. That matters more each year for any supplier inside a US or European customer's Scope 3 reporting.

**Score: adverse, and slowly worsening. The water obligation is now a treaty commitment to a neighbour, not only a domestic policy choice.**

## Legal — three big changes since 2024

Mexico has changed more of its business law in two years than in the previous ten:

| Change | In force | What it does | Who it costs |
|---|---|---|---|
| **Judicial reform** | Enacted 15 Sept 2024; first full year of elected judges 2026 | Federal judges, including the Supreme Court, are elected; a 2026 amendment pushed the next judicial elections to **4 June 2028** and added mandatory professional exams | Firms with contracts already exposed to Mexican courts |
| **40-hour week** | Constitution amended Mar 2026; law in force 1 May 2026; phase-in 2027-2030 | 48 → 40 hours, no pay cut; overtime capped; electronic time records | Employers with existing 48-hour shift patterns |
| **Tariffs on non-FTA imports** | 1 Jan 2026 | **5-50%** on **1,463** tariff lines in 13+ sectors from China, India, South Korea, Thailand, Indonesia and others | Manufacturers with Asian input chains |

Outside Mexico's own statute book, the US Section 232 auto tariff is the legal fact with the biggest effect on volume: Mexico's auto exports to the US fell 11.3% in Q1 2026, and passenger-car exports fell 22%.

Jones Day's advice to foreign investors on the judicial reform is the clearest sign of how the Legal cell splits. Investors should check whether their corporate structure qualifies for protection under an investment treaty, and restructure *"before any alleged breach occurs or becomes foreseeable."* That advice is easy to follow for a firm that has not yet invested and much harder for one that already has.

**Score: adverse for incumbents, who must absorb all three changes. Manageable for entrants, who can design around all three from day one.**

## PESTEL scorecard for Mexico, September 2026

| Force | Incumbent (already operating) | Entrant (deciding whether to come) | The fact that sets it |
|---|---|---|---|
| **Political** | Favourable: USMCA in force, preferences intact | **Adverse**: every year of payback runs through a review | USTR, 1 July 2026: "the USMCA is not renewed" |
| **Economic** | **Favourable**: reinvesting at a record pace | Neutral-to-adverse: new investment −13.4% | FDI H1: 88.5% reinvested earnings |
| **Social** | Neutral, adverse long-run | Neutral, adverse long-run | Fertility 1.2; 40-hour week by 2030 |
| **Technological** | **Favourable**: connected | **Adverse**: queue for megawatts | 279 MW of data centres, 72% in one state |
| **Environmental** | Adverse | Adverse | ~50% short on the last water-treaty cycle |
| **Legal** | **Adverse**: three changes to absorb | Neutral: three changes to design around | Elected judges, 40-hour week, 5-50% Asia tariffs |

Four of the six rows score differently depending on the column, and they do not all point the same way. That is what the next section explains.

## The Entrant Test

Standard PESTEL assumes the reader is a single, timeless decision-maker. Mexico in 2026 shows why that assumption matters: firms that committed before July 2026 and firms deciding after it read the same six forces and reach different answers. The investment data shows them doing so.

> **The Entrant Test: score every PESTEL cell twice, once for a firm already operating in the country (the incumbent) and once for a firm deciding whether to arrive (the entrant). Then sort the cells where the two readings differ by one question: can an entrant design around this cell before it commits? Cells an entrant can design around are a cost of arriving. Cells it cannot design around are a reason to wait, and if the binding one has a scheduled date, waiting until that date is cheap.**

Applied to Mexico:

| Cell | Incumbent | Entrant | Can an entrant design around it? | Set by |
|---|---|---|---|---|
| Legal: judicial reform | Adverse | Neutral | **Yes**: structure through an investment treaty before any dispute is foreseeable | Mexico |
| Legal: 40-hour week | Adverse (re-roster existing shifts) | Neutral (staff for 40 from day one) | **Yes** | Mexico |
| Legal: 5-50% Asia tariffs | Adverse if inputs are Asian | **Favourable**: competitors with Asian inputs pay more | **Yes**: source in North America | Mexico |
| Political: USMCA annual review | Favourable (capital already sunk) | **Adverse** | **No**: depends on Washington, every 1 July | United States |
| Technological: grid connection | Favourable (connected) | **Adverse** | **Only partly**: backup generation at a cost | CFE build-out |

Two findings come out of this table.

**First, the cells that favour entrants are all Mexican; the cells that favour incumbents are American or infrastructural.** Each of Mexico's own reforms can be planned for in a new site: a treaty-protected holding structure, a 40-hour shift design, a North American supply chain. None of them can be planned around once the plant exists. Mexico has spent two years changing exactly the laws an entrant can absorb most easily. The cell no entrant can design around is set in Washington.

**Second, the binding cell has a date.** A firm that waits until 1 July 2027 gives up one year of production and learns something it cannot learn any other way: whether the second annual review produces renewal, new conditions, or another refusal. That is the logic the H1 data shows. Incumbents, whose capital is already committed, reinvested **US$30.9 billion**. Entrants, for whom waiting is cheap, put in **US$2.7 billion**, down 13.4%. On this reading the decline in new investment is a sensible response to how the annual review is scheduled, not a loss of confidence in Mexico.

This differs from the [Two-Ledger Test](/examples/china-pestel-analysis-2026) used for China, which splits the scan by which side of the economy a decision touches (production or household). It also differs from the [Imported-Cell Test](/examples/india-pestel-analysis-2026) used for India, which tags cells by who can move them. The Entrant Test splits by *when you committed*. A cell can be imported and still identical for incumbents and entrants (Mexico's water obligation is), or domestic and still read in opposite directions by the two (the 40-hour week).

### One prediction, written down before the data

The test makes a checkable claim, so it is recorded here with the date it will be scored:

| | |
|---|---|
| **Placement** | Mexico, 2026: favourable to incumbents, adverse to entrants, until a renewal signal from the annual USMCA review |
| **Prediction** | Full-year 2026 *new investment* comes in below full-year 2025's, while reinvested earnings keep total FDI near record levels |
| **Falsifier** | Full-year 2026 new investment at or above the 2025 figure without any renewal signal, which would mean entrants are not treating the review date as a reason to wait |
| **Scored on** | The Economy Ministry's full-year 2026 FDI release (expected February 2027), then the 1 July 2027 review |

## Counter-argument: isn't reinvested earnings always most of Mexico's FDI?

The strongest objection is that reinvested earnings have dominated Mexico's FDI for years, because a large stock of foreign-owned plants generates a large flow of profit. If 88.5% is roughly normal, the composition says nothing about 2026.

The objection is right about the share and wrong about what the test reads. The Entrant Test does not depend on the share. It depends on the **change in new investment**, which fell 13.4% year on year, and on the fact that Banxico's independent net-FDI measure fell 11.7% over the same months. A high reinvestment share would explain a record total. It does not explain new money falling.

The honest limit is the one this site applies to any single-window reading: **one half-year is not a trend.** H1 2026 includes the run-up to the 1 July review, when waiting was obviously sensible. If new investment recovers in the second half without a renewal signal, the test's prediction fails, and the table above says in advance what failure would look like.

## Key takeaway

On headline numbers, Mexico in September 2026 looks like a country that won nearshoring: record FDI, the best quarter since 2020, inflation inside the target band, a budget that finally reduces support for Pemex. The scan changes once you ask who those numbers describe. The record is incumbents reinvesting. New arrivals fell 13.4%. The reason is not anything Mexico changed. It is the one cell no entrant can design around, which has been reviewed annually in Washington since 1 July 2026.

**If you already operate in Mexico, the environment is favourable and the main risk is legal: the 40-hour phase-in from 2027 and the judicial reform apply to you whether you planned for them or not.** If you are deciding whether to come, every Mexican-made change can be designed around, and the US-made one has a date. The decision is less "Mexico or not" than "now or after 1 July 2027." The answer depends on whether a year of lost production costs more than a year of review risk.

The three releases that will update this analysis cheapest are Q3 GDP (late October, which will show how much of Q2 was the World Cup), the full-year 2026 FDI composition (February 2027, which scores the prediction above), and the second annual USMCA review on 1 July 2027.

> Want to run a PESTEL on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a PESTEL worksheet with all six forces and AI assistance for the scan.

## Want to go deeper

- [PESTEL framework](/frameworks/pestel): the six forces, and how to score them
- [How to do a PESTEL analysis](/academy/how-to-do-a-pestel-analysis): the step-by-step method
- [PESTEL analysis of the USA (2026)](/examples/usa-pestel-analysis-2026): the other side of the annual review, and the Load-Bearing Force Test
- [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026): the third USMCA economy, one political force rewriting the other five, and the Reversal Test
- [PESTEL analysis of China (2026)](/examples/china-pestel-analysis-2026): the supplier Mexico's 50% tariffs are aimed at, and the Two-Ledger Test
- [PESTEL analysis of India (2026)](/examples/india-pestel-analysis-2026): also caught by Mexico's non-FTA tariffs, and the Imported-Cell Test
- [World Cup 2026 PESTEL analysis](/examples/world-cup-2026-pestel-analysis): the June scan that called Mexico the tournament's relative winner
- [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026): a different reason to wait for a date, and the Two-Clock Score
- [PESTEL analysis of Argentina (2026)](/examples/argentina-pestel-analysis-2026): Latin America's other reform story, where the risk is a domestic vote, and the Lock-In Ladder
- [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces): when the macro scan is the wrong tool

*Cover photo: [Juan Pablo Lara on Unsplash](https://unsplash.com/photos/99XZLOBKdqU).*

---

### Microsoft Porter's Five Forces Analysis 2026
URL: https://frameworklist.com/examples/microsoft-porters-five-forces-analysis-2026
> A worked Porter's Five Forces analysis of Microsoft's enterprise cloud + AI business in 2026 — Azure vs AWS/GCP rivalry, OpenAI supplier power, Nvidia GPU lock-in, AI-native cloud entrants, and the substitute threat from self-hosted open-source models.

![Photograph of a hyperscale data center server hall](https://images.unsplash.com/photo-1558494949-ef010cbdcc31?auto=format&fit=crop&w=1600&q=80)

Microsoft's enterprise cloud + AI business in 2026 is the cleanest case study for Porter's Five Forces in the current market. Five distinct competitive pressures shape the segment, each with non-trivial weight, and the framework gives you a structured way to score them against each other rather than letting any one of them dominate the narrative. Most commentary focuses on the Azure-AWS rivalry. Five Forces says supplier power is actually the more binding constraint — and the strategic moves of the last 18 months only make sense once you see it that way.

## Position being analyzed

Mid-2026: Azure is the #2 cloud by share but #1 by growth, Microsoft Copilot is approaching 100M paid commercial seats, the extended OpenAI partnership has been amended to clarify model exclusivity carve-outs, Microsoft's in-house MAI model family is in commercial preview, Maia and Cobalt silicon are shipping in Azure datacenters at non-trivial scale (single-digit % of new capacity), and the FTC's Activision review concluded two years ago with a behavioral remedy that left the structure intact. The strategic question Five Forces helps with: which of the five forces is the binding constraint on the 2027–2028 trajectory of the AI-cloud business?

| Metric | Value | Direction vs. 12 months ago |
|---|---|---|
| Azure revenue growth (YoY) | ~+28% | Stable |
| Cloud infrastructure share (Synergy) | AWS 32% / Azure 23% / GCP 12% | Azure +1 pt, AWS -1 pt |
| Microsoft 365 Copilot paid seats | ~100M | Up from ~50M |
| Azure OpenAI service customers | 60,000+ | Up from ~40,000 |
| OpenAI revenue share to Microsoft | 20% (pre-AGI clause) | Unchanged |
| Maia/Cobalt share of new capacity | Single-digit % | Up from negligible |
| FY26 capex | $115B+ | Up from ~$80B |

## Five Forces applied

### Rivalry among existing competitors — high, stable

The cloud infrastructure rivalry is structurally intense but operationally disciplined. AWS, Azure, and GCP are the three primary competitors; Oracle Cloud Infrastructure has carved a meaningful AI-workload niche; Alibaba and Tencent dominate China but are essentially excluded from the Western enterprise market by geopolitical fact. The rivalry produces continuous product investment (every quarter brings new AI services from all three hyperscalers) and aggressive sales motions for enterprise accounts. It does not produce price wars on standard SKUs — the three are too profitable to attack each other on price, and enterprise customers are too sticky for marginal price moves to flip accounts.

The AI-workload rivalry is more interesting. Microsoft has Azure OpenAI Service + Copilot pull-through. AWS has Bedrock + Anthropic. Google has Vertex + native Gemini. Each hyperscaler is differentiating on which frontier-model relationship it can offer enterprise customers. This is rivalry at the *partnership* level, which is unusual for the Five Forces framework but real.

### Bargaining power of buyers — moderate, increasing

Enterprise cloud buyers have more leverage in 2026 than they did in 2022. Multi-cloud has become operationally normal (a typical Fortune 500 runs workloads on at least two hyperscalers), FinOps practices have matured, and AI workload portability tools (LangChain abstractions, model gateway services, agnostic prompt frameworks) make switching costs lower at the AI-services layer than at the infrastructure layer. The Reserved Instance / Savings Plan / Enterprise Agreement structures all impose switching costs but don't eliminate them.

The largest buyers (hyperscaler AI labs themselves, banks, government) negotiate bespoke discount tiers that aren't reflected in published pricing. The medium-sized enterprise segment — where Microsoft is strongest — has less negotiating leverage and is the segment where Copilot economics are most favorable.

### Bargaining power of suppliers — high, concentrated, the binding constraint

This is the force most under-discussed in standard analyst coverage and the one Five Forces correctly elevates. Two suppliers dominate Microsoft's AI input stack:

**OpenAI** is the supplier of frontier models that power Azure OpenAI Service and Copilot. The 2023 partnership extension granted Microsoft a defined revenue share (20% pre-AGI), defined exclusivity on certain commercial deployment paths, and a board observer seat. But the model roadmap belongs to OpenAI. The 2025 amendments carved out exceptions for OpenAI to deploy through other partners. Microsoft's response — building the MAI in-house model family — is precisely the strategic move Five Forces predicts when supplier concentration becomes operational risk.

**Nvidia** is the supplier of frontier GPU silicon (H100, B100, B200, soon Rubin) that limits Azure's AI capacity expansion. Microsoft commits multi-billion-dollar pre-orders to secure allocation, has been a launch customer for every major Nvidia generation, and has consistently been allocation-constrained rather than demand-constrained. Microsoft's response — Maia (training/inference accelerator) and AMD MI400 commitments — is again the textbook Five Forces response to supplier power: develop or sponsor alternatives.

The supplier story isn't that either OpenAI or Nvidia is "going to lose Microsoft as a customer." The story is that the *cost of these inputs* and the *strategic flexibility around them* are set partly outside Microsoft's control, and that's the force the framework is built to surface.

### Threat of new entrants — low at hyperscale, moderate in AI-native niches

The economics of hyperscale cloud (data centers, undersea cables, regional presence, compliance certifications) are a near-perfect entry barrier. No new general-purpose hyperscaler will emerge — the capital cost and time-to-credibility are prohibitive.

The interesting new-entrant story is AI-native specialty clouds: CoreWeave, Lambda Labs, Crusoe, and a handful of others have built GPU-rich clouds aimed at the AI training workload. These don't compete with Microsoft on enterprise SaaS or general compute, but they do compete for a slice of the AI training spend and have shown the ability to win marquee deals (xAI, Meta, OpenAI itself for incremental capacity). The threat is real but bounded — it segments a piece of the AI-cloud market rather than substituting for the broader cloud category.

Sovereign-cloud entrants (national or regional clouds built for data-residency and political reasons) are a separate story. They constrain Microsoft's TAM in specific geographies but don't compete in the global commercial market.

### Threat of substitutes — moderate, asymmetric

The substitute story has two layers:

1. **Self-hosted open-source models** substitute for Azure OpenAI Service in cost-sensitive workloads. The substitution rate depends on quality gap (closing slowly) and operational tolerance (enterprises need indemnification, SLAs, compliance — all expensive to self-provide). Net effect: compresses Azure OpenAI margins, doesn't significantly substitute volume at Microsoft's enterprise customer base.

2. **Vertical AI platforms** (Salesforce's Agentforce, ServiceNow's Now Assist, niche industry SaaS with embedded AI) substitute for Copilot in specific workflows. The substitute pressure is highest where Microsoft's productivity dominance is weakest (CRM, ITSM, vertical workflows).

Neither substitute is existential. Both compress pricing power at the margin and require ongoing differentiation investment.

## Counter-argument

The bull view: Microsoft's distribution advantage (every enterprise already buys M365), the Copilot bundling economics, and the scale of capital deployment all create reinforcing moats that compound. The OpenAI dependency is mitigated by MAI and the multi-model strategy. The Nvidia dependency is mitigated by Maia + AMD + custom silicon. The five forces are tight but Microsoft's structural advantages absorb them.

Five Forces doesn't refute this — it forces the question of *which force is most likely to break the structural advantages*. The answer is supplier power. If OpenAI's commercial terms shift unfavorably, or if Nvidia allocation tightens further, the Copilot growth story has to be re-underwritten. Every other force is currently manageable.

## Signals to watch (next 18 months)

| Signal | Force | Why it matters |
|---|---|---|
| MAI commercial adoption inside Azure | Supplier power | Whether Microsoft can credibly source frontier-quality models in-house |
| Maia % of new Azure capacity | Supplier power | The Nvidia diversification trajectory |
| OpenAI direct enterprise sales activity | Supplier power | Whether the supplier is competing with the customer |
| Azure margin trajectory | Buyer power + Substitutes | Pricing discipline holding or compressing |
| Bedrock + Anthropic enterprise wins | Rivalry | Whether AWS is closing the AI-workload gap |
| CoreWeave / Crusoe contract sizes | New entrants | Whether specialty clouds graduate into hyperscale-substitute |
| Copilot per-seat ARPU | Buyer power | Revenue extension into the installed base |

## Key takeaway

The Microsoft Five Forces story in 2026 is not about Azure vs AWS. It's about supplier concentration: two suppliers (OpenAI for frontier models, Nvidia for GPUs) define the cost structure and strategic flexibility of the fastest-growing segment in the company. Every major strategic move of the last 18 months — MAI, Maia, Cobalt, the AMD MI400 commitment, the OpenAI amendment — is the Five Forces playbook for relaxing supplier power. The framework's contribution is to focus attention on the force that's actually shaping decisions, rather than the rivalry that gets most of the press.

If you only have time to track one variable, track the share of Microsoft AI inference happening on non-Nvidia, non-OpenAI stack. That number is the proof point for whether the supplier-power problem is being solved.

*Cover photo: [Taylor Vick on Unsplash](https://unsplash.com/photos/M5tzZtFCOfs).*

> **Want to run Five Forces on your own industry?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=microsoft-five-forces-example) walks each force with AI-assisted prompts and keeps the scorecard next to your other analyses. Free to start.

## Related

- [Porter's Five Forces beginner's guide](/academy/porters-five-forces-beginners-guide) — the framework's template and force definitions
- [Netflix Porter's Five Forces Analysis 2026](/examples/netflix-porters-five-forces) — a sibling analysis with very different force scoring
- [Five Forces airline industry analysis](/examples/five-forces-airline-industry) — an industry-level (not company-level) application
- [Apple PESTEL Analysis 2026](/examples/apple-pestel-analysis-2026) — when to use PESTEL *instead of* Five Forces
- [PESTEL framework](/frameworks/pestel) — the macro environment scan

---

### Netflix Porter's Five Forces Analysis 2026
URL: https://frameworklist.com/examples/netflix-porters-five-forces
> A worked Porter's Five Forces analysis of Netflix in 2026 — streaming rivalry, supplier power after the WWE deal, ad-tier substitutes, and what the model tells us about margin direction.

The streaming wars have a winner — at least on margin. Netflix entered 2026 with ~301 million paid members, double-digit operating margin expansion year over year, and the only ad-supported tier in streaming that's actually working at scale. So why is Porter's Five Forces still a useful lens? Because the same model that explains Netflix's pricing power also predicts where that power runs out. The most interesting force in 2026 isn't rivalry. It's substitutes — and what they do to the long-run ceiling on subscription revenue per hour of attention.

## Position being analyzed

Netflix's strategic position in mid-2026: it has converted scale into both buyer-side pricing power (multiple successful US price increases) and supplier-side commissioning power (paying showrunners directly instead of licensing finished shows). The open question for the next three years: where does the next leg of margin growth come from when subscription ARPU stops being elastic?

## Competitive rivalry — High, but structurally different from 2020

Four credible peers, each with a non-streaming parent that subsidizes the streaming P&L:

- **Disney+ / Hulu / ESPN bundle** — $25B+ in annual content; cross-funded by parks, cruises, and merchandise. Achieved DTC streaming profitability in Q1 2025.
- **Amazon Prime Video** — bundled into Prime; the marginal cost of a Prime subscriber consuming video is below the revenue from their commerce purchases. Effective price to the user: zero.
- **Max (Warner Bros. Discovery)** — HBO library + DC + sports tier; under pressure from the WBD split, but still spending $10B+ a year. *Update, October 2026:* Netflix agreed to buy Warner Bros. in December 2025, declined to match Paramount Skydance's $31-a-share offer on 26 February 2026, and Paramount completed the acquisition on 6 October 2026. So this rival now sits inside a larger parent. What Netflix's walk-away price says about its own resources is covered in the [Netflix VRIO analysis](/examples/netflix-vrio-analysis-2026).
- **Apple TV+** — small library, premium production. Apple is the only one with an explicit strategy of accepting losses to feed services revenue and Apple One bundling.

| Competitor | Content spend 2025 | Subsidy source | Threat type |
|---|---|---|---|
| Disney+ bundle | ~$25B | Parks, cruises, merchandise | Direct head-on |
| Amazon Prime Video | ~$19B (incl. sports rights) | E-commerce, AWS | Bundle / pricing |
| Max | ~$12B | HBO library equity | Premium content |
| Apple TV+ | ~$5B | Hardware, services bundle | Premium / long tail |

What's *different* from the 2020 picture: rivalry no longer expresses itself as "race to add subscribers at any cost." It now expresses itself as content-cost inflation and live-sports rights inflation. Netflix has the highest revenue per subscriber, the lowest churn (1.85%–1.88% in EMEA across the first three quarters of 2024 per company disclosures), and the strongest engagement per dollar of content spend. The rivalry is real but Netflix wins the underlying unit economics.

## Bargaining power of buyers — Low, with a soft floor at the ad tier

Two empirical tests Porter's model gives for buyer power:

- **Can you raise prices?** Netflix raised the US standard tier from $15.49 to $17.99 in 2024 and again to ~$19 in early 2026. Net subscriber additions in the quarter following each hike were positive in the US/Canada region. That's revealed preference: the modal household will pay.
- **Can subscribers switch costlessly?** Technically yes — no contracts. Behaviorally no — household viewing routines, profile customization, recommendation tuning, and the friction of cancelling-then-resubscribing produce ~5–7% monthly churn industry-wide vs Netflix's ~2%.

The exception is the ad-supported tier. **About 45% of US Netflix accounts are on the cheaper $7.99 ad-supported plan as of early 2025** (per Antenna). That tier dragged down ARPU per nominal subscriber — and it lowered the effective "price ceiling" for the whole subscription market. Buyer power isn't expressed through churn anymore; it's expressed through tier mix.

## Bargaining power of suppliers — Mixed, concentrated at the top

Two distinct supplier categories:

**High supplier power**:
- **Major sports leagues and live-rights holders.** The five-year, ~$5B Netflix–WWE deal (Variety, January 2024) and the NFL Christmas Day games are signal: when Netflix wants a uniquely valuable live property, it pays the price the rights-holder names.
- **A handful of A-tier showrunners and talent** with output deals (Shonda Rhimes, Ryan Murphy, Greta Gerwig).
- **AWS** — Netflix's primary cloud provider, also the parent of a direct competitor. Switching costs are real (engineering rewrite + multi-region capacity). Our [Amazon VRIO analysis](/examples/amazon-vrio-analysis-2026#the-rivals-invoice) reads this from Amazon's side: a rival that still has to pay AWS is evidence AWS is hard to imitate.

**Low supplier power**:
- Mid-tier studios. Netflix commissions originals rather than licensing back-catalog, so most studios face Netflix as a buyer-of-content with global distribution leverage.
- Talent agencies, post-production, dubbing/subtitling vendors. Netflix's scale of work makes them price-takers.

Net: supplier power is concentrated in 5–10 specific relationships, not diffuse across the supply chain.

## Threat of new entrants — Low

The barrier to entry is no longer "build a streaming app" — it's "spend $5B+ a year on content for five years to reach catalog viability AND build a global recommendation engine AND amortize over a global user base." That has been the same answer since 2018; no new credible entrant has launched since Apple TV+ in 2019. The closest thing to a new entrant in 2026 is YouTube *Primetime Channels* repositioning itself as the aggregation layer above streaming — which is not really entry, it's a different business model.

## Threat of substitutes — High, and rising

The substitute that matters isn't Disney+. It's **time spent**. Streaming subscribers don't quit Netflix to switch to Max; they quit because TikTok, YouTube Shorts, Instagram Reels, and gaming ate the evening hours they used to spend watching long-form video.

- Under-30s spend more weekly hours on TikTok and YouTube than on any subscription streaming service.
- US adults spend ~8.45 hours per week playing video games, and the gaming industry is on track for $270B in revenue by 2025 — money and time both substituting away from passive video.
- Netflix's own data suggests roughly 70% of viewing serves the "fill 30 minutes of downtime" use case, which is the exact need short-form video meets at zero price.

This is the most important force in the analysis. It explains why Netflix is investing in **games, live programming, and ad-tier**: each is a way to re-anchor attention that's drifting to free, short-form alternatives. Porter's framework doesn't tell you to build a games studio — but it tells you that the substitute force is the binding constraint, and any growth strategy that doesn't address it is treating a symptom.

## Key takeaway

Five Forces on Netflix in 2026 says the same thing as the income statement: this is a structurally good business that earned its current margins. The model predicts that competitive rivalry will keep content costs sticky-high but won't compress Netflix's margin further because Netflix has the unit-economics lead. Supplier and buyer power are managed. The binding force is **substitutes** — short-form video and gaming eat attention that the model can't price into a subscription. The strategic implication: the next 5 points of operating margin have to come from ad-load growth, the live/sports pricing premium, and adjacent monetization (games, transactional rentals) — not from another standard-tier price hike. Any plan that assumes ARPU keeps rising at the 2024–25 cadence is reading the wrong force.

## Want to go deeper on the framework

Read [Porter's Five Forces: a beginner's guide](/academy/porters-five-forces-beginners-guide) for how the model works in general, or see [Nvidia at $5T: the AI chip industry through Five Forces](/blog/ai-chip-five-forces-nvidia-5-trillion) and [Real Madrid Porter's Five Forces: the Super League play](/examples/real-madrid-porters-five-forces-2026) for current, news-pegged reads on very different industries. For a case where the five forces all move against the company at once, see the [Tesla Porter's Five Forces analysis 2026](/examples/tesla-porters-five-forces-2026), run against its July 22 Q2 earnings. Compare frameworks at [SWOT vs Five Forces](/compare/swot-vs-five-forces) to pick the right lens for your own analysis. To run a Five Forces on a different company, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance.

If you came here looking for a SWOT instead, our sister site [SWOTPal has a full Netflix SWOT analysis](https://swotpal.com/examples/netflix?utm_source=frameworklist&utm_medium=referral&utm_campaign=fiveforces-netflix) — it's a dedicated AI SWOT tool, free for the basic workflow.

---

### Netflix VRIO Analysis 2026: What the Warner Bros. Bid Priced
URL: https://frameworklist.com/examples/netflix-vrio-analysis-2026
> A VRIO analysis of Netflix in October 2026, after Paramount closed its Warner Bros. Discovery deal. Seven resources scored, and what Netflix's walk-away price says about imitability.

On 6 October 2026 Paramount Skydance closed its acquisition of Warner Bros. Discovery at $31 a share. Ten months earlier the same studios, HBO and the library behind them had been under contract to **Netflix**. That makes this the right month to run a VRIO analysis of Netflix, because the company has just told the market, in dollars, how much one missing resource was worth to it.

VRIO scores a company's resources one by one. For each it asks whether the resource is **V**aluable, **R**are, costly to **I**mitate, and whether the firm is **O**rganized to capture its value. Most VRIO write-ups answer the imitability question by assertion ("competitors would struggle to copy this"). Netflix's failed bid lets us answer it with a price. That is the anchor of this page, [The Auction Test](#the-auction-test).

## Position being analyzed

The numbers below come from Netflix's [Q2 2026 shareholder letter](https://www.sec.gov/Archives/edgar/data/0001065280/000106528026000211/ex991_q226.htm) unless noted. Netflix reports Q3 on **20 October 2026**.

| Metric | Value | Direction |
|---|---|---|
| Q2 2026 revenue | $12.56bn | +13% YoY (+12% FX-neutral) |
| Q2 2026 operating margin | 33.4% | vs 34.1% in Q2 2025 |
| Full-year 2026 revenue guidance | $51.0–51.4bn | Range narrowed; ~12% FX-neutral growth |
| Full-year 2026 operating margin target | 31.5% | vs 29.5% in 2025 |
| 2026 ads revenue target | ~$3bn | "A projected rough doubling" |
| Free cash flow, 2026 guidance | ~$12.5bn | Q2 FCF $1.5bn, hit by cash taxes on the WB termination fee |
| View hours, H1 2026 | 97bn+ | +2% YoY |
| Buyback capacity remaining | $27.1bn | After a new $25bn authorization in April and a record $4.7bn repurchased in Q2 |

The deal timeline, from Netflix's own releases and the [deal record](https://en.wikipedia.org/wiki/Proposed_acquisition_of_Warner_Bros._Discovery_by_Paramount_Skydance):

| Date | Event |
|---|---|
| Dec 2025 | Netflix agrees to acquire Warner Bros. (studios + HBO Max, after the Discovery Global split) at **$27.75/share**: $72.0bn equity, **$82.7bn enterprise value** |
| 13 Jan 2026 | Netflix amends the deal to all cash at the same price |
| 26 Feb 2026 | WBD's board rules Paramount Skydance's **$31/share** offer superior. Netflix [declines to raise](https://about.netflix.com/en/news/netflix-declines-to-raise-offer-for-warner-bros), calling the deal "no longer financially attractive" at that price, and says it will invest about $20bn in films and series in 2026 |
| Apr 2026 | Netflix authorizes an additional $25bn of buybacks. Paramount covers Netflix's $5.8bn termination fee |
| 6 Oct 2026 | Paramount completes the acquisition after DOJ, EU and UK approval and a September settlement with California and the WGA |

## VRIO applied, resource by resource

### 1. Global distribution and recommendation at scale: sustained advantage ✅

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | It turns one title into a global release on day one. 97bn hours watched in H1 2026 is the denominator every ad and pricing decision runs on |
| **Rare** | Yes | No other streamer pairs this reach with a single global catalog and a single recommendation system |
| **Inimitable** | Yes | The asset is years of viewing data in more than 190 countries. A rival can buy content, but it cannot buy back the time it would take to collect that data |
| **Organized** | Yes | Product, content and ads all run on the same system |

### 2. The cash engine: sustained advantage ✅

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | A 31.5% operating margin target and ~$12.5bn of FCF fund $20bn of content without outside capital |
| **Rare** | Yes | Every other large streamer is a division of a parent that subsidizes it |
| **Inimitable** | Yes | Getting there took 15 years of losses and scale. A late entrant cannot shortcut it |
| **Organized** | Yes | It is the resource that let Netflix walk away. A firm that needed the deal could not have |

### 3. Owned franchise IP: competitive disadvantage ❌

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | Franchises sell sequels, merchandise, parks and games long after the first release |
| **Rare** | Yes, for its owners | Decades-old characters and worlds are finite, and Disney and now Paramount own most of them |
| **Inimitable** | Yes | Nobody can create a 90-year-old character in 2026 |
| **Netflix holds it?** | **No** | This is the gap |

The clearest evidence is Netflix's biggest hit. KPop Demon Hunters became the most-watched title in Netflix history (266m views by 31 August 2025, per [Korea JoongAng Daily](https://www.koreajoongangdaily.com/entertainment/kpop-demon-hunters-becomes-most-watched-title-on-netflix-across-film-tv-categories/12176067) citing Tudum), and it was "developed and produced by Sony Pictures Animation" and licensed to Netflix, per [Variety](https://au.variety.com/2026/film/news/kpop-demon-hunters-2-confirmed-netflix-sony-34146). The sequel was announced jointly with Sony in March 2026. Netflix's answer was to sign the directors to an exclusive multi-year deal, which secures the talent but not the IP. When a resource is valuable, rare and inimitable and you don't have it, VRIO calls that a **competitive disadvantage**. The Warner Bros. bid was an attempt to buy the missing resource.

### 4. Ad-supported tier: competitive parity ➖

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | ~$3bn in 2026, roughly double 2025 |
| **Rare** | No | YouTube, Amazon and Disney all sell video ads at larger scale |
| **Inimitable** | n/a | Fails at Rare |
| **Organized** | Yes | Upfront commitments were closing in Q3 |

### 5. Live events: temporary advantage at best ⏳

Live is just over 5% of 2026 content spend and about 1% of view hours, yet it accounts for six of the top ten new-member sign-up days of the last five years (Q2 letter). That makes it **Valuable**. But NFL games and boxing cards are rented rights, and any rival can outbid Netflix when they come up for renewal. A rented resource fails **Inimitable** by construction. It works as an acquisition tool, not a moat.

### 6. Games: not yet a resource 🔬

Netflix's cloud TV games had their two best debuts in June, and kids' mobile engagement was up 600% YoY "off a small base." There is no revenue line to score yet, so VRIO treats games as an option rather than an advantage.

### 7. Local-language production network: temporary advantage ⏳

Netflix's network of producers in Korea, Spain, India and elsewhere is **Valuable** and still **Rare** at its breadth. It is not **Inimitable**, though. Production partners are not exclusive, as the Sony case shows, and Amazon and Disney are building the same networks. Its lead is in time and volume, not in anything a rival cannot eventually buy.

### Scorecard

| Resource | V | R | I | O | VRIO result |
|---|---|---|---|---|---|
| Global distribution + recommendation | ✅ | ✅ | ✅ | ✅ | Sustained advantage |
| Cash engine (margin + FCF) | ✅ | ✅ | ✅ | ✅ | Sustained advantage |
| Local-language production network | ✅ | ✅ | ❌ | ✅ | Temporary advantage |
| Live events | ✅ | ❌ | ❌ | ✅ | Parity, rented |
| Ad-supported tier | ✅ | ❌ | — | ✅ | Competitive parity |
| Games | ? | ❌ | — | — | Not yet a resource |
| Owned franchise IP | ✅ | ✅ | ✅ | ❌ (absent) | **Competitive disadvantage** |

## The Auction Test

VRIO's third question, "is it costly to imitate?", is the hardest to answer honestly, because nobody publishes a number for it. Netflix just did.

> **The Auction Test:** when a firm bids for a resource and walks away, its last price is the most it believes the resource is worth over the cheapest alternative, whether that is building it, substituting for it, or doing without. That number is that firm's imitation cost.

| Step | Netflix and Warner Bros., 2025–26 |
|---|---|
| The resource | Warner Bros. film and TV studios, HBO and HBO Max, and the library (DC, the Wizarding World films, the HBO catalog) |
| Highest price offered | $27.75/share, **$82.7bn enterprise value**, all cash |
| Price refused | Paramount's $31/share for all of WBD (26 Feb 2026). This is a different perimeter that includes Discovery Global, so the two figures cannot be compared directly |
| The firm's own build cost | About $20bn a year on films and series in 2026 |
| Ceiling ÷ build budget | 82.7 ÷ 20 ≈ **4.1 years** of Netflix's own content spend |
| What it did with the money | A $25bn additional buyback, $4.7bn repurchased in Q2 alone, and a $5.8bn termination fee collected |
| Revealed verdict | To Netflix, the WB library was Valuable and Rare but **substitutable for less than about four years of its own output** |

What makes this more than a restatement of the deal is the third column of VRIO. The library is not *imitable* at any price. No amount of money recreates Batman. But Jay Barney's original 1991 test listed **non-substitutability** as a separate condition, and VRIO folds it into the imitability question. Netflix's walk-away is a bet on substitution. Its argument is that a firm with the distribution advantage in row 1 can manufacture new franchises (Squid Game, Stranger Things, KPop Demon Hunters) faster than it could integrate old ones. The buyback says Netflix's board thinks its own resources are a better use of the next $25bn than Warner Bros.' resources were at $31 a share.

This is related to the [Buy-or-Become Test](/examples/apple-mckinsey-7s-analysis-2026#the-buy-or-become-test) on our Apple 7S page, but it runs the other way. Apple closed a capability gap by buying (licensing Gemini). Netflix tried to buy, priced the gap, and decided to build. One tests what a company changed. The Auction Test reads what a company refused to pay.

### Pre-registered: build, not buy

| | |
|---|---|
| **Placement** | Owned IP stays a competitive disadvantage that Netflix chose to close by building and substituting, not by acquisition |
| **Prediction** | Netflix announces no acquisition of a studio or film/TV library above **$10bn** before 31 December 2027 |
| **Falsifier** | Any such deal announced, including a renewed bid for a Paramount/Skydance asset |
| **Scored on** | Netflix's Q4 2027 shareholder letter (January 2028) |

## Where this misleads

- **A walk-away price is not a pure valuation.** Netflix also faced antitrust risk. The states and the WGA sued to block the Paramount version of the deal, and a Netflix–WB combination would have drawn at least as much scrutiny. Part of Netflix's ceiling is a regulatory discount, not a judgment about the library.
- **The perimeters differ.** Netflix bid for the studios and streaming business. Paramount bought all of WBD including the cable networks. The Auction Test uses Netflix's own ceiling against Netflix's own build budget for this reason, and never the gap between the two bids.
- **Substitution can fail slowly.** If Netflix's next five years of originals produce no second KPop Demon Hunters that it owns outright, the disadvantage in row 3 compounds. A VRIO score is a snapshot, and this one will be wrong if Netflix's hit rate falls.

## Signals to watch

| Signal | Resource | Date |
|---|---|---|
| Q3 revenue vs the $12.86bn guide, and operating margin vs 33.2% | Cash engine | 20 Oct 2026 |
| Ads revenue tracking toward ~$3bn | Ad tier | Q3 and Q4 2026 letters |
| Paramount–WB plans for HBO Max and licensing of WB titles to third parties | Owned IP (rival) | Ongoing |
| A Netflix-owned franchise reaching KPop Demon Hunters scale | Owned IP | Any Tudum top-10 report |
| NFL and live-rights renewals and their costs | Live events | 2026–27 |
| Any studio or library deal above $10bn | The pre-registered prediction | Through Dec 2027 |

## Key takeaway

VRIO on Netflix in 2026 finds a company with two genuine moats (reach and cash) and one real hole (owned franchise IP), and the Warner Bros. saga is the hole made visible. Netflix's $82.7bn ceiling is the only public number anyone has for what that hole was worth to it: about four years of its own content budget. Above that, it chose to keep substituting with originals and to buy back its own stock. **When a VRIO analysis can't settle imitability by argument, look for an auction.** The losing bidder's last price is the honest answer.

> Want to run VRIO on your own company's resources? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=netflix-vrio-example) walks the four questions with AI assistance.

## Related

- [VRIO framework](/frameworks/vrio): the four questions and how to score them
- [Tesla VRIO Analysis 2026](/examples/tesla-vrio-analysis-2026): the same test on a company whose durable moats are the boring industrial ones
- [Netflix Porter's Five Forces Analysis 2026](/examples/netflix-porters-five-forces): the industry this resource stack has to survive in
- [Amazon VRIO Analysis 2026](/examples/amazon-vrio-analysis-2026): The Rival's Invoice, which reads who has to buy from whom. Netflix, for one, pays AWS
- [Apple McKinsey 7S Analysis 2026](/examples/apple-mckinsey-7s-analysis-2026): the Buy-or-Become Test, the mirror image of The Auction Test

If you came here looking for a SWOT, our sister site [SWOTPal has a Netflix SWOT analysis](https://swotpal.com/examples/netflix?utm_source=frameworklist&utm_medium=referral&utm_campaign=vrio-netflix).

---

### Nike PESTEL Analysis (2026): the $1.5B tariff squeeze
URL: https://frameworklist.com/examples/nike-pestel-analysis-2026
> A 2026 PESTEL analysis of Nike: a ~$1.5B tariff hit and 1.2pp margin squeeze force a sourcing reshuffle out of China. Six macro forces, scored.

![A pair of white Nike sneakers photographed from above on a plain background](https://images.unsplash.com/photo-1597892657493-6847b9640bac?auto=format&fit=crop&w=1600&q=80)

Nike in mid-2026 is a textbook case of a company whose strategy is being written by something outside the industry. Not by On or Hoka eating its running share, not by Adidas's resurgence, not even by the cooled brand heat that CEO Elliott Hill was hired to fix — but by US trade policy. The single largest line item moving Nike's plan for fiscal 2026 is a tariff bill the company itself now estimates at roughly **$1.5 billion** gross, up from the ~$1 billion it forecast in June 2025, with a projected **1.2-percentage-point** drag on gross margin.

That is why this is a PESTEL, not a Five Forces. Five Forces analyzes an industry; PESTEL scans the macro environment — Political, Economic, Social, Technological, Environmental, Legal. Run cleanly on Nike, PESTEL does something useful and slightly uncomfortable: it refuses to give you six balanced cells. One force dwarfs the others, and most of the others are downstream of it.

### Prefer to watch or listen?

<YouTube id="qP4YZmAY00g" title="Nike's $1.5B Tariff Problem: A 2026 PESTEL Analysis" />

<Spotify id="1oPkXxEwnj17LMOTx2XZBK" title="Nike's $1.5B Tariff Problem: A 2026 PESTEL Analysis — Framework podcast episode" />

## Position being analyzed

Mid-2026: Nike is roughly eighteen months into Elliott Hill's turnaround, fiscal 2025 closed with revenue down about 10% to ~$46.3 billion (from ~$51.4 billion), and the company has begun phasing in "surgical" US price increases that started in the fall of 2025. The strategic question PESTEL helps with is not "is the brand healthy" — it's "which macro force sets the ceiling on the recovery, and can Nike move it?"

| Metric | Value | Direction vs. 12 months ago |
|---|---|---|
| FY2026 gross tariff cost estimate | ~$1.5B | Up from ~$1.0B (June 2025 forecast) |
| Tariff drag on gross margin (FY2026) | ~1.2 pts | Worse (was ~0.75 pts) |
| FY2025 revenue | ~$46.3B (−10% YoY) | Down from ~$51.4B |
| Footwear sourced from Vietnam + China + Cambodia | ~95% | Highly concentrated |
| China share of US footwear imports | ~16% → high single digits | Falling (deliberate, by end FY26) |
| US consumer pricing | Surgical increases from fall 2025 | New lever pulled |

## PESTEL scorecard for Nike, mid-2026

| Force | Direction for Nike | Strength | What flips it |
|---|---|---|---|
| **Political** | ❌ Hurting | Very high | Tariff relief / exemptions on SE Asia footwear |
| **Economic** | ❌ Hurting | High | Margin recovery vs. price-led volume loss |
| **Social** | ⚠️ Mixed | Medium | Sneaker culture tailwind vs. brand-heat cooling |
| **Technological** | ✅ Helping | Medium | AI demand-planning de-risks the re-sourcing |
| **Environmental** | ❌ Hurting | Rising | Move to Zero cost vs. SE Asia supply-chain footprint |
| **Legal** | ❌ Hurting | Medium | Supply-chain labor + customs-classification exposure |

One force is doing most of the work. The discipline of the scorecard is to show that — not to pretend Environmental and Political weigh the same this year.

## Political — the force that wrote the plan

The Trump administration's tariff regime is the defining external fact of Nike's fiscal 2026. Because ~95% of Nike footwear is made in Vietnam, China, and Cambodia, a tax on imports from those countries is effectively a tax on Nike's cost of goods. The company's own escalating estimate — from ~$1 billion in June 2025 to ~$1.5 billion by the fall — is the cleanest evidence that this is a moving, not a settled, risk ([Supply Chain Dive](https://www.supplychaindive.com/news/nike-1b-tariff-sourcing-price-hikes/752159/); [Manufacturing Digital](https://manufacturingdigital.com/news/nike-counts-cost-of-trump-trade-tariffs)).

The structural problem is that the obvious mitigation — leave China — runs into the fact that the alternatives are also tariffed. Vietnam, Nike's single largest sourcing country, sits squarely inside the same trade policy. Nike is cutting China's share of US footwear imports from ~16% toward the high single digits by the end of fiscal 2026, but that is a concentration play (don't depend on one tariffed country), not an exit from the tariff regime.

## Economic — margin compression, and the price-vs-volume bet

The Political force lands immediately as an Economic one. Tariffs compress gross margin by ~1.2 points in a year when Nike is already rebuilding from a 10% revenue decline. Management's response includes a "surgical" US price increase phased in from fall 2025 — and that is the central economic bet of the year: can Nike raise prices enough to offset tariff cost without triggering the volume loss that would deepen the revenue hole? In a soft consumer-discretionary environment, with Hoka and On offering credible premium alternatives, that elasticity question is genuinely open ([CNBC](https://www.cnbc.com/2025/10/06/nike-prices-rising-tariffs-ceo-elliott-hill-turnaround-plan.html)).

## Social — sneaker culture up, brand heat down

Two opposing social currents. The tailwind: athleisure and sneaker culture remain structurally large, and Nike still owns more mindshare than any competitor. The headwind: the brand cooled measurably through the DTC-overreach years, ceding shelf and cultural relevance to On, Hoka, and New Balance — which is precisely the gap Elliott Hill's turnaround targets by rebuilding wholesale relationships and sport-led storytelling. Social is the one force Nike most directly controls, which is why it's scored "mixed" rather than red.

## Technological — quietly the helpful one

Nike isn't a technology-moat company, but technology is the force most aligned with the year's actual problem. AI-driven demand planning and inventory allocation make the re-sourcing reshuffle less risky: moving production across Vietnam, Indonesia, and other Southeast Asian sites without overstocking or stocking out is a forecasting problem, and better forecasting is the difference between a clean transition and a margin-eating one. The Nike app, SNKRS, and membership data also give the company first-party signal to support the surgical pricing without flying blind.

## Environmental — Move to Zero meets a tariffed supply chain

Nike's Move to Zero commitments (carbon and waste reduction toward science-based targets) run through a supply chain concentrated in Southeast Asian contract manufacturing — the same factories now at the center of the tariff story. Sustainable-materials investment adds cost in a year where every cost point matters, and the environmental footprint of the supply base is increasingly a reporting and reputational obligation rather than an optional one. The force is rising, not decisive, in 2026.

## Legal — labor, customs, and the cost of compliance

Two legal vectors. First, supply-chain labor scrutiny in Vietnam and Cambodia — auditing, disclosure, and the reputational cost of any lapse — is a permanent feature of operating where Nike operates. Second, and newly salient, customs classification and trade-compliance complexity: when tariff schedules shift by country and product category, the legal-operational work of correctly classifying and documenting imports becomes a real cost center and a real risk. Neither is a quarter-mover alone; together they raise the baseline cost of being Nike's compliance function.

## The Nike Tariff Cascade

Here is the synthesis PESTEL surfaces that a margin bridge does not. When a Political cost lands on a company, it gets absorbed down a four-rung ladder — and **how far down a company has to reach is the true measure of its tariff insulation.** Nike's own stated four-pronged mitigation maps exactly onto these rungs:

| Rung | Absorption lever | Nike's 2026 move | Who pays |
|---|---|---|---|
| 1 | **Supply-base geography** | Cut China to high-single-digit % of US footwear; spread across Vietnam / Indonesia / others | Nobody (if alternatives are cheaper) |
| 2 | **Supplier & retail-partner margin** | Renegotiate factory and wholesale terms | Suppliers and retail partners |
| 3 | **Consumer price** | Surgical US price increases from fall 2025 | Customers |
| 4 | **Own cost structure** | Corporate cost reductions | Nike itself |

The diagnostic: a lightly tariff-exposed brand can stop at rung 1. A moderately exposed one reaches rung 2. **Nike is pulling all four rungs simultaneously** — which is the real read on the $1.5B number. The shock is larger than any single lever can absorb, so the response cannot be sequential; it has to be all-at-once. That is what "macro force exceeds firm-level mitigation" looks like in practice, and it's the kind of thing PESTEL is built to make visible.

## Key takeaway

PESTEL on Nike in 2026 doesn't return a balanced six-cell grid — it returns a verdict: one Political force, large enough to reorganize the entire fiscal year, cascading directly into Economics, with the other four forces mostly playing supporting roles. The strategic question isn't "is Nike's brand recovering" (it may well be, under Hill); it's whether a company can out-execute a macro shock it cannot exit, because the entire low-cost footwear supply base sits inside the tariffed zone. The Nike Tariff Cascade says Nike is reaching all the way to rung four — and a company pulling every absorption lever at once is, by definition, one whose macro environment has outrun its toolkit. PESTEL's contribution is to insist you score that honestly instead of narrating a tidy turnaround.

## Want to go deeper

Read more about the [PESTEL framework](/frameworks/pestel) or browse other [strategy framework examples](/examples). For PESTEL on a very different kind of subject — three macro forces across a host economy — see the [World Cup 2026 PESTEL analysis](/examples/world-cup-2026-pestel-analysis), and for the hyperscaler-buyer angle, the [Amazon PESTEL analysis 2026](/examples/amazon-pestel-analysis-2026). When the binding question is growth direction rather than macro exposure, the [Ansoff Matrix](/frameworks/ansoff) is the natural next lens — Nike's re-sourcing and premium-pricing moves each map onto a different Ansoff quadrant.

To run a PESTEL analysis on a company you're tracking, [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each of the six forces.

For Nike's SWOT counterpart, see our sister site [SWOTPal's Nike SWOT analysis](https://swotpal.com/examples/nike?utm_source=framework&utm_medium=referral&utm_campaign=pestel-nike) — a dedicated AI SWOT tool, free for the basic workflow.

*Cover photo: [Jakob Owens on Unsplash](https://unsplash.com/photos/A4579vLezz8).*

---

### Nvidia Ansoff Matrix 2026: the RTX Spark PC bet
URL: https://frameworklist.com/examples/nvidia-ansoff-matrix-2026
> A worked Ansoff Matrix of Nvidia's 2026 growth strategy, pegged to the Computex RTX Spark launch — why a consumer PC superchip is a Diversification bet, not just product development, and how the four quadrants balance.

The Ansoff Matrix is a deliberately simple framework — two axes, four quadrants, escalating risk as you move from the upper-left (selling what you have to who you have) to the lower-right (new product, new market). That simplicity is exactly what makes it the right lens for the Nvidia announcements at Computex on June 1, 2026. The headlines treated RTX Spark, Vera Rubin, and the Isaac GR00T humanoid robot as three separate product stories. Ansoff treats them as one portfolio decision — and immediately surfaces the part the product coverage missed: how much of Nvidia's growth is now riding on the highest-risk quadrant.

### Prefer to watch or listen?

<YouTube id="UyhCf8Nm6UM" title="Nvidia Ansoff Matrix 2026: the RTX Spark PC bet" />

<Spotify id="5xnh6lSPliLDwROfysKrZX" title="Nvidia Ansoff Matrix 2026: the RTX Spark PC bet — Framework podcast episode" />

## Position being analyzed

Nvidia in mid-2026 is a company of well over $130B in annual revenue with roughly 88% of it concentrated in Data Center / AI compute. Its core business is selling AI accelerators to hyperscalers and AI labs, defended by the CUDA software moat. At Computex, Jensen Huang announced [Vera Rubin in full production](https://nvidianews.nvidia.com/news/rubin-platform-ai-supercomputer), [RTX Spark](https://www.tomshardware.com/laptops/nvidia-unveils-rtx-spark-superchip-at-computex-2026-new-platform-promises-to-turn-windows-into-an-agentic-ai-os-with-arm-cpu-blackwell-gpu-and-128gb-unified-memory) — the company's first processor built for mainstream Windows PCs — and the Isaac GR00T reference humanoid robot. The strategic question Ansoff helps with: is this growth portfolio balanced, or is it tilting toward the riskiest quadrant just as the core business is already concentrated?

## The four quadrants

| Quadrant | Definition | Risk | Nvidia 2026 entries |
|---|---|---|---|
| **Market Penetration** | Existing product, existing market | Low | More Blackwell/Rubin GPUs into the same hyperscalers; deepening CUDA lock-in; gaming RTX into PC gamers |
| **Market Development** | Existing product, new market | Medium | Sovereign-AI national clouds; enterprise AI (NIM/AI Enterprise); Spectrum-X to non-Nvidia-GPU clusters |
| **Product Development** | New product, existing market | Medium-High | Vera Rubin platform; Spectrum-X annual cadence; next-gen networking into existing AI-cluster customers |
| **Diversification** | New product, new market | High | **RTX Spark** (consumer PC superchip); **Isaac GR00T** humanoid robot |

## Market Penetration: the cash engine

The unglamorous quadrant that funds everything else. Nvidia's penetration play is selling more accelerators to the same buyers — and the lever is less price than supply and software gravity. Every Blackwell and Rubin GPU shipped into an existing hyperscaler deepens the CUDA codebase those customers run on, which raises switching costs for the next purchase. This is penetration via moat, not via discounting. Ansoff scores it low-risk because the customer, the product, and the channel are all known — and it is where the operating cash that underwrites the riskier quadrants comes from.

## Market Development: same silicon, new buyers

Two moderate-risk bets take Nvidia's existing compute into new customer sets. **Sovereign AI** — selling the same accelerators to national governments building domestic AI clouds — is existing product into a genuinely new market. **Enterprise AI software and Spectrum-X networking** extends the existing stack to customers who may not be buying Nvidia's top-end GPUs. Same product, new market: textbook medium-risk Market Development.

## Product Development: where Vera Rubin lives

This is the quadrant casual observers conflate with diversification. **Vera Rubin**, announced in full production at Computex, is a new product — but it is sold to Nvidia's *existing* market: the hyperscalers and AI labs already buying Blackwell. New silicon, known customer, known channel, known use case. That is Product Development, the medium-high-risk quadrant, not Diversification. The same logic applies to the annual **Spectrum-X** networking cadence: new fabric products sold into the AI-cluster customers Nvidia already serves. The risk here is execution and roadmap (can the foundry and packaging keep pace), not market acceptance.

## Diversification: RTX Spark and the humanoid robot

This is the quadrant where the Ansoff lens earns its keep, because it forces the analyst to call Diversification what it is: highest risk.

**RTX Spark** is the headline. It is Nvidia's first SoC built for mainstream Windows PCs — an Arm-based 20-core Grace CPU (co-engineered with MediaTek), a Blackwell-class GPU with 6,144 CUDA cores, an NPU, and up to 128GB of unified LPDDR5X memory on a single TSMC 3nm package, rated at roughly 1 petaFLOP of AI performance ([Gizmochina](https://www.gizmochina.com/2026/06/01/nvidia-rtx-spark-launch-specs-windows-on-arm-pc/)). It ships in the fall across [Microsoft, Dell, HP, ASUS, Lenovo and MSI](https://www.cnbc.com/2026/05/31/nvidias-new-chip-to-power-fresh-line-of-windows-laptops-by-dell-hp.html) machines — Nvidia's plan is 30+ laptops and 10+ desktops at a premium tier (early Lenovo listings imply roughly $3,500–$4,700).

Why is this Diversification rather than Product Development? Nvidia already sells GPUs into PCs — but only as discrete add-in cards to gaming enthusiasts. RTX Spark is a different product category (a CPU/SoC, the heart of the machine, which Nvidia has never shipped for general-purpose PCs) aimed at a different market (the mainstream Windows thin-and-light buyer, going head-to-head with Apple silicon and Qualcomm Snapdragon X). New product axis *and* new market axis. That is the lower-right quadrant.

**Isaac GR00T**, the reference humanoid robot, is the second Diversification bet: a new product (Nvidia does not sell robots) into a new market (physical-AI and robotics OEMs). Like Tesla's Optimus, it scores as highest-risk by any honest reading of the framework.

## The Nvidia Ansoff Ladder (1999–2026)

Here is the original synthesis worth keeping: Nvidia has climbed the Ansoff Matrix one rung per era, and RTX Spark is simply the 2026 rung. The pattern is what makes the company's risk appetite legible.

| Era | Move | Ansoff quadrant |
|---|---|---|
| 1999 | Invents the GPU; sells graphics cards to PC gamers | Market Penetration |
| 2006–2012 | CUDA opens the GPU to general-purpose computing for the same hardware buyers | Product Development |
| 2012–2020 | Same GPUs repositioned for AI training in data centers — a new market | Market Development |
| 2020–2024 | Full data-center platforms (DGX, NVLink, Spectrum-X) for the AI-lab market | Product Development |
| 2025–2026 | Sovereign AI and enterprise clouds (new markets) + **RTX Spark PC SoC and GR00T robotics (new products, new markets)** | Market Development → **Diversification** |

The ladder shows the **adjacency discount** that distinguishes Nvidia's diversification from the textbook version: each new rung reuses the prior rung's asset — CUDA, the OEM channel, the foundry relationships, the software stack. RTX Spark is a Diversification bet, but it inherits Nvidia's existing PC-OEM relationships and CUDA gravity, which lowers its execution risk below a from-scratch market entry. That is the nuance the raw quadrant label hides — and the reason Ansoff is a starting point for the conversation, not the end of it.

## Key takeaway

The Ansoff Matrix on Nvidia in 2026 reveals a deliberate, two-front diversification layered on top of an already-concentrated core. Market Penetration and Product Development — more GPUs and the Vera Rubin platform into the same data-center customers — remain the cash engine and the center of gravity. But the genuinely new bets announced at Computex, RTX Spark and GR00T, both land in the highest-risk quadrant: new products into new markets, against entrenched incumbents (Apple, Qualcomm, Intel in PCs; an unproven category in humanoid robotics). The framework's contribution is to label that clearly and ask the proportionality question: is the ~88%-of-revenue data-center Star generating enough cash and management bandwidth to underwrite two simultaneous Diversification bets at once? Ansoff doesn't answer it — the next four quarters of data-center growth will. But the model makes sure the question gets asked instead of getting lost in the spec-sheet coverage.

## Want to go deeper

New to the model? Start with [Ansoff Matrix examples: the 4 growth strategies](/academy/ansoff-matrix-examples), which walks all four quadrants (and the Placement Test used above) on real companies. Read more about the [Ansoff Matrix framework](/frameworks/ansoff), or browse other [strategy framework examples applied to real companies](/examples). For the same lens on a different operator with a similar diversification tilt, see the [Tesla Ansoff Matrix analysis 2026](/examples/tesla-ansoff-matrix) — both companies are anchoring their valuation to their riskiest quadrant. For the same framework on a non-tech operator running all four quadrants at once, see the [FIFA Ansoff Matrix 2026: the World Cup growth bet](/examples/fifa-ansoff-matrix-2026). For the mirror image of Nvidia's risk appetite — a company that has quietly *retreated* from Diversification — see the [Apple Ansoff Matrix example 2026](/examples/apple-ansoff-matrix-2026), where 78% of revenue now sits in the lowest-risk quadrant. For Nvidia through two other lenses, see the [Nvidia BCG Matrix analysis 2026](/examples/nvidia-bcg-matrix) (which Stars and Cash Cows fund these bets — the mechanics of that funding loop are laid out in [Ansoff Matrix vs BCG Matrix](/compare/ansoff-matrix-vs-bcg-matrix)) and [Nvidia at $5T: the AI chip industry through Five Forces](/blog/ai-chip-five-forces-nvidia-5-trillion). To run an Ansoff analysis on a company you're tracking, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each quadrant.

For Nvidia's SWOT counterpart, see our sister site [SWOTPal's Nvidia SWOT analysis](https://swotpal.com/examples/nvidia?utm_source=frameworklist&utm_medium=referral&utm_campaign=ansoff-nvidia) — a dedicated AI SWOT tool, free for the basic workflow.

---

### Nvidia BCG Matrix Analysis 2026
URL: https://frameworklist.com/examples/nvidia-bcg-matrix
> A worked BCG Growth-Share Matrix of Nvidia's product portfolio in 2026 — Data Center as the dominant Star, Gaming as the Cash Cow, Automotive and Networking as Question Marks, and what the Dogs quadrant reveals about discipline.

The BCG Growth-Share Matrix is the right lens for Nvidia in 2026 for a specific reason: Nvidia is no longer a single-product company, but the public discussion treats it as one. The matrix forces the question every investor and operator should be asking — beyond the AI Star, what does the rest of the portfolio look like, and is it positioned to matter when AI capex growth eventually decelerates?

## Position being analyzed

Nvidia in mid-2026 is a roughly $130B-revenue company with one dominant business unit (Data Center / AI compute), one mature high-margin business unit (Gaming), and a handful of strategic bets that have not yet hit Star scale. The strategic question the BCG lens addresses: is the company managing the portfolio with the right discipline given the concentration?

## The four quadrants

| Quadrant | Definition | Nvidia 2026 entries |
|---|---|---|
| **Stars** | High share, high growth | Data Center / AI compute (H100, B200/B300 Blackwell, GB200 NVL72 systems, CUDA stack) |
| **Cash Cows** | High share, low growth | Gaming GPUs (RTX 50 series, GeForce installed base) |
| **Question Marks** | Low share, high growth | Automotive (DRIVE), Networking (Spectrum-X), AI Enterprise software / Omniverse |
| **Dogs** | Low share, low growth | Largely empty — historically Tegra mobile, OEM workstation lines |

## Stars: Data Center & AI compute

The [Star](/glossary/star) is overwhelming. Data Center revenue was ~$26.3B in a single quarter (Q2 FY2025) with 154% year-over-year growth, and continued to compound through FY2026. Three pieces of evidence place this in the Star quadrant unambiguously:

1. **Market growth rate** — AI training silicon [TAM](/glossary/tam-sam-som) is growing at 50%+ annually per IDC; well above the Cash Cow threshold.
2. **Relative market share** — Nvidia holds an estimated 70–95% share of AI training compute depending on which workload you measure. Custom hyperscaler silicon (Google TPU, AWS Trainium/Inferentia, Microsoft Maia) has share but in narrow workloads.
3. **Reinvestment intensity** — every dollar earned is being plowed back into the next generation (Blackwell → Blackwell Ultra → Rubin → Rubin Ultra roadmap), which is the textbook Star behavior. Cash Cows don't fund R&D at this intensity.

What makes this Star unusual within BCG's framework: it's not just dominant in a growing market; it's also defining the market's shape via the CUDA software moat. The matrix can't price moats, but the analyst should note that Nvidia's Star status is anchored to switching costs that are about 10 years deep in enterprise AI codebases.

## Cash Cows: Gaming

Gaming is the canonical Cash Cow:
- **Market growth**: PC gaming hardware grows in low single digits per year with cyclical swings.
- **Relative share**: 80%+ in discrete GPU shipments per Jon Peddie Research.
- **Margin**: gross profit ratio around 75% for the gaming GPU line.
- **Reinvestment requirement**: low — generational improvements (RTX 40 → RTX 50) are evolutionary.

The discipline question for the Cash Cow is *not* "is it growing?" — it isn't, and that's fine — but "is management harvesting cash from it without underinvesting?" Public capital allocation data suggests yes: Nvidia continues to push generational GPUs and DLSS/RTX features at the high end, while letting older SKUs run their natural lifecycle. Classic Cash Cow management.

## Question Marks: Automotive, Networking, and Software

This is where the portfolio gets interesting and where the BCG framework earns its keep.

**Nvidia DRIVE (Automotive)**: the autonomy SoC and software platform. The addressable market — auto compute for ADAS and L4 — is growing 30%+ annually. Nvidia's share is meaningful but not dominant against Mobileye, Qualcomm Snapdragon Ride, and the OEMs that develop in-house silicon (Tesla being the most prominent). DRIVE has been a Question Mark for nearly a decade; the BCG question is whether the next OEM design-win cycle (Mercedes, JLR, BYD partnerships) is enough to migrate it to Star status, or whether it stays a Question Mark indefinitely.

**Networking (Spectrum-X, NVLink Switch, BlueField DPU)**: the post-Mellanox stack positioned as the high-speed fabric for AI training and inference clusters. The market is growing rapidly because AI workloads are network-bound. Nvidia's share is rising fast as Spectrum-X gets bundled with GB200 / NVL72 systems. This is the Question Mark most likely to graduate to Star — it's already partly riding the Star's growth.

**Software & Subscriptions (AI Enterprise, NIMs, Omniverse Cloud)**: high-growth software-revenue category, low share of the overall enterprise AI software market (which is fragmented across hyperscalers, model vendors, and platform ISVs). Nvidia's discipline here will determine whether it becomes a Star or stays a small Question Mark.

For each Question Mark, BCG's discipline is binary: commit the cash to push it to leadership, or divest. The Spectrum-X investment is the most committed; Automotive is the longest-suffering.

## Dogs: notably empty

A healthy BCG portfolio usually has a few Dogs that should be divested. Nvidia's Dogs quadrant is notable for what's *not* there. The company has been unusually disciplined about shutting down weak lines:

- Tegra mobile (smartphone SoC) — exited in mid-2010s, redeployed to Switch and automotive.
- GeForce Now (the consumer cloud-gaming retail aspiration) — repositioned as an enterprise streaming service rather than a Stadia competitor.
- OEM workstation SKUs — pruned and consolidated into the Studio brand.

The absence of Dogs is a quiet leading indicator. Portfolios that accumulate Dogs (companies that can't kill products) tend to underperform; Nvidia's willingness to retire weak lines is a discipline most semiconductor companies lack.

## Key takeaway

The BCG matrix on Nvidia in 2026 says: the portfolio is dangerously concentrated behind one Star, but it's managed well. Gaming is being harvested correctly. The Question Marks are appropriately funded — Spectrum-X looks like the next Star in waiting; DRIVE is the long bet. There are no Dogs draining cash. The strategic risk the matrix surfaces isn't internal discipline; it's external — the entire valuation rests on the Star's market continuing to compound. The model's prediction: if AI capex growth decelerates faster than Question Marks can graduate, the company will look very different on this same matrix in 24 months. Worth re-running the analysis quarterly.

## Want to go deeper

New to the model? Read [BCG Matrix Analysis: The Four Quadrants Explained](/academy/bcg-matrix-analysis-explained) for the full methodology and the Cash-Cow Dependency Test, or the shorter [BCG Matrix framework page](/frameworks/bcg), and compare it to other portfolio tools at our [compare hub](/compare). For Nvidia through other lenses, see the [Nvidia Ansoff Matrix 2026: the RTX Spark PC bet](/examples/nvidia-ansoff-matrix-2026) — where the BCG Stars and Cash Cows here become the cash engine funding Nvidia's growth quadrants (new to that model? see [Ansoff Matrix examples: the 4 growth strategies](/academy/ansoff-matrix-examples), and [Ansoff Matrix vs BCG Matrix](/compare/ansoff-matrix-vs-bcg-matrix) for exactly how this portfolio diagnosis hands off to a growth prescription) — and [Nvidia at $5T: the AI chip industry through Five Forces](/blog/ai-chip-five-forces-nvidia-5-trillion). For the BCG Matrix applied to a portfolio in crisis rather than in surplus, see the [FC Barcelona BCG Matrix: the economic levers gamble](/examples/barcelona-bcg-matrix-2026), or to a freshly public company where the quadrants form a self-funding loop, the [SpaceX BCG Matrix Analysis 2026 (post-IPO portfolio)](/examples/spacex-bcg-matrix-2026), or to a giant whose single Cash Cow is under live AI attack, the [Alphabet BCG Matrix 2026](/examples/alphabet-bcg-matrix-2026). To run a BCG on a company you care about, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) walks you through the four quadrants with AI assistance.

For Nvidia's broader SWOT analysis, see our sister site [SWOTPal's Nvidia SWOT](https://swotpal.com/examples/nvidia?utm_source=frameworklist&utm_medium=referral&utm_campaign=bcg-nvidia) — a dedicated SWOT tool, free for the basic workflow.

---

### OKR examples from Google's early years
URL: https://frameworklist.com/examples/okr-google-classic-objective
> Andy Grove brought OKRs to Intel; John Doerr brought them to Google in 1999. A look at the OKRs that shaped Google's culture and what they teach about writing your own.

OKRs at Google are the canonical case study — partly because John Doerr documented them, partly because Google's growth made them the most-cited operating system in tech. The examples below are the ones Doerr describes in *Measure What Matters* and that have been confirmed publicly by Google executives over the years. They're useful both as templates and as warnings.

## OKR 1 — Sundar Pichai on Chrome (2008)

**Objective:** Build the best browser

**Key Results:**
- Reach 20 million 7-day-active users by end of 2008
- Reach 50 million 7-day-active users by end of 2009
- Reach 100 million 7-day-active users by end of 2010

What's right about this: a single, sharp metric (7-day-active users) repeated three times with escalating targets. Easy to track, hard to game. The target was explicitly ambitious — at the time Chrome had zero users.

The team missed 2008. They hit 2009. They beat 2010 (~120M).

**Lesson**: missing year 1 of a stretch OKR isn't failure — it's information. Google didn't fire the team. They re-set for the next quarter and continued.

## OKR 2 — YouTube on watch-time (2012)

**Objective:** Reach 1 billion hours of daily watch-time

**Key Results:**
- Improve the recommendation algorithm by [specific metric]
- Reduce video load time to under [N] seconds
- Expand video catalog by partnering with [N] new creators per quarter

What's right: the objective is a single bold number. The key results are specific actions the team could control. The team didn't promise watch-time directly (a lagging metric outside their full control); they promised the inputs that would drive it.

YouTube hit 1B daily hours in 2016.

**Lesson**: when an objective is a lagging metric (revenue, retention, watch-time), the key results should be the *leading* metrics you control.

## OKR 3 — Larry Page on a stalled project (~2008)

This one is famous for what it warned against. Larry was reviewing a struggling team's quarterly OKRs and noticed:

- **Objective:** "Maintain product quality"
- **Key Results:** "Reach 99.5% uptime", "Resolve 90% of support tickets within 24h"

His response, paraphrased: "This isn't an OKR. This is operational floor. You should be doing all of these every quarter. What's the *change* we're going to make?"

The team had quietly converted their quarterly bet into routine KPIs. The objective was vague; the key results were ongoing standards. Larry sent them back to write real OKRs.

**Lesson**: this is the most common OKR failure mode. An OKR has to commit to *change*, not to *maintenance*. If at the end of the quarter the world looks the same, the OKR wasn't an OKR — it was a status report.

## OKR 4 — Google Search ranking team (early 2010s)

**Objective:** Make search results meaningfully better for ambiguous queries

**Key Results:**
- Improve click-through on top result by 5% (measured: yes / no)
- Reduce abandoned searches by 10% (measured: yes / no)
- Launch ranking improvements based on [specific signal] (measured: yes / no)

What's right: each key result is binary — at quarter-end you either hit the number or you didn't. No fuzzy "made progress" judgments. The team either improved CTR by 5% or they didn't.

**Lesson**: well-formed key results have a single test of success that's defensible without explanation. "Improve X" is not a key result. "Improve X to Y by [date]" is.

## What these have in common

Looking across all four:

- **Objectives are 1 sentence, qualitative, ambitious.** "Build the best browser." Not "Improve Chrome's market share by 12% via the Q3 features roadmap and the Q4 marketing campaign while maintaining team velocity."
- **Key Results are quantitative and binary.** A real KR can be checked off as hit / missed without interpretation.
- **3–5 KRs per Objective.** Fewer and the bet is too narrow; more and the focus dissolves.
- **Ambition produces ~70% achievement.** Google's culture explicitly rewarded missed-but-stretched OKRs over hit-but-conservative ones. Teams that hit 100% were suspected of sandbagging.

## What Google got wrong (and learned)

Doerr admits OKRs at Google went through several wrong turns:

- **Year 1 (1999)**: too many OKRs per team. Teams were drowning in 12+ objectives per quarter. They cut to 3–5.
- **Years 2–3**: managers used OKRs as performance reviews. This destroyed the willingness to stretch — if missing your OKR meant a bad review, you'd write easy OKRs. They explicitly decoupled OKRs from promotion criteria.
- **Years 4+**: too much bureaucracy around grading OKRs. They simplified to a 0.0–1.0 score per KR, calculated once per quarter, with a simple readout.

The version Doerr describes in *Measure What Matters* is the one that survived 25 years of iteration. Other companies adopting OKRs would do well to skip the wrong turns and start with the simplified version.

## Run your own

The full method, including how OKRs differ from KPIs, is in the [OKRs vs KPIs Academy guide →](/academy/okrs-vs-kpis-difference). For modern, outcome-based templates by focus area, see [OKR examples for product teams](/academy/okr-examples-for-product-teams). The [OKR catalog entry](/frameworks/okr) has more templates. [Start a canvas](/sign-in) to draft your own.

> **Want to draft OKRs on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=okr-google-example) keeps objectives, key results, and their scoring in one worksheet — with AI-assisted prompts for the measurable half. Free to start.

---

### Pre-mortem Example: The Failure a Premortem Cannot Catch
URL: https://frameworklist.com/examples/premortem-cydoc-shutdown
> A founder published nine reasons her health AI startup failed after seven years. A premortem run on day one would have caught most of them — and structurally missed the one that mattered.

![Photograph of sticky notes covering a planning whiteboard](https://images.unsplash.com/photo-1454165804606-c3d57bc86b40?auto=format&fit=crop&w=1600&q=80)

A [pre-mortem](/frameworks/premortem) is a prediction exercise. You sit down before the work starts, assume it has already failed, and generate the reasons. Which means the honest way to evaluate one is against a known outcome — and almost nobody does that, because the two halves are rarely both public.

Here they are both public. In February 2026 **Rachel Draelos, MD PhD** published ["Why I Shut Down My Bootstrapped Health AI Startup After 7 Years"](https://glassboxmedicine.com/2026/02/21/why-i-shut-down-my-bootstrapped-health-ai-startup-after-7-years-a-founders-postmortem/) — an itemised, first-person, nine-cause account of why **Cydoc** did not work.

That is a more rigorous self-assessment than most companies ever produce, and it makes a fair test possible: run a competent premortem on the April 2018 starting conditions, and see how many of her nine it would have found.

The answer is six. What matters is *which* three it missed, and why one of them was never findable.

## The situation being analysed

Cydoc launched in **April 2018** (incorporated April 2019) and shut down on **22 August 2025**. It sold automated patient intake forms and AI-generated clinical notes to small medical practices. It was not a non-starter: it reached paying customers, was granted **two US patents**, and demonstrated a measured **10-minute saving per visit**.

Draelos is a physician with a computer science PhD from Duke, who worked on health AI during her medical training. On paper, close to an ideal founder for the problem.

| What was true at the start | |
|---|---|
| Founder background | MD + CS PhD, health AI research |
| Team | **Solo founder** |
| Funding | **Bootstrapped** |
| Target customer | Small medical practices |
| Founder's stated pricing philosophy | *"I'll price the software at what it costs to run!"* |
| Founder's stated customer assumption | *"I was representative of my target customer"* |
| Distribution plan | Effectively none — "build it and they will come" |

## Her nine causes, sorted by whether a premortem finds them

The [site's premortem procedure](/frameworks/premortem) is a 60–90 minute session: assume total failure, write reasons silently, round-robin, cluster, vote, assign mitigations. Run that in April 2018 with a couple of outside skeptics in the room, and here is the realistic yield.

| # | Her stated cause | Would a day-one premortem generate it? |
|---|---|---|
| 1 | Waited over a year before talking to real potential customers | **Yes** — a top-three answer in almost any startup premortem |
| 2 | Misunderstood the MVP; built complexity, omitted essentials | **Yes** — follows directly from #1 |
| 4 | No sales or marketing owner; "build it and they will come" | **Yes** — the single most-generated failure narrative there is |
| 5 | Solo founder wearing CEO, CTO and CRO hats | **Yes** — and it was a *known fact*, not a forecast |
| 6 | No EHR integration → workflow friction → churn | **Yes**, plausibly — she is a physician; the friction is domain-obvious |
| 7 | Weak technological moat; competitors replicated the core | **Maybe** — generic enough to appear, hard to make actionable |
| 3 | Inefficient early software practices, wasted rewrites | **Unlikely** — real, but not the shape of a failure story |
| 8 | A bad custom-development contract for promised revenue that never came | **No** — a specific contingent event years out |
| 9 | **Broken business model, never addressed** | **No — and not for lack of imagination** |

Six clear hits. That is not a bad showing, and it is consistent with what the technique's own evidence base claims: a premortem reliably gets risks **onto the table**.

Then there is number nine.

## The one it could not have found

Draelos describes the pricing decision as a deliberate act, made on principle:

> "I thought to myself, I'm going to be the first person to run a business where I sell things for a fair price. I'll price the software at what it costs to run!"

And the arithmetic that eventually followed from it:

> "Doctors in the small practices we had been targeting wanted to pay fewer than $100 per month for our product. Now that we'd added the AI scribe, the hosting and AI costs for our platform had gone up to about $70 per doctor."

> "With revenue only $30 above hosting costs, and $4,000 to $6,000 per EHR integration, it would take 11 years per practice just to break even."

That last figure is not rhetorical. **$4,000 ÷ $30 per month = 133 months ≈ 11.1 years**, and that is the low end. The integration was also cause #6 — the fix for the churn problem was priced out of reach by the pricing philosophy.

Her own diagnosis of the philosophy is the sharpest line in the postmortem:

> "You have to factor in all kinds of other costs, like software engineers, tech support, salespeople, marketers, legal fees, accounting fees, and so on."

Now try to generate that in a premortem. The prompt is *"it is 2025 and Cydoc has failed — why?"* You are asking a room to imagine a future disaster. But this is not a future disaster. **It is a ratio that is false today, held in place by something that feels like a virtue.** There is no failure narrative to tell about it, because nothing goes wrong — the plan works exactly as designed, and the design cannot support a company.

## The Decision Replay

| What the framework says | What she actually did | What actually happened |
|---|---|---|
| A day-one premortem generates ~6 of the 9 eventual causes — customer discovery, MVP scope, no sales owner, solo-founder risk, workflow friction, weak moat. Per its own procedure, the team then **votes** and mitigates the top 5–7. | Built for over a year without customer discovery; priced at cost of hosting on principle; stayed solo; shipped standalone without EHR integration. | Reached paying customers, two US patents, a measured 10-minute saving per visit — and shut down on 22 August 2025 after seven years, with the business model listed as the ninth and final cause. |

The uncomfortable part is that the premortem's six hits would probably not have saved it. Fix customer discovery, fix the MVP, hire a sales lead, find a cofounder — and you arrive faster at a company that still earns $30 a month per doctor against a $4,000 integration bill.

**The premortem would have made Cydoc better at a business that could not work.**

## The Day-One Test

The site's own [premortem page](/frameworks/premortem) already carries the technique's central caveat, and it is worth restating precisely because this case extends it. The 1989 Mitchell, Russo and Pennington study behind prospective hindsight measured **how many** reasons people generated, not whether the reasons were any good. Getting risks onto the table is what the evidence supports; ranking them is the load-bearing step.

This case adds something the triage step cannot fix. **Triage can only sort what was generated**, and there is a class of failure the generation step never produces.

Look at what the 1989 study actually found: describing an event as certain rather than possible produced longer explanations containing more **episodic** reasons. Episodic means story-shaped — events, sequences, things that happen. That is what the technique is built to recruit, and it is very good at it.

A broken unit economic is not episodic. Nothing happens. It is simply already true. Surfacing it takes decomposition, not imagination: the move [first principles thinking](/academy/first-principles-thinking-with-examples) is built for.

> **The Day-One Test — before running a premortem, sort your plan's load-bearing assumptions into two piles: the ones that need imagination to evaluate, and the ones that need a calculator. Compute the second pile now, because those quantities are already either true or false and no failure narrative will change them. Then run the premortem on the first pile, which is what prospective hindsight is genuinely good at.**

The calculator pile is short and nearly always the same shape:

- **Unit cost against unit price.** What does one customer cost to serve, and what do they pay? Cydoc: ~$70 versus under $100.
- **Payback period on the thing you'll be forced to build.** Cydoc: $4,000–$6,000 EHR integration against a $30 monthly margin — 11 years.
- **Customers needed to cover fixed costs.** At a $30 margin, one salary is thousands of doctors.
- **Runway against sales-cycle length.** How many full sales cycles fit before the money runs out?

None of these requires foresight. All of them were computable in April 2018, and each would have produced a number that no amount of imagined disaster could have produced.

## Where this misleads

**This is not a criticism of Draelos.** She built a product that worked, earned patents and paying customers, and then published a nine-cause postmortem more honest and more specific than most companies manage. The finding here is about the *technique*, and it only exists because she did the unusual thing of publishing both halves. The counterfactual premortem in this piece is generous to her and hard on the framework, which is the right way round.

**Six out of nine is a good result, not a bad one.** It would be easy to read this as "premortems don't work." They do the thing they claim: surface risks a team would otherwise not voice. The claim here is narrower — that there is a category they structurally cannot reach, and that category is cheap to cover by other means.

**The Day-One Test is not a substitute for a premortem, and its output can be wrong too.** Unit economics change: costs fall, prices rise, a segment shifts. Cydoc's got *worse* mid-life, when adding the AI scribe pushed hosting to ~$70. So the calculator pile needs recomputing at every major product change, not just at founding — which is the same discipline as the premortem's own step 8, rereading the list at the midpoint.

**One case is not evidence about the technique in general.** This is a single well-documented failure, chosen precisely because both halves are public. It is a demonstration of a mechanism — narrative generation misses non-narrative facts — not a measurement of how often that mechanism bites.

## Now run yours

1. **Write the two piles first**, before booking the premortem. Anything with a unit, a rate, or a period goes in the calculator pile.
2. **Compute the calculator pile.** If a number comes back structurally impossible, stop — you have found something a premortem would not have told you, and no mitigation list fixes an inverted ratio.
3. **Then run the premortem on what's left**, and remember that voting and triage is the load-bearing step, not the brainstorm.

The [free Pre-mortem worksheet](/tools/premortem) runs step 3 in the browser with no signup — assume the failure, list the causes, then rank them. For a copyable version with steps 1-2 built in, the [premortem template](/academy/how-to-run-a-premortem#the-premortem-template) carries them as a single **Calculator Row**.

> Want to run a premortem on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a pre-mortem worksheet with AI assistance alongside 100+ other frameworks.

## Want to go deeper

- [Pre-mortem framework](/frameworks/premortem) — the procedure, the provenance chain, and The 30% Gap
- [How to run a premortem](/academy/how-to-run-a-premortem) — the full facilitation guide
- [Pre-mortem vs post-mortem](/compare/premortem-vs-postmortem) — the two halves of the same instinct, and when each is worth the meeting
- [Ikigai Career Example: The Four Circles Pointed at Google](/examples/ikigai-turning-down-google) — the other Decision Replay, on a personal decision with a known outcome
- [Pros and Cons Example: 9 Pros, 5 Cons, and the One That Decided It](/examples/proscons-cto-to-ic) — a real published pros/cons list, graded seven years later
- [Ansoff Matrix Example: The Growth Move That Isn't on the Grid](/examples/ansoff-37signals-subtraction) — the first business-decision replay, where the winning move is not on the grid

*Cover photo: [Patrick Perkins on Unsplash](https://unsplash.com/photos/ETRPjvb0KM0).*

---

### Premortem on a product launch that almost shipped broken
URL: https://frameworklist.com/examples/premortem-product-launch
> A 45-minute premortem before a major SaaS launch surfaced 3 risks the team hadn't named. Two became the actual reasons the launch needed a 2-week delay.

A B2B SaaS team three weeks from launching a major redesign. The product was technically ready, marketing was queued, the launch date had been announced internally. The CEO asked for one premortem before pulling the trigger.

What the premortem surfaced — and what happened when they ignored it — is one of the cleanest case studies I have for why this 45-minute exercise pays off.

## Setup

The launch in question: a complete redesign of the core product surface, plus a new pricing tier introduced alongside. The redesign had been in development 5 months; pricing tier was a 3-week add. Both were ready in staging.

7 people in the premortem: the CEO, 2 PMs, 2 engineers, head of CS, head of sales. Everyone had been on the project for 3+ months.

## How it ran

Standard premortem structure:

1. **Frame** (5 min). "Six months from now, the launch failed. It's our retrospective. What happened?"
2. **Silent writing** (10 min). Each person wrote independently. No discussion.
3. **Round-robin readout** (15 min). Captured every item on stickies.
4. **Cluster and prioritize** (10 min). Grouped by underlying theme.
5. **Decide** (5 min). Top 3 clusters got owners and mitigations.

## What got surfaced (8 raw items, 3 clusters)

The 8 individual items written by the team:

1. "The new pricing tier confused existing customers and triggered churn"
2. "Sales team didn't know what to say to customers asking about the price change"
3. "The redesign broke a specific power-user workflow we don't have telemetry on"
4. "Onboarding flow assumed users knew where things had moved"
5. "Support was overwhelmed in week 1"
6. "We launched on the wrong day (overlap with a competitor announcement)"
7. "Press coverage was lukewarm — the story wasn't sharp"
8. "We hadn't migrated existing customer data to the new schema for an edge case"

Clustered into three themes:

- **Cluster A — Pricing change communication** (items 1, 2, 5): nobody knew exactly what to tell existing customers
- **Cluster B — Power-user breakage** (items 3, 4, 8): the redesign and migration assumptions hadn't been pressure-tested against actual workflows
- **Cluster C — Launch narrative** (items 6, 7): the team wasn't aligned on the single sentence that would describe the launch externally

## What got acted on

The CEO accepted clusters A and B as material risks. Cluster C was acknowledged as a real gap but deferred (the team felt the redesign was the story).

**Cluster A action**: Sales + CS spent the next week creating a customer-facing FAQ and an internal cheat-sheet. Identified 30 highest-ARR accounts and pre-briefed them by phone before the public announcement.

**Cluster B action**: Engineering rebuilt the migration script to handle the edge case (item 8) and added telemetry to the suspect power-user workflow (item 3). They also extended access for the 50 most active customers to test the redesign in a parallel environment for the final week before launch.

**Cluster C**: deferred — turned out to be the right call for the wrong reason (the launch story was indeed weak; press coverage was lukewarm; not catastrophic).

## What happened at launch

Two of the three predicted failure modes materialized.

**Cluster A risk fully realized.** Despite the pre-briefing of top accounts, the rest of the customer base reacted to the pricing tier with confusion and a noticeable spike in support tickets. The cheat-sheet that Sales had built was crucial — without it, the team estimated CS would have been overwhelmed for weeks instead of days.

**Cluster B risk partially realized.** The migration edge case (item 8) was caught by the rebuilt script — never hit a real customer. The power-user workflow telemetry (item 3) immediately showed a 60% completion drop the day of launch. Engineering shipped a fix within 36 hours that restored the workflow. Without the pre-launch telemetry, the team estimated the issue would have taken 7–10 days to identify and fix, during which they'd have lost several enterprise accounts to escalation.

**Cluster C** materialized exactly as predicted (lukewarm press, story not sharp). No real impact — the launch's success came from existing customer expansion, not new sign-ups.

## What the premortem was worth

The team calculated, roughly:

- 12 customer escalations avoided (Cluster A pre-brief) × estimated $5k/escalation in churn risk = ~$60k saved
- 60% completion drop caught in 36 hours vs ~10 days (Cluster B telemetry) = unmeasured but counted in retained accounts

Cost: 45 minutes of 7 people's time. The most absurdly leveraged time the team spent that quarter.

## What this teaches

- **The premortem's value is the items that surface that the project lead refused to see.** Cluster A had been raised informally by CS *twice* before the premortem. Both times the founder shrugged it off. In the premortem context, it became a list everyone could see and not deny.
- **Acting on premortem output requires the project owner's buy-in.** This CEO accepted the analysis. I've watched premortems where the lead defended against every item — those produce no risk reduction.
- **The post-launch retrospective is the validation step.** Most teams skip the retro that compares premortem predictions to actual outcomes. That's the loop that compounds — each subsequent premortem gets sharper.

## Run your own

[Open the premortem worksheet →](/tools/premortem), or read the [full Academy guide](/academy/how-to-run-a-premortem) for the methodology. For the difference between this technique and its retrospective cousin, see [Premortem vs Postmortem](/compare/premortem-vs-postmortem). PMs studying for certification: see [Cynefin Framework for PMP](/academy/cynefin-framework-for-pmp) — Cynefin tells you whether you're in the Complex domain where premortems earn their keep.

> **Running a premortem before your next launch?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=premortem-launch-example) ships the premortem worksheet — imagine the failure, list the causes, assign the mitigations. Free to start.

---

### Pros and Cons Example: 9 Pros, 5 Cons, and the One That Decided It
URL: https://frameworklist.com/examples/proscons-cto-to-ic
> A CTO published the real pros and cons list for stepping down to individual contributor. Seven years on, the count was irrelevant and one unlisted property decided everything.

![Photograph of a forest path splitting into two trails between trees](https://images.unsplash.com/photo-1429743305873-d4065c15f93e?auto=format&fit=crop&w=1600&q=80)

Almost every [pros and cons](/frameworks/proscons) tutorial demonstrates the technique on a decision nobody made, with items nobody wrote, and then declares the longer column the winner.

Real lists are rarely published. Lists with a checkable outcome attached are rarer still. This one is both.

In November 2019, six months after leaving the CTO role at Artsy for a Principal Engineer role at AWS, **Daniel Doubrovkine** published [the actual list](https://code.dblock.org/2019/11/17/the-pros-and-cons-of-going-from-management-back-to-ic.html) under his own name: nine pros, five cons, for going from management back to individual contributor.

Seven years later we can ask the only question that really matters about a decision framework: **did the structure of the list do any of the work?**

It did not. And the reason is a property of the decision that he *did* write down — in the wrong place.

## The list, as published

| Pros (9) | Cons (5) |
|---|---|
| Extended technical relevance by ~a decade, at unprecedented operational scale | Loss of organisational power — no longer in hiring, firing, promoting |
| Autonomy — *"working autonomously is literally in my job description"* | Can only influence, not decide, on non-technical matters |
| Reduced stress; normal hours; room for deep work | Must *"spend a lot of energy explaining a problem to a decision maker instead of just fixing it"* |
| Coding as a primary activity | Many perceive the move as **career limiting** |
| *"I can choose not to take a meeting, cater to an investor or deal with an unhappy customer"* | No longer the face of the organisation |
| Not on call for catastrophic failures | |
| No direct reports venting; less gossip and politics | |
| Competitive compensation — AWS RSUs *"are liquid and are the same as cash"* | |
| **Reversible** — can return to management or a CTO role later | |

Count them and the list says **move, nine to five.** He moved, and six months in his verdict was *"Six months in, yes."*

So the framework was right. This is the case that should make pros/cons look good — which is exactly why it is worth taking apart.

## What actually decided it

Doubrovkine tells us, and it is not the count:

> "My health is better and the stress level is lower. Some things money can't buy."

That is **one bullet out of nine.** In the list it sits between "coding as a primary activity" and "I can choose not to take a meeting" — three entries that the format renders identical in weight. The thing that decided the decision is typographically indistinguishable from meeting flexibility.

This is the failure mode the [framework page](/frameworks/proscons) already names first: **false symmetry**, where every entry is treated as equally weighted so the longer column wins. Here the longer column *was* the right answer, which makes the symmetry problem harder to see, not easier.

> A framework that returns the correct answer while contributing nothing to it is more dangerous than one that is obviously wrong — because you will trust it next time, on a decision where the count and the truth point in different directions.

## What happened to the cons

Seven years is long enough to grade them.

| Con, as listed in 2019 | What followed |
|---|---|
| Loss of organisational power | Real, and by his account it was the trade he wanted |
| Can only influence, not decide | Real |
| Energy spent explaining rather than fixing | Real |
| **"Many perceive the move as career limiting"** | **Did not bind.** He became a founding Principal Engineer of **OpenSearch**, one of AWS's most visible open-source projects, and later moved to Shopify Engineering where, by his own account, he **created the Augmented Engineering team** |
| No longer the face of the organisation | Inverted, arguably — OpenSearch made him a public face of a project rather than a company |

The con that sounds most frightening when you write it is the one that did not happen. That is not a general law — it is one person, in one market, with an unusually strong track record. But it is a useful corrective to how that particular fear reads on a list, where "career limiting" occupies exactly as much space as "less gossip."

## The Decision Replay

| What the framework says | What he actually did | What actually happened |
|---|---|---|
| **Move.** Nine pros against five cons is a decisive margin by an unweighted count — the standard way the technique is taught. | Left the CTO role for Principal Engineer at AWS, and published the list six months in. | Stayed on the IC track for years as founding Principal Engineer of OpenSearch; later created a team at Shopify. His own self-description is still *"entrepreneur, technologist, and open-source enthusiast."* The decisive factor he names — health and stress — held. The scariest con did not materialise. |

Right answer. Right outcome. **And the list's structure contributed nothing** — because the one item that mattered was weighted the same as the eight around it, and the item that should have governed the whole exercise was filed as pro number nine.

## The Reversibility Multiplier

Look again at that ninth pro:

> **Reversible** — can return to management or a CTO role later.

He did not omit reversibility. The [framework page's third pitfall](/frameworks/proscons) warns against exactly that — *"leaving out reversibility. A decision you can undo in three months should be weighted differently from one you're locked into for five years."* He included it.

He included it **as a line item**, which is the subtler error, because a pros/cons list has no slot for a thing of this type. Reversibility is not a benefit of one option. It does not belong on a side.

> **The Reversibility Multiplier — reversibility is not an entry in a pros and cons list, it is a scalar on how lopsided the list has to be before you act. Write it above the list as one line: how long would undoing this take, and what would it cost? If the answer is under a year at modest cost, you do not need a decisive list — you need a non-catastrophic one. If the decision is irreversible, a modest majority of pros is nowhere near enough.**

Run Doubrovkine's decision that way and the nine-to-five count stops mattering entirely:

1. **Above the list:** *Can I undo this?* Yes — a former CTO with a strong track record can return to management. Cost: some time, some perception risk.
2. **Therefore the bar is low.** The list does not need to be decisive. It needs to contain no catastrophic con.
3. **Scan the cons for catastrophe.** Loss of power, less authority, more explaining, perception risk, less visibility. All are real, none is unrecoverable.
4. **Done.** The decision is made without counting anything.

That is a two-minute exercise that reaches the same place as the fourteen-item list, and it reaches it for the right reason. It also explains why he could act on a list whose decisive item he could only articulate as *"some things money can't buy"* — with the option to return, he did not need to justify the feeling. He only needed the downside to be survivable.

## Where this misleads

**Reversibility is often overestimated, and the multiplier cuts both ways.** "I can always go back" is one of the most common self-deceptions in career decisions — skills decay, networks cool, titles get harder to re-earn with each year away, and the market you would return to is not the one you left. The multiplier is only as good as an honest answer to *"how long, and at what cost."* If you cannot state both, treat the decision as irreversible.

**Doubrovkine's reversibility was unusually real.** A former CTO with a public track record and a decade of visible open-source work has options most people do not. Someone stepping off a management track without that record may find the return path genuinely closed, which flips the bar from low to high.

**This is a survivorship case with a happy ending.** The people whose IC move did turn out to be career limiting are not publishing seven-year retrospectives. The con was real; it simply did not bind here.

**One published list is not evidence about lists in general.** What it demonstrates is a mechanism — that an unweighted format hides both the decisive item and the governing property — not how often that mechanism changes an outcome.

## Now run yours

1. **Write the reversibility line first, above everything.** How long to undo, at what cost. Be specific and pessimistic.
2. **Set the bar from it.** Reversible and cheap → the list only has to be non-catastrophic. Irreversible → you need a wide margin and you should probably not be using a pros/cons list at all.
3. **Then write the list, and mark the one item you would not trade away.** If you cannot name it, you are not ready to decide. If you can, check whether the count agrees — and if it disagrees, believe the item, not the count.

The [free Pros and Cons worksheet](/tools/pros-and-cons) runs in the browser with no signup, and supports weighting — which is the whole point.

> Want to run this on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships a weighted pros/cons worksheet alongside 100+ other frameworks.

## Want to go deeper

- [Pros and Cons framework](/frameworks/proscons) — the method, the four pitfalls, and when to escalate to a weighted matrix
- [Weighted Decision Matrix](/frameworks/weightedmatrix) — the right tool once you have more than two options or more than one criterion that matters
- [Regret Minimization](/frameworks/regretmin) — the framework for the item you would not trade away
- [Ikigai Career Example: The Four Circles Pointed at Google](/examples/ikigai-turning-down-google) — a Decision Replay where the count and the truth *did* point in different directions
- [Pre-mortem Example: The Failure a Premortem Cannot Catch](/examples/premortem-cydoc-shutdown) — the same treatment applied to a startup shutdown
- [Ansoff Matrix Example: The Growth Move That Isn't on the Grid](/examples/ansoff-37signals-subtraction) — the first business-decision replay, where the winning move is not on the grid

*Cover photo: [Jens Lelie on Unsplash](https://unsplash.com/photos/u0vgcIOQG08).*

---

### PSG McKinsey 7S: the post-Mbappé team-first reset
URL: https://frameworklist.com/examples/psg-mckinsey-7s-2026
> A McKinsey 7S analysis of Paris Saint-Germain — how QSI's club finally won the Champions League by realigning the soft elements (style, staff, shared values), not by spending more.

This is part of our [World Cup 2026 strategy series](/series/world-cup-2026) — the business of football read through strategy frameworks. We've used Ansoff to read [FIFA](/examples/fifa-ansoff-matrix-2026) and [Manchester City](/examples/manchester-city-ansoff-matrix-2026), and Porter's Five Forces for [Real Madrid](/examples/real-madrid-porters-five-forces-2026). Paris Saint-Germain needs a different lens again, because its story isn't about growth or industry structure — it's about **organisational alignment**. For that, the tool is McKinsey 7S.

The puzzle: for a decade, Qatar Sports Investments tried to *buy* the Champions League — Neymar, Messi, and Kylian Mbappé, the most expensive front three ever assembled — and never won it. Then, with all three gone, PSG finally lifted the trophy. McKinsey 7S explains why the empty-handed superstar years and the winning post-superstar season are the same story told through seven variables.

## Position being analyzed

PSG is QSI's flagship: €806m in revenue, third-highest in world football, and for years the textbook case of money failing to buy the one trophy it most wanted. In [2025 it finally won its first Champions League, beating Inter Milan 5-0](https://www.olympics.com/en/news/psg-win-mens-champions-league-final-2025-final-result) in Munich — the largest margin in any major European final — with [four goals scored or assisted by teenagers](https://www.espn.com/soccer/report/_/gameId/733620). The strategic question 7S answers: what actually changed? The budget didn't. The owner didn't. The ambition didn't. What changed were the soft elements of the organisation.

## PSG's 7S Realignment

The citable core: each of the seven elements, the MNM (Messi–Neymar–Mbappé) era versus the post-Mbappé reset. Note that the *hard* S's barely move; the *soft* S's all flip.

| Element | Type | MNM era | Post-Mbappé reset |
|---|---|---|---|
| **Strategy** | Hard | Win the Champions League | Win the Champions League (unchanged) |
| **Structure** | Hard | QSI capital, elite infrastructure | QSI capital + empowered sporting advisor (Luis Campos) |
| **Systems** | Hard | Unlimited transfer budget for marquee names | Recruitment for young, system-fit talent; no single dominant earner |
| **Shared Values** | Soft | Individual stars; commercial brand-building | "Collective over individual" |
| **Style** | Soft | Managers deferential to superstars | Luis Enrique's demanding, system-first management |
| **Staff** | Soft | A collection of names | A young, coherent team (Dembélé, Doué, Kvaratskhelia, João Neves) |
| **Skills** | Soft | Individual star power | High-pressing, positional, collective play |

## The hard S's were never the problem

For a decade PSG maxed out the three elements money can buy. **Strategy** was explicit and unchanging: win the Champions League. **Structure** was elite — QSI's capital, a world-class training centre, global commercial reach. **Systems** were effectively unlimited: PSG could and did outbid almost anyone for almost any player. If performance came from the hard S's, PSG would have won the Champions League five times over. It didn't win once. That is the diagnostic clue 7S is built to surface — when the hard elements are maxed and the result still fails, the misalignment is in the soft S's.

## The soft S's are where it was lost — and won

**Shared Values** under MNM optimised for individual stardom and the commercial brand that came with it; the dressing-room culture was a set of individuals, not a collective. **Style** suffered for it: a succession of managers couldn't impose a coherent system on superstars who expected deference. **Staff** was a collection of the most marketable names rather than a balanced team. And **Skills** — the organisation's actual capabilities on the pitch — were individual brilliance rather than collective pressing and positional play. Four soft elements, all misaligned with the hard strategy of winning Europe.

The reset flipped all four together. Sporting advisor **Luis Campos** changed Staff and Systems — recruiting younger, system-fit talent (Désiré Doué, João Neves, Bradley Barcola, Willian Pacho, Khvicha Kvaratskhelia) over marquee names. Head coach **Luis Enrique** changed Style and Skills — a demanding, high-pressing, positional system with the authority to bench or sell anyone. Together they reset Shared Values from "individual stars" to "the collective." Crucially, [QSI let Mbappé leave](https://en.wikipedia.org/wiki/2025_UEFA_Champions_League_final) and backed the approach through a wobbly league phase rather than reversing it. The hard S's never moved; the soft realignment delivered the trophy.

## The Soft-S Breakthrough

Here is the synthesis worth keeping. McKinsey's original argument in the 7S model is that the *soft* S's — Shared Values, Style, Staff, Skills — are harder to change and more decisive than the hard ones, which is exactly why most transformations that only move the hard S's fail. PSG is an unusually clean proof, because it held the hard S's at maximum for ten years. With Strategy, Structure, and Systems effectively constant, the only variable that changed between "richest team without the trophy" and "European champion" was soft alignment. **The lesson isn't "stars don't win" — it's that an organisation whose soft elements contradict its strategy will fail no matter how much it spends on the hard ones.** Most companies read 7S and rush to fix Structure and Systems because those are buyable; PSG is the reminder that the soft S's are the ones that decide.

## Key takeaway

McKinsey 7S turns PSG's decade of expensive failure and sudden success into one coherent story. The hard elements — Strategy, Structure, Systems — were elite throughout and explain nothing about the change, because they didn't change. The soft elements — Shared Values, Style, Staff, Skills — were misaligned with the strategy of winning Europe under the galácticos, and were realigned, all at once, under Luis Enrique and Luis Campos. The result was a first Champions League, won 5-0 by a team of largely young players. For any organisation tempted to fix performance by spending on the buyable elements, PSG is the cautionary and instructive case: alignment beats accumulation, and the soft S's are where alignment is won or lost.

## Want to go deeper

This analysis is part of the [World Cup 2026 strategy series](/series/world-cup-2026). New to the model? Start with [the McKinsey 7S framework: hard and soft elements](/academy/mckinsey-7s-framework-hard-soft-elements), read more about the [McKinsey 7S framework](/frameworks/mckinsey7s), or browse [strategy framework examples applied to real companies](/examples). For the same model applied to very different organisations, see the [Apple McKinsey 7S analysis 2026](/examples/apple-mckinsey-7s-analysis-2026) and the [SpaceX–Cursor McKinsey 7S integration analysis 2026](/examples/spacex-cursor-mckinsey-7s-2026) — the latter applies 7S to a live $60B acquisition where all the risk sits in the soft S's. For the rest of the football series, see the [Real Madrid Porter's Five Forces](/examples/real-madrid-porters-five-forces-2026), the [Manchester City Ansoff Matrix](/examples/manchester-city-ansoff-matrix-2026), and the [FC Barcelona BCG Matrix](/examples/barcelona-bcg-matrix-2026). To run a 7S analysis on an organisation you're tracking, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each element.

For PSG's SWOT counterpart, see our sister site [SWOTPal's PSG SWOT analysis](https://swotpal.com/examples/psg-swot-analysis?utm_source=frameworklist&utm_medium=referral&utm_campaign=mckinsey7s-psg) — a dedicated AI SWOT tool, free for the basic workflow.

---

### Real Madrid Porter's Five Forces: the Super League play
URL: https://frameworklist.com/examples/real-madrid-porters-five-forces-2026
> A Porter's Five Forces analysis of Real Madrid's business model — why the world's richest club (€1.185bn) is rebuilding the Bernabéu and suing UEFA, read as a textbook industry-structure play.

This is part of our [World Cup 2026 strategy series](/series/world-cup-2026) — the business of football read through strategy frameworks. The [FIFA](/examples/fifa-ansoff-matrix-2026) and [Manchester City](/examples/manchester-city-ansoff-matrix-2026) pieces used the Ansoff Matrix to read *growth*. Real Madrid needs a different lens, because its defining moves aren't about growth — they're about **industry structure**. For that, Porter's Five Forces is the tool.

Here's the puzzle Five Forces solves: Real Madrid is the [world's highest-revenue football club, a record €1.185bn in 2024-25](https://www.managingmadrid.com/2025/7/17/24469539/real-madrid-reports-record-1-185-billion-in-revenue-provides-update-bernabeu-renovation-financial) — and yet it spent €1.347bn rebuilding its stadium and is suing UEFA for billions to break away from the Champions League. Why would the richest club in the sport try to blow up the competition it keeps winning? Because the forces shaping its industry are turning against it.

## Position being analyzed

Real Madrid sits at the top of European football's revenue table — the first club to pass €1bn, now at €1.185bn — but it competes in an industry whose economics have shifted underneath the traditional elite. State-backed owners have uncoupled spending from revenue; UEFA controls access to the sport's most lucrative competition; and fans' attention is increasingly contested by everything else on a screen. Real Madrid's two signature strategies — the **Super League** legal campaign and the **Santiago Bernabéu** transformation — only make sense as responses to that structure. Porter's Five Forces is how you see the structure.

## Real Madrid's Five Forces Scorecard

The citable core: each force scored from Real Madrid's seat, with the direction it's moving and the club's countermove.

| Force | Strength | Direction | Real Madrid's countermove |
|---|---|---|---|
| **Threat of new entrants** | High | ↑ Rising | Super League with controlled entry — restore a barrier state capital tore down |
| **Supplier power — players/agents** | High | → Steady | Financial discipline; signing marquee players (e.g. Mbappé) on free transfers |
| **Supplier power — UEFA (competition)** | Very high | ↑ Contested | Super League / A22 "Unify League" to disintermediate UEFA; €4.5bn lawsuits |
| **Bargaining power of buyers (broadcasters/fans)** | Medium-High | ↑ Consolidating | Bernabéu = owned, year-round revenue independent of broadcast cycle |
| **Threat of substitutes (other entertainment)** | Medium | ↑ Rising | Bernabéu as a destination venue (concerts, NFL, 365 events) competing for attention |
| **Competitive rivalry** | High | → Intense | Sporting investment + commercial scale; reshape the competition itself |

## Threat of new entrants: the force that started it all

The historic moat of a club like Real Madrid was financial: more revenue bought better players, which won more, which earned more revenue. State-backed ownership broke that loop. Manchester City, PSG, Newcastle, and the Saudi Pro League clubs inject capital that is *uncoupled* from commercial revenue — so a new entrant can outspend a self-sustaining club regardless of how big its business is. That single change is the most important fact about Real Madrid's industry, because it neutralised the advantage being the richest club used to confer. Almost everything else Real Madrid does is downstream of trying to rebuild that barrier to entry.

## Supplier power: players, agents, and UEFA

Two suppliers sit between Real Madrid and its profits. The first is the **player-and-agent** complex, which captures value through wages and transfer fees; Real Madrid manages it with relative discipline, often refusing the top of the market and signing marquee names on free transfers when it can. The second supplier is the one most analyses miss: **UEFA itself.** UEFA is the monopoly supplier of the Champions League — the single most valuable input to an elite club's business, because it generates the premium broadcast revenue. A supplier with monopoly control over your most valuable input is, in Porter's terms, the force that most compresses your margins. That framing is the key to the Super League.

## The Super League is a Five Forces play

Read as sport, the Super League looks like a greedy breakaway. Read through Porter's, it is a rational attack on supplier power. The Super League — and A22's revised **"Unify League"** with a free **"Unify"** streaming platform — is an attempt to disintermediate UEFA: let the founding clubs control the competition format and capture broadcast value directly, rather than receive a UEFA-distributed share. The legal campaign backs it: after the [Madrid Provincial Court dismissed UEFA's appeals in October 2025](https://www.espn.com/soccer/story/_/id/46770438/madrid-seek-compensation-uefa-super-league-ruling) — upholding that UEFA breached EU competition law by blocking the breakaway — [Real Madrid and A22 launched claims totalling roughly €4.5bn](https://www.goal.com/en-us/lists/real-madrid-and-super-league-launch-eur4-5bn-lawsuits-against-uefa-as-president-aleksander-ceferin-told-to-approve-new-competition-after-eu-court-ruling/blt851d71dde38d3462). Whether the league ever launches almost doesn't matter to the Five Forces reading: the campaign itself is a bargaining move to weaken a monopoly supplier's grip. Notably, Real Madrid is now close to the last elite holdout still pushing it — which tells you how much *this specific club* feels the supplier squeeze.

## Buyers and substitutes: why the Bernabéu

The other two forces explain the stadium. **Buyers** — broadcasters above all — are consolidating, and a club dependent on the next TV deal is exposed every cycle. **Substitutes** — streaming, other sports, esports, social media — compete for the same finite resource: fan attention. The €1.347bn [Bernabéu rebuild](https://www.iqmagazine.com/2025/08/real-madrids-bernabeu-stadium-eyes-concert-return/) is the answer to both. The renovated venue generates roughly **€1m per day**, is built for up to 365 events a year, and hosted an **NFL game in November 2025**; it now drives an estimated 29–34% of total club revenue, against the old stadium's €150–200m a year from all sources. In Porter's terms, that converts a club exposed to powerful buyers into a diversified entertainment venue that competes against substitutes on its own terms — owned revenue that doesn't depend on a broadcaster's contract or on Saturday's result.

## Key takeaway

Porter's Five Forces reframes Real Madrid's two most controversial strategies as one coherent response to industry structure. The threat of new entrants — state capital uncoupled from revenue — destroyed the financial moat that being the richest club used to provide. The supplier power of UEFA compresses the value the club can capture from the competition it dominates. Real Madrid's answers map cleanly onto the forces: the **Super League** attacks supplier power and tries to rebuild a barrier to entry; the **Bernabéu** neutralises buyer power and meets substitutes head-on with owned, year-round revenue. You don't have to like the Super League to see that it isn't irrational — it's a textbook attempt to restructure the two forces squeezing the business hardest. The open question Porter's leaves on the table: an industry's structure is hard to change unilaterally, and Real Madrid is increasingly trying to change it alone.

## Want to go deeper

This analysis is part of the [World Cup 2026 strategy series](/series/world-cup-2026). New to the model? Start with [Porter's Five Forces: a beginner's guide](/academy/porters-five-forces-beginners-guide), read more about the [Porter's Five Forces framework](/frameworks/fiveforces), or browse [strategy framework examples applied to real companies](/examples). For the same lens on different industries, see [Netflix through Porter's Five Forces](/examples/netflix-porters-five-forces). For the football business read through other lenses, see the [Manchester City Ansoff Matrix](/examples/manchester-city-ansoff-matrix-2026), the [FIFA Ansoff Matrix 2026](/examples/fifa-ansoff-matrix-2026), the [PSG McKinsey 7S analysis](/examples/psg-mckinsey-7s-2026), and — for Barça's own financial puzzle — the [FC Barcelona BCG Matrix](/examples/barcelona-bcg-matrix-2026). To run a Five Forces analysis on an organisation you're tracking, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each force.

For Real Madrid's SWOT counterpart, see our sister site [SWOTPal's Real Madrid SWOT analysis](https://swotpal.com/examples/real-madrid-swot-analysis?utm_source=frameworklist&utm_medium=referral&utm_campaign=fiveforces-realmadrid) — a dedicated AI SWOT tool, free for the basic workflow.

---

### RICE prioritization on a real SaaS team's Q3 backlog
URL: https://frameworklist.com/examples/rice-saas-q3-backlog
> 12 candidate features, scored honestly, ranked by RICE. The surprising losers and one feature the team almost killed that scored at the top.

A B2B SaaS team running their Q3 planning. 12 candidate features on the backlog, capacity for roughly 5. The team had been arguing about three favorites for two weeks. They ran RICE on a Tuesday afternoon — by 5pm the ranking was settled and the planning meeting on Thursday took 20 minutes instead of two hours.

> If you need the formula and scoring rules before reading this example, see [RICE score calculator: the formula with 3 worked examples](/academy/rice-score-calculator-with-examples).

> **Score your own backlog on your phone** — [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=rice-backlog-example-hero) ships the RICE calculator: enter Reach, Impact, Confidence, and Effort, get the ranked list. Free to start.

## Setup

- Product: workflow automation for mid-market customer success teams
- Active accounts: 1,800
- Team capacity: ~12 engineer-months for Q3 features (after carrying ops and bugs)
- Scoring scale: Reach = customers affected/quarter; Impact = 0.25/0.5/1/2/3; Confidence = %; Effort = engineer-months

## The candidates and scores

| Feature | Reach | Impact | Conf | Effort | RICE |
|---|---|---|---|---|---|
| Bulk-edit account fields | 1,400 | 1 | 80% | 1.5 | **747** |
| Slack notification routing | 900 | 2 | 70% | 2 | **630** |
| Custom dashboard widgets | 600 | 2 | 60% | 3 | **240** |
| New onboarding wizard for trial users | 1,200 | 0.5 | 90% | 2 | **270** |
| Salesforce 2-way sync v2 | 400 | 3 | 60% | 4 | **180** |
| Mobile push notifications | 1,800 | 0.5 | 70% | 1.5 | **420** |
| Account merge tool | 300 | 1 | 90% | 1 | **270** |
| Inline AI summaries on accounts | 1,800 | 1 | 40% | 2.5 | **288** |
| Multi-workspace support | 200 | 3 | 80% | 6 | **80** |
| Auto-renew reminder emails | 1,600 | 0.5 | 90% | 0.5 | **1,440** |
| Custom report builder | 500 | 2 | 50% | 4 | **125** |
| Real-time activity feed | 1,800 | 1 | 60% | 3 | **360** |

Total effort if everything shipped: 31 engineer-months. Available: 12.

## The ranked top 5

By RICE:

1. **Auto-renew reminder emails** — 1,440 (the surprise winner)
2. **Bulk-edit account fields** — 747
3. **Slack notification routing** — 630
4. **Mobile push notifications** — 420
5. **Real-time activity feed** — 360

Total effort for top 5: **8.5 engineer-months**. Fits with room to spare.

## What was surprising

**Auto-renew reminders almost didn't make the candidate list.** A product manager had floated it casually; nobody pushed hard for it. When the team computed RICE honestly — affects almost every customer, modest per-customer impact, very high confidence (we know exactly what this does), and tiny effort (0.5 eng-month) — it landed at 1,440. The Effort being so low and Reach so high produced the disproportionate score the formula was designed to surface.

**Multi-workspace support, the founder's favorite, ranked dead last.** Reach was small (only enterprise customers needed it), Effort was huge (6 eng-months), and the resulting RICE score of 80 was honest. The team would have shipped it on intuition; the scoring forced an explicit conversation about whether enterprise-tier expansion justified the trade. They concluded: not this quarter. Revisit when 3+ enterprise prospects ask for it.

**Inline AI summaries** had high Reach × Impact (1,800 × 1) but low Confidence (40%) because the team had no evidence summaries would actually be read. The Confidence multiplier dropped it from a potential 1,800 to 288. Penalty for speculation working as intended.

## The "we cheated" check

After the scoring, the lead asked the question that prevents most RICE abuse: *"are any of these scores driven by what we wanted the answer to be?"*

One score got revised: Salesforce sync v2 (Confidence raised from 60% → 80%) was an attempt by an engineer to push the score up. The team caught it because Salesforce sync v2 had failed user testing twice before — 60% confidence was the right number. After the revision back, Salesforce sync stayed out of the top 5.

## What this teaches

- **The formula's denominator (Effort) is what produces non-obvious winners.** A small Effort with even modest other inputs jumps to the top. Most teams under-weight this.
- **Confidence is the term that penalizes wishful thinking.** Without honest confidence numbers, the score becomes "what we hope is true × what we wish it cost".
- **Surprise winners and surprise losers are signals.** When RICE produces a ranking that conflicts with team intuition, both deserve a serious look. Sometimes the intuition was right and the scoring is off; more often the scoring is honest and the intuition was anchored on irrelevant features.

## Run your own

The full method is in the [Academy guide →](/academy/rice-prioritization-framework). Open the [framework page](/frameworks/rice) for the catalog entry, or [start a canvas](/sign-in) to score your own backlog.

> **Want to score your own backlog on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=rice-backlog-example) ships the RICE calculator — enter Reach, Impact, Confidence, and Effort, get the ranked list. Free to start.

---

### SpaceX BCG Matrix Analysis 2026 (Post-IPO Portfolio)
URL: https://frameworklist.com/examples/spacex-bcg-matrix-2026
> A worked BCG Growth-Share Matrix of SpaceX's business segments after its June 2026 IPO — Starlink as the Star, Falcon 9 launch as the Cash Cow, Starship as the Question Mark, and what the near-empty Dogs quadrant reveals.

On June 12, 2026, SpaceX completed the largest IPO in US history — pricing at $135 a share for a valuation near $1.75 trillion, opening at $150, and closing its first day up 19% with a market capitalization above $2 trillion. It joins the Nasdaq 100 on July 7. For the first time, public investors own a slice of a company that used to disclose almost nothing — and the question every new shareholder is now asking is the one the [BCG Growth-Share Matrix](/frameworks/bcg) was built to answer: what are you actually buying, segment by segment, and which parts are funding which?

## Position being analyzed

SpaceX in mid-2026 is a ~$18.7B-revenue company (2025, up 43% year over year) with three businesses that could not be more different in their BCG coordinates: a consumer-broadband rocket ship (Starlink), a mature launch monopoly (Falcon 9), and a moonshot that is literally a moonshot (Starship). The strategic question the matrix addresses: is the portfolio balanced so that the cash-generating unit can fund the growth units long enough for the biggest bet to pay off?

| Metric | Value | Direction vs. 12 months ago |
|---|---|---|
| Total revenue (2025) | $18.7B | ▲ up 43% |
| Starlink revenue (2025) | $11.4B (61% of total) | ▲ up 48% |
| Starlink operating profit (2025) | $4.4B | ▲ up (first full profitable year) |
| Launch services revenue (2025) | ~$4.1B | ▲ up ~8% |
| Starlink subscribers (mid-2026) | 12M+ across 160+ countries | ▲ up from ~7M |
| IPO valuation (June 12, 2026) | ~$1.75T (topped $2T day one) | ▲ up from $350B (Dec 2024) |

## The four quadrants

| Quadrant | Definition | SpaceX 2026 entries |
|---|---|---|
| **Stars** | High share, high growth | Starlink consumer & enterprise broadband |
| **Cash Cows** | High share, low growth | Falcon 9 / Falcon Heavy commercial launch services |
| **Question Marks** | Low/uncertain share, high growth | Starship, Starshield (defense), direct-to-cell |
| **Dogs** | Low share, low growth | Falcon 1 (retired) — quadrant otherwise empty |

## Stars: Starlink

Starlink is the Star, and after the IPO it is the reason for most of the valuation. Three pieces of evidence place it in the Star quadrant unambiguously:

1. **Market growth rate** — Starlink revenue grew 48% year over year to $11.4B in 2025, and the subscriber base roughly doubled to 12M+ by mid-2026, adding ~4.6M customers in a single year. That is high growth by any threshold.
2. **Relative market share** — Starlink is the dominant provider of low-earth-orbit satellite broadband, a market it effectively created and where competitors (Amazon's Kuiper, OneWeb) are years behind on constellation scale.
3. **Reinvestment intensity** — every dollar of Starlink's $4.4B operating profit is being plowed back into V3 satellites, direct-to-cell, and Starship (its cheapest future deployment vehicle). That is textbook Star behavior; Cash Cows don't reinvest at this rate.

What makes this Star unusual within BCG's framework: it is vertically fused to the Cash Cow. Starlink only works because Falcon 9 launches its own satellites at near-cost. The matrix can't price that internal subsidy, but the analyst should note it — Starlink's margins are partly a function of owning the launch vehicle.

## Cash Cows: Falcon 9 launch services

Falcon 9 (with Falcon Heavy) is the canonical Cash Cow:

- **Market growth**: commercial launch grows in the low single digits per year; SpaceX's launch revenue rose only ~8% in 2025.
- **Relative share**: roughly 90% of the commercial launch market in early 2025 — a near-monopoly.
- **Margin**: reusable boosters make each flight structurally cheaper than any competitor's, so the segment throws off cash. This is the long-run payoff of the materials-cost gap Musk described in 2012 (see [first principles thinking examples](/academy/first-principles-thinking-with-examples)).
- **Reinvestment requirement**: low — Falcon 9 is a mature, proven vehicle.

The discipline question for a Cash Cow is not "is it growing?" — it isn't, and that's fine — but "is management harvesting it correctly without starving it?" SpaceX flies Falcon 9 at record cadence while pouring the proceeds into Starship and Starlink. Classic Cash Cow management: milk the monopoly, fund the future.

## Question Marks: Starship, Starshield, direct-to-cell

This is where the portfolio gets interesting and where the BCG lens earns its keep.

**Starship**: the fully reusable heavy-lift vehicle. The addressable markets — mass satellite deployment, lunar and Mars cargo, national-security heavy lift, eventually point-to-point transport — are enormous and high-growth. But SpaceX's *revenue* share of those markets is effectively zero today, and the vehicle is unproven: 12 flights, 7 successes, 5 failures, with the V3 variant only debuting in May 2026. Starship is the highest-burn Question Mark in the portfolio. BCG's rule is binary — commit fully or divest — and SpaceX has committed harder to Starship than to anything in its history.

**Starshield (defense/government)**: a high-growth government market where SpaceX's share is building fast but not yet dominant against incumbent defense primes. A Question Mark trending toward Star.

**Direct-to-cell**: high-growth market (satellite-to-phone connectivity), share still forming as carrier partnerships scale. Rides Starlink's infrastructure, which shortens its path to Star status.

## Dogs: notably empty

A healthy BCG portfolio usually carries a few Dogs that should be divested. SpaceX's Dogs quadrant is notable for what's *not* there. Falcon 1 — the original rocket, last flown in 2009 — is the textbook Dog: zero current share, zero growth, fully retired. And that's the pattern: SpaceX retires losers rather than nursing them. The absence of Dogs is a quiet leading indicator of portfolio discipline that most large industrial companies lack.

## The SpaceX Portfolio Flywheel

Here is the named insight the matrix produces — the thing worth quoting. Read SpaceX's four quadrants not as a static snapshot but as a **flywheel**, because each quadrant funds the next:

| Stage | Quadrant | Role in the flywheel |
|---|---|---|
| 1 | **Falcon 9** (Cash Cow) | Generates cash from a ~90%-share launch monopoly and launches Starlink's satellites at near-cost |
| 2 | **Starlink** (Star) | Converts cheap launch into $4.4B operating profit; becomes the company's primary cash engine |
| 3 | **Starship** (Question Mark) | Funded by 1 and 2; once proven, deploys Starlink V3 at a fraction of Falcon 9's cost |
| 4 | back to **Starlink** | Cheaper deployment widens Starlink's margin and lead — compounding the Star |

The strategic point most single-segment takes on SpaceX miss: the Question Mark isn't a side bet the Cash Cow merely tolerates — Starship is the mechanism that makes the Star cheaper to scale. That circularity is why SpaceX can rationally out-invest every competitor in an unproven rocket. It's also the risk the matrix surfaces: if Starship's failure rate stays high and the flywheel's stage 3 stalls, the whole loop slows at once. That is the strategic clock public investors are now watching.

## Key takeaway

The BCG matrix on SpaceX in 2026 says: this is one of the most *balanced* portfolios in large-cap tech, not the reckless moonshot the headlines imply. A dominant Cash Cow (Falcon 9) funds a compounding Star (Starlink) that is already profitable, while a single concentrated Question Mark (Starship) carries the long-term upside — and there are no Dogs draining cash. The risk the model highlights is not imbalance; it's *dependency* — every quadrant is fused to the others through the launch vehicle, so a sustained Starship setback would ripple across the whole matrix rather than being contained to one bet. Worth re-running this analysis every quarter now that the numbers are public.

## Want to go deeper

New to the model? Read [BCG Matrix Analysis: The Four Quadrants Explained](/academy/bcg-matrix-analysis-explained) for the full methodology and the Cash-Cow Dependency Test — which SpaceX's flywheel passes and most portfolios fail. Or see the matrix applied to a very different portfolio in the [Nvidia BCG Matrix Analysis 2026](/examples/nvidia-bcg-matrix), where one Star so dominates that the matrix tips out of balance — the opposite of SpaceX's problem. New to the model? Start with [Ansoff Matrix vs BCG Matrix](/compare/ansoff-matrix-vs-bcg-matrix) to see how a portfolio diagnosis (BCG) hands off to a growth prescription (Ansoff), or [BCG Matrix vs GE-McKinsey Matrix](/compare/bcg-matrix-vs-ge-mckinsey-matrix) for when a portfolio outgrows BCG's four boxes and needs the nine-box grid. For SpaceX through a strategy-and-culture lens after its high-profile Cursor integration, see the [SpaceX × Cursor McKinsey 7S analysis](/examples/spacex-cursor-mckinsey-7s-2026). For another 2026 mega-IPO read through a different lens, the [Anthropic Business Model Canvas (2026 IPO edition)](/examples/anthropic-business-model-canvas) maps the AI lab's nine blocks against its confidential S-1 numbers. For the same four quadrants applied to a portfolio whose one Cash Cow (Search) is being actively contested — the mirror risk to SpaceX's fused-flywheel dependency — see the [Alphabet BCG Matrix 2026](/examples/alphabet-bcg-matrix-2026), written going into its July 22 Q2 earnings. To run a BCG on a company you care about, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) walks you through all four quadrants with AI assistance.

---

### SpaceX–Cursor Acquisition: A McKinsey 7S Integration Analysis (2026)
URL: https://frameworklist.com/examples/spacex-cursor-mckinsey-7s-2026
> A McKinsey 7S analysis of SpaceX's $60B all-stock acquisition of Cursor (Anysphere) — why the hard S's (Strategy, Structure, Systems) line up while the soft S's (Staff, Style, Shared Values) carry all the integration risk after xAI lost all 11 co-founders.

![Photograph of rows of servers in a data center, evoking the Colossus supercompute infrastructure at the center of the SpaceX–Cursor deal](https://images.unsplash.com/photo-1558494949-ef010cbdcc31?auto=format&fit=crop&w=1600&q=80)

On June 16, 2026 — four days after the largest IPO in history — SpaceX agreed to acquire Cursor (the AI-coding company Anysphere) for **$60 billion in all-stock**, the biggest acquisition of a venture-backed startup ever, at roughly **15x revenue**. SpaceX's own framing to investors is unusually honest about what it is buying: not cash flows, but **data, compute, and talent** to let its xAI division catch the frontier AI labs. That framing is also why a financial model is the wrong tool to judge the deal — and why [McKinsey 7S](/frameworks/mckinsey7s) is the right one.

Run through 7S, the SpaceX–Cursor deal is a clean split. The three **hard S's** (Strategy, Structure, Systems) are aligned and fully funded. All of the risk lives in the four **soft S's** (Shared Values, Skills, Style, Staff) — and the central irony is that SpaceX is buying *talent* into a division that just watched **all 11 of its own xAI co-founders walk out** by the end of March 2026.

## Position being analyzed

SpaceX listed on the Nasdaq on June 12, 2026 at $135 per share, added roughly $1 trillion in market cap within days, and announced the Cursor acquisition four days later — covering the entire $60B with less than a tenth of those gains. The deal had been pre-structured in April 2026 as an option: buy Cursor for $60B in stock, or pay a $10B break-up fee. The strategic question 7S helps with: now that the money is trivially handled, is the *combined organization* configured to actually capture the data, compute, and talent value the deal was sold on?

| Deal fact | Value | Note |
|---|---|---|
| Headline price | $60B all-stock | Largest VC-backed-startup acquisition ever |
| Revenue multiple | ~15x | Cursor ~$4B annualized revenue in under 4 years |
| Enterprise revenue share | ~$2.6B of ~$4B | ~65% is enterprise B2B contracts |
| Break-up fee (April structure) | $10B | Protected the transaction, not the retention |
| Expected close | Q3 2026 | Subject to regulatory approval |
| xAI co-founders remaining | 0 of 11 | All departed by end of March 2026 |
| Compute on offer to Cursor | xAI Colossus supercluster | The strongest hard-S argument for the deal |

## McKinsey 7S applied

The 7S model splits an organization into **hard S's** (Strategy, Structure, Systems — concrete, top-down-controllable) and **soft S's** (Shared Values, Skills, Style, Staff — cultural, slow to shift). In M&A its diagnostic value is to compare how the two organizations differ across all seven and surface where integration will actually break — which, the [framework's M&A literature](https://www.hackingthecaseinterview.com/pages/mckinsey-7s-framework) consistently finds, is in the soft S's. For the underlying hard/soft split, see the [McKinsey 7S Framework: Hard and Soft Elements](/academy/mckinsey-7s-framework-hard-soft-elements) explainer.

### Strategy (Hard) — vertical AI integration to catch the frontier

The Strategy is coherent and explicit: bolt a leading AI-coding product onto xAI so SpaceX's AI division can close the gap with OpenAI, Anthropic, and Google DeepMind. SpaceX pitched IPO investors a ~$28 trillion total addressable market, nearly all of it AI. Cursor is the enterprise wedge — a real product with real revenue, not a research bet. As Strategy, this is internally consistent: own the developer surface, feed the model, monetize the enterprise. The hard S aligns.

### Structure (Hard) — three layers, but legible

The org design is a clean three-layer stack: Cursor sits under xAI, which merged into SpaceX earlier in 2026. That is more nesting than a standalone acquisition, but it is legible — there is no ambiguity about reporting lines or who owns the AI mandate. The Structure question 7S raises is decision rights: how much autonomy Cursor retains versus how fast it gets absorbed into xAI's operating model. But the structure itself is not the risk; it is buildable.

### Systems (Hard) — the strongest argument for the deal

This is where the deal's logic is most defensible. Cursor's coding interactions become **training data for Grok** — a proprietary, hard-to-replicate data flywheel. In return, Cursor gains access to xAI's **Colossus supercluster**, compute it could never have funded as an independent company raising at a $50B valuation. The Systems fit is genuine mutual reinforcement: data up, compute down. If you only looked at the hard S's, this deal is excellent.

### Shared Values (Soft) — a developer-trust brand under a controversy-prone parent

Here the alignment breaks. Cursor's enterprise customers — roughly **65% of its revenue** — bought a calm, trustworthy developer tool. The acquirer's parent brand carries reputational baggage: xAI faced early-2026 controversies including non-consensual deepfake content and a California Attorney General cease-and-desist. For a consumer product, a Shared Values clash is cosmetic. For a company where two-thirds of revenue is annually-renewing enterprise contracts, vendor brand risk is a procurement and security-review line item. The values that sold Cursor to its customers and the values associated with its new parent are not the same values.

### Skills (Soft) — real, but only if the people stay

Cursor's Skills are exactly what SpaceX says it wants: frontier-grade applied AI engineering, product velocity, enterprise developer experience. The 7S caution is that Skills are not an asset on a balance sheet — they walk out the door in people. Acquired Skills are only retained if the Staff carrying them stays, which makes the next element the load-bearing one.

### Style (Soft) — Musk's hardcore tempo vs an enterprise-tools cadence

Cursor built a sustainable, enterprise-grade product on a measured cadence. Musk's operating Style is famously hardcore, high-tempo, and high-churn. Elon Musk himself said xAI "was not built right the first time around" — a candid admission that the Style has already produced one organizational reset. Style is the hardest S to change, and the acquirer's Style is the one Cursor's team will be asked to absorb, not the reverse.

### Staff (Soft) — the element the whole deal turns on

SpaceX states it is **buying talent**. Yet the division doing the buying lost **all 11 of its own xAI co-founders** by the end of March 2026. That is the most concrete misalignment 7S can surface: an acquirer trying to backfill a founder exodus by acquiring a new team — that will join the same culture the original founders left. The $10B break-up fee protected the transaction; nothing protects post-close retention. Staff is where the gap between the deal's thesis ("we are buying talent") and its execution risk ("can we keep talent") is widest.

## The SpaceX–Cursor 7S Integration Risk Scorecard

The citable core. Each element, scored aligned or at-risk for *this* deal, with the single variable that flips it.

| Element | Type | Fit | Key risk | What flips it |
|---|---|---|---|---|
| **Strategy** | Hard | ✅ Aligned | Frontier labs out-execute | Grok closing the model gap |
| **Structure** | Hard | ✅ Aligned | Slow absorption blurs decision rights | Clear Cursor autonomy charter |
| **Systems** | Hard | ✅ Aligned (strongest) | Data/compute integration stalls | Cursor → Grok data pipeline shipping |
| **Shared Values** | Soft | ⚠️ At risk | Enterprise customers flee parent-brand risk | xAI brand-safety cleanup |
| **Skills** | Soft | ⚠️ Contingent | Skills leave with people | Retention of Cursor's core engineers |
| **Style** | Soft | ⚠️ At risk | Hardcore tempo repels enterprise team | A protected "carve-out" operating mode |
| **Staff** | Soft | 🔴 Highest risk | Acquihire into a founder-exodus culture | 12-month Cursor leadership retention |

Three hard S's aligned; four soft S's ranging from contingent to critical. This is the canonical 7S shape — the buyable elements are fine; the deal will be decided by the unbuyable ones.

## The Acquihire Paradox

Here is the synthesis worth keeping. SpaceX's stated rationale is that it is buying **data, compute, and talent**. The first two are hard S's and are essentially solved on day one — the data flows and the Colossus compute is real. The third, talent, is a soft S, and it is governed by a paradox the deal cannot buy its way out of: **you cannot retain acquired talent with a culture that expelled your own founders.** xAI lost all 11 of its co-founders before the ink on this deal was dry. Cursor's engineers are being asked to do the job those founders left — inside the same Style and Shared Values. The Acquihire Paradox is that the more a deal's value depends on retaining acquired people, the more the acquirer's *own* retention track record becomes the binding constraint. SpaceX is paying a 15x multiple for an asset whose value can quietly walk out the door, and its recent history says that door is open. Most M&A post-mortems blame "culture" in hindsight; 7S lets you name the specific soft-S failure mode *before* close — and here it is named: Staff retention against a hostile Style.

## Counter-argument

The bull case: compute and data are the real moat, and those transfer on day one regardless of who stays. Even if half of Cursor's team leaves, SpaceX keeps the product, the user base, the proprietary coding data feeding Grok, and a flagship enterprise wedge — for a price that cost less than a tenth of its post-IPO market-cap gain. On that view the talent is upside, not the thesis, and the Staff risk is overstated.

7S doesn't refute this — it sharpens the question. If the data and compute are the real assets, then management should *say so* and stop pricing the deal on talent it has a poor record of keeping. The framework's contribution is to force the honest version: which soft S's must hold for the *stated* thesis to be true? If the answer is "none, the hard S's carry it," then the deal is cheaper than it looks. If the answer is "talent retention," then a 15x multiple is exposed to the one element SpaceX has most recently fumbled.

## Signals to watch (next 12 months)

| Signal | Element | Why it matters |
|---|---|---|
| Cursor founding/leadership team still in place at +12 months | Staff | The cleanest single retention indicator |
| Enterprise logo churn / renewal rate post-close | Shared Values | Whether parent-brand risk costs revenue |
| Cursor → Grok data pipeline shipping in product | Systems | The hard-S thesis actually executing |
| A published "Cursor operates independently" charter | Structure + Style | Whether the carve-out protects the culture |
| xAI brand-safety remediation (regulatory closure) | Shared Values | Whether enterprise procurement fears ease |
| Net engineering headcount in the Cursor unit | Skills + Staff | Whether acquired Skills are retained or replaced |

## Key takeaway

The SpaceX–Cursor McKinsey 7S story is that the hard S's (Strategy, Structure, Systems) are aligned and fully funded — the money, the org design, and the data/compute fit are the *easy* part — while all four soft S's range from contingent to critical, with Staff the highest risk of all. The deal was sold on buying talent, but it is being executed by a division that just lost its entire founding team, and ~65% of the acquired revenue sits with enterprise customers who care about the acquirer's brand. The Acquihire Paradox names the trap: talent-driven acquisitions are hostage to the acquirer's own retention culture, and SpaceX's is, by Musk's own admission, freshly reset.

If you only track one variable, track whether Cursor's leadership is still in place twelve months after close. That number is the cleanest single indicator of whether the 7S soft-S alignment the deal's thesis requires is actually holding.

> Want to run a 7S analysis on a deal or org you're tracking? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each of the seven elements.

*Cover photo: [Taylor Vick on Unsplash](https://unsplash.com/photos/M5tzZtFCOfs).*

## Related

- [McKinsey 7S Framework: Hard and Soft Elements](/academy/mckinsey-7s-framework-hard-soft-elements) — the hard/soft split + how to score each element
- [McKinsey 7S framework](/frameworks/mckinsey7s) — the seven elements and when to use them
- [Apple McKinsey 7S Analysis 2026](/examples/apple-mckinsey-7s-analysis-2026) — 7S on a single company's internal AI alignment
- [PSG McKinsey 7S: the post-Mbappé team-first reset](/examples/psg-mckinsey-7s-2026) — the cleanest soft-S-vs-hard-S case study
- [Tesla VRIO Analysis 2026](/examples/tesla-vrio-analysis-2026) — a resource-based lens on another Musk company
- [Microsoft Porter's Five Forces Analysis 2026](/examples/microsoft-porters-five-forces-analysis-2026) — industry-structure lens on the AI race for contrast
- [SpaceX BCG Matrix Analysis 2026](/examples/spacex-bcg-matrix-2026) — the same company's business portfolio (Starlink / Falcon 9 / Starship) after its record June 2026 IPO

---

### SWOT analysis of Tesla in 2024
URL: https://frameworklist.com/examples/swot-tesla-2024
> A worked SWOT covering Tesla's position heading into 2024 — the EV manufacturing lead, the Cybertruck rollout, China headwinds, and Robotaxi vapor.

> **Need to actually run a SWOT?** [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-redirect) is the dedicated AI SWOT tool — free, no signup. The worked Tesla analysis below shows the rigor it helps you reach.

A SWOT only earns its keep when each entry is sharp and specific. The version below covers Tesla's strategic position at the start of 2024 — the moment Cybertruck started shipping and price-cuts had been compressing margins for ~12 months. Sources cited in line.

## Position being analyzed

**Tesla's strategic position entering 2024.** Frame: should management double down on the EV manufacturing flywheel or pivot capital toward AI/Robotaxi/Optimus?

## Strengths

- **Manufacturing cost leadership in EVs**: Model Y was the world's best-selling vehicle by units in 2023 (Forbes, Jan 2024). Tesla had the lowest cost-per-vehicle of any pure-play EV maker.
- **Vertical integration**: in-house battery cell production (4680), in-house silicon (FSD chip), proprietary charging network (Supercharger).
- **Brand equity that bypasses traditional marketing**: zero paid ads, organic media presence dominated by founder.
- **FSD data moat**: ~4 million vehicles uploading driving telemetry — orders of magnitude more than Waymo or Cruise had.

## Weaknesses

- **Aging core lineup**: Model S/X refresh in 2021 was minor; Model 3 refresh ("Highland") didn't reach all markets until late 2023; Cybertruck shipped but at small volume.
- **Margin compression from 2023 price cuts**: Q4 2023 auto gross margin (ex-credits) ~16%, down from peak ~30% in 2022.
- **Concentrated execution risk on the CEO** — strategic attention split across Tesla, X, xAI, Neuralink, SpaceX.
- **Service network undersized for fleet growth**: customer-satisfaction surveys consistently cited service waits as the #1 complaint.

## Opportunities

- **China EV market still growing despite competitive pressure**: BYD lead in China is real but PHEV-heavy; pure-BEV segment Tesla still leads in some price tiers.
- **Energy storage**: Megapack backlog was at multi-year highs; utility-scale storage was Tesla's fastest-growing segment by % in 2023.
- **Compact Model ("Model 2") platform**: a sub-$30k vehicle would address the largest unaddressed market segment Tesla hadn't entered.
- **Robotaxi**: if FSD reaches L4 viability, the unit economics inversion is enormous — but the "if" is the entire question.

## Threats

- **Chinese OEM cost structure**: BYD and others were building EVs at sub-$10k bill-of-materials. Western tariffs were not going to be a permanent moat.
- **Legacy OEM EV ramp finally happening**: Hyundai/Kia, GM Ultium, Ford BlueOval — slow but real.
- **Regulatory exposure on FSD safety claims**: NHTSA investigation open in 2024; lawsuit exposure if a fatal accident is tied to FSD marketing.
- **The threat from the strengths**: the entire bull case for the stock priced in Robotaxi success. If management spent the next 3 years validating that thesis and it didn't pan out, the price-to-earnings multiple would compress savagely.

## What this analysis suggests

The dominant tension is the **bottom-right of the Threats quadrant**: a strategy that bets on AI/Robotaxi delivers a different company than one that bets on continued EV manufacturing leadership. SWOT doesn't decide which — but it forces the team to acknowledge the bet is binary, not "both."

A reading of Tesla's 2024–25 public actions (cancelling Model 2, doubling down on Robotaxi day) suggests management chose the AI path. Whether that was the right call is a question for the next SWOT, in ~24 months.

## Want to run your own?

[Open the SWOT worksheet →](/tools/swot) — works in your browser, no sign-up. Or [read the full SWOT guide →](/academy/what-is-a-swot-analysis) for the methodology.

> **Want frameworks beyond SWOT on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=swot-tesla-example) fills in any of 100+ frameworks with AI assistance. For SWOT specifically, [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-tesla-ios) is the dedicated tool.

## Related

- [Tesla through Porter's Five Forces (2026)](/examples/tesla-porters-five-forces-2026) — the industry-structure read that this SWOT's Threats quadrant kept reaching for
- [Tesla VRIO analysis 2026](/examples/tesla-vrio-analysis-2026) — whether the strengths above are actually durable advantages or just current facts
- [Tesla Ansoff Matrix](/examples/tesla-ansoff-matrix) — the binary bet (AI/Robotaxi vs EV manufacturing) mapped onto growth quadrants
- [SWOT vs Five Forces](/compare/swot-vs-five-forces) — which tool holds "threats" better
- [The SWOT framework page](/frameworks/swot) — catalog entry and worksheet

---

### Tesla Ansoff Matrix Analysis 2026
URL: https://frameworklist.com/examples/tesla-ansoff-matrix
> A worked Ansoff Matrix of Tesla's growth strategy in 2026 — Market Penetration via price cuts and FSD, Product Development in Cybertruck and Optimus, Market Development in India and Energy, and Diversification with Robotaxi and humanoid robotics.

The Ansoff Matrix is a deliberately simple framework — two axes, four quadrants, escalating risk as you move from the upper-left to the lower-right. That simplicity is exactly why it's useful for a company like Tesla in 2026, which is doing all four things at once. The framework makes visible something the income statement does not: where the capital and management attention is actually being spent on growth, and how risky those bets are relative to the company's stated strategy.

## Position being analyzed

Tesla in mid-2026: the auto business has stabilized after the 2023–24 price war, energy storage is the fastest-growing segment by percentage, and the public valuation thesis depends increasingly on Robotaxi and Optimus rather than on selling more cars. The strategic question Ansoff helps with: is the growth portfolio balanced, or weighted toward the highest-risk quadrant?

## The four quadrants

| Quadrant | Definition | Risk | Tesla 2026 entries |
|---|---|---|---|
| **Market Penetration** | Existing product, existing market | Low | Price cuts on Model Y/3, FSD subscription push, Supercharger fleet expansion |
| **Market Development** | Existing product, new market | Medium | India entry, Energy in new geographies (Australia, Europe utility), Supercharger to non-Tesla vehicles |
| **Product Development** | New product, existing market | Medium-High | Cybertruck, refreshed Model Y "Juniper," the compact "Model 2"/affordable platform, Megapack scaling |
| **Diversification** | New product, new market | High | Robotaxi service, Optimus humanoid robot, Dojo / AI compute services |

## Market Penetration: holding the base

The work in this quadrant is unglamorous and necessary. Three plays:

- **Price elasticity testing.** The 2023–24 price cuts on Model 3 and Model Y produced volume growth but at the cost of operating margin. By 2026, ASP has stabilized as the mix shifts toward higher-margin Model Y configurations.
- **FSD attach rate.** Pushing FSD subscription on the installed fleet is pure Market Penetration — same customer, same vehicle, more revenue per customer. Conversion from free trial to paid subscription is the operational lever.
- **Supercharger network as moat reinforcement.** Now that the network is the de facto US standard (NACS adoption by Ford, GM, Hyundai, Rivian), every Tesla sold has a stronger ownership value proposition. This is Penetration via competitive moat, not via marketing.

This quadrant produces the cash that funds the others. Ansoff scores it low-risk because the customer, the product, and the distribution are all known.

## Market Development: India and Energy

Two notable bets here.

**India entry.** Tesla announced its India entry plan in 2025 after a multi-year tariff negotiation. The vehicle and the brand are existing; the market is new. India's premium EV segment is small but growing, and Tesla's GoToMarket challenge is operational (service network, charging infrastructure) rather than product-market fit. This is the textbook Medium-risk Market Development play.

**Energy storage in new geographies.** Megapack deployments expanded substantially in Australia, Europe, and select Middle East utility customers in 2024–25. Same product (utility-scale storage) into new geographic markets. The bottleneck is manufacturing capacity (Lathrop expansion) rather than market acceptance.

**Supercharger network opening to non-Tesla vehicles.** Arguably Market Development: existing product (charging infrastructure) sold to a new market (other-brand EV owners). Revenue contribution is small but the option value is large.

## Product Development: where the auto roadmap lives

This is the quadrant most casual observers underestimate. Tesla has been criticized for an aging product lineup, but the 2025–26 product cycle is dense:

- **Cybertruck**: shipping but at small volume relative to original projections; the unit-economics curve is still steepening.
- **Refreshed Model Y "Juniper"**: launched in 2025 across major markets — addresses the "aging product" critique for the best-selling vehicle.
- **The affordable platform** (formerly "Model 2"): development status is the most-watched question for the auto business. Strategic logic per Ansoff: a sub-$30k Tesla is Product Development (new product, existing market) and would meaningfully expand the addressable customer base.
- **Megapack and Powerwall iterations**: rapid product development cadence in the energy business, often understated in coverage focused on autos.

Risk in this quadrant is Medium-High because new auto products require new manufacturing tooling, supply chains, and demand validation — but the customer and channel are known.

## Diversification: where the valuation lives

This is the quadrant where Ansoff earns its keep, because it forces the analyst to call Diversification what it is: highest risk.

**Robotaxi (Cybercab) service**. Unveiled at the "We, Robot" event in October 2024. This is genuinely Diversification: a ride-hailing service is a new product (different unit economics, different operations) into a new market (consumers of mobility services, not owners of vehicles). Regulatory exposure, software autonomy maturity, and operational ramp are all unproven.

**Optimus humanoid robot**. New product (humanoid robotics is not adjacent to automotive in any meaningful technical sense beyond manufacturing automation) and new market (industrial/commercial labor automation, potentially consumer eventually). High-Diversification risk by any reading of the framework.

**Dojo / AI compute services**. The internally-developed AI training stack repositioned as a potential service offering. New product (compute service), new market (third-party AI training customers). Same Diversification logic.

Tesla's Master Plan Part 3 explicitly commits to a "sustainable energy economy" framing that places Diversification at the center of the strategy. Ansoff doesn't say that's wrong — it says it carries the highest risk and asks whether the rest of the portfolio is throwing off enough cash to underwrite it.

## Key takeaway

The Ansoff Matrix on Tesla in 2026 reveals a balance-of-portfolio question. Market Penetration and Product Development are doing the steady work of keeping the auto business productive — that's where the operating cash comes from. Market Development is moderate, with India as the biggest discrete bet. But the management attention and the public-market valuation are anchored to **Diversification** — Robotaxi, Optimus, AI compute. Ansoff's contribution is to label that asymmetry: the highest-risk quadrant is also the one bearing the company's narrative weight. The framework doesn't say the strategy is wrong — but it forces the question of whether the lower-risk quadrants are producing enough cash flow to underwrite the highest-risk one for as long as it takes. That's the discipline that gets lost in the day-to-day stock-price discourse.

## Want to go deeper

New to the model? Start with [Ansoff Matrix examples: the 4 growth strategies](/academy/ansoff-matrix-examples) for the four quadrants worked on real companies. Read more about the [Ansoff Matrix framework](/frameworks/ansoff) or browse other [strategy framework examples applied to real companies](/examples). For the same Ansoff lens on another company anchoring its growth to the riskiest quadrant, see the [Nvidia Ansoff Matrix 2026: the RTX Spark PC bet](/examples/nvidia-ansoff-matrix-2026), or — for a non-tech case running a move in every quadrant inside one year — the [FIFA Ansoff Matrix 2026: the World Cup growth bet](/examples/fifa-ansoff-matrix-2026). For the industry-structure read on the same company — why the quadrants above got harder to fund after the July 2026 Q2 earnings — see the [Tesla Porter's Five Forces analysis 2026](/examples/tesla-porters-five-forces-2026). For a different macro lens on a different operator, see the [Amazon PESTEL analysis 2026](/examples/amazon-pestel-analysis-2026) — PESTEL is the natural complement to Ansoff: one scores the macro environment, the other scores the growth-bet portfolio. To run an Ansoff analysis on a company you're tracking, the [Framework iPhone & iPad app](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each quadrant.

For Tesla's SWOT counterpart, see our sister site [SWOTPal's Tesla SWOT analysis](https://swotpal.com/examples/tesla?utm_source=frameworklist&utm_medium=referral&utm_campaign=ansoff-tesla) — a dedicated AI SWOT tool, free for the basic workflow.

---

### Tesla Porter's Five Forces Analysis 2026 (After Q2 Earnings)
URL: https://frameworklist.com/examples/tesla-porters-five-forces-2026
> A worked Porter's Five Forces analysis of Tesla after its July 22, 2026 Q2 earnings — record revenue, 16.3% margins, and all five forces moving the wrong way at once.

On **July 22, 2026, Tesla reported a record quarter and the stock fell 4%.** Revenue hit $28.2 billion, up 26% year over year, on more than 480,000 deliveries. Adjusted earnings came in at $0.33 per share against a consensus near $0.49. That gap is the whole story, and [Porter's Five Forces](/frameworks/fiveforces) is the framework built to explain it — because a company can execute well and still lose margin when the *structure* of its industry deteriorates underneath it.

Most Tesla Five Forces analyses on the web were written to a template and score the forces from brand narrative: strong moat, low new-entrant threat, moderate supplier power. Run against the Q2 2026 numbers instead, four of the five forces have moved against Tesla in the last twelve months, and the fifth — the one everyone scores as Tesla's protection — is the one China has already disproven.

## Position being analyzed

The framing numbers, all from the July 22 release and the quarters around it:

| Metric | Q2 2026 | Direction |
|---|---|---|
| Total revenue | $28.2B | +26% YoY, a record |
| Adjusted EPS | $0.33 | Missed ~$0.49 consensus; down 18% YoY |
| Deliveries | >480,000 | +25% YoY |
| Automotive gross margin (ex-credits) | 16.3% | Down from 19.2% in Q1 2026 |
| Regulatory-credit revenue | $146M | Down from $439M a year earlier |
| Capital expenditure | ~$5.79B | +142% YoY; FY2026 guidance raised above $25B |
| Energy storage deployed | 13.5 GWh | Growing |

The strategic question this poses: *is Tesla a company with a temporary margin problem, or a company whose industry has structurally re-priced?* Five Forces answers structural questions, which makes it the right tool here — and a poor one for the robotaxi debate, which we handle separately below.

## Competitive rivalry — high, and no longer one-sided

Rivalry is the force everyone gets right directionally and wrong in detail. The detail that matters in 2026 is that Tesla is now winning the near-term race and losing the structural one.

On first-half BEV volume, BYD held a cumulative lead of roughly 867,000 units to Tesla's 838,000 — but BYD's Q2 sales *fell* about 8% year over year while Tesla's grew 25%. Read narrowly, Tesla is taking share back. Read as industry structure, two things are true at once: the global BEV leader is close enough that the crown changes hands quarter to quarter, and the price competition required to hold that position is visible in Tesla's own 16.3% ex-credit gross margin.

The subtler rivalry effect is the regulatory-credit collapse. Credit revenue fell to **$146 million from $439 million** a year ago — that is near-pure profit that disappeared not because Tesla did anything, but because rivals built enough of their own compliant vehicles to stop buying. Tesla's competitors were, for a decade, also its customers. Rivalry intensifying and a high-margin revenue line vanishing are the same event.

**Verdict: High and rising.** The unusual feature is that Tesla's rivals were previously a profit center.

## Bargaining power of buyers — the force that changed fastest

This is the force most template analyses still score as "low," on the theory that Tesla buyers are brand-loyal and there is a waiting list. That has not been true in the US since **September 30, 2025**, when the $7,500 federal EV tax credit expired.

The demand data since:

| US battery-electric market | Figure |
|---|---|
| Q1 2026 new BEV sales | 212,600 (−28% YoY from 296,304) |
| Q2 2026 new BEV sales | 247,226 (+14.2% QoQ, but −20.5% YoY) |
| Average new-EV transaction price (Feb 2026) | $55,300 |
| Price gap vs comparable combustion models | $6,500 — a record low |
| Dealer days' supply, EVs vs gasoline | ~130 days vs 89 days |

Read those last two rows together. The price gap to combustion cars hit a record low *while* inventory piled up to 130 days. That is not buyers being won over — that is manufacturers absorbing the withdrawn subsidy out of their own margin and still not clearing the lots. When a buyer can wait, and the seller cannot, buyer power is high regardless of how much the buyer likes the brand.

**Verdict: High, and structural rather than cyclical.** The credit is not coming back on the old terms.

## Bargaining power of suppliers — moderate, concentrating at the cell

Porter's supplier force asks whether the inputs you cannot make yourself have leverage over you. For EVs that question is almost entirely about battery cells, and the cell market is consolidating rather than fragmenting: **CATL held 39.2% of the global battery market and 50.1% of the Chinese domestic market in Q1 2026**, with energy-storage orders from some overseas markets booked out through the second quarter — capacity that is not available to automakers at any price.

Tesla's counter is the one it has always run: vertical integration. The Q2 2026 capex plan explicitly includes in-house semiconductor fabrication, 4680 cell capacity, and solar manufacturing. That is Porter's textbook response to supplier power — backward integration — and it is expensive, which is part of why capex rose 142%.

The comparison worth making is with a rival that chose the opposite: Xiaomi sources over 80% of its cells from CATL, and is only now diversifying to Sunwoda and CALB for its Skynomad sub-brand. Xiaomi accepted supplier power in exchange for speed to market. Tesla is spending billions to refuse it. Both are defensible; only one shows up as a margin drag this quarter.

**Verdict: Moderate, rising — and Tesla is paying cash to keep it moderate.**

## Threat of substitutes — the hybrid problem

Substitutes are where the 2026 picture diverges most sharply from the 2021 consensus. The substitute for a Tesla is not another EV. It is a hybrid.

Hybrids are on track to grow roughly **9% in 2026**, against about **2% for the overall US light-vehicle market** — while battery-electric sales fell 20.5% year over year in Q2. A hybrid gives the buyer most of the fuel-cost benefit, none of the charging anxiety, and, since the credit expired, a comparable or better total cost of ownership. Used EVs are the second substitute, with demand hitting record highs precisely because new-EV pricing lost its subsidy.

Tesla has no hybrid and will not build one; the entire manufacturing architecture is premised on not needing to. That is a strategic commitment, not an oversight — but Five Forces does not grade intent. It grades whether the buyer has an acceptable alternative, and in 2026 the buyer does.

**Verdict: High and rising.** This is the force with the least Tesla can do about it.

## Threat of new entrants — low by the book, disproven in practice

Every template analysis scores this force low, citing capital intensity, brand, and manufacturing learning curves. Those barriers are real. They are also the barriers **Xiaomi cleared in about two years**: cumulative deliveries approached 700,000 by the end of April 2026, June deliveries were 34,738 (+36.5% YoY), and Xiaomi rose to CATL's third-largest battery customer at 6.8% of June purchases.

The correct reading is not that entry barriers are low — it is that they are low *for a specific kind of entrant*: a consumer-electronics firm with an existing brand, a distribution network, and enough balance sheet to buy cells at scale rather than make them. That describes a short list, but it is not an empty one, and the list is concentrated in the market with the most EV demand.

**Verdict: Low globally, high in China for electronics incumbents.** Scoring this force with a single number is the most common error in Tesla Five Forces analyses.

## The Capex-Follows-Forces Test

Here is the problem with everything above: it is an honest Five Forces analysis of an industry Tesla is deliberately spending its way out of.

Porter's model analyzes **industry structure, not companies**. Tesla in 2026 straddles two industries whose force profiles point in opposite directions — and averaging them produces an analysis that describes neither. So run the model twice and compare the columns:

| Force | EV manufacturing (where the revenue is) | Autonomy & robotics (where the capex is) |
|---|---|---|
| Competitive rivalry | **High** — BYD at parity, Xiaomi scaling, price war ongoing | **Moderate** — Waymo ahead on driverless miles, few credible others |
| Buyer power | **High** — subsidy gone, 130 days' supply | **Low** — no established price, no incumbent alternative for riders |
| Supplier power | **Moderate–high** — CATL at 39.2% global share | **Moderate** — compute and chips, which Tesla is integrating |
| Substitutes | **High** — hybrids +9%, used EVs at record demand | **High** — human-driven rideshare is cheap and ubiquitous today |
| New entrants | **Low globally, breached in China** | **High** — every AI lab and automaker is a potential entrant |
| Net structure | Deteriorating | Unformed, contestable |

The test itself is three questions, and it applies to any company whose spending has outrun its revenue mix:

1. **Which industry produces the revenue today?** For Tesla: EV manufacturing, essentially all of it.
2. **Which industry receives the marginal capital?** For Tesla: autonomy and robotics — robotaxi fleet, Optimus capacity, AI compute, a semiconductor fab. Capex up 142% to $5.79B, FY2026 guidance above $25B, and up to $30B in debt facilities being arranged.
3. **Do the forces in industry #2 justify the migration — and can industry #1 fund the crossing?**

Question 3 is the whole valuation debate, stated structurally. The robotaxi service was operating in seven metro areas as of the Q2 call, with a reported ~380,000 driverless miles — a real product at a scale that cannot yet fund anything, while an active NHTSA probe into FSD sits over the timeline. Meanwhile the industry expected to fund the crossing is the one whose five forces all just deteriorated.

**When a company's revenue industry and its capex industry diverge, a single Five Forces analysis is not conservative — it is wrong.** Analysts who scored Tesla's forces favorably in 2021 were scoring an industry Tesla dominated; analysts scoring them harshly in 2026 are scoring an industry Tesla is trying to leave. Both are analyzing the left column. The bet is entirely in the right one.

## Key takeaway

Tesla's Q2 2026 is a clean demonstration of the difference between company performance and industry structure. The company executed — record revenue, record deliveries, 25% volume growth against a declining BYD. The industry re-priced — subsidy withdrawn, credits evaporating, hybrids taking the substitute slot, cell supply concentrating, and the entry barrier breached by a phone maker.

Five Forces cannot tell you whether the robotaxi bet works. What it can tell you, precisely, is what that bet is *being funded by*: an industry where all five forces now point the wrong way, at the exact moment the capital requirement went up 142%. That is the real tension in the quarter, and it is why a record revenue print was met with a 4% decline.

> Want to run this analysis on your own market? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — fill in Porter's Five Forces, VRIO, or Ansoff with AI assistance.

## Go deeper

- The framework itself: [Porter's Five Forces](/frameworks/fiveforces)
- Tesla's resources scored one by one: [Tesla VRIO Analysis 2026](/examples/tesla-vrio-analysis-2026)
- Where the capex is pointed, in growth terms: [Tesla Ansoff Matrix Analysis 2026](/examples/tesla-ansoff-matrix)
- Five Forces on an industry going the other way: [Nvidia at $5 trillion — moat or mirage](/blog/ai-chip-five-forces-nvidia-5-trillion)
- Picking between lenses: [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) and [SWOT vs Five Forces](/compare/swot-vs-five-forces)
- All Tesla analyses: [Tesla framework examples](/examples/tesla)

---

### Tesla VRIO Analysis 2026
URL: https://frameworklist.com/examples/tesla-vrio-analysis-2026
> A worked VRIO analysis of Tesla's resources and capabilities in 2026 — vertical integration, FSD data flywheel, Supercharger/NACS, gigafactory manufacturing, energy storage, the Musk brand, and the Optimus bet. Which of these survive the four-question VRIO test.

![Photograph of a circuit board with components, evoking the silicon underpinning of modern EVs and autonomy systems](https://images.unsplash.com/photo-1518770660439-4636190af475?auto=format&fit=crop&w=1600&q=80)

Tesla in 2026 is a company that's been valued, alternately, as a car company, a software company, an energy company, an AI company, and a robotics company — depending on which quarter and which analyst is talking. VRIO is the right framework for cutting through that noise. Instead of trying to score Tesla *as a whole*, it forces a resource-by-resource analysis: what does the company own, and which of those things actually constitute sustained competitive advantages by the four-question test?

Run cleanly on Tesla in May 2026, VRIO produces a less flattering but more useful map than the bull-bear consensus. Two resources are durable moats. Two are temporary advantages that are eroding. Two are bets that VRIO doesn't yet credit as advantages at all.

## Position being analyzed

Mid-2026: Tesla deliveries are flat-to-down YoY against the 2023-2024 peak, gross margin has stabilized in the high teens after the 2022-2024 price-cut cycle, FSD revenue (subscription + sale) is growing but still modest in absolute terms, Cybertruck production has reached a sustainable run-rate (~80k/year) without becoming a volume product, Energy Storage is the fastest-growing segment by margin contribution, Optimus is shipping single-digit-thousand units to Tesla's own factories and a small number of pilot customers, and Robotaxi / Cybercab is in a multi-city limited deployment with a 2027 commercial scale target. The strategic question VRIO helps with: which of Tesla's resources, if challenged tomorrow, would still produce returns above the cost of capital?

| Metric | Value | Direction vs. 12 months ago |
|---|---|---|
| Vehicle deliveries (TTM) | ~1.7M | Down from ~1.81M peak |
| Automotive gross margin (ex-credits) | ~17% | Stable |
| Energy storage deployments (GWh) | ~50+ TTM | Up materially |
| Supercharger stalls (global) | 70,000+ | Up; non-Tesla revenue meaningful |
| FSD active subscription base | 600k+ | Up from ~400k |
| Optimus units shipped | Low thousands | Up from ~0 |
| Robotaxi commercial vehicles in service | Low hundreds | Up from 0 |

## VRIO applied — resource by resource

### Supercharger Network + NACS standard — sustained advantage ✅

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | Charging infrastructure is a binding constraint on EV adoption |
| **Rare** | Yes | No peer network operates at this scale or reliability |
| **Inimitable** | Yes | CapEx + permitting + utility coordination + site economics make replication slow (5+ years) and expensive |
| **Organized** | Yes | Tesla operates it for both Tesla and non-Tesla vehicles, monetizing both flows; NACS adoption by GM/Ford/Rivian/Hyundai/etc. converts it from a captive amenity into a *platform* |

The Supercharger story is the clearest VRIO pass in the Tesla resource stack. It's also the resource that gets *least* analyst attention because it isn't sexy. The 2024-2025 NACS standardization moves converted the network from a Tesla-only feature into the de facto US EV charging standard, which means Tesla now monetizes its capital investment from every EV sold in the US. That's a structural shift VRIO weights heavily.

### Manufacturing platform learning curve (gigafactory operations) — sustained advantage ✅

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | Cost per vehicle is the binding constraint on margin in a price-sensitive market |
| **Rare** | Yes | The actual operational know-how (yield rates, takt-time discipline, gigacasting, dry electrode) is held by maybe 3-5 companies globally |
| **Inimitable** | Yes — but eroding | BYD, CATL, and a handful of Chinese OEMs have built parallel capability; the gap is real but no longer infinite |
| **Organized** | Yes | Vertical integration captures the learning across vehicles, energy storage, and Optimus |

The honest tension here is that BYD's manufacturing capability in 2026 is at least as efficient as Tesla's on a unit-cost basis, especially in China. So the *global* Inimitability is weakening. But within the Western market — where political-economic forces are increasingly restricting Chinese OEMs — Tesla's manufacturing learning curve remains hard to match. VRIO scores this as a sustained advantage *within the markets Tesla can actually compete in*, which is the operational reality.

### FSD / Autonomy stack — temporary advantage, downgrading ⚠️

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | Subscription revenue + brand premium + Robotaxi enablement |
| **Rare** | No longer clearly | Waymo, Cruise (paused), BYD God's Eye, Mobileye, Mercedes Drive Pilot, multiple Chinese stacks are all in the field |
| **Inimitable** | Eroding | The data-flywheel argument was strong in 2019; in 2026, multiple competitors collect billions of fleet-miles |
| **Organized** | Yes | Tesla's vertical-integration story still differentiates how it captures value |

This is the most contested resource in Tesla's stack. The bull case is that Tesla's data scale + custom training silicon + vertical integration produces a [flywheel](/glossary/flywheel) competitors structurally can't catch. The VRIO read is more sober: every part of that flywheel has competitive analogs in 2026 — Waymo has the regulatory + driverless deployment lead, BYD has the scale and the China market, the Chinese ADAS stack is closing the gap quickly. FSD is still ahead on many axes, but the *trajectory* is convergence, not divergence. VRIO calls that a temporary advantage.

### Brand + Musk halo — contested resource ⚠️

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes — and No | Drives both purchase intent and rejection in 2026; net effect is bimodal by cohort |
| **Rare** | Yes | No other automotive brand has comparable narrative gravity |
| **Inimitable** | Yes | But that's because the Musk-volatility tradeoff is unique, not entirely positive |
| **Organized** | Partial | Tesla has not built brand independence from Musk; he is the brand |

Brand was a textbook VRIO sustained-advantage resource for Tesla through 2022. From 2023-2025, Musk-related political and social controversy converted the brand from a clear premium asset into a polarized one. Sales data shows the brand attracts and repels customers in roughly equal measure depending on the cohort — younger urban liberal cohorts have shifted negative, conservative-leaning cohorts have shifted positive. The net is hard to call. VRIO downgrades this from "advantage" to "contested resource that requires active management."

### Optimus humanoid platform — not yet a VRIO resource ❌

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Theoretically, yes | Currently zero commercial revenue |
| **Rare** | No | Figure, Boston Dynamics, Apptronik, Unitree, Agility, multiple Chinese efforts |
| **Inimitable** | No | The hardware and ML stacks are converging across competitors |
| **Organized** | Yes | Tesla has the manufacturing + AI infrastructure |

VRIO is strict: it only credits resources that *currently* generate competitive returns. Optimus is impressive engineering and may become a significant advantage by 2028-2030. In 2026, it's optionality, not advantage. Investors paying for an Optimus moat today are paying for an option, not a resource.

### Robotaxi / Cybercab service — not yet a VRIO resource ❌

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Theoretically | No commercial revenue at scale |
| **Rare** | No | Waymo is years ahead in commercial deployment |
| **Inimitable** | No | The bet depends on FSD being inimitable — and it isn't, see above |
| **Organized** | Yes | Tesla controls the vehicle and the software |

Same logic as Optimus. The 2027 commercial-scale target is a real corporate plan, but VRIO doesn't credit forward plans as current resources. If the service scales as promised, this becomes a VRIO advantage in 2027-2028. In 2026, it isn't one.

### Energy Storage (Megapack) — sustained advantage, under-discussed ✅

| Test | Verdict | Reasoning |
|---|---|---|
| **Valuable** | Yes | Grid-scale storage is the fastest-growing energy infrastructure category |
| **Rare** | Yes | LG, CATL, BYD, and Fluence compete but Megapack has captured a leadership position in the Western utility market |
| **Inimitable** | Partially | The hardware is increasingly commoditized; the software (Autobidder, Powerhub) is differentiating |
| **Organized** | Yes | Vertical integration with Tesla's battery sourcing and manufacturing |

The interesting hidden story. Energy Storage was a side bet for most of Tesla's history and is now a structural margin contributor. VRIO scores it as a sustained advantage primarily on the software + Western-market positioning, not on the cell hardware itself. The cell-cost story shows why: the industry reached Musk's 2012 raw-materials floor by switching to LFP chemistry, so a low cell cost is available to everyone (see [first principles thinking examples](/academy/first-principles-thinking-with-examples)).

## Counter-argument

The bull view: VRIO under-counts Tesla's *combinations*. The Supercharger + FSD + manufacturing + brand together produce a customer experience no competitor can replicate, even if each individual resource is contestable. The framework analyzes resources individually and misses the integration value.

VRIO has a partial answer to this — the Organized question is meant to capture exactly the integration value. Tesla scores Yes on Organized for nearly every resource, which credits the integration. But it's true that VRIO under-weights *combinatorial* moats: when three resources together produce something none of them would produce alone. For Tesla, the most likely combinatorial moat is Supercharger + Manufacturing + Energy — the bundle that no other car-or-energy company could assemble. That's the steel-frame story under the AI-and-robotaxi hype.

## Signals to watch (next 18 months)

| Signal | Resource | Why it matters |
|---|---|---|
| Non-Tesla Supercharger revenue mix | Supercharger network | The platform-vs-amenity transition is the structural shift |
| BYD US/Europe sales progression | Manufacturing | The Inimitability test on Western-market terms |
| Waymo / Cruise / Chinese robotaxi commercial scale | FSD | Whether FSD's temporary advantage shortens further |
| FSD subscription attach rate | FSD | Whether consumer perception matches Tesla's narrative |
| Optimus shipping milestones (10k, 100k units) | Optimus | When VRIO can start crediting it as a resource |
| Energy Storage gross margin | Megapack | Whether the hardware commoditizes faster than the software differentiates |
| Tesla 2026 election-cycle brand polling | Brand | The bimodal cohort drift trajectory |

## Key takeaway

The Tesla VRIO story in 2026 is that the *boring* resources are the durable ones (Supercharger network, manufacturing learning, Energy Storage), and the *exciting* resources are either eroding (FSD, brand) or not yet resources at all (Optimus, Robotaxi). That's nearly the inverse of how the equity is priced. The framework's contribution is to refuse the synthesis and force the discipline of scoring each resource on its own merits.

If you only have time to track one variable, track non-Tesla Supercharger revenue. That number is the cleanest proof of whether Tesla's most under-priced moat is converting from amenity to platform — and if it is, Tesla is a better business than the FSD-or-Optimus debate makes it look.

*Cover photo: [Alexandre Debiève on Unsplash](https://unsplash.com/photos/FO7JIlwjOtU).*

> **Want to test your own resources against VRIO?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=tesla-vrio-example) walks all four questions — value, rarity, imitability, organization — with AI-assisted prompts. Free to start.

## Related

- [VRIO framework](/frameworks/vrio) — the four-question template + how to apply it
- [Netflix VRIO Analysis 2026](/examples/netflix-vrio-analysis-2026) — the same four questions on Netflix after its failed Warner Bros. bid, with The Auction Test for pricing imitability
- [Amazon VRIO Analysis 2026](/examples/amazon-vrio-analysis-2026) — the same four questions on Amazon, with The Rival's Invoice: Amazon Leo has to buy SpaceX launches to catch up with Starlink
- [McKinsey 7S Framework: Hard and Soft Elements](/academy/mckinsey-7s-framework-hard-soft-elements) — for the internal-alignment lens that complements VRIO's resource-based view
- [Tesla Ansoff Matrix Analysis 2026](/examples/tesla-ansoff-matrix) — same company, growth-strategy lens
- [Tesla Porter's Five Forces Analysis 2026](/examples/tesla-porters-five-forces-2026) — the industry-structure counterpart, run against the July 2026 Q2 results. VRIO scores what Tesla owns; Five Forces scores the industry those resources have to survive in
- [Nvidia BCG Matrix Analysis 2026](/examples/nvidia-bcg-matrix) — a portfolio-allocation analysis for contrast
- [Apple PESTEL Analysis 2026](/examples/apple-pestel-analysis-2026) — macro-environment scan on a different company
- [Microsoft Porter's Five Forces Analysis 2026](/examples/microsoft-porters-five-forces-analysis-2026) — industry-level analysis for contrast

---

### PESTEL Analysis of the USA (2026): the one-force economy
URL: https://frameworklist.com/examples/usa-pestel-analysis-2026
> A PESTEL analysis of the USA in 2026 — an AI capex boom masking a stalling labour market, the Supreme Court tariff reversal, and a grid that cannot keep up.

![Photograph of a data centre server hall lit in blue](https://images.unsplash.com/photo-1558494949-ef010cbdcc31?auto=format&fit=crop&w=1600&q=80)

Most country PESTELs read like an encyclopedia entry: stable institutions, large consumer market, strong legal system, leadership in technology. That description of the United States has been true for forty years and is useless for a 2026 planning decision. A PESTEL is worth running only when it changes what you'd do, and the interesting thing about the US right now is not any single one of the six forces — it's that one of them is holding up the other five.

[PESTEL](/frameworks/pestel) scans six external macro forces — Political, Economic, Social, Technological, Environmental, Legal — around an entity. Run on the US in August 2026, the scan produces an unusual shape: one very large positive cell, four negative or deteriorating cells, and a physical constraint that the positive cell is itself creating.

## Position being analyzed

August 2026. The Supreme Court has struck down the IEEPA tariff regime, the Federal Reserve is on hold with inflation still above target, the July jobs report showed the first outright payroll decline of the cycle, and AI data-centre construction has become a measurable share of national output. The strategic question PESTEL helps with: if you are siting a plant, pricing a 2027 budget, or deciding whether to hire in the US, which of these forces should actually drive the decision?

| Metric | Value | Direction vs. 12 months ago |
|---|---|---|
| Real GDP growth (Q2 2026, advance) | 1.5% annualised | Down — missed ~2.0–2.1% consensus |
| Fed funds target range | 3.50%–3.75% | Held at both the June and July meetings |
| Core inflation (June 2026) | 3.3% | Still well above the 2% target |
| Nonfarm payrolls (July 2026) | **−23,000** | Down — first decline; +83,000 expected |
| Unemployment rate | 4.1% | Down from 4.2% — on falling participation |
| Labour force participation | 61.4% | Down — lowest in over five years |
| Average hourly earnings (12-month) | 3.2% | Down — lowest since May 2021 |
| US AI investment (2026, projected) | ~$600B | Up — 0.7% → 1.4% of GDP in a year |
| Data-centre power draw | 31 GW → 41 GW | Up — 4.1% → 5.3% of peak summer demand |

## PESTEL scorecard for the United States, August 2026

| Force | Direction for the US economy | Strength | What flips it |
|---|---|---|---|
| **Political** | ⚠️ Mixed | High | Whether Section 232 duties are widened to replace struck-down IEEPA tariffs |
| **Economic** | ❌ Hurting | High | Core inflation falling toward 2% without a labour-market break |
| **Social** | ❌ Hurting | Medium-High | Participation recovering off its five-year low |
| **Technological** | ✅ Helping | Very High | AI capex holding through 2027 rather than hitting a demand air-pocket |
| **Environmental** | ❌ Hurting | Rising fast | The 100+ GW generation shortfall closing |
| **Legal** | ⚠️ Mixed | Medium | Whether AI preemption is settled by statute or by litigation |

One strongly positive cell, three negative, two mixed. The positive cell is also the largest — which is the whole story.

## Political — the tariff regime changed instrument, not direction

The defining political event of 2026 was judicial, not legislative. On [20 February 2026 the Supreme Court ruled 6-3](https://www.congress.gov/crs-product/LSB11398) that the International Emergency Economic Powers Act does not authorise the President to impose tariffs of indefinite scope, invalidating the April 2025 "reciprocal" tariffs and every other IEEPA-based duty.

The magnitudes are large. IEEPA tariffs represented roughly half of all US customs duties, and [Penn Wharton put the potential refunds at up to $175B](https://budgetmodel.wharton.upenn.edu/p/2026-02-20-supreme-court-tariff-ruling/), with the Court of International Trade directing Customs and Border Protection to process them from 4 March.

The mistake would be to score this as "tariffs are over." [The ruling left other authorities untouched](https://www.hklaw.com/en/insights/publications/2026/02/supreme-court-strikes-down-ieepa-tariffs): Section 232 duties on steel, aluminium, copper, automobiles, auto parts, lumber, timber, trucks and semiconductors all survive, as do Section 301 tariffs. What changed is the *instrument* — from a fast, broad, unilateral tool to slower, sector-specific ones that require findings and process. For an importer, that converts a tail risk into a scheduling problem: the same protection can return, but it arrives sector by sector with visible lead time. The second political vector is the November 2026 midterms, which put every trade and energy-price decision on a short clock.

## Economic — 1.5% growth with 3.3% core inflation

The Q2 2026 advance estimate put growth at [1.5% annualised, against consensus near 2.0–2.1%](https://www.cnbc.com/2026/07/30/us-economy-slowed-to-1point5percent-growth-rate-in-q2-june-core-inflation-at-3point3percent.html), with June core inflation at 3.3%. The Federal Reserve has held the funds rate at 3.50–3.75% through its June and July meetings and revised its own 2026 growth projection down from 2.4% to 2.2%, while the dot plot moved hawkish.

That combination — decelerating growth, inflation stuck above target, a central bank unwilling to ease — is the least comfortable cell on this grid. It removes the conventional shock absorber. In a normal slowdown the Economic force turns negative and monetary policy turns positive to offset it; here both are pointed the same way, because cutting into 3.3% core inflation is not available.

## Social — the labour market is weakening behind a falling unemployment rate

The July 2026 employment report is the most misread number of the year. [Nonfarm payrolls fell by 23,000](https://www.cnbc.com/2026/08/07/jobs-report-july-2026.html) against an expected gain of 83,000, driven by a 53,000 drop in government jobs plus softness in retail and leisure. May and June were revised down by a combined 103,000. And yet the unemployment rate *fell*, from 4.2% to 4.1%.

Both are true because they come from different surveys and the reconciling variable is participation, which dropped to **61.4%** — the lowest in more than five years. The unemployment rate is a ratio against the labour force; people who stop looking leave the denominator. Wage growth confirms the direction: average hourly earnings rose 3.2% over twelve months, the slowest since May 2021.

For a PESTEL, the discipline is to score the force, not the headline. The Social force here is a shrinking, cooling labour supply — which is a hiring-cost tailwind and a demand headwind at the same time.

## Technological — the force carrying the entire grid

This is the one unambiguously positive cell, and it is very large.

[Goldman Sachs projects global AI investment above $1 trillion in 2026](https://www.goldmansachs.com/insights/articles/global-investment-is-forecast-to-exceed-1-trillion-in-2026), with just under $600B of it in the US. The five largest hyperscalers alone have committed roughly $660–690B of 2026 infrastructure spend, the bulk directed at AI compute, data centres and networking. [Epoch AI puts data-centre, hardware and networking investment at 1.4% of US GDP in Q1 2026, up from 0.7%](https://epoch.ai/data-insights/ai-datacenter-share-gdp) — a doubling in roughly a year.

Set that against 1.5% annualised GDP growth and the significance is hard to miss. The comparison is deliberately crude — a change in a spending category's *share of the level* of GDP is not the same thing as its contribution to the *growth rate*, and anyone quoting one as the other is overclaiming. But the order of magnitude survives the caveat: a category that added roughly seven-tenths of a percentage point of GDP in share, inside an economy growing 1.5%, is not a rounding error. It is the marginal buyer.

## Environmental — the constraint the Technological force is manufacturing

Data centres need power, and the US grid does not have it.

[Gartner projects data-centre electricity consumption growing 26% in 2026](https://www.gartner.com/en/newsroom/press-releases/2026-06-10-gartner-says-data-center-electricity-demand-to-grow-26-percent-in-2026); demand rises from 31 GW in 2025 to 41 GW in 2026, taking data centres from 4.1% to 5.3% of total US peak summer power demand. The supply side does not match: [BofA estimates the US needs more than 230 GW of new generating capacity over five years while regulated utilities plan to add roughly 93 GW](https://www.utilitydive.com/news/ai-data-center-growth-utilities-generation-plans/825541/) — a shortfall above 100 GW. Power availability, not land or permitting, is now the leading cause of construction delay in major markets, and reliability risk is concentrated in the Mid-Atlantic, Mid-Continent and Northwest rather than in Texas or Georgia.

Note what this cell actually is. It is not a separate environmental trend that happens to coincide with the technology boom. It is the technology boom, arriving as a physical constraint — and, through retail electricity prices in a midterm year, as a political one.

## Legal — an AI patchwork that federal policy has not resolved

The legal force is unsettled in a specific, plannable way. [A December 2025 executive order, "Ensuring a National Policy Framework for Artificial Intelligence,"](https://www.whitecase.com/insight-alert/state-ai-laws-under-federal-scrutiny-key-takeaways-executive-order-establishing) directed the Attorney General to stand up an AI litigation task force to challenge state AI laws, and required Commerce to publish an evaluation of burdensome state laws by 11 March 2026. Child-safety rules, state procurement, and AI infrastructure regulation were carved out.

What matters for planning is what did *not* happen: [no federal preemption was enacted](https://www.ropesgray.com/en/insights/alerts/2026/03/examining-the-landscape-and-limitations-of-the-federal-push-to-override-state-ai-regulation). The executive order suspends no state law, and until courts resolve the preemption disputes, compliance obligations under every existing state regime remain live. The practical result is a company facing a patchwork it must satisfy in full, plus litigation risk about whether that patchwork survives — the most expensive configuration available, and one that will not resolve on a schedule anyone can plan around.

## The Load-Bearing Force Test

Standard PESTEL practice scores six cells and ranks them — that's what the [PESTEL Materiality Filter](/academy/how-to-do-a-pestel-analysis#the-pestel-materiality-filter) does. Ranking assumes the forces are independent. Sometimes they aren't, and when one force is structurally holding up the others, a ranked list actively misleads: it will show you five problems and one strength, when what you have is one strength whose failure creates five problems.

Three questions detect it. **Two or more "yes" answers mean you have a load-bearing force and must model the coupling rather than reading cell by cell.**

| # | Question | United States, August 2026 | Verdict |
|---|---|---|---|
| 1 | **Removal test** — strip the force out; does the headline metric stall? | Data-centre capital formation went from 0.7% to 1.4% of GDP against Q2 growth of 1.5% annualised | ✅ Yes |
| 2 | **Generation test** — does the force *create* the constraints appearing in other cells? | AI capex → 31→41 GW data-centre draw → a 100+ GW generation shortfall → electricity prices → a midterm-year political issue | ✅ Yes |
| 3 | **Funding test** — is the force paid for by forward conviction rather than current cash flow? | ~$660–690B of committed 2026 hyperscaler capex against AI revenue that does not yet cover it | ✅ Yes |

Three of three. The US in 2026 is a single-force macro environment, and the three tests also say what to monitor: not GDP, but the AI capex commitment schedule — because question 3 says that is the variable with the least support underneath it, and questions 1 and 2 say everything else moves when it does.

The test generalises past this case. Ireland in the 2000s (foreign direct investment), Australia through the 2010s (Chinese commodity demand), and Saudi Arabia today all pass at least two of the three, and in each the useful analysis was never the six-cell ranking.

## Key takeaway

PESTEL run properly on the United States in 2026 does not produce a list of six macro factors — it produces a dependency. The Technological force is carrying national output, and it is simultaneously manufacturing the Environmental constraint (a 100+ GW generation gap) and feeding the Political one (electricity prices in a midterm year). Underneath it, the forces that would normally provide a floor are all pointed down: growth at 1.5% with core inflation at 3.3% removes the monetary shock absorber, and a labour market shedding jobs behind a falling unemployment rate removes the consumption one.

That reframes the planning question. The instinct is to hedge the visible risks — tariffs, inflation, hiring. The Load-Bearing Force Test says those are downstream. The variable worth tracking is whether roughly $660–690B of committed hyperscaler capex holds through 2027, because it is the only cell on the grid currently pushing in the right direction, and it is funded by conviction rather than by cash flow.

## Want to go deeper

New to the method? Start with [How to Do a PESTEL Analysis](/academy/how-to-do-a-pestel-analysis) — the six factors, a six-step process, and the Materiality Filter for ranking forces. For the framework reference, see [PESTEL](/frameworks/pestel), or browse all [strategy framework examples](/examples).

For PESTEL run on single companies rather than a whole economy, the [Amazon PESTEL analysis (2026)](/examples/amazon-pestel-analysis-2026) shows a five-against-one force asymmetry, and the [Nike PESTEL analysis (2026)](/examples/nike-pestel-analysis-2026) traces how one tariff shock cascades through the entire grid. For another economy-level scan, see the [World Cup 2026 PESTEL analysis](/examples/world-cup-2026-pestel-analysis) — six forces across a three-country host economy. And for the counterparty to the tariff story above, the [PESTEL analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) scans the same six forces on the other side of the border, where the pathology is different: not one force carrying the other five, but one force *rewriting* them.

The [PESTEL analysis of China (2026)](/examples/china-pestel-analysis-2026) is the sixth scan and the counterparty to this page's trade cell: written ten days before the 24 September Washington summit, it finds every one of China's six cells returning two readings — a production reading (exports +17.8% in July) and a household reading (retail sales +0.6%) — with opposite signs, and introduces the Two-Ledger Test to score them separately. The 7.5% overcapacity tariff on this page's agenda is Washington pricing the first ledger. The [PESTEL analysis of India (2026)](/examples/india-pestel-analysis-2026) is the seventh scan and the mirror image of this one: where the USA's Political cell is the load-bearing force for its own five, India's Political cell is load-bearing for *someone else's* — the Graham Act signed on 18 September gives the USTR thirty days to propose a tariff of up to 100% on the largest buyer of Russian oil, and the Imported-Cell Test scores that cell on Washington's calendar rather than New Delhi's. The [PESTEL analysis of Germany (2026)](/examples/germany-pestel-analysis-2026) is the fourth economy-level scan and the sharpest contrast with the reading on this page: where the USA has one force carrying the other five *today*, Germany has substantive policy in all six and a delivery date on most of them — the Disbursement Gap counts the interval between enactment and effect. The [PESTEL analysis of the European Union (2026)](/examples/europe-pestel-analysis-2026) is the fifth scan and the first whose subject is not a state: it introduces the Competence Test, which asks *which* government holds each cell's lever before scoring it — the question the Load-Bearing Force Test can skip only because the USA has one government behind all six cells. The [PESTEL analysis of France (2026)](/examples/france-pestel-analysis-2026) is the third economy-level scan and the one that most directly challenges the reflex this page warns about: France scores badly on Political and Social and well on Technological and Environmental, and the Ballast Test explains why the two groups do not move together. The [PESTEL analysis of Mexico (2026)](/examples/mexico-pestel-analysis-2026) is the eighth scan and reads this page's trade cell from the receiving end: after the USTR declined to renew USMCA on 1 July 2026, Mexico's record first-half FDI turned out to be 88.5% reinvested profit, with new investment down 13.4%, and the Entrant Test explains why firms already there and firms deciding whether to come read the annual review in opposite directions.

PESTEL scans the macro environment; it does not analyse an industry's competitive structure. When you need the second thing, [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) explains which to reach for. And if you're weighing PESTEL against an internal-plus-external scan, [SWOT vs PESTLE](/compare/swot-vs-pestle) covers that pairing.

To run a PESTEL on a market you're tracking, [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each of the six forces.

If a SWOT is what you actually need, our sister site [SWOTPal](https://swotpal.com?utm_source=frameworklist&utm_medium=referral&utm_campaign=pestel-usa) is a dedicated AI SWOT tool — free for the basic workflow.

*Cover photo: [Taylor Vick on Unsplash](https://unsplash.com/photos/M5tzZtFCOfs).*

---

### World Cup 2026 PESTEL Analysis: the host-economy bet
URL: https://frameworklist.com/examples/world-cup-2026-pestel-analysis
> A PESTEL analysis of the 2026 World Cup host economy — FIFA's $30.5B windfall promise versus the realized macro impact across the USA, Canada, and Mexico.

PESTEL is the framework for the question no scoreboard answers: when a mega-event lands on a country, do the *external macro forces* around it actually leave the host economy better off? It scans six of them — Political, Economic, Social, Technological, Environmental, Legal — and it is the right lens for the 2026 World Cup precisely because the headline coverage measures the wrong thing. The match schedule and the revenue records describe FIFA's business. PESTEL describes the *host* economy — the USA, Canada, and Mexico — where the [2026 World Cup kicks off on June 11](https://www.euronews.com/business/2026/06/02/the-2026-world-cup-billions-promised-but-will-the-economic-boom-arrive) across 16 cities, and where FIFA's promised windfall meets six forces that will decide whether it lands.

## Position being analyzed

FIFA has promised the host nations a [roughly $30.5B economic windfall](https://www.euronews.com/business/2026/06/02/the-2026-world-cup-billions-promised-but-will-the-economic-boom-arrive) and as much as $40.9B in additional global GDP, alongside an estimated 824,000 jobs. The tournament itself is the most lucrative ever — about [$11B in revenue](https://www.sportsvalue.com.br/en/the-2026-fifa-world-cup-will-be-the-most-lucrative-in-history-with-revenues-expected-to-exceed-us-10-9-billion/), up ~47% on Qatar 2022. But those are FIFA's numbers and FIFA's P&L. The strategic question for a host-nation policymaker, investor, or city is different: net of the macro forces, does the World Cup actually grow *our* economy, or does it deliver a localized, time-limited blip dressed up as a boom? PESTEL is built to answer exactly that — by separating the forces pushing the host-economy case forward from the ones quietly cancelling it out.

## PESTEL scorecard for the 2026 World Cup host economy

| Force | Net direction for the host economy | The fact that defines it |
|---|---|---|
| **Political** | Headwind | A US travel ban covering 39 nations bars fans from four qualified countries, suppressing international demand |
| **Economic** | Marginal tailwind | The ~$17B US boost is under 0.1% of GDP; Mexico (~$3B) is the relative winner at 0.2–0.5% of GDP |
| **Social** | Mixed | 5–7M visitors projected, but ~80% of US host-city hotels report bookings below forecast |
| **Technological** | Tailwind (for FIFA) | $4.4B broadcast rights and streaming scale monetise the event globally — more than they lift host cities |
| **Environmental** | Headwind | An estimated 7.8–9M tonnes of CO₂, likely the most polluting World Cup ever; 87% from fan travel |
| **Legal** | Headwind | Cross-border immigration law (visa bonds, B1/B2 suspensions) is in open tension with FIFA's "most inclusive" pledge |

## Political — the travel-ban contradiction

This is the force that defines the 2026 host economy, and it points the wrong way. A US presidential proclamation that began in June 2025 covering 19 countries [expanded to 39 nations by December 2025](https://www.americanimmigrationcouncil.org/blog/travel-ban-impact-on-2026-world-cup-draw/), and it directly affects four qualified World Cup nations — [Haiti, Iran, Côte d'Ivoire, and Senegal](https://www.npr.org/2026/05/16/nx-s1-5770562/iran-and-haiti-qualified-for-the-world-cup-but-face-u-s-travel-bans-affecting-fans) — whose ordinary fans are largely barred from entering the US, with B1/B2 visitor-visa issuance suspended across most affected countries. Players and essential staff are exempt, and [ticketholders from some bond-listed countries had visa bonds waived](https://time.com/article/2026/05/14/fifa-world-cup-us-visa-bonds-waiver-immigration-ice/), but the headline stands: a tournament FIFA marketed as the most inclusive ever is being hosted under the tightest US entry regime in decades. For the host economy, the Political force isn't an abstraction — it is the demand suppressor sitting upstream of every hotel night and ticket that doesn't get sold.

## Economic — the marginal-percentage reality

Strip the billions down to percentages and the boom shrinks. The FIFA-aligned ~$17B US figure amounts to [less than 0.1% of US GDP](https://www.euronews.com/business/2026/06/02/the-2026-world-cup-billions-promised-but-will-the-economic-boom-arrive) — statistically a rounding error nationally. The impact is real but *local*: host cities are estimated to see $160–620M in incremental activity each, with net benefits of roughly $90–480M after costs. And the percentage flips by geography — Mexico's smaller economy turns an estimated ~$3B into 0.2–0.5% of GDP, making it the relative winner of the tri-national split, while Canada lands around CAD 3.8B. The economists' standard caveats apply in full: substitution (tournament spending replaces other local spending) and crowding-out (displaced conventions, deterred regular tourists) mean a chunk of the gross number was never net new. Economic is a tailwind — just a far smaller one than the press release implies.

## Social — the visitor surge that may not arrive

The promise is a human wave: [5–7 million international visitors](https://www.euronews.com/business/2026/06/02/the-2026-world-cup-billions-promised-but-will-the-economic-boom-arrive) across the 16 host cities, 150,000+ temporary jobs directly, and more than 250,000 once indirect employment is counted. The reality check is already in the booking data: a survey of more than 200 hotels across the 11 US host cities found nearly **80% reporting bookings below initial forecasts**, citing visa wait times, geopolitical tension, and steep ticket and travel prices. The Social force is genuinely two-sided — the legacy, civic pride, and soft-power upside are real and durable — but the leading indicator that matters for the host-economy case (rooms actually booked) is flashing amber, not green.

## Technological — a distribution upgrade that mostly accrues to FIFA

The 2026 tournament is the most technologically monetised ever: [$4.4B in broadcast rights](https://www.sportsvalue.com.br/en/the-2026-fifa-world-cup-will-be-the-most-lucrative-in-history-with-revenues-expected-to-exceed-us-10-9-billion/), FIFA+ streaming, and an expanding gaming ecosystem extend the event to audiences who never travel. For the *host* economy, technology cuts a narrower way: it powers cross-border ticketing, transport, and security coordination across three countries and 104 matches, and — unlike Qatar — it runs on existing venues rather than new builds, lowering construction and stranded-asset risk. But the lion's share of the technological upside (global reach, data, advertising) flows to FIFA's balance sheet, not to the host cities. Tailwind, with the arrow pointing mostly at the organiser.

## Environmental — the most polluting World Cup ever

The Environmental force is an unambiguous headwind, and it is getting louder as kickoff nears. Independent estimates put the tournament's footprint at [around 7.8 million tonnes of CO₂](https://time.com/article/2026/06/03/carbon-emissions-2026-fifa-world-cup/) (carbon-accounting platform Greenly) to [roughly 9 million tonnes](https://www.sgr.org.uk/resources/2026-fifa-men-s-world-cup-be-most-polluting-ever) (Scientists for Global Responsibility) — close to double the average of recent World Cups and more than double Qatar 2022's official figure. The cause is structural: [spectator travel accounts for about 87% of emissions](https://www.insideworldfootball.com/2026/06/04/fan-travel-carbon-footprint-fifa-world-cup/), because a 48-team, 16-city, three-country format means far more fans flying far greater distances. The one bright spot is that reusing existing stadiums keeps infrastructure to ~3.1% of the footprint versus 24.6% for Qatar's seven new builds. For host nations carrying public climate commitments, the reputational and regulatory exposure here is a cost the windfall math rarely books.

## Legal — the cross-border entry regime

PESTEL's Legal force here is dominated by one theme: immigration and entry law, operating across three sovereign jurisdictions. The same proclamation that drives the Political headwind creates concrete legal friction — [visa bond requirements, B1/B2 suspensions, and country-specific exemptions](https://time.com/article/2026/05/14/fifa-world-cup-us-visa-bonds-waiver-immigration-ice/) — that fans, and the cities banking on them, must navigate. Layer on a tournament governed by FIFA's standard host-country guarantees and commercial protections, enforced across US, Canadian, and Mexican law, and the result is a legal surface area far larger than a single-host event. For the host economy, Legal is less a discrete shock than the connective tissue that determines how much of the promised demand can physically, lawfully, show up.

## The World Cup Host-Economy Gap

Here is the synthesis worth keeping — a named diagnostic for reading any mega-event host claim, grounded in the 2026 numbers. **The World Cup Host-Economy Gap** is the distance between the windfall a host is *promised* and the macro impact it actually *realises*, and it has four predictable components: the headline figure is (1) marginal as a share of GDP, (2) time-limited to a few weeks, (3) localized to a handful of host-city sectors, and (4) partly offset by substitution and crowding-out. 2026 adds a fifth, edition-specific component: the Political–Legal travel regime is suppressing the very international demand the windfall is built on.

| Host nation | Promised benefit | Share of GDP | The catch PESTEL surfaces |
|---|---|---|---|
| **United States** | ~$17B | under 0.1% | Largest absolute figure, smallest macro signal; travel ban + booking shortfall hit hardest here |
| **Mexico** | ~$3B | 0.2–0.5% | Relative winner — a smaller economy turns the same kind of event into a larger percentage |
| **Canada** | ~CAD 3.8B | sub-1% | Real but modest; benefits concentrated in two host cities, weighed against public cost |
| **All three** | ~$30.5B combined | — | Gross, not net; substitution, crowding-out, and ~80% below-forecast hotel bookings erode it |

The Gap isn't a reason to skip hosting — civic, legacy, and soft-power returns sit outside GDP. It's a reason to stop quoting the gross windfall as if it were net new growth.

## Key takeaway

PESTEL on the 2026 host economy delivers a verdict the revenue headlines obscure: **FIFA's tournament is booming; the host-economy case is real but oversold, and currently bounded by its own Political and Environmental forces.** Two of the six forces (Political travel restrictions, Environmental emissions) are genuine headwinds; Economic is a marginal-positive concentrated unevenly, with Mexico the relative winner; Social is hanging on the booking numbers; Technological and Legal mostly route value and complexity to FIFA and the entry regime rather than to host cities. The framework's contribution is discipline: it stops the analysis at "is the macro environment net-favourable for the host?" instead of letting the $30.5B promise stand unchallenged. The post-tournament accounts will settle the size of the Host-Economy Gap — PESTEL just makes sure someone measured it before the confetti.

## Want to go deeper

This is the macro-environment companion to our [World Cup 2026 strategy series](/series/world-cup-2026) — where the [FIFA Ansoff Matrix 2026](/examples/fifa-ansoff-matrix-2026) reads the *organiser's* growth bet and the club analyses (Real Madrid, PSG, Barcelona, Manchester City) read the *teams*. PESTEL is the layer above all of them: the forces none of those organisations control. New to the model? Read the [PESTEL framework](/frameworks/pestel), then compare it with the industry lens in [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces). For the same six-force scan on a single company, see the [Amazon PESTEL analysis 2026](/examples/amazon-pestel-analysis-2026) and [Apple PESTEL analysis 2026](/examples/apple-pestel-analysis-2026), or browse other [strategy framework examples](/examples). And for the scan run on one of the three host economies in its own right — not as a tournament venue — the [PESTEL Analysis of the USA (2026)](/examples/usa-pestel-analysis-2026) covers the American macro environment the tournament actually landed in: 1.5% GDP growth, a negative July payroll print, and a data-centre boom straining the same power grid the host cities run on. The [PESTEL Analysis of Mexico (2026)](/examples/mexico-pestel-analysis-2026) checks this page's call that Mexico would be the relative winner: Q2 2026 GDP grew 1.4% quarter on quarter, the best since 2020, and Banco Base attributed about two-thirds of that growth to World Cup spending, while warning of a Q3 payback.

To run a PESTEL analysis on a market or event you're tracking, [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) ships with the model and AI assistance for each of the six forces.

---

## Compare

### Ansoff Matrix vs BCG Matrix: which growth framework to use
URL: https://frameworklist.com/compare/ansoff-matrix-vs-bcg-matrix
> The BCG Matrix reads the portfolio you already have. The Ansoff Matrix picks the growth you'll fund next. One is a diagnosis, the other a prescription — here's which to run, and how they hand off.

The Ansoff Matrix and the BCG Matrix are the two 2×2 grids every strategy course teaches back-to-back, and the two students most often blur together — both have four quadrants, both live on a whiteboard, both get drawn during the same planning offsite. But they do opposite jobs. The BCG Matrix is a **diagnosis** of the portfolio you already own; the Ansoff Matrix is a **prescription** for the growth you don't have yet. One reads the map; the other picks the road.

## At a glance

| | Ansoff Matrix | BCG Matrix |
|---|---|---|
| What it does | Prescribes a growth direction | Diagnoses the current portfolio |
| The two axes | Product newness × Market newness | Market growth rate × Relative market share |
| Quadrants | Market Penetration, Market Development, Product Development, Diversification | Stars, Cash Cows, Question Marks, Dogs |
| Question answered | "Where should we grow next, and how risky is it?" | "Which units make cash, and which consume it?" |
| Time orientation | Forward — the next bet | Present — a snapshot of what exists |
| Unit of analysis | A growth move (product × market) | A business unit or product line |
| Output | 4 growth vectors ranked by risk | 4 quadrants ranked by cash role |
| Origin | Igor Ansoff, *Harvard Business Review*, 1957 | Bruce Henderson / BCG, 1970 |
| Best for | Choosing and pricing the next growth bet | Allocating capital across an existing portfolio |

## What the BCG Matrix is best for

The BCG Growth-Share Matrix earns its place when you have **several distinct business units** and the question is *where the cash is*:

- **Capital allocation across a portfolio** — the core use. Which units are self-funding Cash Cows, which Stars need continued investment to hold share, which Question Marks demand a commit-or-divest decision, and which Dogs are quietly consuming management attention. See the worked [Nvidia BCG Matrix analysis](/examples/nvidia-bcg-matrix) — one Star (Data Center) so dominant it distorts the whole grid, with Gaming as the textbook Cash Cow — and the [Barcelona BCG Matrix (2026)](/examples/barcelona-bcg-matrix-2026) for the same lens applied to a football club's revenue lines.
- **Spotting portfolio imbalance** — BCG is designed to make concentration and neglect visible. A portfolio that's all Question Marks is over-extended; one that's all Cash Cows is quietly dying.
- **Divestment discipline** — the Dog quadrant exists to force the unsentimental question most teams avoid: what should we stop doing?

What BCG does *not* do: it never tells you what to *build* next. It sorts what exists; it's blind to the product or market you haven't entered.

## What the Ansoff Matrix is best for

The Ansoff Matrix earns its place when the decision is **where to grow** and how much risk that growth carries:

- **Choosing a growth vector** — the core use. Sell more to current customers (Market Penetration, lowest risk), take the current product to new customers (Market Development), build new products for current customers (Product Development), or both at once (Diversification, highest risk). [Full Ansoff walk-through with examples →](/academy/ansoff-matrix-examples)
- **Pricing the risk of a bet** — Ansoff's real value is the diagonal: risk rises as you move from top-left to bottom-right. See the worked [Nvidia Ansoff Matrix (2026)](/examples/nvidia-ansoff-matrix-2026), where the RTX Spark PC chip scores as Diversification despite feeling like Product Development, and [Tesla's Ansoff Matrix](/examples/tesla-ansoff-matrix) for a company running all four quadrants at once. For evidence that the risk ordering is real rather than asserted, the [Apple Ansoff Matrix example (2026)](/examples/apple-ansoff-matrix-2026) attaches actual segment revenue to each quadrant and finds the outcomes degrade in Ansoff's predicted order — records in Market Penetration, a halted production line in Diversification.
- **Any size of company** — unlike BCG, Ansoff works for a one-product startup, because every business faces the same four choices regardless of whether it has a "portfolio."

What Ansoff does *not* do: it doesn't tell you whether you can *afford* the bet. It prices risk but says nothing about which existing unit generates the cash to fund it — which is exactly the gap BCG fills.

## The decision rule

> **Use the BCG Matrix to see where your cash is. Use the Ansoff Matrix to decide where that cash should grow you next. Run BCG first when you have a real portfolio; run Ansoff alone when you have one product and a decision to make.**

Concretely:

- Several business units and a capital-allocation question ("what do we fund, hold, or cut?") → **BCG**.
- One product, or a specific "where do we grow next?" question → **Ansoff**.
- A full annual strategy cycle → **both, BCG first** — diagnose the portfolio, then prescribe the growth.

Nvidia in 2026 is the cleanest real example of the sequence. Read through **BCG**, its portfolio is a diagnosis: Data Center is the [dominant Star at ~88% of revenue](/examples/nvidia-bcg-matrix), Gaming is the mature Cash Cow, Automotive and Networking are Question Marks. That diagnosis is *why* the [Ansoff](/examples/nvidia-ansoff-matrix-2026) move at Computex made sense — the Gaming cash and the Data Center margin are what underwrite two simultaneous Diversification bets (the RTX Spark consumer PC chip and the Isaac GR00T humanoid robot). BCG told Nvidia where the cash was; Ansoff told it where to spend it. Neither framework alone explains the strategy; the handoff between them does.

## The Portfolio-to-Growth Handoff

Here is the synthesis Framework's compare library is built to support — a named way to connect the two grids so the diagnosis actually drives the prescription instead of sitting in a separate slide. We call it the **Portfolio-to-Growth Handoff**: each BCG quadrant implies a *default* Ansoff move, and the cash flows in one direction across the map.

| BCG quadrant (diagnosis) | Cash role | Default Ansoff vector (prescription) | Why the handoff works |
|---|---|---|---|
| **Cash Cow** | Generates surplus cash | Funds **Diversification** & new **Market Development** | Predictable margin is the only safe way to underwrite a high-risk new-product/new-market bet |
| **Star** | Cash-neutral, must hold share | **Market Penetration** + **Product Development** | Keep pouring into the growing market you already lead; don't wander while the Star is still climbing |
| **Question Mark** | Consumes cash, unproven | **Product Development** or exit | Commit enough to prove the thesis, or divest — the same commit-or-cut call Ansoff frames as risk |
| **Dog** | Ties up capital | **Divest** → redeploy to another vector | The freed capital becomes fuel for a Penetration or Development bet elsewhere |

Read the table top to bottom and the money moves in a loop: **Cash Cows and divested Dogs fund the risky vectors; Stars stay focused; Question Marks earn or lose their funding.** Nvidia runs exactly this loop — Gaming Cash Cow + Data Center Star cash → funds the RTX Spark and GR00T Diversification bets, while the company has [historically divested its Dogs](/examples/nvidia-bcg-matrix) (Tegra mobile) rather than nurse them. When teams draw the two matrices on separate slides and never link them, they lose this loop — and end up funding Diversification out of hope instead of out of a Cash Cow.

## Edge cases and combined use

- **Small companies skip BCG.** With one product line, three BCG quadrants are empty and the diagnosis is trivial. Run Ansoff alone until you have three or more genuinely separate units with their own P&Ls.
- **BCG's Dog can launch an Ansoff bet.** A low-share, low-growth unit is sometimes worth keeping *if* it owns a channel or brand you can extend — that's a Product Development launchpad hiding inside a Dog. The frameworks only "disagree" when the portfolio diagnosis is ignored in the growth decision.
- **Neither is the right tool for *whether the market itself is attractive*.** BCG and Ansoff both assume the market is worth playing in. To judge that, step out to [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) — the macro-and-industry layer that sits *above* both of these portfolio-and-growth grids.
- **When BCG's 2×2 is too coarse for a large portfolio**, don't force the diagnosis into four boxes — step up to the nine-box. [BCG Matrix vs GE-McKinsey Matrix](/compare/bcg-matrix-vs-ge-mckinsey-matrix) covers exactly when two axes stop being enough and the multi-factor grid earns its extra hour.
- **For product-level, not portfolio-level, prioritization**, both are too coarse — use [RICE](/academy/rice-prioritization-framework) or the [Eisenhower Matrix](/academy/eisenhower-matrix-urgent-vs-important).

## In 30 seconds

Diagnose the portfolio you own → **BCG**. Prescribe the growth you'll fund next → **Ansoff**. A full strategy cycle → **both, BCG first**, connected by the [Portfolio-to-Growth Handoff](#the-portfolio-to-growth-handoff) so your Cash Cows actually fund your next bet instead of your slide deck.

New to the BCG side of this comparison? [BCG Matrix Analysis: The Four Quadrants Explained](/academy/bcg-matrix-analysis-explained) walks the methodology with Apple's 2026 portfolio. See BCG worked end to end on a real portfolio in the [SpaceX BCG Matrix Analysis 2026](/examples/spacex-bcg-matrix-2026), where the four quadrants form a self-funding flywheel, or the [Nvidia BCG Matrix Analysis 2026](/examples/nvidia-bcg-matrix) for a single-Star portfolio.

> Want to run these on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — fill in the Ansoff Matrix, BCG Matrix, or any of 100+ frameworks with AI assistance.

## Sources

- [Igor Ansoff — "Strategies for Diversification," Harvard Business Review (1957)](https://hbr.org/1957/09/strategies-for-diversification)
- [Bruce Henderson — "The Product Portfolio," BCG Perspectives (1970)](https://www.bcg.com/publications/1970/strategy-the-product-portfolio)
- [Institute for Strategy & Competitiveness, Harvard Business School — strategy frameworks overview](https://www.isc.hbs.edu/strategy/business-strategy/Pages/default.aspx)

---

### BCG Matrix vs GE-McKinsey Matrix: which portfolio grid to use
URL: https://frameworklist.com/compare/bcg-matrix-vs-ge-mckinsey-matrix
> The BCG Matrix sorts a portfolio on two axes; the GE-McKinsey Matrix scores it on nine boxes. One is a fast triage, the other adjudicates the ties — here's which to run, and when 2×2 stops being enough.

The BCG Matrix and the GE-McKinsey Matrix are the two portfolio grids every strategy course teaches back-to-back, and the two most often mistaken for the same tool with different box counts. They share a job — deciding where to invest, hold, harvest, or exit across a set of business units — but they take opposite bets on how much resolution that job needs. The BCG Matrix is a **fast two-axis triage**; the GE-McKinsey Matrix is a **nine-box adjudicator**. One is built for speed and objectivity, the other for nuance.

## At a glance

| | BCG Matrix | GE-McKinsey Matrix |
|---|---|---|
| Grid | 2×2 (four boxes) | 3×3 (nine boxes) |
| The two axes | Market growth rate × relative market share | Industry attractiveness × business-unit strength |
| Axis inputs | One measurable metric each | A composite of several weighted factors each |
| Boxes | Stars, Cash Cows, Question Marks, Dogs | Nine cells → Invest / Hold / Harvest zones |
| Question answered | "Which units make cash, which consume it?" | "Where is each unit strong, in a market worth winning?" |
| Strength | Fast, objective, hard to fudge | Nuanced, multi-factor, separates near-ties |
| Weakness | Too coarse for large or subtle portfolios | Subjective — factor choice and weighting can be gamed |
| Best for | Small portfolios; a defensible answer in an afternoon | Large portfolios; units BCG can't tell apart |
| Origin | Bruce Henderson / BCG, 1970 | McKinsey for General Electric, 1970s |

## What the BCG Matrix is best for

The BCG Growth-Share Matrix earns its place when you want a **fast, defensible read** on where the cash sits:

- **Triaging a portfolio quickly** — the core use. Two measurable axes mean you can classify a set of units in an afternoon, and because both axes are single numbers (not composites), the result is hard to argue with. See the four quadrants walked end-to-end in [BCG Matrix Analysis: The Four Quadrants Explained](/academy/bcg-matrix-analysis-explained), and worked on real portfolios in the [SpaceX BCG Matrix (2026)](/examples/spacex-bcg-matrix-2026) and [Nvidia BCG Matrix](/examples/nvidia-bcg-matrix).
- **Spotting portfolio imbalance at a glance** — all Question Marks means over-extended; all Cash Cows means quietly dying. The 2×2 makes concentration visible instantly.
- **Forcing the divestment question** — the Dog quadrant exists to make teams say out loud what they should stop doing.

What BCG does *not* do well: it collapses when several units land in the same box but clearly aren't equal, and its two axes ignore everything that isn't growth or share — margins, regulation, brand, capital intensity.

## What the GE-McKinsey Matrix is best for

The GE-McKinsey nine-box earns its place when the portfolio is **too large or too subtle for two axes** to resolve:

- **Allocating across many units** — this is literally why it exists. McKinsey built it for [General Electric](https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/enduring-ideas-the-ge-and-mckinsey-nine-box-matrix), whose dozens of divisions overwhelmed BCG's four boxes. Nine cells give enough resolution to rank units BCG would pile together.
- **Scoring on more than growth and share** — industry attractiveness folds in market size, margins, competitive intensity and regulation; business strength folds in brand, cost position, and capability. When those factors drive the decision, GE-McKinsey captures them and BCG can't.
- **Separating the near-ties** — two units that both read as "Question Mark" in BCG can land in visibly different nine-box cells once you score them on multiple weighted factors.

What GE-McKinsey does *not* do well: because you choose and weight the factors, the scoring is subjective and easy to game to justify a pet project. It's also slower — the nuance costs an extra hour and a debate about weights.

## The decision rule

> **Use the BCG Matrix to triage the whole portfolio fast. Use the GE-McKinsey Matrix on the units the triage can't separate. Two axes when growth and share are the whole story; nine boxes when they aren't.**

**Alphabet's 2026 portfolio** is the cleanest live illustration of why one grid isn't enough. Run **BCG** across it and the obvious units sort themselves immediately: Search and YouTube advertising inside [Google Services](https://abc.xyz/investor/) are the mature, cash-generating **Cash Cow**; Google Cloud — which [crossed into operating profit in 2023](https://blog.google/inside-google/message-ceo/alphabet-earnings-q4-2023/) and kept growing — reads as the **Star**. That's the two-axis triage doing its cheap, useful work.

But BCG stalls on the **Other Bets**. Waymo, Verily, Isomorphic and the rest all read the same way on BCG's axes — tiny relative share in high-growth markets, i.e. a pile of indistinguishable Question Marks. That's exactly the ambiguity BCG can't resolve, and where **GE-McKinsey** pays for itself: score each bet on *industry attractiveness* (robotaxi TAM and regulatory tailwind for [Waymo, which expanded paid rides across multiple US cities through 2026](https://www.reuters.com/business/autos-transportation/)) and *business strength* (Waymo's mileage-and-safety lead versus an earlier-stage bet), and the nine-box separates a "selectively invest" unit from a "harvest or exit" one that BCG had glued together. BCG told Alphabet which units throw off cash; GE-McKinsey told it which of the cash-consuming bets is actually worth the cash.

The same split shows up in consumer goods. [Unilever](https://www.unilever.com/investors/) — the textbook nine-box user, with dozens of brands and a [2025 demerger of its ice-cream business](https://www.reuters.com/business/retail-consumer/) — can't run its portfolio on growth-and-share alone, because two brands with identical share sit in wildly different-margin, differently-regulated categories. That's a GE-McKinsey portfolio by nature. A three-product startup is the opposite: BCG is all it will ever need.

## The Resolution Test

Here is the synthesis Framework's compare library is built to support — a named way to decide *which grid your portfolio actually needs*, instead of defaulting to whichever one the last consultant drew. We call it the **Resolution Test**: run BCG first as the cheap triage, then escalate to GE-McKinsey only on the units that fail one of three questions.

| Diagnostic question | If NO → BCG is enough | If YES → escalate to GE-McKinsey |
|---|---|---|
| Do two or more units land in the **same BCG quadrant** but clearly shouldn't be funded the same? | The 2×2 already separates them | You need the nine-box to rank the tie |
| Do factors **beyond growth and share** (margin, regulation, brand, capital intensity) drive the call? | Growth × share is the whole story | Composite axes capture what BCG ignores |
| Is the portfolio **large** (roughly 6+ genuinely distinct units)? | Four boxes hold it fine | Four boxes are too coarse; use nine |

Read it top to bottom: **BCG does the cheap sorting; GE-McKinsey is the extra hour you spend only where BCG's four boxes are demonstrably too blunt.** Alphabet passes the test on its core segments (BCG is fine for Search-vs-Cloud) and fails it on Other Bets (the Question Marks need nine-box resolution) — which is why the honest answer to "BCG or GE-McKinsey?" for most real portfolios is *both, in that order*. Teams that pick one grid for the whole portfolio either over-simplify the ambiguous units (BCG-only) or waste an hour scoring factors on units that were never in doubt (GE-McKinsey-only).

## Edge cases and combined use

- **Small companies never need GE-McKinsey.** With a handful of units, the nine-box is false precision — you'll spend an hour debating factor weights to separate units BCG already told apart. Run [BCG](/academy/bcg-matrix-analysis-explained) alone until you have six or more genuinely distinct units.
- **GE-McKinsey's subjectivity is a governance risk.** Because you weight the factors, a division head can lobby the weights to move their unit into "Invest." Fix it by setting the attractiveness/strength factors *before* anyone knows which unit is being scored.
- **Neither judges whether the market is worth playing in the first place.** Both assume the industries are given. To pressure-test attractiveness itself, step out to [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) — the macro-and-industry layer above both portfolio grids.
- **Neither tells you what to build next.** Both diagnose the portfolio you own; to prescribe the growth you don't yet have, hand off to the [Ansoff Matrix — see Ansoff vs BCG](/compare/ansoff-matrix-vs-bcg-matrix) for how the diagnosis feeds the growth decision.
- **For product-level, not portfolio-level, prioritization**, both are far too coarse — use [RICE](/academy/rice-prioritization-framework) or the [Eisenhower Matrix](/academy/eisenhower-matrix-urgent-vs-important).

## In 30 seconds

Fast triage of a small portfolio on growth and share → **BCG**. Many units, or units BCG can't tell apart, or factors beyond growth and share → **GE-McKinsey**. For most real portfolios the answer is **both, BCG first**, connected by the [Resolution Test](#the-resolution-test) so you only spend nine-box effort where two boxes were genuinely too blunt.

New to these grids? Start with [BCG Matrix Analysis: The Four Quadrants Explained](/academy/bcg-matrix-analysis-explained), then see the two-axis diagnosis worked on a real portfolio in the [SpaceX BCG Matrix Analysis 2026](/examples/spacex-bcg-matrix-2026). For the growth side of portfolio strategy, read [Ansoff Matrix vs BCG Matrix](/compare/ansoff-matrix-vs-bcg-matrix).

> Want to run these on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — fill in the BCG Matrix, GE-McKinsey Matrix, or any of 100+ frameworks with AI assistance.

## Sources

- [Bruce Henderson — "The Product Portfolio," BCG Perspectives (1970)](https://www.bcg.com/publications/1970/strategy-the-product-portfolio)
- [McKinsey — "Enduring Ideas: The GE–McKinsey nine-box matrix"](https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/enduring-ideas-the-ge-and-mckinsey-nine-box-matrix)
- [Alphabet Inc. — Investor Relations (segment reporting: Google Services, Google Cloud, Other Bets)](https://abc.xyz/investor/)
- [Alphabet — "Q4 2023 earnings" (Google Cloud reaches full-year operating profit)](https://blog.google/inside-google/message-ceo/alphabet-earnings-q4-2023/)
- [Reuters — autos & transportation coverage (Waymo robotaxi expansion)](https://www.reuters.com/business/autos-transportation/)
- [Unilever — Investor Relations (portfolio and 2025 ice-cream demerger)](https://www.unilever.com/investors/)

---

### Cynefin vs Stacey Matrix: which complexity framework to use
URL: https://frameworklist.com/compare/cynefin-vs-stacey-matrix
> Stacey diagnoses why a problem is hard — knowledge gap or disagreement. Cynefin decides how to respond. Here's which complexity framework to use, and how to run both together.

The Cynefin Framework and the Stacey Matrix are the two models managers reach for when a project feels harder than its plan admits — and the two most often confused, because both draw a line between *complicated* and *complex*. The distinction is one of job. The [Stacey Matrix](/frameworks/stacey) **diagnoses** why a situation is uncertain: are you missing knowledge, or missing agreement? [Cynefin](/frameworks/cynefin) **prescribes** what to do about it: follow a runbook, call in experts, run experiments, or stabilize first. Stacey reads the cause; Cynefin sets the response.

## At a glance

| | Stacey Matrix | Cynefin Framework |
|---|---|---|
| What it does | Diagnoses *why* a problem is hard | Prescribes *how* to respond |
| Structure | Two axes: certainty × agreement | Five domains, no axes |
| Components | Simple, Complicated, Complex, Chaotic (Anarchy) | Clear, Complicated, Complex, Chaotic, Confused |
| Distinctive lever | The **agreement** axis — surfaces stakeholder politics | The **response** for each domain (e.g. probe-sense-respond) |
| Question answered | "Is this a knowledge gap or a disagreement gap?" | "What action does this kind of situation demand?" |
| Best for | Choosing a delivery method (agile / waterfall / expert-led) | Decision-making across projects, incidents, and crises |
| Origin | Ralph D. Stacey, 1996 | Dave Snowden, IBM, 1999 |
| Watch out for | Treating it as a static map you only read once | The central "confused" state — not knowing which domain you're in |

## What the Stacey Matrix is best for

Stacey earns its place when the useful question is *what kind of uncertainty are we dealing with* — because its two axes split "this is hard" into two very different causes:

- **Methodology selection.** Stacey maps cleanly onto delivery approaches: close to certainty *and* agreement → plan-driven (waterfall); far from both → iterative ([agile](/academy/strategy-framework-decision-map)); far on one axis only → resolve that axis first. It's the framework most often drawn on a whiteboard to justify "why we're running this one agile."
- **Surfacing politics, not just unknowns.** The agreement axis is Stacey's unique contribution. A project can be perfectly understood technically and still sit in the danger zone because stakeholders disagree on the goal. Stacey forces that onto the page; most problem-only models bury it.
- **Diagnosing where the work is.** Far from certainty means the bottleneck is *knowledge* — you need research, experts, or a spike. Far from agreement means the bottleneck is *alignment* — you need negotiation, a clearer mandate, or a decision owner. Naming which axis is far tells you which lever to pull.

What Stacey does *not* do: it stops at the diagnosis. It plots where you are but doesn't prescribe the operating rhythm once you know.

## What Cynefin is best for

Cynefin earns its place when the question is *what do we actually do now* — it pairs each kind of situation with a response:

- **Matching response to context.** Each domain has a prescribed sequence: sense-categorize-respond (clear), sense-analyze-respond (complicated), probe-sense-respond (complex), act-sense-respond (chaotic). That last one — *act first, then sense* — is why Cynefin handles crises that Stacey's static map doesn't speak to. See the full breakdown in the [Cynefin Framework for PMP guide](/academy/cynefin-framework-for-pmp).
- **Beyond software.** Cynefin covers incident response, policy design, and live crises, not just project delivery. When a system is on fire, "probe" is the wrong first move; Cynefin tells you to stabilize, then analyze — the same instinct a [premortem](/academy/how-to-run-a-premortem) builds in advance.
- **Catching the misclassification trap.** Cynefin's central "confused" domain is its sharpest idea: the most dangerous position is not knowing which domain you're in, because you default to the approach you're most comfortable with — usually treating a complex problem as a merely complicated one.

What Cynefin does *not* do: it won't tell you *why* you're uncertain. It names the domain but not whether the fix is knowledge or alignment.

## The decision rule

> **Use the Stacey Matrix to diagnose the source of difficulty — a knowledge gap (low certainty) or a politics gap (low agreement). Use Cynefin to choose the response once you know the domain. When in doubt, run Stacey first, then Cynefin: read, then act.**

The cost of skipping the diagnosis is concrete. In 2023, **Klarna** replaced roughly [700 customer-service agents](https://www.entrepreneur.com/business-news/klarna-ceo-reverses-course-by-hiring-more-humans-not-ai/491396) with an OpenAI-trained assistant that soon handled two-thirds of all support chats. The decision was framed as *complicated* — a known efficiency problem with a known solution: automate the routine, cut the cost. On the Stacey axes it was nothing of the sort. It sat far from **certainty** (no one knew how the model would handle emotionally charged disputes, multi-step refunds, or [confidently-wrong answers about fees and policy](https://www.digitalapplied.com/blog/klarna-reverses-ai-layoffs-replacing-700-workers-backfired) — a compliance risk in fintech) and far from **agreement** (customers, agents, and regulators were not aligned on AI handling money disputes). That puts it squarely in the **complex** zone, where Cynefin prescribes *probe-sense-respond* — safe-to-fail pilots, not a one-shot replacement of 700 people.

By mid-2025 Klarna [reversed course and began rehiring humans](https://www.fintechweekly.com/magazine/articles/klarna-hires-customer-service-after-ai-pivot); CEO Sebastian Siemiatkowski conceded the company "focused too much on efficiency and cost" and that "the result was lower quality, and that's not sustainable." Stacey's agreement axis would have flagged the stakeholder conflict the efficiency framing ignored; Cynefin would have set the cadence — experiment, don't replace. The two frameworks together describe exactly the mistake, which is the strongest argument for running them in sequence.

## The Stacey Read, Cynefin Act Sequence

Here is the synthesis this comparison was built to support — a named way to chain the two frameworks so the diagnosis feeds the response instead of duplicating it. We call it the **Stacey Read, Cynefin Act Sequence**: Stacey *reads* the two axes to tell you which lever to pull; Cynefin *acts* by setting the operating rhythm.

| Certainty | Agreement | Stacey zone | Cynefin domain | What to actually do |
|---|---|---|---|---|
| High | High | Simple | Clear | Run the playbook — plan-driven delivery, best practice, waterfall |
| Low **or** Low (one axis far) | — | Complicated | Complicated | Pull the matching lever: experts/research if it's a **knowledge** gap; negotiation or a decision owner if it's an **agreement** gap |
| Low | Low | Complex | Complex | Probe-sense-respond — short iterations, safe-to-fail experiments (agile) |
| None | None | Chaotic / anarchy | Chaotic | Act first to stabilize, then sense — don't experiment in a fire |

The insight the table encodes is the one neither framework gives alone: **Stacey splits uncertainty into two causes — a certainty (knowledge) axis and an agreement (politics) axis — that Cynefin collapses into a single "complex" bucket.** So Stacey tells you *whether to send in experts or a mediator*; Cynefin tells you *the cadence to run once they're in the room*. Klarna's mistake reads cleanly on this table: it acted on the top row (Simple → run the playbook) while sitting on the third (Complex → experiment first).

## Edge cases and combined use

- **One axis far, not both.** This is the most useful Stacey reading and the one teams skip. If you're certain *how* to do the work but stakeholders disagree on *whether* to, no amount of expert analysis helps — you have a Complicated-by-disagreement problem, and the fix is a mandate, not a spike. Cynefin alone would miss this, because it has no agreement axis.
- **Chaotic vs Complex.** Both frameworks warn against confusing these, but only Cynefin gives the rule: in chaos you *act first* (stabilize), in complexity you *probe first* (experiment). Running a safe-to-fail experiment during a live outage is the classic error.
- **When neither is the right tool.** For prioritizing a known backlog, both are too abstract — use [RICE](/academy/rice-prioritization-framework). For a specific risky launch, a [premortem](/academy/how-to-run-a-premortem) is sharper than a domain label. For surfacing the macro forces *around* a complex market rather than inside your project, that's [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) territory.

## In 30 seconds

*Why* is this hard — knowledge or agreement? → **Stacey Matrix**. *What do I do* about it — plan, analyze, experiment, or stabilize? → **Cynefin**. A genuinely uncertain initiative → run **both, Stacey first**, using [The Stacey Read, Cynefin Act Sequence](#the-stacey-read-cynefin-act-sequence) so the diagnosis sets the response. The framework you can name beats the one you only feel.

> Want to run these on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — fill in Cynefin, the Stacey Matrix, or any of 100+ frameworks with AI assistance.

## Sources

- [Ralph D. Stacey — "Complexity and Creativity in Organizations" (1996)](https://www.berrett-koehler.com/book/complexity-and-creativity-in-organizations/)
- [Dave Snowden & Mary Boone — "A Leader's Framework for Decision Making," Harvard Business Review (2007)](https://hbr.org/2007/11/a-leaders-framework-for-decision-making)
- [Entrepreneur — "Klarna Is Hiring Customer Service Agents After AI Couldn't Cut It on Calls"](https://www.entrepreneur.com/business-news/klarna-ceo-reverses-course-by-hiring-more-humans-not-ai/491396)
- [Digital Applied — "Klarna Reverses AI Layoffs: Why Replacing 700 Failed"](https://www.digitalapplied.com/blog/klarna-reverses-ai-layoffs-replacing-700-workers-backfired)
- [FinTech Weekly — "Klarna Reverses Course on AI Customer Support, Resumes Human Hiring"](https://www.fintechweekly.com/magazine/articles/klarna-hires-customer-service-after-ai-pivot)

---

### Eisenhower Matrix vs Covey Matrix: which time-management grid to use
URL: https://frameworklist.com/compare/eisenhower-matrix-vs-covey-matrix
> Eisenhower and Covey's Time Management Matrix are the same urgent/important 2×2 — but one triages today's tasks and the other redesigns your week.

The **Eisenhower Matrix** and **Covey's Time Management Matrix** are, structurally, the *same* grid — urgency across the top, importance down the side, four quadrants. The difference isn't the shape; it's the job. Eisenhower labels each quadrant with an **action** — *Do, Schedule, Delegate, Delete* — and exists to triage the tasks already in front of you today. Covey labels each quadrant with its **nature** — *Necessity, Quality, Deception, Waste* — and exists to change where your weeks go over the next few months, by pushing you to live in Quadrant II. One sorts your inbox; the other redesigns your calendar. Treating them as rivals is the mistake — you almost certainly need both, at different altitudes.

> **Want to run the grid on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=eisenhower-vs-covey) fills in an Eisenhower / urgent-important grid with AI-assisted sorting so you can triage a task list in a couple of taps. Free to start.

New to the underlying grid? See the [Eisenhower Matrix explained](/academy/eisenhower-matrix-urgent-vs-important) guide and the [Eisenhower Matrix catalog entry](/frameworks/eisenhower) for the mechanics before comparing the two lineages.

## At a glance

| | Eisenhower Matrix | Covey Time Management Matrix |
|---|---|---|
| **Quadrant labels** | Do / Schedule / Delegate / Delete (by action) | Necessity / Quality / Deception / Waste (by nature) |
| **Core question** | What do I do with *this* task? | Where is my *life* going, quadrant by quadrant? |
| **Time horizon** | Today / this week | This quarter / this year |
| **Primary move** | Triage: clear and route the current list | Invest: grow Quadrant II, shrink Quadrant I |
| **Unit of work** | A task | A pattern of how you spend time |
| **Origin** | The urgent/important distinction Eisenhower quoted in 1954 — from "a former college president," not from him; the grid itself is later ([see the provenance chain](#the-eisenhower-matrix-provenance-chain)) | Stephen Covey, *The 7 Habits of Highly Effective People* (1989) — this is where the four quadrants are actually published |
| **Best for** | Fast daily/weekly triage under overload | Long-term rebalancing away from constant firefighting |
| **Blind spot** | Says nothing about *why* you're overloaded | Too slow to help when 40 things are on fire right now |

## What the Eisenhower Matrix is best for

Eisenhower wins when the constraint is **a full plate and not enough hours today**. Its action labels are its value: every task lands in a quadrant that names your next move, so a messy list becomes a routed one in minutes.

Use the Eisenhower Matrix when:

- You have **more tasks than time this week** and need to decide what actually gets your hands
- Things keep arriving **urgent**, and you need a forcing function to separate the genuinely important ones
- You want a method **anyone on a team understands instantly** — Do/Schedule/Delegate/Delete needs no training
- You're an **operator in the thick of execution** — on-call, launch week, month-end — where the job is to clear and route, not reflect

Its blind spot: Eisenhower tells you what to do with each task but says nothing about *why your Quadrant I keeps refilling*. Run it every day and you can stay permanently, efficiently, on fire. That's the exact gap Covey was built to close.

## What Covey's matrix is best for

Covey wins when the risk is **being busy for years without moving the things that matter**. The [Covey Time Management Matrix](/academy/covey-time-management-matrix) isn't really a to-do triage tool; it's a diagnosis of your *life balance*. Covey's core teaching is that effective people deliberately spend more time in **Quadrant II** — important, not-yet-urgent work like planning, prevention, learning, and relationships — which over time starves Quadrant I of new crises.

Use Covey's matrix when:

- You're **always firefighting** (Quadrant I) and can't work out why the fires never stop
- You want to audit **how last month actually went**, not sort today's list — where did the hours go, quadrant by quadrant?
- You suspect you're losing time to **Quadrant III** (urgent-feeling interruptions that aren't important) disguised as real work
- You're doing **personal or strategic planning** and the question is *what deserves more of my life*, not *what do I do next*

Its blind spot: Covey is too slow and too reflective to help when forty things genuinely need doing before end of day. Its answer to overload — "invest more in Quadrant II" — is correct over a quarter and useless at 4pm on launch day.

## The decision rule, on two real calendars

The cleanest way to feel the difference is to look at how two very real working styles use the same grid.

**Warren Buffett runs a Covey matrix.** His calendar is famously almost empty — when Bill Gates first saw it he was stunned at the white space. Buffett protects that space on purpose: he spends the majority of his day reading and thinking, and describes time as the one thing he can't buy more of. That is Quadrant II as a life strategy — deliberately guarding important, not-urgent work (reading, capital-allocation thinking, relationships) so that Berkshire faces fewer Quadrant I crises. Buffett isn't triaging a task list; he's *designing* where his years go.

**An incident commander runs an Eisenhower matrix.** When a service is down and the queue is filling with alerts, tickets, and stakeholder pings, the job is pure triage: *Do* the fix that restores service, *Schedule* the postmortem, *Delegate* the status updates, *Delete* the noise. Reflection on quarterly balance is exactly the wrong move mid-outage. (See [Eisenhower applied to an engineering manager's week](/examples/eisenhower-engineering-manager-week) for this worked in detail.)

Here's the catch: **it's usually the same person, at different moments.** Buffett still has to triage the day the market crashes; the incident commander still has to invest in prevention so next quarter has fewer 4pm outages. The grids don't compete — they operate at different altitudes on the same axes.

### The Triage–Invest Split

The named test for which one you actually need right now — the thing to reach for when someone asks "aren't these the same tool?":

| Ask yourself | If yes → | Use | Because |
|---|---|---|---|
| "I have a pile of tasks and not enough hours **today**." | Triage | **Eisenhower** | You need each item routed to an action (Do/Schedule/Delegate/Delete), fast. |
| "I'm always busy but never getting to what **matters**." | Invest | **Covey** | You need to grow Quadrant II so Quadrant I stops refilling. |
| "My urgent list is full of things that **aren't actually important**." | Diagnose | **Covey (Q3)** | Covey's Deception quadrant names the leak Eisenhower silently delegates away. |
| "I know what matters — I just need to **act on the next 20 items**." | Execute | **Eisenhower** | Covey adds nothing here; you've already done the reflection. |

**The rule in one line:** if your problem is *this list*, use Eisenhower; if your problem is *this life*, use Covey. They're the same four boxes asked at two different time horizons — which is why "which is better" is the wrong question and "which altitude am I at" is the right one.

## The Eisenhower Matrix Provenance Chain

Almost every page that compares these two grids opens the same way: the urgent/important split is *Eisenhower's*, and Covey built a matrix on top of it. Read the primary sources and **both halves of that sentence fall apart**. Neither the quote nor the grid is Eisenhower's.

| Date | What is actually documented | What gets claimed instead |
|---|---|---|
| **19 Aug 1954** | Eisenhower, addressing the Second Assembly of the World Council of Churches at Evanston, Illinois: *"I have two kinds of problems, the urgent and the important. The urgent are not important, and the important are never urgent."* He introduces it as the words of **"a former college president"** — not his own. | Quoted as Eisenhower's own formulation. |
| **1949–1970** | J. Roscoe Miller is the **sitting** president of Northwestern University, hosting the Evanston assembly. Eisenhower refers to him separately in the same passage. | Miller is widely named as the "former college president" Eisenhower was quoting. |
| **1973 → 1975** | The hedged wording — *"what is important is seldom urgent and what is urgent is seldom important"* — appears in the press attached to Eisenhower, first without quotation marks (Winnipeg Free Press), then as settled attribution (Christian Science Monitor). | Treated as the verbatim 1954 quote. |
| **1989** | Stephen Covey publishes the four-quadrant Time Management Matrix in *The 7 Habits of Highly Effective People*, Habit 3. **This is the grid.** | The grid is called Eisenhower's. |

### The Double Misattribution

Two separate errors compound into the standard story, and it is worth separating them because they fail in different ways:

1. **The quote is not his.** Eisenhower explicitly sourced it to someone else, on the record, in the primary text. This is not a subtle reading — he says so in the sentence.
2. **The grid is not his either.** There is no documented instance of Eisenhower drawing, using, or describing a 2×2. The four quadrants are Covey's, published 35 years after the speech.

What survives is real but narrower than the legend: Eisenhower **repeated and popularised a distinction** in a widely covered address, and that is the whole of his contribution.

### The Seldom Swap

The most quoted version of the line is not the one he said. Eisenhower spoke in absolutes — *"are not"*, *"are never"*. The famous version hedges to *"seldom"* twice, which is a materially weaker claim: "never urgent" asserts a rule, "seldom urgent" describes a tendency. The hedge is what makes the adage survive scrutiny, and it was added by the press two decades later, not by the speaker.

**And the commonly named source cannot be right.** Eisenhower said *former* college president; Miller was the *incumbent*, in the room, addressed separately in the same breath. [Quote Investigator's](https://quoteinvestigator.com/2014/05/09/urgent/) survey of the dated citations reaches the same conclusion from the other direction: the originator has never been identified. Treat the attribution as open.

**Why this matters for choosing between the two grids:** if the quadrants are Covey's invention rather than Eisenhower's, then the "Eisenhower Matrix" is best understood as a *later re-labelling of Covey's grid for task triage* — which is exactly why the two share axes and differ only in what the labels tell you to do. The shared shape is not a coincidence or a convergence. It is one lineage.

## Edge cases and combined use

- **The healthy loop:** run Covey monthly to see where your time actually went and set a Quadrant II target; run Eisenhower daily to clear the list without letting Quadrant I swallow the Quadrant II time you just protected. Covey sets the budget; Eisenhower spends it.
- **Team vs personal:** both grids are personal-productivity tools. Once the question becomes *which items should the team build*, neither fits — move to [Impact/Effort](/compare/eisenhower-matrix-vs-impact-effort-matrix) for selection or [RICE](/academy/rice-prioritization-framework) for a scored backlog. Don't stretch a time-management grid into a roadmap tool.
- **When Quadrant II keeps losing:** if you protect Quadrant II on Monday and it's gone by Wednesday, the problem isn't the framework — it's that nothing is defending the calendar. Pair either grid with time-blocking, or Quadrant II stays a good intention.
- **When they seem to disagree:** they can't, really — they're the same axes. If Eisenhower says "delegate" and Covey says "this is Quadrant III deception," they agree: it's urgent, not important, and shouldn't be eating *your* time. "Disagreement" is usually you noticing the same task from two altitudes.

## Also compare

- [Covey Time Management Matrix explained](/academy/covey-time-management-matrix) — the four quadrants on their own terms, with Microsoft's workday telemetry mapped onto the grid
- [Eisenhower vs Impact/Effort Matrix](/compare/eisenhower-matrix-vs-impact-effort-matrix) — the same 2×2 shape, but for picking *initiatives* instead of managing *time*
- [RICE vs MoSCoW](/compare/rice-vs-moscow) — when the bottleneck moves from your week to the team's backlog and a fixed deadline
- [Eisenhower vs RICE vs MoSCoW](/academy/eisenhower-matrix-urgent-vs-important#eisenhower-vs-rice-vs-moscow-when-each-prioritization-framework-wins) — the three-way split for personal vs team vs stakeholder prioritization

## Sources

- [Stephen R. Covey — *The 7 Habits of Highly Effective People* (Habit 3, the Time Management Matrix)](https://www.franklincovey.com/the-7-habits/)
- [The American Presidency Project — "Address at the Second Assembly of the World Council of Churches, Evanston, Illinois" (19 August 1954)](https://www.presidency.ucsb.edu/documents/address-the-second-assembly-the-world-council-churches-evanston-illinois) — the primary text, including Eisenhower's attribution to "a former college president"
- [Quote Investigator — "What Is Important Is Seldom Urgent and What Is Urgent Is Seldom Important"](https://quoteinvestigator.com/2014/05/09/urgent/) — the dated citation trail for the "seldom" wording, and the finding that the originator is unidentified
- [Wikipedia — J. Roscoe Miller](https://en.wikipedia.org/wiki/J._Roscoe_Miller) — president of Northwestern University 1949–1970, i.e. the incumbent at the 1954 assembly
- [Big Think — "Why the 'Eisenhower matrix' is a fantastic productivity hack"](https://bigthink.com/the-learning-curve/why-the-eisenhower-matrix-is-a-fantastic-productivity-hack/) — independent account of the misattribution
- [CNBC — "Warren Buffett's secret to productivity: an almost empty calendar"](https://www.cnbc.com/2018/09/06/warren-buffett-and-bill-gates-say-this-is-key-to-being-productive.html)
- [LaunchNotes — "Eisenhower Matrix vs Covey Matrix: which productivity tool is right for you?"](https://www.launchnotes.com/blog/eisenhower-matrix-vs-covey-matrix-which-productivity-tool-is-right-for-you)

> Want to run the grid on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=eisenhower-vs-covey-footer) fills in an urgent-important grid with AI-assisted sorting. Free to start.

---

### Eisenhower Matrix vs GTD: which productivity system to use
URL: https://frameworklist.com/compare/eisenhower-matrix-vs-gtd
> The Eisenhower Matrix prioritizes tasks by urgent vs important. GTD (Getting Things Done) captures and processes them. Same problem, different layers — here's when to use each, and how to combine them.

The Eisenhower Matrix and GTD (Getting Things Done) are the two most-used personal productivity systems — and they solve different problems. The Eisenhower Matrix is a **prioritization** tool: it sorts the tasks you already have by urgent vs important, so you know what to do first. GTD is a **workflow** system: it captures everything that has your attention, clarifies what each item means, and organizes it into a trusted system so nothing slips through.

Most debates about "which is better" miss the point: they operate at different layers. The best practitioners use both — GTD as the workflow, Eisenhower as the prioritization engine inside it.

> New to either? See the [Eisenhower Matrix explained](/academy/eisenhower-matrix-urgent-vs-important) and the [GTD catalog entry](/frameworks/gtd).

## At a glance

| | Eisenhower Matrix | GTD |
|---|---|---|
| **Type** | Prioritization tool | Workflow system |
| **Core question** | "What do I do first?" | "What has my attention, and what do I do about it?" |
| **Inputs** | Tasks you already have | Everything — emails, ideas, commitments, vague worries |
| **Outputs** | Four quadrants with action verbs (Do, Schedule, Delegate, Drop) | Trusted lists: Next Actions, Projects, Waiting For, Someday/Maybe |
| **Cadence** | Weekly or daily triage | Ongoing capture + weekly review |
| **Weakness** | Doesn't capture or process inputs — only sorts what you give it | Doesn't prioritize — assumes you'll decide in the moment |
| **Origin** | Dwight Eisenhower; popularized by Stephen Covey (1989) | David Allen (2001) |
| **Best for** | Deciding what to do today | Clearing mental clutter and trusting your system |

## What the Eisenhower Matrix is best for

**Deciding what to work on next, by trading off urgency and importance.**

The Eisenhower Matrix assumes you already have a list of tasks — and you need to triage them. It plots each task on two axes:

- **Urgent**: Does it have a deadline or external pressure?
- **Important**: Does it advance a goal you've committed to?

The four quadrants imply four actions:

1. **Important + Urgent → Do now.** Crises, deadlines, customer escalations.
2. **Important + Not Urgent → Schedule.** Strategy, learning, deep work — the quadrant most people under-invest in.
3. **Not Important + Urgent → Delegate.** Other people's priorities flowing through you.
4. **Not Important + Not Urgent → Drop.** Activities that feel productive but aren't.

Use the Eisenhower Matrix when:

- You have too many tasks and need a triage rule
- You're confusing "loud" with "important" and reactive weeks are eating strategic work
- You want a quick 15-minute exercise to reset your priorities for the day or week

Its blind spot: **it doesn't help you capture or process inputs**. If tasks aren't already on a list, the matrix can't sort them. And if the list is stale or incomplete, the matrix's output is only as good as its input.

## What GTD is best for

**Capturing everything and building a trusted external system.**

GTD's core claim is that stress comes from *open loops* — commitments, ideas, and worries stored in your head rather than a trusted external system. The 5-step workflow externalizes everything:

1. **Capture** — Collect anything that has your attention into an inbox (physical, digital, or both).
2. **Clarify** — For each item: Is it actionable? If yes, what's the next physical action? If no, is it trash, reference, or someday/maybe?
3. **Organize** — Put the clarified item in the right place: calendar (time-specific), next-action list (context-specific), project list (multi-step outcomes), waiting-for, someday/maybe, or reference.
4. **Reflect** — Weekly review: process all inboxes, review all projects, check the calendar, and ask "is this system current?"
5. **Engage** — Do the work, trusting that you're working on the right thing because everything else is captured.

Use GTD when:

- You feel overwhelmed by the sheer volume of inputs (email, Slack, meetings, ideas)
- You keep forgetting commitments or rediscovering the same tasks
- You want a system that handles *any* kind of input without special-case rules

Its blind spot: **it doesn't prioritize**. David Allen's original GTD assumes that if your system is trusted, you'll make good in-the-moment decisions about what to do. But many practitioners find that a list of 50 next actions with no ranking leads to decision fatigue — and reach for a prioritization layer to fill the gap.

## The decision rule

**Use GTD as the workflow. Use Eisenhower as the prioritization layer inside it.**

This isn't "pick one" — it's "use both at the right layer." Here's how they fit together:

1. **GTD Capture** — Everything goes into the inbox. Eisenhower doesn't touch this step.
2. **GTD Clarify** — Ask "what's the next action?" Once you know the action, *then* ask the Eisenhower questions: is it urgent? Is it important?
3. **GTD Organize** — Place the item based on both GTD category (calendar, next-action, waiting-for) *and* Eisenhower quadrant. A "Not Important + Urgent" task might still be a next action — but it's tagged for delegation or batching.
4. **GTD Reflect** — Weekly review includes re-triaging the Eisenhower quadrants. Items that were urgent last week may have dropped off.
5. **GTD Engage** — When it's time to work, filter by Eisenhower quadrant. Work the Important + Urgent items first, then the Important + Not Urgent items you've scheduled.

### The Clarify-Then-Prioritize Rule

> A named integration protocol: **never apply the Eisenhower Matrix to unclarified 'stuff.'** If you try to sort vague inputs ("that email from Sarah," "the marketing thing") into urgent/important quadrants before GTD's Clarify step, you're sorting fog. The Eisenhower Matrix only works on *concrete next actions* — and GTD's Clarify step is what produces those.

| Step | GTD asks | Eisenhower asks |
|---|---|---|
| Capture | "What has my attention?" | (nothing yet) |
| Clarify | "Is it actionable? What's the next action?" | "Is this action urgent? Is it important?" |
| Organize | "Where does it live?" | "What's the default verb — do, schedule, delegate, drop?" |
| Reflect | "Is my system current?" | "Have any quadrants shifted since last week?" |
| Engage | "What can I do right now, given my context?" | "Am I working on Q1/Q2 or drifting into Q3/Q4?" |

The integration point is Clarify. Once GTD has turned vague "stuff" into a concrete next action, Eisenhower can sort it. Not before.

## How a Stripe PM would use both

To ground this in a real scenario: a product manager at Stripe running a payments-infrastructure squad.

**Monday morning.** The PM opens their inbox: 23 emails, 14 Slack threads, 3 docs shared for review, a vague reminder about "the compliance thing." This is *stuff*, not tasks.

**GTD Capture + Clarify.** The PM processes each item:
- Email from legal about PCI audit → next action: "Schedule 30-min sync with compliance lead" → Important + Urgent (regulatory deadline)
- Slack thread about a customer bug → next action: "Review Jira ticket #4521 and comment on severity" → Important + Urgent
- Doc shared for review → next action: "Read and comment on API proposal by Friday" → Important + Not Urgent → Schedule for Thursday deep-work block
- Vague "compliance thing" → Clarified: it's the same PCI audit, already captured

**Eisenhower triage at the end of Clarify.** 7 tasks land in Q1 (do now), 4 in Q2 (schedule), 3 in Q3 (delegate — the PM forwards to the junior analyst), 5 in Q4 (drop — outdated threads, FYI emails that require no action).

**Weekly review (GTD Reflect).** The PM asks: "Are all my projects current? Are any Q2 items now Q1 because deadlines shifted?" The PCI audit moved from Q2 to Q1 over the week — the matrix gets re-run.

**Engage.** When it's time to work, the PM filters by Eisenhower quadrant. Q1 first. Then the scheduled Q2 blocks. Q3 was delegated. Q4 was deleted.

This is the full integration: GTD provides the workflow (capture everything, clarify into actions, organize, review weekly, engage). Eisenhower provides the prioritization lens at the Clarify and Reflect steps.

## Edge cases / combined use

**What if I only have 15 minutes a day?** Run the Eisenhower Matrix on whatever's in front of you — email inbox, sticky notes, mental list. It's better than nothing. But you'll eventually hit the limit: items slip through because there's no capture system. When that happens, add GTD's Capture and Weekly Review.

**What if I'm a solo founder with no one to delegate to?** The Delegate quadrant becomes "automate or batch." Low-importance, high-urgency tasks still exist — but instead of handing them off, you cluster them into a single time block (email hour, admin hour) so they don't interrupt deep work.

**What if I need to prioritize a team backlog, not personal tasks?** Neither system is designed for shared prioritization. GTD is explicitly personal. The Eisenhower Matrix can be adapted for teams, but "urgent" and "important" become contested terms. For team backlogs, consider [RICE](/academy/rice-prioritization-framework) (quantified scoring) or [MoSCoW](/frameworks/moscow) (scope bucketing) instead.

## Run them

[Eisenhower Matrix explained →](/academy/eisenhower-matrix-urgent-vs-important) · [GTD catalog entry →](/frameworks/gtd) · [Eisenhower applied to an engineering manager's week →](/examples/eisenhower-engineering-manager-week)

## Also compare

- [Eisenhower vs Covey Matrix](/compare/eisenhower-matrix-vs-covey-matrix) — the same urgent/important grid used to triage today vs to redesign where your weeks go
- [Eisenhower vs Impact/Effort Matrix](/compare/eisenhower-matrix-vs-impact-effort-matrix) — execution-layer triage vs selection-layer initiative picking
- [RICE vs MoSCoW](/compare/rice-vs-moscow) — for team prioritization, not personal productivity

## Sources

- [Dave Edwards Media — "Can the Eisenhower Matrix Be Used With GTD?"](https://daveedwardsmedia.com/2024/04/10/can-the-eisenhower-matrix-be-used-with-gtd/)
- [Productivity Patrol — "Elevate Your GTD Game: The Key to Effective Prioritization"](https://productivitypatrol.com/gtd-prioritization/)
- [GTD Forums — "Success with Eisenhower Matrix?"](https://forum.gettingthingsdone.com/threads/success-with-eisenhower-matrix.15229/)
- David Allen, *Getting Things Done: The Art of Stress-Free Productivity* (2001).
- Stephen Covey, *The 7 Habits of Highly Effective People* (1989).

> Want to run the Eisenhower Matrix on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=eisenhower-gtd-compare) — sort your tasks into the four quadrants with AI assistance. Free to start.

---

### Eisenhower Matrix vs Impact/Effort Matrix: which to use
URL: https://frameworklist.com/compare/eisenhower-matrix-vs-impact-effort-matrix
> The Eisenhower Matrix triages your day by urgent vs important. The Impact/Effort (Value vs Effort) matrix picks which projects deserve a quarter. Same 2×2 shape, different jobs.

The Eisenhower Matrix and the Impact/Effort matrix are both 2×2 grids, which is exactly why they get confused. But they sit at different layers of decision-making. The Eisenhower Matrix triages the tasks already on your plate by **urgent vs important**. The Impact/Effort matrix — also sold as **Value vs Effort** or the **Action Priority Matrix** — decides which initiatives earn a place on the roadmap by **payoff vs work**. Pick the wrong one and you'll build a quarter of urgent, low-impact features.

> New to either? See the [Eisenhower Matrix explained](/academy/eisenhower-matrix-urgent-vs-important) and the [Value vs Effort catalog entry](/frameworks/valueeffort).

## At a glance

| | Eisenhower Matrix | Impact/Effort Matrix |
|---|---|---|
| Axes | Urgent × Important | Impact (value) × Effort |
| Question it answers | "What do I touch today?" | "Which initiatives deserve our quarter?" |
| Layer | Execution — time & attention | Selection — resource commitment |
| Unit being sorted | Tasks already on your plate | Candidate initiatives / features |
| Four cells | Do now / Schedule / Delegate / Drop | Quick Wins / Major Projects / Fill-ins / Thankless Tasks |
| Default cadence | Weekly (decays fast) | Quarterly / per planning cycle |
| Best owner | Individual (IC, manager, founder) | Team / product org |
| Quantified cousin | ABCDE method | [RICE](/academy/rice-prioritization-framework) |
| What it ignores | Cost and payoff of the work | Deadlines and external pressure |

## What the Eisenhower Matrix is best for

**Triaging the work that already exists, by time pressure.**

The Eisenhower Matrix assumes the tasks are already real — they're in your inbox, your calendar, your Slack. Its only job is to assign each one an action by crossing two axes: does missing this produce a consequence in the next 48 hours (urgent), and does it advance a committed goal (important)?

Use Eisenhower when:

- You're an individual — IC, manager, or founder — triaging **your own week**
- The list is **reactive**: requests are flowing in faster than you can choose
- The problem is **attention**, not budget — nobody's asking "should this exist?", they're asking "do I do it now?"
- You need to defend a *no* — the Delegate and Drop quadrants give "not today" a name

Its strength is that it surfaces the **Important + Not Urgent** quadrant — strategy, planning, deep work — which reactive weeks quietly starve. It says nothing, however, about whether a task was worth having on the list in the first place. That's the other matrix's job.

## What the Impact/Effort matrix is best for

**Choosing which initiatives get built, by return on work.**

The Impact/Effort matrix plots each *candidate* initiative on two axes: the impact if it lands (revenue, retention, user value) against the effort to ship it (time, people, complexity). The four cells each imply a verdict:

- **Quick Wins** (high impact, low effort) — do these first; highest ROI
- **Major Projects** (high impact, high effort) — worth it, but plan carefully
- **Fill-ins** (low impact, low effort) — do them between big bets, or not at all
- **Thankless Tasks** (low impact, high effort) — avoid or defer

Use Impact/Effort when:

- You're a **team** deciding the roadmap, not an individual managing a calendar
- The question is **"should this exist?"**, not "when do I do it?"
- You have enough candidates (10+) that ranking by gut is wasting cycles
- You want a fast, low-rigor version of [RICE](/academy/rice-score-calculator-with-examples) — Impact/Effort is RICE with the Reach and Confidence terms collapsed into "impact"

Its strength is forcing the **Thankless Tasks** conversation — the high-effort, low-payoff work that survives only because nobody put it on a grid. Its weakness is that it's blind to urgency: a regulatory deadline doesn't move a feature's impact score, but it absolutely changes when you build it.

## The decision rule

**Use the Eisenhower Matrix when the question is "what do I touch today?"**
**Use the Impact/Effort matrix when the question is "which initiatives deserve our quarter?"**

The cleanest way to see the split is on a real company's actual rhythm. Take **Spotify**, which has publicly documented a squad-based model and a heavy 2026 push into podcast and audiobook bets. At the *selection* layer, a Spotify squad deciding whether to fund a new creator-monetization feature versus an audiobook-discovery improvement is running an Impact/Effort decision — high-impact, high-effort Major Projects competing for a finite quarter. Urgency barely enters; neither feature is on fire. But once that squad commits and the work is underway, the same squad lead triaging Monday morning — a partner escalation, a flaky deploy, a design review, a roadmap doc — is running an Eisenhower decision. The escalation is urgent and important (do now); the roadmap doc is important and not urgent (schedule); the deploy noise is urgent and not important (delegate).

Same team, same week, two matrices — because the questions are different. The roadmap question is *what's worth building*; the Monday question is *what gets my attention now that we've decided*.

### The Initiative–Execution Split

> A named test for which matrix you actually need: **if the items you're sorting don't exist yet as committed work, you're at the Initiative layer — use Impact/Effort (or [RICE](/academy/rice-prioritization-framework) to quantify it). If the items already exist and are competing for today, you're at the Execution layer — use Eisenhower.**

| Signal | Initiative layer → Impact/Effort | Execution layer → Eisenhower |
|---|---|---|
| The items are… | candidate ideas / bets | tasks already on your plate |
| You're deciding… | whether to commit resources | what to do with committed work |
| The clock matters because… | of opportunity cost | of real deadlines / external pressure |
| Owner | team / product org | individual |
| Cadence | per planning cycle | weekly |
| Quantified version | [RICE](/academy/rice-prioritization-framework), [WSJF](/compare/rice-vs-wsjf) | ABCDE method |

The recurring failure both matrices guard against is the same: using urgency as a proxy for value. Teams that run roadmaps on an Eisenhower-style "what's urgent" instinct build a quarter of loud, low-impact features. Individuals who run their week on an Impact/Effort "what's high-value" instinct never ship anything, because the highest-impact work is rarely the most urgent. Match the matrix to the layer and that confusion disappears.

## Edge cases / combined use

**A founder wearing both hats.** Early-stage founders make initiative *and* execution decisions in the same hour. Run Impact/Effort once a month to set the few bets that matter; run Eisenhower every morning to survive the day inside those bets. Don't merge them into one grid — the axes mean different things.

**When Impact/Effort isn't rigorous enough.** If "impact" keeps getting argued in circles, upgrade to [RICE](/academy/rice-score-calculator-with-examples), which splits impact into Reach × Impact × Confidence and divides by Effort. RICE is the quantified Impact/Effort matrix; reach for it when the stakes justify the extra 5 minutes per item. See [RICE vs ICE](/compare/rice-vs-ice) for the lighter-weight scoring option.

**When a deadline is fixed.** Neither matrix handles a hard cut line well. If the question is "what makes the launch by date X?", use [MoSCoW](/compare/rice-vs-moscow) to bucket scope, then Eisenhower to triage the daily work toward the deadline.

**Strategic, not tactical, decisions.** If you're deciding *which market or product line* to pursue — not which task or feature — a 2×2 task grid is the wrong altitude. Use [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) or the [BCG Matrix](/frameworks/bcg) instead.

## Run them

[Eisenhower Matrix explained →](/academy/eisenhower-matrix-urgent-vs-important) · [Value vs Effort catalog entry →](/frameworks/valueeffort) · [RICE Academy guide →](/academy/rice-prioritization-framework) · [Eisenhower applied to an engineering manager's week →](/examples/eisenhower-engineering-manager-week)

## Also compare

- [RICE vs ICE](/compare/rice-vs-ice) — when you've decided to quantify impact/effort and need the lighter or heavier scoring model
- [RICE vs MoSCoW](/compare/rice-vs-moscow) — scoring an open backlog vs scoping a fixed-deadline release
- [RICE vs WSJF](/compare/rice-vs-wsjf) — when delay itself has a cost and time-criticality should drive the order
- [Eisenhower vs Covey Matrix](/compare/eisenhower-matrix-vs-covey-matrix) — the same urgent/important grid used to triage today vs to redesign where your weeks go

## Sources

- [Tempo — "Impact effort matrix: your key to better decisions"](https://www.tempo.io/blog/impact-effort-matrix)
- [monday.com — "Action priority matrix vs Eisenhower matrix"](https://monday.com/blog/project-management/action-priority-matrix-vs-eisenhower-matri/)
- [IdeaScale — "Eisenhower Matrix Alternatives"](https://ideascale.com/blog/eisenhower-matrix-alternatives/)
- Eisenhower's 1954 "urgent vs important" remark, popularized in Stephen Covey, *The 7 Habits of Highly Effective People* (1989).

> Want to run both matrices on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=eisenhower-valueeffort-compare) — fill in any framework with AI assistance. Free to start.

---

### Jobs-to-be-Done vs Customer Personas
URL: https://frameworklist.com/compare/jtbd-vs-personas
> Personas describe who the customer is. JTBD describes what the customer is trying to accomplish. The difference shapes which features you build.

Both claim to model the customer. The model is different in a way that shows up in the product roadmap.

## At a glance

| | JTBD | Personas |
|---|---|---|
| Unit | A *job* the customer is hiring a product for | A *person* (often composite) representing a customer segment |
| Output | "When [situation], I want to [job], so I can [outcome]" | A profile: name, age, role, goals, pain points, quotes |
| Stability over time | High (jobs are stable) | Low (personas drift as users change) |
| Best for | Product strategy, competitive set definition | Marketing copy, UX research synthesis |
| Origin | Christensen / Ulwick / Moesta | Alan Cooper, *The Inmates Are Running the Asylum*, 1999 |
| Common abuse | Vocabulary-only ("our job is to help users feel productive") | Stereotypes ("Sarah, 34, busy mom") that aren't grounded in research |

## When personas help

- **UX research synthesis**: collapsing 30 interviews into 3 typical-user profiles helps designers reason about edge cases without listing every interview verbatim
- **Marketing copy and persona-driven landing pages**: when the value prop varies meaningfully by who the buyer is
- **Sales enablement**: arming reps with profiles of who they're likely to be selling to
- **Cross-functional alignment**: easier to say "Sarah won't understand this" than "users in segment 2 with the following attributes"

The persona's value is *anchoring*. It makes an abstract user concrete enough for the team to reason about.

[Open the Empathy Map in the catalog →](/frameworks/empathymap) — the worksheet most teams actually use to build a persona.

## When JTBD helps

- **Defining a new product or feature**: what job is this hired for?
- **Identifying real competitors**: what else gets hired for the same job?
- **Pivoting or repositioning**: when the apparent customer hasn't changed but engagement has, the job probably has
- **Killing features**: ones that don't serve the job, regardless of how nice they are

The [JTBD](/glossary/jtbd)'s value is *focus*. It forces the team to articulate the outcome the customer is trying to achieve.

[Full JTBD Academy guide →](/academy/jobs-to-be-done-framework-explained)

## The pattern that works

Use both, in this order:

1. **JTBD first** — name the jobs your product is hired for. Surfaces the durable demand.
2. **Personas second** — for each job, who tends to hire the product for that job? Maps job to buyer/user characteristics.

The combination tells you both *what the product needs to do* (JTBD) and *who you're talking to about it* (Personas).

## The common mistake

Picking the framework that requires less customer research. Both done badly produce fiction; both done well require interviews.

- A persona built from a strategy offsite without customer interviews is just stereotypes the team agreed on.
- A JTBD job written without customer interviews is just the product team's pitch deck.

Neither tool excuses you from talking to users. They're both *synthesis* tools — what you synthesize depends on the quality of inputs.

## The diagnostic

If your team can describe the customer's *day* (what they do hour by hour, what frustrates them, what they're trying to accomplish), you have enough material for a JTBD. If your team can describe the customer's *role and demographics* (where they work, what title, what tools they use), you have enough material for a persona. Most teams have both — and most should produce both.

If neither — go do 5–10 user interviews before reaching for any synthesis framework.

> **Want both artifacts on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=jtbd-vs-personas) ships JTBD job statements and persona templates side by side, with AI-assisted prompts for each. Free to start.

## Related

- [Jobs-to-be-Done framework explained](/academy/jobs-to-be-done-framework-explained) — the underlying JTBD method + when to reach for it
- [Jobs-to-be-Done examples: 8 real companies](/academy/jobs-to-be-done-examples) — see the three-layer job map applied to Duolingo, Slack, Uber and more
- [JTBD applied to Instagram Stories](/examples/jtbd-instagram-stories) — worked example showing job statements derived from real product behaviour
- [JTBD framework catalog](/frameworks/jtbd) — the canonical template + worked applications
- [JTBD vs user stories](/compare/jtbd-vs-user-stories) — the delivery-side comparison: how a job becomes shippable increments via the Job-to-Story Ladder
- [JTBD for healthcare & digital health](/playbooks/jtbd-for-healthcare) — industry playbook where the buyer/user split is widest

---

### Jobs-to-be-Done vs User Stories: Which to Use When
URL: https://frameworklist.com/compare/jtbd-vs-user-stories
> JTBD captures the outcome a customer is hiring your product for; user stories capture the increment you build. Here's how the two connect — and when to use each.

**One-line version:** Jobs-to-be-Done tells you *what outcome is worth building and why*; user stories tell you *what increment to ship next*. They sit at different altitudes — strategy versus delivery — so the real question isn't "which one," it's "am I at the right altitude for the decision in front of me?"

The two get pitted against each other because both can be written as a single sentence about a user wanting something. But a [Jobs-to-be-Done](/frameworks/jtbd) statement and a user story answer completely different questions, and treating them as interchangeable is how teams end up with a tidy, well-groomed backlog that ships the wrong product.

## At a glance

| | Jobs-to-be-Done | User Stories |
|---|---|---|
| **Question it answers** | What progress is the customer trying to make? | What increment do we build next? |
| **Altitude** | Strategy / discovery | Delivery / execution |
| **Format** | "When [situation], I want to [motivation], so I can [outcome]" (job story) | "As a [persona], I want [feature], so that [benefit]" |
| **Solution-bound?** | No — deliberately feature-agnostic | Yes — assumes the solution is chosen |
| **Lifespan** | Stable for years (the job rarely changes) | Disposable — closed at the end of a sprint |
| **Owner** | Product / research | Whole delivery team |
| **Fails when** | Treated as a backlog item | Written before the job is understood |
| **Origin** | Christensen / Ulwick (milkshake study) | Extreme Programming / Mike Cohn |

The clearest tell: a job is **stable and solution-free** ("help me feel settled fast in a new city"), while a user story is **disposable and solution-bound** ("as a new user, I want to import my contacts"). One survives three product pivots; the other is closed and forgotten in two weeks.

## What JTBD is best for

JTBD earns its keep *before* you've committed to building anything:

- **Deciding whether a problem is worth solving at all.** The job exists whether or not your product does. Naming it tells you the size of the prize.
- **Understanding switching behavior** — why customers fire their old solution and hire yours (or yours and hire a competitor's). This is the milkshake study's whole point.
- **Exploring a new product line** where no roadmap, no persona, and no feature set exist yet.
- **Aligning a leadership team on the "why"** behind a bet, where a list of features would just trigger feature-by-feature debate.

If the argument in the room is "should we even be doing this?", you're in JTBD territory. For a fuller treatment, see the [Jobs-to-be-Done framework explained](/academy/jobs-to-be-done-framework-explained).

## What user stories are best for

User stories earn their keep *after* the bet is made and you're slicing delivery:

- **Breaking agreed work into shippable increments** small enough to finish in a sprint and test against reality.
- **Creating a shared, lightweight contract** between product, design, and engineering on the next thing to ship.
- **Sequencing and estimating** — stories are the unit most agile tooling, planning, and velocity tracking are built around.
- **Closing the loop** — each story has an acceptance criterion, so "done" is unambiguous.

If the argument in the room is "how do we break this down and what's first?", you're in user-story territory.

## The Job-to-Story Ladder

The reason these two get confused is that nobody shows the rung between them. Here it is — a three-layer ladder that takes one customer truth from strategy all the way to a sprint ticket:

| Layer | Format | Example (audiobooks) | Changes how often? |
|---|---|---|---|
| **1. Job (strategy)** | "When [situation], I want to [motivation], so I can [outcome]" | "When my commute is dead time, I want to make progress on books I never finish, so I feel my time wasn't wasted." | Almost never |
| **2. Job story (bridge)** | Same format, narrowed to one situation | "When I finish an audiobook chapter mid-commute, I want the next chapter to start seamlessly, so I stay in flow." | Per opportunity |
| **3. User story (tactics)** | "As a [persona], I want [feature], so that [benefit]" | "As a listener, I want autoplay-next-chapter with a 5-second skip, so I'm not pulled out of the experience." | Per sprint |

The **Job-to-Story Ladder** is the named test: *a healthy backlog can trace every user story back up to a job.* If a story has no rung above it, you're building a feature nobody hired you for. If a job has no rungs below it, you have strategy with no delivery. Walk the ladder in both directions during backlog refinement — top-down to check coverage, bottom-up to check justification.

The middle rung — the **job story** — is the piece most teams skip. Popularized by [Intercom's Alan Klement](https://www.intercom.com/blog/using-job-stories-design-features-ui-ux/), it keeps JTBD's focus on situation and outcome while being concrete enough to design against, *without* prematurely committing to a persona or a feature the way a user story does.

## The decision rule, on a real bet

Take Spotify's continued push into [audiobooks through 2026](https://newsroom.spotify.com/audiobooks/). Imagine the team weighing two roadmap directions: deepen audiobook discovery, or build better in-listening controls.

- **At the JTBD altitude**, the question is which *job* is underserved. "When I have dead commute time, help me make progress on books I never finish" is a different job from "when I'm browsing, help me find my next great listen." Research — not a backlog — decides which job the audiobook business is losing customers on. That's a JTBD decision, and writing it as user stories too early would smuggle in a solution before the bet is chosen.
- **Once the bet is chosen** — say, "win the in-listening job" — user stories take over: autoplay-next-chapter, a sleep timer that bookmarks your place, variable playback speed. Each is a shippable increment with a clear acceptance test, and each traces cleanly back up the ladder to the chosen job.

**The rule:** if you're choosing between outcomes, use JTBD. If you've chosen the outcome and are choosing increments, use user stories. The moment you catch yourself writing user stories to *justify* a direction rather than to *deliver* a chosen one, stop and climb back up the ladder.

## Edge cases and combined use

- **B2B with many stakeholders:** the job belongs to the buyer's organization; user stories often split across multiple personas (admin, end user, approver). Use JTBD to keep the stories anchored to one shared outcome instead of drifting into per-role wish lists.
- **Platform / API products:** the "user" is a developer and the job is "ship my own feature faster." Job stories travel better than persona-based user stories here, because the persona is thin but the situation is rich.
- **Bug-fix and tech-debt work:** neither framework fits cleanly — these are constraints on delivering the job, not jobs themselves. Don't force a job story onto a security patch.

For the layered relationship between JTBD, personas, and user stories together, see [JTBD vs personas](/compare/jtbd-vs-personas) — personas describe *who*, JTBD describes *what progress*, and user stories describe *what to build*. Used together, the three answer who/why/what without overlap. For a worked example of the job statement itself, see [what job Instagram Stories is hired to do](/examples/jtbd-instagram-stories) — the case that shows why a well-framed job doesn't cannibalize the surface it sits next to.

## Related

- [Jobs-to-be-Done framework explained](/academy/jobs-to-be-done-framework-explained) — the full JTBD method, with worked examples
- [JTBD vs personas](/compare/jtbd-vs-personas) — the other half of the customer-research picture
- [RICE prioritization framework](/academy/rice-prioritization-framework) — once you have stories, RICE helps you sequence them
- [Jobs-to-be-Done](/frameworks/jtbd) in the framework library

> Want to model a customer's job on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — fill in any framework with AI assistance.

## Sources

- [Clayton Christensen et al. — "Know Your Customers' Jobs to Be Done," Harvard Business Review (2016)](https://hbr.org/2016/09/know-your-customers-jobs-to-be-done)
- [Alan Klement / Intercom — "Using Job Stories to Design Features"](https://www.intercom.com/blog/using-job-stories-design-features-ui-ux/)
- [Mike Cohn / Mountain Goat Software — "User Stories"](https://www.mountaingoatsoftware.com/agile/user-stories)
- [Spotify Newsroom — Audiobooks](https://newsroom.spotify.com/audiobooks/)

---

### Lean Canvas vs Business Model Canvas
URL: https://frameworklist.com/compare/lean-canvas-vs-business-model-canvas
> Lean Canvas was Ash Maurya's adaptation of Alex Osterwalder's Business Model Canvas, specifically for startups. The differences look small but determine which tool fits which stage of company.

Both are 9-block, one-page strategy canvases. Lean Canvas swaps out 4 of the Business Model Canvas's blocks for 4 different ones — and that change is targeted at startups specifically.

## The 9 blocks compared

| | Business Model Canvas | Lean Canvas |
|---|---|---|
| 1 | Customer Segments | Customer Segments |
| 2 | Value Propositions | **Problem** *(replaced)* |
| 3 | Channels | **Solution** *(replaced)* |
| 4 | Customer Relationships | Unique Value Proposition |
| 5 | Revenue Streams | **Unfair Advantage** *(replaced)* |
| 6 | Key Resources | Channels |
| 7 | Key Activities | Key Metrics |
| 8 | Key Partnerships | Revenue Streams |
| 9 | Cost Structure | Cost Structure |

The 4 substitutions: **Problem · Solution · Unfair Advantage · Key Metrics** replace **Value Propositions · Channels · Customer Relationships · Key Resources/Activities/Partnerships**.

## Why Lean Canvas swapped those out

Ash Maurya wrote *Running Lean* in 2010 to adapt the Business Model Canvas for startups specifically. His argument:

- **Problem** is what startups under-validate. Forcing it onto the canvas surfaces whether the founders have evidence the problem exists.
- **Solution** is a draft answer to the Problem, deliberately compressed to one block so founders don't fall in love with their solution.
- **Unfair Advantage** answers "why won't this be copied?" — a question early-stage companies rarely engage with explicitly.
- **Key Metrics** forces a measurable definition of "is this working?" up front.

What got removed (Customer Relationships, Key Resources, Activities, Partnerships) was Maurya's bet that startups don't yet have these — they're outcomes of execution, not inputs to strategy. Trying to fill them too early produces fiction.

## When to use Lean Canvas

- **Pre-product or pre-[PMF](/glossary/product-market-fit) startup**
- **Founder testing a new business idea**
- **Strategy work where customer evidence is the missing piece**
- **Anywhere "do we have a real problem to solve" is the open question**

[Open the framework entry →](/frameworks/lean)

## When to use Business Model Canvas

- **Existing business** mapping its current model
- **Established product** considering channel or partnership expansion
- **Operational planning** where Activities, Partnerships, Resources are real and need mapping
- **M&A diligence** on a mature target

[Open the framework entry →](/frameworks/bmc)

## The diagnostic question

Are you trying to design a business model *or* describe one that already exists?

- **Design** → Lean Canvas (you're proposing; the canvas tests it against problem evidence)
- **Describe** → Business Model Canvas (you have a model; the canvas maps it for analysis)

## A common mis-use

Mature companies adopting Lean Canvas because it's the trendy version. They fill in Problem/Solution earnestly even though the problem is well-known and the solution has been shipping for years. The canvas adds no insight because the questions it forces don't apply to their stage.

The reverse also happens: early-stage startups use Business Model Canvas because it looks more "official". They fill in Key Partnerships and Key Activities for partnerships and activities that don't yet exist. The output is hopeful fiction.

## Run them

Both [Lean Canvas](/frameworks/lean) and [Business Model Canvas](/frameworks/bmc) have catalog entries with worksheet templates. For Lean Canvas specifically, the original *Running Lean* book is still the best step-by-step methodology guide. For a worked Business Model Canvas on a real company at scale, see the [Anthropic Business Model Canvas (2026 IPO edition)](/examples/anthropic-business-model-canvas) — it maps all nine blocks against the actual mid-2026 IPO numbers.

> **Want to fill either canvas on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=lean-vs-bmc) ships both Lean Canvas and Business Model Canvas with AI-assisted prompts per block. Free to start.

---

### MoSCoW vs Kano Model: which prioritization framework to use
URL: https://frameworklist.com/compare/moscow-vs-kano
> MoSCoW buckets features by delivery commitment (Must/Should/Could/Won't); Kano classifies them by the satisfaction they create. One commits scope, the other diagnoses value — here's when to use each.

Both **MoSCoW** and the **Kano Model** help a team decide what to build, but they answer different questions. MoSCoW is a **scope commitment**: it sorts features into *Must have, Should have, Could have,* and *Won't have (this time)* so a deadline survives contact with a growing backlog. Kano is a **satisfaction diagnosis**: it labels each feature a *must-be, performance,* or *delighter* by how it moves customer happiness. MoSCoW asks *what ships now?* Kano asks *what kind of value is this?* Treating them as rivals is the common mistake — the mature answer is to run Kano first to diagnose, then MoSCoW to commit.

> New to either one? See the [MoSCoW method](/frameworks/moscow) and [Kano Model](/frameworks/kano) catalog entries for the mechanics before comparing them.

## At a glance

| | MoSCoW | Kano Model |
|---|---|---|
| **What it produces** | Four scope buckets (Must / Should / Could / Won't) | A category per feature (must-be / performance / delighter) |
| **Core question** | What ships in *this* release? | What kind of satisfaction does this create? |
| **Based on** | Team judgment of delivery necessity | Customer-satisfaction research (surveys) |
| **Output shape** | A committed scope line + Won't-have list | A diagnosis, not a ranking |
| **Biggest strength** | Fast, deadline-protecting, everyone gets it | Catches delighters and hidden table-stakes |
| **Biggest weakness** | Subjective — "Must" inflates without discipline | No ordering; needs a second tool to sequence |
| **Best for** | Time-boxed releases, stakeholder alignment | Upstream discovery, quarterly value refresh |
| **Originated in** | DSDM Agile (Dai Clegg, 1994) | Noriaki Kano, 1984 |

## What MoSCoW is best for

MoSCoW wins when the constraint is **a deadline and a nervous stakeholder table**. Its whole value is drawing a defensible line: the *Must haves* are what makes the release viable, the *Won't-have-this-time* list is what stops scope creep, and both are visible to everyone in one artifact. It's the fastest way to get a room to agree on what "done" means for this increment.

Use MoSCoW when:

- You have a **fixed release date** and a backlog that won't all fit
- Stakeholders keep escalating everything to "critical" and you need a forcing function
- You want a lightweight method **non-product people understand instantly**
- The team is running **DSDM or time-boxed Agile** where scope flexes but the date doesn't

Its weakness is subjectivity: without discipline, every feature becomes a "Must." That's exactly the gap Kano fills.

## What Kano is best for

Kano wins when the risk is **building the wrong *kind* of thing** — shipping more performance features while a basic expectation is missing, or starving the delighters that create loyalty. It classifies features by how they actually move satisfaction, using customer input rather than the loudest voice in the room.

Use Kano when:

- You're doing **upstream discovery** and need to know which ideas are table stakes vs. differentiators
- Your product has **satisfied the basics** and you're deciding where to invest for delight
- You suspect the team is **over-indexing on linear "more is better" features** and under-investing in surprises
- You have access to **real customer-satisfaction data** to classify against (Kano without data is just opinion in a fancier grid)

Its weakness is that Kano **produces no order** — it diagnoses, it doesn't rank or commit. You still need a tool to draw the release line. That tool is MoSCoW (for scope) or [RICE](/academy/rice-prioritization-framework) (for build order).

## The decision rule, on a real roadmap

Take **Notion** heading into 2026, deciding what to build across its expanding suite — the core editor, Notion AI, Notion Calendar, and Notion Mail.

- **Kano first (diagnose).** Reliable sync and fast search are *must-be* — nobody praises them, but their absence causes churn. AI writing quality is a *performance* feature: more accuracy linearly lifts satisfaction. An AI agent that drafts and files your email unprompted is a *delighter* — unexpected, loyalty-creating, but low on request volume.
- **MoSCoW second (commit).** For the Q1 release: sync reliability and search are **Must have** (Kano flagged them as basic). One headline AI accuracy improvement is **Should have**. The surprise email-agent delighter is a **Could have** — high upside, but it can slip a release without causing dissatisfaction. Anything requiring a data-model rewrite is **Won't have this time**.

The rule in one line: **Kano tells you which features you're not allowed to skip; MoSCoW tells you which of the rest fit before the deadline.** Skip the diagnosis and MoSCoW will happily let a team rank a basic expectation as "Could have" and ship active dissatisfaction.

## The Prioritization Stack: Kano → MoSCoW → RICE

Here's the synthesis Framework's prioritization library supports that most single-tool articles miss. MoSCoW and Kano aren't just complementary to each other — they slot into a three-layer stack, each answering the question the previous one leaves open:

| Layer | Framework | Question it answers | What it hands to the next layer |
|---|---|---|---|
| **1. Diagnose** | **Kano** | What *kind* of value is each feature? | The must-be features that can't be cut |
| **2. Commit** | **MoSCoW** | What's *in* this release? | The Should/Could items that are genuinely optional |
| **3. Sequence** | **RICE** | In what *order* do we build the optional ones? | A ranked, defensible build queue |

Kano stops MoSCoW from being subjective; MoSCoW stops RICE from scoring table-stakes against delighters as if they were interchangeable; RICE puts a number on the order MoSCoW leaves ambiguous. Run all three and each framework covers the next one's blind spot. Most teams reach for exactly one and inherit its weakness — I call this the **Prioritization Stack**, and it's the reason these comparisons are sequencing questions, not either/or choices.

## Edge cases and combined use

- **Small team, tight deadline, no research budget:** MoSCoW alone is fine. Kano without customer data is just opinion — don't fake it.
- **Pre-launch product still finding table stakes:** Kano alone (or Kano → RICE). There's no fixed release scope to commit yet, so MoSCoW's buckets add little.
- **Mature product, quarterly planning:** run the full stack — Kano quarterly to refresh the value map, MoSCoW per release, RICE within the Should/Could tier.
- **Both flag the same feature differently:** trust Kano for *whether* it's non-negotiable, MoSCoW for *when* it ships. They're answering different questions, so "disagreement" usually means you're conflating value with timing.

## Also compare

- [RICE vs MoSCoW](/compare/rice-vs-moscow) — score-based ranking vs bucket-based scope cutting
- [RICE vs Kano](/compare/rice-vs-kano) — when you need an order vs a diagnosis
- [RICE vs WSJF](/compare/rice-vs-wsjf) — when delay has a cost and time-criticality should drive the order

## Sources

- [HotPMO — "Kano Model vs MoSCoW: How Do You Prioritize?"](https://www.hotpmo.com/management-models/moscow-kano-prioritize/)
- [Noriaki Kano et al. — "Attractive Quality and Must-Be Quality" (foundational 1984 paper, overview)](https://en.wikipedia.org/wiki/Kano_model)
- [Agile Business Consortium — "MoSCoW Prioritisation" (DSDM origin)](https://www.agilebusiness.org/dsdm-project-framework/moscow-prioritisation.html)
- [Plane — "Feature prioritization frameworks: RICE, MoSCoW, and Kano explained"](https://plane.so/blog/feature-prioritization-frameworks-rice-moscow-and-kano-explained)

> Want to run this stack on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=moscow-vs-kano) fills in MoSCoW, Kano, and RICE with AI-assisted inputs. Free to start.

---

### OKR vs MBO: which goal-setting system to use
URL: https://frameworklist.com/compare/okr-vs-mbo
> MBO sets private, must-hit objectives reviewed annually. OKRs make ambitious objectives transparent and grade them at 70%. OKRs evolved from MBO — here's what changed and when each still wins.

OKRs didn't replace MBO — they *evolved* from it, and the two surviving differences are the only ones that matter. **MBO** (Management by Objectives) sets private, must-hit objectives you're graded against annually and paid on. **OKRs** make ambitious objectives transparent across the company, grade them quarterly, and deliberately treat 70% attainment as success. Pick the wrong one and you'll either bury goals that needed to be public or punish a team for missing a stretch target that was never meant to be fully hit.

> New to objectives-and-key-results? Read [OKRs vs KPIs: the difference](/academy/okrs-vs-kpis-difference) and [OKR examples for product teams](/academy/okr-examples-for-product-teams) first — this page assumes you know what a Key Result is.

## At a glance

| | OKR | MBO |
|---|---|---|
| Full name | Objectives and Key Results | Management by Objectives |
| Origin | Andy Grove, Intel (1970s); spread to Google by John Doerr, 1999 | Peter Drucker, *The Practice of Management*, 1954 |
| Visibility | **Transparent** — anyone can see anyone's OKRs, CEO to IC | **Private** — set in a confidential manager–employee discussion |
| Cadence | Quarterly (sometimes monthly) | Annual |
| Attainment target | 60–80% is "strong"; 100% means it was too easy | 100% — the objective is a commitment to fully meet |
| Linked to pay? | **Deliberately decoupled** from compensation | **Tied** to performance reviews and bonuses |
| Structure | Qualitative Objective + 2–5 measurable Key Results | An objective with a target, agreed top-down/bottom-up |
| Core question | "What ambitious thing are we chasing, and how will we know we're moving?" | "What must this person commit to deliver this year?" |
| Fails when | Tied to pay (people sandbag) or used for routine commitments | Used for moon-shots, or when siloed goals need cross-team visibility |

## What OKRs are best for

**Transparent, cross-team alignment on ambitious goals.**

The OKR's defining moves are transparency and stretch. Splitting a goal into a qualitative **Objective** ("Make onboarding so good new users reach value on day one") and 2–5 quantitative **Key Results** ("activation 35% → 55%", "median time-to-value under 10 min") is borrowed straight from MBO. What OKRs *added* was making every objective public and grading it on a stretch scale.

Use OKRs when:

- **Several teams must align** on the same direction each quarter and need to see each other's goals
- You want a **stretch target** where 70% attainment is a win, not a failure
- One objective needs **multiple leading indicators**, not a single number
- You want a cadence that **re-sets quarterly** so priorities move with the market

The reason OKRs decouple from pay is structural: the moment a 70%-target goal affects someone's bonus, they set easier goals to protect the bonus — which recreates the exact sandbagging problem OKRs exist to solve.

## What MBO is best for

**Private, must-hit objectives owned by one person and tied to their review.**

Drucker's MBO was a breakthrough in 1954: instead of bosses dictating tasks, manager and employee *agree* on objectives, then the employee is measured against them. The objective is a **commitment** — 100% is the bar — and because it's tied to the annual review and compensation, it stays private between the two of them.

Use MBO when:

- The objective is an **individual commitment** where 100% is the expectation (a sales quota, a compliance deadline, a hiring plan)
- A **single metric** captures success cleanly
- Goals are **genuinely confidential** — executive targets, sensitive financial objectives
- You're running a **formal annual performance cycle** and need goals that can be fairly graded and paid against

MBO's strength is accountability. Because one named owner commits to a number they'll be reviewed on, there's no diffusion of responsibility. For must-hit, individually-owned work, that clarity beats OKR ceremony.

> Setting an individual must-hit objective against a deadline? A [premortem](/academy/how-to-run-a-premortem) pairs naturally with an MBO commitment — it surfaces what could make the owner miss before the review date turns the miss into a surprise.

## The decision rule: the Transparency-and-Stretch Test

OKRs and MBO share DNA, so don't compare them on surface features (cadence, structure) that both can flex. Compare them on the **two axes that actually changed** when OKR evolved out of MBO. Run any goal through two questions:

1. **Should this goal be transparent across the org, or private to one owner?**
   Transparent → OKR. Private → MBO.
2. **If you only hit 70% of it, is that a strong result or a failure?**
   Strong (stretch) → OKR. Failure (commit) → MBO.

Two "OKR" answers → run it as an OKR. Two "MBO" answers → run it as an MBO. A split (one each) is the tell that you have **two different goals tangled together** — usually a public ambition and a private commitment — and you should write them separately. The test isolates transparency and stretch because those are literally the two things Grove and Doerr changed; everything else (quarterly vs annual, decoupled from pay) follows from them.

**Grounded example.** When Andy Grove built the system at Intel, he explicitly called it "iMBOs" — *Intel MBOs* — then made two changes: he made objectives company-visible and graded them as stretch goals, which John Doerr carried to Google in 1999, where the canonical "20× growth" objectives were never expected to be fully hit. That is the OKR case: ambition you'd be thrilled to mostly reach, in the open. Contrast the model Drucker documented at **Hewlett-Packard** — the "HP Way" ran on MBO, with managers and reports privately agreeing on annual objectives that were committed to and reviewed for pay. A regional sales director committing to "$8M bookings this fiscal year, reviewed for bonus" is pure MBO: private, must-hit, annual. Same lineage, opposite settings on the two dials that matter.

## Edge cases and combined use

**Run both layers.** The most common modern setup keeps an **annual MBO-style layer** for individual performance and pay, and a **quarterly OKR layer** for team execution and alignment. They don't conflict — they answer different questions ("what is this person accountable for and paid on?" vs "what is the team chasing this quarter, in the open?"). Trouble starts only when you tie the OKR layer to comp, collapsing it back into MBO.

**Individual contributors.** MBO-style goals usually win for personal performance reviews — the cycle wants commitments that can be fairly graded at 100%. Stretch OKRs at the individual level backfire when compensation punishes the 30% miss OKRs are designed to tolerate. (Same reason [SMART goals](/compare/okr-vs-smart-goals) often beat OKRs for individuals.)

**Highly regulated or sales-driven orgs.** Where a number must simply be hit — quotas, certifications, regulatory deadlines — MBO's commit-to-100% model matches the binary reality better than a stretch OKR.

**Early-stage startups.** Before [product-market fit](/glossary/product-market-fit), skip both ceremonies. Set one or two must-hit commitments around survival ([runway](/glossary/runway), a single activation number) and add OKR machinery only once you have teams to align.

## When neither is the right tool

- **Monitoring ongoing operational health** — that's a [KPI](/glossary/kpi), not a goal. KPIs are dials you watch; OKRs and MBOs are targets you chase. See [OKRs vs KPIs](/academy/okrs-vs-kpis-difference).
- **Sequencing a feature backlog** — use [RICE](/academy/rice-prioritization-framework) or [RICE vs MoSCoW](/compare/rice-vs-moscow), not a goal system.
- **Deciding what the goal should even be about** — run [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) or a SWOT with [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=compare-cta) (dedicated tool, free) to set direction before you set goals.

## Run them

[OKR catalog entry →](/frameworks/okr) · [OKRs vs KPIs explained →](/academy/okrs-vs-kpis-difference) · [OKR examples for product teams →](/academy/okr-examples-for-product-teams) · [OKR vs SMART Goals →](/compare/okr-vs-smart-goals)

## Also compare

- [OKR vs SMART Goals](/compare/okr-vs-smart-goals) — stretch vs commit, the other half of the goal-setting decision
- [OKRs vs KPIs](/academy/okrs-vs-kpis-difference) — goals you chase vs dials you monitor

## Sources

- [Peter Drucker — *The Practice of Management* (1954), where MBO was introduced](https://en.wikipedia.org/wiki/Management_by_objectives)
- [What Matters (John Doerr) — "MBO vs. OKR: What's the difference?"](https://www.whatmatters.com/resources/okr-and-mbo-difference-between)
- [Bernard Marr — "OKR vs MBO: What is the Difference?"](https://bernardmarr.com/default.asp?contentID=1460)
- [Quantive (WorkBoard) — "MBO vs. OKR: What's the Difference?"](https://quantive.com/resources/articles/mbo-vs-okr)

> Want to set OKRs or MBO objectives on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?mt=8) — fill in any framework with AI assistance.

---

### OKR vs SMART Goals: which goal-setting framework to use
URL: https://frameworklist.com/compare/okr-vs-smart-goals
> SMART goals make one objective specific and achievable. OKRs hang several measurable Key Results off an ambitious, deliberately-unachievable Objective. The difference is stretch vs commit.

OKRs and SMART goals both promise measurable goals, but they grade success on opposite scales. A **SMART goal** is engineered to be hit — the "A" literally stands for Achievable. An **OKR** is engineered to stretch: the convention at Intel and Google is that hitting 100% means you aimed too low. Pick the wrong one and you'll either sandbag your ambition or punish your team for missing a target that was never meant to be fully reached.

> New to objectives-and-key-results? Read [OKRs vs KPIs: the difference](/academy/okrs-vs-kpis-difference) and [OKR examples for product teams](/academy/okr-examples-for-product-teams) first — this page assumes you know what a Key Result is.

## At a glance

| | OKR | SMART Goals |
|---|---|---|
| Shape | One ambitious Objective + 2–5 measurable Key Results | One goal made Specific, Measurable, Achievable, Relevant, Time-bound |
| Metrics per goal | Multi-metric (several Key Results) | Single-metric (usually one number) |
| Attainment target | 60–80% is "strong"; 100% means it was too easy | 100% — the goal is meant to be fully met |
| Ambition | Stretch by design | Realistic by design ("Achievable") |
| Typical cycle | Quarterly (sometimes monthly) | Annual (sometimes quarterly) |
| Originated | Intel (Andy Grove, 1970s); spread by John Doerr to Google, 1999 | George T. Doran, *Management Review*, 1981 |
| Core question | "What ambitious thing are we chasing, and how will we know we're moving?" | "Is this one target specific and realistic enough to commit to?" |
| Fails when | Used for routine, must-hit commitments (people sandbag) | Used for moon-shots (the 'Achievable' clause caps ambition) |

## What OKRs are best for

**An ambitious direction that several measurable signals ladder up to.**

The OKR's defining move is splitting a goal into two parts: a qualitative, inspirational **Objective** ("Make onboarding so good new users reach value on day one") and 2–5 quantitative **Key Results** that prove progress ("activation rate 35% → 55%", "median time-to-value under 10 minutes", "NPS of new cohort ≥ 40").

Use OKRs when:

- You want a **stretch target** and you'll treat 70% attainment as success, not failure
- One objective needs **multiple leading indicators**, not a single number
- **Several teams must align** on the same direction each quarter
- You want a cadence that **re-sets quarterly** so priorities can move with the market

The deeper value of OKRs isn't the scoring — it's that the Objective forces a conversation about *why*, while the Key Results force honesty about *whether you're actually moving*. A team that can't write good Key Results usually doesn't understand its own objective yet.

## What SMART Goals are best for

**A single commitment that must be fully met on a fixed timeline.**

SMART makes one goal sharp by running it through five filters: **S**pecific, **M**easurable, **A**chievable, **R**elevant, **T**ime-bound. "Grow revenue" becomes "Increase EU subscription revenue from €2M to €2.4M by Dec 31." There's no ambitious Objective hovering above it — the sharpened target *is* the goal.

Use SMART goals when:

- The target is a **commitment** (a revenue number, a compliance deadline, a hiring plan) where 100% is the bar
- A **single metric** captures success cleanly
- You're setting **individual performance goals** in a review cycle
- The owner is a **solo founder or small team** that doesn't need cross-team alignment machinery

SMART's strength is its honesty about constraints. The "Achievable" and "Relevant" filters kill goals that sound impressive but can't or shouldn't be done — exactly the goals OKRs are willing to chase. For must-hit work, that conservatism is the feature.

> Setting goals against a fixed deadline release? The [premortem](/academy/how-to-run-a-premortem) pairs naturally with a SMART goal — it surfaces what could make you miss the target before the deadline turns the risk into a crisis.

## The decision rule: the Stretch-vs-Commit Test

The frameworks aren't competing on quality — they're built for opposite intentions. Run any goal through three questions:

1. **If you only hit 70% of this, is that a strong result or a failure?**
   Strong → OKR. Failure → SMART.
2. **Does one number capture success, or do you need several signals?**
   One number → SMART. Several → OKR.
3. **Are you aligning multiple teams, or committing one owner?**
   Multiple teams → OKR. One owner → SMART.

Two "OKR" answers means use OKRs; two "SMART" answers means use SMART. The test works because it isolates the one axis that actually separates them — **stretch vs commit** — instead of the surface features (cycle length, number of metrics) that follow from it.

**Grounded example.** When John Doerr introduced OKRs to Google in 1999, the canonical illustration was the famous "20× growth" objectives — targets nobody expected to fully hit, where reaching 70% still meant extraordinary progress. That is the OKR case: ambition you'd be thrilled to mostly reach. Contrast a regulated fintech that must "achieve SOC 2 Type II certification by March 31" — there is no 70% version of a compliance certification. You either have it or you don't. That is the SMART case: a binary commitment on a fixed date. Andy Grove built OKRs at Intel precisely because *engineering and operational* goals needed both an ambitious "what" and concrete "how-will-we-know" measures; Doran's 1981 SMART criteria were written for *managers committing to attainable objectives* — different jobs, different tools.

## Edge cases and combined use

**Use both, layered.** The most stable setup writes the Objective in OKR language, then makes each Key Result pass the SMART test. The Objective supplies ambition; SMART supplies rigor. Teams who "switched from SMART to OKRs" usually just added an Objective on top of goals they were already writing.

**Individual contributors.** SMART tends to win for personal performance goals — the review cycle wants commitments that can be fairly graded at 100%. Stretch OKRs at the individual level often backfire because compensation and performance reviews punish the 30% miss that OKRs are supposed to tolerate.

**Early-stage startups.** Before product-market fit, both are shaky. Your "Reach" and baselines are guesses, so OKR Key Results are made up and SMART's "Achievable" is unknowable. Set one or two SMART goals around survival metrics ([runway](/glossary/runway), a single activation number) and skip the OKR ceremony until you have teams to align.

**Annual vs quarterly mismatch.** If leadership sets annual SMART targets but teams run quarterly OKRs, translate: each annual SMART target becomes the parent of 1–2 quarterly OKR Objectives. The mismatch is a feature if you wire it deliberately, a mess if you don't.

## When neither is the right tool

- **Tracking ongoing operational health** — that's a [KPI](/glossary/kpi), not a goal. KPIs are the dials you monitor; OKRs and SMART goals are the targets you chase. See [OKRs vs KPIs](/academy/okrs-vs-kpis-difference).
- **Sequencing a backlog of features** — use [RICE](/academy/rice-prioritization-framework) or [RICE vs MoSCoW](/compare/rice-vs-moscow), not a goal framework.
- **Strategic positioning before you set any goal** — run [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) or a [SWOT](/academy/what-is-a-swot-analysis) with [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=compare-cta) (dedicated tool, free) to decide *what* the goal should be about first.

## Run them

[OKR catalog entry →](/frameworks/okr) · [SMART Goals catalog entry →](/frameworks/smart) · [OKRs vs KPIs explained →](/academy/okrs-vs-kpis-difference) · [OKR examples for product teams →](/academy/okr-examples-for-product-teams) · [OKR examples from Google's early years →](/examples/okr-google-classic-objective)

## Also compare

- [OKR vs MBO](/compare/okr-vs-mbo) — OKRs evolved from Management by Objectives; what changed and when MBO still wins
- [OKRs vs KPIs](/academy/okrs-vs-kpis-difference) — goals you chase vs dials you monitor
- [RICE vs MoSCoW](/compare/rice-vs-moscow) — once the goal is set, how to sequence the work under it

## Sources

- [What Matters (John Doerr) — "OKRs vs. SMART goals: What's the difference?"](https://www.whatmatters.com/resources/okrs-smart-goals-difference-between)
- [Smartsheet — "Understanding the Unique Utility of OKRs vs. SMART Goals"](https://www.smartsheet.com/content/okr-vs-smart-goals)
- [George T. Doran — "There's a S.M.A.R.T. Way to Write Management's Goals and Objectives," *Management Review*, 1981](https://en.wikipedia.org/wiki/SMART_criteria)
- [John Doerr — *Measure What Matters* (the Intel-to-Google OKR history)](https://www.whatmatters.com/the-book)

> Want to set OKRs or SMART goals on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?mt=8) — fill in any framework with AI assistance.

---

### PESTEL vs Porter's Five Forces: which strategy framework to use
URL: https://frameworklist.com/compare/pestel-vs-porters-five-forces
> PESTEL maps the macro environment around an industry. Porter's Five Forces maps the competitive structure inside it. Same word — 'external' — two different rings. Here's which to run, and when to run both.

PESTEL and Porter's Five Forces are the two frameworks every strategy course pairs, and the two students most often confuse — because both are labeled "external analysis." The distinction is one of radius. PESTEL scans the *macro environment* around a whole market. Five Forces dissects the *competitive structure* inside one industry. One tells you which way the wind is blowing; the other tells you whether the boat can make money in that water.

### Prefer to watch or listen?

<YouTube id="gOUWq5RwtzE" title="PESTEL vs Porter's Five Forces: Which One to Use" />

<Spotify id="5r90e37uOd4rM6vheecJUd" title="PESTEL vs Porter's Five Forces — Framework podcast episode" />

## At a glance

| | PESTEL | Porter's Five Forces |
|---|---|---|
| What it analyzes | The macro environment around a market | The competitive structure inside an industry |
| The "ring" | Outer ring — society-wide forces | Inner ring — industry-specific forces |
| Components | Political, Economic, Social, Technological, Environmental, Legal | Rivalry, New entrants, Substitutes, Supplier power, Buyer power |
| Question answered | "Which way is this market moving over 3–5 years?" | "Can a well-run firm make money in this industry?" |
| Time horizon | Long, directional (years) | Structural (years), but a snapshot of *now* |
| Output | 6 force scans + directional read | 5 force-strength ratings + profitability verdict |
| Origin | Aguilar (1967), evolved into PESTEL | Michael Porter, 1979–1980 |
| Best for | Market entry, geographic expansion, scenario planning | Industry attractiveness, entry/exit, M&A diligence |

## What PESTEL is best for

PESTEL earns its place when the decision turns on forces *no single firm controls* and that affect *every player in a market at once*:

- **Entering a new country or region** — Political stability, legal regimes, and economic conditions vary enormously by geography. See our worked [Amazon PESTEL analysis](/examples/amazon-pestel-analysis-2026) and [Apple PESTEL analysis](/examples/apple-pestel-analysis-2026) for how the same company faces different macro forces in different markets, the [Nike PESTEL analysis (2026)](/examples/nike-pestel-analysis-2026) for a case where the Political force (tariffs) dominates every other cell, or the [World Cup 2026 PESTEL analysis](/examples/world-cup-2026-pestel-analysis) for the same lens applied to a mega-event host economy across three countries.
- **Long-horizon planning (3–5+ years)** — PESTEL is directional. It's the natural front end to [scenario planning](/frameworks/scenario), where you stress-test which macro forces could break your plan.
- **Spotting structural shifts early** — A "Technological" or "Legal" entry in PESTEL is often the first signal of a competitive disruption that Five Forces will register only later, once entrants have actually arrived.

What PESTEL does *not* do: it never tells you whether your specific industry is profitable. A market can have every macro tailwind and still be a margin desert.

## What Porter's Five Forces is best for

Five Forces earns its place when the question is industry profitability — will *anyone* here make sustained money?

- **Industry attractiveness** — The core use. [Full Five Forces Academy guide →](/academy/porters-five-forces-beginners-guide)
- **Entry / exit / restructuring decisions** within a known industry.
- **M&A and investment diligence** — it's the default lens for judging whether a target sits in a structurally good business. See the worked [Netflix Five Forces](/examples/netflix-porters-five-forces), [Microsoft Five Forces](/examples/microsoft-porters-five-forces-analysis-2026), and [airline industry Five Forces](/examples/five-forces-airline-industry) — the last is the canonical example of a market with demand but no margin.

What Five Forces does *not* do: it's blind to macro forces brewing outside the industry. It assumes the environment is fixed while you assess the structure.

## The decision rule

> **Use PESTEL when the threat or opportunity is bigger than your industry. Use Five Forces when it lives inside your industry. Use both — PESTEL first — for any decision with a 3–5 year horizon.**

Concretely:

- A new government, an interest-rate swing, a demographic shift, a sweeping regulation → **PESTEL**.
- A new competitor, a substitute product, a supplier squeeze, a price war → **Five Forces**.
- "Should we enter this market?" → **both**, PESTEL first to confirm the environment, Five Forces second to confirm the economics.

## The Three-Ring Strategy Scan

Here is the synthesis Framework's compare library was built to support — a named way to sequence the three external/internal frameworks so each one feeds the next instead of overlapping. We call it the **Three-Ring Strategy Scan**, because each framework analyzes a different ring around your decision:

| Ring | Framework | The question | What it screens out |
|---|---|---|---|
| **Ring 1 — Macro environment** | **PESTEL** | Is the environment moving toward or against this market? | Markets the world is moving away from (declining demographics, hostile regulation) |
| **Ring 2 — Industry structure** | **Porter's Five Forces** | Can a well-run firm make money in this industry? | Industries that are structurally unprofitable for everyone (see airlines) |
| **Ring 3 — Firm position** | **SWOT** | Can *this specific firm* win the opportunity the first two rings approve? | Opportunities that are real but that this firm can't actually capture |

Run them outside-in. PESTEL can kill a market before you analyze its industry; Five Forces can disqualify an industry before you bother profiling your own firm; SWOT then asks whether you, specifically, can win the game the first two rings said is worth playing. A "go" decision should survive all three rings — most failed market entries passed one and skipped the other two.

The handoff matters more than any single ring: a strong, directional PESTEL factor should *flow into* a specific Five Forces pressure (a "Technological" tailwind lowering barriers to entry; a "Legal" change shifting buyer power), and the dominant Five Forces pressure should become a single, specific entry in SWOT's Threats — not a vague worry. When the rings are linked this way, you get a chain of reasoning; when they're run in isolation, you get three disconnected lists.

The sibling comparisons fill out the rest of this map: [SWOT vs Five Forces](/compare/swot-vs-five-forces) (Ring 3 vs Ring 2) and [SWOT vs PESTLE](/compare/swot-vs-pestle) (Ring 3 vs Ring 1).

## Edge cases and combined use

- **PESTEL feeding Five Forces.** The cleanest workflow: run PESTEL ([step-by-step here](/academy/how-to-do-a-pestel-analysis)), identify the 2–3 macro forces that are strong *and* directional, then ask which Five Forces pressure each one flows into. This turns PESTEL from a static list into a leading indicator of structural change.
- **Both folding into SWOT.** Teams often try to dump both frameworks into SWOT's Opportunities/Threats columns. It works, but loses fidelity — the dominant macro force and the dominant industry force get buried among tactical items. Better: run PESTEL and Five Forces as standalone sessions, then promote only the *single dominant force from each* into SWOT.
- **When neither is the right tool.** For product-level decisions, both are too high-level — use [RICE](/academy/rice-prioritization-framework) or [JTBD](/academy/jobs-to-be-done-framework-explained). For organizational design after a merger, use [McKinsey 7S](/academy/mckinsey-7s-framework-hard-soft-elements). For a specific risky bet, a [premortem](/academy/how-to-run-a-premortem) is sharper.

## In 30 seconds

Macro forces around a whole market → **PESTEL**. Competitive structure inside one industry → **Five Forces**. A real market-entry or expansion decision → **both, PESTEL first**, then [SWOT](/compare/swot-vs-five-forces) for your own position. That outside-in sequence is the [Three-Ring Strategy Scan](#the-three-ring-strategy-scan).

For a worked PESTEL at the widest ring — a whole national economy rather than one company — see the [PESTEL Analysis of the USA (2026)](/examples/usa-pestel-analysis-2026). It's also the clearest illustration of why the two frameworks aren't interchangeable: the US grid is dominated by a single force whose knock-on effects reshape three other cells, a coupling that no industry-level Five Forces scan would surface. The [PESTEL Analysis of Canada (2026)](/examples/canada-pestel-analysis-2026) makes the same point from the opposite direction — a country whose Political cell is not a force at all but the channel through which an external one reaches the other five. Five Forces has no cell that can represent that, which is precisely when you need the macro scan.

> Want to run these on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — fill in PESTEL, Five Forces, or any of 100+ frameworks with AI assistance.

## Sources

- [Indeed — "Pestle Analysis vs. Porter's Five Forces: What's the Difference?"](https://www.indeed.com/career-advice/career-development/pestle-analysis-vs-porters-five-forces)
- [FourWeekMBA — "Porter's Five Forces vs PESTEL Analysis: Key Differences & When to Use Each"](https://fourweekmba.com/porter-five-forces-vs-pestel-analysis/)
- [Michael E. Porter — "How Competitive Forces Shape Strategy," Harvard Business Review (1979)](https://hbr.org/1979/03/how-competitive-forces-shape-strategy)

---

### Premortem vs postmortem: opposite directions, complementary tools
URL: https://frameworklist.com/compare/premortem-vs-postmortem
> A premortem imagines failure before it happens. A postmortem investigates failure after. Same psychological technique (working backwards from failure), different timing — and different teams use them for different reasons.

The word similarity hides important differences. Both work backwards from failure; the difference is whether the failure has happened yet.

## At a glance

| | Premortem | Postmortem |
|---|---|---|
| When | Before the project ships | After a failure has occurred |
| Question | "Imagine the project failed — what caused it?" | "It failed. What actually caused it?" |
| Output | Risk mitigation plan | Root-cause analysis + action items |
| Time budget | 45–60 minutes | 60–90 minutes |
| Emotional load | Low (hypothetical) | High (real consequences) |
| Origin | Gary Klein, [*The Power of Intuition*, 2004](/frameworks/premortem) (popularized by his 2007 HBR column) | Engineering / aviation / medicine for decades |

## When to use a premortem

You're about to make a decision or ship something that's hard to reverse. The team has been working forward for weeks/months and is emotionally invested. A premortem inverts the perspective to surface risks that forward planning misses.

Typical uses:
- 1 week before a product launch
- Start of a multi-quarter initiative
- After a strategy decision but before the budget locks
- Late-stage M&A diligence

[Premortem template and full guide →](/academy/how-to-run-a-premortem#the-premortem-template)

## When to use a postmortem

Something has gone wrong. The team needs to understand what happened, name root causes, and decide what to change so the same failure doesn't recur. Postmortems are also called "incident retros" or "after-action reviews".

Typical uses:
- After a production outage
- After a launch that missed targets badly
- After a hire that didn't work out
- After a quarter where OKRs missed by >50%

## The relationship

A team running both produces a tight learning loop:

1. **Premortem** surfaces predicted failure modes → produces mitigations
2. Project ships → some predicted failures avoided, others materialize
3. **Postmortem** identifies what actually happened
4. **Compare**: which premortem predictions were right? Which were wrong? Which failures were unpredicted?

Teams that do this loop consistently get progressively better at premortems — they learn which categories of risk they tend to underweight.

## Both share one critical mechanic

Both use the same psychological move: **make the abstract risk concrete by imagining (or recovering) the failure state**.

Forward-only planning surfaces optimistic risks ("we might be slightly late") because the unconscious bias is to defend the plan. Backward thinking from failure surfaces specific risks ("user data was corrupted in week 2 because nobody had run the migration script on production volumes") because the unconscious bias flips — once failure is the frame, the mind searches for plausible causes.

This is why a premortem and a postmortem feel similar to participate in. Both ask "given that this failed, what happened?". The premortem is hypothetical, but the cognitive mechanism is identical.

That shared mechanic also sets a shared limit. "The mind searches for plausible causes" means it searches for *events* — and some failures are not events. The [Pre-mortem Example: The Failure a Premortem Cannot Catch](/examples/premortem-cydoc-shutdown) replays a premortem against a founder's published nine-cause postmortem of the same company, which is as close to a controlled comparison of the two techniques as this subject gets.

## Common failure mode (in both)

The same one: **the project owner refuses to engage with the conclusions**. In a premortem, the owner defends against every imagined failure ("that won't happen"). In a postmortem, the owner deflects blame to external factors.

Both are signs the team doesn't have the psychological safety to do the exercise honestly. Fixing that is upstream of any framework.

## Which to do first?

A new team running both for the first time should do a premortem before the next major project ships, then commit to a postmortem after. The comparison is where the learning compounds. For a concrete sense of what a premortem surfaces, see [a premortem on a product launch that almost shipped broken](/examples/premortem-product-launch) — a 45-minute session that caught two of the three risks that ended up delaying the launch.

[Open the premortem worksheet →](/tools/premortem) or read the [Academy guide](/academy/how-to-run-a-premortem). For the postmortem side, the [5 Whys entry](/frameworks/fivewhys) has the root-cause template most retrospectives are built on, and [Fishbone](/frameworks/fishbone) is where to go when the causes turn out to be plural rather than a single chain.

> **Want both rituals on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=premortem-vs-postmortem) ships the premortem and postmortem worksheets — same failure-cause structure, run before or after. Free to start.

---

### RICE vs ICE: which prioritization framework to use
URL: https://frameworklist.com/compare/rice-vs-ice
> RICE adds a Reach term that ICE leaves out. That single difference makes RICE better for teams with quantifiable user data — and ICE better for early-stage decisions where Reach is unknowable.

Both score ideas with multiplication. RICE has 4 inputs, ICE has 3. The missing term — Reach — is the entire difference, and it matters more than it looks.

> Need the RICE formula with worked examples? See [RICE score calculator: the formula with 3 worked examples](/academy/rice-score-calculator-with-examples).

> **Score a backlog on your phone** — [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=rice-vs-ice-hero) ships both the RICE and ICE calculators. Free to start.

## At a glance

| | RICE | ICE |
|---|---|---|
| Formula | (Reach × Impact × Confidence) / Effort | Impact × Confidence × Ease |
| Inputs | 4 | 3 |
| Best for | Mid-to-late stage products with usage data | Early stage / experiments where Reach is unknowable |
| Time per scoring | 5–10 min per item | 2–5 min per item |
| Origin | Intercom, 2016 | Sean Ellis / growth-hacking community |

## The Reach difference

RICE forces you to estimate **how many customers each idea affects in a given period**. That sounds obvious, but it has two effects:

1. **It penalizes ideas with narrow audiences.** A feature for 50 enterprise customers scores lower than a feature for 5,000 mid-market customers, all else equal. ICE doesn't capture this.
2. **It requires the team to have the data.** If you can't estimate Reach, you can't score RICE. For a 6-month-old startup with 200 users, Reach is approximately "everyone or nobody"; the term degrades to noise.

The Effort vs Ease difference is cosmetic — both are denominators that reward small bets. ICE phrases it positively ("Ease, 1–10") because the growth-hacker culture preferred upbeat framing.

## When to use RICE

- You have an established product with **real usage data** by feature, by user segment, by geography
- The team is scoring **a backlog** rather than testing hypotheses
- You need a **defensible quarterly prioritization** for stakeholders

Used at Intercom, Shopify, and most mid-to-late stage SaaS companies for the same reason: the Reach denominator surfaces non-obvious priorities.

## When to use ICE

- **Early stage** — limited usage data, every idea is partly speculative
- **Growth experiments** — ICE was designed for testing hypotheses, not shipping features
- **Decision under high uncertainty** — when Reach is unknowable, asking for it produces fake numbers worse than not asking

Sean Ellis's original framing: ICE was specifically built for evaluating growth hacks, where the question is *"is this worth trying?"* not *"which of these should we ship?"*

## When neither is enough

- **For specific high-stakes decisions** (which market to enter), the right tool is [SWOT](/academy/what-is-a-swot-analysis), not a scoring framework
- **For strategic positioning**, scoring frameworks don't help at all — use [Five Forces](/academy/porters-five-forces-beginners-guide)
- **For team alignment on a single bet**, a [premortem](/academy/how-to-run-a-premortem) reveals more than scoring would

## A diagnostic

If you're scoring 20+ items and you can't credibly estimate Reach for most of them, that's a signal you should be running ICE — or, more likely, that your team needs more user research before *any* scoring will produce reliable rankings.

## Run them

[Full RICE Academy guide →](/academy/rice-prioritization-framework). For ICE, the [catalog entry](/frameworks/ice) has the worksheet template.

> **Want to score a backlog on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=rice-vs-ice) ships both the RICE and ICE calculators — enter the terms, get the ranked list, no spreadsheet. Free to start.

## Also compare

- [RICE vs MoSCoW](/compare/rice-vs-moscow) — when to score an open backlog vs bucket a fixed-deadline release
- [RICE vs WSJF](/compare/rice-vs-wsjf) — when delay has a cost and time-criticality should drive the order
- [Eisenhower vs Impact/Effort Matrix](/compare/eisenhower-matrix-vs-impact-effort-matrix) — the un-quantified parents of RICE: urgent/important triage vs impact/effort selection
- [RICE vs Kano Model](/compare/rice-vs-kano) — scoring for build order vs classifying features by type of satisfaction

---

### RICE vs Kano Model: which prioritization framework to use
URL: https://frameworklist.com/compare/rice-vs-kano
> RICE scores a backlog to decide build order; Kano classifies features by the kind of satisfaction they create. The deciding question is whether you need an order or a diagnosis.

Both RICE and the Kano Model help a product team decide what to build next, but they do fundamentally different jobs. RICE produces a **number that orders a backlog**: (Reach × Impact × Confidence) ÷ Effort. Kano produces a **category that labels a feature**: is it a must-be, a performance driver, or a delighter? RICE asks *in what order?* Kano asks *what kind?* Treating them as rivals is the most common mistake — the mature answer is to run Kano first to classify, then RICE to sequence.

> Need the RICE formula with worked examples first? See [RICE score calculator: the formula with 3 worked examples](/academy/rice-score-calculator-with-examples), or the full [RICE Academy guide](/academy/rice-prioritization-framework).

## At a glance

| | RICE | Kano Model |
|---|---|---|
| Output | A score that ranks items | A category that labels items |
| Formula / method | (Reach × Impact × Confidence) ÷ Effort | Classify via paired functional/dysfunctional survey questions |
| Question it answers | In what order do we build these? | What kind of satisfaction does this create? |
| Categories / scale | Continuous score | Must-be · Performance · Delighter · Indifferent · Reverse |
| Data source | Usage data + estimates | Customer survey responses |
| Handles time / satisfaction decay | No | Yes — delighters erode to must-be over time |
| Native home | Product management (Intercom, 2016) | Quality management (Noriaki Kano, 1984) |
| Best used | Sequencing an optional backlog | Discovery — understanding the emotional value of features |
| Failure mode | Under-builds delighters (low Reach, low Confidence) | Gives no build order; classification without ranking |

## What RICE is best for

- You already have a **shortlist of comparable, optional features** and the real question is sequence, not category.
- You have **usage data** — Reach by feature, by segment, by geography is knowable rather than guessed.
- You need a **defensible quarterly ranking** to show stakeholders, and the Effort denominator forces honest cost accounting.

RICE's strength is converting a political "this feels important" argument into comparable numbers, and the Reach term specifically surfaces wide-but-unglamorous work that gut-feel rankings under-weight. Its blind spot is *type of value*: RICE treats a table-stakes login fix and a surprising delighter as the same kind of thing, differing only in score. It has no way to say "this one is non-negotiable" or "this one creates loyalty out of proportion to its Reach."

## What the Kano Model is best for

- You're in **discovery** and still deciding *which* ideas deserve to be scored at all.
- You need to separate **table stakes from differentiators** — the features that only hurt you when missing (must-be) from the ones that actively delight.
- Your market is **maturing**, and you need to see which of last year's delighters have decayed into this year's baseline expectations.

Kano's killer feature is that it prices *emotional value*, not effort. Its five categories — must-be, performance, delighter, indifferent, reverse — tell you that a fast, crash-free core (must-be) earns no praise but causes churn when absent, while an unexpected delighter creates loyalty disproportionate to how many people asked for it. Kano's blind spot is the mirror image of RICE's: it gives you *no order*. It will tell you five features are all "performance," and then leave you to decide which to build first — which is exactly the job RICE does.

## The Classify-Then-Score Rule

The cleanest way to use RICE and Kano is not to choose — it's to sequence them. Run every backlog item through this two-step rule before a single RICE score is calculated:

**Step 1 — Classify with Kano.** Sort each item into one category:

| Kano category | What it does to satisfaction | Prioritization consequence |
|---|---|---|
| **Must-be** | Absence causes active dissatisfaction; presence earns nothing | Build regardless of RICE score — it is table stakes |
| **Performance** | Satisfaction rises linearly with quality/quantity | Score with RICE — this is what RICE ranks best |
| **Delighter** | Unexpected; creates loyalty out of proportion to Reach | Reserve capacity for the top 1–2; RICE alone will bury these |
| **Indifferent** | Users don't care either way | Cut before scoring — don't waste Effort estimating it |
| **Reverse** | Presence actively annoys some users | Cut or make optional |

**Step 2 — Score the survivors with RICE.** Only *performance* features and shortlisted *delighters* go into the RICE model. Must-be features are committed unconditionally; indifferent and reverse features are dropped. RICE then decides the order of the genuinely optional value.

**The decision in one line:** Kano decides *what belongs in the scoring set*; RICE decides *the order within it*. If someone asks "RICE or Kano?", the honest answer is "Kano to classify, then RICE to rank" — the two are stages of one pipeline, not competing tools. The failure mode of skipping Kano is **The Delighter Trap**: because delighters score low on Reach (few users request them) and low on Confidence (no data yet), a pure RICE ranking systematically under-builds the exact features that would have differentiated the product.

## Worked example: Spotify's 2026 audio roadmap

Consider the kind of backlog Spotify faced heading into 2026, using only its publicly announced bets — lossless audio (its long-delayed [Lossless tier finally rolled out in late 2025](https://newsroom.spotify.com/2025-09-10/hear-every-detail-with-spotify-lossless/)), an expanding [AI DJ with voice requests](https://newsroom.spotify.com/2025-04-15/spotify-brings-ai-dj-to-more-users/), audiobook hours, and rock-solid offline playback. Classify first:

| Feature | Kano category | Why |
|---|---|---|
| Crash-free offline playback | **Must-be** | Nobody praises it; everybody churns when it fails |
| Lossless / HiFi audio | **Performance** | For engaged listeners, higher fidelity is linearly better and a competitive-parity move against Apple Music and Tidal |
| Audiobook hours in Premium | **Performance** | More included hours = more value, straightforwardly |
| AI DJ with voice requests | **Delighter** | Few users asked for it; those who use it describe it as a reason to stay |

Now the sequencing logic falls out. The must-be (playback reliability) is committed regardless of any score — it never enters the RICE model. The two **performance** features (lossless, audiobook hours) are exactly what RICE ranks well: both have knowable Reach, measurable Impact, and comparable Effort, so a RICE pass produces a defensible order between them. The **delighter** (AI DJ) is the trap: on Reach and Confidence it would lose a naive RICE ranking to audiobook hours every time — yet it is the feature most likely to move retention. Kano is what forces a team to reserve capacity for it instead of letting the spreadsheet quietly kill it.

*(Categories and ordering above are an analytical illustration of the Classify-Then-Score Rule on Spotify's public roadmap; Spotify does not publish internal Kano or RICE scores.)*

## When neither is enough

- **For a strategic bet rather than a feature** — which market to enter, whether to build at all — neither framework helps. Start with [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) or a [SWOT](/academy/what-is-a-swot-analysis).
- **When Reach is genuinely unknowable** (pre-launch, early stage), RICE's Reach term adds noise, not signal — drop to [RICE vs ICE](/compare/rice-vs-ice), where ICE removes it.
- **When a hard deadline drives the order** rather than impact-per-effort, see [RICE vs WSJF](/compare/rice-vs-wsjf) — WSJF prices the cost of delay that both RICE and Kano ignore.

## Combined use in practice

The mature setup is a two-stage funnel. Kano runs in **discovery**: a paired-question survey classifies the raw idea list, must-be features get committed, and indifferent/reverse features are cut before anyone wastes an Effort estimate on them. RICE then runs on the **survivors** — the performance features and the one or two delighters worth defending — to produce the quarterly order. A worked RICE pass on a real backlog is in [RICE applied to a SaaS Q3 backlog](/examples/rice-saas-q3-backlog); to bucket by release scope instead of scoring, see [RICE vs MoSCoW](/compare/rice-vs-moscow).

## Run them

[Full RICE Academy guide →](/academy/rice-prioritization-framework) and the [RICE catalog entry](/frameworks/rice) have worksheet templates. For classification, the [Kano Model catalog entry](/frameworks/kano) covers the five categories and the survey method.

## Also compare

- [RICE vs ICE](/compare/rice-vs-ice) — when Reach is unknowable and the third term should go
- [RICE vs MoSCoW](/compare/rice-vs-moscow) — score-based ranking vs bucket-based scope cutting
- [RICE vs WSJF](/compare/rice-vs-wsjf) — when delay has a cost and time-criticality should drive the order
- [MoSCoW vs Kano Model](/compare/moscow-vs-kano) — scope commitment vs satisfaction diagnosis, and the Kano → MoSCoW → RICE stack

## Sources

- [Intercom — "RICE: Simple prioritization for product managers"](https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/)
- [Noriaki Kano et al. — "Attractive Quality and Must-Be Quality" (foundational 1984 paper, overview)](https://en.wikipedia.org/wiki/Kano_model)
- [Spotify Newsroom — "Hear Every Detail With Spotify Lossless"](https://newsroom.spotify.com/2025-09-10/hear-every-detail-with-spotify-lossless/)
- [Spotify Newsroom — "Spotify Brings AI DJ to More Users"](https://newsroom.spotify.com/2025-04-15/spotify-brings-ai-dj-to-more-users/)

> Want to score your backlog on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=rice-vs-kano) computes RICE with AI-assisted inputs. Free to start.

---

### RICE vs MoSCoW: which prioritization framework to use
URL: https://frameworklist.com/compare/rice-vs-moscow
> RICE ranks an open backlog by score. MoSCoW scopes a fixed-deadline release into Must / Should / Could / Won't buckets. They solve different problems, and the best teams use both.

RICE and MoSCoW both call themselves prioritization frameworks, but they answer different questions. RICE produces a ranked list from an open backlog. MoSCoW carves a fixed-deadline release into Must / Should / Could / Won't. Picking one over the other comes down to whether you have a deadline or a backlog.

> New to RICE? Read [the RICE framework explained](/academy/rice-prioritization-framework) or run the math in [RICE score calculator: 3 worked examples](/academy/rice-score-calculator-with-examples).

## At a glance

| | RICE | MoSCoW |
|---|---|---|
| Format | Score (number) | Bucket (category) |
| Inputs | Reach × Impact × Confidence ÷ Effort | Must / Should / Could / Won't |
| Output | Ranked list of all items | Four buckets of items |
| Best for | Ranking an open backlog | Scoping a fixed-deadline release |
| Originated | Intercom, 2016 | DSDM Atern, late 1990s |
| Team conversation | "Which of these scores highest?" | "What absolutely has to ship by date X?" |
| Time per item | 5–10 min | 1–3 min |
| What it doesn't tell you | Where to draw the cut line for a deadline | The magnitude of difference between items |

## What RICE is best for

**Ranking an open backlog with usage data.**

RICE gives you a single number per item — derived from four explicit inputs — that lets you sort 50 ideas into a ranked list. The number is unit-less, which is the point: you're not comparing one team's RICE to another's, just one item to the next in the same backlog.

Use RICE when:

- You're planning a **quarterly roadmap** and need to defend the order to stakeholders
- You have **real usage data** by feature, segment, or geography (otherwise Reach is a guess)
- The backlog has **20+ items** and arguing them one by one is wasting cycles
- You want a **rubric the team can re-run** next quarter without restarting the debate

The deeper value of RICE isn't the ranking — it's that the math exposes which numbers everyone is guessing at. When two scorers diverge on Confidence by 30 points, that's a discussion worth having. When they agree on every input, the score adds little; you already had alignment.

## What MoSCoW is best for

**Scoping a release where the deadline is non-negotiable.**

MoSCoW puts every candidate item into one of four buckets:

- **Must have** — release fails without this; the deadline slips before this gets cut
- **Should have** — important and high-value, but the release can ship without it if needed
- **Could have** — nice to include if time permits; quietly drops first
- **Won't have (this cycle)** — explicitly excluded, with a reason and a future cycle attached

Use MoSCoW when:

- A **deadline is fixed** (regulatory, contractual, conference launch, customer commit)
- Stakeholders keep asking "is X in or out?" mid-sprint
- The team has **trust in qualitative judgment** and doesn't need a score to defend a cut
- The release is **finite** — not an ongoing backlog, but a defined slice

MoSCoW's strength is its lack of math. There's no scoring system to game, no Confidence percentage to argue. The conversation is forced into yes/no terms: would the release fail without this? If yes, Must. If no, Should at most.

> Building toward a deadline release? The [premortem](/academy/how-to-run-a-premortem) pairs naturally with MoSCoW — premortem reveals what could go wrong with each Must, surfacing risks before the deadline turns them into emergencies.

## The decision rule

**Use RICE when the question is "what do we work on next?"**
**Use MoSCoW when the question is "what makes the cut for date X?"**

If you have a deadline AND an open backlog, you need both. Most teams who feel torn between RICE and MoSCoW are actually facing this combined case — they default to one framework, struggle, then add the other later.

A working pattern:

1. **MoSCoW first** — bucket the candidate list into Must / Should / Could / Won't for the release
2. **RICE inside Must and Should** — score those buckets to sequence engineering pickup
3. **Could bucket gets ad-hoc judgment** — not worth scoring; if there's time, take the obvious wins

This sequence matches how planning meetings actually run: stakeholders care about scope (MoSCoW); engineers care about order (RICE). Each framework speaks to the audience that owns its question.

## Edge cases

**Early-stage products.** Neither framework works cleanly. You don't have usage data for RICE's Reach term, and you don't have enough features for MoSCoW's bucketing to do real work. At this stage, use [ICE](/compare/rice-vs-ice) for scoring growth experiments, and just write a one-page release scope by hand.

**Heavily regulated industries.** MoSCoW dominates because compliance items are non-negotiable Musts; the framework's lack of math matches the binary nature of "does this meet the regulation, yes or no." RICE would mislead by suggesting a regulatory feature could be deprioritized for higher-scoring work.

**Large engineering orgs (50+).** RICE travels better across teams because the score is portable and comparable within a domain. MoSCoW's buckets depend on shared context about what "Must" means — when teams don't share that context, the buckets fragment.

**Consultancies on short engagements.** MoSCoW was originally built for DSDM (a UK agile consultancy methodology) for exactly this reason. The client has a budget, a deadline, and a list of asks. MoSCoW carves the list against the budget faster than scoring would. RICE is overkill for engagements under 8 weeks.

**Reverse-engineering an existing roadmap.** If someone hands you a sequenced roadmap and asks whether the order is defensible, score the top 10 items with RICE. The resulting list either confirms the original sequence (then defend it) or surfaces 2–3 items that look mis-prioritized (then negotiate).

## Common combined use

The most stable pattern in mid-sized SaaS teams (engineering 10–50, product 2–5):

- **Annually**: leadership sets quarterly Must goals at the company level (OKR-style)
- **Quarterly**: each team runs **MoSCoW** to scope the release shape against the quarter's deadline
- **Sprint planning**: **RICE** ranks the inside of the Must and Should buckets to drive ticket order
- **Mid-quarter checkpoint**: if Could items get pulled up, re-score them with RICE against current Must items so the swap is defensible

You'll see RICE scores show up in Linear or Jira as a custom field. MoSCoW typically lives in a release-planning Confluence page or a kickoff Notion doc — it's an artifact of the planning meeting, not a permanent backlog property.

## When neither is enough

- **Strategic positioning decisions** — use [Porter's Five Forces](/academy/porters-five-forces-beginners-guide), not a scoring framework
- **Risk-driven prioritization on big bets** — use a [premortem](/academy/how-to-run-a-premortem) to surface what could fail
- **Cross-functional alignment on a single direction** — use [SWOT](/academy/what-is-a-swot-analysis) with [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=compare-cta) (dedicated tool, free)
- **Comparing strategic options across markets** — [BCG Matrix](/frameworks/bcg) or [Ansoff Matrix](/frameworks/ansoff)

## Run them

[Full RICE Academy guide →](/academy/rice-prioritization-framework) · [RICE calculator with worked examples →](/academy/rice-score-calculator-with-examples) · [MoSCoW Method catalog entry →](/frameworks/moscow)

## Also compare

- [RICE vs ICE](/compare/rice-vs-ice) — when Reach is unknowable and the third term should go
- [RICE vs WSJF](/compare/rice-vs-wsjf) — when delay has a cost and time-criticality should drive the order
- [RICE vs Kano Model](/compare/rice-vs-kano) — scoring for build order vs classifying features by type of satisfaction
- [MoSCoW vs Kano Model](/compare/moscow-vs-kano) — scope commitment vs satisfaction diagnosis, and the Kano → MoSCoW → RICE stack

> Want to score RICE on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?mt=8) — fill in any framework with AI assistance.

---

### RICE vs WSJF: which prioritization framework to use
URL: https://frameworklist.com/compare/rice-vs-wsjf
> RICE optimizes for total user impact; WSJF optimizes for economic throughput when delay has a cost. The deciding question is whether an item's value decays with time.

Both RICE and WSJF reduce a backlog to a single number, and both divide value by a size term so small bets float up. The difference is what sits in the numerator: RICE multiplies **Reach × Impact × Confidence**, while WSJF uses **Cost of Delay**. RICE asks *how much total user value does this create?* WSJF asks *how much value do we lose by shipping it late?* That is the entire comparison — and it decides which framework fits your team.

> Need the RICE formula with worked examples first? See [RICE score calculator: the formula with 3 worked examples](/academy/rice-score-calculator-with-examples), or the full [RICE Academy guide](/academy/rice-prioritization-framework).

## At a glance

| | RICE | WSJF |
|---|---|---|
| Formula | (Reach × Impact × Confidence) ÷ Effort | Cost of Delay ÷ Job Size |
| Optimizes for | Total user impact per unit of effort | Economic throughput when delay is costly |
| Time-criticality term | None | Built in (Time Criticality is part of Cost of Delay) |
| Inputs | 4 estimated numbers per item | Cost of Delay (3 sub-scores) + Job Size |
| Scoring scale | Reach in real units; Impact 0.25–3; Confidence 50–100% | Relative Fibonacci (1, 2, 3, 5, 8, 13) |
| Native home | Product management (Intercom origin, 2016) | Scaled Agile Framework / SAFe |
| Best team shape | Single product team, open backlog | Multi-team program sequencing dependencies |
| Origin of the value concept | Reach (audience breadth) | Cost of Delay (Reinertsen / flow economics) |

## What RICE is best for

- You have an **established product with real usage data** — Reach by feature, by segment, by geography is knowable rather than a guess.
- You're ranking an **open backlog** where the dominant question is "which of these creates the most user value for the work involved," and few items have hard deadlines.
- You need a **defensible quarterly prioritization** to show stakeholders, and the Effort denominator forces honest cost accounting.

RICE's strength is that it converts a political "this feels important" conversation into comparable numbers, and the Reach term specifically surfaces wide-but-unglamorous work that gut-feel rankings under-weight. Its blind spot is timing: RICE has no clean way to say "this is worth half as much if we ship it in Q3 instead of Q1."

## What WSJF is best for

- **Delay erodes the value** of the work — regulatory deadlines, competitive responses, seasonal launches, contractual dates. Cost of Delay is designed to capture exactly this.
- You're running a **multi-team program** (the SAFe context WSJF was built for) and need a shared, throughput-maximizing sequence across dependencies.
- The backlog is full of items where **finishing small things quickly frees capacity** for the bigger bets — WSJF's division by Job Size formalizes that intuition.

WSJF's killer feature is making time-criticality explicit. By pricing the cost of delay, it pushes items where waiting destroys value to the top — the kind of work RICE systematically under-ranks because its numerator is time-blind. Its blind spot is reliability of estimates: relative Fibonacci scoring across many teams drifts, and "Job Size" guesses are weakest at the start of complex work.

## The Cost-of-Delay Test

The cleanest way to choose between RICE and WSJF is not to compare their formulas — it's to ask one question about your *backlog*, not your *process*:

**Does the value of a typical item decay with time?**

Run each candidate item through three yes/no checks:

1. **Deadline pressure** — Is there a hard external date (regulation, contract, market window, season) after which this is worth materially less?
2. **Competitive decay** — Does a rival shipping first erode what this is worth to us?
3. **Compounding loss** — Does every week of delay actively cost us (churn, lost revenue, accruing risk), not just postpone a gain?

| Answers across your backlog | Use | Why |
|---|---|---|
| Mostly **No** to all three | **RICE** | Value is time-invariant; impact-per-effort is the right optimization |
| Mostly **Yes** to one or more | **WSJF** | Cost of Delay is real and RICE can't see it |
| **Split** — some items decay, most don't | **RICE backlog-wide, WSJF on the decaying subset** | Don't distort the whole ranking for a few time-bombs |

**The decision in one line:** if delay is cheap, RICE; if delay is expensive, WSJF. The frameworks aren't competing on rigor — they're tuned for different cost structures, and the Cost-of-Delay Test tells you which structure you're in before you waste a scoring session on the wrong one.

## When neither is enough

- **For a specific high-stakes strategic bet** (which market to enter, whether to build at all), scoring frameworks don't help — start with [SWOT](/academy/what-is-a-swot-analysis) or [Porter's Five Forces](/academy/porters-five-forces-beginners-guide).
- **For team alignment on a single risky launch**, a [premortem](/academy/how-to-run-a-premortem) reveals more than any score.
- **When Reach itself is unknowable** (early-stage, pre-launch), drop to [RICE vs ICE](/compare/rice-vs-ice) — ICE removes the Reach term that both RICE and WSJF assume you can estimate.

## Combined use in practice

The most common mature setup separates the two by lifecycle stage. RICE governs the **discovery backlog** — deciding which bets are worth pursuing on impact-per-effort. WSJF governs the **committed delivery backlog** — sequencing what's already been greenlit, where cost of delay and job size decide execution order. A worked RICE pass on a real backlog is in [RICE applied to a SaaS Q3 backlog](/examples/rice-saas-q3-backlog); the [WSJF glossary entry](/glossary/wsjf) covers the Cost of Delay sub-scores in detail.

## Run them

[Full RICE Academy guide →](/academy/rice-prioritization-framework) and the [RICE catalog entry](/frameworks/rice) have worksheet templates. For WSJF, the [WSJF glossary entry](/glossary/wsjf) breaks down the Cost of Delay composite.

## Also compare

- [RICE vs ICE](/compare/rice-vs-ice) — when Reach is unknowable and the third term should go
- [RICE vs MoSCoW](/compare/rice-vs-moscow) — when to score an open backlog vs bucket a fixed-deadline release

## Sources

- [Intercom — "RICE: Simple prioritization for product managers"](https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/)
- [Scaled Agile Framework — "WSJF (Weighted Shortest Job First)"](https://scaledagileframework.com/wsjf/)
- [Centercode — "RICE vs WSJF: Choosing the Right Prioritization Framework"](https://www.centercode.com/blog/rice-vs-wsjf-prioritization-framework)

> Want to score your backlog on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=rice-vs-wsjf) computes RICE with AI-assisted inputs. Free to start.

---

### SWOT vs Porter's Five Forces
URL: https://frameworklist.com/compare/swot-vs-five-forces
> SWOT analyzes a specific position. Five Forces analyzes the industry that position sits inside. Confusing them produces strategy decisions that don't survive contact with the market.

These are the two most-recognized strategy frameworks. Both feel like "competitive analysis" tools, which is why they get conflated. The difference matters: SWOT is about *who you are*; Five Forces is about *which game you're playing*.

## At a glance

| | SWOT | Five Forces |
|---|---|---|
| What it analyzes | A specific firm, product, or position | An entire industry's structure |
| Unit of analysis | One company / one decision | One market / one industry segment |
| Time horizon | Snapshot (months) | Structural (years) |
| Output | 4 quadrants of actions | 5 force-strength assessments + structural verdict |
| Question answered | "What should this team do?" | "Is this a good industry to be in?" |
| Origin | Humphrey at SRI, 1960s | Michael Porter, 1980 |

## When to use SWOT

You're evaluating a specific decision facing a specific organization — for instance, a founder working through whether to [pivot or persevere](/decisions/pivot-or-persevere) on the current product. The internal/external structure (S/W are internal; O/T are external) directs you to actions that fit your particular situation.

[Full SWOT Academy guide →](/academy/what-is-a-swot-analysis)

## When to use Five Forces

You're trying to understand the long-run profitability potential of an industry, or you're deciding whether to enter / exit / restructure within an industry.

[Full Five Forces Academy guide →](/academy/porters-five-forces-beginners-guide)

## The pattern that works

**Five Forces first, then SWOT** — when entering or evaluating an industry.

1. Five Forces tells you whether the industry is structurally attractive (will *any* well-run firm here make money?)
2. If yes, SWOT tells you whether *this specific firm* has the position to capture that opportunity.

A SWOT done without industry context produces strategy that ignores structural forces. A Five Forces without SWOT tells you the game is worth playing but not whether you can win it.

## The conflation pattern

Teams sometimes try to fold Five Forces into SWOT's Threats quadrant. This sort of works but loses fidelity — the Threats quadrant becomes a long list, and the structural force most likely to dominate gets buried among tactical threats.

The cleaner pattern: do Five Forces as a standalone session. Identify the *dominant* force (usually one of the five is much stronger than the others). Then in SWOT, the dominant force becomes a single specific entry in Threats — with the structural reasoning behind it documented in the Five Forces output.

## Common failure mode

**Treating internal capability (SWOT strength) as a substitute for industry structure (Five Forces).** A team will say "we have a strong team and great product — we can win in this market." But if Five Forces shows the industry compresses every player's margins to near zero (e.g., airlines), team quality doesn't save you. Buffett famously made this mistake on airlines twice.

The diagnostic question: if you're certain you have strengths but the industry has shown long-run low returns for everyone, the structural force is winning. Either change the game (find a niche the structural forces don't dominate) or pick a different industry.

## When neither is the right tool

- For **product-level decisions**, both are too high-level — use [RICE](/academy/rice-prioritization-framework) or [JTBD](/academy/jobs-to-be-done-framework-explained)
- For **risk evaluation on a specific bet**, a [premortem](/academy/how-to-run-a-premortem) is sharper
- For **organizational design**, use McKinsey 7S, not Five Forces

## In 30 seconds

Specific position, specific decision → **SWOT**. Whole industry, structural question → **Five Forces**. Real strategy work → **both, Five Forces first**.

For a worked Five Forces on a real company, see [Netflix Porter's Five Forces 2026](/examples/netflix-porters-five-forces). To see where the macro environment fits above the industry ring, read [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces). For the SWOT counterpart, our sister site [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=compare-cta) is the dedicated SWOT generator.

> **Want to run Five Forces on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=swot-vs-five-forces) walks each force with AI-assisted prompts. For SWOT specifically, [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=compare-cta-ios) is the dedicated tool.

---

### SWOT vs PESTLE: which one to use when
URL: https://frameworklist.com/compare/swot-vs-pestle
> SWOT is a position assessment. PESTLE is a macro-environment scan. They're not substitutes — they answer different questions and often get used together.

The mistake most teams make: picking SWOT *or* PESTLE when they need both, or picking one when they actually need a different tool entirely.

## At a glance

| | SWOT | PESTLE |
|---|---|---|
| What it analyzes | A specific strategic position | The macro environment |
| Scope | One company, product, or decision | An industry or market |
| Time horizon | Current snapshot | Multi-year trends |
| Output | 4 quadrants (S/W/O/T) | 6 force categories (Political, Economic, Social, Technological, Legal, Environmental) |
| Best for | Evaluating a specific choice | Spotting macro shifts that affect strategy |
| Typical session | 60–90 minutes | 90–120 minutes |

## When to use SWOT

You're evaluating something specific — a position, a decision, a product launch. The internal/external split tells you what you control vs what you don't. Output is action-oriented.

Examples:
- "Should we enter the Japan market?"
- "What's our position vs the new competitor that just raised?"
- "Should this team take on the migration project?"

## When to use PESTLE

You're trying to understand the *environment* a business operates in — independent of any specific decision. Useful for strategic planning at the industry or category level.

Examples:
- "What macro forces will shape our industry over the next 3 years?"
- "How might regulation change the legal landscape we operate in?"
- "What technological shifts could re-set the cost structure of our sector?"

## When to use both together

The pattern that actually works: **PESTLE first to inform the Opportunities and Threats quadrants of a SWOT.**

PESTLE catches macro forces a SWOT would miss because the team is too close to the day-to-day. Once PESTLE has identified the 3–4 environmental forces that matter, those become specific entries in SWOT's external quadrants. The combined output is much sharper than either alone.

This pattern is standard in M&A diligence — the strategy consultants run a PESTLE on the target industry, then build SWOT on the target company informed by it.

## When neither is right

- For **competitive position within an industry**, [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) is more specific than either SWOT or PESTLE — and [PESTEL vs Porter's Five Forces](/compare/pestel-vs-porters-five-forces) shows how the macro and industry rings hand off to each other
- For **prioritizing a backlog**, neither — use [RICE](/academy/rice-prioritization-framework)
- For **a personal decision**, neither — Pros/Cons or Eisenhower is enough

## How to choose in 30 seconds

- Decision about something specific you control? → **SWOT**
- Trying to understand the industry's trajectory? → **PESTLE**
- Both? → **PESTLE first, then SWOT**

## Run them

[Open the SWOT worksheet →](/tools/swot) (free) or [read the SWOT Academy guide →](/academy/what-is-a-swot-analysis). For PESTLE, [the catalog entry](/frameworks/pestel) has a worksheet template — and our [Amazon PESTEL analysis 2026](/examples/amazon-pestel-analysis-2026) is a worked company-level example with six current macro forces scored against a real operator.

> **Want to run PESTLE on your phone?** [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580?utm_source=framework&utm_medium=ios-cta&utm_campaign=swot-vs-pestle) scans all six macro factors with AI-assisted prompts and keeps the scan next to your other frameworks. Free to start.

## If you've decided on SWOT

Use [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=compare-cta) — it's a dedicated SWOT generator with AI assistance. Free for the basic workflow.

---

## Framework vs other tools

### ChatGPT vs Framework for strategy: prose or a real canvas?
URL: https://frameworklist.com/vs/chatgpt-for-strategy
> ChatGPT is a brilliant strategy brainstorming partner — but it returns prose you can't rank or export. Framework returns a structured, editable canvas. Here's the honest head-to-head.

Ask ChatGPT to "do a SWOT analysis of my business" and it will hand you four tidy paragraphs in seconds. It's genuinely useful — and it's the reason "[chatgpt for strategy](https://chat.openai.com/)" is one of the most common AI queries there is. But look closely at what you actually received: prose, in a chat thread, that you can't sort, can't score, can't mark up, and that scrolls out of view the moment you ask a follow-up. [Framework](/) starts from the same AI assistance and ends somewhere different — a structured canvas built for the specific framework you picked. This is the honest comparison of when each one wins.

## At a glance

| | ChatGPT | Framework |
|---|---|---|
| What it is | General-purpose AI chat | A library of 100+ strategy frameworks with an AI co-pilot |
| What you get back | Prose in a conversation thread | A structured, editable canvas (2×2 SWOT, scored RICE table, Porter's grid) |
| Framework library | None — you describe the framework each time | 100+ named frameworks, each with its own input shape |
| AI output | Free-form text | Written directly into the framework's structure |
| Edit & refine | Re-prompt in chat | Edit the canvas in place, or refine in plain English |
| AI vs. your input | Indistinguishable | Every AI-generated item is visually marked |
| Export | Copy-paste, reformat yourself | One-page typeset brief (PDF), Notion export |
| Best at | Open-ended thinking, drafting, breadth | Producing a specific, structured, reusable deliverable |
| Pricing | Flat monthly subscription (ChatGPT Plus) | Free · Premium $9.99/mo · Ultra $14.99/mo (more flagship models) |

## What ChatGPT is best for

ChatGPT is the better tool whenever the value is in the *thinking*, not the artifact:

- **Open-ended ideation.** "What are five ways we could enter this market?" is a question ChatGPT answers brilliantly. There's no framework to fill — you want range, and chat gives you range.
- **Drafting and rewriting.** Turning a rough strategy into a polished memo, a board narrative, or an email is squarely ChatGPT's strength.
- **One-off questions across any domain.** Strategy today, a regex tomorrow, a recipe tonight. ChatGPT's generality is the whole point.
- **Pressure-testing an idea conversationally.** The back-and-forth of "what's wrong with this plan?" is a genuine strength of a chat interface.

What ChatGPT does *not* do: it doesn't hand you a structured, rankable, exportable canvas. The output is text, and text is where it stops.

## What Framework is best for

Framework is the better tool when you already know which framework you want and you need a *result you can use*:

- **Structured output, not prose.** Pick [SWOT](/academy/what-is-a-swot-analysis), [RICE](/academy/rice-prioritization-framework), [Porter's Five Forces](/academy/porters-five-forces-beginners-guide), or any of [100+ frameworks](/frameworks), describe your situation in a sentence, and the AI fills the actual canvas — a real 2×2, a scored table you can re-sort, a five-force grid — not a paragraph describing one.
- **Edit and rank in place.** A RICE backlog you can re-sort by score is a different object from a chat message listing scores. You work *with* the structure.
- **Know what's AI and what's yours.** Every AI-generated item is marked, so a brief you take into a meeting is one you can stand behind.
- **Export a one-page brief.** Framework produces a typeset deliverable — context, top quick wins, the one big bet, what to cut — plus one-click [Notion export](/integrations). No copy-paste-and-reformat.
- **Repeatable workflow.** When framework analysis is a recurring part of your job, a purpose-built library beats re-describing the framework to a chatbot every time.

What Framework does *not* do: it's not a general assistant. It won't write your code or answer trivia. It's opinionated about one thing — the shape of strategic thinking.

## The honest pick

> **Use ChatGPT when the job is open-ended thinking, drafting, or a one-off question. Use Framework when you want a specific framework filled into a structured canvas you can edit, rank, and export. The fastest workflow uses both: ideate in ChatGPT, build the deliverable in Framework.**

Concretely:

- "Help me think through whether to expand" → **ChatGPT**.
- "Give me a SWOT 2×2 / a ranked RICE backlog / a Porter's grid I can edit and export" → **Framework**.
- "Draft the board memo from this analysis" → **ChatGPT**, fed by the brief Framework produced.

The two aren't really enemies. Chat is where strategy starts messy; a canvas is where it becomes a deliverable. The mistake is using a chat thread as your system of record for a decision — prose scrolls away, and a 2×2 you can export doesn't.

## See also

- [Framework vs Notion AI](/vs/notion-ai-alternative) — purpose-built canvases vs a general doc assistant
- [Framework vs Miro](/vs/miro-ai-alternative) — guided AI fill vs a freeform whiteboard
- [Meta Muse vs Framework's Decision Agent](/vs/meta-muse-alternative) — a personal agent that does tasks vs one that makes the decision
- [Compare frameworks head-to-head](/compare) — SWOT vs PESTLE, RICE vs ICE, and more
- [Pricing](/pricing) — Free, Premium, and Ultra tiers

> Want structured strategy canvases on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — 100+ frameworks, AI-filled, exportable, synced across web, iPhone, and iPad.

## Sources

- [OpenAI — ChatGPT](https://chat.openai.com/)
- [Framework — Pricing](https://frameworklist.com/pricing)

---

### Meta Muse vs Framework's Decision Agent: which personal agent for business decisions?
URL: https://frameworklist.com/vs/meta-muse-alternative
> Meta Muse is a general personal agent that books, buys, and fills forms. Framework's Decision Agent is narrow: it runs strategy frameworks on one decision and hands back a brief. The honest head-to-head.

Meta's [Muse](https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/) made "personal agent" a mainstream product category in September 2026: tell it what you need, close the app, and it works in the background — reading email, booking travel, filling in forms, paying bills. Framework's [Decision Agent](/app/agent) borrows the same "delegate it and walk away" shape but applies it to a much narrower job: making one business decision well. This is the honest comparison of when each one wins.

## At a glance

| | Meta Muse | Framework Decision Agent |
|---|---|---|
| What it is | General personal AI agent | An agent that runs strategy frameworks on one decision |
| The job | Do things: email, travel, forms, bills, purchases, business apps | Decide: analyse the question and recommend |
| What you hand it | A task | A decision in one sentence |
| What comes back | The task done (it pauses for approval before sending or buying) | A decision brief: recommendation, scored options, risks, 30/60/90-day plan |
| Method | General reasoning plus tools and connectors | 2–3 named frameworks (SWOT, Pre-mortem, Regret Minimization…) chained into a brief |
| Works in the background | Yes | Yes — close the tab, get an email |
| You approve | Before it sends or spends | The framework plan, before it runs |
| Output you keep | Whatever the task produced | Editable canvases + a brief in your library, PDF and Notion export |
| Availability | US only, 18+; iOS, Android, web, WhatsApp, Mac | Web, iPhone, iPad; no country restriction; EN / JA / zh-TW |
| Pricing | Free · Power $20/mo · Maximum $100/mo (reported) | Included in Ultra, $14.99/mo (~18–20 decisions/month) |

## What Muse is best for

Muse is the better tool whenever the work is *execution*:

- **Life admin on autopilot.** Inbox triage, travel and appointment booking, forms, bills — the jobs Meta built Muse around.
- **Buying things.** Muse can complete purchases (through Link by Stripe) and stops for your approval before it spends.
- **Running a small business's busywork.** Since September 29, [Muse for Small Business](https://www.unite.ai/meta-adds-small-business-skills-and-app-connectors-to-muse-ai-agent/) connects to tools like Shopify, Stripe, QuickBooks, Notion and Slack, plus Instagram and Facebook Pages.
- **Living where you already chat.** Muse is reachable through WhatsApp as well as its own apps.

What Muse doesn't offer: a library of strategy frameworks or a structured decision brief. It's a generalist that does tasks, not a method for deciding.

## What Framework's Decision Agent is best for

The Decision Agent is the better tool when the hard part is *the decision itself*:

- **A method, not an opinion.** It picks frameworks that fit the question — [SWOT](/academy/what-is-a-swot-analysis), Pre-mortem, Regret Minimization, [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) and [100+ others](/frameworks) — and tells you why it chose each before running anything.
- **Reasoning you can check.** Each framework becomes a real canvas you can open and edit, so a co-founder or investor can see *how* the recommendation was reached.
- **A brief you can act on.** The output is a one-page decision brief: the sharpened decision, an issue tree, scored options, a recommendation with supports and risks, and a 30/60/90-day plan.
- **Hands-off, with one checkpoint.** You approve the plan once; it runs in the background and emails you when it's done.
- **Not US-only.** Works anywhere on the web, iPhone and iPad.

What the Decision Agent doesn't do: it won't book, buy, send or file anything for you. It stops at the decision.

## The honest pick

> **Use Muse when the task is getting something done. Use Framework's Decision Agent when the task is deciding what to do. The strongest workflow chains them: decide in Framework, then let Muse execute the plan.**

Concretely:

- "Book the flights and send the invites for our offsite" → **Muse**.
- "Should we raise prices 10% this quarter?" → **Framework's Decision Agent**.
- "Do the 30-day tasks from that pricing brief" → **Muse**, working from the brief Framework produced (export it to [Notion](/integrations), which Muse for Small Business connects to).

A capable general agent will happily give you an answer to a strategic question. The difference is whether you can see the reasoning, challenge it, and reuse it. That's the gap a framework-based agent is built to fill.

## See also

- [Meta Muse through Jobs-to-be-Done](/blog/meta-muse-jobs-to-be-done) — which jobs people actually hand a personal agent, scored on CNN's hands-on test
- [Framework vs ChatGPT for strategy](/vs/chatgpt-for-strategy) — prose answers vs structured canvases
- [Framework vs Notion AI](/vs/notion-ai-alternative) — purpose-built canvases vs a general doc assistant
- [Pivot or persevere](/decisions/pivot-or-persevere) — a worked three-framework decision chain
- [Pricing](/pricing) — Free, Premium, and Ultra tiers

## Sources

- [Meta — Introducing Muse](https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/)
- [Axios — Meta debuts Muse, its long-planned personal AI agent](https://www.axios.com/2026/09/08/meta-debuts-muse-personal-ai-agent)
- [CNBC — Meta pushes into personal AI agents](https://www.cnbc.com/2026/09/08/meta-personal-ai-agents-public-reckoning-privacy-safety.html)
- [Unite.AI — Meta adds small business skills and app connectors to Muse](https://www.unite.ai/meta-adds-small-business-skills-and-app-connectors-to-muse-ai-agent/)
- [Tech Insider — Muse pricing tiers (reported)](https://tech-insider.org/meta-muse-personal-ai-agent-launch-2026/)
- [Framework — Pricing](https://frameworklist.com/pricing)

---

### Miro AI alternative for strategy: Framework vs Miro
URL: https://frameworklist.com/vs/miro-ai-alternative
> Miro is the best freeform whiteboard for team workshops. But a sprawling board isn't a decision. Framework gives you a guided, AI-filled canvas and a one-page brief. The honest comparison.

"[Miro ai alternative](https://miro.com/ai/)" is usually searched by someone who loves Miro for workshops but found that an infinite whiteboard, for all its energy, doesn't hand you a *decision*. A board full of sticky notes is a record of a conversation — and turning it into a one-page brief is still manual work. That's the gap [Framework](/) fills. Both tools offer strategy-framework templates; they optimize for opposite moments. Here's the honest comparison.

## At a glance

| | Miro | Framework |
|---|---|---|
| What it is | Infinite freeform whiteboard for team collaboration | A library of 100+ strategy frameworks with an AI co-pilot |
| Optimized for | Live, multiplayer workshops | A structured, AI-filled canvas + a decision brief |
| Frameworks | Templates you fill in by hand on the board | Canvases the AI fills from a one-sentence prompt |
| AI | Miro AI / Assist as an add-on | AI fill is the default behavior |
| Collaboration | Real-time multiplayer, sticky notes, voting | Single-user / small-team, synced across your devices |
| Output | A sprawling shared board | A typeset one-page brief (PDF) + Notion export |
| Best at | Facilitating a session, divergent thinking | Producing a convergent, shippable deliverable |
| The artifact | The canvas *is* the record | The brief is the record |

## What Miro is best for

Miro is the better tool when the value is the *room* — people thinking together, live:

- **Workshops and facilitation.** An infinite canvas with multiplayer cursors, sticky notes, timers, and voting is purpose-built for a group working in real time.
- **Divergent, visual thinking.** Mind maps, journey maps, affinity diagrams, big messy clusters of ideas — Miro thrives on breadth and spatial layout.
- **Cross-functional collaboration.** When twelve people need to draw on the same surface at once, that's Miro's home turf.
- **Freeform structure.** No opinion about the shape of the output — you arrange the canvas however the session needs.

What Miro does *not* do: it doesn't fill the framework for you or distill the board into a one-page decision. The sprawl that makes it great for sessions makes it weak as a deliverable.

## What Framework is best for

Framework is the better tool when the value is the *deliverable* — a structured, shareable decision:

- **AI fills the canvas.** Describe your situation in a sentence and the AI populates the actual [SWOT](/academy/what-is-a-swot-analysis), [RICE](/academy/rice-prioritization-framework), or [Porter's](/academy/porters-five-forces-beginners-guide) structure — no manual sticky-note arranging.
- **Guided, not freeform.** Each of the [100+ frameworks](/frameworks) enforces the right shape, so you get a real 2×2 or a scored table, not a blank infinite plane to organize.
- **A one-page brief.** Framework distills the canvas into context, top quick wins, the one big bet, and what to cut — the artifact you actually hand to a decision-maker.
- **Marked AI vs. yours**, plus one-click [Notion export](/integrations) and sync across web, iPhone, and iPad.

What Framework does *not* do: it's not a multiplayer whiteboard. For a live 20-person facilitation, Miro is the right tool.

## The honest pick

> **Use Miro when the deliverable is a shared visual workspace and the value is a live session. Use Framework when the deliverable is a structured, exportable decision and you want AI to fill the canvas. The natural workflow: diverge in Miro, converge in Framework.**

Concretely:

- "We're running a strategy workshop with the whole team Thursday" → **Miro**.
- "I need a clean SWOT / ranked RICE backlog / one-page brief from this" → **Framework**.
- "We brainstormed on a board and now need the decision document" → **Miro → Framework**.

The board and the brief are different artifacts. Miro is unbeatable for the room; Framework is built for what you ship after.

## See also

- [Framework vs ChatGPT for strategy](/vs/chatgpt-for-strategy) — structured canvas vs prose
- [Framework vs Notion AI](/vs/notion-ai-alternative) — AI-filled canvases vs a general doc assistant
- [Framework vs Strategyzer](/vs/strategyzer-alternative) — 100+ frameworks vs a Lean/BMC-centric tool
- [Compare frameworks head-to-head](/compare)

> Want a guided, AI-filled strategy canvas on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — 100+ frameworks, one-page briefs, synced across web, iPhone, and iPad.

## Sources

- [Miro — AI](https://miro.com/ai/)
- [Framework — Pricing](https://frameworklist.com/pricing)

---

### Notion AI alternative for strategy frameworks: Framework vs Notion
URL: https://frameworklist.com/vs/notion-ai-alternative
> Notion AI is a brilliant writing assistant inside your docs. But strategy frameworks are templates you fill by hand. Framework makes the AI fill the canvas. Here's the honest comparison.

Search "[notion ai alternative](https://www.notion.so/product/ai)" and a lot of the intent is people who tried to run their strategy frameworks inside Notion and found the experience was *templates plus a writing assistant*, not *AI that fills the framework*. That's the real distinction between Notion AI and [Framework](/). Both pair templates with AI; they differ in where the AI does its work. Here's the honest comparison.

## At a glance

| | Notion AI | Framework |
|---|---|---|
| What it is | AI writing assistant inside an all-in-one workspace | A library of 100+ strategy frameworks with an AI co-pilot |
| Frameworks | Template pages you fill in yourself | First-class canvases the AI fills for you |
| Where the AI acts | Writes text around your content | Fills the framework's actual cells (2×2, scored table, grid) |
| Default state | A blank template to populate | A complete AI first draft to edit down |
| AI vs. your input | Not distinguished | Every AI-generated item is visually marked |
| Output | A Notion page | A structured canvas + one-page brief (PDF) + Notion export |
| Best at | All-in-one workspace: docs, wikis, databases, PM | Purpose-built, AI-filled framework canvases |
| Scope | Broad — your whole operating system | Deep — strategy frameworks specifically |

## What Notion AI is best for

Notion AI is the better choice when strategy is one room in a much bigger house:

- **An all-in-one workspace.** If your notes, wikis, project trackers, and docs already live in Notion, keeping strategy there too means everything is in one place and searchable.
- **Writing-heavy work.** Notion AI excels at drafting, summarizing, and rewriting the prose *around* your frameworks — meeting notes, project briefs, narrative docs.
- **Team knowledge base.** Databases, relations, and permissions make Notion a strong system of record for a whole team, which a single-purpose tool isn't trying to be.
- **Flexibility.** Notion is programmable and general; you can shape it into almost anything, frameworks included.

What Notion AI does *not* do: it doesn't fill a SWOT 2×2 or a scored RICE table for you as structured output. The framework is a template you maintain, and the AI helps with the words.

## What Framework is best for

Framework is the better choice when you want frameworks themselves to be the product, not a template you build:

- **AI fill as the default.** Describe your situation in a sentence and the AI populates the actual [SWOT](/academy/what-is-a-swot-analysis), [RICE](/academy/rice-prioritization-framework), or [Porter's](/academy/porters-five-forces-beginners-guide) canvas — you start from a complete draft, not a blank table.
- **Purpose-built structure.** Each of the [100+ frameworks](/frameworks) has its own input shape, so a Business Model Canvas looks and behaves like a BMC, not a generic table.
- **No template maintenance.** You don't build, format, or keep the framework templates up to date — they ship correct.
- **Structured, exportable output.** A one-page brief (context, quick wins, the one big bet, what to cut), plus one-click [Notion export](/integrations) so the finished artifact can still live in your Notion workspace.
- **Marked AI vs. yours.** Every AI item is flagged, so the brief is defensible.

What Framework does *not* do: it's not a workspace. It won't hold your wikis, tasks, or team databases — it's opinionated about strategy frameworks alone.

## The honest pick

> **Use Notion AI when strategy is part of an all-in-one workspace you already live in and you mainly want help with the writing. Use Framework when you want frameworks as first-class, AI-filled canvases without building the templates yourself — then export the brief back into Notion.**

Concretely:

- "Everything my team does lives in Notion" → **Notion AI**, with Framework alongside for the framework work.
- "I want the AI to fill the SWOT / RICE / BMC, not just write next to it" → **Framework**.
- "I want the finished brief in my Notion workspace" → **Framework → Notion export**, the best of both.

The cleanest setup for most people isn't either/or: fill the canvas in Framework, keep the record in Notion.

## See also

- [Framework vs ChatGPT for strategy](/vs/chatgpt-for-strategy) — structured canvas vs prose
- [Framework vs Miro](/vs/miro-ai-alternative) — guided AI fill vs a freeform whiteboard
- [Framework vs Strategyzer](/vs/strategyzer-alternative) — 100+ frameworks vs a Lean/BMC-centric tool
- [Integrations & Notion export](/integrations)

> Want AI-filled framework canvases on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — 100+ frameworks, structured output, one-click Notion export, synced everywhere.

## Sources

- [Notion — AI](https://www.notion.so/product/ai)
- [Framework — Pricing](https://frameworklist.com/pricing)

---

### Strategyzer alternative: Framework vs Strategyzer for canvases
URL: https://frameworklist.com/vs/strategyzer-alternative
> Strategyzer is the gold standard for the Business Model & Value Proposition Canvas. Framework is broader and cheaper — 100+ frameworks, AI fill, $9.99/mo. The honest comparison.

Search "[strategyzer alternative](https://www.strategyzer.com/)" and you'll usually find someone who respects the Business Model Canvas but balked at consultant-grade pricing for what is, in the end, two canvases. Strategyzer is the authoritative tool for the BMC and Value Proposition Canvas — built by the people who invented them. [Framework](/) takes a different bet: those same canvases, plus ninety-eight others, with AI fill, at a consumer price. Here's the honest comparison.

## At a glance

| | Strategyzer | Framework |
|---|---|---|
| What it is | The official BMC & Value Proposition Canvas tool | A library of 100+ strategy frameworks with an AI co-pilot |
| Depth | Deep on BMC / VPC methodology | Broad across 100+ frameworks |
| Authority | From BMC/VPC creator Alex Osterwalder | A general framework library |
| AI | Limited | AI fills every canvas from a one-sentence prompt |
| Training & courses | Extensive (books, courses, certification) | Built-in academy guides, no certification |
| Output | BMC / VPC canvases | Any framework's canvas + one-page brief + Notion export |
| Mobile | Web-focused | Web, iPhone, iPad with real-time sync |
| Pricing | Team / enterprise (consultant-grade) | Free · Premium $9.99/mo · Ultra $14.99/mo |
| Best at | Enterprise BMC/VPC programs | Breadth, AI fill, mobile, price |

## What Strategyzer is best for

Strategyzer is the better choice when the Business Model Canvas *is* your methodology:

- **Authority and depth on BMC/VPC.** It's the source-of-truth tool from the framework's creators, with the most rigorous treatment of the canvas you'll find.
- **Methodology and training.** Courses, books, and certification make it a full program, not just software — valuable when you're standardizing a team on the method.
- **Enterprise team facilitation.** Built for organizations running structured strategy programs at scale.
- **Committed BMC/VPC users.** If those two canvases are 90% of your strategy work and you want the deepest tool for them, Strategyzer earns its price.

What Strategyzer does *not* do: it isn't a broad framework library, and AI fill isn't its center of gravity. You're buying depth on a few canvases, not breadth across many.

## What Framework is best for

Framework is the better choice when you use *many* frameworks and want AI to do the filling:

- **Breadth.** [Business Model Canvas](/frameworks/bmc), [Value Proposition Canvas](/frameworks/vpc), and [Lean Canvas](/frameworks/lean) are all here — alongside [SWOT](/academy/what-is-a-swot-analysis), [RICE](/academy/rice-prioritization-framework), [Porter's](/academy/porters-five-forces-beginners-guide), and [100+ more](/frameworks).
- **AI fill as default.** Describe your business in a sentence and the AI populates the canvas; you edit down from a complete draft.
- **Price.** $9.99/month for the whole library and AI assistance, versus consultant-grade pricing for two canvases.
- **Mobile and export.** Web, iPhone, and iPad with real-time sync, a one-page brief export, and one-click [Notion export](/integrations).

What Framework does *not* do: it doesn't offer Strategyzer's certification or the depth of its BMC/VPC methodology program. It's breadth and assistance, not methodology authority.

## The honest pick

> **Use Strategyzer if your team is committed to the Business Model Canvas / Value Proposition Canvas as its core methodology and wants the authoritative tool plus training. Use Framework if you want those canvases among 100+ frameworks, with AI fill and mobile access, at a consumer price.**

Concretely:

- "We're standardizing the org on the Business Model Canvas and want the official program" → **Strategyzer**.
- "I'll use a Lean Canvas, a SWOT, and a RICE this month and want AI to fill them" → **Framework**.
- "I want BMC and VPC without consultant pricing" → **Framework**.

It comes down to depth versus breadth. Strategyzer is the deepest tool for two canvases; Framework is the broadest AI-filled library that includes them.

## See also

- [Framework vs ChatGPT for strategy](/vs/chatgpt-for-strategy) — structured canvas vs prose
- [Framework vs Notion AI](/vs/notion-ai-alternative) — AI-filled canvases vs a general doc assistant
- [Lean Canvas vs Business Model Canvas](/compare/lean-canvas-vs-business-model-canvas) — which canvas to use
- [Pricing](/pricing)

> Want the Business Model Canvas and 100+ frameworks on your phone? [Framework for iPhone & iPad](https://apps.apple.com/app/id6765632580) — AI-filled canvases, one-page briefs, synced everywhere, from $9.99/month.

## Sources

- [Strategyzer](https://www.strategyzer.com/)
- [Framework — Pricing](https://frameworklist.com/pricing)

---

## Playbooks

### Jobs-to-be-Done for healthcare and digital-health products
URL: https://frameworklist.com/playbooks/jtbd-for-healthcare
> How to apply JTBD in healthcare where the buyer is rarely the user, jobs span functional/emotional/social dimensions with stakes higher than other categories, and regulatory context shapes which jobs you're even allowed to solve.

JTBD shines in healthcare because the gap between "what the buyer says they want" and "what the user is actually trying to accomplish" is wider in healthcare than in almost any other category. Personas built from buyer requirements consistently miss what patients, clinicians, and caregivers are really hiring a product to do.

## The healthcare buyer/user split

Healthcare almost always has multiple distinct "job hirers":

- **Patient**: the end recipient of care. Job is usually a mix of clinical outcome ("manage diabetes") and lived experience ("not feel like a sick person").
- **Caregiver**: family member or paid support staff. Job is usually about reducing their own burden while supporting the patient.
- **Clinician**: the provider delivering care. Job is delivering good care efficiently within constrained time, plus protecting their license and avoiding burnout.
- **Institutional buyer**: health system, payer, or employer purchasing the product. Job is managing cost, quality outcomes, and risk.

A product that serves only the institutional buyer's job is bought but not used. A product that serves only the patient's job is loved but not bought. Effective healthcare products serve at least two of these jobs simultaneously and don't conflict with the others.

## Writing JTBD statements for healthcare

The standard JTBD template — *When [situation], I want to [motivation], so I can [expected outcome]* — works in healthcare with sharpened inputs:

- **Situation**: specific clinical or life moment (a new diagnosis, a flare-up, a discharge transition, a routine follow-up)
- **Motivation**: explicit and honest (often emotional or social, not just functional)
- **Outcome**: measurable in either clinical terms ("A1C below 7") or experience terms ("feel confident I can manage a flare without going to the ER")

Examples that actually drive product decisions:

- *"When my insulin pump alerts me and I'm in a meeting at work, I want to silence and respond to it discreetly, so I can manage my condition without my coworkers noticing."*
- *"When I'm caring for my elderly parent who just came home from the hospital, I want a clear daily checklist of what to do and what to watch for, so I can keep them safe without calling the doctor for every question."*
- *"When I'm a primary care physician with 15-minute appointments, I want a 30-second summary of a new patient's recent history before I walk in, so I can be present in the room instead of scrolling notes."*

These statements look different from "patients with diabetes" or "PCPs aged 35–55" personas — and they drive sharper product decisions.

## Functional, emotional, and social jobs in healthcare

Christensen's job dimensions matter especially in healthcare because emotional and social jobs often dominate clinical jobs in determining whether a product gets adopted:

- **Functional job**: "manage my chronic condition"
- **Emotional job**: "feel competent and in control"
- **Social job**: "look like a healthy person, not a sick person, to my family and coworkers"

A diabetes management product that solves only the functional job (great glucose tracking) but ignores the emotional job (the patient feels constantly reminded they're sick) under-performs even when clinically effective. CGM products that succeed treat the social dimension explicitly — discreet wearables, less-medical UI, language that doesn't pathologize.

## The regulatory overlay

Healthcare regulation determines what your product is allowed to claim and how. Map each candidate job to its regulatory framing before committing to specs:

- "Diagnose" → FDA regulated as a medical device
- "Help decide whether to seek care" → allowed without medical-device classification (with careful claims)
- "Treat" → FDA regulated; clinical trials usually required
- "Support a treatment plan" → less regulated; depends on integration
- "Provide information about a condition" → low regulatory bar; consumer health framing

The JTBD statement and the regulatory framing have to match. A statement that promises diagnosis is a statement that requires FDA clearance. The framework is not just a product tool — it's a go-to-market gate.

## How to do JTBD discovery in healthcare

Standard JTBD discovery requires interviews. In healthcare, interview design needs extra care:

- **Recruit from real "trigger moments"** — patients within 30 days of diagnosis, caregivers within 30 days of a hospital discharge, clinicians fresh off a clinic session
- **Avoid leading clinical framings** — ask about the situation and what they tried, not about their diagnosis or treatment plan
- **Listen for emotional/social cues** — what they felt, what they hid from others, what they wished they could do without being noticed
- **IRB / compliance**: if interviewing patients about specific conditions, work with research ethics review depending on jurisdiction

Aim for 30+ interviews per job hypothesis before committing to product direction.

## When JTBD isn't the right tool

For pure operational improvements inside a health system (RCM, scheduling, staffing), use process analysis rather than JTBD. For clinical efficacy questions (does this treatment work?), use RCT methodology. JTBD is the right tool when the question is "what should this product do for users in this category?" — and in healthcare, that question has more layers than a generic SaaS JTBD would suggest.

## Related

- [JTBD framework](/frameworks/jtbd) — the full framework page
- [JTBD explained](/academy/jobs-to-be-done-framework-explained) — long-form guide
- [JTBD vs Personas](/compare/jtbd-vs-personas) — when to use each
- [SWOT for healthcare](/playbooks/swot-for-healthcare) — companion strategy analysis

---

### Premortem for a SaaS product launch
URL: https://frameworklist.com/playbooks/premortem-for-saas-launch
> A step-by-step premortem playbook for SaaS launches — the risk categories that consistently surface, the cross-functional participants you need in the room, and the trade-offs between launch-blocking and launch-mitigating findings.

A premortem is the cheapest pre-launch risk audit a SaaS team has access to. Done well, it surfaces the 2–4 risks that actually matter — usually at cross-functional interfaces — while filtering out the 20+ generic worries that flood any "what could go wrong" session. The key is running it on a SaaS-specific question set and with the right cross-functional group in the room.

## When to run

The right window for a SaaS launch premortem is **4–6 weeks before launch**. Earlier and the team's imagined-failure scenarios stay abstract; later and the cost of addressing findings tips teams toward rationalizing risks away.

Schedule a 90-minute block. Distribute the launch plan (one-pager + roadmap + GTM brief) 24 hours before so participants arrive with context.

## Who's in the room

The standard SaaS launch premortem participant list:

- **Launch owner** (usually the PM or product lead) — present but not facilitating
- **Engineering lead** — for technical and reliability risks
- **Design lead** — for UX and onboarding risks
- **Customer success lead** — for customer adoption and support risks
- **Sales lead** — for pipeline and pricing communication risks
- **Marketing/GTM lead** — for messaging and audience risks
- **Support lead** — for inbound volume and content readiness risks
- **One executive sponsor** — observer who speaks only at the end

**Facilitator should not be the launch owner.** Use a senior peer from a different team, a chief of staff, or a designated devil's advocate. The launch owner has too much invested in the plan to surface risks honestly.

## The session structure

1. **Frame (10 min)**: facilitator describes the imagined failure. "It's 6 months after launch. The launch failed — the feature didn't drive the metric we promised, customer success is overwhelmed, and sales is asking us to roll it back. What happened?"
2. **Silent writing (15 min)**: each participant individually writes the most likely failure modes. Silent writing is non-negotiable — discussion in this phase causes anchoring and reduces output quality dramatically.
3. **Round-robin sharing (30 min)**: each person shares one risk at a time, no discussion. Facilitator captures verbatim. Continue rounds until people pass.
4. **Cluster and discuss (20 min)**: group similar risks, identify duplicates, name themes.
5. **Categorize and assign (15 min)**: each risk gets categorized as Address-now / Mitigate / Accept, with an owner and a date for follow-up.

The total: 90 minutes. Shorter compresses silent writing; longer admits debate that produces worse output.

## SaaS-specific risk categories that consistently surface

After running premortems on hundreds of SaaS launches, five categories recur:

### 1. Onboarding and activation failures

Users don't reach the value moment fast enough. New feature requires existing users to learn a new flow. Trial users don't activate because the onboarding doesn't surface the new capability. **Defense**: define activation event explicitly, instrument it before launch, set up a dashboard the team will actually watch for the first 30 days.

### 2. Customer-success staffing gaps

Support volume spikes 3–5× in the first two weeks of any meaningful launch. If CS is at capacity going in, the launch *causes* a degradation in CSAT and creates churn risk. **Defense**: forecast inbound volume, add temporary capacity, prepare canned responses for top 5 expected questions.

### 3. Pricing or packaging confusion

Existing customers misinterpret what they're getting — is this an upgrade? A separate purchase? Included in their tier? **Defense**: pricing communication is its own workstream with explicit owner; review the customer-facing pricing page from the perspective of three customer types (new prospect, existing self-serve, existing enterprise) before launch.

### 4. Integration and API breakage

API changes — even backward-compatible ones — break existing customers' workflows in ways the team didn't anticipate. **Defense**: ship API changes behind a version flag, give integration customers 30+ days lead time, communicate explicitly via developer mailing list.

### 5. Sales / CS misalignment

Sales pitches the feature with one frame, CS delivers it with a different frame, customers feel deceived. **Defense**: shared enablement materials, joint Q&A sessions, sales-CS handoff document for every closed deal in the launch quarter.

## After the session

A premortem produces a punch list. The follow-up discipline matters as much as the session:

- Each Address-now risk has an owner, a date, and a clear definition of done — track in the same system as the launch plan
- Each Mitigate risk has an explicit mitigation (monitor, rollback plan, staged rollout) and an owner
- Each Accept risk is documented with the rationale and reviewed at launch + 30 days

The launch lead reviews the punch list weekly until launch. A premortem that produces a list and is never referenced again is a ritual, not a tool.

## When not to do a premortem

Skip premortems for small, reversible launches — a minor feature update for a subset of users doesn't justify 90 cross-functional minutes. Skip them for launches you've already committed to where findings won't change anything; that's a worry session, not a premortem. The right threshold: a launch where 2-week-or-more delay is acceptable if findings warrant, and where executive attention is meaningful if the launch fails.

## Related

- [Premortem framework](/frameworks/premortem) — the full framework page
- [How to run a premortem](/academy/how-to-run-a-premortem) — long-form guide
- [Premortem on a product launch](/examples/premortem-product-launch) — worked example
- [Premortem vs postmortem](/compare/premortem-vs-postmortem) — when to use each

---

### RICE prioritization for agency teams
URL: https://frameworklist.com/playbooks/rice-for-agency
> Adapting RICE to agency contexts where 'Reach' is a portfolio of clients, 'Impact' is utilization or margin, and 'Effort' translates to billable vs. non-billable hours. How to rank internal initiatives and pitches without faking the math.

Agencies have backlogs too. They're not product backlogs — they're queues of internal initiatives like "build a productized brand-audit offering", "implement a project management system upgrade", "raise rate cards by 10% on new contracts", "launch a senior advisory tier", "automate our reporting deliverables with AI". These compete for the same scarce resource: principal attention and senior staff time. RICE — with adapted inputs — produces a defensible ranking across them.

## When RICE works for agencies

RICE is a good fit when:

- You have 8–20 internal initiatives competing for the same scarce capacity
- Items are roughly comparable in scope (not "build a new office" vs. "improve a single email template")
- You want a defensible ranking that survives partner debate

RICE is a poor fit when:

- The decision is fundamentally strategic (entering a new category, acquiring another firm) — use a SWOT or premortem
- Initiatives are deeply non-comparable in time horizon — score within timeframes (annual vs. multi-year) separately
- The agency is in survival mode where one or two decisions dominate the calendar

## Defining Reach for agency initiatives

Three options, used in different contexts:

- **Client-level Reach** = number of client accounts affected (active engagements, retained relationships)
- **Staff-level Reach** = number of staff affected (when the initiative changes how work is delivered)
- **Revenue-weighted Reach** = sum of ARR/contract value affected (when revenue impact is the primary lens)

Pick one definition per scoring round. The most common error is unwittingly mixing definitions: scoring one item by client count, the next by staff count, the next by revenue. The resulting RICE numbers cannot be compared.

## Defining Impact for agency initiatives

Tie Impact to a measurable agency outcome. The four most useful Impact targets:

- **Utilization rate** change in percentage points (e.g., +5 points = a "2" on the RICE scale)
- **Gross margin** change in percentage points
- **Client retention** annualized basis points (1% retention improvement is material)
- **Staff retention** annualized percentage points (turnover reduction)

Map to the 0.25–3 scale based on your agency's typical performance:

- 0.25 = barely measurable
- 0.5 = small but real (e.g., +1 utilization point)
- 1 = solid improvement (e.g., +3 utilization points)
- 2 = material (e.g., +5–7 utilization points or +3 margin points)
- 3 = transformative (e.g., +10+ utilization points or +5+ margin points)

Different agencies need different rubrics. Calibrate against your historical range.

## Defining Confidence

Same 50/80/100% scale as product RICE, with agency-specific evidence types:

- **100%**: you've piloted the change with a subset of clients or staff and have measured the outcome
- **80%**: a peer agency has reported a similar change with a similar outcome, or you have a strong analogy
- **50%**: informed intuition; no direct or analog evidence

Anything under 50% means the initiative needs a pilot or research step before it can be scored honestly.

## Defining Effort

Effort = person-months of senior-staff time required. Distinguish billable-time loss (initiatives that pull senior staff off client work) from non-billable time (initiatives that consume nights/weekends or ops bandwidth). Both count, but for an agency the billable-time loss is the more painful currency — every senior week pulled off client work has direct margin cost. Surface this in the Effort calculation rather than averaging it away.

## The override discipline

For agencies, the most common override is **client-relationship-driven**: a low-RICE initiative that a flagship client has named as critical. Override the ranking when the relationship value is real, but document the override and review whether the pattern is justified.

Also override for **succession capacity**: initiatives that distribute knowledge or expand the bench (mentorship programs, IP documentation) are systematically under-scored by RICE because their Reach and Impact compound slowly. Allocate 20–30% of capacity to these explicitly, separate from the RICE-ranked stack.

## A worked example pattern

Agency leadership team has 12 candidate internal initiatives for the year:

1. Each initiative gets a one-page brief from its sponsor (PM equivalent — usually a partner or practice head)
2. Initial RICE scores drafted async by the ops lead
3. Leadership team review session — 90 minutes focused on disputed scores
4. Final ranking published with rubric, override list, and capacity allocation
5. Quarterly check-in: shipped initiatives compared against original Reach and Impact estimates; calibration adjusted

The pattern matches product RICE — the difference is who's in the room and what evidence counts.

## Related

- [RICE framework](/frameworks/rice) — the full framework page
- [The RICE framework for prioritization](/academy/rice-prioritization-framework) — long-form guide
- [RICE vs ICE](/compare/rice-vs-ice) — when to use each
- [RICE for SaaS product teams](/playbooks/rice-for-saas) — for software-product RICE

---

### RICE prioritization for SaaS product teams
URL: https://frameworklist.com/playbooks/rice-for-saas
> How to score a SaaS backlog with RICE — the inputs that matter (NRR-weighted Reach, expansion vs. retention Impact), the traps that produce false rankings, and the override discipline that keeps RICE useful instead of bureaucratic.

RICE works well for SaaS backlogs when the inputs are defined with SaaS-specific rigor. The most common failure mode isn't the formula; it's how teams populate Reach, Impact, and Confidence without thinking through what those values mean in a multi-product, multi-segment SaaS business.

## When to use RICE in SaaS

RICE shines for **backlog ranking** of 10–30 items with comparable scope — typically a quarterly planning cycle. It's overkill for sub-week tactical decisions and undersized for strategic bets ("should we build a second product?"). The sweet spot is feature-level product decisions where a defensible relative ranking matters more than a precise absolute score.

## Defining Reach in SaaS

Two definitions, used in different contexts:

- **Account-level Reach** = number of customer accounts affected per quarter. Use for retention features, account-management improvements, anything where the value scales with account count.
- **User-level Reach** = number of individual users affected per quarter. Use for engagement features, onboarding improvements, anything where the value scales with active-user count.

For mature SaaS, a third option:

- **ARR-weighted Reach** = sum of ARR of affected accounts. Most defensible for retention features where preventing churn matters disproportionately to high-ARR customers.

**Document which version you're using on each item.** Mixing definitions produces invalid comparisons.

## Defining Impact in SaaS

The standard RICE Impact scale (0.25, 0.5, 1, 2, 3) maps to:

- 0.25 = minimal — small UX polish, edge-case fix
- 0.5 = low — incremental improvement, secondary use case
- 1 = medium — solid improvement to a core flow
- 2 = high — material shift in activation, retention, or expansion behavior
- 3 = massive — category-changing capability, expected to drive NRR shift

In SaaS, **split Impact into retention impact and expansion impact** when the two diverge. A feature that strengthens retention (reduces churn risk) may not drive expansion (upsell to higher tier). For a ranking, sum them with weights tied to your current strategic priorities — if NRR is the company's primary goal, weight expansion 1.5× retention; if churn is the urgent problem, weight retention 2× expansion.

## Defining Confidence

The 50/80/100% scale in SaaS:

- **100%**: you have direct usage data or behavioral evidence from existing customers showing the Reach and Impact estimates
- **80%**: you have a credible analogy (a similar feature you've shipped before) or strong customer signal (multiple unsolicited requests with named ARR)
- **50%**: you have informed intuition but no evidence — the idea is plausible but unverified
- **Under 50%**: the idea isn't ready to score; do a discovery sprint first

The single most-violated rule is honest Confidence. A SaaS team that defaults every item to 80% has effectively turned RICE into a free-form gut-feel ranking with extra math.

## Defining Effort

Effort is person-months across all roles needed to ship — engineering, design, PM, QA, GTM. For SaaS this often includes:

- Backend, frontend, and infra work
- Design discovery and visual polish
- API documentation and migration work for existing integrations
- Sales enablement and customer communication

Rough estimates are fine; precision isn't the point. Internal consistency is — apply the same estimation rigor across all backlog items.

## The Effort trap

Engineering-led teams under-estimate Effort on technical work and over-estimate it on UX work. PM-led teams do the opposite. Calibrate by re-checking the last 5–10 shipped items against their original Effort estimate — if the bias is systematic, adjust the team's estimation defaults. Don't pretend the bias doesn't exist.

## Override discipline

RICE produces a starting ranking, not a verdict. Three legitimate override categories:

- **Strategic alignment**: a lower-scoring item directly advances a quarterly OKR or strategic bet that the score doesn't capture
- **Dependency chains**: a lower-scoring item unblocks a higher-scoring sequel
- **Customer relationship**: a specific high-value account has named the lower-scoring item as a renewal-blocker

Document overrides explicitly. The next quarterly review should audit override patterns — if you override frequently in the same direction, your scoring rubric is mis-calibrated; adjust the rubric, don't keep overriding.

## A worked example pattern

For a typical mid-market SaaS backlog of 15 items in one quarter:

1. PM drafts initial scores async — Reach, Impact (split into retention/expansion), Confidence, Effort
2. Team reviews async — anyone can challenge any input
3. 90-minute session focuses only on disputed inputs (usually Confidence and Impact)
4. Final ranking is published with the rubric and any overrides documented
5. Next quarterly cycle reviews shipped items vs. original scores — calibration check

A team running this loop for 3–4 quarters develops calibrated estimation. A team that scores once and ignores the calibration step never improves.

## Related

- [RICE framework](/frameworks/rice) — the full framework page
- [The RICE framework for prioritization](/academy/rice-prioritization-framework) — long-form guide
- [RICE score calculator with examples](/academy/rice-score-calculator-with-examples) — formula and worked examples
- [RICE vs ICE](/compare/rice-vs-ice) — when to use each
- [RICE on a real SaaS backlog](/examples/rice-saas-q3-backlog) — worked example

---

### SWOT analysis for agencies and consultancies
URL: https://frameworklist.com/playbooks/swot-for-agency
> A SWOT tuned to agency businesses — utilization rates, client concentration, talent acquisition, and the AI-substitution dynamics that have reshaped agency economics since 2023.

Agency SWOTs fail when they read like product-company SWOTs. Agencies are people businesses with utilization economics, talent leverage, and client concentration as the primary drivers — not product features or recurring revenue mechanics. A SWOT tuned to those drivers exposes what's actually load-bearing.

> **Need to actually run a SWOT?** [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-playbook) is the dedicated AI SWOT tool — free, no signup. This playbook tunes the *inputs*; SWOTPal runs the analysis.

## The position to analyze

Define the scope: which service line, which client segment, which geography. "Our agency strategy" is too broad. "Our brand-strategy practice serving DTC consumer brands from $5M–$50M ARR, heading into 2026" is sharp. Multi-service agencies should run separate SWOTs per practice and then a roll-up — different practices have wildly different economics and competitive dynamics.

## Strengths — what to probe

Defensible agency Strengths usually look like:

- **Utilization** at 65–75% blended (target varies; below 60% signals demand or staffing problem)
- **Gross margin** above 50% on delivery, with senior-junior staffing leverage that's sustainable
- **Repeat client revenue** as % of total — over 60% signals strong retention; under 40% signals constant pipeline pressure
- **Named expertise** — recognized partners, frequent speaker spots, published thought leadership
- **Client logo concentration in a defensible niche** — DTC beauty, B2B SaaS Series A–C, fintech regulation, etc.
- **Talent retention** — senior staff tenure above 3 years average
- **IP/methodology assets** — proprietary frameworks, named research, templates that reduce delivery time
- **Brand among target clients** — measurable through inbound % of pipeline

Soft Strengths ("creative team", "great culture") need to point to a measurable signal — retention, NPS from staff, win rate on referrals.

## Weaknesses — usually understated

- **Client concentration** — top 3 clients above 40% of revenue, top 10 above 75%
- **Utilization below 60%** — bench cost burning margin
- **Founder/partner dependency** — over 50% of pipeline comes from one or two named partners
- **Pricing model issues** — time-and-materials when clients want fixed-price; project-based when retainers would be more durable
- **Service line decay** — declining demand for services tied to fading platforms or methods
- **Bench skills gap** — can't staff the next-gen work (AI, data, modern marketing stacks) without senior-only delivery
- **Cash flow** — over 60 days AR outstanding signals collections or contract issues that compound

## Opportunities — durable categories in 2026

- **AI-augmented delivery** — productize a repeatable service that AI lets you deliver at higher margin
- **Subscription/retainer conversion** — moving project-based clients to retainers smooths revenue and improves utilization
- **Productization** — taking a repeatable engagement and turning it into a fixed-scope, fixed-price offering with documented playbook
- **Specialty depth** — narrowing focus to a single category and dominating it (e.g., "the agency for DTC pet brands")
- **Partner channel** — referral relationships with SaaS vendors, VCs, or other professional services firms
- **Senior advisory tier** — pricing senior-only strategic engagements at premium rates separate from delivery work
- **Adjacent geographies** — expanding to lower-cost talent markets while maintaining client-facing senior team in-market

Each Opportunity should name: capacity required, the pipeline rebuild needed, and 12-month revenue target.

## Threats — the agency-specific list

- **AI in-housing** — clients moving previously-outsourced work in-house with AI; name the specific services exposed
- **Procurement-led commoditization** — client procurement teams treating creative/strategy work as commodity hours
- **Senior talent flight** — best people leaving for client-side or AI-native startups
- **Macro client budget cuts** — agency spend is one of the first cuts in any client downturn
- **Platform / methodology obsolescence** — services tied to a single platform (Meta-only paid, Klaviyo-only email) are exposed when that platform changes
- **Founder-led pipeline risk** — if the founder/partner stops bringing in deals, what happens to the next 12 months?

## Turning the SWOT into decisions

The two most useful cross-references for agencies:

- **Weaknesses × Threats**: which Weakness magnifies which Threat? Bench skills gap × AI in-housing is a higher-priority fix than either alone. Client concentration × macro budget cuts is the canonical agency failure mode and warrants either a diversification plan or an explicit "we accept this risk for these reasons" decision.
- **Strengths × Opportunities × Capacity**: which Strength supports which Opportunity, and do you have the bench capacity to deliver? Opportunities that require hiring you can't execute in 6 months are deferred regardless of attractiveness.

The deliverable: 2–3 specific decisions. A service line to invest in or sunset, a client to fire or expand, a hiring plan to start, a pricing model change.

## When SWOT isn't the right tool

For account-level decisions, use a portfolio review (not a SWOT). For positioning and category choice, pair SWOT with positioning work (April Dunford's [Obviously Awesome](/glossary/positioning)). For M&A or partnership decisions, use a separate diligence framework. SWOT is the right tool for medium-stakes strategic moves: practice investment, geographic expansion, pricing model shifts, talent strategy.

## Related

- [SWOT framework](/frameworks/swot) — full framework page
- [What is a SWOT analysis?](/academy/what-is-a-swot-analysis) — beginner's guide
- [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) — for analyzing the agency category structurally

---

### SWOT analysis for e-commerce businesses
URL: https://frameworklist.com/playbooks/swot-for-ecommerce
> A SWOT tuned to e-commerce dynamics — unit economics on a per-SKU basis, paid-channel concentration, supply-chain exposure, and the platform Threats that decide whether a brand sustains its margins.

An e-commerce SWOT looks different from a SaaS or healthcare SWOT because the load-bearing inputs are different. Unit economics happen at the SKU level, distribution is dominated by paid channels with their own algorithm risk, and supply-chain exposure can swing margin by 5–10 points in a single quarter. The four cells stay the same; the inputs that go into each cell are e-commerce-specific.

> **Need to actually run a SWOT?** [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-playbook) is the dedicated AI SWOT tool — free, no signup. This playbook tunes the *inputs*; SWOTPal runs the analysis.

## The position to analyze

Define scope precisely. For a multi-brand house, run separate SWOTs per brand. For a single brand, anchor on a specific category position: "Mid-tier skincare brand in DTC + Amazon channels, US market, heading into Q4 2026" is the right level of specificity. "The brand's strategy" is too broad to produce sharp entries.

## Strengths — measurable, not aspirational

Defensible e-commerce Strengths almost always come back to one of:

- **Contribution margin per order** above category benchmark after returns and fulfillment
- **Repeat purchase rate** — 30%+ at 90 days is healthy for most categories
- **Organic acquisition share** — over 25% of new customers from organic search, social, or referral
- **Brand equity** — measurable through unaided recall, branded search volume trend
- **Proprietary product** — formulation, IP, or sourcing that competitors can't replicate
- **First-party data** — email/SMS list size and engagement rate

Soft Strengths ("strong brand", "loyal customers") need to point to a measurable signal — repeat rate, NPS, branded search volume — or they're aspirations dressed as Strengths.

## Weaknesses — the unit-economics view

E-commerce Weaknesses are usually visible in the P&L if you look honestly:

- **CAC payback over 9 months** — signals over-reliance on paid channels at unsustainable cost
- **Contribution margin under 20%** after all variable costs (COGS, shipping, returns, packaging, payment processing)
- **Return rate above category benchmark** — apparel benchmarks differ from beauty, but both signal product or sizing issues
- **Inventory exposure** — months of cover above 6 in non-seasonal categories signals capital trapped
- **Customer concentration** in a single SKU or category — fragile to category trend reversal
- **Channel concentration** — >50% revenue from one channel (Amazon, Meta-driven DTC, wholesale) is a strategic vulnerability

Most e-commerce founders underestimate fulfillment and return costs. Always run the numbers through full contribution margin, not gross margin.

## Opportunities — channel and category

E-commerce Opportunities tend to cluster around channel mix and category expansion:

- **Marketplace expansion** — adding TikTok Shop, Amazon, or international marketplaces that fit the brand
- **Owned-channel buildout** — increasing email/SMS contribution to revenue (target 25–35% for mature DTC)
- **Subscription introduction** — for consumables, can lift LTV by 2–3× when fit is genuine
- **Wholesale or retail expansion** — for brands with proven DTC unit economics, retail can add discovery without cannibalizing
- **Bundle and AOV expansion** — repackaging existing SKUs to lift contribution per order
- **International** — typically where DTC brands hit a wall on logistics and tax; only an Opportunity if you can name the operations plan

For each, name what would need to be true in 6–12 months to capture it. A trend isn't an Opportunity until it has an associated next step.

## Threats — the e-commerce-specific list

- **Paid-channel concentration risk** — Meta CPM inflation, Google algorithm changes, Apple iOS privacy shifts
- **Marketplace policy changes** — Amazon brand registry suspensions, Etsy fee restructures, TikTok Shop policy shifts
- **Tariff and trade exposure** — Section 301 tariffs on Chinese imports, post-de minimis exemption changes
- **Freight and fulfillment cost volatility** — ocean freight, last-mile carrier rate increases
- **Category disruption from AI** — AI-generated content displacing organic discovery, AI search displacing Google product search
- **Macro consumer spending shifts** — discretionary categories hit first in any downturn

Each Threat pairs with either a hedge (channel diversification, sourcing diversification) or an explicit decision to accept the risk.

## Turning the SWOT into decisions

The most useful e-commerce SWOT cross-references are:

- **Strengths × Opportunities**: which Strength most directly supports which Opportunity? If proprietary formulation is a Strength and international expansion is an Opportunity, that's an alignment worth pursuing.
- **Weaknesses × Threats**: which Weakness most magnifies which Threat? Channel concentration Weakness × algorithm-change Threat is a higher-priority fix than either alone.

An e-commerce SWOT should end with 2–3 specific decisions: a channel to invest in or divest from, a SKU line to cut or double down on, a fulfillment partner to renegotiate, a creative or paid budget shift. The four-cell grid is the starting point; the decisions are the output.

## When SWOT isn't enough

For paid-channel optimization, use channel-specific analysis (ROAS, MER, blended payback) rather than a SWOT. For category entry, pair the SWOT with a TAM/SAM/SOM sizing. For M&A or acquisition decisions, use a separate diligence framework. SWOT is the right tool for medium-stakes strategic moves: positioning shifts, channel mix changes, product line bets.

## Related

- [SWOT framework](/frameworks/swot) — full framework page
- [What is a SWOT analysis?](/academy/what-is-a-swot-analysis) — beginner's guide
- [Unit Economics](/glossary/unit-economics) — the math that underlies most e-commerce SWOT entries
- [CAC](/glossary/cac) — the metric most often misjudged in e-commerce strategy

---

### SWOT analysis for EdTech companies
URL: https://frameworklist.com/playbooks/swot-for-edtech
> A SWOT tuned to EdTech — distinct buyer/user dynamics, district procurement cycles, learning-outcome credibility, and the AI-substitution Threat that has reshaped the category since 2023.

EdTech SWOT analyses fail in predictable ways: they ignore the buyer/user split, list "personalized learning" as a vague Strength, treat "AI" as a generic Threat without naming which specific jobs are exposed, and underweight the procurement-cycle reality that determines whether even a great product gets adopted. A useful EdTech SWOT puts those four dynamics front and center.

> **Need to actually run a SWOT?** [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-playbook) is the dedicated AI SWOT tool — free, no signup. This playbook tunes the *inputs*; SWOTPal runs the analysis.

## The position to analyze

Scope precisely. EdTech is split into distinct sub-categories that need separate analyses:

- **K-12** (district sales) vs. **higher-ed** (university procurement) vs. **DTC** (parents or learners) vs. **corporate L&D**
- **Tutoring/learning** vs. **teacher productivity** vs. **administrative/operational** vs. **credentialing/assessment**

"Acme's EdTech strategy" is too broad. "Acme's K-12 math curriculum platform sold to US public school districts, heading into 2026 budget cycles" is sharp enough.

## Strengths — what matters in EdTech

Defensible EdTech Strengths usually look like:

- **Learning outcome evidence** — RCT data, third-party efficacy studies, or strong before/after assessment data
- **Curriculum alignment** — Common Core, NGSS, state-by-state standards mapping
- **Compliance posture** — SOC 2 Type II, FERPA, COPPA, state-specific (e.g., NY Education Law 2-d, California SOPIPA) compliance
- **Teacher adoption signals** — usage data from teachers, not just enrollment numbers; teacher NPS
- **District retention** — multi-year contract renewal rate, expansion within districts
- **Outcomes per dollar** — increasingly the procurement criterion as district budgets tighten
- **Defensible distribution** — district sales relationships, channel partners (CoSN, ISTE presence), or word-of-mouth among teachers

Vanity metrics (downloads, signups) without active-usage data are Weaknesses dressed as Strengths.

## Weaknesses — common blind spots

- **AI-exposed core feature** — if the main job your product does is now doable in ChatGPT, that's a Weakness even if revenue is currently strong
- **Single-product, single-grade-level concentration** — vulnerability when standards or budget priorities shift
- **Procurement cycle mismatch** — high CAC payback because sales cycle is 12+ months while contracts are annual
- **Teacher workflow friction** — products that require extra steps from teachers consistently fail to retain regardless of student engagement
- **Outcome evidence gaps** — anecdotes instead of measurable outcomes; districts increasingly screen this out
- **Pricing model misalignment** — per-student per-year pricing in a per-license-per-school district preference

## Opportunities — the durable ones in 2026

- **Teacher productivity** — AI-assisted lesson planning, grading, and differentiation; budgets are growing and procurement friction is lower than student-facing tools
- **Skills-based credentialing** — employers shifting away from degree requirements; verifiable skills credentials have growing market
- **Tutoring/intervention** — federal ESSER funding largely sunset by 2024, but state and district intervention budgets continue
- **High-stakes assessment alternatives** — AI is forcing rethinking of testing; products with assessment integrity have advantage
- **International expansion** — many EdTech categories have less competition outside US/UK markets
- **Bundle into LMS or SIS platforms** — partnerships with Canvas, Schoology, PowerSchool, etc., reduce distribution cost

Each Opportunity should name the procurement path and timeline to capture.

## Threats — the post-2023 reality

- **AI substitution** — name specific exposed jobs (tutoring, essay feedback, language drills); generic "AI threat" isn't actionable
- **Budget pressure** — district budgets shrinking after ESSER expiration; higher-ed enrollment cliff (US 18-year-old population peaks 2025-ish then declines)
- **Privacy regulation expansion** — new state laws, FTC enforcement, COPPA tightening
- **Vendor consolidation** — district preference for fewer vendors; risk of being the cut category
- **Public sentiment shifts** — screen-time backlash, AI-in-classroom debates affecting parent and district appetite

## Turning the SWOT into decisions

The most useful EdTech cross-reference is **Strengths × Opportunities × Procurement Cycle**: which Strength can capture which Opportunity within one procurement cycle? Opportunities that require multiple procurement cycles to reach material revenue are deprioritized regardless of size.

The second-most-useful: **Weaknesses × AI Threat**. Which Weaknesses are amplified by AI substitution? Products with AI-exposed jobs and weak outcome evidence are in the danger zone — that's where defensive moves (outcome-data investment, repositioning around teacher workflow, building assessment integrity moats) are urgent.

## When SWOT isn't the right tool

For product feature decisions, use [JTBD analysis](/academy/jobs-to-be-done-framework-explained) to understand which jobs students vs. teachers vs. districts hire your product for. For category disruption analysis, use Porter's Five Forces — many EdTech categories are structurally bad businesses (high churn, low willingness to pay, long sales cycles) regardless of product quality. SWOT is the right tool for positioning, channel mix, and product-line investment decisions.

## Related

- [SWOT framework](/frameworks/swot) — full framework page
- [JTBD framework](/frameworks/jtbd) — to separate teacher, student, and district jobs
- [What is a SWOT analysis?](/academy/what-is-a-swot-analysis) — beginner's guide
- [Porter's Five Forces](/academy/porters-five-forces-beginners-guide) — for category-level analysis

---

### SWOT analysis for healthcare organizations
URL: https://frameworklist.com/playbooks/swot-for-healthcare
> How to run a SWOT analysis tuned to healthcare — regulatory exposure, payer mix, clinical staffing, and the compliance constraints that change which Opportunities are actually capturable.

Healthcare SWOT analyses fail in predictable ways: regulatory constraints get listed as a generic Threat without naming the specific rule that bites, payer mix is treated as a back-office concern instead of a strategic variable, and clinical staffing is assumed to be solvable with budget when it's actually a structural ceiling. The cells of a healthcare-tuned SWOT look different from a SaaS or retail SWOT because the load-bearing inputs are different.

> **Need to actually run a SWOT?** [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-playbook) is the dedicated AI SWOT tool — free, no signup. This playbook tunes the *inputs*; SWOTPal runs the analysis.

## The position to analyze

Define the analysis target precisely: which service line, which payer segment, which geography. "A primary care group's strategy" is too broad; "an independent multi-site primary care group's commercial payer strategy in metro Atlanta heading into 2026 contract renewals" is the right scope. Healthcare strategy is dominated by local-market dynamics — state regulation, regional payer concentration, local labor supply — so geographic specificity matters more than in other industries.

## Strengths — what to probe

For a healthcare organization or digital-health company, defensible Strengths usually look like:

- **Clinical quality metrics**: risk-adjusted mortality, HCAHPS scores, readmission rates within or above peer benchmarks
- **Payer contract leverage**: in-network with all major payers in your geography at favorable rates
- **Clinical talent**: retention of senior physicians or nurses above market, named clinical leaders with academic credentials
- **Compliance posture**: clean HIPAA history, completed SOC 2 Type II, FDA clearances if applicable
- **Local market position**: top 1–2 share for the service line in the geography
- **Data assets**: longitudinal patient or claims data that's hard to recreate

Soft Strengths ("great culture", "patient-first") may be true but won't appear in a defensible analysis unless backed by retention, NPS, or HCAHPS data.

## Weaknesses — usually understated

Healthcare leaders frequently understate three classes of Weakness:

- **Payer mix concentration** — over 30% of revenue from any single payer, or over 40% from Medicaid in a non-FQHC, signals revenue fragility
- **Clinical staffing exposure** — vacancy rates above peer benchmarks, age curve of senior physicians (succession risk), reliance on locums above 10%
- **Technology debt** — EHR or RCM systems older than 7 years, manual handoffs in revenue cycle, missing interoperability hooks
- **Regulatory near-misses** — recent corrective action plans, CMS enforcement actions, near-miss compliance incidents
- **Capacity utilization** — chronically below 60% or chronically above 90% both indicate underlying problems

A Weakness that lacks a named metric isn't a Weakness — it's a worry. Force each item to point to a measurable signal.

## Opportunities — the regulatory feasibility test

Healthcare Opportunities die more often from regulatory infeasibility than from market demand. For every Opportunity, name:

- The specific regulatory pathway (FDA 510(k), state licensure, payer contracting, CMS waiver)
- The estimated timeline to clear that pathway
- The capital required

Common real Opportunities in 2026:

- **Value-based care contract participation** — capacity to manage MSSP, ACO REACH, or commercial bundled contracts
- **Behavioral health integration** — high unmet demand and improving reimbursement
- **Hybrid care delivery** — telehealth-friendly state regulations that opened post-2020 and are largely staying
- **AI-assisted diagnostics or documentation** — only credible if FDA pathway is named or not required
- **Specialty pharmacy buildout** — high-margin but capital-intensive, with payer contracting complexity

For each, the discipline is naming what would have to be true in 12 months for capture — not just listing the trend.

## Threats — the ones healthcare boards routinely miss

- **Reimbursement compression** — CMS Physician Fee Schedule cuts, commercial payer Medicare-rate ratcheting
- **Staffing market tightening** — competing health systems hiring senior clinicians in your market at premiums
- **Vertical integration of payers and primary care** — Optum, CVS Health, Amazon One Medical are increasingly competing in primary care delivery
- **New entrants from outside healthcare** — tech-enabled care startups with VC capital and lower cost structures
- **Cybersecurity events** — ransomware in health systems has become an existential operational risk, not just an IT problem

Each Threat should pair with either a defensive move or an explicit decision to accept the risk and explain why.

## Turning the SWOT into decisions

A healthcare SWOT earns its session only if it converges on 2–3 specific decisions: a contract to renegotiate, a service line to invest in or exit, a regulatory pathway to start, a hiring priority, a technology project to prioritize. SWOTs that produce a four-cell PowerPoint slide and no decisions are common and worthless.

The most useful cross-reference is **Weaknesses × Threats**: which Weakness most magnifies which Threat? A staffing shortage Weakness combined with a reimbursement-compression Threat is more urgent than either alone. That intersection is usually where the next quarter's executive attention should go.

## When SWOT isn't the right tool

For payer contract negotiations, use a focused contract analysis, not a SWOT. For service-line investment decisions, pair the SWOT with a financial pro forma — payer-mix-adjusted, capacity-adjusted — because SWOT alone won't surface the margin sensitivities. For M&A targets, use a separate due diligence framework that's heavier on financial, clinical-quality, and regulatory diligence.

## Related

- [SWOT framework](/frameworks/swot) — full framework page
- [What is a SWOT analysis?](/academy/what-is-a-swot-analysis) — beginner's guide
- [Porter's Five Forces](/frameworks/fiveforces) — companion analysis for industry-level questions
- [SWOT vs PESTLE](/compare/swot-vs-pestle) — when each is the better tool

---

### SWOT analysis for SaaS companies
URL: https://frameworklist.com/playbooks/swot-for-saas
> How to run a SWOT analysis tuned to SaaS dynamics — multi-product expansion, retention economics, platform risk, and AI disruption — with sharper input prompts and the entries that actually predict outcomes.

A SWOT analysis tuned to SaaS economics gets sharper when the prompts inside each cell reflect what actually drives SaaS outcomes: retention, expansion, platform risk, and the specific cost structure of recurring revenue businesses. The generic 4-quadrant grid is intact; the questions you ask inside each quadrant are what changes.

> **Need to actually run a SWOT?** [SWOTPal](https://swotpal.com?utm_source=framework&utm_medium=referral&utm_campaign=swot-playbook) is the dedicated AI SWOT tool — free, no signup. This playbook tunes the *inputs*; SWOTPal runs the analysis.

## The position to analyze

For a SaaS SWOT, define the position precisely: which product (or product line), which customer segment, which geography. "Acme's strategic position" is too broad; "Acme's mid-market North America offering heading into Q3 2026" is the right scope. Vague scope produces vague entries and a SWOT that can't drive decisions.

## Strengths — what to probe

A SaaS Strength must support both *acquisition* and *expansion*. The entries that actually predict outcomes are usually:

- **Net Revenue Retention (NRR)** above 110% — best-in-class for mid-market, signals strong expansion mechanics
- **Unit economics** — payback period under 18 months, LTV/CAC above 3
- **Defensible distribution** — organic search dominance, integration ecosystem, partner channel
- **Product velocity** — release cadence and customer-led roadmap evidence
- **Brand equity within an ICP segment** — measurable through unaided recall surveys or branded search volume

Avoid soft Strengths ("great team", "passionate founders"). They may be true and won't appear in any defensible analysis.

## Weaknesses — what's actually load-bearing

The Weaknesses that most often go unnamed in SaaS SWOTs:

- **Single-product risk** — over 80% of ARR from one product is fragile if a category leader pivots
- **Onboarding/activation gap** — high signup-to-paid drop-off rates that the team is normalized to
- **Support cost-to-serve** above 15% of gross margin — signals an unscalable product
- **Customer concentration** — top 10 accounts at >40% of ARR
- **Technical debt blocking core roadmap items** — name the specific blockers, not "tech debt" generally

A SaaS team is allergic to listing real Weaknesses because they sound damning. The discipline is treating each Weakness as an addressable item, not a verdict.

## Opportunities — sized and dated

A SaaS Opportunity should be sized in TAM/SAM/SOM terms and dated. Vague Opportunities ("AI is hot") aren't actionable. Sharp ones look like:

- **Mid-market downstream expansion** from enterprise — quantify the SAM and current penetration
- **New geography** — Japan or DACH after EU GDPR readiness already cleared
- **Bundle/cross-sell** to existing accounts that today use only one product line
- **Pricing repositioning** — usage-based or seat-expansion levers not yet pulled
- **AI-native feature** that captures a job currently being done outside your product

For each Opportunity, name what would need to be true for you to capture it in 12 months. If you can't name a concrete next step, the Opportunity is too vague.

## Threats — the SaaS-specific ones

Generic SWOT lists "competitors" as a Threat. A SaaS-tuned SWOT names the *kind* of competitive threat:

- **Category leader expansion** — when the leader adds your feature as a checkbox, can you survive at a lower price?
- **AI substitution** — generative AI can replace a thin layer in 6 months
- **Platform dependency** — if 30%+ of distribution comes from one channel (Salesforce, Shopify, AWS Marketplace), what happens if their terms change?
- **Customer concentration** — what happens if your top 5 customers churn or renegotiate
- **Open-source alternatives** — when the open-source equivalent crosses 80% of feature parity, your differentiation has to be elsewhere

Each Threat should pair with a defensive move — even if the move is "we're not going to address this and here's why".

## Turning the SWOT into decisions

A SaaS SWOT earns its 90 minutes only if it ends with 2–3 concrete decisions. Common patterns:

- **Cross-reference Strengths × Opportunities**: which Strength most directly captures which Opportunity? That's where to over-invest next quarter.
- **Cross-reference Weaknesses × Threats**: which Weakness magnifies which Threat? That's the urgent fix list — if a Weakness is uncoupled from any Threat, it's lower priority.
- **Name the dominant force**: in most SaaS positions, one of the four cells is doing 60%+ of the work. Name it explicitly so the team's attention follows.

The deliverable is not the four-cell grid. The deliverable is the decisions the grid produces.

## When SWOT isn't the right tool for SaaS

For board-level capital allocation decisions, a SWOT is usually insufficient — pair it with a unit-economics deep dive and a Porter's Five Forces on the category. For day-to-day product decisions, SWOT is overkill; use RICE for backlog and a [premortem](/academy/how-to-run-a-premortem) for major launches. SWOT shines for medium-stakes strategic moves: pricing, positioning, geographic expansion, product line bets.

## Related

- [SWOT framework](/frameworks/swot) — full framework page
- [What is a SWOT analysis?](/academy/what-is-a-swot-analysis) — beginner's guide
- [SWOT of Tesla in 2024](/examples/swot-tesla-2024) — worked example
- [SWOT vs PESTLE](/compare/swot-vs-pestle) — when to use each

---

## Decisions

### Pivot or Persevere: A Founder's Decision Framework (2026)
URL: https://frameworklist.com/decisions/pivot-or-persevere
> When growth stalls, founders face the pivot-or-persevere decision. Walk the 3-framework chain — PMF Trifecta, JTBD, Blue Ocean — that resolves it with worked Slack and Quibi cases.

Every founder faces it eventually: growth stalls, the team is tired, the bank balance is shrinking, and a small voice asks whether the product is even the right product. **Pivot or persevere** is the cleanest articulation of the choice, but it's also the most misleading framing. It implies a binary. The actual decision is a three-step process — and most pivots that fail get the steps in the wrong order.

This page walks the chain end-to-end. It's written for founders and early-stage CEOs of teams between seed and Series B, where the runway-to-signal ratio still makes pivoting feasible but the cost of waiting is rising.

## When this decision shows up

The pivot question rarely appears on a single bad day. It accumulates. The four most common triggers:

- **Growth has gone flat for 2-3 consecutive quarters** despite focused execution. New customer acquisition is stable but retention or expansion stops compounding.
- **Sales cycles are getting longer**, not shorter. Each new deal requires more handholding, more discounts, more custom work. The "sales motion" you thought you'd cracked is regressing.
- **Investor feedback gets vaguer**. Term sheets aren't materialising. Existing investors are supportive in 1-on-1s but not introducing you to follow-on capital. Vague support is often a polite signal.
- **The team is asking "what are we even building"** without a clear answer. Founder energy is the leading indicator; if you can't articulate the bet you're making in two sentences, the team can't either.

Any one of these is noise. Two or more together is signal. That's when you walk the chain.

## Your inputs before walking the chain

Pull these numbers before opening any framework. You'll need them for every step:

| Input | What it tells you | How to get it |
|---|---|---|
| Runway in months | The decision window | Cash on hand ÷ monthly net burn |
| Cohort retention curve | Whether the product holds users | Weekly retention by signup cohort, 6+ months out |
| Sean Ellis score | Whether users would miss the product | Survey ≥40 active users with the Very/Somewhat/Not Disappointed question |
| Top 3 referral sources | Whether growth is organic or pushed | New users tagged by acquisition channel |
| Customer interview tally | How many you've actually talked to in the last 60 days | Real count — most founders overestimate this 2-3× |

If any of these inputs is missing, **stop and gather it first**. A pivot decided without these numbers is a guess wearing a suit.

## Step 1 — Apply the PMF Trifecta

Pivoting is expensive — team turnover, lost momentum, capital burn on rebuilding. So first you have to rule out the simpler hypothesis: **persevere harder, because the product is actually fit, you just haven't found the distribution.**

Use the [PMF Trifecta](/glossary/product-market-fit): all three of Sean Ellis ≥ 40%, flat retention curve after 4-8 weeks, and organic share ≥ 25% of new users.

| Trifecta result | Read | Decision implication |
|---|---|---|
| 3 of 3 pass | You have PMF. Growth issue is acquisition, pricing, or positioning. | **Persevere.** The pivot question is the wrong question — go fix distribution. |
| 2 of 3 pass | PMF is partial. One axis is failing. | **Investigate before pivoting.** A partial PMF often resolves with positioning or pricing changes, not a product rebuild. |
| 0–1 of 3 pass | PMF is broken. The product is not yet fit. | **Continue to Step 2.** The pivot is now on the table. |

**Quibi (2020)** failed at the 0-of-3 result and still tried to "persevere" with bigger marketing — the result was a $1.75B teardown 6 months after launch. **[Slack (pre-2013)](https://a16z.com/podcast/a16z-podcast-stewart-butterfield-on-finding-the-real-business/)** read its 0-of-3 result on the original game (Glitch), accepted that PMF was broken, and pivoted to the internal chat tool the team had built for itself. The chat tool passed all 3 within months of launch.

The Trifecta separates "we need to try harder" from "we need to try something different." Most failed pivots happen when teams skip this step and pivot away from a product that was actually fit; most failed perseverance happens when teams refuse to accept a 0-of-3 result.

## Step 2 — Run a Jobs-to-be-Done audit

This is the step most pivots skip, and it's why most pivots fail.

If Step 1 says PMF is broken, the natural founder reflex is to change the *product* — different features, different UX, different pricing. But the product is downstream of the **job** the customer is hiring it to do. Pivoting the product without re-checking the job means rebuilding for the same wrong job and getting the same broken result.

Run a [Jobs-to-be-Done audit](/academy/jobs-to-be-done-framework-explained) on your existing users — not your assumed personas. The [minimum viable version](/glossary/mvp): 5-8 interviews with users who *did* convert and *did* stay, asked the JTBD interview structure ("when did you last hire this? what were you trying to accomplish? what almost stopped you?"). If the personas are what you actually have on hand, [JTBD vs Personas](/compare/jtbd-vs-personas) explains why they won't answer this question.

You're looking for one of four outcomes:

| JTBD audit result | What it means | Pivot direction |
|---|---|---|
| The job your loyal users describe matches your assumed job | You built the right thing; the issue is reach — not enough of the market has this job | **Persevere** with sharper segmentation |
| The job your loyal users describe is *different* from your assumed job | You built the right thing for a job you didn't realise — Slack's case | **Persevere** but reposition to the real job |
| Multiple distinct jobs across users, no dominant pattern | The product serves no one job well — typical for early-stage with broad scope | **Pivot** by narrowing to one job |
| No coherent job emerges from the interviews | The job you thought existed doesn't | **Pivot** — change the customer or the problem |

The dominant pattern: founders discover the *real* job is one they hadn't built for, and the pivot is a repositioning, not a rebuild. **Slack** is the canonical version — the team kept the chat product but pivoted from "make our game team's life easier" (an internal job) to "make any team's communication faster" (the real job their early users were hiring it for).

Note: if you can only do *one* thing from this page, do this step. It is the highest-leverage move and the most-often-skipped.

## Step 3 — Check the competitive ocean

Now you have a real job. You're either persevering against a sharper target or pivoting toward a new one. The last check before committing capital: **is the market itself worth being in?**

Use [Blue Ocean](/frameworks/blueocean) thinking, but in its diagnostic form rather than its generative form. Ask:

1. How many credible incumbents are serving the job you've identified? (More than 5 with >$50M ARR = red ocean.)
2. What is the underserved dimension of the job? (Price, simplicity, speed, integration, support — there's almost always one.)
3. Are there adjacent jobs your current capability could serve where the ocean is bluer?

| Blue Ocean read | Decision implication |
|---|---|
| Red ocean, no underserved dimension you can credibly own | The right pivot is to an adjacent job, not a deeper feature push |
| Red ocean, clear underserved dimension | Persevere but reposition against the dimension — Superhuman did this with speed in email |
| Blue ocean, you can defend it | Persevere; the job is unclaimed and your runway is the constraint |

The trap: many founders pivot from a red ocean to another red ocean because they don't run this check. The blue-ocean view forces you to commit only when there's whitespace.

## Putting the chain together: the 4-step worked example

A real Series A SaaS founder (anonymised here) running through this chain in late 2025:

1. **Trigger**: growth flat 2 quarters, 11 months of runway, founder ambivalent.
2. **Step 1 (Trifecta)**: Sean Ellis 27% (failing 40% bar); retention curve flat after week 4 (passing); organic 12% (failing). Score: 1/3. Result: **PMF broken, continue to Step 2.**
3. **Step 2 (JTBD)**: 6 interviews with loyal customers. Hypothesised job: "help mid-market RevOps automate quote-to-cash." Real job heard repeatedly: "give me one place to see why deals are stalling, so I can talk to the sales lead about it." Different job. Result: **reposition rather than rebuild.**
4. **Step 3 (Blue Ocean)**: 6+ competitors in quote-to-cash automation (red ocean). 2 competitors in "deal-stall diagnosis" (blue ocean). Result: **pivot positioning, keep product 70%, narrow to deal-stall diagnosis.**
5. **Outcome 6 months later**: Sean Ellis 51%, retention now flattening at month 8 (vs. month 4), organic share 28%. Trifecta passing 3/3. Series B raised 11 months after the pivot.

This is the typical pattern: the "pivot" turned out to be a repositioning + narrowing, not a rebuild. They kept the team, the codebase, and most of the customers. What changed was the job they were targeting.

## When to bypass the chain

Three situations where the chain doesn't apply:

- **Founder-market fit is gone**. If you've lost belief in the market itself (not just the product), no framework chain will rescue the situation. Pivot to a new market or wind down.
- **Material technology shift makes the product obsolete**. If GPT-4 made your AI-flashcard startup irrelevant, the chain is irrelevant too — start over.
- **A regulator just outlawed your business model**. PESTEL-level external shocks override product-level analysis. Different decision page (forthcoming).

## Next steps

Whichever way the chain points, the next actions are concrete:

- If the Trifecta passed 3/3 and you're persevering, [open the canvas](/sign-in) to map the distribution problem with Lean Canvas — you've already won the product question.
- If you ran a JTBD audit and discovered a different real job, draft the new positioning with the [JTBD framework page](/academy/jobs-to-be-done-framework-explained) and re-test the Trifecta in 60 days.
- If Step 3 said you're in a red ocean, work the [Blue Ocean entry](/frameworks/blueocean) to find a defensible underserved dimension before committing pivot capital.
- For the founder coaching layer this page can't replicate, our [Framework iOS app](https://apps.apple.com/app/id6765632580) walks you through each framework with AI assistance, save state, and exportable briefs.

Pivot-or-persevere is rarely the right binary. The real question is which of three sub-decisions is actually broken — and the chain above tells you that in 3-5 days of focused work instead of 6 months of regret.

---

## Help center

### Requesting account deletion
URL: https://frameworklist.com/help/account/requesting-account-deletion
> Email support to delete your account and all associated data. Permanent and unrecoverable.

Account deletion isn't surfaced in the app yet — it's a manual request to support.

## How to request

Email <a href="mailto:support@frameworklist.com">support@frameworklist.com</a> from the address tied to your account, with the subject **"Delete my account"**. We'll respond within 2 business days.

To prevent accidental deletion, we'll send one confirmation request before processing. Reply to confirm.

## What gets deleted

When we process the deletion:

- Your auth record (Google / Apple / email link)
- Your profile (display name, avatar)
- All canvases and briefs
- AI interaction history
- Settings and preferences

Within 30 days of the deletion request, all data is purged from production. Backups roll off the same way over the following 30 days.

## What doesn't get deleted

- **Billing records** — kept as long as legally required for tax and accounting (typically 7 years), per Stripe / Apple's terms
- **Aggregate analytics** — already de-identified, retained as-is

## Cancel your subscription first

If you have an active subscription, cancel it *before* requesting deletion to avoid being charged for the next period:

- **Web subscription**: Settings → Subscription → Manage subscription → Cancel
- **iOS subscription**: iPhone Settings → Apple ID → Subscriptions → cancel FrameworkList

See [Canceling your subscription](/help/billing/canceling-your-subscription) for the detailed flow.

## In-app deletion

We're working on a self-serve deletion button in Settings. Until then, the email route is the only path.

---

### Sign-in methods: Google, Apple, and email magic link
URL: https://frameworklist.com/help/account/sign-in-methods
> We support three sign-in methods, all passwordless. Here's how each works.

FrameworkList has no passwords. All sign-in is passwordless, via one of three methods:

## 1. Continue with Google

Click **Continue with Google** on the sign-in page. You'll be redirected to Google's consent screen. After approval, you're signed in and bounced back to the app.

We receive your email, display name, and profile photo URL. Nothing else.

## 2. Continue with Apple

Same flow as Google but routed through Apple. Available on both web and iOS.

On Apple's consent screen you can choose to **share** or **hide** your real email. Hiding gives us a relay address — that's fine; we use whichever is sent.

## 3. Email magic link

Click **Use email instead** on the sign-in page. Type your email and click **Send magic link**. Check your inbox for an email from FrameworkList (from `noreply@frameworklist.com` or similar), open the link, and you'll be signed in automatically.

The link expires after 1 hour. If you wait too long, request a new one.

## Switching methods on the same account

The account is keyed to your **email address**. If you sign in with Google and later use email magic link with the *same* email, you'll land in the same account. Same for Apple.

If your Apple Hide-My-Email relay differs from your Google email, those are treated as *different accounts*. To merge, email <a href="mailto:support@frameworklist.com">support@frameworklist.com</a>.

## Trouble signing in

- **Magic link email never arrives.** Check spam. Wait 1–2 minutes. If still nothing, the email may be misspelled — request again with the correct spelling.
- **Google / Apple OAuth fails.** Usually a browser cookie / popup blocker issue. Try in a fresh browser window with default settings.
- **Signed in but app shows "Loading…" forever.** Refresh the page once. If it persists, sign out and back in.

Still stuck? <a href="mailto:support@frameworklist.com">Email support</a> with the method you tried and the error message you saw.

---

### Updating your profile and avatar
URL: https://frameworklist.com/help/account/updating-your-profile
> Display name and avatar are editable. Email and sign-in method are not — they're tied to your auth provider.

## Display name and avatar

Both editable from **Settings → Profile** (sidebar → Settings).

- **Display name** — what shows up next to your work and in the sidebar. Initially seeded from your Google / Apple profile; change anytime.
- **Avatar** — upload a square image (JPG / PNG). It's compressed automatically and stored in a public Supabase bucket. The link is stable; you can replace the image later, the link stays.

Changes save when you click **Save changes**. They propagate to iOS within a few seconds via the same Supabase backend.

## Email address

Your email is tied to your sign-in provider (Google, Apple, or the email you used for magic-link sign-in). To **change** your email:

- If you signed in with Google: change the email on your Google account, then sign back in.
- If you signed in with Apple: managed via Apple ID settings.
- If you signed in with email magic link: email <a href="mailto:support@frameworklist.com">support@frameworklist.com</a> with both your old and new email — we'll merge the accounts manually.

We don't currently support changing email in-app for magic-link accounts. That's on the roadmap.

## Sign-in method

You can use multiple sign-in methods on the same email — they all land in the same account. To stop using a particular method, simply stop using it. There's no separate "remove provider" step.

## Sign out

A **Sign out** button is at the top of Settings. Signing out clears your session locally; your data stays on the server and reappears when you sign in again.

---

### Canceling your subscription
URL: https://frameworklist.com/help/billing/canceling-your-subscription
> Cancel anytime. You keep access through the end of the period you already paid for.

You can cancel anytime, from the same place you subscribed.

## If you subscribed on the web

1. Open the web app → **Settings → Subscription**
2. Click **Manage subscription** (opens Stripe Customer Portal)
3. Click **Cancel plan**
4. Confirm

Your subscription stays active until the end of the current billing period. You keep all Premium / Ultra features until then. After that, your account drops to Free — your canvases and briefs stay intact, but new AI operations will hit the Free credit limit.

## If you subscribed in the iOS App Store

1. Open **Settings** on your iPhone
2. Tap your name → **Subscriptions**
3. Tap **FrameworkList**
4. Tap **Cancel Subscription**

Same logic: you keep access through the end of the paid period. Apple sends you an email confirmation.

## Refunds

- **Web (Stripe)**: we don't auto-refund partial periods, but if you have unusual circumstances, email <a href="mailto:support@frameworklist.com">support@frameworklist.com</a> within 7 days and we'll review case-by-case.
- **iOS (App Store)**: refund requests go through Apple at [reportaproblem.apple.com](https://reportaproblem.apple.com). We can't issue iOS refunds — Apple controls all billing.

## What happens after cancellation

- Subscription status changes to "expired" once the paid period ends
- AI credits drop to the Free allotment
- Canvases, briefs, profile, and all other data stay intact
- You can resubscribe anytime — picks up cleanly

## If you want to delete your account too

Cancel the subscription *first*, then follow [Requesting account deletion](/help/account/requesting-account-deletion).

---

### Managing your subscription
URL: https://frameworklist.com/help/billing/managing-your-subscription
> Where to upgrade, downgrade, change payment, or cancel — depends on whether you subscribed via web or iOS.

Where you manage your subscription depends on **where you originally subscribed**:

## If you subscribed on the web

- Go to **Settings → Subscription** in the web app
- Click **Manage subscription** — this opens the Stripe Customer Portal
- From the portal you can: change plan, update payment method, view invoices, cancel

The portal is a hosted Stripe page; changes apply within seconds to your FrameworkList account.

## If you subscribed in the iOS App Store

- Open **Settings** on your iPhone
- Tap your name → **Subscriptions**
- Find **FrameworkList** in the list
- From there you can change plan, change payment method, or cancel

Apple handles the entire billing relationship — we don't have access to your credit card. The **Manage subscription** button is hidden in the web app for iOS-billed users because we can't actually manage it for you.

## Switching from one to the other

You can't transfer an iOS subscription to web (or vice versa) directly. To switch:

1. Cancel the current subscription in the place you bought it
2. Wait for the current period to end (you keep access until then)
3. Subscribe again via the new channel

We won't double-charge — web checkout is blocked while an iOS subscription is active.

## Upgrading tiers (Premium → Ultra)

- **On web**: Stripe Portal → Update subscription → pick the new plan. Pro-rated.
- **On iOS**: iPhone Settings → Subscriptions → FrameworkList → change plan. Apple handles proration.

## Need help?

Email <a href="mailto:support@frameworklist.com">support@frameworklist.com</a> with your account email and we'll help you find the right place to make a change.

---

### I subscribed on iOS — can I use the web app?
URL: https://frameworklist.com/help/billing/subscribed-on-ios
> Yes. Same account = same subscription. Here's what to expect.

**Yes.** Your iOS subscription unlocks the web app automatically as long as you sign in with the same account.

## What works

- All AI features (canvas generation, refinement, brief building)
- Your monthly credit allotment
- PDF export on briefs (Premium feature, included)
- All canvases and briefs you've created on iOS

## What's different

- The **Manage subscription** button in web Settings is hidden. You have to manage from your iPhone (Settings → Apple ID → Subscriptions).
- You can't upgrade or downgrade from web. Same: do it on iPhone.
- You can't cancel from web. Same: iPhone Settings → Subscriptions.

## What if I tried to subscribe again on web?

We block it. If the system detects an active iOS subscription on your account, the web checkout returns a polite "Already subscribed via iOS" notice and won't process payment. We never want to double-charge.

## What if my iOS subscription expires or fails?

Once Apple reports the subscription is gone (cancellation, billing issue, refund), your web account drops back to Free within a few minutes. You can then subscribe via web (Stripe) if you want.

## Account matching

The pairing is by **email address**. If you subscribed on iOS using a different email than you sign into web with, the systems can't pair them automatically.

Tell us at <a href="mailto:support@frameworklist.com">support@frameworklist.com</a> and we'll merge the accounts manually. Include both emails plus the Apple receipt if you have it.

---

### Choosing the right framework
URL: https://frameworklist.com/help/getting-started/choosing-the-right-framework
> 100+ frameworks is a lot. Three questions get you to the right one fast.

The library has 100+ frameworks. Picking by browsing is slow. Use this three-question shortcut instead.

## 1. What kind of work is this?

Frameworks live in five buckets:

- **Triage** — sorting what you already have (Eisenhower, MoSCoW, Pareto)
- **Prioritization** — ranking options (RICE, ICE, Weighted decision matrix)
- **Decision** — choosing between alternatives (Pros/Cons, Decision tree, Cost-benefit)
- **Strategy** — figuring out what to be doing (SWOT, Porter's Five Forces, JTBD)
- **Diagnosis** — understanding what's happening (5 Whys, OODA, First principles)

Naming the bucket cuts 80 frameworks from your search.

## 2. How reversible is the decision?

- **Easily reversible** → use a lightweight tool (Pros/Cons, ICE). Don't overthink it.
- **Hard to reverse** → use SWOT or Five Forces, plus a [Premortem](/tools/premortem).
- **Strategically defining** → multi-framework approach: map with SWOT, stress-test with Premortem, decide with a matrix, commit with OKRs.

## 3. Do other people need to see the result?

If yes, prefer frameworks that produce a one-page visual: SWOT, RICE, Eisenhower, Lean Canvas. Skip ones that work in conversation but not on paper.

## Just want a starting point?

Try one of the [free tools](/tools) — no sign-up needed. SWOT for strategy, Eisenhower for triage, Pros/Cons for everyday choices.

If you'd rather have AI suggest the framework that fits your specific situation, [sign up free](/sign-in) and drop your thought into the New Canvas flow — we'll recommend one.

---

### Creating your first canvas
URL: https://frameworklist.com/help/getting-started/creating-your-first-canvas
> A canvas is one framework filled in with your own thinking. Here's the 5-minute path to your first one.

A **canvas** is a single framework (like SWOT or Eisenhower) populated with your actual situation. Each canvas belongs to a "thought" — the decision or question you're working through.

## The flow

1. Click **New** in the sidebar (or open `/app/new`).
2. Type a thought: one or two sentences describing what you're trying to decide or figure out. Example: *"Should we launch pricing changes in Q3 or wait until after the summit?"*
3. Either pick a framework yourself or let the AI suggest one.
4. The canvas opens with empty blocks (e.g., 4 quadrants for SWOT). AI fills in a first pass automatically.
5. Edit, add, or remove items in each block. Your changes save automatically.

## What happens with AI

The first AI pass uses one credit and produces a draft. Refining the canvas with a follow-up instruction ("focus more on the timing risk", "what about the competitor angle") uses another credit. Free accounts get a small starter allowance; [Premium and Ultra](/pricing) come with monthly allotments.

## Tips that matter

- **Keep the scenario sentence sharp.** "Our company needs a new strategy" is too vague to help the AI. "Should we add a self-serve tier alongside the existing sales-led motion?" gets a useful draft.
- **Edit AI output ruthlessly.** The draft is a starting point, not a deliverable. Read each line and ask whether you'd actually say it.
- **Use refine, not regenerate.** Refining preserves the parts that worked. Regenerating throws everything out, which is usually worse.

## Where canvases live

All canvases show up in your **Frameworks** sidebar tab (the library of *your* worked canvases — separate from the catalog of templates at **Library**). They sync across web and iOS.

If you got stuck, email <a href="mailto:support@frameworklist.com">support@frameworklist.com</a>.

---

### What is FrameworkList?
URL: https://frameworklist.com/help/getting-started/what-is-frameworklist
> FrameworkList is a curated library of 100+ thinking frameworks with AI-assisted canvases and strategy briefs, available on web and iOS.

FrameworkList is a tool for thinking more clearly about hard decisions. It bundles three things in one place:

- A **library of 100+ frameworks** — SWOT, OKRs, RICE, Eisenhower, Premortem, Jobs-to-be-Done, Five Forces, and many more, each with a definition, a worked example, and guidance on when it applies.
- **Canvases** that let you fill in any framework with your own thinking. The web app and the iOS app share the same data; whatever you start on one device shows up on the other.
- **AI assistance** that takes a thought and either runs a framework for you or refines what you have written. Premium and Ultra plans include more AI credits.

## How people use it

- **Founders and operators** use it to pressure-test decisions before committing.
- **Product managers** use it to structure briefs, prioritization meetings, and quarterly planning.
- **Consultants and coaches** use it to walk clients through structured exercises.
- **Students** use it to learn the strategy and decision-making frameworks taught in MBA and design programs.

## What it is not

FrameworkList is not a note-taking app, a task manager, or a project tracker. It is purpose-built for the structured-thinking moments inside whatever workflow you already use. People typically open it for 20–60 minutes when a real decision needs working through, then export the result and act.

If you have more questions, the rest of the help center covers specific features. If you want to talk to a human, email [support@frameworklist.com](mailto:support@frameworklist.com).

---

### The iOS app: what's the same, what's different
URL: https://frameworklist.com/help/ios-app/ios-vs-web-differences
> Both apps share an account and a backend, but each has features the other doesn't. Here's the breakdown.

The web app and iOS app share the same account, the same canvases, the same briefs. Anything you create on one shows up on the other in real time. There are a few differences worth knowing.

## What's the same on both

- Your account, profile, and subscription
- All canvases and briefs
- The 100+ framework library
- AI canvas generation, refinement, and brief building
- AI credit pool (one shared counter)

## What's different

- **Subscription origin**: if you subscribed in the iOS App Store, web shows your tier but the **Manage subscription** button is hidden — you have to manage from your iPhone. Conversely, if you subscribed via web (Stripe), you can manage from web but iOS can't change the subscription either.
- **Web checkout is blocked while an iOS subscription is active.** Trying to subscribe via web when you already have an active iOS sub returns a polite "already subscribed via iOS" notice.
- **Free interactive tools** (`/tools/[slug]`) exist only on web. They're meant as a no-sign-up entry point.
- **Blog, Academy, Help center** are web-only.
- **iOS has system widgets and shortcuts** the web app can't offer.

## Switching between them

Sign in with the same Google / Apple / email account on both. Subscription, canvases, briefs, settings, and avatar all sync. Profile changes propagate within seconds.

## Which one should I use?

- **Long thinking sessions, brief writing, sharing with stakeholders** → web (bigger canvas area, easier to share / PDF / copy)
- **Quick captures, on-the-go reading, one-handed reflection** → iOS
- **You'll naturally use both** — the apps are designed as one product across two surfaces

## App Store link

[Download FrameworkList for iOS →](https://apps.apple.com/app/id6765632580). Free to download; the same subscription tiers apply.

---

### How we handle your data
URL: https://frameworklist.com/help/privacy/how-we-handle-your-data
> What we store, where, who can see it, and how to get it deleted. Short version: your canvases are private by default; we don't sell anything to anyone.

The full legal version is in our [Privacy Policy](/privacy). This is the human-readable summary.

## What we store

- **Account basics**: email, display name, avatar URL, sign-in provider
- **Subscription state**: tier, billing origin (Stripe / Apple), period dates — *not* your card number; Stripe and Apple hold those
- **Your work**: every canvas and brief you create, with timestamps
- **AI conversation context**: the prompts you sent and the AI responses, kept to support refinement and brief generation
- **Minimal analytics**: aggregated, de-identified usage (page views, feature usage). No third-party trackers, no marketing pixels.

## What we don't store

- Your payment card details (Stripe / Apple's job)
- Browsing history outside FrameworkList
- Location data beyond what your IP implicitly provides
- Anything from other apps or services

## Who can see your work

- **You** — always
- **Anyone you explicitly share with** — currently only via Copy Link to other signed-in users on your account
- **Our team** — only when investigating a support request you've sent, or under legal compulsion (warrant, subpoena). We don't browse user data for analytics or marketing.
- **AI providers** — when you trigger an AI operation, your scenario + relevant context is sent to our AI provider (Anthropic / Claude). We don't allow that data to be used for model training; the provider agreement covers this.

## Storage location

- **Database**: Supabase (Postgres) — currently in the AWS US region
- **File storage**: Supabase Storage for avatars
- **Backups**: daily, encrypted at rest, 30-day retention

## Getting your data out

We don't have a self-serve export yet. If you need a copy, email <a href="mailto:support@frameworklist.com">support@frameworklist.com</a> and we'll send you a JSON dump of your canvases, briefs, and profile within 7 days.

## Deleting your data

See [Requesting account deletion](/help/account/requesting-account-deletion) for the full flow. Short version: email support, we'll confirm, and within 30 days everything except billing records is purged.

## Marketing emails

We send transactional emails (welcome, billing receipts) and an optional weekly newsletter (opt-in via the [newsletter form](#) in the footer; unsubscribe anytime). We don't sell, rent, or share your email with anyone else.

## Questions

Email <a href="mailto:support@frameworklist.com">support@frameworklist.com</a>. Real human responses within 2 business days.

---

### How AI credits work
URL: https://frameworklist.com/help/web-app/ai-credits-explained
> What a credit is, what consumes one, and how the monthly allotment resets.

FrameworkList uses **credits** to meter AI usage. One credit covers one AI operation.

## What consumes a credit

- **Generating a canvas** from a thought (1 credit)
- **Refining a canvas** with a follow-up instruction (1 credit)
- **Running the brief wizard** (1 credit per wizard run)
- **Regenerating an insight panel** for a canvas (1 credit)

Reading the framework catalog, browsing your library, editing canvases by hand — none of these use credits. Only AI calls do.

## Monthly allotment by plan

- **Free** — a small starter allowance to try things out (typically enough for 3–5 AI operations total)
- **Premium** — 50 credits / month
- **Ultra** — 200 credits / month (4× more, plus access to more flagship AI models for higher-stakes work)

## When credits reset

Credits reset at the start of each billing period. You can see your current usage and the next reset date on the **Settings → Subscription** panel.

## What happens when you run out

The next AI call returns a "you are out of credits this period" message. You have two options:

- **Wait for the reset** (date shown on the settings panel)
- **Upgrade to a higher tier** to get more credits immediately

Unused credits do **not** roll over to the next period.

## Free tools never use credits

The interactive [free tools](/tools) (SWOT, Eisenhower, Pros/Cons, Premortem, 5 Whys) run entirely in your browser without AI. They never consume credits. They also don't sync across devices — that's the trade-off.

## Estimating how many you need

- Power users (PMs running multiple briefs per week): Ultra
- Regular users (1–2 briefs per week + occasional canvas refinement): Premium
- Light users (testing the product, occasional one-off decisions): Free is usually enough

If you're unsure, start on Free and upgrade when you hit the limit. There's no commitment.

---

### Exporting a brief as PDF
URL: https://frameworklist.com/help/web-app/exporting-a-brief-as-pdf
> Every brief has a PDF export. Free tools too. Here's how to use both.

There are two PDF exports in FrameworkList. Both produce a clean A4 layout suitable for sharing.

## Exporting a strategy brief

Briefs are a Premium feature. If you have one generated:

1. Open the brief from the **Briefs** sidebar tab.
2. Click **Download PDF** in the header.
3. The file downloads with the brief headline as the filename.

The PDF includes every section that was generated for the brief (refined thought, options, recommendation, risks, 30/60/90 plan).

## Exporting a free tool worksheet

Each free worksheet on `/tools/[slug]` has its own **Export PDF** button. No sign-in or subscription needed.

1. Fill in the scenario field and one or more block textareas.
2. Click **Export PDF** in the bottom-right of the worksheet.
3. The PDF downloads with the scenario as the filename.

The PDF is laid out as a one-page A4 with the framework name, your scenario, and each block as a labeled card.

## Troubleshooting

- **The button is disabled.** You haven't filled in any content yet (or only have empty bullets). Type something and the button enables.
- **The download fails or hangs.** Usually a browser blocking issue. Allow downloads from the site and try again.
- **Chinese / CJK characters render as boxes.** Should be fixed — we bundle Noto Sans SC. If you still see boxes, email <a href="mailto:support@frameworklist.com">support@frameworklist.com</a> with the brief or worksheet so we can reproduce.

## Sharing the link instead

For canvases and briefs, there's also a **Copy link** option in the article header (web only). The link works for anyone signed into the same account. Briefs are private by default; we don't support public sharing yet.

---

### Generating a strategy brief from a canvas
URL: https://frameworklist.com/help/web-app/generating-a-strategy-brief
> Turn a filled-in canvas into a one-page strategy brief you can share. Premium feature.

A **brief** is a structured one-pager generated from one of your canvases: refined thought, options, recommendation, risks, and a 30/60/90 plan. You can export it as PDF and share it.

## How to generate one

1. Open any canvas with content in it.
2. In the insight panel on the right, click **Build Strategy Brief**.
3. The brief wizard runs a short multi-turn Q&A — it asks clarifying questions about the scenario, your priorities, and any constraints. Answer briefly; the wizard uses your answers to shape the final brief.
4. After the last question, the brief renders. It takes 10–30 seconds depending on length.
5. Edit any section inline. Changes save automatically.

## What goes into a brief

- **Refined thought** — your scenario sharpened into a decision statement
- **Issue tree** — the sub-questions that need to be answered
- **Options** — 2–4 candidate paths with effort / impact / confidence scores
- **Recommendation** — the AI's pick, with reasoning and confidence level
- **Risks** — what could go wrong, with probability × impact
- **30 / 60 / 90 day plan** — concrete tasks per window

Not every brief surfaces every section — the wizard skips ones that don't apply.

## Premium feature

Brief generation is a Premium feature. Free accounts can read the wizard intro but need to upgrade to run it. See [Pricing](/pricing) for tiers.

## Export

Once generated, every brief has an **Export PDF** button in the header. The PDF uses a neutral layout suitable for sharing with stakeholders.

## Where briefs live

Briefs appear in the **Briefs** sidebar tab, sorted by most recent. Each brief is linked back to the canvas it came from.

---

### Searching and organizing your library
URL: https://frameworklist.com/help/web-app/searching-and-organizing-the-library
> Finding past canvases and briefs as your library grows.

Two pages list your saved work:

- **Frameworks** (sidebar tab) — every canvas you've created
- **Briefs** (sidebar tab) — every strategy brief you've generated

Both support search and sorting.

## Search

A search bar at the top of each list filters by:

- Scenario text (the sentence you wrote at the top of the canvas)
- Framework name (e.g. typing "swot" filters to SWOT canvases)
- Headline text (for briefs)

Search runs client-side — it's instant and works offline.

## Sorting

By default, lists are sorted **most recently updated first**. Switch to alphabetical with the sort control next to the search bar.

## Renaming and deleting

Every canvas and brief has a kebab menu (⋯) in its header with **Rename** and **Delete** options. Renaming changes only the scenario text — the underlying canvas/brief id stays stable so links keep working.

Deleting is permanent — there's no trash bin. We'll prompt you to confirm.

## Cross-device sync

Lists are synced from the same Supabase backend that the iOS app uses. Anything you create on iPhone shows up here in real time, and vice versa.

If you don't see something you created on iOS, refresh the page — occasionally the SWR cache lags.

## Bulk operations

Not supported yet. If you want to delete a batch of old canvases, do it one at a time. We'll add multi-select when enough users ask for it.

---

## Glossary

### Activation
URL: https://frameworklist.com/glossary/activation

The point a new user has experienced enough of the product's core value that they're likely to return — usually defined by a specific in-product behavior.

---

### Aha Moment
URL: https://frameworklist.com/glossary/aha-moment

The specific point in a new user's experience when they first understand why the product matters to them — when intent converts to belief. Identifying and accelerating users to the Aha Moment is the core of activation-stage product work.

---

### ARR / MRR (Annual / Monthly Recurring Revenue)
URL: https://frameworklist.com/glossary/arr-mrr

Annual Recurring Revenue is the normalized yearly value of all active subscriptions; MRR is the same figure expressed monthly. Together they are the headline revenue metrics for any subscription business.

---

### Blue Ocean
URL: https://frameworklist.com/glossary/blue-ocean

A market space where competition is irrelevant because the offering is uncontested — created by either redefining an industry's value proposition or by entering an entirely new market segment.

---

### Burn Rate
URL: https://frameworklist.com/glossary/burn-rate

The amount of cash a company spends per month in excess of what it earns. Gross burn is total monthly spend; net burn subtracts revenue collected. Burn rate is the rate at which runway depletes.

---

### CAC (Customer Acquisition Cost)
URL: https://frameworklist.com/glossary/cac

The total sales and marketing spend required to acquire one new paying customer, averaged across a period. Computed as sales + marketing spend / net new paying customers.

---

### CAC Payback Period
URL: https://frameworklist.com/glossary/payback-period

The number of months it takes for a customer's gross profit to repay the cost of acquiring them. The standard threshold of efficient SaaS growth is under 12 months for SMB, under 18 months for mid-market, under 24 months for enterprise.

---

### Cash Cow
URL: https://frameworklist.com/glossary/cash-cow

A business unit with high relative market share in a low-growth market — the BCG Matrix quadrant that generates far more cash than it consumes, and whose surplus funds the rest of the portfolio.

---

### Churn
URL: https://frameworklist.com/glossary/churn

The rate at which customers stop using or paying for a product over a given period. Customer churn measures lost logos; revenue churn measures lost recurring revenue. Usually expressed as a monthly or annual percentage.

---

### Cohort Analysis
URL: https://frameworklist.com/glossary/cohort-analysis

A method of analyzing user behavior by grouping users into cohorts based on a shared event (usually signup date) and tracking how each cohort's behavior evolves over time, rather than averaging across all users at once.

---

### CSAT (Customer Satisfaction Score)
URL: https://frameworklist.com/glossary/csat

A satisfaction metric measured by asking customers to rate a specific interaction or experience, typically on a 1–5 or 1–7 scale. CSAT is calculated as the percentage of customers who rate 4–5 (or 6–7), making it a transaction-level complement to NPS's relationship-level measurement.

---

### DAU / MAU
URL: https://frameworklist.com/glossary/dau-mau

Daily Active Users and Monthly Active Users — the two most-used engagement counts for consumer products. The DAU/MAU ratio (often called the 'stickiness ratio') measures how habitual usage is: 50% means the average user shows up half the days in a month.

---

### Flywheel
URL: https://frameworklist.com/glossary/flywheel

A self-reinforcing business mechanic where each part of the system makes the next part stronger — producing compounding rather than linear growth.

---

### ICP (Ideal Customer Profile)
URL: https://frameworklist.com/glossary/icp

A precise description of the customer type for whom a product delivers the highest value at the lowest cost to acquire and serve. ICP is the operational filter that prevents a sales team from chasing every lead.

---

### JTBD (Jobs-to-be-Done)
URL: https://frameworklist.com/glossary/jtbd

A customer-research framework that models purchases as the customer 'hiring' a product to make progress on a job. Instead of asking who the customer is, JTBD asks what they are trying to accomplish.

---

### KPI (Key Performance Indicator)
URL: https://frameworklist.com/glossary/kpi

A quantitative metric that summarizes ongoing operational health of a business function. KPIs answer 'is this part of the business running correctly?'; they are maintenance metrics, not ambition metrics.

---

### LTV (Lifetime Value)
URL: https://frameworklist.com/glossary/ltv

The total gross profit a business expects from a single customer over the entire duration of their relationship. LTV is the upper bound on how much you can spend to acquire that customer (CAC) and remain profitable.

---

### Moat
URL: https://frameworklist.com/glossary/moat

A sustainable competitive advantage that protects a business from competitors — analogous to a castle moat. Warren Buffett popularized the term in investing; the same concept applies to product strategy.

---

### MVP (Minimum Viable Product)
URL: https://frameworklist.com/glossary/mvp

The smallest version of a product that can be shipped to real users to test a critical hypothesis — not a polished early version of the final product, but a learning instrument.

---

### Network Effects
URL: https://frameworklist.com/glossary/network-effects

A property where each additional user makes the product more valuable to every other user — turning adoption itself into a competitive advantage that compounds and is hard for late entrants to overcome.

---

### North Star Metric
URL: https://frameworklist.com/glossary/north-star-metric

The single metric that best captures the core value a product delivers to its customers — the one number every team can rally around.

---

### NPS (Net Promoter Score)
URL: https://frameworklist.com/glossary/nps

A single-question customer loyalty metric calculated as %Promoters (9–10) minus %Detractors (0–6). NPS ranges from −100 to +100. Above 30 is good, above 50 is excellent, above 70 is best-in-class.

---

### NRR (Net Revenue Retention)
URL: https://frameworklist.com/glossary/nrr

The percentage of recurring revenue retained from existing customers over a period, including expansion and contraction but excluding new acquisitions. NRR above 100% means existing customers grew your revenue net of churn.

---

### OKRs (Objectives and Key Results)
URL: https://frameworklist.com/glossary/okrs

A goal-setting framework where each Objective is a qualitative, ambitious statement of intent and 3–5 Key Results are the quantitative measures of achievement. Developed by Andy Grove at Intel; brought to Google in 1999.

---

### Positioning
URL: https://frameworklist.com/glossary/positioning

The deliberate choice of how a product is described, framed, and compared so a defined customer immediately understands why they should choose it over alternatives. Positioning is the bridge between segmentation and messaging.

---

### Product-Market Fit
URL: https://frameworklist.com/glossary/product-market-fit

The state where a product satisfies strong market demand — typically signaled by usage growing without forced acquisition and >40% of users saying they'd be 'very disappointed' if the product disappeared.

---

### Retention
URL: https://frameworklist.com/glossary/retention

The share of customers (or users, or revenue) that continues to engage with a product over a defined time window. Retention is the closest single proxy for whether a product is delivering ongoing value.

---

### Rule of 40
URL: https://frameworklist.com/glossary/rule-of-40

A SaaS-investing heuristic: a healthy software company's growth rate plus its profit margin should sum to at least 40. The rule trades growth for profitability — either 40% growth with 0% margin or 0% growth with 40% margin clears the bar.

---

### Runway
URL: https://frameworklist.com/glossary/runway

The number of months a company can continue operating at its current spend before exhausting its cash. Runway = current cash ÷ monthly net burn. It is the most important number on a startup CEO's dashboard.

---

### Segmentation
URL: https://frameworklist.com/glossary/segmentation

The practice of dividing a market into groups that share buying behavior, needs, or willingness to pay. Useful segmentation produces groups large enough to matter and homogeneous enough to act on differently.

---

### Star
URL: https://frameworklist.com/glossary/star

A business unit with high relative market share in a high-growth market — the BCG Matrix quadrant that leads its category but consumes most of the cash it generates defending that lead.

---

### SWOT
URL: https://frameworklist.com/glossary/swot

A 2×2 strategy framework that maps a position across four dimensions: internal Strengths and Weaknesses (what the team controls) and external Opportunities and Threats (what the market is doing around it). Developed by Albert Humphrey at Stanford in the 1960s.

---

### TAM / SAM / SOM
URL: https://frameworklist.com/glossary/tam-sam-som

Three nested market-sizing figures: Total Addressable Market (the whole opportunity), Serviceable Addressable Market (the slice your offering can reach), and Serviceable Obtainable Market (the slice you can realistically win in the near term).

---

### Time to Value (TTV)
URL: https://frameworklist.com/glossary/time-to-value

The time between a customer signing up for a product and experiencing its first meaningful value. Short TTV correlates strongly with retention; long TTV correlates with churn before users ever see what the product can do.

---

### Unit Economics
URL: https://frameworklist.com/glossary/unit-economics

The revenue and cost associated with a single 'unit' of a business — typically one customer or one transaction. The fundamental test of whether a business model can ever be profitable.

---

### Viral Coefficient (K-factor)
URL: https://frameworklist.com/glossary/viral-coefficient

The average number of new users each existing user invites and converts. A K-factor above 1.0 produces exponential viral growth; under 1.0 means virality assists but does not sustain growth on its own.

---

### WSJF (Weighted Shortest Job First)
URL: https://frameworklist.com/glossary/wsjf

A prioritization formula from the Scaled Agile Framework that ranks work by cost of delay divided by job size. WSJF favors small, time-sensitive items over large, value-but-not-urgent items.

---