Skip to content

existential-birds/beagle / plugins/beagle-analysis/skills/strategy-review

strategy-review

Verified

Use when reviewing, critiquing, or stress-testing an existing strategy document. Evaluates seven dimensions — diagnosis quality, guiding policy strength, action coherence, assumption exposure, falsifiability — with optional 7S, Five Forces, Balanced Scorecard, and Hoshin Kanri lenses. Triggers on: review my strategy, poke holes in this plan, what's weak here, strategy audit, red team this. Does NOT build strategy (use strategy-interview) or brainstorm project ideas (use brainstorm-beagle).

references/interview-lens-audit.md

View on GitHub
# Interview Lens Audit

Audit criteria for checking whether interview lens findings survived into the strategy draft. Use this during Step 3b when the strategy document or companion notes show evidence that landscape mapping, strategic choice cascade, or value innovation lenses were applied during the [strategy-interview](../../strategy-interview/SKILL.md) skill.

The audit is about **fidelity and impact** — did the lens findings make it into the draft, and did they actually sharpen the kernel? A lens finding that appears in the notes but vanishes from the draft is a red flag. A lens finding that appears in the draft but didn't change anything is decorative.

---

## 1. Landscape Mapping (Wardley)

### What to look for in the notes

Wardley-informed interview notes typically contain:
- A value chain or dependency structure (user need at the top, components underneath)
- Evolution stage assessments for key components (genesis, custom-built, product, commodity)
- Tension points: building custom what's becoming commodity, treating genesis as procurement, competitor further along the evolution curve
- Inertia patterns: attachment to a component whose evolution stage has shifted
- Value-capture dynamics: which layer of the chain captures margin, and whether that's shifting

### Audit checklist

Check each item against both the notes and the draft. A "present in notes, absent in draft" finding is the most important signal.

| Criterion | What to check | Dimension |
|-----------|--------------|-----------|
| **User need anchoring** | Does the diagnosis start from a clearly stated user need, or does it start from the company's internal perspective? Wardley mapping anchors everything to the user need at the top of the chain. | Dim 1 |
| **Value-chain / dependency structure** | Does the diagnosis identify which components the strategy depends on and how they relate? Not necessarily a formal map — but awareness of the dependency chain. | Dim 1 |
| **Evolution stage awareness** | Does the diagnosis distinguish between components at different evolution stages? Look for language about commoditization, maturity, or "table stakes" vs. novel/uncertain capabilities. | Dim 1 |
| **Control and dependency points** | Does the strategy identify which components it controls vs. depends on? A strategy built on a component controlled by someone else carries risk the document should acknowledge. | Dim 6 |
| **Value-capture or inertia insights** | Did the interview surface where margin sits in the chain, or where organizational inertia is masking a shift? Does the draft reflect these insights, or did it revert to conventional framing? | Dim 1, Dim 6 |
| **Diagnosis sharpening** | Did the landscape analysis actually change or sharpen the diagnosis — or was it acknowledged but left aside? A good test: does the diagnosis contain a claim that could only come from mapping the landscape (e.g., "we're building custom what has become commodity"), or does it read the same as it would without the mapping? | Dim 4 |

### Common drop patterns

These are the ways Wardley findings most often get lost between notes and draft:

- **Abstraction wash**: The notes contain specific evolution-stage findings ("our data pipeline is custom-built but three vendors now sell this as a product") but the draft abstracts them into generic competitive language ("we face increasing competitive pressure").
- **Inertia silence**: The notes identify organizational inertia around a commoditizing capability, but the draft treats the current approach as a strength rather than a liability.
- **Missing dependency risk**: The notes flag a critical dependency on a component controlled by another party, but the draft's assumption exposure doesn't mention it.
- **Value-chain flattening**: The notes describe a multi-layer value chain with different dynamics at each layer, but the draft collapses it into a single "our market" description.

---

## 2. Strategic Choice Cascade (Playing to Win)

### What to look for in the notes

Cascade-informed interview notes typically contain:
- A winning aspiration — concrete picture of what winning looks like
- Where-to-play choices — specific segments, geographies, or value-chain positions chosen (and excluded)
- How-to-win mechanism — the structural advantage, not just "better execution"
- Capability assessment — 3-5 reinforcing capabilities required, with gap identification
- Management systems — processes, metrics, and feedback loops to keep the strategy on track

### Audit checklist

| Criterion | What to check | Dimension |
|-----------|--------------|-----------|
| **Winning aspiration clarity** | Does the draft contain a concrete picture of success that two people would agree on, or has it softened into a generic vision statement? | Dim 7 |
| **Where-to-play specificity** | Does the guiding policy name specific segments *and* exclusions? If the cascade surfaced a narrow playing field, check whether the draft expanded it back to "everyone." | Dim 2 |
| **How-to-win mechanism** | Does the guiding policy name a structural advantage — not just "superior product" but the specific asymmetry? If the cascade identified why competitors can't copy the advantage, does that reasoning appear? | Dim 2 |
| **Capability gaps in assumptions** | Did capability gaps identified during the cascade appear in the assumption exposure or as caveats in the actions? Or were they silently assumed away? | Dim 6 |
| **Management systems in actions** | Did the cascade's management systems findings — measurement, reinforcement, drift prevention — make it into the coherent actions? This is the most commonly dropped cascade element. | Dim 3 |
| **Policy/action sharpening** | Did the cascade choices actually tighten the guiding policy and actions, or were they acknowledged in passing? Test: remove the cascade language — does the policy read differently? If not, the cascade was decorative. | Dim 4 |

### Common drop patterns

- **Aspiration inflation**: The cascade produced a specific, bounded winning aspiration, but the draft inflated it into a broad vision statement.
- **Exclusion erosion**: The where-to-play analysis excluded specific segments, but the draft hedges ("primarily mid-market, but we'll also serve enterprise when opportunities arise").
- **Capability optimism**: The cascade identified capability gaps, but the draft treats them as tasks rather than risks — "hire mobile team" instead of acknowledging a fundamental capability the org hasn't built.
- **Systems omission**: The most common drop. Management systems are almost always the weakest part of the cascade, and the first thing cut from the draft.

---

## 3. Value Innovation (Blue Ocean)

### What to look for in the notes

Blue Ocean-informed interview notes typically contain:
- A strategy canvas or convergence analysis — factors the industry competes on, with all players roughly similar
- ERRC moves — specific factors to eliminate, reduce, raise, or create
- Noncustomer tier analysis — who isn't buying and why
- A diagnosis reframe from "how to beat competitors" to "the competitive arena itself is the problem"

### Audit checklist

| Criterion | What to check | Dimension |
|-----------|--------------|-----------|
| **Strategy canvas / convergence recognition** | Does the diagnosis acknowledge competitive convergence — that all players compete on the same factors? Or did it revert to "we're behind on features"? | Dim 1 |
| **ERRC moves in actions** | Do the coherent actions reflect eliminate/reduce/raise/create moves — deliberately diverging from competitors? Or do they default to matching and incrementing? | Dim 3 |
| **Noncustomer awareness** | If noncustomer tiers were identified, does the strategy target them, or did the draft narrow back to existing customers? | Dim 2 |
| **Diagnosis reframe** | Did the diagnosis shift from competitive positioning ("we're losing share") to competitive convergence ("the category has converged and further investment in these factors produces declining returns")? This is the most important Blue Ocean contribution to the kernel. | Dim 1 |
| **Value-cost tradeoff** | Does the guiding policy break the value-cost tradeoff (simultaneously reducing cost in some areas and increasing value in others), or does it stay within the conventional differentiation-vs-cost frame? | Dim 2, Dim 4 |
| **Divergence from competitor matching** | Read the coherent actions as a whole: are they about catching up to competitors, or about going somewhere competitors aren't? If the Blue Ocean analysis surfaced a divergent path but the actions converge back, flag it. | Dim 3, Dim 4 |

### Common drop patterns

- **Convergence denial**: The notes document clear competitive convergence, but the draft frames the problem as "we need to execute better on the same dimensions" — reverting to a red ocean diagnosis.
- **ERRC flattening**: The notes contain specific eliminate/reduce/raise/create moves, but the draft turns them into conventional feature prioritization ("we'll focus on X and Y") without the deliberate elimination and reduction that makes the strategy distinctive.
- **Noncustomer retreat**: The notes identify a promising noncustomer tier, but the draft's playing field narrows back to the existing market — often because the existing market feels safer or more measurable.
- **Incremental creep**: The actions start divergent but accumulate "and also" items that pull the strategy back toward competitor matching. Check whether actions added after the Blue Ocean analysis dilute the ERRC moves.

---

## Reporting interview lens audit findings

Record each finding under the relevant dimension in the dimension ratings. In the Lens Findings section of the review output, use this format for the interview lens audit subsection:

```markdown
**Interview lens audit:**

- **[Lens name] — [Reflected / Partially reflected / Missing]**: [What survived, what was dropped or softened, and what was lost. If partially reflected, name the specific elements that made it and the ones that didn't.]
```

The most valuable finding is often the gap between the notes and the draft — the sharpest strategic thinking from the interview that got polished away during document writing. Name it specifically so the author can recover it.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall