# Detecting Bad Strategy

## Table of Contents

- [Bad Strategy Is Its Own Species](#bad-strategy-is-its-own-species)
- [Hallmark 1: Fluff](#hallmark-1-fluff)
- [Hallmark 2: Failure to Face the Challenge](#hallmark-2-failure-to-face-the-challenge)
- [Hallmark 3: Mistaking Goals for Strategy](#hallmark-3-mistaking-goals-for-strategy)
- [Hallmark 4: Bad Strategic Objectives](#hallmark-4-bad-strategic-objectives)
- [Why Bad Strategy Proliferates](#why-bad-strategy-proliferates)
- [Auditing a Strategy Deck Section by Section](#auditing-a-strategy-deck-section-by-section)
- [The Audit Report Format](#the-audit-report-format)

## Bad Strategy Is Its Own Species

Bad strategy is not the absence of strategy, and it is not a good strategy that failed. It is a recognizable construction with its own logic: it skips the hard work of diagnosis and choice, and fills the space with substitutes — buzzwords, ambitions, templates, and positive thinking. Because it has structure, it can be detected systematically. Hunt for the four hallmarks below; finding any one is a finding, finding three is a verdict.

## Hallmark 1: Fluff

Fluff is gibberish masquerading as strategic concepts: inflated language, restated obviousness, and abstraction stacked on abstraction to create the illusion of high-level thinking.

**Detection checklist:**

- **Plain-language restatement.** Translate the sentence into ordinary words. If it collapses into the obvious ("our strategy is customer-centric intermediation" → "we are a bank"), it is fluff.
- **The negation test.** Negate the claim. If the negation is absurd — "we will *not* pursue excellence," "we will *not* put customers first" — the original carries zero information.
- **Buzzword density.** Count occurrences of *leverage, synergy, world-class, best-in-class, ecosystem, holistic, next-generation, win-win, empower* per page. More than two per page in load-bearing sentences is a red flag.
- **Abstraction stack.** If defining one term requires three more undefined terms ("a platform-led ecosystem strategy enabling scalable value creation"), the stack is hiding an empty center.
- **The Monday test.** Ask: what would someone do differently on Monday because of this sentence? No answer, no content.

**Before:** "Our strategy is to leverage best-in-class AI capabilities and a customer-obsessed culture to deliver differentiated, scalable value across the full customer lifecycle."

**After (plain restatement):** "We use AI and try to be good to customers" — which every competitor would also claim. A real replacement: "We will win mid-market support teams by being the only vendor whose agent resolves tickets end-to-end inside Zendesk — accepting that enterprises with custom stacks are not our market."

## Hallmark 2: Failure to Face the Challenge

If a strategy document does not name and analyze the obstacle, there is no way to evaluate the strategy or improve it. International Harvester's 1979 plan was full of projections and initiatives — and never mentioned its famously toxic labor relations, the actual problem that sank it. The omission is rarely accidental: naming the challenge embarrasses someone or implies a painful choice.

**Detection checklist:**

- Search the document for an obstacle. Is there a section that says what stands in the way? (Not "risks" boilerplate — the actual difficulty.)
- Does it explain *why* performance is what it is — why deals are lost, why churn rose, why the last plan missed?
- Would a smart new executive, reading only this document, learn what is hard about this business right now?
- Are competitors named, with the specific reason they win when they win?
- Is anything in the document unflattering to the team that wrote it? A document with no self-implicating facts has been sanitized.

**Before:** "Building on our momentum, we will accelerate growth through product-led expansion, strategic partnerships, and operational excellence."

**After:** "Inbound demand fell 40% in two quarters because AI answers absorbed the search traffic our content funnel depended on. Our growth model — SEO → trial → sales-assist — is structurally broken at the top. The challenge is rebuilding demand generation around channels we can defend." Now a strategy can exist, because there is something for it to overcome.

## Hallmark 3: Mistaking Goals for Strategy

Goals are ambitions: revenue targets, market-share numbers, "20% growth." Strategy is the lever — the diagnosis and approach that make the ambition achievable. A CEO whose plan is "20/20: twenty percent growth, twenty percent margin" plus exhortation to push harder has a desire and a pep talk, not a strategy.

**Detection checklist:**

- **Verb audit.** Circle the verbs in the "strategy" section. *Achieve, grow, increase, deliver, drive, accelerate, maximize* are ambition verbs. *Concentrate, exit, rebuild, target, replace, consolidate* are choice verbs. A section with only ambition verbs is a goals list.
- **Mechanism check.** For each number, is there an answer to "what changes in the world or in our conduct that produces this?"
- **Effort substitution.** Phrases like "relentless execution," "raising the bar," "one team, one dream" used as the *how* signal motivation standing in for method.
- **Source of the number.** Was the target derived from a diagnosis ("fixing activation should lift conversion from 9% to 15%") or from desire ("the board wants 2x")?

**Before:** "Our strategy for FY26: grow ARR 25%, raise NRR to 115%, launch 12 features, expand to two new regions."

**After:** "Diagnosis: expansion revenue stalled because our pricing caps usage growth. Guiding policy: re-price around the metric that scales with customer value (documents processed), concentrating sales on the 200 accounts hitting plan ceilings. Actions: usage-based tier (Q1), migration playbook for the 200 accounts (Q1-Q2), retire per-seat plans for new sales (Q2). The 25% ARR target is the *forecast* of this working — not the strategy."

## Hallmark 4: Bad Strategic Objectives

Even when leaders move past fluff and goals, they can produce objectives that no one can act on. Two failure shapes:

**The dog's dinner** — a long list of "strategic priorities" that is really a union of every department's wish list. One city's strategic plan contained 47 "strategies" and 178 action items; item 122 was "create a strategic plan." Tests:

- Count the "priorities." More than five means none are priorities.
- Check for resourcing. If the list exceeds what the org can staff, it is a wish list, not a plan.
- Check for conflict. Real choices conflict with something; a list where nothing conflicts with anything was assembled, not chosen.

**The blue sky** — an objective that simply restates the desired end state, skipping over the gap between here and there: "become the #1 platform," "be the most trusted brand in the category." Tests:

- Can the team see *how*? If the objective is as hard to act on as the original challenge, it has added nothing.
- Is it a re-description of winning? "Win the market" is not an objective; "win 10 of the 30 design-partner candidates in fintech by June" is.
- Does it resolve ambiguity, or just relocate it?

**Before:** "Strategic priorities: 1) Delight customers 2) Win the enterprise 3) Build a world-class team 4) Operational excellence 5) Innovate boldly 6) Expand internationally 7) Strengthen the brand..." (and 16 more).

**After:** "Objective for the next two quarters: make the EU instance fully self-serve — signup to production without a sales call — because the diagnosis shows sales-assisted onboarding caps us at 40 deals/quarter. Everything on the old list that does not serve this is parked."

## Why Bad Strategy Proliferates

Detection improves when you know why bad strategy gets written despite everyone preferring good strategy.

**1. Choice is painful.** A real guiding policy rules things out, and every ruled-out option has a sponsor. Faced with that conflict, leaders produce "strategies" that fund everything a little — universal buy-in, zero concentration. Digital Equipment Corporation's leadership, unable to choose among three rival futures, blended them into "DEC is committed to providing high-quality products and services and being a leader in data processing" — mush that chose nothing while the company sank. When you see mush, look for the unresolved fight underneath it.

**2. Template-style planning.** A whole industry sells the fill-in-the-blanks format: Vision → Mission → Values → Strategies. The template manufactures documents that look complete while containing no diagnosis and no choice — the "strategies" slot gets filled with goals because nothing upstream forced an analysis of the obstacle. The template is how organizations produce bad strategy *in good faith*.

**3. New Thought culture.** A nineteenth-century idea — that visualizing success produces success — survives in business as the cult of vision: believe, project confidence, never entertain doubt. It makes diagnosis feel disloyal ("too negative") and substitutes shared belief for analysis. The tell: a document whose emotional register is inspiration throughout, with no section that could disappoint anyone.

## Auditing a Strategy Deck Section by Section

A practical procedure for auditing a strategy document, deck, or annual plan:

1. **Inventory.** List every section/slide. Classify each as: *diagnosis, guiding policy, action, goal, evidence, fluff, other.* Most decks classify as 60% goals + fluff, 0% diagnosis.
2. **Hunt the diagnosis.** Is there one falsifiable paragraph naming the critical challenge? If absent, the audit's top finding is already written.
3. **Test the policy.** Apply the negation test and the competitor-paste test (would this read as false in the rival's deck?). List what the policy rules out; if nothing, flag it.
4. **Test the actions.** Coherence (do they reinforce each other?), resourcing (owners, budgets, dates?), and traceability (does each serve the policy?). Orphan actions reveal the real, unstated strategy: momentum.
5. **Apply the hallmark checklists** above to the remaining sections; log each hit with a quote.
6. **Score it** on the skill's 0-10 scale and write the rewrite path: which sections to delete, which single paragraph to write first (always the diagnosis), which list to cut to three.

| Deck section | What to look for | Typical red flag |
|--------------|------------------|------------------|
| "Vision / Mission" | Anything load-bearing | Strategy expected to live here — it can't |
| "Market" | Facts that imply the obstacle | TAM slides with no implication for conduct |
| "Strategy" | A guiding policy | Goals with ambition verbs; platitudes |
| "Strategic priorities" | 1-3 choices that conflict with something | 10+ items; every department represented |
| "Roadmap / Initiatives" | Coherence and resourcing | Independent projects; nothing stopped |
| "Financials" | Forecast linked to mechanism | Hockey stick justified by "momentum" |

## The Audit Report Format

Deliver findings in this shape:

```
STRATEGY AUDIT: [document name]
Score: X/10 (skill scoring bands)

THE CHALLENGE THE DOCUMENT FACES (or fails to):
[your one-paragraph statement of what the real challenge appears to be]

HALLMARK FINDINGS:
- Fluff: [quote] → [plain restatement] → [verdict]
- Challenge: [named? where? what's missing]
- Goals-as-strategy: [quote] → [the missing mechanism]
- Bad objectives: [dog's dinner / blue sky, with counts]

WHAT SURVIVES: [sections worth keeping, evidence worth reusing]

REWRITE PATH:
1. Write the diagnosis paragraph (draft provided below)
2. [specific next steps — policy candidates, list cuts, no-list]
```

Lead with the diagnosis you believe the document avoided — an audit that only criticizes is itself a dog's dinner. The goal is not to shame the deck but to leave its owners one page away from a real kernel.

# Case Studies: Good Strategy Bad Strategy in Practice

## Table of Contents

- [Case Study 1: Auditing a SaaS Annual Plan](#case-study-1-auditing-a-saas-annual-plan)
- [Case Study 2: A Startup Chooses Where to Concentrate](#case-study-2-a-startup-chooses-where-to-concentrate)
- [Case Study 3: Rewriting a Vision Deck into a Kernel](#case-study-3-rewriting-a-vision-deck-into-a-kernel)
- [Key Takeaways](#key-takeaways)

## Case Study 1: Auditing a SaaS Annual Plan

### Context

A 60-person B2B SaaS company sells compliance-training software to mid-market HR teams. $9M ARR, growth slowing from 40% to 12% year over year. The leadership team produced a 34-slide annual plan titled "Strategy FY27" and asked for a review before presenting it to the board.

### The Document

The deck contained: a vision slide ("To be the most trusted partner in workforce compliance"), three values slides, a market-size slide ($4.2B TAM), targets (25% ARR growth, NRR from 103% to 112%, logo churn under 8%), and fourteen initiatives spanning every department — AI course generation, a manager dashboard, SOC 2 Type II, a partner program, two new verticals, a website refresh, and eight more.

### Applying the Skill

**Step 1 — Inventory and classification.** Every slide was classified as diagnosis, policy, action, goal, evidence, or fluff. Result: 0 diagnosis slides, 0 policy slides, 19 goal/initiative slides, 6 fluff slides, 9 evidence slides. The headline finding wrote itself: the plan contained targets and activities but no statement of what stands in the way.

**Step 2 — Hallmark scan.** Fluff: "trusted partner in workforce compliance" failed the negation test (no rival aspires to be untrusted). Goals for strategy: the verb audit found *grow, increase, deliver, expand, accelerate* — not one choice verb. Bad objectives: fourteen initiatives for nine engineers was a dog's dinner; nothing conflicted with anything, the signature of an assembled rather than chosen list.

**Step 3 — Hunting the missing diagnosis.** The audit reconstructed the challenge from evidence the deck itself contained but never confronted: 70% of historical leads came from SEO content; organic traffic was down 45% in three quarters as AI answers absorbed compliance questions; win rates were stable. The company did not have a growth problem — it had a demand-generation collapse the plan never mentioned, plus a quieter fact buried in the churn appendix: accounts using the audit-trail feature churned at one-third the rate of the rest.

**Step 4 — Kernel rewrite.** Working session with the exec team produced one page:

- **Diagnosis:** Our acquisition engine (SEO → trial) is structurally broken by AI search, and we are funding fourteen initiatives as if it still worked. Meanwhile our stickiest value — audit-proof training records — is treated as a feature, not the product.
- **Guiding policy:** Reposition from "training content" to "audit protection" — the system of record HR shows the regulator — and rebuild demand on channels AI answers cannot absorb: compliance-auditor partnerships and integration marketplaces. Therefore we will not: chase the two new verticals, build AI course generation this year, or bid on broken SEO terms.
- **Coherent actions:** (1) Audit-trail becomes the lead product and demo (product, Q1); (2) partner program rebuilt exclusively for compliance auditors and HRIS marketplaces (one senior hire, Q1-Q2); (3) pricing anchored to audit risk, not seat count (Q2); (4) kill eight initiatives, redeploying six engineers (immediately).

### Outcome

| Aspect | Before | After |
|--------|--------|-------|
| Plan length | 34 slides | 1 kernel page + 6 evidence slides |
| Initiatives | 14 | 4 coordinated actions + kill list |
| Challenge named | Nowhere | First paragraph |
| Board reaction | (prior year) "ambitious" | "First time we understood the business" |
| Two quarters later | — | Partner-sourced pipeline 0% → 31%; NRR 103 → 109 |

### Lessons

1. The decisive audit move was classification — counting zero diagnosis slides ended the debate about whether the plan was a strategy.
2. The diagnosis was already in the appendix data; bad strategy is usually evidence avoidance, not evidence absence.
3. The kill list freed more capacity than any hiring plan could have.

## Case Study 2: A Startup Chooses Where to Concentrate

### Context

A seed-stage startup (9 people, $1.8M raised, 13 months of runway) sells an AI agent that turns sales calls into CRM updates. $21K MRR spread across three customer types: SMB sales teams, recruiting agencies, and management consultants. Each segment uses the product differently; the roadmap is a queue of per-segment requests. Growth is 4% a month and the founders disagree about where to push.

### Applying the Skill

**Step 1 — Name the pattern.** The diagnosis workshop recognized a threshold shortfall: three motions, none past the visibility threshold. Nine people cannot hold three ICPs above threshold; the strategy question was not "how do we grow" but "where do we concentrate."

**Step 2 — Anticipation scan.** The team wrote the "announced futures" register. Decisive entry: the two dominant CRMs had both announced native call-summary features shipping within a year. Generic "calls → CRM notes" was a dying wedge — whatever segment they chose had to be one where native features would still lose.

**Step 3 — Score the segments against sources of power.** Each segment was scored 1-5 on: pull (inbound, usage depth), asymmetry (why incumbents/native features can't serve it), isolating-mechanism potential (what compounds), and threshold reachability within runway.

| Criterion | SMB sales | Recruiting agencies | Consultants |
|-----------|-----------|--------------------:|-------------|
| Pull today | 3 | 4 | 2 |
| Asymmetry vs. native CRM features | 1 — head-on | 4 — ATS fragmentation, candidate + client double-entry | 3 — but bespoke workflows |
| Isolating-mechanism potential | 1 | 4 — placement-outcome data network | 2 |
| Threshold within 13 months | 2 — broad market | 4 — dense niche, 3 conferences, 2 communities | 2 |
| **Total** | **7** | **16** | **9** |

Recruiting agencies won on the only criterion that mattered most: the CRM vendors' announced features (anticipation) would commoditize the sales use case first, while recruiting ran on fragmented ATSes the natives would not prioritize — a rival's-roadmap asymmetry plus a reachable, dense niche.

**Step 4 — Set the proximate objective and the no-list.** High ambiguity ruled out a revenue target. The proximate objective: *in 8 weeks, 20 recruiting agencies live, with intake-call → ATS + client-update workflow complete end-to-end, and weekly usage retention above 60%.* The no-list: no new SMB sales features, no consultant customizations, sunset both with 90-day migration help, decline non-recruiting inbound.

**Step 5 — Create-destroy before commit.** One founder spent two days building the case *against* recruiting (small TAM, ATS API risk, agency churn). The attack surfaced a real rabbit hole — two ATS APIs covered only 60% of target agencies — which became action item one (integration coverage) instead of a Q3 surprise. The bet survived its own destruction and shipped.

### Outcome

Six months later: $58K MRR, 96% from recruiting; growth 11% monthly; the placement-outcome dataset (which intake answers predict successful placements) became the demo's closing slide — an isolating mechanism no horizontal note-taker had. The CRM-native features shipped as predicted and erased three of the startup's former competitors. One founder's note: "Choosing felt like killing two-thirds of the company. It was the first day the company existed."

### Lessons

1. Anticipation — reading rivals' announced roadmaps — eliminated an option that pull alone would have kept alive.
2. The scoring table did not make the choice; it forced the disagreement into criteria, where it could be resolved.
3. Create-destroy converted the riskiest unknown into the first action item.

## Case Study 3: Rewriting a Vision Deck into a Kernel

### Context

A 200-person payments scale-up prepared for its Series C with an offsite that produced a 30-slide "Vision 2030" deck: mission, five values, five strategic pillars (Growth, Innovation, Customers, People, Excellence), and 23 initiatives distributed under the pillars. A board member's only comment: "This is lovely. What's the strategy?" The CEO brought the deck to a working group with this skill.

### Applying the Skill

**Step 1 — Honest classification.** The group labeled every slide. Pillars were categories, not choices — each one passed the negation test into absurdity ("we will not pursue Excellence"). The 23 initiatives mapped 1:1 to org-chart departments: the deck was the org chart wearing a costume, the signature of unwillingness to choose.

**Step 2 — Force candidate diagnoses.** Instead of debating pillars, each of five leaders wrote a one-paragraph diagnosis of the single critical challenge. Three candidates emerged: (a) enterprise deals stall in security review; (b) unit economics depend on interchange fees that regulators in two core markets have signaled they will cap; (c) product breadth has outrun reliability.

**Step 3 — Create-destroy with a virtual panel.** Each candidate was attacked through three personas: a skeptical CFO ("show me the number"), a churned customer, and the rival's head of product ("which diagnosis would I *hope* they pick?"). The interchange-cap diagnosis (b) survived strongest: the CFO persona found 61% of gross margin exposed to announced regulatory intent — a wave, with a date range. Candidates (a) and (c) were real but downstream: both became easier with the margin problem named, failing the unlock test in reverse.

**Step 4 — Write the kernel.**

- **Diagnosis:** 61% of gross margin rides on interchange fees that two regulators have signaled they will cap within ~three years. Our "vision" assumes an economic engine that is scheduled to shrink; every initiative priced against it is built on sand.
- **Guiding policy:** Shift the revenue base from payment rails to the software workflow around money movement — reconciliation, spend controls, forecasting — where willingness-to-pay survives fee caps, concentrating on the 400 mid-market customers who already use two or more workflow features. Therefore we will not: expand to new payment geographies this cycle, compete on rail pricing, or fund initiatives that scale fee-dependent volume.
- **Coherent actions:** (1) Software-revenue line target with its own owner (CRO, immediate); (2) workflow suite packaged and priced standalone (product, two quarters); (3) the 400-account expansion motion staffed by reassigning the geo-expansion team (Q1); (4) initiative review: each of the 23 initiatives re-justified against the policy.
- **Review trigger:** any regulatory ruling, or software revenue share below 25% by year-end.

**Step 5 — The cull.** Against the policy, 14 of 23 initiatives were killed or parked, including two sacred ones (a consumer app pilot and a sponsorship). The remaining nine were re-sequenced so each fed the software-revenue shift. The five pillars were retired; the values slides moved to the employee handbook, where they belonged.

### Outcome

| Aspect | Vision deck | Kernel |
|--------|------------|--------|
| Length | 30 slides | 1 page + appendix |
| Initiatives | 23 unranked | 9, sequenced, each policy-traced |
| Margin exposure named | No | First paragraph, quantified |
| Series C diligence | — | Kernel reused verbatim in the data room |
| One year later | — | Software revenue 14% → 33% of gross margin |

### Lessons

1. "What's the strategy?" is answered by a diagnosis, never by pillars — categories are where choices go to hide.
2. The virtual panel converted a political fight (whose diagnosis wins) into an analytical one (which diagnosis survives attack).
3. Retiring the vision deck cost nothing: mission and values survived intact in their proper home, and the strategy finally existed.

## Key Takeaways

1. **Classification beats argument.** Counting diagnosis slides (usually zero) settles "is this a strategy?" faster than any debate.
2. **The diagnosis is usually avoidable evidence, already in hand.** Appendix churn tables, announced regulations, rivals' public roadmaps — bad strategy is the art of not looking.
3. **Choice creates losers, and that is the point.** Every case required killing real work with real sponsors; the relief came after, never before.
4. **Proximate objectives make strategy executable under ambiguity.** Eight-week, owner-named, done-testable targets moved teams that grand targets had stalled.
5. **Destroy your strategy before the market does.** Create-destroy and the virtual panel found the rabbit holes and weak diagnoses while they were still cheap.

# Riding Dynamics, Fighting Inertia

## Table of Contents

- [Why Waves of Change Favor Attackers](#why-waves-of-change-favor-attackers)
- [Five Guideposts for Sensing Waves](#five-guideposts-for-sensing-waves)
- [Writing a Wave Brief](#writing-a-wave-brief)
- [The Three Inertias](#the-three-inertias)
- [Entropy](#entropy)
- [Attacker Playbooks](#attacker-playbooks)
- [Notes for Defenders](#notes-for-defenders)

## Why Waves of Change Favor Attackers

In stable periods, incumbents win: scale, brand, distribution, and accumulated learning compound in their favor, and a second-rate strategy is enough. Waves of change — technology shifts, deregulation, demographic and cost-structure changes — reset the contest. The incumbent's optimized machine is optimized for the old world; its margins are hostage to the old model; its people were promoted for mastering rules that no longer apply. For an attacker, a wave is exogenous leverage: you do not have to create the shift, only to see its implications earlier and commit to them more coherently than those who cannot.

The discipline is seeing the wave *as it is breaking* — not predicting the far future. Most of what matters has already happened: the cost curve has already bent, the rule has already been announced, the behavior has already shifted in the youngest cohort. Strategy reads the present closely rather than the future speculatively.

## Five Guideposts for Sensing Waves

Use these as a standing checklist whenever an industry feels like it is moving.

**1. Rising fixed costs.** When the cost of staying at the technical frontier rises sharply (R&D, content, capital equipment), the industry consolidates around the few who can pay, and everyone else must reposition. Detection questions: What does it cost to field a competitive offering today vs. five years ago? Who can no longer afford the table stakes? Product read: frontier-model training costs consolidate AI infrastructure into a handful of labs — so most companies' strategies should assume models are rented, not owned, and differentiation must live in data, workflow, and distribution built *on top* of the consolidating layer.

**2. Deregulation — and rule changes generally.** When governments or platform owners change the rules (deregulation, new compliance regimes, app-store policy, privacy frameworks), the value pool is re-divided. Incumbents systematically misjudge the new world: they keep prices and cross-subsidies anchored to the old regime, overpay to defend formerly protected businesses, and underinvest where the new rules open ground. Detection questions: Which prices in this industry exist only because a rule made them possible? Whose cross-subsidy becomes untenable? Product read: a platform's API pricing change or a new AI act is a re-division of the pool — map who was subsidized by the old rules and serve the newly orphaned.

**3. Predictable biases.** In transitions, people forecast badly in patterned ways: they extrapolate the present (assuming growth continues because it has), assume the old normal will return, imitate the most visible player, and pile into whatever the herd funds. Each bias is exploitable by whoever bets on the underlying mechanics instead. Detection questions: What does everyone currently assume continues forever? Where is capital crowding on momentum rather than mechanism? The contrarian opportunity is rarely "the opposite" — it is the specific spot the herd's simplification ignores.

**4. Incumbent response.** Incumbents respond to waves in predictable defensive shapes: protect the legacy margin (milk the old business rather than cannibalize it), retreat upmarket toward their best customers, bundle the threatened product into suites, and announce hybrid offerings that preserve the old economics. Each defensive move tells you where the door is open. Detection questions: Read the incumbent's earnings calls — what number are they defending? What would they have to destroy internally to follow you? Product read: when the suite vendor responds to your point product by bundling harder, they are conceding the standalone market's users while defending the CFO relationship — choose which contest you want.

**5. Attractor states.** An attractor state is where the industry "should" end up given technology and cost fundamentals — the configuration that would emerge if efficiency alone decided. "All data transport becomes IP" was telecom's attractor state; Cisco rode it for a decade while incumbents protected circuit-switched margins. Attractor states discipline wishful thinking because they are grounded in demand and cost logic, not in your hopes. Detection questions: In the efficient end state, who does the work, who gets paid, and which of today's toll booths still exist? What accelerants (cost curves, standards) and impediments (regulation, switching costs, installed bases) set the pace? Product read: "routine support tickets get resolved by software" is an attractor state; the strategic questions are pace and who owns the workflow when it arrives.

## Writing a Wave Brief

Condense the guideposts into a one-page brief before betting a roadmap on a wave:

```
WAVE BRIEF: [shift name, date]
What already changed: [cost curves, rules, behaviors — facts, not forecasts]
Guidepost readings: [fixed costs / rules / biases / incumbent response / attractor state]
Who is mispositioned: [incumbents and why their economics block response]
The attractor state: [who does the work, who gets paid, when]
Timing risk: [what makes this slower than it looks; can we survive being early?]
Our asymmetry on this wave: [why us]
```

The timing line is mandatory. Waves reliably take longer than enthusiasts expect — being early without the runway to wait is indistinguishable from being wrong.

## The Three Inertias

Inertia is an organization's inability or unwillingness to adapt. Diagnose the type before prescribing — or before attacking — because each has a different mechanism.

| Type | Mechanism | Signs | Fix (incumbent) | Attack (challenger) |
|------|-----------|-------|-----------------|---------------------|
| Routine | Old playbooks keep executing | Metrics, pricing, and processes from the previous era | New metrics, outside hires, forced exposure to lost deals | Compete where the playbook misfires |
| Culture | Identity blocks adaptation | "We are an X company"; sacred projects; new ventures starved | Simplify, break insulated units, change leaders; takes years | Announce the future loudly — their culture will deny it |
| Proxy | Customers' inertia shields the incumbent | Incumbent profits from customers not switching | Painful: moving first cannibalizes today's profit | Collapse the customers' switching cost directly |

**Inertia by routine** is the mildest: the organization *could* adapt but its standard procedures keep reproducing yesterday's answers — airlines after deregulation kept the route, pricing, and staffing formulas of the regulated era for years. The cure is changing what gets measured and who is hired; the attack is simply moving where the routine gives wrong answers.

**Inertia by culture** is deeper: adaptation threatens identity, status hierarchies, and internal coalitions. Engineering-led cultures dismiss design threats; sales-led cultures dismiss self-serve. Renewal requires simplification first — killing the overgrowth of units, initiatives, and committees in which the old culture lives — then breaking the political structure, then rebuilding. Leaders who skip to "rebuilding" with a new slogan change nothing.

**Inertia by proxy** is the subtle one: the incumbent is not asleep — it is *rationally* unresponsive because its profits ride on its customers' inertia. Banks paid low deposit rates while money-market funds grew because most depositors didn't move, and repricing for everyone to retain the few who did would have destroyed margin. The attack: make switching trivial and visible — one-click data migration, automatic import, side-by-side statements. When the customers' inertia breaks, the incumbent's position collapses quickly and it has no practiced response, because its "strategy" was the inertia itself.

## Entropy

Entropy is drift, not resistance: absent active management, organizations blur. Product lines proliferate and overlap; prices drift toward undisciplined discounts; cross-subsidies appear that nobody chose; ownership fuzzes. GM's brands — once a clean price-quality ladder from Chevrolet to Cadillac — drifted over decades into overlapping offerings that competed with each other and stood for nothing.

Entropy matters to strategists for two reasons: weeding it from your own garden is valuable work even with no competitor in sight, and a rival's entropy is a map of your opportunity.

**Entropy audit (quarterly or annual):**

1. Plot every product/plan/SKU by price against the customer need it serves. Overlaps are entropy; so are gaps everyone assumed someone owned.
2. Trace margin by offering. Unchosen cross-subsidies — profitable line A quietly funding zombie line B — get a decision: re-price, kill, or *choose* the subsidy explicitly.
3. List the discounts, exceptions, and custom deals added in the last two years. Each was locally rational; ask what the set does to the price ladder.
4. Re-draw the intended structure (clean ladder, named segments, one owner per line) and schedule the cuts.

The test for entropy is the *no-competition test*: if these blurred lines and leaky prices would still be wrong with zero competitors, the problem is entropy, and the fix is housekeeping, not repositioning.

## Attacker Playbooks

**Playbook A — Margin shadow.** Exploit an incumbent defending legacy margins. (1) Identify the revenue line they cannot cannibalize — seat licenses, services attach, transaction fees. (2) Configure your economics so following you destroys that line: usage-based pricing against per-seat, software against their services revenue. (3) Take the customers they rationally sacrifice first (small, price-sensitive, modern-stack), then move up. Requirement: your cost structure must be *structurally* lower, not VC-subsidized — a subsidy shadow evaporates. Risk: an incumbent with a board-level crisis may burn the boats and follow anyway; watch for leadership change as the signal.

**Playbook B — Wave rider.** Pick the wave with the guideposts, then commit with a design-type strategy configured for the attractor state: every piece — pricing, architecture, hiring, channel — presupposing the new world, with no hedge dragging the old one along. Set a proximate-objective ladder (resolve ambiguity in weeks, capability in quarters) rather than a five-year vision. Risk is timing: size the bet to survive the wave arriving two years late.

**Playbook C — Proxy breaker.** Attack the customer inertia that shields the incumbent. Make migration the product: importers, parallel-run modes, switching concierges, contract buyouts. Aim at moments when inertia naturally breaks — renewals, audits, platform deprecations, a champion changing jobs — and instrument them. Risk: switching subsidies attract deal-shoppers; qualify for fit, not just willingness to leave.

## Notes for Defenders

If you are the incumbent: run the guideposts against yourself annually; diagnose which inertia you have before launching a "transformation" (the fixes are different and culture-stage fixes take years you must start now); weed entropy on a calendar, not when crisis forces it; and when a wave is real, judge your response by what it does to the attacker's economics, not by how well it protects this year's margin — the margin you are defending is often the door you are holding open.

# Writing the Kernel

## Table of Contents

- [What the Kernel Is](#what-the-kernel-is)
- [Diagnosis Craft](#diagnosis-craft)
- [Formulating the Guiding Policy](#formulating-the-guiding-policy)
- [Designing Coherent Actions](#designing-coherent-actions)
- [The Kernel Template](#the-kernel-template)
- [Worked Example 1: Seed-Stage Startup](#worked-example-1-seed-stage-startup)
- [Worked Example 2: Established Product](#worked-example-2-established-product)
- [When Is a Kernel Done](#when-is-a-kernel-done)

## What the Kernel Is

The kernel is the minimum viable structure of a strategy: a **diagnosis** that defines the nature of the challenge, a **guiding policy** that commits to an overall approach for dealing with it, and a set of **coherent actions** that carry the policy out. Everything else in a strategy document — market sizing, vision statements, financial projections — is either input to the kernel or decoration around it.

The kernel deliberately excludes things most strategy documents lead with:

| Common plan artifact | What it actually is | Kernel replacement |
|---------------------|--------------------|--------------------|
| Vision statement | A description of a desired future | Diagnosis of what stands between you and any future |
| Mission and values | Identity and conduct norms | Nothing — they are fine, but they are not strategy |
| Goals and targets ("$10M ARR") | Ambitions; outputs of strategy | Guiding policy: the approach that could produce them |
| List of initiatives | Department wish lists | Coherent actions that reinforce one another |
| SWOT grid | Raw material | A judgment about which item on the grid is *the* challenge |

A kernel fits on one page. If it does not, you have not finished choosing.

## Diagnosis Craft

The diagnosis is the most skipped and most valuable element. It is a judgment — a simplification of messy reality that names the critical challenge and, implicitly, what kind of situation you are in. Get it wrong and everything downstream is coordinated effort aimed at the wrong target.

### Finding the critical challenge

1. **Collect the raw mess.** List every problem, threat, complaint, and stalled ambition: churn numbers, lost-deal notes, competitor moves, team frustrations. Do not filter yet. Aim for 15-30 items.
2. **Cluster into candidate challenges.** Group items that share a cause. "Sales cycle lengthening," "champions ghosting," and "more stakeholders per deal" might all cluster into "our buyer changed."
3. **Apply the unlock test.** For each candidate ask: *if this were solved, how much of the rest of the list gets easier?* The critical challenge is upstream of many symptoms.
4. **Apply the addressability test.** Ask: *can we act on this with resources we have or can realistically get?* "The macro economy" fails; "our onboarding loses technical buyers" passes.
5. **Choose one.** The candidate scoring highest on unlock × addressability is your critical challenge — the crux. Naming two is allowed only if one is clearly sequenced behind the other.

### Simplification and the courage to judge

A diagnosis is not a list of facts; it is a claim about which facts matter. "We have 14 problems" is an inventory. "We are a chain-link system stuck at the activation link" is a diagnosis. The simplification feels risky — you are discarding real complexity — but an un-simplified situation cannot be acted on. Write the diagnosis as one falsifiable paragraph, not a slide of bullets.

### Diagnosis by analogy

Experienced strategists diagnose by pattern-matching the situation to known structures. Useful patterns:

| Pattern | Signature | What it implies |
|---------|-----------|----------------|
| Chain-link stuck | Several functions adequate, one weak; global metrics frozen | Fix the weakest link first; ignore global metrics meanwhile |
| Wave of change | Cost structures or rules shifting industry-wide | Position for the attractor state; exploit incumbent inertia |
| Entropy / blur | Overlapping products, drifting prices, fuzzy ownership | Clean house before seeking new advantage |
| Strength-on-strength | You compete head-on where the rival is strongest | Re-segment; find ground where their strength is irrelevant |
| Threshold shortfall | Effort spread thin; nothing reaches visible results | Concentrate; accept being absent elsewhere |

### Tests of a good diagnosis

- Names a cause or structure, not a symptom ("activation is broken," not "growth is slow")
- Falsifiable — specific enough that evidence could prove it wrong
- An informed skeptic would accept that the facts support it
- Points toward action without dictating it
- One paragraph, plain language, no fluff

## Formulating the Guiding Policy

The guiding policy is the overall approach for overcoming the diagnosed obstacles. It is not a goal (an outcome you want) and not an action (a step you will take). It is a method — guardrails that rule out vast realms of possible action and channel effort toward your sources of power: leverage, asymmetric advantage, a wave you can ride, a rival's inertia.

**Drafting procedure:**

1. Write three to five candidate policies in this form: *"We will [approach] by [where/how we concentrate], because [the asymmetry or leverage that makes it work for us specifically]."*
2. For each candidate, list at least three significant things it **rules out**. If you cannot, the candidate is a platitude — discard it.
3. Check each against the diagnosis: does it actually address the named obstacle, or just sound strategic near it?
4. Pick one. Two guiding policies means you have not chosen.

**Tests of a good guiding policy:**

- Rules out real options people currently want to pursue
- Exploits a named asymmetry — it would be a *bad* policy for your nearest competitor
- Short enough to repeat in meetings from memory
- Stable for quarters, not days — actions change faster than policy

## Designing Coherent Actions

Actions are where strategy becomes visible — and where most documents collapse into a list of independent department initiatives. Coherence means the actions are coordinated: each one makes the others more effective, and none works against another.

**Design steps:**

1. **Derive, don't collect.** Generate actions only from the guiding policy. Do not import the existing roadmap and relabel it.
2. **Run the coherence check.** For each pair of actions ask: does A make B easier, harder, or neither? A strategy whose actions are all "neither" is a list; any "harder" pair must be resolved now, not discovered in Q3.
3. **Back each action with resources.** Owner, people, budget, start date, done-test. An action nobody is staffed for is a hope.
4. **Write the stop-doing list.** Coherent action includes withdrawal: name the projects, segments, or features being stopped to fund the strategy. If nothing stops, nothing was chosen.
5. **Make the first step proximate.** Something concrete starts within two weeks. Distant-future actions are goals wearing costumes.

## The Kernel Template

```
KERNEL: [name / date / author]

DIAGNOSIS (one paragraph)
The critical challenge is [cause/structure, not symptom].
Evidence: [2-4 facts that support it].
This is a [pattern/analogy] situation.
What would prove this wrong: [signal].

GUIDING POLICY (one or two sentences)
We will [approach] by [concentration], because [our asymmetry].
Therefore we will NOT: [3+ ruled-out options].

COHERENT ACTIONS (3-5, each resourced)
1. [Action] — owner, resources, start, done-test, reinforces #__
2. ...
STOP DOING: [projects/segments/features being withdrawn]

REVIEW: re-test diagnosis on [date / metric trigger].
```

## Worked Example 1: Seed-Stage Startup

**Situation:** Eight-person startup selling an AI code-review tool. $35K MRR, flat for five months. Self-serve signups convert at 9%; the team is split across building IDE plugins, a GitHub app, and an enterprise pilot. Two competitors are better funded.

**Diagnosis:** "Growth is flat" is the symptom. The cluster analysis shows: trials stall before the tool sees a real pull request; setup requires CI changes most users abandon; the enterprise pilot consumes 40% of engineering for one logo. The critical challenge: **time-to-first-value is ~2 days in a market where rivals demo value in minutes — and our effort is spread across three motions, none past the visibility threshold.** Pattern: threshold shortfall plus a weak activation link.

**Guiding policy:** *Win the GitHub-native mid-size team by being the only reviewer that shows a high-quality review on the customer's own code within 10 minutes of install, concentrating everything on that single motion.* Therefore we will NOT: pursue enterprise pilots this year, build IDE plugins, or support GitLab/Bitbucket.

**Coherent actions:**

1. Rebuild onboarding to run on a repo's last 20 merged PRs at install — no CI changes (2 engineers, starts Monday; done when median time-to-first-review < 10 min)
2. End the enterprise pilot; refund and refer (founder, this week) — frees the 40% that funds action 1
3. Retarget all marketing to "first review in 10 minutes," with live public benchmark repos (1 marketer, 2 weeks)
4. Instrument the activation funnel install → first review → first comment accepted (1 engineer, 1 week) — the lab for testing the diagnosis

Each action reinforces the others: the pilot's end staffs the rebuild; instrumentation proves or kills the diagnosis; marketing's promise is the product's new behavior.

## Worked Example 2: Established Product

**Situation:** Twelve-year-old field-service management platform, $28M ARR, serving HVAC, plumbing, landscaping, and cleaning companies. Renewals slipping (NRR 96%); a vertical-only HVAC rival wins on "built for HVAC" despite fewer features. Three pricing plans overlap; the roadmap is a union of the four industries' requests.

**Diagnosis:** Not "the rival is cheaper" — win/loss notes show price is rarely decisive. Twelve years of serving four verticals created **entropy and below-threshold quality everywhere**: the product is 70% right for each industry while the rival is 95% right for one. Each vertical's requests dilute the others. Pattern: entropy plus strength-on-strength against a focused attacker.

**Guiding policy:** *Re-concentrate as the system of record for mechanical trades (HVAC + plumbing), matching the vertical rival's fit while exploiting our one real asymmetry — ten years of job-cost data — to ship benchmarking no startup can copy.* Therefore we will NOT: build for landscaping/cleaning beyond maintenance mode, chase feature parity horizontally, or discount to save renewals.

**Coherent actions:**

1. Split the roadmap: 80% of engineering to mechanical-trades workflows; landscaping/cleaning enter maintenance mode with a 12-month support promise (VP Product, this quarter)
2. Ship job-cost benchmarking ("your margin vs. 4,000 mechanical contractors") as the renewal anchor (data team, 2 quarters; done at 30% renewal-conversation usage)
3. Collapse three overlapping plans into one mechanical-trades ladder; grandfather others (pricing lead, 6 weeks)
4. Retrain sales on a "built for mechanical trades" narrative with benchmark proof (sales enablement, parallel with 2)

The stop-doing list is the strategy: maintenance mode funds the concentration, and the data asymmetry — not nostalgia for breadth — is what the rival cannot follow.

## When Is a Kernel Done

- Diagnosis: one falsifiable paragraph a skeptic would sign
- Guiding policy: one approach, three-plus ruled-out options, anchored in a named asymmetry
- Actions: 3-5, mutually reinforcing, each with owner/resources/date/done-test
- Stop-doing list exists and actually frees the resources the actions need
- The whole kernel fits on one page and can be explained aloud in five minutes
- A review trigger is set — date or metric — at which the diagnosis gets re-tested

If the kernel passes all six, you have a strategy. If it fails any one, you have a draft — keep choosing.

# Sources of Power

## Table of Contents

- [Choosing a Source of Power](#choosing-a-source-of-power)
- [Leverage](#leverage)
- [Proximate Objectives](#proximate-objectives)
- [Chain-Link Systems](#chain-link-systems)
- [Design-Type Strategy](#design-type-strategy)
- [Focus](#focus)
- [Using Advantage](#using-advantage)
- [Stacking Sources](#stacking-sources)

## Choosing a Source of Power

A guiding policy without a source of power is a wish. Before formulating policy, identify which asymmetry the strategy will run on:

| Source | Core question | Reach for it when |
|--------|--------------|-------------------|
| Leverage | Where does a unit of effort buy the most result? | You can anticipate others' behavior or see a pivot point |
| Proximate objectives | What can we actually hit from here? | Ambiguity is high; teams stall on grand targets |
| Chain-link | Which link caps the whole system? | Effort everywhere, results nowhere |
| Design | What configuration of pieces wins? | Stakes are high and resources scarce |
| Focus | Which narrow target can we dominate? | Rivals serve everyone adequately, no one well |
| Advantage | What asymmetry do we already hold? | You have something rivals structurally cannot copy |

## Leverage

Strategic leverage comes from three multiplied ingredients: **anticipation**, a **pivot point**, and **concentration**. Each alone helps; together they let a small force move a large outcome.

**Anticipation.** Most behavior is predictable: customers keep their habits, incumbents defend their margins, platforms follow announced roadmaps, regulators follow published calendars. You do not need to forecast the future — you need to notice commitments already made. When a major OS vendor announces privacy changes 18 months out, every business built on third-party tracking will predictably scramble; a startup that builds the first-party-data alternative *before* the deadline harvests the scramble. Practice: keep a one-page register of "announced futures" — platform deprecations, regulation effective dates, rivals' public commitments — and ask which one your roadmap exploits.

**Pivot points.** A pivot point is a place where effort is amplified — where a small, feasible change releases a disproportionate result. Signatures of a pivot point: a constraint shared by all rivals that you alone can relax; a moment of peak user emotion (first run, failure, renewal) that nobody has designed; an imbalance between how much something matters to customers and how little attention it gets. Finding them is empirical: walk the customer journey and rank each step by (impact if 10x better) ÷ (cost to make it 10x better).

**Concentration.** Effects become visible only past a threshold. Marketing in five channels at 20% intensity each typically produces nothing measurable in any of them; one channel at 100% breaks through, and the visible win compounds — it attracts talent, references, and belief. Concentration is painful precisely because it makes you absent elsewhere; that pain is the cost of crossing the threshold. Rule of thumb for early-stage products: if you cannot name the segment where you are *over*-investing relative to its current size, you are spread below threshold everywhere.

**When to use:** whenever you can know or decide something rivals haven't — leverage is the default source of power for resource-poor attackers.

## Proximate Objectives

A proximate objective is a target close enough that the team can see how to hit it. Leaders who hand down objectives as hard to reach as the original challenge ("become the category leader") have not done their job; resolving ambiguity into feasible targets *is* the job.

**Calibrate distance to ambiguity:**

| Ambiguity level | Situation | Right objective distance | Example |
|-----------------|-----------|--------------------------|---------|
| Low | Stable market, known playbook | 12-month outcome targets | "Grow EU self-serve revenue 40%" |
| Medium | Known direction, unknown mechanics | One-quarter capability targets | "Stand up a working PLG funnel with 3 instrumented cohorts" |
| High | New market, new tech, shifting rules | 2-6 week ambiguity-resolving targets | "Run 15 problem interviews; decide wedge by March 15" |

**Deciding the ambiguity away.** When the Surveyor program could not design a Moon lander because no one knew the lunar surface, a JPL engineer wrote a specification — firm enough to land on, specific slopes and granularity — and the program designed against it. The spec was a judgment, not a fact, but it converted an undesignable problem into an engineering problem. Product equivalent: when the team stalls on unknowables ("what will enterprise buyers require?"), *write the assumption down as a design spec*, date it, and build against it. Revise the spec when evidence arrives; never stall waiting for certainty.

**Writing a proximate objective:** one owner; a done-test a outsider could verify; a deadline inside one planning horizon; and the team's honest answer to "can you see how?" is yes. Cascade them: each accomplished proximate objective creates new capabilities, which bring previously blue-sky targets into proximate range — strategy as a ladder, not a leap.

**When to use:** always, as the bridge from policy to action — and especially when smart teams are stalled, because stalling usually means the objective is too far away, not the team too weak.

## Chain-Link Systems

A system is chain-linked when overall performance is capped by its weakest link — excellence in one stage adds nothing until the others match. The Challenger was lost to one O-ring. A product funnel is a chain: acquisition → activation → retention → expansion; a 10x improvement in acquisition poured into 15% activation is mostly waste.

**Diagnosing a chain-link situation:**

1. Map the links — the stages where value is created or lost (funnel stages, or the quality chain: data → model → UX → trust).
2. Set a "good enough" threshold per link, benchmarked against the best rival or user expectation.
3. Measure each link against its threshold. A chain-link diagnosis holds when one or two links sit far below threshold while others are at or above it.
4. Confirm the cap: improvements in strong links haven't moved the global metric. That is the signature.

**Why chain-link systems get stuck:** fixing one link shows no system-level result (the next weak link now caps it), so the effort looks wasted and gets abandoned. Escaping requires a leader who takes responsibility for the *whole* chain, fixes links one at a time with slack resources, and refuses to judge progress by global metrics until the last weak link is repaired. Tell the team explicitly: "Activation work will not move revenue this quarter — it removes the cap so that next quarter's acquisition work can."

**Excellence as a moat:** the same logic in reverse. When every link is matched and mutually adapted — IKEA's in-house flat-pack design, catalog, and out-of-town warehouse showrooms each presuppose the others — a rival copying any single link gains nothing, and copying all of them means becoming a different company. Matched chains are among the strongest isolating mechanisms available.

**When to use:** when effort is everywhere and results are nowhere — and as a build target when you want advantage rivals cannot cherry-pick.

## Design-Type Strategy

Some strategies are choices among known positions; the most powerful are *designs* — premeditated configurations of resources and actions, like designing an aircraft rather than picking one from a catalog. Hannibal's victory at Cannae was not "fight harder"; it was a designed sequence — feigned retreat, enveloping cavalry, anticipation of Roman aggression — every piece presupposing the others.

**The three marks of design:** premeditation (worked out in advance, not emergent improvisation), anticipation (built on others' predicted behavior), and coordination (parts configured to reinforce each other, accepting trade-offs a menu-chooser would refuse).

**The performance/flexibility trade-off.** Tight integration extracts maximum performance from limited resources but resists change; loose, modular configurations sacrifice peak performance for adaptability. Choose tight design when stakes are high, resources are scarce, and the competitive window is now — a vertical AI product owning data pipeline, fine-tuned model, and workflow UI will beat an assembled API stack on quality, but will re-platform slower when models leap. Choose modularity when rich in resources or when uncertainty dominates.

**When to use:** high-stakes plays where you must beat better-resourced rivals — design is how the weak beat the strong, and why second-rate strategies suffice for those with overwhelming advantage.

## Focus

Focus is a coordinated set of policies aimed at a narrow target, producing power that rivals serving everyone cannot match without wrecking their own economics. Crown Cork & Seal prospered in the "commodity" can business by configuring everything — plant location, spare capacity, technical service — around short runs and rush orders for smaller customers, and earned pricing power where larger rivals saw none.

**Application discipline:** pick the segment where the incumbent's strengths are irrelevant or self-blocking; configure multiple policies (product, pricing, support, distribution) on it simultaneously — focus is the *coordination*, not just the narrowing; and verify the segment either values you enough to pay or leads somewhere larger. A startup "focused" on a segment it serves with the same generic product is narrow, not focused.

## Using Advantage

Advantage is rooted in asymmetry — a difference between you and rivals that translates into lower cost or higher willingness-to-pay. Two disciplines:

**Advantage is positional, not general.** No company is simply "better"; it is advantaged in some contests and disadvantaged in others. And an advantage matters only at the *point of contention*: nobody cares about your costs except where you actually compete for a customer's decision. Strategy means steering competition toward the contests where your asymmetry decides.

**An advantage must be used to be valuable.** Like a silver mine, an advantage you cannot extract more value from is sterile. Four ways to work it:

1. **Deepen it** — widen the gap between value delivered and cost in your existing wedge (the default, most neglected move).
2. **Broaden it** — carry the underlying asymmetry to adjacent fields: proprietary job-cost data extends from dispatch software into benchmarking and insurance pricing; a beloved character franchise extends from films into parks and merchandise.
3. **Create demand** for what you are uniquely good at — grow the segment where your asymmetry decides.
4. **Strengthen isolating mechanisms** — the barriers that stop imitation from eroding returns: patents, brand and reputation, network effects, switching costs, tacit team know-how, exclusive relationships. If returns are good and undefended, your strategy's clock is running.

**When to use:** whenever you already hold an asymmetry — and as a test of every proposed advantage: if it changes neither cost nor willingness-to-pay at a real point of contention, it is decoration.

## Stacking Sources

Real strategies stack two or three sources. The startup in [kernel.md](kernel.md) stacks concentration (one motion), a pivot point (time-to-first-value), and anticipation (rivals' enterprise distraction). The established platform stacks focus (mechanical trades), advantage (proprietary data), and de-entropy. When reviewing a strategy, name its sources of power explicitly; if you cannot name any, the strategy is effort dressed as insight.