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/review-lenses.md

View on GitHub
# Review Lenses

Four complementary frameworks that sharpen the review when the strategy document warrants them. Lenses load conditionally — most reviews use one or two; some use none. The reviewer weaves lens-specific questions into the existing seven dimensions rather than adding new sections.

**The lenses do not ask the author to adopt a new framework.** They give the reviewer sharper questions by applying structured thinking that the core dimensions alone might miss — particularly around execution feasibility and competitive environment accuracy.

---

## 1. McKinsey 7S — Execution Alignment

### When to load

When the strategy requires organizational change — new structure, new processes, cultural shift, or cross-functional coordination. Load this lens when you see:

- Actions that imply structural reorganization (new teams, new reporting lines, consolidated functions)
- A guiding policy that requires different skills or capabilities than the organization currently has
- Cross-functional dependencies that the actions treat as straightforward
- References to "culture change," "mindset shift," or "new ways of working"

### What to look for

The seven elements: strategy, structure, systems, shared values, style, staff, skills. The most common gap: the strategy changes the "strategy" element but assumes the other six will follow.

Check alignment between what the strategy demands and what the organization currently is:

- **Structure**: Does the current org structure support the new direction, or does it create friction? If teams need to collaborate differently, has the strategy addressed how?
- **Systems**: Do existing processes, tools, and decision-making systems support the change, or will they produce antibodies?
- **Shared values**: Does the strategy conflict with deeply held organizational beliefs? A strategy requiring "move fast" in an organization that values "measure twice" will face silent resistance.
- **Style**: Does leadership behavior reinforce the strategy? If the strategy says "empower teams" but leadership is command-and-control, the strategy loses.
- **Staff**: Does the organization have the people this requires? Not just headcount — the specific mix of experience, judgment, and domain knowledge.
- **Skills**: Does the organization have the capabilities? Not individual skills — organizational capabilities like "shipping mobile products" or "managing enterprise sales cycles."

### Pressure-test questions

1. Which of the six non-strategy elements (structure, systems, shared values, style, staff, skills) must change for this strategy to work? Does the document acknowledge any of them?
2. Where will current systems and processes produce friction against the new direction? Is that friction addressed or ignored?
3. If the strategy requires cross-functional coordination that doesn't exist today, what's the plan for creating it? "Better communication" is not a plan.
4. Does leadership style match what the strategy demands? A strategy requiring decentralized decisions won't work under centralized leadership.
5. What's the gap between the skills the organization has and the skills the strategy needs? Is closing that gap part of the action plan, or is it assumed away?

### Common gaps this reveals

- **The structural orphan**: A key action requires coordination between teams that don't currently work together, and no one owns making that coordination happen.
- **The systems antibody**: Existing approval processes, budgeting cycles, or performance metrics will actively undermine the new strategy because nobody thought to change them.
- **The cultural contradiction**: The strategy requires behaviors that conflict with "how we actually do things here." The document won't mention this; the reviewer should.
- **The skills gap dressed as a timeline**: "Hire a mobile team by Q2" treats a capability-building challenge as a procurement problem.

**Dimension connections**: Primarily strengthens Dimension 3 (Action Coherence) and Dimension 6 (Assumption Exposure). The "slow drift" and "political veto" failure paths are often 7S misalignment in disguise.

---

## 2. Balanced Scorecard — Objective Translation

### When to load

When the strategy's success criteria are one-dimensional or vague. Load this lens when you see:

- Success measured only in financial terms (revenue, margin, market share)
- "What success looks like" is aspirational rather than observable
- No leading indicators — only outcomes that take 6-12 months to appear
- Actions without clear measures of progress

### What to look for

Check whether the strategy translates into objectives across four perspectives — not as a formal scorecard, but as a completeness check on how success is defined:

- **Financial**: Revenue, margin, cost targets. Almost always present. The question is whether these are the *only* measures.
- **Customer**: What changes for the customer? How would you know the strategy is working from the customer's perspective before financial results arrive? Acquisition cost, retention, NPS, usage patterns, time-to-value.
- **Internal Process**: What processes must improve or be created? How do you measure whether the operational capabilities the strategy requires are actually being built?
- **Learning & Growth**: Is the organization developing the capabilities, knowledge, and culture the strategy needs? Staff development, knowledge management, innovation pipeline health.

A strategy with only financial success criteria can't course-correct — by the time revenue tells you something's wrong, the underlying causes are 6-12 months old.

Beyond the four perspectives, check for the deeper Balanced Scorecard elements that separate rigorous objective translation from surface-level "balanced KPI coverage":

- **Causal linkage**: Do the objectives across perspectives form a cause-and-effect chain? Learning & Growth improvements should drive Internal Process improvements, which should drive Customer outcomes, which should drive Financial results. If the objectives are just four independent lists, the scorecard thinking is decorative — it hasn't identified the causal theory of how the strategy creates value.
- **Targets**: Are there specific, time-bound targets for each objective — not just metrics to watch, but thresholds that distinguish success from failure? "Track NPS" is monitoring; "NPS above 45 by Q3" is a target the org can rally around and course-correct against.
- **Strategic initiatives**: For each objective gap (where-we-are vs. target), is there a funded initiative to close it? Objectives without initiatives are wishes. Check whether the coherent actions map to specific objective gaps or float independently.
- **Review cadence**: Does the strategy specify how often progress will be reviewed and by whom? The Balanced Scorecard's operational power comes from regular strategy review meetings where leading indicators trigger mid-course corrections. Without a review rhythm, the scorecard degrades into a dashboard nobody checks.

### Pressure-test questions

1. If the strategy is working as intended, what would you see in 90 days that isn't a financial metric? If there's no answer, the strategy has no early warning system.
2. What customer behavior would change first if the strategy is succeeding? Is that behavior being measured?
3. Which internal processes are load-bearing for this strategy? How would you know if they're improving or degrading?
4. What capabilities must the organization build? How would you measure progress on capability-building before end results arrive?
5. If the financial targets are missed in Q3, what non-financial indicators from Q1-Q2 should have flagged the problem? If none exist, the strategy is flying blind.
6. Can you trace a causal chain from a Learning & Growth objective through Internal Process and Customer objectives to a Financial outcome? If the objectives don't link causally, they're four independent wish lists.
7. For each success indicator — is there a specific target with a deadline, or just a metric to "track"? Monitoring without thresholds can't trigger corrective action.
8. For each gap between current state and target — is there a funded initiative to close it, or is the gap expected to close on its own?
9. How often will the strategy's leading indicators be reviewed, by whom, and what authority do they have to adjust course? If there's no review cadence, the scorecard is a one-time artifact, not an operating tool.

### Common gaps this reveals

- **The financial-only trap**: Success defined entirely in outcomes (revenue, market share) with no visibility into the drivers. Problems are discovered 6+ months after they start.
- **The activity-as-progress illusion**: Actions have timelines but no outcome measures. "Launch mobile app by Q3" tells you whether the action happened, not whether it worked.
- **The missing learning loop**: No measures for capability development. The strategy requires new skills but has no way to tell whether the organization is acquiring them.
- **The customer blind spot**: Financial projections assume customer behavior changes, but no customer-facing metrics would confirm whether those changes are happening.

**Dimension connections**: Primarily strengthens Dimension 7 (Specificity and Falsifiability). Also informs the "measurement void" failure path.

---

## 3. Porter's Five Forces — Competitive Pressure Audit

### When to load

When the diagnosis addresses competitive dynamics. Load this lens when you see:

- Market position or competitive standing as part of the diagnosis
- Pricing pressure, margin erosion, or commoditization discussed
- New market entrants or emerging competitors mentioned
- Technology substitution or category disruption referenced
- Supply chain dependencies or customer concentration acknowledged

### What to look for

Check whether the diagnosis has identified the full set of competitive pressures, not just the most visible one:

1. **Rivalry among existing competitors**: Most strategies address this. The question is whether the analysis goes beyond "we compete with X" to understand structural drivers of rivalry — industry growth rate, differentiation levels, switching costs, exit barriers.

2. **Threat of new entrants**: What barriers prevent new competitors from entering? Are those barriers eroding? Strategies that assume today's competitor set is fixed often miss that the real threat is someone who doesn't compete today.

3. **Threat of substitutes**: Not just direct competitors — alternative approaches to the same customer need. The strategy might be winning against Competitor X while a substitute technology makes the entire category irrelevant.

4. **Bargaining power of suppliers**: How dependent is the organization on specific suppliers, platforms, or partners? A strategy built on a platform you don't control carries supplier-power risk.

5. **Bargaining power of buyers**: How much leverage do customers have? Strategies that assume pricing power should check whether buyer concentration or switching-cost dynamics support that assumption.

### Pressure-test questions

1. The diagnosis addresses rivalry — but has it considered which other forces shape the competitive environment? Which forces are notably absent from the analysis?
2. What prevents a new entrant from pursuing the same guiding policy? If the answer is "nothing," the strategy's advantage window may be shorter than assumed.
3. Is there a substitute technology, business model, or approach that could make the strategy's value proposition irrelevant — not by competing directly, but by redefining the problem?
4. Does the strategy depend on a platform, supplier, or partner whose interests might diverge? What happens if they change terms, compete directly, or disappear?
5. Does the strategy assume customer loyalty or switching costs that may not hold? What happens if buyers gain more leverage through alternatives or consolidation?

### Common gaps this reveals

- **The rivalry-only diagnosis**: Competitive dynamics treated as a two-player game (us vs. main competitor) while ignoring structural forces shaping the entire environment.
- **The invisible substitute**: Direct competitors correctly identified, but a different category of solution is about to absorb the customer need.
- **The platform dependency**: Strategy built on a platform (cloud provider, app store, marketplace) treated as infrastructure but actually a supplier with increasing bargaining power.
- **The eroding moat**: Strategy assumes barriers to entry that are weakening — regulatory protection being removed, proprietary technology being commoditized, talent becoming more available.

**Dimension connections**: Primarily strengthens Dimension 1 (Diagnosis Quality). For each force the strategy mentions, check the analysis depth. For forces it doesn't mention, ask whether the omission is justified or a blind spot.

---

## 4. Hoshin Kanri — Strategy Deployment

### When to load

When the strategy involves multiple organizational levels — when actions need to cascade from executive intent to team-level execution. Load this lens when you see:

- Actions stated at different altitudes (some executive-level, some operational)
- Multiple teams or departments responsible for different parts of execution
- Initiatives that require translation from strategic intent to operational plans
- A gap between the strategy's ambition and the specificity of its actions

### What to look for

Strategy fails at the translation layers. The board-level strategy becomes a VP-level initiative becomes a team-level OKR, and at each translation, meaning is lost:

- **Altitude consistency**: Are actions stated at the right level? If they're all executive-level ("launch mobile app"), do they account for the team-level translation needed? If they're all operational ("implement offline sync"), is there a clear line back to strategic intent?
- **Catchball evidence**: Has the strategy been tested bidirectionally — top-down intent meeting bottom-up feasibility? If it reads as purely top-down, the actions may not survive contact with the teams who must execute them.
- **Translation gaps**: Between each organizational level, ask: could a team lead read this and know what to prioritize this quarter? If not, translation work is needed that the strategy doesn't acknowledge.
- **Breakthrough vs. operational**: Does the strategy distinguish between breakthrough objectives (change the trajectory) and operational objectives (keep the business running)? Breakthrough objectives need protection from being crowded out by operational demands.

### Pressure-test questions

1. If a team lead reads this strategy, can they derive their team's priorities for the next quarter? If not, where does translation break down?
2. Is there evidence that the actions were validated with the people who must execute them — or do they read as mandates from above?
3. Which actions are "breakthrough" (change the trajectory) and which are "operational" (keep the business running)? Are the breakthrough actions protected from being deprioritized when operational demands surge?
4. If the strategy requires coordination between teams, who owns the integration points? If nobody does, those are the points where execution will fragment.
5. What gets deprioritized to make room for these strategic actions? If the strategy adds without subtracting, execution teams will make their own subtraction choices — and those choices may undermine the strategy.

### Common gaps this reveals

- **The altitude mismatch**: Executive-level actions with no operational translation. "Enter the enterprise market" is a strategy-level statement; the teams need to know which segment, through which channel, with which product changes.
- **The missing catchball**: Actions designed without input from executors. The strategy assumes feasibility that hasn't been validated. This surfaces as "we had no idea this was coming" when strategy is announced.
- **The crowded-out breakthrough**: Breakthrough objectives that compete with operational demands for the same resources. Without explicit protection, operational urgency always wins — and the strategy quietly dies.
- **The orphaned integration**: Actions that depend on cross-team coordination, but no one owns the coordination itself. Each team optimizes their piece; the whole fragments.

**Dimension connections**: Primarily strengthens Dimension 3 (Action Coherence). Also feeds the "execution bottleneck" failure path.

---

## Using lenses in the review

### Selection

After reading the strategy document and extracting the kernel (Step 2), mentally check each lens trigger. Load the relevant lenses for Step 3. Most reviews activate one or two; activating all four suggests the strategy has broad structural gaps.

### Integration

Lens questions weave into the existing seven dimensions — they don't create separate evaluation sections. When a lens reveals a gap, record the finding under the relevant dimension (usually 1, 3, 6, or 7). The lens is the tool that found the gap; the dimension is where the gap lives.

### Reporting

If any lenses were applied, include a "Lens Findings" section in the review output (see review-template.md). This section captures what the lenses revealed that the core dimensions alone would likely have missed — particularly systemic issues that span multiple dimensions.

### What lenses don't do

- They don't ask the author to adopt a new framework or fill out a grid
- They don't add new dimensions to the review
- They don't replace the core kernel analysis
- They don't require the reviewer to explain the framework to the user — use the thinking, not the vocabulary
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