existential-birds/beagle / plugins/beagle-analysis/skills/strategy-review
strategy-review
VerifiedUse 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 30.0 KB |
| references/interview-lens-audit.md | markdown | 10.1 KB |
| references/judge-artifact-schema.md | markdown | 29.8 KB |
| references/pressure-tests.md | markdown | 8.9 KB |
| references/review-dimensions.md | markdown | 21.8 KB |
| references/review-lenses.md | markdown | 17.4 KB |
| references/review-template.md | markdown | 9.0 KB |
references/review-dimensions.md
View on GitHub# Review Dimensions
Seven dimensions for evaluating strategy documents. Each dimension has criteria for each rating level, common failure patterns, and the kinds of pressure-test questions to apply.
The overall goal: find where the strategy could break — the gaps, unexamined risks, and failure paths that the author hasn't accounted for. A strategy that survives this review has a meaningfully better chance of surviving contact with reality.
---
## 1. Diagnosis Quality
**Core question:** Does the diagnosis name the actual challenge with enough specificity that you could imagine being wrong about it?
A diagnosis isn't a description of the situation — it's a *judgment* about what matters most. It picks from a complex reality and says "this is the thing." That act of picking is what makes it useful and what makes it testable.
### Rating criteria
**Strong**: Names a specific challenge. Uses the company's particular situation, not generic industry observations. You could argue against this diagnosis — it takes a position. Often uses analogy or identifies a structural pattern ("this is a classic disintermediation problem," "we're in the position Kodak was in when digital hit 5% market share").
**Adequate**: Identifies a real challenge but stays somewhat generic. Could apply to several companies in the same industry without modification. Correct but not sharp enough to generate a distinctive guiding policy.
**Weak**: Describes the situation without identifying what matters most. Lists multiple challenges without prioritizing. Uses language like "the market is changing" or "we face increasing competition" without specifying *how* or *why it matters for this company specifically*.
**Missing**: No diagnosis at all. The document jumps from context to goals or actions. The most common version: a SWOT analysis with no "therefore."
### Pressure-test questions
- Could a competitor read this diagnosis and say "yes, that's exactly our challenge too"? If so, it's not specific enough.
- Does the diagnosis identify *why now*? What changed that makes this challenge urgent or this opportunity available?
- Is there an unstated assumption about the external environment that, if wrong, would invalidate the diagnosis entirely?
- Does the diagnosis identify the *root* challenge, or a symptom? ("We're losing market share" is a symptom. "Our product architecture prevents us from serving the mobile-first workflow that 68% of inspections now use" is a root cause.)
- What would the diagnosis look like if the author's biggest fear were true? What if their most optimistic assumption were false?
### Common failure patterns
- **The comfortable diagnosis**: Identifies a challenge that the organization already knows how to solve, avoiding the harder truth that requires a different approach.
- **The diagnosis-by-data-dump**: Presents extensive market research and trend analysis but never synthesizes it into a judgment. The reader is left to figure out what it all means.
- **The inherited diagnosis**: Repeats the diagnosis from last year's strategy without checking whether the underlying situation has changed.
- **The consensus diagnosis**: So carefully worded to avoid offending any stakeholder that it says nothing specific. Usually produced by committee.
**Lens connection — Competitive Pressure Audit**: When the diagnosis addresses competitive dynamics, apply Five Forces thinking from `references/review-lenses.md`. Check whether the diagnosis accounts for all five forces (rivalry, new entrants, substitutes, supplier power, buyer power) or focuses narrowly on direct rivalry while ignoring structural pressures that could reshape the competitive environment. A diagnosis that says "we're losing to Competitor X" but doesn't consider substitution risk or eroding entry barriers has only seen part of the picture.
---
## 2. Guiding Policy Strength
**Core question:** Does the guiding policy make a real choice that rules things out — including things a reasonable person might choose?
A guiding policy that everyone agrees with hasn't decided anything. The value is in what it excludes. If a competitor could adopt the same policy verbatim without contradiction, it's not doing strategic work.
### Rating criteria
**Strong**: Makes a clear directional choice. Names what the organization will *not* do. The rejected alternatives are plausible — someone could reasonably argue for them. Exploits a specific asymmetry or pivot point. Short enough to remember.
**Adequate**: Makes a choice but the exclusions are implicit rather than stated. You can infer what's been ruled out but it hasn't been made explicit, which means different readers may interpret the scope differently.
**Weak**: Describes a desirable direction without excluding anything. Could be adopted by any company in the industry. Language like "focus on the customer," "drive innovation," "be the best" — these sound like policies but aren't, because they don't constrain decisions.
**Missing**: No guiding policy. The document has goals and actions but nothing connecting them — no principle that explains why *these* actions and not others.
### Pressure-test questions
- What does this policy *prevent* the organization from doing? Can the author name three specific initiatives or investments they would decline because of this policy?
- Is there a real alternative to this policy that a thoughtful person might advocate? If not, it's not a choice — it's a platitude.
- Does the policy address the diagnosis? Trace the line: the diagnosis says X is the challenge, the policy says we'll address it by Y. Does Y actually respond to X, or is it a non sequitur?
- Who in the organization would be uncomfortable with this policy? If nobody, it hasn't decided anything.
- What does this policy look like in a bad quarter? Does it still hold when resources are tight, or would the organization quietly abandon it?
### Common failure patterns
- **The umbrella policy**: Broad enough to accommodate any initiative anyone wants to pursue. "Invest in growth" covers everything from R&D to acquisitions to sales hiring — it constrains nothing.
- **The stealth goal**: "Our policy is to achieve market leadership in segment X" — that's a goal wearing a policy costume. The policy would be the *approach* to achieving market leadership: through price, through service depth, through platform lock-in, etc.
- **The both/and policy**: "We will be the cost leader AND the innovation leader AND the customer service leader." Strategies that refuse to choose between contradictory positions are not strategies.
- **The re-emerging rejected alternative**: The guiding policy explicitly rules something out, but one of the coherent actions quietly reintroduces it. Check for this specifically.
---
## 3. Action Coherence
**Core question:** Do the actions reinforce each other, and would they actually carry out the guiding policy?
Coherence is the tell. An incoherent action set — actions that pull in different directions, duplicate effort, or silently contradict each other — is the signature of a strategy that was assembled by committee rather than designed as a system.
### Rating criteria
**Strong**: Actions clearly reinforce each other — doing A makes B easier, B makes C cheaper, C protects A. The set has focus (3-6 actions, not 15). Each action has an owner, a timeframe, and a clear connection to the guiding policy. The author can trace the chain: if you remove any one action, the system degrades.
**Adequate**: Actions are consistent with the guiding policy and don't contradict each other, but the reinforcement is weak or unstated. They're a reasonable to-do list for someone pursuing this policy, but they haven't been designed as a system.
**Weak**: Actions include items that contradict or compete with each other for resources. Or the action list is too long (8+) and lacks prioritization — it's a project portfolio, not a coherent set. Or actions are so vague ("invest in technology") that coherence can't be assessed.
**Missing**: No actions, or actions that are disconnected from both the diagnosis and the guiding policy. The document ends with the policy and leaves execution to "the teams."
### Pressure-test questions
- For each pair of actions: does A make B easier or harder? Are there hidden resource conflicts?
- Which action is load-bearing? If it fails, does the rest of the strategy still work, or does it collapse? This identifies single points of failure.
- Are there actions that would happen regardless of this strategy — business-as-usual relabeled as strategic? Remove those and see what's left.
- Do the actions require capabilities the organization doesn't have? If so, is building those capabilities itself one of the actions?
- What's the *sequence*? Some actions must precede others. If the document treats them as parallel but they're actually sequential, the timeline is fiction.
- What happens if the most expensive or most difficult action is delayed by six months? Does the strategy degrade gracefully or break?
### Common failure patterns
- **The laundry list**: Every team's top priority became a "strategic action." No prioritization, no sequencing, no resource allocation.
- **The invisible dependency**: Action 3 depends on action 1 being complete, but this isn't stated. The actions look parallel but are actually sequential, and the timeline doesn't account for it.
- **The orphan action**: One action doesn't connect to any other. It was probably added to satisfy a stakeholder and wasn't part of the original strategic logic.
- **The missing action**: The guiding policy implies something that doesn't appear in the action list. For example, the policy says "focus on segment X" but no action addresses exiting segment Y.
**Lens connection — Execution Alignment**: When the strategy requires organizational change, apply 7S thinking from `references/review-lenses.md`. Actions that demand new capabilities, cross-functional coordination, or cultural shifts carry invisible requirements the strategy may not account for — check whether the actions address alignment across structure, systems, shared values, style, staff, and skills, or assume the organization will simply follow the new direction.
**Lens connection — Strategy Deployment**: When the strategy involves multiple organizational levels, apply Hoshin Kanri thinking from `references/review-lenses.md`. Check whether actions are stated at the right altitude and whether translation from executive intent to team-level execution has been accounted for. If the strategy adds actions without subtracting existing work, execution teams will make their own prioritization choices — and those choices may silently undermine the strategy.
---
## 4. Kernel Chain Integrity
**Core question:** Does the logical chain — "because [diagnosis], we will [guiding policy], which means we will [actions]" — actually hold?
This is the meta-dimension. Dimensions 1-3 evaluate each kernel element individually; this one evaluates whether they fit together. A strategy can have a good diagnosis, a good policy, and good actions that don't logically connect.
### Rating criteria
**Strong**: The "therefore" test passes cleanly. Reading "[diagnosis]. Therefore, [policy]. Which means [actions]." sounds like a logical argument, not a slide transition. Each link is tight — the policy responds to the specific diagnosis (not a different challenge), and the actions carry out the specific policy (not a generic version of it).
**Adequate**: The chain is traceable but requires some inference. The connections are present but not tight — you can see how they relate, but the policy could serve a somewhat different diagnosis, or the actions could serve a somewhat different policy.
**Weak**: Significant gaps in the chain. The diagnosis and policy address different topics. Or the actions seem disconnected from the policy — they might be good actions for a different strategy.
**Missing**: The document has components that don't form a chain at all — either because elements are missing, or because they were written independently and assembled without checking fit.
### Pressure-test questions
- Read the strategy as a single paragraph: "[Diagnosis]. Therefore, [policy]. Which means [actions]." Does it sound coherent, or do the transitions feel forced?
- If the diagnosis were different — say the opposite were true — would the guiding policy still make sense? If yes, the policy isn't responding to the diagnosis.
- If the guiding policy ruled something out but an action quietly reintroduces it, the chain is broken. Check the exclusion list against each action.
- Could someone read just the actions and correctly guess the diagnosis? If the actions don't contain the DNA of the diagnosis, the chain has broken by the time it reaches execution.
---
## 5. Bad-Strategy Pattern Detection
**Core question:** Are any of the four hallmarks of bad strategy (plus the additional anti-pattern) present in the document?
Bad strategy isn't the absence of strategy — it's the *presence of specific patterns* that look like strategy but aren't. These patterns are dangerous because they create confidence without substance. A document that contains them will feel "strategic" to casual readers while providing no actual guidance for decisions.
### The four Rumelt hallmarks (plus one additional anti-pattern)
**1. Fluff** — Buzzword-heavy language that sounds sophisticated but says nothing.
- Signal phrases: synergy, leverage, ecosystem, platform play, holistic, transformational, best-in-class, next-generation, customer-centric.
- The test: replace the buzzword with its plain-language definition. If the sentence now says nothing, it was fluff.
- Note: a single buzzword in an otherwise concrete document isn't a finding. The pattern is when fluff *replaces* specificity rather than supplementing it.
**2. Failure to face the challenge** — No clear statement of what the actual problem is. The document is all aspiration and no obstacle.
- The test: can you state the challenge in one sentence? If you can only state the desired outcome, the challenge has been avoided.
**3. Mistaking goals for strategy** — Revenue targets, market share goals, or outcome metrics presented as if they were strategy. "Grow 30% YoY" is a wish, not a plan.
- The test: does the document explain *how* and *why that how*? If the "strategy" section could be replaced by a spreadsheet target, it's goals.
**4. Bad strategic objectives** — Either a laundry list with no prioritization (the "dog's dinner") or blue-sky objectives that assume away the hard part ("we will eliminate tech debt").
- The test: if every objective is "high priority," none of them are. If the objective restates the problem as if naming it solved it, it's blue-sky.
**5. Strategy by analogy** (additional anti-pattern, not a Rumelt hallmark) — "Netflix did X, so we should too" without examining whether the conditions that made it work for Netflix exist here.
- The test: can the author name three conditions that made the analogy work for the original company, and verify they hold here?
### Rating criteria
**Strong**: No hallmarks detected, or minor traces that don't undermine the strategy's substance.
**Adequate**: One or two hallmarks present in mild form — some fluff in the executive summary, a section that reads more like goals than strategy. The core thinking is sound but the document could be tightened.
**Weak**: Multiple hallmarks present. The document has significant sections that sound strategic but lack substance. The reader would struggle to make a concrete decision based on this strategy.
**Missing** (meaning: the entire document is bad strategy): The document is primarily goals, fluff, or laundry lists with no underlying strategic logic. This is a "start over" finding.
---
## 6. Assumption Exposure
**Core question:** Has the strategy identified its load-bearing assumptions, and are those assumptions testable?
Every strategy is a bet. The question isn't whether it rests on assumptions — all strategies do — but whether the author *knows* which assumptions are load-bearing and has a plan for what happens if they're wrong.
### Rating criteria
**Strong**: Load-bearing assumptions are explicitly stated, distinguished from background assumptions. Each one is testable — the author could describe what evidence would confirm or refute it. The strategy acknowledges what changes if the biggest assumption is wrong. Risk exposure is proportional to the stakes.
**Adequate**: Some assumptions are stated but the list is incomplete. The most obvious ones are there; the subtle or uncomfortable ones are missing. Limited discussion of what happens if assumptions fail.
**Weak**: Assumptions are either absent or buried in optimistic language ("as the market continues to grow..."). The strategy reads as if the environment is certain and the plan will execute as designed.
**Missing**: No assumptions stated. The strategy presents its view of the world as fact. This is especially dangerous when the strategy depends on market trends, competitor behavior, or technology adoption curves.
### Pressure-test questions
- What are the three assumptions that, if wrong, would break this strategy entirely? Are they stated in the document?
- Does the strategy assume competitor behavior (e.g., "competitors will be slow to respond")? That's almost always optimistic.
- Does the strategy assume capability that doesn't yet exist (e.g., "once we build the new platform")? What happens if it takes twice as long?
- Does the strategy assume market conditions will continue (e.g., "the market is growing at 15% annually")? What if growth stalls?
- Are there second-order effects that haven't been considered? If action A succeeds, what does the competitor do in response? What does the customer do?
- Does the strategy assume organizational willingness? "We will stop doing X" — will the team that owns X agree? Is there political resistance the strategy pretends doesn't exist?
- What's the failure path that *doesn't* involve a dramatic crisis — the slow drift scenario where the strategy dies quietly because nobody noticed it wasn't working?
### Common failure patterns
- **Optimism as strategy**: The document's assumptions about the future consistently break in the org's favor. Markets grow, competitors stumble, technology works, talent arrives. No downside scenarios.
- **The missing "what if"**: No discussion of what changes if a key assumption fails. A strategy without contingency exposure is a strategy without humility.
- **Invisible assumptions**: The most dangerous kind. The strategy implicitly assumes things that nobody has stated — for example, that the team has the skills to execute a new approach, or that the board will fund the investment, or that customers will switch behavior.
- **The political assumption**: The strategy assumes organizational alignment that doesn't exist. "We will consolidate the three product lines" — has anyone told the three product line owners?
**Lens connection — Execution Alignment**: When the strategy requires organizational change, the most dangerous assumptions are often about the organization itself. Apply 7S thinking from `references/review-lenses.md` to surface unstated assumptions about whether current structure, systems, culture, and leadership style will support the new direction. The "slow drift" and "political veto" failure paths are frequently 7S misalignment that nobody named as an assumption.
---
## 7. Specificity and Falsifiability
**Core question:** Could you tell in 12 months whether this strategy worked, partially worked, or failed? If so, how?
A strategy that can't be evaluated can't be improved. Specificity isn't about adding metrics for the sake of metrics — it's about making the strategy's claims testable. If the diagnosis is vague, you can't tell whether the guiding policy addressed it. If the success criteria are vague, you can't tell whether the actions worked.
### Rating criteria
**Strong**: Each kernel element is specific enough to be falsified. The diagnosis names something concrete that can be verified. The guiding policy's exclusions are clear enough that you'd notice a violation. The actions have enough detail to tell whether they happened. Success indicators are observable, not aspirational.
**Adequate**: Mostly specific but with pockets of vagueness. The diagnosis is concrete but the success indicators are fuzzy. Or the actions are clear but the guiding policy is broad enough to accommodate almost any action set.
**Weak**: Significant vagueness throughout. You could read the strategy a year from now and have no way to assess whether it was followed, whether the diagnosis was correct, or whether the actions produced the intended effect.
**Missing**: The strategy is entirely unfalsifiable — so vague that no outcome could ever contradict it. "We will drive growth through innovation" cannot fail because it never committed to anything specific.
### Pressure-test questions
- Imagine you're reviewing this strategy in 12 months. What evidence would tell you it succeeded? What evidence would tell you it failed? If you can't describe the failure case, the strategy isn't specific enough.
- Are the success indicators leading indicators (detect problems early) or lagging indicators (confirm what already happened)? A strategy with only lagging indicators can't course-correct.
- Could a new employee read this document and understand what they should and shouldn't work on? If not, it's not specific enough to guide decisions.
- Take each action: what does "done" look like? Is there a clear difference between "we did this" and "we said we would do this but didn't"?
**Lens connection — Objective Translation**: When success criteria are one-dimensional or vague, apply Balanced Scorecard thinking from `references/review-lenses.md`. Check whether the strategy has leading indicators from customer and internal-process perspectives that would signal problems before financial metrics confirm them. A strategy measurable only in revenue and market share has a 6-12 month blind spot between cause and detection.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |