Product Strategy Frameworks That Survive Contact with the Enemy

Everybody loves a good 2x2 matrix. You draw it on a whiteboard, look incredibly smart, and then everyone goes back to their desks and keeps doing exactly what they were doing before.

Most strategy frameworks you read about in PM books break the moment they make contact with a real engineering team. They assume a sanitized world where priorities don't shift, the codebase is clean, and executives don't change their minds on a Tuesday.

Here are the strategy frameworks that I've found actually survive the friction of reality.

The Problem with Most Frameworks

Intelligence is overrated in product management. Courage beats intelligence.

You don't need a more complex framework to tell you what to build. You usually know what to build. You need the courage to look at the other 90 things on the list and explicitly say, "We are going to let these fail."

A framework is just a tool to help you make decisions faster. If your framework takes three weeks of research to fill out, it's not a framework, it's a side project.

1. The Kernel Strategy (Rumelt)

This is the only strategy definition you actually need. Richard Rumelt outlined it in Good Strategy/Bad Strategy, and it's brutally simple.

Every good strategy has a kernel with three parts:

1. A Diagnosis: What is the actual problem? Not the symptom. The underlying physics of the problem.
2. A Guiding Policy: The guardrails. How are we generally going to approach this?
3. Coherent Actions: The specific things we are going to do (and not do) that align with the policy.

If your strategy is just a list of goals ("Grow revenue by 20%"), you don't have a strategy. You have a wishlist. You need the diagnosis. When we were figuring out growth at Vibo, we spent 80% of our time arguing about the diagnosis. Once we agreed on what the actual bottleneck was, the actions became obvious.

2. Hard & Soft Priorities

I use this when dealing with stakeholder chaos.

The human brain can only hold about three priorities before everything becomes priority zero.

• Hard Priorities: The 1-2 things we will literally stop other work to protect. We burn political capital for these.
• Soft Priorities: Things we want to do, and will try to fit in, but we will ruthlessly cut the second a Hard Priority is threatened.

That's it. It's binary. The moment a stakeholder comes with a new urgent request, the framework does the heavy lifting. "Is this a Hard Priority? No? Then it goes into the backlog."

3. The Reversible vs Irreversible Matrix

Jeff Bezos called this Type 1 and Type 2 decisions.

• Type 1 (Irreversible): Two-way doors. If you walk through and don't like it, you can't come back easily. (e.g., Changing the core database architecture, altering pricing models). Make these decisions slowly and methodically.
• Type 2 (Reversible): One-way doors. If you don't like it, walk back through. (e.g., Changing button color, a new onboarding flow layout, launching a minor feature). Decide these in 5 minutes.

Most PMs treat all decisions like Type 1 decisions. They write 10-page PRDs for things that could be A/B tested to a small cohort in three days. Speed is a feature. Reduce the friction to making Type 2 decisions and you will outpace your competitors purely on iteration velocity.

Strategy is What You Don't Do

We talk about ambition in terms of size. "How big is your ambition?" That's the wrong question.

The real question is: What is the shape of your ambition? What are you willing to sacrifice?

If your strategy document doesn't have an explicit, painful list of things you are actively choosing not to do, then you haven't made any hard choices. A strategy that makes everyone happy is usually a strategy that accomplishes nothing.

---

FAQ

How do I introduce a new framework to a stubborn team?

Don't call it a framework. Just start asking the questions from the framework in your normal meetings. "Before we decide, what's our diagnosis here?" If you present a slide deck with a 2x2 matrix, people get defensive. If you just weave the logic into the conversation, people naturally adopt it.

What happens when the CEO bypasses the strategy?

This happens. The strategy is your shield, but occasionally an executive will blast through it. First, run the "Reversible" framework. Is their request a Type 2 decision? If yes, just do it fast and measure the result. If it's a Type 1 decision, you use the Kernel framework to force the diagnosis. Ask them: "What diagnosis of the market changed to prompt this new direction?"

Is OKR a strategy framework?

No. OKRs are a measurement framework. They tell you if you are arriving at the destination. They do not tell you how to navigate the map. Never confuse the speedometer for the steering wheel.