Paste your plan, goals, or strategy notes and get back

Get an honest read on your business plan

by wondelai · MIT license · ★ 2,235 on GitHub · updated Sep 10

Paste your plan, goals, or strategy notes and get back a clear verdict on what's real strategy versus wishful thinking, plus the exact fixes to make it stronger.

---
name: good-strategy-bad-strategy
description: 'Formulate and audit real strategy using Richard Rumelt''s "Good Strategy Bad Strategy": an honest diagnosis, a guiding policy, and coherent action instead of goals, vision, and wishful thinking. Use when the user mentions "good strategy bad strategy", "strategy kernel", "diagnosis guiding policy coherent action", "our strategy is just goals", "strategic planning", "mission vs strategy", "annual plan", or "is this actually a strategy". Also trigger when auditing a strategy doc or pitch deck for fluff, turning a goal list into real strategy, formulating strategy for a product or company, or finding leverage and proximate objectives. Covers the kernel of strategy, bad-strategy detection, and sources of power. For product positioning, see obviously-awesome. For uncontested markets, see blue-ocean-strategy.'
license: MIT
metadata:
author: wondelai
version: "1.2.0"
---

# Good Strategy Bad Strategy

A framework for creating and auditing strategy, distilled from Richard Rumelt's *Good Strategy Bad Strategy: The Difference and Why It Matters*. Good strategy has a simple underlying logic — an honest diagnosis of the critical challenge, a guiding policy for overcoming it, and coherent actions that carry the policy out. Use this skill to detect the four hallmarks of bad strategy and to replace goal lists and vision decks with a working kernel.

## Core Principle

**Strategy is coherent action backed by an honest diagnosis — not goals, vision, or wishful thinking.** A goal ("20% growth") names an ambition; a strategy explains how the ambition will be achieved given the actual obstacles. Bad strategy is not the absence of strategy but an active substitute for it: buzzword fluff, refusal to name the challenge, and laundry lists of initiatives. The heart of strategy work is choice — concentrating effort and resources on the one or two pivotal objectives whose accomplishment unlocks everything else.

## Scoring

Overview

A framework for creating and auditing strategy, distilled from Richard Rumelt's Good Strategy Bad Strategy: The Difference and Why It Matters. Good strategy has a simple underlying logic — an honest diagnosis of the critical challenge, a guiding policy for overcoming it, and coherent actions that carry the policy out. Use this skill to detect the four hallmarks of bad strategy and to replace goal lists and vision decks with a working kernel.

The SKILL.md below is the copy AgentAlley read and checked. The repo has changed it since; the other files are from commit c172996.

Manual install (npx, ZIP)

Claude Codenpx skills add wondelai/skills --skill good-strategy-bad-strategy -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wondelai/skills/tar.gz/c172996495be \
  | tar -xz -C ~/.claude/skills --strip-components=1 skills-c172996495be/good-strategy-bad-strategy

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/e84a65059cba931b9e01/good-strategy-bad-strategy.zip" -OutFile "$env:TEMP\good-strategy-bad-strategy.zip"; Expand-Archive "$env:TEMP\good-strategy-bad-strategy.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md19.0 KB
references/5 files · 59.2 KB

Read the files here

wondelai/c1729966 files

SKILL.md19.0 KB

SKILL.md

Show the full text194 lines

good-strategy-bad-strategy/SKILL.md194 lines · 18.6 KB · c172996

PreviewCode

Outline

RawView on GitHub

Good Strategy Bad Strategy

A framework for creating and auditing strategy, distilled from Richard Rumelt's Good Strategy Bad Strategy: The Difference and Why It Matters. Good strategy has a simple underlying logic — an honest diagnosis of the critical challenge, a guiding policy for overcoming it, and coherent actions that carry the policy out. Use this skill to detect the four hallmarks of bad strategy and to replace goal lists and vision decks with a working kernel.

Core Principle

Strategy is coherent action backed by an honest diagnosis — not goals, vision, or wishful thinking. A goal ("20% growth") names an ambition; a strategy explains how the ambition will be achieved given the actual obstacles. Bad strategy is not the absence of strategy but an active substitute for it: buzzword fluff, refusal to name the challenge, and laundry lists of initiatives. The heart of strategy work is choice — concentrating effort and resources on the one or two pivotal objectives whose accomplishment unlocks everything else.

Scoring

Goal: 10/10. Score strategies, plans, and strategy documents by walking the eight rows of the Quick Diagnostic and counting how many pass. Report the current score and the specific changes needed to reach 10/10. The bands below name what each tier looks like; the row count keeps the rating reproducible run to run.

9-10 (8 rows pass): Complete kernel — honest diagnosis, choiceful guiding policy, coordinated resource-backed actions — aimed at a pivot point, with an explicit list of what will not be done
7-8 (6-7 pass): Kernel present but one element weak: thin diagnosis, a policy that rules little out, or actions not yet coordinated and funded
5-6 (4-5 pass): The challenge is named, but the plan is a list of independent initiatives and some goals masquerade as strategy
3-4 (2-3 pass): Mostly goals, targets, and vision statements; no diagnosis; fluff in key passages; nothing ruled out
0-2 (0-1 pass): Pure bad strategy — buzzword fluff, dog's-dinner objective lists, denial of the real challenge

Framework

1. The Kernel of Good Strategy

Core concept: Every good strategy shares the same structure: a diagnosis that defines and simplifies the critical challenge, a guiding policy — the overall approach chosen to overcome the diagnosed obstacles — and coherent actions: coordinated, resource-backed steps that carry out the policy. A document missing any of the three is not yet a strategy.

Why it works: A diagnosis replaces the overwhelming complexity of reality with a simpler story that highlights what is critical, often by analogy to a known pattern. The guiding policy channels effort by ruling out vast realms of possible action — like guardrails, it directs without dictating every move. Coherent actions turn intent into coordinated force; most plans fail by jumping straight from ambition to a list of independent initiatives.

Key insights:

The diagnosis is the strategy's pivot: Gerstner reframed IBM's 1993 challenge from "mainframes are dying, break the company up" to "our advantage is integrated capability; the obstacle is internal coordination" — and everything downstream changed
A guiding policy is not a goal or a vision — it is an approach ("ride wave X by concentrating on Y"), and a real one feels like a choice with losers
If a competitor could paste your guiding policy into their deck unchanged, it is a platitude, not a policy
Coherent actions reinforce one another — each step makes the others easier — and every one carries an owner, resources, and a date
A kernel needs no mission, vision, or values preamble; it fits on one page
Most failed "strategies" skip the diagnosis entirely — prescribing before examining

Applications:

Context	Application	Example
Annual planning	Kernel before targets	Diagnosis: week-one churn; policy: fastest time-to-value in segment; actions: onboarding rebuild + roadmap cuts
Strategy review	Trace each action to the policy	Initiative serving no policy → cut or re-justify
Pitch deck	Kernel slide, not goals slide	"The obstacle, our approach, three coordinated moves"

Ethical boundary: An honest diagnosis names internal causes too — never soften it to protect egos or settle politics.

See references/kernel.md when you actually draft a kernel — diagnosis craft, guiding-policy formulation, coherent-action design, a fill-in template, and two worked examples with owners and done-tests.

2. Detecting Bad Strategy

Core concept: Bad strategy is not the absence of strategy — it is its own species with four hallmarks: fluff (gibberish masquerading as strategic concepts), failure to face the challenge, mistaking goals for strategy, and bad strategic objectives (dog's-dinner laundry lists or blue-sky impracticalities).

Why it works: Naming the hallmarks turns a vague sense that "this deck says nothing" into specific, fixable findings. Bad strategy persists for identifiable reasons — choice is painful, templates are easy, and positive thinking feels like leadership — so detection must hunt for substitutes for choice, not just bad writing.

Key insights:

Fluff test: restate the sentence in plain words — "our fundamental strategy is customer-centric intermediation" collapses to "we are a bank," which says nothing
If the document never names the obstacle, the strategy cannot be evaluated or improved — International Harvester's 1979 plan never mentioned its toxic labor relations, the actual problem
"20% growth, 20% margin" is a goal; exhortation to push harder is motivation, not a lever — strategy is the lever
Dog's dinner: a city plan with 47 "strategies" and 178 action items has no strategy; blue-sky: "become the leading platform" restates the end state and skips the how
Bad strategy has causes: unwillingness to choose (every real choice creates losers — DEC's consensus produced mush), template-style vision-mission-values planning, and New Thought culture (belief that visualizing success produces it)
The negation test: if the opposite of a statement is absurd ("we will not be customer focused"), the statement carries no information

Applications:

Context	Application	Example
Strategy deck audit	Score sections against the four hallmarks	"Vision" slide flagged as fluff; no obstacle named anywhere
OKR review	Separate ambitions from mechanisms	"Double signups" kept as goal, paired with an explicit how
Board update	Demand the challenge slide	"What we're up against" before "what we'll achieve"

See references/bad-strategy.md when auditing a deck or plan — per-hallmark detection checklists, before/after rewrites, why bad strategy proliferates, and a step-by-step deck-audit procedure with a report format.

3. Sources of Power

Core concept: Good strategy applies strength where it has the greatest effect, drawing on recurring sources of power: leverage (anticipation, pivot points, concentration), proximate objectives (targets close enough to actually hit), chain-link systems (quality matched across links), design (premeditated, coordinated configuration), focus, and using advantage (asymmetries protected by isolating mechanisms).

Why it works: Resources are always scarce relative to ambitions. Power comes from asymmetry — knowing something rivals don't, pressing where effort is amplified, or concentrating where they are spread thin. A strategy that names no source of power is hoping effort alone will win, which is matching strength against strength.

Key insights:

Leverage = anticipation × pivot point × concentration: anticipate predictable behavior, find the point where effort is amplified, then commit past the threshold where results become visible
A proximate objective is one the team can see how to hit; under high ambiguity, choose closer targets — a JPL engineer made Moon-lander design feasible by simply deciding a lunar soil model others could build against
In chain-link systems, performance is capped by the weakest link — investing in strong links is wasted until the weak one is fixed, which is why such systems stay stuck
A fully matched chain is also the deepest moat: IKEA's in-house design, flat-pack logistics, and warehouse showrooms each fit the others, so copying one link gains a rival nothing
Design-type strategy — tight, premeditated coordination of parts — pays when stakes are high and resources scarce; integration buys performance at the cost of flexibility
An advantage matters only at the point of contention: deepen it, broaden it, or strengthen isolating mechanisms (network effects, brand, patents, tacit know-how) that block imitation

Applications:

Context	Application	Example
Startup wedge choice	Concentrate past the threshold	One vertical owned end-to-end, not five touched
Stalled growth	Chain-link diagnosis	Fix activation (weakest link) before scaling paid acquisition
Ambiguous roadmap	Set a proximate objective	"Ten fintech design partners live" not "be the leader"

Ethical boundary: Build isolating mechanisms on delivered value — lock-in engineered purely to trap users eventually isolates you from them.

See references/sources-of-power.md when choosing where to apply strength — leverage, proximate objectives, chain-link systems, design, focus, and advantage, each with a when-to-use test (unlock test, addressability test, coherence check).

4. Riding Dynamics and Fighting Inertia

Core concept: Waves of change — technology shifts, deregulation, demographic change — are the attacker's best friend: they redistribute advantage and reset rules the incumbents had mastered. Incumbents are held back by three kinds of inertia (routine, culture, proxy) and by entropy — the unmanaged drift into blur and waste.

Why it works: In stable periods incumbents win on scale and accumulated advantage; in transitions their strengths become anchors — they defend legacy margins, rerun obsolete playbooks, and answer to cultures built for the old world. You don't need to predict the future, only to recognize that the present has already changed and act on it before those who can't.

Key insights:

Guideposts for sensing waves: rising fixed costs (force consolidation), deregulation or rule changes, predictable biases (people extrapolate the present), incumbent response (watch them protect old margins), and attractor states (where the industry "should" land given the technology)
An attractor state disciplines hype: ask "in the end state, who does the work and who gets paid?" — "all data transport becomes IP" correctly guided Cisco's rise
Inertia by routine yields to new metrics and outside hires; inertia by culture requires simplification and breaking insulated units; inertia by proxy means the incumbent profits from its customers' inertia — banks kept paying low deposit rates because depositors were slow to move
A rival's inertia is an exploitable asymmetry: attack where responding would force them to break their own economics
Entropy shows up as blurred product lines, drifting prices, and accidental cross-subsidies — weeding it is real strategy work even with no competitor in sight

Applications:

Context	Application	Example
Platform shift	Read the guideposts	Model training costs consolidate; value migrates to workflow owners
Pricing attack	Exploit margin defense	Usage-based pricing a seat-license incumbent can't match
Mature product	Entropy audit	Three overlapping plans collapsed into one clean ladder

Ethical boundary: Ride waves by serving the new need better — never by manufacturing fear about the old one.

See references/dynamics-inertia.md when a market is shifting or an incumbent is stuck — guideposts for spotting waves, diagnosing the three inertia types and entropy, and attacker playbooks for exploiting a rival's inertia.

5. Thinking Like a Strategist

Core concept: A strategy is a hypothesis about what will work, not a deduction from goals. Work like a scientist — diagnose, formulate, test against evidence, revise — and use deliberate techniques (create-destroy, the virtual panel of experts, a written first-person kernel) to defend judgment against first conclusions and herd opinion.

Why it works: The mind grabs the first plausible frame and defends it; groups converge on comfortable consensus. The market is an expensive place to discover you were wrong — cheap, disciplined destruction of your own ideas before commitment buys that learning early.

Key insights:

Treat strategy as a hypothesis and the market as the lab: Howard Schultz's Italian espresso-bar concept survived because he kept revising it against evidence — dropped the opera music, added chairs, offered nonfat milk
Create-destroy: generate genuinely different alternatives, then attack your own front-runner as hard as you would attack a rival's plan
Convene a virtual panel of experts: simulate the specific critiques of people whose judgment you respect — borrowed standards beat solo blind spots
First conclusions are the enemy; before accepting any diagnosis ask "what else could be going on?"
Keep the kernel written down — a strategy that lives in your head is unfalsifiable — with the list of what you choose not to do beside it
Independent judgment matters most when the crowd agrees: the market capitalized Global Crossing's hype while the underlying numbers said otherwise

Applications:

Context	Application	Example
Quarterly review	Re-test the diagnosis	Churn data contradicts it → kernel revised, not defended
Big bet	Create-destroy before commit	A second team builds the case against the acquisition
Founder discipline	Written kernel + no-list	One page: diagnosis, policy, three actions, five explicit nots

Ethical boundary: Use the virtual panel to find flaws, not to stage imagined authority blessing a foregone conclusion.

See references/case-studies.md for fully worked end-to-end examples — a SaaS annual-plan audit, a startup concentration decision, and a vision deck rewritten into a kernel.

Common Mistakes

Mistake	Why It Fails	Fix
Mistaking goals for strategy	"20% growth" names desire, not the lever that produces it	Write the kernel: diagnosis → policy → coherent actions
Skipping the diagnosis	Prescribing before examining; plan solves the wrong problem	One-paragraph diagnosis of the critical challenge first
Template planning (vision-mission-values)	Fill-in-the-blank boilerplate substitutes for analysis and choice	Start from the obstacle, not the template
Fluff in key passages	Buzzwords hide the absence of thought; nothing is testable	Restate plainly; if it becomes obvious or empty, cut it
Refusing to choose	Pleasing every stakeholder concentrates nothing	Name what you will not do; accept that choice creates losers
Dog's-dinner objectives	Forty "priorities" means none; resources spread to uselessness	Pick one to three proximate objectives; park the rest
Blue-sky objectives	Restates the desired end state; the team cannot see how	Choose targets close enough to actually hit
Spreading resources evenly	Below-threshold effort everywhere produces results nowhere	Concentrate on the pivot point until wins are visible
Treating strategy as settled truth	Conditions change; a defended diagnosis goes stale	Review as a hypothesis; revise on evidence, on a cadence

Quick Diagnostic

Question	If No	Action
Does the document name the critical challenge?	Nothing can be evaluated or improved	Write the one-paragraph diagnosis before any goals
Is there a guiding policy that rules out whole classes of action?	It is a platitude, not a policy	Add "therefore we will not..." statements until it bites
Are actions coordinated and resource-backed?	It is a wish list	Give each action an owner, budget, date, and a reinforcing role
Would the strategy be wrong for your nearest competitor?	It is generic fluff	Anchor it in your specific asymmetries and obstacles
Is the first objective close enough to actually hit?	Blue-sky target; the team stalls	Set a proximate objective with an owner and a done-test
Does the plan exploit a wave, asymmetry, or rival's inertia?	Strength is matched against strength	Find leverage: anticipation, pivot point, concentration
Is there an explicit list of what you will not do?	Scope creeps back to everything	Write the no-list next to the action list
Has anyone tried to destroy this strategy before adopting it?	First conclusions ship untested	Run create-destroy with a virtual panel of experts

About the Author

Richard Rumelt is professor emeritus at UCLA Anderson School of Management and one of the world's most influential thinkers on strategy — McKinsey Quarterly dubbed him "the strategist's strategist," and The Economist named him among the 25 most influential living management thinkers. He distilled four decades of research and consulting into Good Strategy Bad Strategy (2011) and The Crux (2022).

1	---
2	name: good-strategy-bad-strategy
3	description: 'Formulate and audit real strategy using Richard Rumelt''s "Good Strategy Bad Strategy": an honest diagnosis, a guiding policy, and coherent action instead of goals, vision, and wishful thinking. Use when the user mentions "good strategy bad strategy", "strategy kernel", "diagnosis guiding policy coherent action", "our strategy is just goals", "strategic planning", "mission vs strategy", "annual plan", or "is this actually a strategy". Also trigger when auditing a strategy doc or pitch deck for fluff, turning a goal list into real strategy, formulating strategy for a product or company, or finding leverage and proximate objectives. Covers the kernel of strategy, bad-strategy detection, and sources of power. For product positioning, see obviously-awesome. For uncontested markets, see blue-ocean-strategy.'
4	license: MIT
5	metadata:
6	author: wondelai
7	version: "1.2.0"
8	---
9
10	# Good Strategy Bad Strategy
11
12	A framework for creating and auditing strategy, distilled from Richard Rumelt's Good Strategy Bad Strategy: The Difference and Why It Matters. Good strategy has a simple underlying logic — an honest diagnosis of the critical challenge, a guiding policy for overcoming it, and coherent actions that carry the policy out. Use this skill to detect the four hallmarks of bad strategy and to replace goal lists and vision decks with a working kernel.
13
14	## Core Principle
15
16	Strategy is coherent action backed by an honest diagnosis — not goals, vision, or wishful thinking. A goal ("20% growth") names an ambition; a strategy explains how the ambition will be achieved given the actual obstacles. Bad strategy is not the absence of strategy but an active substitute for it: buzzword fluff, refusal to name the challenge, and laundry lists of initiatives. The heart of strategy work is choice — concentrating effort and resources on the one or two pivotal objectives whose accomplishment unlocks everything else.
17
18	## Scoring
19
20	Goal: 10/10. Score strategies, plans, and strategy documents by walking the eight rows of the Quick Diagnostic and counting how many pass. Report the current score and the specific changes needed to reach 10/10. The bands below name what each tier looks like; the row count keeps the rating reproducible run to run.
21
22	- 9-10 (8 rows pass): Complete kernel — honest diagnosis, choiceful guiding policy, coordinated resource-backed actions — aimed at a pivot point, with an explicit list of what will not be done
23	- 7-8 (6-7 pass): Kernel present but one element weak: thin diagnosis, a policy that rules little out, or actions not yet coordinated and funded
24	- 5-6 (4-5 pass): The challenge is named, but the plan is a list of independent initiatives and some goals masquerade as strategy
25	- 3-4 (2-3 pass): Mostly goals, targets, and vision statements; no diagnosis; fluff in key passages; nothing ruled out
26	- 0-2 (0-1 pass): Pure bad strategy — buzzword fluff, dog's-dinner objective lists, denial of the real challenge
27
28	## Framework
29
30	### 1. The Kernel of Good Strategy
31
32	Core concept: Every good strategy shares the same structure: a diagnosis that defines and simplifies the critical challenge, a guiding policy — the overall approach chosen to overcome the diagnosed obstacles — and coherent actions: coordinated, resource-backed steps that carry out the policy. A document missing any of the three is not yet a strategy.
33
34	Why it works: A diagnosis replaces the overwhelming complexity of reality with a simpler story that highlights what is critical, often by analogy to a known pattern. The guiding policy channels effort by ruling out vast realms of possible action — like guardrails, it directs without dictating every move. Coherent actions turn intent into coordinated force; most plans fail by jumping straight from ambition to a list of independent initiatives.
35
36	Key insights:
37	- The diagnosis is the strategy's pivot: Gerstner reframed IBM's 1993 challenge from "mainframes are dying, break the company up" to "our advantage is integrated capability; the obstacle is internal coordination" — and everything downstream changed
38	- A guiding policy is not a goal or a vision — it is an approach ("ride wave X by concentrating on Y"), and a real one feels like a choice with losers
39	- If a competitor could paste your guiding policy into their deck unchanged, it is a platitude, not a policy
40	- Coherent actions reinforce one another — each step makes the others easier — and every one carries an owner, resources, and a date
41	- A kernel needs no mission, vision, or values preamble; it fits on one page
42	- Most failed "strategies" skip the diagnosis entirely — prescribing before examining
43
44	Applications:
45
46	\| Context \| Application \| Example \|
47	\|---------\|-------------\|---------\|
48	\| Annual planning \| Kernel before targets \| Diagnosis: week-one churn; policy: fastest time-to-value in segment; actions: onboarding rebuild + roadmap cuts \|
49	\| Strategy review \| Trace each action to the policy \| Initiative serving no policy → cut or re-justify \|
50	\| Pitch deck \| Kernel slide, not goals slide \| "The obstacle, our approach, three coordinated moves" \|
51
52	Ethical boundary: An honest diagnosis names internal causes too — never soften it to protect egos or settle politics.
53
54	See [references/kernel.md](references/kernel.md) when you actually draft a kernel — diagnosis craft, guiding-policy formulation, coherent-action design, a fill-in template, and two worked examples with owners and done-tests.
55
56	### 2. Detecting Bad Strategy
57
58	Core concept: Bad strategy is not the absence of strategy — it is its own species with four hallmarks: fluff (gibberish masquerading as strategic concepts), failure to face the challenge, mistaking goals for strategy, and bad strategic objectives (dog's-dinner laundry lists or blue-sky impracticalities).
59
60	Why it works: Naming the hallmarks turns a vague sense that "this deck says nothing" into specific, fixable findings. Bad strategy persists for identifiable reasons — choice is painful, templates are easy, and positive thinking feels like leadership — so detection must hunt for substitutes for choice, not just bad writing.
61
62	Key insights:
63	- Fluff test: restate the sentence in plain words — "our fundamental strategy is customer-centric intermediation" collapses to "we are a bank," which says nothing
64	- If the document never names the obstacle, the strategy cannot be evaluated or improved — International Harvester's 1979 plan never mentioned its toxic labor relations, the actual problem
65	- "20% growth, 20% margin" is a goal; exhortation to push harder is motivation, not a lever — strategy is the lever
66	- Dog's dinner: a city plan with 47 "strategies" and 178 action items has no strategy; blue-sky: "become the leading platform" restates the end state and skips the how
67	- Bad strategy has causes: unwillingness to choose (every real choice creates losers — DEC's consensus produced mush), template-style vision-mission-values planning, and New Thought culture (belief that visualizing success produces it)
68	- The negation test: if the opposite of a statement is absurd ("we will not be customer focused"), the statement carries no information
69
70	Applications:
71
72	\| Context \| Application \| Example \|
73	\|---------\|-------------\|---------\|
74	\| Strategy deck audit \| Score sections against the four hallmarks \| "Vision" slide flagged as fluff; no obstacle named anywhere \|
75	\| OKR review \| Separate ambitions from mechanisms \| "Double signups" kept as goal, paired with an explicit how \|
76	\| Board update \| Demand the challenge slide \| "What we're up against" before "what we'll achieve" \|
77
78	See [references/bad-strategy.md](references/bad-strategy.md) when auditing a deck or plan — per-hallmark detection checklists, before/after rewrites, why bad strategy proliferates, and a step-by-step deck-audit procedure with a report format.
79
80	### 3. Sources of Power
81
82	Core concept: Good strategy applies strength where it has the greatest effect, drawing on recurring sources of power: leverage (anticipation, pivot points, concentration), proximate objectives (targets close enough to actually hit), chain-link systems (quality matched across links), design (premeditated, coordinated configuration), focus, and using advantage (asymmetries protected by isolating mechanisms).
83
84	Why it works: Resources are always scarce relative to ambitions. Power comes from asymmetry — knowing something rivals don't, pressing where effort is amplified, or concentrating where they are spread thin. A strategy that names no source of power is hoping effort alone will win, which is matching strength against strength.
85
86	Key insights:
87	- Leverage = anticipation × pivot point × concentration: anticipate predictable behavior, find the point where effort is amplified, then commit past the threshold where results become visible
88	- A proximate objective is one the team can see how to hit; under high ambiguity, choose closer targets — a JPL engineer made Moon-lander design feasible by simply deciding a lunar soil model others could build against
89	- In chain-link systems, performance is capped by the weakest link — investing in strong links is wasted until the weak one is fixed, which is why such systems stay stuck
90	- A fully matched chain is also the deepest moat: IKEA's in-house design, flat-pack logistics, and warehouse showrooms each fit the others, so copying one link gains a rival nothing
91	- Design-type strategy — tight, premeditated coordination of parts — pays when stakes are high and resources scarce; integration buys performance at the cost of flexibility
92	- An advantage matters only at the point of contention: deepen it, broaden it, or strengthen isolating mechanisms (network effects, brand, patents, tacit know-how) that block imitation
93
94	Applications:
95
96	\| Context \| Application \| Example \|
97	\|---------\|-------------\|---------\|
98	\| Startup wedge choice \| Concentrate past the threshold \| One vertical owned end-to-end, not five touched \|
99	\| Stalled growth \| Chain-link diagnosis \| Fix activation (weakest link) before scaling paid acquisition \|
100	\| Ambiguous roadmap \| Set a proximate objective \| "Ten fintech design partners live" not "be the leader" \|
101
102	Ethical boundary: Build isolating mechanisms on delivered value — lock-in engineered purely to trap users eventually isolates you from them.
103
104	See [references/sources-of-power.md](references/sources-of-power.md) when choosing where to apply strength — leverage, proximate objectives, chain-link systems, design, focus, and advantage, each with a when-to-use test (unlock test, addressability test, coherence check).
105
106	### 4. Riding Dynamics and Fighting Inertia
107
108	Core concept: Waves of change — technology shifts, deregulation, demographic change — are the attacker's best friend: they redistribute advantage and reset rules the incumbents had mastered. Incumbents are held back by three kinds of inertia (routine, culture, proxy) and by entropy — the unmanaged drift into blur and waste.
109
110	Why it works: In stable periods incumbents win on scale and accumulated advantage; in transitions their strengths become anchors — they defend legacy margins, rerun obsolete playbooks, and answer to cultures built for the old world. You don't need to predict the future, only to recognize that the present has already changed and act on it before those who can't.
111
112	Key insights:
113	- Guideposts for sensing waves: rising fixed costs (force consolidation), deregulation or rule changes, predictable biases (people extrapolate the present), incumbent response (watch them protect old margins), and attractor states (where the industry "should" land given the technology)
114	- An attractor state disciplines hype: ask "in the end state, who does the work and who gets paid?" — "all data transport becomes IP" correctly guided Cisco's rise
115	- Inertia by routine yields to new metrics and outside hires; inertia by culture requires simplification and breaking insulated units; inertia by proxy means the incumbent profits from its customers' inertia — banks kept paying low deposit rates because depositors were slow to move
116	- A rival's inertia is an exploitable asymmetry: attack where responding would force them to break their own economics
117	- Entropy shows up as blurred product lines, drifting prices, and accidental cross-subsidies — weeding it is real strategy work even with no competitor in sight
118
119	Applications:
120
121	\| Context \| Application \| Example \|
122	\|---------\|-------------\|---------\|
123	\| Platform shift \| Read the guideposts \| Model training costs consolidate; value migrates to workflow owners \|
124	\| Pricing attack \| Exploit margin defense \| Usage-based pricing a seat-license incumbent can't match \|
125	\| Mature product \| Entropy audit \| Three overlapping plans collapsed into one clean ladder \|
126
127	Ethical boundary: Ride waves by serving the new need better — never by manufacturing fear about the old one.
128
129	See [references/dynamics-inertia.md](references/dynamics-inertia.md) when a market is shifting or an incumbent is stuck — guideposts for spotting waves, diagnosing the three inertia types and entropy, and attacker playbooks for exploiting a rival's inertia.
130
131	### 5. Thinking Like a Strategist
132
133	Core concept: A strategy is a hypothesis about what will work, not a deduction from goals. Work like a scientist — diagnose, formulate, test against evidence, revise — and use deliberate techniques (create-destroy, the virtual panel of experts, a written first-person kernel) to defend judgment against first conclusions and herd opinion.
134
135	Why it works: The mind grabs the first plausible frame and defends it; groups converge on comfortable consensus. The market is an expensive place to discover you were wrong — cheap, disciplined destruction of your own ideas before commitment buys that learning early.
136
137	Key insights:
138	- Treat strategy as a hypothesis and the market as the lab: Howard Schultz's Italian espresso-bar concept survived because he kept revising it against evidence — dropped the opera music, added chairs, offered nonfat milk
139	- Create-destroy: generate genuinely different alternatives, then attack your own front-runner as hard as you would attack a rival's plan
140	- Convene a virtual panel of experts: simulate the specific critiques of people whose judgment you respect — borrowed standards beat solo blind spots
141	- First conclusions are the enemy; before accepting any diagnosis ask "what else could be going on?"
142	- Keep the kernel written down — a strategy that lives in your head is unfalsifiable — with the list of what you choose not to do beside it
143	- Independent judgment matters most when the crowd agrees: the market capitalized Global Crossing's hype while the underlying numbers said otherwise
144
145	Applications:
146
147	\| Context \| Application \| Example \|
148	\|---------\|-------------\|---------\|
149	\| Quarterly review \| Re-test the diagnosis \| Churn data contradicts it → kernel revised, not defended \|
150	\| Big bet \| Create-destroy before commit \| A second team builds the case against the acquisition \|
151	\| Founder discipline \| Written kernel + no-list \| One page: diagnosis, policy, three actions, five explicit nots \|
152
153	Ethical boundary: Use the virtual panel to find flaws, not to stage imagined authority blessing a foregone conclusion.
154
155	See [references/case-studies.md](references/case-studies.md) for fully worked end-to-end examples — a SaaS annual-plan audit, a startup concentration decision, and a vision deck rewritten into a kernel.
156
157	## Common Mistakes
158
159	\| Mistake \| Why It Fails \| Fix \|
160	\|---------\|-------------\|-----\|
161	\| Mistaking goals for strategy \| "20% growth" names desire, not the lever that produces it \| Write the kernel: diagnosis → policy → coherent actions \|
162	\| Skipping the diagnosis \| Prescribing before examining; plan solves the wrong problem \| One-paragraph diagnosis of the critical challenge first \|
163	\| Template planning (vision-mission-values) \| Fill-in-the-blank boilerplate substitutes for analysis and choice \| Start from the obstacle, not the template \|
164	\| Fluff in key passages \| Buzzwords hide the absence of thought; nothing is testable \| Restate plainly; if it becomes obvious or empty, cut it \|
165	\| Refusing to choose \| Pleasing every stakeholder concentrates nothing \| Name what you will not do; accept that choice creates losers \|
166	\| Dog's-dinner objectives \| Forty "priorities" means none; resources spread to uselessness \| Pick one to three proximate objectives; park the rest \|
167	\| Blue-sky objectives \| Restates the desired end state; the team cannot see how \| Choose targets close enough to actually hit \|
168	\| Spreading resources evenly \| Below-threshold effort everywhere produces results nowhere \| Concentrate on the pivot point until wins are visible \|
169	\| Treating strategy as settled truth \| Conditions change; a defended diagnosis goes stale \| Review as a hypothesis; revise on evidence, on a cadence \|
170
171	## Quick Diagnostic
172
173	\| Question \| If No \| Action \|
174	\|----------\|-------\|--------\|
175	\| Does the document name the critical challenge? \| Nothing can be evaluated or improved \| Write the one-paragraph diagnosis before any goals \|
176	\| Is there a guiding policy that rules out whole classes of action? \| It is a platitude, not a policy \| Add "therefore we will not..." statements until it bites \|
177	\| Are actions coordinated and resource-backed? \| It is a wish list \| Give each action an owner, budget, date, and a reinforcing role \|
178	\| Would the strategy be wrong for your nearest competitor? \| It is generic fluff \| Anchor it in your specific asymmetries and obstacles \|
179	\| Is the first objective close enough to actually hit? \| Blue-sky target; the team stalls \| Set a proximate objective with an owner and a done-test \|
180	\| Does the plan exploit a wave, asymmetry, or rival's inertia? \| Strength is matched against strength \| Find leverage: anticipation, pivot point, concentration \|
181	\| Is there an explicit list of what you will not do? \| Scope creeps back to everything \| Write the no-list next to the action list \|
182	\| Has anyone tried to destroy this strategy before adopting it? \| First conclusions ship untested \| Run create-destroy with a virtual panel of experts \|
183
184	## Further Reading
185
186	- "Good Strategy Bad Strategy: The Difference and Why It Matters" by Richard Rumelt
187	- "The Crux: How Leaders Become Strategists" by Richard Rumelt
188	- "Playing to Win: How Strategy Really Works" by A.G. Lafley & Roger L. Martin
189	- "7 Powers: The Foundations of Business Strategy" by Hamilton Helmer
190
191	## About the Author
192
193	Richard Rumelt is professor emeritus at UCLA Anderson School of Management and one of the world's most influential thinkers on strategy — McKinsey Quarterly dubbed him "the strategist's strategist," and The Economist named him among the 25 most influential living management thinkers. He distilled four decades of research and consulting into Good Strategy Bad Strategy (2011) and The Crux (2022).
194