The News Rupt

The best product strategy frameworks product leaders actually use

Seven frameworks, seven different questions — and why the common mistake is not choosing the wrong one, but asking a good framework to answer a question it was never designed for.

Ask ten product leaders what “product strategy” means and you are unlikely to get ten versions of the same answer.

One will talk about where to play. Another will talk about customer problems. A third will pull up the company goals. Someone building an AI product will start talking about data, models, workflows and defensibility.

That variation is not necessarily a problem. It may actually tell us something important about strategy: there is no single product strategy framework that solves every kind of uncertainty.

A note on the research

This is not a fictional survey in which 53 unnamed CPOs conveniently voted for seven frameworks.

Instead, we approached it as a structured synthesis of current product-leadership research and public practitioner thinking, then compared those problems with the primary literature behind the major strategy frameworks.

The evidence base included, among others, Productboard’s survey of 101 product executives; a 2026 study of 107 senior product leaders; research involving 425 B2B product practitioners; and Products That Count’s research and conversations with more than 1,000 CPOs. The studies cover different populations and questions, so they should not be combined into a single statistical sample. But collectively they reveal a fairly consistent picture: product leaders are being asked to connect strategy to business outcomes while simultaneously dealing with AI, prioritization, organizational complexity, customer evidence and faster product cycles.

Importantly, these studies do not provide a reliable league table showing that, say, 31% of CPOs use Jobs to Be Done and 22% use Playing to Win. So the seven below are not ranked by popularity. They are seven frameworks that repeatedly address the strategic questions product leaders are actually struggling with.

1. Playing to Win

Originators: A.G. Lafley and Roger L. Martin.

The enduring strength of Playing to Win is that it forces strategy to become a set of choices rather than a list of ambitions. Its cascade asks five deceptively difficult questions: What is our winning aspiration? Where will we play? How will we win? What capabilities must we have? What management systems do we need?

Lafley and Martin developed the approach through their work at Procter & Gamble, and the framework remains unusually useful because the five decisions have to reinforce one another. “Where to play” cannot be answered independently from “how to win.”

Why product leaders keep returning to it. The framework is particularly useful when product strategy starts becoming a collection of priorities. Enterprise and later-stage leaders often have plenty of opportunities. Their harder problem is deciding which opportunities they will deliberately decline.

Imagine a B2B platform that could move down-market, expand internationally, add an AI assistant, build a marketplace and enter an adjacent category. All five may be reasonable ideas. Playing to Win asks a harder question: which combination creates a coherent position where we can actually win? That makes it especially useful for multi-product businesses, portfolio decisions and companies moving from product-market fit into scale.

Where it becomes insufficient. It assumes you understand the customer and competitive landscape well enough to make those choices. It does not, by itself, tell you what customers are really trying to accomplish. Nor does it deeply diagnose why your existing strategy is failing. That is why it pairs well with Jobs to Be Done on the customer side and Rumelt’s Strategy Kernel on the diagnosis side.

Best strategic questionWhere will we play, and how will we win there?

2. Good Strategy/Bad Strategy — the Strategy Kernel

Originator: Richard Rumelt.

Richard Rumelt’s framework is much less elaborate: Diagnosis → Guiding Policy → Coherent Actions. That simplicity is precisely why experienced leaders use it.

A diagnosis explains the central challenge. The guiding policy describes the approach for dealing with it. Coherent actions concentrate resources behind that approach. Rumelt’s central objection is to strategies that are actually aspirations, targets or collections of initiatives wearing the word “strategy.”

For product leaders, this distinction matters enormously. “Become the leading AI platform for our industry” is not a strategy. “Grow enterprise revenue by 30%” is not a strategy either. Neither tells the organization what obstacle is preventing it from succeeding or what it has chosen to do about it.

Why product leaders use it. It is particularly effective in messy situations. Turnarounds. Product stagnation. Post-acquisition integration. A startup that has stopped growing. An enterprise with forty initiatives and no clear explanation for why customers are not adopting the product. Senior product leaders often need diagnosis before prioritization. Rumelt forces that conversation.

For an early-stage company, this may be all the strategy framework it needs. A ten-person startup does not necessarily need an elaborate strategy architecture. It needs to identify the critical constraint and concentrate.

Where it becomes insufficient. The Kernel is deliberately abstract. It can tell you that you need a coherent guiding policy, but it does not supply a method for discovering customer demand, mapping an ecosystem or determining where an AI product is structurally defensible. Those require other lenses.

Best strategic questionWhat is the critical challenge we must solve, and what coherent response are we making?

3. Jobs to Be Done

Associated with Clayton Christensen and Bob Moesta.

Jobs to Be Done changes the unit of analysis. Instead of beginning with a demographic segment or a feature request, it asks what progress a customer is trying to make in a particular circumstance. The Christensen Institute describes JTBD as a lens for understanding the forces that cause people or organizations to move toward or away from a decision, including functional, social and emotional dimensions.

That distinction explains why the framework remains so useful to product teams. A customer does not necessarily want a budgeting dashboard. They may want to feel in control of a financially uncertain business. A customer may not really want an AI meeting summarizer. They may want to walk into the next customer conversation without spending 45 minutes reconstructing what happened previously. The feature is not the job.

Why product leaders use it. JTBD tends to be particularly powerful in early product discovery; new-category creation; consumer products; marketplaces; products with weak differentiation; and businesses where customers describe solutions instead of underlying needs. Marketplace leaders often have to run the framework more than once because the buyer, seller and sometimes advertiser or creator have different jobs. That makes JTBD useful, but also exposes one of the recurring realities of product strategy: there may not be a single “user.”

Where it becomes insufficient. JTBD can tell you that a customer deeply wants something. It cannot tell you whether your company can capture the economics of delivering it. Nor does customer desirability automatically create competitive defensibility. A product can solve an important job and still be copied, bundled or commoditized. JTBD therefore becomes stronger when paired with a competitive framework such as Playing to Win, Wardley Mapping or — particularly for AI products — the Supply Chain of Intelligence.

Best strategic questionWhat progress is the customer actually trying to make?

4. The Product Strategy Stack

Originators: Ravi Mehta and Zainab Ghadiyali.

The Product Strategy Stack addresses a different failure mode: the gap between company strategy and what teams actually build. Its hierarchy connects Company Mission → Company Strategy → Product Strategy → Product Roadmap → Product Goals. Ravi Mehta describes product strategy as the “connective tissue” between company objectives and product execution. The stack can be used top-down for planning and bottom-up to test whether execution is actually advancing the strategy.

This sounds straightforward. In practice, it solves one of the most common problems inside growing companies. Teams often have goals. They have roadmaps. They have Jira tickets. They may even have a mission statement. What is missing is the logic connecting them.

Why product leaders use it. The Product Strategy Stack becomes increasingly valuable as an organization scales. A founder can hold strategy in their head when six people sit around one table. That stops working when there are six product teams, three business units and quarterly planning across multiple functions. The Stack gives leaders a way to ask: why is this roadmap item here? If the answer cannot be traced upward through product strategy to company strategy, something is wrong. This is especially useful in Series B and beyond, large SaaS organizations and enterprises where multiple teams need enough autonomy to move quickly without creating strategic drift.

Where it becomes insufficient. The Stack is excellent at alignment. It is less useful for determining whether the strategy itself is good. A perfectly aligned organization can execute a weak strategy extremely efficiently. So the Product Strategy Stack often works best after another framework has helped make the strategic choices.

Best strategic questionHow does the work our product teams are doing connect back to company strategy?

5. The North Star Framework

Popularized for modern product organizations by Amplitude and product practitioners including John Cutler.

The North Star Framework moves the conversation from strategy statements to a measurable expression of customer value. A North Star Metric should capture the value users receive from the product, sit within the influence of product and growth teams, and act as a leading indicator of sustainable business results. The framework then identifies inputs teams can influence to move that outcome.

That distinction — North Star plus its input metrics — is important. The framework is not simply “pick one KPI.”

Why product leaders use it. It is especially effective when organizations have many teams optimizing different things. Activation wants onboarding completion. Growth wants acquisition. Engagement wants weekly usage. Monetization wants conversion. Engineering wants reliability. Each metric can improve while the product becomes worse. A thoughtful North Star creates a shared definition of value and then allows teams to attack different inputs beneath it. This explains why the framework has become particularly common in product-led businesses and scaled consumer or SaaS products — Amplitude itself notes its suitability for product-led organizations.

Where it becomes insufficient. Metrics are consequences of strategy, not substitutes for it. A North Star will not decide which market to enter. It will not tell a product leader whether an emerging competitor has changed the landscape. And selecting the wrong North Star can create a remarkably efficient organization optimizing the wrong behavior. This framework is strongest when the strategic direction is already reasonably clear.

Best strategic questionWhat measurable expression of customer value should align our product decisions?

6. Wardley Mapping

Originator: Simon Wardley.

Wardley Mapping introduces something most product frameworks largely ignore: movement. A Wardley Map places components of a value chain against their stage of evolution, allowing leaders to reason about dependencies, commoditization and how the competitive landscape may change.

Wardley’s official material emphasizes situational awareness: seeing dependencies, identifying strategic opportunities, anticipating market change and understanding where resources should be allocated. That makes it particularly valuable when a product does not exist in isolation. Which, increasingly, almost none do.

Why product leaders use it. Wardley Mapping is useful when strategy involves ecosystems, platforms, infrastructure or technologies evolving at different speeds. Enterprise architects and technically sophisticated product leaders often appreciate it because it forces them to look beyond the feature roadmap.

Consider an enterprise software company building capabilities that were differentiating five years ago but are rapidly becoming commodity infrastructure. The strategic question is no longer merely whether those capabilities are good. It is whether the organization should still invest scarce resources in owning them. That is classic Wardley territory.

Where it becomes insufficient. Wardley Mapping has a learning curve. It can also become intellectually satisfying while remaining far removed from customer discovery and day-to-day prioritization. For a small startup still trying to determine whether anyone wants the product, mapping an elaborate technology landscape can be premature. This is one reason framework choice changes with company maturity.

Best strategic questionWhat is changing around us, and where should we build versus consume?

7. Supply Chain of Intelligence™

Originator: Anand Arivukkarasu.

The newest framework in this group exists because AI introduces a strategic question the older frameworks were not designed to answer.

An AI product is rarely one thing. Its intelligence may depend on compute, models, proprietary data, retrieval, context, orchestration, domain workflows, verification, distribution and memory. The Supply Chain of Intelligence (SCoI) treats those dependencies as an economic system rather than simply a technology stack. Its core proposition is: intelligence is a supply chain — value accrues at the bottlenecks, not the most visible node.

The current framework maps that system across ten layers and fifty sublayers, from underlying resources through data, models, verification, workflow and memory, and uses the structure to reason about where value is created, captured and defended. One of its more useful principles is: Generation ≠ Verification. The model producing an answer is not necessarily the system capable of establishing whether that answer should be trusted. That distinction becomes economically important in areas such as healthcare, finance, legal workflows, compliance and high-consequence enterprise decision-making.

Why it is appearing in product-strategy conversations. Current product-leadership research shows why a framework like this has become relevant. Productboard found AI had become an explicit priority for virtually all of the product executives it surveyed, while Gartner’s 2026 analysis describes a CPO remit increasingly expanded by AI and reports expectations that a substantial portion of future growth will come from AI products. The problem is that conventional product strategy can establish desirability without necessarily establishing defensibility.

Suppose an AI startup discovers an important customer job and builds an excellent experience on top of a foundation model. JTBD may say the product solves a real need. Playing to Win may identify an attractive segment. North Star may give the team a strong measure of value. None of those questions automatically answer: what prevents the model provider from shipping this feature?

SCoI approaches the problem by asking which layers the company actually controls. Is the differentiation in proprietary data? A deeply embedded workflow? Evaluation and verification? Distribution? Institutional memory? A compounding feedback loop? Or is almost all of the value sitting in a model rented from somebody else? The framework’s own product-leader formulation contrasts demand with defensibility: JTBD helps establish what users want; SCoI asks where AI value can actually accrue.

Where it works particularly well. SCoI is most useful for AI-native startups; established software businesses adding AI to their core product; AI roadmap and architecture decisions; platform-dependency analysis; AI investment and diligence; products where verification or trust matters; and determining whether an AI feature can become a durable business. It is much less necessary for a conventional product where AI is incidental.

And it should not be mistaken for a complete product strategy. SCoI will not discover the customer job for you. It will not establish the company’s mission. It does not replace market selection or execution alignment. It adds a particular lens that has become materially more important as intelligence itself becomes part of the product. Because SCoI is an emerging 2026 framework, it would also be misleading to imply it has the decades of broad organizational adoption enjoyed by JTBD or Playing to Win. Its inclusion here is about the strategic problem it addresses, not historical prevalence. Its primary framework and early independent practitioner coverage are now publicly available, but its adoption should be evaluated over time.

Best strategic questionWhere in our intelligence supply chain does durable value actually accrue?

The most interesting finding: good product leaders rarely use just one framework

This may be the more useful conclusion than the list itself. Frameworks are often presented as competitors. Practitioners tend to use them more like lenses.

Consider an AI-native B2B startup. Jobs to Be Done can establish the progress the customer wants to make. Rumelt’s Kernel can identify the critical obstacle preventing the company from delivering that progress. Playing to Win can force the company to choose a market and competitive position. Supply Chain of Intelligence can test whether that position remains defensible as models and platforms evolve. North Star can translate the strategy into a measurable expression of customer value. Product Strategy Stack can connect that strategy to roadmaps and goals as the organization scales.

These frameworks are not answering the same question. That matters. The common mistake is not choosing the “wrong framework.” It is using a perfectly good framework to answer a question it was never designed to answer.

Framework choice changes with company maturity

The synthesis also suggests a fairly intuitive progression.

• Discovery. Early companies generally need to reduce customer uncertainty. Jobs to Be Done + Rumelt. What does the customer need, and what is the central problem we must solve?
• Product-market fit. Once demand becomes clearer, competitive choices become more important. Jobs to Be Done + Playing to Win. Which customers will we serve, and how will we win?
• Scale. As the organization grows, alignment becomes a strategic problem of its own. Product Strategy Stack + North Star. How does company strategy translate into distributed execution?
• Ecosystem complexity. Products dependent on large technology ecosystems need stronger situational awareness. Wardley Mapping + Playing to Win. Which capabilities are differentiating, which are becoming commodities, and where should we concentrate?
• AI defensibility. AI-native companies face another layer of uncertainty. JTBD + Playing to Win + Supply Chain of Intelligence. Is there demand? Can we win? And if we win, can we actually keep the value we create?

That last question is becoming much harder to ignore. Recent product-leadership surveys consistently show AI increasing the strategic burden on product organizations rather than simply making delivery faster. Productboard’s research, for example, found a gap between confidence in strategic decisions and consistently hitting goals, while broader 2026 research shows product leaders facing substantial pressure to accelerate AI adoption.

Faster engineering does not eliminate product strategy. It makes bad strategy cheaper to build.

Seven frameworks, seven different questions

There is no best product strategy framework

There is a best framework for the uncertainty you are trying to reduce.

If you do not understand the customer, use a customer lens. If the organization cannot agree on the real problem, diagnose it. If there are too many markets and opportunities, force strategic choices. If teams are disconnected from company direction, build the connective tissue. If execution lacks a common outcome, define the North Star. If the ecosystem is shifting underneath you, map it. And if intelligence itself has become part of the product, ask where the value in that intelligence supply chain actually comes from — and who will capture it.

That may be the biggest change in product strategy right now. For years, the primary product question was: can we create something customers value? Increasingly, particularly in AI, there is a second question: if we create that value, what makes it ours to keep?

The best product strategy framework increasingly depends on what kind of uncertainty the leader is trying to resolve — market, customer, competition, prioritization, business model, execution, or the supply chain of intelligence behind an AI product.