Skip to content

Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/assess-strategic-environment

assess-strategic-environment

Unverified

Diagnoses competitive environment for an industry using BCG's Strategy Palette (Reeves) — Classical / Adaptive / Visionary / Shaping / Renewal — via the three-question discipline (predictability, malleability, harshness). Output: strategic-environment.md classifying the environment, evidencing the 3 dimensions with V/C/A/I tags, flagging ambidexterity, emitting a sub-skill routing matrix that weights Phase 1+2 sub-skills heavy/light/skip. Sub-skill of analyze-industry, invocable standalone. Runs FIRST in orchestrator chain — wrong diagnosis = wrong toolkit. Triggers on 'diagnose strategic environment for [industry]', 'strategy palette for [industry]', 'is [industry] classical or adaptive', 'classify the [industry] environment', 'Reeves environment for [industry]'. Do NOT activate for industry-attractiveness (use map-five-forces), market sizing (use size-market), single-company moat work (use assess-moat-sources), or DTC category go/no-go (use assess-category).

references/strategy-palette.md

View on GitHub
# BCG Strategy Palette — Framework Reference

Source: Martin Reeves, Knut Haanaes, Janmejaya Sinha, *Your Strategy Needs a Strategy: How to Choose and Execute the Right Approach* (BCG / HBR Press, 2015). Original HBR article: Reeves, Love & Tillmanns, "Your Strategy Needs a Strategy," HBR Sept 2012 (two-dimensional version; book added harshness).

## Why this framework exists

Most strategy failures are not failure of execution — they are failure of *style*. The right toolkit depends on the environment. Classical tools (Porter Five Forces, static value chain, plan-and-execute) work in stable, mature, non-shapeable industries. They actively mislead in fast-moving, shapeable, or harsh ones.

Reeves's empirical finding: firms whose strategic style matches their environment generate 4-8pp of TSR premium over mismatched peers.

## The three diagnostic dimensions

| Dimension | Question | What "Yes" looks like |
|-----------|----------|----------------------|
| **Predictability** | Can the trajectory be reliably forecast over 3-5 years? | Stable demand curves, slow tech cadence, locked regulatory regime, few plausible scenarios |
| **Malleability** | Can a single player (or coalition) materially shape industry structure or rules? | Platform dynamics, concentrated players, open regulatory rulebook, active shaping moves (consortia, standards) |
| **Harshness** | Is the industry in survival-mode (capital scarcity, regulatory cliff, demand collapse)? | Sustained negative growth, capital markets closed, existential regulation, cost-base > price |

## The five environments

| Environment | Predictable? | Malleable? | Harsh? | Strategic posture | Example industries (2026) |
|------------|--------------|-----------|--------|------------------|---------------------------|
| **Classical** | High | Low | Low | Be big — plan, position, execute | Industrial gases, packaged cement, regulated utilities |
| **Adaptive** | Low | Low | Low | Be fast — sense, respond, iterate | Industrial robotics, fashion, consumer electronics |
| **Visionary** | High | High | Low | Be first — envision and build | Early-stage biotech platform, foundation models (debatable — see edge cases) |
| **Shaping** | Low | High | Low | Be the orchestrator — coordinate ecosystem | Agentic commerce, payments, dev-tools platforms |
| **Renewal** | — | — | High | Be viable — survive then grow | Distressed retail, declining print media, sectors hit by mandated wind-down |

## Decision rule

1. Test harshness FIRST. If High → Renewal. Stop.
2. If Harshness Low: test malleability.
   - Malleability Low + Predictability High → Classical
   - Malleability Low + Predictability Low → Adaptive
   - Malleability High + Predictability High → Visionary
   - Malleability High + Predictability Low → Shaping

## The Diagnostician role

Reeves names "Diagnostician" as a leadership archetype: the executive whose continuous job is re-classifying the environment as conditions shift. The diagnosis is not a one-time event — quarterly re-diagnosis is recommended in fast-moving sectors. In agentic-commerce sectors in 2026, six-month re-diagnosis is appropriate.

## Ambidexterity (2020s extension)

The 2015 book introduced *ambidexterity* — the capacity for a firm to run multiple Palette approaches concurrently. BCG Henderson Institute work through 2024 has formalized four ambidexterity modes:

- **Separation** — different business units operate in different environments
- **Switching** — the same unit shifts approach as conditions change
- **Self-organization** — local units self-select their approach
- **External ecosystems** — partner with firms whose native style differs

For this skill: when the industry under analysis genuinely spans two environments at different layers/geos/segments, declare ambidexterity in the output. Do not over-call — most industries are single-environment when scoped correctly.

## 2026 overlay — AI as environment disruptor

Not in the 2015 book. The current question to ask in every dimension:

- **Predictability**: does the presence of AI-native players (with no legacy cost base) make a once-predictable industry unpredictable?
- **Malleability**: do agentic-commerce platforms create shaping power that did not exist 5 years ago?
- **Harshness**: are legacy cost structures suddenly above marginal-cost-of-AI-substitute pricing?

If any of these is "Yes," flag a direction-of-travel transition in step 7.

## Anti-patterns

- Classifying digital platform industries as Classical (almost always Shaping or Adaptive)
- Defaulting to Classical because it is familiar
- Inflating to Visionary based on founder rhetoric rather than industry-level malleability evidence
- Under-calling Renewal because the label is unpleasant
- Treating diagnosis as one-time rather than continuous (Diagnostician discipline)
- Classifying a multi-layer industry as a single environment when layers genuinely differ
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall