Building & Strategy
Does Your Strategy Have a Kernel?
If your roadmap feels like a wish list, you probably missed the kernel.
2026-10-251 min read
The kernel is a three‑part pattern: diagnosis, guiding policy, coherent actions. It works because the diagnosis isolates the real obstacle, the guiding policy creates a decision filter, and the coherent actions lock every team member into that filter, preventing drift toward shiny features. A product team of about a dozen gathered for a quarterly planning session, where the product lead framed the market shift as “customers are abandoning complex setups for plug‑and‑play experiences.”
The guiding policy emerged as “simplify onboarding to under ten minutes,” and every proposed feature was tested against that rule before entering the backlog. The result was a launch that cut the onboarding time dramatically, and the market responded with a surge in trial conversions that the team could see on the live dashboard within a few weeks. The kernel prevents the common habit of adding “nice‑to‑have” items that never move the needle, because each item must earn a spot by directly supporting the guiding policy.
The downside appears when the diagnosis is too narrow, turning a flexible strategy into a tunnel vision that blinds the team to emerging opportunities.
Key insights
A clear diagnosis turns ambiguity into a single problem worth solving.
The guiding policy acts as a decision filter that stops feature creep before it starts.
Why it matters
Ignoring the kernel lets vague ambitions fill the roadmap, causing wasted effort and missed market wins.
A weak diagnosis creates a guiding policy that locks the team into the wrong problem, eroding competitive advantage.
Use this tomorrow
1Open your latest roadmap document, locate the top three initiatives, and write next to each why it directly addresses the current diagnosis.
2Scan the last sprint review notes for any item that was added without a reference to the guiding policy, and count how many such items exist.
Go deeper
The kernel concept originates from Richard Rumelt’s work on strategic design, where he argues that a good strategy must contain these three interlocking elements. By separating the problem definition from the solution, leaders avoid the temptation to conflate ambition with actionable direction, which often leads to bloated roadmaps.
The approach can backfire if the diagnosis becomes a self‑fulfilling prophecy; teams may ignore signals that contradict their initial framing, so periodic re‑diagnosis is essential. This mirrors the “premature closure” bias in decision science, where early conclusions block later learning.
