Strategy for Product Leaders: Eight Frameworks for the AI Era
What Each Framework Actually Forces, How They Combine, and Why All Eight Point at the Same Operational Question
Strategy is one of the most theatrical words in management. It’s used to describe five-year plans that turn out to be three-year wishlists, values statements that don’t commit to anything, OKR trees that cascade goals without engaging challenges, and board decks full of mountain-climbing metaphors that never name the mountain. Most of what passes for strategy in product organisations is aspiration, activity, or description—not strategy. Product leaders who want to do better need more than a framework. They need a toolkit of frameworks, each of which forces a specific kind of strategic honesty, and each of which hands its output cleanly to the next.
This directory is that toolkit. Eight frameworks, every one of which I’ve seen do real work in board rooms and ExCo meetings over the last decade. Every one of them remains useful in 2026—though most need recalibrating because AI has changed which strategic moves produce durable advantage. None of them is a template to fill in. Each is a forcing function that makes the organisation name something it would otherwise leave comfortably vague. The eight articles that follow walk each framework in detail; this directory explains what each forces, how they combine, and why the toolkit together produces something no single framework does alone.
The common thread running through all eight is this: every framework is a thinking scaffold for a conversation that the organisation would otherwise avoid. The document the framework produces is a by-product. The value is the discussion the scaffold makes possible. Treat frameworks as templates and you produce shelfware. Treat them as forcing functions and you produce actual direction. That distinction—scaffold vs template—is the spine of this entire cluster.
TL;DR: There are eight strategy frameworks product leaders in 2026 should know. Playing to Win forces strategic choices through a five-question cascade. 7 Powers forces honesty about whether your moat is real. Good Strategy Bad Strategy forces diagnosis before action. Wardley Maps force situational awareness. Blue Ocean Strategy forces creativity about where to play. Porter’s Five Forces forces industry-structure honesty. Porter’s Generic Strategies forces commitment to one position. SWOT forces a structured scan—but only if you subordinate it to a real choice framework. In 2026, all eight have one common update: build cost has collapsed, so the durable moats have shifted toward channel, brand, focus, switching costs, and network effects. Use the frameworks to force the conversation, tag the roadmap capacity against the outputs, and the strategy stops being theatre.
What Is Strategy, Actually?
Strategy is not a goal. It is not a vision. It is not a set of values. It is not a list of OKRs. These are all useful—but they are not strategy. Strategy is the set of choices that determine where the organisation will play, how it will win there, and what coherent actions will be taken to execute against that choice given the specific obstacles in the way.
Three elements make a real strategy, and all three are required:
- A diagnosis of the specific challenge being engaged. Not “competition is increasing”—a specific, bounded, named challenge (see Rumelt’s kernel ).
- A commitment to a direction that rules out other directions. Where will we play; how will we win; what will we deliberately not do (see Playing to Win ).
- A coherent set of actions that mutually reinforce each other and execute the commitment against the diagnosed challenge.
A strategy document missing any one of these is not a strategy. It is an aspirational artefact that looks like one. Product organisations produce aspirational artefacts constantly; they produce real strategy rarely. The eight frameworks in this cluster are the tools that increase the hit rate.
The Eight Frameworks: What Each One Forces
Each framework in this cluster answers a specific strategic question. Understanding which question you need to answer tells you which framework to pick up.
1. Playing to Win — Forces Coherent Choice
A.G. Lafley and Roger Martin’s five-question cascade: Winning Aspiration → Where to Play → How to Win → Capabilities → Management Systems. Its job is to force the organisation to make choices—to commit to a direction that rules out others, and to demonstrate that every answer is coherent with every other answer. If your Where-to-Play and How-to-Win answers don’t match, the cascade tells you immediately. The most versatile framework in the cluster and the natural anchor.
2. 7 Powers — Forces Moat Honesty
Hamilton Helmer’s seven durable structural advantages: Scale Economies, Network Economies, Counter-Positioning, Switching Costs, Branding, Cornered Resource, Process Power. Its job is to force honesty about which structural Power (if any) your product actually possesses. Operational excellence is not a Power. Feature leadership is not a Power. If your How-to-Win from the Playing to Win cascade doesn’t name one of the seven, you don’t have a durable answer. The best durability-testing framework I know.
3. Good Strategy Bad Strategy — Forces Diagnosis
Richard Rumelt’s kernel: diagnosis → guiding policy → coherent action. Its job is to distinguish real strategy from fluff by demanding a sharp diagnosis of the specific challenge before any direction or action is named. Most corporate “strategy” is goals without diagnosis—an aspirational artefact pretending to engage a challenge it hasn’t named. Rumelt’s kernel is the fluff detector.
4. Wardley Maps — Forces Situational Awareness
Simon Wardley’s mapping technique: plot the value chain on the genesis → custom → product → commodity evolution axis. Its job is to produce situational awareness—the ability to see which components are moving from product to commodity, which substitutes are emerging, and which capabilities should be pioneered vs. industrialised. The only framework in the cluster that explicitly maps terrain rather than making choices.
5. Blue Ocean Strategy — Forces Creativity (Carefully)
W. Chan Kim and Renée Mauborgne’s value innovation framework: find uncontested market space rather than fight in feature-crowded ones. Its job is to force creativity about where to play, not just how. The trap is its main tool (the strategy canvas) plots features, which is exactly the wrong place to look for 2026 blue oceans. Real blue oceans today are in segment, channel, and workflow—not features.
6. Porter’s Five Forces — Forces Industry-Structure Diagnosis
Michael Porter’s five competitive forces: new entrants, suppliers, buyers, substitutes, rivalry. Its job is to diagnose industry structure—whether the market is structurally attractive to operate in. In 2026, three of the five forces have rewritten themselves materially (threat of new entrants is effectively infinite in software), and using the framework without recalibration produces textbook answers that don’t match market reality.
7. Porter’s Generic Strategies — Forces Positional Commitment
Porter’s three strategies: cost leadership, differentiation, focus. Its job is to force commitment to one positional stance rather than trying to straddle. In 2026, two of the three have died in software categories (cost leadership and feature-based differentiation), leaving focus—segment + channel + brand—as the surviving durable position. The most dramatic AI-era update in the cluster.
8. SWOT Analysis — Forces a Structured Scan (Not a Strategy)
The oldest framework in the cluster and the most misused. Strengths, Weaknesses, Opportunities, Threats. Its job is to produce a structured scan of the company’s position—but only as input to a real choice framework. Used as strategy, SWOT is the forty-item catalogue Hill and Westbrook demolished in 1997. Used as input to Playing to Win or Rumelt’s kernel, it earns its keep.
The AI-Era Reframe That Runs Through All Eight
Strategy frameworks developed before 2022 all rested on an assumption that has quietly stopped being true: that building a competing product was expensive, slow, and required scarce engineering talent. In 2026, that assumption is dead. AI has collapsed the marginal cost of producing a credible software product to near zero. A competitor can clone your feature set in weeks. A new entrant with no sunk cost can undercut your pricing by 40-60% while still generating positive unit economics.
What has not changed is the cost of convincing a customer to buy. Customer acquisition, trust, credibility, switching costs, channel relationships, and brand equity all cost what they always cost. The asymmetry between collapsed build cost and unchanged sell cost has become the dominant force reshaping every strategy framework’s answers:
- Cost leadership has died as a durable moat (see Porter’s Generic Strategies).
- Feature-based differentiation has died (Blue Ocean, Generic Strategies).
- Threat of new entrants is effectively infinite (Porter’s Five Forces).
- Substitutes emerge faster than annual strategic reviews can track (Wardley, Five Forces).
- Scale Economies (7 Powers) weaken in the cost-leadership variant; compute/data scale strengthens.
What has strengthened:
- Channel access. You cannot clone a framework agreement.
- Brand authority. Trust accumulated over years is uncloneable in weeks.
- Switching costs. When features are cheap, leaving costs matter more.
- Network effects. Data-network effects compound faster in AI.
- Counter-positioning. Incumbents’ inability to self-cannibalise is amplified.
- Focus (segment + channel + brand). The only generic strategy that survives.
A product strategy in 2026 that underweights these five and overweights cost leadership or feature differentiation is using a 2016 playbook. Every framework in this cluster has been updated below to reflect the shift. Read the frameworks through this lens and the strategy toolkit becomes fit for the current terrain rather than nostalgic for the last one.
How the Eight Frameworks Combine
No single framework produces a complete strategy. The ideal strategic process uses several in combination, each contributing the piece it’s best at:
- Start with situational awareness. Wardley Maps show the terrain. Which components are evolving from product to commodity? Where are substitutes emerging? This is what you’re working with.
- Add industry-structure diagnosis. Porter’s Five Forces tells you whether the industry itself is attractive and which force is most threatening.
- Scan company position. SWOT captures the situational input—as input, never as output.
- Name the diagnosis. Rumelt’s kernel forces you to name the specific challenge your strategy is going to engage.
- Make the choices. Playing to Win cascades the choice into five coherent answers.
- Get creative about where. Blue Ocean Strategy helps find segment, channel, and workflow positions the incumbents aren’t serving.
- Commit to a position. Porter’s Generic Strategies forces commitment (in 2026, almost always to focus).
- Test for durability. 7 Powers asks whether the chosen How-to-Win rests on a structural moat.
Not every strategy exercise needs all eight. A fast-moving startup running a Playing to Win cascade does not need to run PESTLE and Five Forces first—they can start with what they see and iterate. A PE portfolio company doing a 100-day plan does need the full sweep, because the diagnostic weight of understanding what they’ve just bought is the whole point. Match the tool depth to the decision depth.
What does not change: the output should always feed into a business case / PID that every ExCo member signs, which in turn flows into the roadmap capacity grid via tagged Objectives. Strategy without that operational bridge is theatre. The frameworks do their job when each framework’s output becomes the next framework’s input, the final output becomes the PID, and the PID becomes the capacity allocation. That’s what mature strategy practice looks like.
Which Framework, When?
| You need to… | Use… |
|---|---|
| See how the landscape is evolving | Wardley Maps |
| Diagnose industry attractiveness | Porter’s Five Forces |
| Scan the company’s position | SWOT |
| Name the specific challenge | Good Strategy Bad Strategy |
| Make coherent strategic choices | Playing to Win |
| Find uncontested market space | Blue Ocean Strategy |
| Commit to a positional stance | Porter’s Generic Strategies |
| Test whether your moat is real | 7 Powers |
A common misuse is to pick the wrong framework for the question. Using SWOT to answer industry-structure questions, using Playing to Win as a situational-awareness tool, or using 7 Powers as a first-pass strategic choice framework—all produce shallow work. Match the framework to the question.
From Strategy to the Roadmap
All eight frameworks ultimately point at the same operational question: does the capacity actually reflect the strategy?
The bridge is tagging. Objective Tagging is the operational mechanism that makes the gap between strategy and allocation visible. Pick a tagging lens that matches the strategic output: RGT if the strategy is about portfolio balance; segment-based tagging if the strategy is focus; Power-based tagging if the strategy is 7-Powers-aligned; force-based tagging if the strategy is Five-Forces-aligned.
Whichever lens you pick, every squad-sprint WIP in RoadmapOne should be tagged to a strategic element. The analytic question that becomes answerable is: what percentage of our capacity is actually serving the strategy we committed to? Most teams running this analysis for the first time are shocked at the gap—strategy says one thing, capacity does another. That gap is the conversation the tagging forces. Close it with conscious reallocation; leave it open and the strategy is theatre regardless of how well-crafted the document is.
Prioritisation frameworks like BRICE get sharper when strategy-aligned. The Business Importance dimension becomes concrete once the strategy has produced a named diagnosis, a committed direction, and a tagged set of Objectives. Without strategy upstream, prioritisation collapses into politics. With strategy upstream, prioritisation becomes arithmetic.
FAQ
What is the best strategy framework for product leaders?
There is no single best framework. The eight frameworks in this cluster each force a specific kind of strategic honesty, and the ideal practice uses several in combination. If you can only pick one to learn first, start with Playing to Win —its five-question cascade is the most versatile and pairs naturally with the others. If you’re diagnosing why your current strategy isn’t working, start with Rumelt’s kernel to test whether you actually have a strategy or a list of goals.
How does strategy connect to the roadmap?
Strategy produces commitments. The commitments become an ExCo-signed business case / PID . The PID flows into tagged Objectives on the roadmap capacity grid . When every squad-sprint allocation is tagged against a strategic element, a capacity view can show whether the roadmap is actually serving the strategy or has drifted into operational work. The gap between strategy and allocation is where most strategies die; the tagging discipline is what surfaces it.
What has changed about strategy in the AI era?
Build cost has collapsed to near zero while customer-acquisition cost has not. This asymmetry has materially changed several classic strategic moves: cost leadership is no longer a durable moat, feature-based differentiation is cloned in weeks, and the threat of new entrants in software is effectively infinite. What has strengthened: channel access, brand authority, switching costs, network effects, counter-positioning, and focus (segment + channel + brand). Every strategy framework in this cluster has been updated for the AI era in its dedicated article.
How many strategy frameworks do I need to know?
For most product leaders, four are essential: Playing to Win for coherent choice-making, Good Strategy Bad Strategy for the diagnosis discipline, 7 Powers for moat testing, and Wardley Maps for situational awareness. The other four (Porter’s Five Forces , Generic Strategies , Blue Ocean , SWOT ) are valuable as specific tools for specific questions—learn them as you need them.
What is the difference between strategy and OKRs?
Strategy names the specific challenge, commits to a direction, and sets out the coherent actions that will address the challenge. OKRs are a mechanism for expressing goals and measurable key results that track progress toward those goals. OKRs are excellent at the coherent-action layer of strategy; they are terrible as strategy substitutes. An OKR tree with no diagnosis or guiding policy above it is strategy theatre in a neat format. Use OKRs to express strategy; don’t confuse them for strategy itself.
Do PE firms use these frameworks?
PE firms are outcome-oriented and interrogate business fundamentals (unit economics, moat durability, segment validation, channel economics) rather than being wedded to specific named frameworks. They use whichever analytical lens gets them to the answer fastest for the specific business in front of them. The honest question to ask of any strategy framework isn’t “do PE firms use this?” but “does this produce the business-fundamentals insights a PE due-diligence team would actually test for?”. All eight frameworks in this cluster, used honestly, do produce that kind of insight.
Conclusion
Strategy is the most theatrical word in management and, done properly, one of the most valuable management disciplines. The eight frameworks in this cluster don’t produce strategy on their own—no framework does. What they produce is forcing functions: scaffolds that make the organisation have a conversation it would otherwise avoid, and name a commitment it would otherwise leave comfortably vague.
In the AI era, the stakes of getting this right have risen. Build cost has collapsed; sell cost has not. Every classic strategic move has to be re-tested against the new terrain. Cost leadership and feature-based differentiation are dead. Channel, brand, switching costs, network effects, counter-positioning, and focus are what survive. Product leaders who run their strategy process through the combined toolkit in this cluster—situational awareness, diagnosis, coherent choices, durability testing—and then tag the roadmap capacity against the outputs will end up with strategies that survive the noise. Leaders who treat frameworks as templates to fill in will produce beautifully formatted artefacts that change nothing.
Pick which side of that you want to be on. The frameworks are neutral. The discipline is up to you.