Strategy Clarity

Overview

Strategy clarity is the process of defining a coordinated set of choices that uniquely position an organization to win. This skill composes four frameworks into a pipeline: Wardley evolution mapping builds situational awareness, Lafley's cascade makes the choices, Helmer's 7 Powers stress-tests defensibility, and Working Backwards translates intent into execution. The Lafley cascade is the default and core process; the others compose around it based on what's already decided.

Decision State

Strategic clarity is not a single framework — it is a pipeline of frameworks, each handling a different phase. Your entry point depends on what's already decided:

What's already decided determines where you start:

1. Nothing — greenfield, pivot, or "we don't know where to play" Start with evolution mapping to build situational awareness before choosing. → Read references/evolution-mapping.md, then return here for the Cascade.

2. Where to play is clear, how to win isn't Start with the Strategic Choice Cascade below (Step 3: How to Win).

3. Strategy is chosen, unsure if it's defensible Stress-test the position for durable power sources. → Read references/seven-powers-audit.md.

4. Strategy is validated, need execution machinery Translate strategic intent into customer-facing artifacts. → Read references/working-backwards-execution.md.

Each phase validates the previous one's output. If the Lafley cascade produces a vague position ("be the best platform"), loop back to evolution mapping. If 7 Powers finds no defensible power source, loop back to How to Win.

Organizational commitment. This skill covers strategic choice, not organizational adoption. Securing institutional commitment for a strategy — coalition-building, guiding policy, coherent action — is a distinct challenge not covered here. (See: Rumelt, Good Strategy Bad Strategy; Kotter, Leading Change.)

Guiding Principles

Principle 1: Strategy is Choice (Source: Lafley, Playing to Win)

Strategy is not a goal or a vision; it is a coordinated set of choices that uniquely positions the firm. If you haven't made a choice about where not to play, you don't have a strategy.

Principle 2: The Monopoly Aim (Source: Thiel, Zero to One)

Every successful business is a monopoly by solving a unique problem. Competition is a destructive force that competes away profits. Your strategy must aim for 0-to-1 vertical progress, not 1-to-n horizontal copying.

Principle 3: The Bill Gates Line (Source: Stratechery, "The Bill Gates Line")

A true platform's value is defined by the economic value created by third parties exceeding the value of the platform itself. Strategic clarity requires knowing if you are an Aggregator (owning the user) or a Platform (empowering the ecosystem).

Principle 4: Work Backwards from the Customer (Source: Bryar, Working Backwards)

Strategy is not what you can build, but what the customer needs you to build. All strategic logic must be validated by a "Working Backwards" PR/FAQ that proves the future state is compelling.

Principle 5: The Secret (Source: Thiel, Zero to One)

Great companies are built on a "secret"—a truth that very few people agree with. Strategic clarity requires identifying this contrarian insight and building a moat around it.

When to Use This Skill

• When a team has "too many priorities" and needs to decide where not to play.
• When launching a new product category or entering a new market.
• When evaluating if a business model is structurally an Aggregator or a Platform.
• When a strategic plan feels like a "list of goals" rather than a "set of choices."

When NOT to Use This Skill

• For routine tactical execution within an already clear strategic framework.
• For purely operational efficiency tasks (unless the strategy is "Cost Leadership").

Core Process

Step 1: Define the Winning Aspiration

Identify the core purpose of the enterprise and the specific "Winning" state. (Source: Lafley, Ch. 2) 1. The Goal: What does winning look like in this specific context? 2. The Metric: How will we know we've achieved it (e.g., monopoly share, flywheel velocity)?

Step 2: Set the "Where to Play" (WTP) Boundary

Define the specific field of play. (Source: Lafley, Ch. 3) 1. Geography: Which regions? 2. Product: Which categories? 3. Consumer: Which segments (JTBD-driven)? 4. Channel: Which distribution paths?

Step 3: Determine "How to Win" (HTW)

Define the unique value proposition. (Source: Lafley, Ch. 4) 1. Value Type: Are we a Cost Leader or a Differentiator? 2. The Moat: Are we building a moat via Proprietary Tech, Network Effects, or Economies of Scale? (Source: Thiel, Ch. 5)

Step 4: Map the Capability System

Identify the 3-5 activities that must be performed at a high level to execute the HTW. (Source: Lafley, Ch. 5) 1. Reinforcing Loops: How do these capabilities reinforce each other (The Flywheel)? 2. The Gap: What capabilities are we currently missing?

Step 5: Test the Logic (Reverse Engineering)

Ask: "What must be true about the market, customers, and competitors for this strategy to be a great idea?" (Source: Lafley, Ch. 7)

Frameworks & Models

The Strategic Choice Cascade (Source: Lafley, Playing to Win)

1. Winning Aspiration: The guiding purpose. 2. Where to Play: The field. 3. How to Win: The value prop. 4. Core Capabilities: The activities required. 5. Management Systems: The measurement and support structures.

The Monopoly Audit (Source: Thiel, Zero to One)

1. Proprietary Technology: Must be 10x better than the nearest substitute. 2. Network Effects: Does the product get more useful as more people use it? 3. Economies of Scale: Does the business get stronger as it gets bigger? 4. Branding: Is there a strong, unique identity?

Cross-Skill Invocations

• REQUIRED SUB-SKILL: non-fiction-precision — Strategy must be communicated with absolute clarity (Pyramid Principle).
• RECOMMENDED SUB-SKILL: mental-model-library — Use first principles and second-order thinking to validate strategic "Secrets."
• RECOMMENDED SUB-SKILL: devils-advocate — Stress-test the "What must be true" assumptions.

Common Mistakes

1. Strategic Blindness: Treating a "vision" or "goals" as a strategy without making hard choices. (Source: Lafley, Ch. 1) 2. The 1% Trap: Assuming a small share of a huge market is a strategy. (Source: Thiel, Ch. 13) 3. Indefinite Optimism: Expecting the future to work out without a definite plan. (Source: Thiel, Ch. 6) 4. Platform Confusion: Mistaking an Aggregator (owning the customer) for a Platform (empowering suppliers). (Source: Stratechery, "The Bill Gates Line")

Gotchas

• Counter-Positioning requires self-harm. A position is only Counter-Positioned (Helmer) if the incumbent's rational response would cannibalize their core business. If they can respond without self-harm, you don't have Counter-Positioning — you have a feature lead with a countdown timer. (Source: Helmer, 7 Powers, Ch. 3)
• Evolution stage applies to components, not products. A product can contain components at Genesis (novel AI model), Custom (proprietary data pipeline), and Commodity (cloud hosting) simultaneously. Map each component's evolution separately when assessing Where to Play. (Source: Wardley, Wardley Maps, Ch. 2-3)
• Working Backwards PR/FAQ is not a PRD. If the press release reads like a requirements document, the customer-empathy step was skipped. The PR must be written as if a journalist is explaining why a customer cares. (Source: Bryar, Working Backwards, Ch. 4)
• "Where to Play" without evolution awareness is a snapshot. Markets move. A Where to Play choice grounded only in current structure will miss value migration. Wardley's evolution axis shows where components are heading, not just where they are. (Source: Wardley, Wardley Maps, Ch. 4)
• Vague positions can't be stress-tested. If the Lafley cascade output is "be the leading platform for X," it's too vague for 7 Powers analysis. A testable position names the specific mechanism: "own the demand aggregation layer by..." Loop back to How to Win.

Diagnostic Checklist

• [ ] Have we explicitly chosen where NOT to play?
• [ ] Is the "Where to Play" informed by component evolution, not just current market structure?
• [ ] Is the "How to Win" specific enough to name the mechanism (not just "differentiation")?
• [ ] Can we identify at least one of Helmer's 7 Powers that this position could build?
• [ ] Has the position been validated with a "What must be true" reverse-logic test?
• [ ] Can we state the contrarian insight ("Secret") this strategy is built on?
• [ ] Is there a clear path from strategy to execution artifact (PR/FAQ or equivalent)?

Sources

• Lafley & Martin, Playing to Win, Ch. 1-5, 7 — Strategy Cascade, WTP/HTW.
• Thiel, Zero to One, Ch. 3, 5, 6, 8, 13 — Monopoly theory, Secrets, Definite Optimism.
• Bryar & Carr, Working Backwards, Ch. 1 — Flywheel, Customer Obsession.
• Bryar & Carr, Working Backwards, Ch. 4-5 — PR/FAQ, Mechanisms, Controllable Inputs.
• Helmer, 7 Powers, Ch. 1-9 — Power types, barriers, dynamics.
• Wardley, Wardley Maps, Ch. 2-5 — Evolution, Value Chains, Situational Awareness.
• Rumelt, Good Strategy Bad Strategy — Kernel of strategy, organizational commitment.
• Stratechery, "The Bill Gates Line" & "Aggregation Theory" — Platform vs Aggregator dynamics.

Evolution Mapping

Use this when "Where to Play" is unclear. This procedure maps the evolution stage of value chain components to identify where strategic opportunity exists.

Procedure

Step 1: List the Value Chain

Start from the user need and work downward to underlying components. Identify 5-15 components that connect the user need to the capabilities required to serve it.

• Begin with the anchor: what does the user need?
• Work down: what activities, data, services, and infrastructure enable that need?
• Each component should be a noun (a thing that exists), not a verb (an activity you perform).
• Stop at 15. If the chain is longer, merge lower-level components into groups.

Output: An ordered list of components, from user-visible to infrastructure.

Step 2: Assess Evolution Stage

For each component, assign one of four evolution stages:

Assess based on the market reality of the component, not your organization's internal implementation. Ask four questions per component:

1. How widely available is this component across the industry? 2. How predictable is its behavior and performance? 3. Are there published standards or open-source implementations? 4. How many providers compete to deliver it?

Output: Each component tagged with its evolution stage.

Step 3: Identify Evolution Mismatches (Opportunities)

Scan the map for components sitting further left (Genesis/Custom) than adjacent components or user expectations suggest they should be.

These mismatches signal strategic opportunity:

• A Custom component feeding into a Product-stage service means someone will productize it. You can be that someone.
• A Genesis component that multiple Product-stage offerings depend on is an emerging platform play.
• A component that users treat as solved (expect Commodity behavior) but that is actually Custom indicates a gap the market will pay to close.

Output: A short list of 1-3 opportunity components with a one-sentence rationale for each.

Step 4: Identify Inertia Risks

Scan for components moving right (toward Commodity) that your organization treats as differentiators.

These are strategic risks:

• If competitors are commoditizing a component you invest heavily in, you are spending resources fighting evolutionary flow.
• If an open-source or utility version of your "differentiator" exists, the market has already moved past you.
• If your custom-built component has three or more SaaS alternatives, it is Product-stage or later regardless of your internal narrative.

Output: A short list of 0-3 risk components with a one-sentence assessment of each.

Step 5: Formulate a Where to Play Hypothesis

Synthesize Steps 3 and 4 into a specific hypothesis:

• Geography or segment: Which customer segment or market experiences the pain from evolution mismatches most acutely?
• Component layer: Which specific component(s) will you own or advance?
• Directional bet: Are you accelerating a component's evolution (pushing it right) or capturing value during a transition?

State the hypothesis in one to two sentences. Include the evolution-based rationale — why the dynamics favor this position.

Output: A Where to Play hypothesis ready for the Lafley Cascade (return to strategy-clarity SKILL.md, Step 2 of the Strategic Choice Cascade).

Gotchas

• Evolution is about the component, not your opinion of it. A database is Commodity even if yours is custom-built — you are fighting the evolutionary flow. Assess what the market does, not what you do.
• Do not map more than 15 components. You are looking for strategic signal, not cartographic completeness. If you need more than 15, you are mapping too granularly — merge related components.
• Do not skip the risk scan (Step 4). Teams naturally gravitate toward opportunity identification and skip the uncomfortable question of what they are over-investing in. Both sides of the map matter.

Validation

The output is a specific Where to Play hypothesis (geography, segment, component layer) with an evolution-based rationale. If you cannot state why the evolution dynamics favor this position, the mapping is not done — return to Step 3 and look harder at the mismatches.

Sources

Wardley, Wardley Maps, Ch. 2-5 — Evolution, Value Chains, Situational Awareness.

Seven Powers Defensibility Audit

Use this to stress-test whether a chosen strategic position has a durable power source. A strategy without at least one power source is a plan to compete away profits.

Audit Procedure

For each of the seven powers below, apply the binary test. Answer YES or NO. Do not hedge. If the answer is "maybe" or "partially," the answer is NO.

---

1. Scale Economies

Question: Does unit cost decline meaningfully with volume in a way competitors cannot match without equivalent scale?

Binary test: Would a competitor operating at 1/10th your scale have materially higher unit costs for the same output?

• YES = You have Scale Economies as a power source.
• NO = Your cost structure is replicable at smaller scale.

---

2. Network Economies

Question: Does product value increase with user count in a way that creates a self-reinforcing flywheel?

Binary test: Would a new entrant with zero users offer materially less value to their first customer than you offer to yours?

• YES = You have Network Economies as a power source.
• NO = Your product value is independent of user base size.

---

3. Counter-Positioning

Question: Would the incumbent's rational response to your strategy cannibalize their existing business model?

Binary test: Can the incumbent copy your approach without harming their core revenue stream?

• YES (they can copy without self-harm) = You do NOT have Counter-Positioning.
• NO (copying would damage them) = You have Counter-Positioning as a power source.

---

4. Switching Costs

Question: Do customers face material cost (financial, procedural, or relational) to switch away from your product?

Binary test: Could a customer switch to a competitor in under a week with no data loss or workflow disruption?

• YES (they can switch easily) = You do NOT have Switching Costs.
• NO (switching is costly or disruptive) = You have Switching Costs as a power source.

---

5. Branding

Question: Does the brand command a price premium or preference that persists even when competitors match on features?

Binary test: Would a customer choose you at a 20% price premium over an identical competing product?

• YES = You have Branding as a power source.
• NO = Your market position is feature-dependent, not brand-dependent.

---

6. Cornered Resource

Question: Do you have preferential access to a resource (talent, IP, regulatory license, data) that competitors cannot replicate?

Binary test: Could a well-funded competitor acquire the same resource within 2 years?

• YES (they could acquire it) = You do NOT have a Cornered Resource.
• NO (the resource is unavailable to them) = You have a Cornered Resource as a power source.

---

7. Process Power

Question: Does your organization have embedded processes that deliver superior outcomes and are opaque or hard to copy?

Binary test: Could a competitor replicate your operational advantage by hiring away 10 of your people?

• YES (hiring would transfer the advantage) = You do NOT have Process Power.
• NO (the advantage is systemic, not individual) = You have Process Power as a power source.

---

Scoring

Count the number of YES results (powers you hold).

• Zero powers: The position may be strategically attractive but it is not

defensible. Loop back to How to Win in the Lafley Cascade and identify a position where at least one power source exists.

• One power: Defensible. Identify which phase of the power's lifecycle you

are in and what sustains it.

• Two or more powers: Strong. Multiple barriers compound defensibility.

Gotchas

Process Power is easy to overlook. It is the hardest to identify and the hardest to copy. It is also the most common power source in non-tech businesses. Do not skip it because it seems less exciting than Network Economies.

Counter-Positioning has an expiry date. Once the incumbent's legacy business declines enough, the self-harm of responding decreases. Plan for what happens when Counter-Positioning erodes. If it is your only power source, you need a second one before the window closes.

Network Economies require critical mass. Before the threshold, you have negative power — the product is worse because too few people use it. Identify the critical mass number and your current distance from it.

Sources

• Helmer, 7 Powers: The Foundations of Business Strategy, Ch. 1-9 — Power

types, barriers, and dynamics.

Working Backwards Execution

Use this to translate a validated strategic position into a customer-facing execution artifact. The PR/FAQ forces you to articulate the strategy from the customer's perspective before building anything.

Procedure

Step 1: Write the Press Release

Write a one-page press release announcing the product, service, or initiative as if it already exists. The press release must answer five questions:

1. Who is the customer? Name the specific segment, not "everyone." 2. What is the problem? State the pain in the customer's language. 3. What is the solution? Describe what the customer gets, not what the team builds. 4. Why should the customer care? What changes in their life or work? 5. What does the customer do next? A concrete action — sign up, buy, switch.

Write it as if a journalist is explaining why this matters to a real person. If it reads like a product spec or internal memo, rewrite it.

Step 2: Write the FAQ

The FAQ has two sections. Both are mandatory.

External FAQ — Questions customers would ask:

• How much does it cost?
• How is this different from [existing alternative]?
• What do I have to give up or change to use this?
• When can I get it?

Write real questions, not softballs. If every answer is "yes, we handle that," the questions are too easy.

Internal FAQ — Questions leadership and engineering would ask:

• What does this cost to build and operate?
• What's the timeline to first customer?
• What existing system or commitment does this conflict with?
• What's the biggest technical risk?
• What assumption, if wrong, kills this?

The Internal FAQ is where strategic assumptions surface. Write it to expose risk, not to reassure.

Step 3: Identify the Controllable Inputs

List the leading indicators the team can directly influence. These become the operational metrics that drive execution.

A controllable input is something the team does, not something the market does.

• "Number of customer interviews per week" = controllable input.
• "Revenue growth" = output, not controllable.
• "Number of integrations shipped per sprint" = controllable input.
• "Market share" = output, not controllable.

Select 3-5 controllable inputs that, if moved consistently, produce the customer outcome described in the press release.

(Source: Bryar & Carr, Working Backwards, Ch. 5)

Step 4: Define the First Mechanism

A mechanism is a structural process that ensures the strategy executes without relying on individual heroics. "Good intentions don't work. Mechanisms do."

Define one mechanism that enforces execution of the most critical controllable input.

A mechanism has three properties:

1. It is structural, not behavioral. It is built into process or tooling. 2. It operates automatically. It does not depend on someone remembering. 3. It has a feedback loop. Deviation is visible and triggers correction.

Example: "Weekly metrics review where controllable inputs are plotted against targets, and any input below threshold generates a written correction plan due within 48 hours."

(Source: Bryar & Carr, Working Backwards, Ch. 1)

Step 5: Validate Against the Strategic Position

Check the press release against the Lafley Cascade choices (Where to Play, How to Win). Ask:

• Does the press release describe a customer outcome that requires the specific

Where to Play and How to Win choices already made?

• Could this press release describe a different strategy equally well?
• Does the How to Win choice appear as the reason the customer cares?

If the PR could describe any strategy, it is too generic. Rewrite until the strategic position is the reason the customer outcome exists.

Gotchas

The PR/FAQ is a thinking tool, not a communication tool. If stakeholders are wordsmithing the press release for external polish, the process has been hijacked. The goal is to force clarity of thought, not to produce publishable copy.

If the Internal FAQ doesn't surface at least one uncomfortable question about feasibility or cost, it's not honest enough. Go back and add the question the team is avoiding.

Mechanisms must be structural, not behavioral. "Engineers will review each other's code" is behavioral — it depends on willpower. "No code merges without automated test coverage above 80%" is structural — it enforces itself.

Sources

• Bryar & Carr, Working Backwards, Ch. 1, 4-5 — PR/FAQ process, Mechanisms,

Controllable Inputs.