# Strategy Kernel

The strategy kernel connects a diagnosis of the central challenge to a guiding policy and a coherent set of reinforcing actions.

- Type: framework
- Domain: Strategy & discovery
- Level: Intermediate
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/strategy-kernel/>)

## What it means

The strategy kernel is Richard Rumelt’s minimum structure for a good strategy: a diagnosis that explains the challenge, a guiding policy that establishes the overall approach, and coherent actions that carry out that policy. It separates strategy from ambition, targets, slogans, and disconnected initiatives by requiring an explanation of the situation and coordinated choices about how to address it.

## Why it matters

Product strategies often become lists of desirable outcomes or roadmap themes without a causal argument. The kernel makes gaps visible. A target without a diagnosis does not say what must change; a policy without action is rhetoric; and projects that do not reinforce one another dissipate scarce capacity. The structure gives teams a compact way to critique and communicate strategic logic.

## When to use it

Use the kernel to create, review, or repair product strategy when teams disagree about the main obstacle or pursue many initiatives without clear coherence. It is especially helpful before translating strategy into bets and objectives. The framework does not replace customer, market, technical, or financial analysis needed to make the diagnosis credible.

## How it works

1. Gather evidence and identify the crux: the most consequential challenge the organization can realistically address.
2. Write a diagnosis that simplifies the situation and explains why the challenge persists.
3. Choose a guiding policy that sets boundaries and an overall method for dealing with the diagnosis.
4. Design a limited set of coordinated actions whose effects reinforce the policy and one another.
5. State exclusions and assumptions, then revisit the kernel when evidence shows the diagnosis or policy is wrong.

## A practical example

A collaboration product diagnoses that small agencies abandon it not because of missing features but because clients refuse to create accounts. Its guiding policy is to make external participation effortless without weakening project control. Coherent actions include secure guest links, client-specific permissions, and removing internal administration work from the near-term roadmap.

## Where it breaks

A neat three-part statement can still encode a false diagnosis or ineffective policy. Complex organizations may need several nested strategies, and uncertainty can require competing hypotheses rather than premature certainty. The kernel also says little about discovery quality, sequencing, resource feasibility, or how power and incentives affect execution.

## Common mistakes

- Writing goals or aspirations as the diagnosis instead of explaining the challenge.
- Using a broad value such as customer focus as a guiding policy without meaningful constraints.
- Attaching every existing initiative as a coherent action rather than making tradeoffs.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/strategy-kernel/#visualization-strategy-kernel>)

## Sources

1. [Good Strategy/Bad Strategy](<https://www.penguinrandomhouse.com/books/208668/good-strategy-bad-strategy-by-richard-rumelt/>) — Penguin Random House · Foundational book
2. [Books](<https://www.richardrumelt.com/books>) — Richard Rumelt · Author bibliography

## Related topics

- [Product Strategy](<https://wiki.soroush.uk/topic/product-strategy/>)
- [Strategic Bets](<https://wiki.soroush.uk/topic/strategic-bets/>)
- [Product Vision](<https://wiki.soroush.uk/topic/product-vision/>)
