AI-Native Versus AI-Enabled: A Distinction of Architecture, Not Marketing

The first distinction a product leader must reason about precisely, because the market uses it loosely, is between AI-enabled and AI-native products. An AI-enabled product is one to which AI has been added as a feature while the product’s fundamental architecture and value proposition would survive the removal of that feature, whereas an AI-native product is one whose value proposition collapses entirely without AI because the intelligence is constitutive of what the product is rather than additive to it (Andreessen Horowitz, 2024). The test is counterfactual and clarifying: if the product would function essentially as before with the AI removed, it is AI-enabled, and if its core reason for existing disappears, it is AI-native. The strategic significance of the distinction is that AI-enabled features, being additive, are the most easily replicated and therefore the least defensible, since a competitor can add the same feature to its own product, while AI-native products, being architecturally reorganized around intelligence, can pursue value propositions and workflows that incumbents bolting AI onto legacy architectures cannot match.

The deeper implication, which connects to the blue ocean and disruption logic of earlier modules, is that the most consequential AI opportunities are typically AI-native reconceptions of a category rather than AI-enabled enhancements of an existing product, because the native architecture can eliminate the assumptions the legacy product was built around. A product leader who frames the AI question as how to add AI features to the current product is, by the structure of the question, confined to the less defensible position, whereas one who asks what the product would be if rebuilt around intelligence from the foundation is positioned to find the durable opportunity.

Agentic Systems: From Assistance to Execution

The most significant capability shift within the AI transition is the move from systems that assist a human performing a task to systems that execute the task autonomously, which is the domain of agentic products. An agentic system is one that pursues a goal through a sequence of actions, invoking tools, making decisions, and adapting to results with limited human intervention, and the strategic consequence of this shift is that the unit of value moves from augmenting human productivity to performing the work itself. This relocates the competitive battleground in two directions at once, as the analysis of the current environment suggests: defensibility shifts downward toward the data models, permissions, workflow logic, and compliance infrastructure that autonomous execution requires, and upward toward the networks, proprietary data generation, and real-world execution that agents enable (Andreessen Horowitz, 2024).

For the product leader, the rise of agentic systems poses both the largest opportunity and the largest substitution threat reasoned about in Module 10, since a sufficiently capable general-purpose agent is the substitute that can absorb the job a specialized product performs. The strategic response is to determine whether the product is positioned to be the agent that executes the valuable workflow, in which case the opportunity is to own end-to-end execution, or whether it is positioned to be a capability the agent invokes, in which case the opportunity is to become an indispensable tool in the agent’s repertoire, accessible through the interfaces that autonomous systems use. The error is to assume the product can remain a human-operated interface in a domain where execution is migrating to agents, since that is the position most exposed to substitution.

Commoditization Risk: The Defining Condition of the Environment

The condition that organizes all AI strategy is that foundation model capability is commoditizing, which means that the raw intelligence a product can access is becoming abundant, broadly available, and decreasingly differentiated across providers and over time. The strategic consequence, stated bluntly by the analysis emerging from the venture community, is that using a capable model or adding an agent is easy to replicate and therefore is not a moat, however impressive the capability may be (Andreessen Horowitz, 2024). A product whose differentiation rests solely on access to model capability is building on a commodity, and as the commodity becomes more capable and more widely available, that differentiation erodes toward zero, which is the fate awaiting the large population of products that are thin wrappers over a rented model. The product leader must internalize that the model is the engine but not the moat, and that strategy in this environment is precisely the work of building advantage that does not reside in the commoditizing layer.

This condition also reframes the supplier-power analysis of Module 10 into a defining strategic risk, since dependence on a commoditizing capability supplied by concentrated providers means that the value a product adds must be located somewhere the provider does not capture, lest the provider, by improving its base offering, absorb the product’s reason for existing. The history of platform shifts is replete with applications rendered obsolete when the platform incorporated their function, and the AI equivalent is the product whose entire value is a capability the next model release will provide natively.

Where Defensibility Actually Resides

The constructive core of AI strategy is the identification of the layers where advantage survives commoditization, and the convergent finding across the most credible analyses is that defensibility lives not in the model but in the assets and relationships that surround it. The first such asset is the proprietary data feedback loop, which becomes more valuable in an AI world rather than less, because when the model is the commodity the scarce input becomes the proprietary data that specializes it, and a product whose usage generates data no competitor can observe builds a model advantage that widens with scale (V7 Labs, 2024). This is the data network effect of Module 14 expressed as the central AI moat, and it is the single most reliable source of durable advantage available to an AI product.

The second is workflow ownership and embedding, the depth to which a product is woven into the systems of record, the daily practices, and the surrounding tools of its customers, since a product that owns an end-to-end workflow and serves as the system of record accrues switching costs that a competitor renting the same model cannot overcome (Andreessen Horowitz, 2024). The third is the network effect among the product’s users, which an AI agent cannot replace, because the value that arises from the presence of other people, as in collaboration and communication products, is not a capability a model can synthesize away (Bain & Company, 2025). The fourth is trust and the surrounding evaluation, governance, and reliability infrastructure, which becomes a durable differentiator precisely because AI outputs are probabilistic and consequential, so that the product which has earned trust and built the mechanisms that sustain it holds an advantage that is slow to accumulate and therefore slow for competitors to replicate.

A sober note belongs here, since the enterprise reality tempers the enthusiasm: a substantial fraction of agentic projects are forecast to be abandoned without clear value, guardrails, and change management, and the majority of firms have struggled to scale AI beyond pilots (Bain & Company, 2025). The strategic implication is that the defensibility which matters is not demonstrated capability but realized, governed, trusted value in production, which is a far higher bar and one that the surrounding infrastructure, rather than the model, determines.

The synthesis that closes both this module and the series is that AI strategy is the discipline of building durable advantage in an environment where the core capability is rented and commoditizing, which returns the product leader to the classical frameworks rather than away from them. The agenda is to pursue AI-native reconceptions rather than AI-enabled additions, to position deliberately within the shift toward agentic execution rather than be substituted by it, to internalize that the model is an engine and never a moat, and to build defensibility in the layers that survive commoditization, namely proprietary data loops, workflow ownership and embedding, network effects, and trust infrastructure. The product leaders who will define the next decade are not those with access to the best model, since that access is becoming universal, but those who understand that in an age of rented intelligence, durable advantage is built in everything that surrounds the intelligence, which is exactly the strategic work the preceding nineteen modules were preparing them to do.

References

Andreessen Horowitz. (2024). Who owns the generative AI platform? https://a16z.com/who-owns-the-generative-ai-platform/

Bain & Company. (2025). Will agentic AI disrupt SaaS? https://www.bain.com/insights/will-agentic-ai-disrupt-saas-technology-report-2025/

V7 Labs. (2024). Are data moats dead in the age of AI? https://www.v7labs.com/blog/data-moats-a-guide

Agrawal, A., Gans, J., & Goldfarb, A. (2022). Power and prediction: The disruptive economics of artificial intelligence. Harvard Business Review Press.

Calibrating to the Level of Uncertainty

The first discipline, which Courtney et al. (1997) contribute and which most teams skip, is to diagnose how much uncertainty actually obtains before choosing how to respond, because the appropriate strategic posture differs by level. They distinguish a spectrum running from a future clear enough for a confident forecast, through a future with a small set of discrete possible outcomes, to a future with a bounded range of outcomes, and finally to genuine ambiguity in which even the range cannot be specified. The strategic error is to treat all uncertainty as though it were the first level, applying point forecasts to situations that demand scenarios or options, and the corrective is to match the instrument to the level, reserving confident forecasting for the rare cases that warrant it and deploying scenario and option methods where the future is genuinely plural. Owing to the pace of the AI transition, most product decisions now sit at the third or fourth level, where a bounded range or genuine ambiguity prevails, which is why the instruments that follow have become essential rather than optional.

Assumption Mapping: Exposing What a Strategy Depends On

Every strategy rests on assumptions, and the difference between a robust strategy and a fragile one is largely whether those assumptions have been made explicit and tested. Assumption mapping, developed as a core practice by Bland and Osterwalder (2019), is the discipline of surfacing the beliefs a strategy depends upon and arranging them by two dimensions, namely how important each assumption is to the strategy’s success and how much evidence currently supports it. The assumptions that are simultaneously most important and least evidenced are the ones that should be tested first, because they carry the greatest risk of invalidating the entire strategy and the team currently knows the least about them. The strategic value of this practice is that it redirects effort from building on unexamined beliefs to testing the beliefs on which everything else rests, which is the most efficient possible allocation of learning, since it resolves the largest uncertainty at the lowest cost before significant resources are committed.

The discipline this imposes on a product organization is to treat a strategy not as a plan to execute but as a set of hypotheses to validate, identifying the load-bearing assumptions, designing the cheapest experiments that would disconfirm them, and committing resources in proportion to the evidence accumulated rather than to the confidence asserted. In the context of AI, where strategies routinely rest on assumptions about how model capabilities will advance, how users will trust autonomous systems, and how quickly costs will fall, assumption mapping is the instrument that prevents an organization from building an elaborate strategy on a capability forecast it has never examined.

Scenario Planning: Preparing for Futures Rather Than Predicting One

Where assumption mapping tests the beliefs underlying a single strategy, scenario planning prepares an organization for multiple plausible futures, and its purpose is frequently misunderstood. The objective of scenario planning, as developed by Schoemaker (1995) from the practice pioneered at Shell, is not to predict which future will occur but to construct a small set of distinct, internally coherent narratives about how the future could unfold, so that the organization develops the perceptual range to recognize each as it emerges and the prepared responses to act when it does. The value lies in the process as much as the product, because the discipline of imagining several genuinely different futures breaks the organization’s habit of planning for a single extrapolation of the present, which is the habit that leaves it blindsided when the future diverges from the forecast.

The practice constructs typically three or four scenarios around the most important and most uncertain driving forces, develops each into a coherent story, and then stress-tests the strategy against all of them, asking which choices succeed across multiple futures and which depend on a single future obtaining. The strategic payoff is the identification of robust moves that perform acceptably across scenarios and the early-warning indicators that signal which scenario is materializing, which together convert an unpredictable future from a threat into a set of conditions the organization has already rehearsed. The AI transition is the canonical subject for this method, since its trajectory admits genuinely different futures regarding the pace of capability advance, the structure of the model-provider market, and the regulatory environment, and a product strategy that is robust across these scenarios is far more valuable than one optimized for the single future its authors happen to expect.

Optionality Thinking: Structuring Commitments to Preserve Flexibility

The third instrument reframes how commitments themselves are structured, drawing on the logic of real options and on Taleb’s (2012) argument that some strategies benefit from volatility rather than merely surviving it. Optionality thinking treats an investment not as a binary commitment to a forecast outcome but as the purchase of the right, without the obligation, to pursue an opportunity once uncertainty resolves, which means that under high uncertainty the most valuable moves are frequently those that buy information and preserve the ability to scale up or abandon cheaply rather than those that commit fully in advance. A strategy structured as a sequence of staged options, in which small investments resolve key uncertainties and earn the right to larger investments, dominates a strategy structured as a single large commitment when the future is genuinely plural, because it limits the downside of being wrong while preserving the upside of being right.

Taleb’s (2012) contribution is to distinguish strategies that are merely robust, surviving a range of futures unchanged, from those that are antifragile, gaining from the disorder, and to observe that a portfolio of small bounded-loss bets with unbounded upside is positioned to benefit from precisely the volatility that destroys strategies built on point forecasts. In the context of AI, optionality thinking counsels the product leader to make many small, staged, cheaply reversible bets on emerging capabilities rather than a single large bet on a predicted trajectory, since the trajectory is genuinely uncertain and the value of preserving the ability to pivot as it resolves is high.

The synthesis for the product leader is that strategy under uncertainty is not a weaker form of strategy but a more honest and ultimately more powerful one. The agenda is to first diagnose the level of uncertainty rather than defaulting to confident forecasting, to map and test the load-bearing assumptions on which the strategy depends before committing to it, to prepare for a small set of distinct futures through scenario planning rather than betting on a single extrapolation, and to structure commitments as staged options that preserve flexibility and limit downside while retaining upside. A product organization that adopts these instruments will make fewer confident pronouncements about the future and far better decisions within it, which, in a regime defined by a future that refuses to hold still, is the only durable form of strategic advantage.

References

Bland, D. J., & Osterwalder, A. (2019). Testing business ideas: A field guide for rapid experimentation. Wiley.

Courtney, H., Kirkland, J., & Viguerie, P. (1997). Strategy under uncertainty. Harvard Business Review, 75(6), 67–79. https://hbr.org/1997/11/strategy-under-uncertainty

Schoemaker, P. J. H. (1995). Scenario planning: A tool for strategic thinking. Sloan Management Review, 36(2), 25–40.

Taleb, N. N. (2012). Antifragile: Things that gain from disorder. Random House.

The North Star Metric: One Measure of Created Value

The north star metric, a framework associated with John Cutler and developed extensively at Amplitude, is the single measure that best expresses the value a product delivers to its customers, chosen so that the entire organization can align its work behind moving it (Amplitude, n.d.). The discipline of the north star is not that it reduces measurement to one number but that it forces an organization to articulate, in one quantity, what value it actually creates, which is a harder and more clarifying exercise than most teams expect. A well-chosen north star measures customer value rather than company extraction, which is why a measure such as the volume of meaningful work a product helps customers complete is a better north star than the revenue that value eventually produces, since the former is a cause the team can influence and the latter is an effect that arrives too late to steer.

Cutler offers a counterintuitive but essential criterion, which is that if a team can move its north star directly, it is probably not a good north star, because the purpose of the measure is to sit one level beyond direct manipulation so that it provokes the organization to reason about why it moves rather than to game it (Amplitude, n.d.). A north star that can be inflated by a single team’s tactical action is a metric the organization will inflate, whereas a north star that can only be moved by genuinely creating more customer value is a metric whose pursuit aligns the organization with its customers. The strategic function of the north star, therefore, is less measurement than alignment, providing a shared definition of value that coordinates otherwise divergent teams.

Leading and Lagging Indicators: The Architecture of Foresight

The deepest structural distinction in strategic measurement is between leading and lagging indicators, and the failure to observe it is the most common reason organizations learn the truth too late to act on it. A lagging indicator reports an outcome that has already occurred, such as revenue, retention realized over a past period, or churn already incurred, and its defining property is that by the time it moves, the events that determined it are complete and beyond influence. A leading indicator measures the behaviors and conditions that precede and predict the outcome, and its defining property is that it moves early enough that the organization can still act on what it foretells. The strategic discipline is to manage primarily by leading indicators while validating by lagging ones, since steering by lagging indicators alone is, as the metaphor goes, navigating by the wake.

The relationship between the two should be made explicit as a causal chain rather than left implicit, since a leading indicator earns its status only if there is a credible mechanism by which it produces the lagging outcome. The most rigorous measurement systems articulate the chain from the input behaviors a team can influence, through the leading indicators those behaviors move, to the lagging outcomes the business ultimately cares about, so that the organization understands not merely what it is measuring but why each measure should predict the next. A north star metric is typically positioned as a leading indicator of the lagging financial outcomes, which is precisely why revenue, a lagging indicator, makes a poor north star despite its obvious importance (Amplitude, n.d.).

The Revenue and Engagement Traps

Two specific traps corrupt strategic measurement so reliably that they deserve to be named. The first is the revenue trap, the temptation to elevate revenue or its proximate cousins to the central steering metric, which fails not because revenue is unimportant but because it is a lagging indicator on which, as Cutler observes, what is done is done, meaning that by the time revenue reflects a problem the opportunity to influence it has passed (Amplitude, n.d.). An organization that steers by revenue is perpetually reacting to outcomes it can no longer change, whereas an organization that steers by the leading indicators of customer value is acting while action still matters.

The second is the engagement trap, the elevation of engagement metrics such as time spent, sessions, or clicks to the status of success measures, which fails because engagement is not intrinsically valuable and is often inversely related to the value the customer actually seeks. A productivity tool whose users spend more time in it may be delivering more value or may be confusing them, and the raw engagement number cannot distinguish the two, which is what makes engagement a quintessential vanity metric, one that rises in a way that flatters the team while inspiring no action and predicting no durable outcome. Ries (2011) framed the underlying distinction as the difference between vanity metrics that look impressive and actionable metrics that inform decisions, and the diagnostic Cutler offers is precise: if a number rises and the only response is satisfaction, and if it falls and the team does not change its strategy, it is a vanity metric regardless of how prominent it sits on the dashboard.

Strategic Measurement in the Age of AI

The AI transition sharpens every one of these distinctions and introduces a specific new hazard. The hazard is that AI products generate seductive engagement and adoption signals, since novelty drives high initial usage that registers as success on exactly the engagement metrics most prone to the vanity trap, which means an AI feature can appear to be winning on the dashboard while retaining no one. The corrective is to insist that the north star measure realized customer value rather than interaction volume, and to weight the leading indicators of durable value, such as whether users return to accomplish meaningful work after the novelty fades, over the engagement spike that novelty produces. The transition also raises the importance of measuring outcome quality directly, because an AI product’s value depends on whether its outputs are correct and trusted, which is a dimension that conventional engagement and revenue instruments do not capture and which must be measured deliberately if the team is to know whether the product is genuinely working.

The synthesis for the product leader is that strategic measurement is the deliberate construction of a system that measures what compounds rather than what comforts. The agenda is to anchor the organization on a north star that expresses created customer value and sits one level beyond direct manipulation, to architect the measurement system as an explicit causal chain from influenceable inputs through leading indicators to lagging outcomes, to refuse the revenue trap of steering by a lagging financial measure and the engagement trap of celebrating interaction volume as though it were value, and to recognize that the AI transition makes vanity signals more seductive and outcome quality more essential to measure. A product organization that measures this way will sometimes report less flattering numbers than one optimizing for vanity, and it will be the one that knows, early enough to act, whether it is actually winning.

References

Amplitude. (n.d.). The North Star playbook: The guide to discovering your product’s North Star [J. Cutler]. https://amplitude.com/north-star

McClure, D. (2007). Startup metrics for pirates (AARRR).

https://500hats.typepad.com

Ries, E. (2011). The lean startup: How today’s entrepreneurs use continuous innovation to create radically successful businesses. Crown Business.

The Three Horizons: Allocating Across Time

The foundational portfolio framework is the three horizons model articulated by Baghai, Coley, and White (1999), which distinguishes investments by their temporal distance from current returns. The first horizon comprises the core business that generates current revenue and demands continual defense and optimization; the second horizon comprises emerging opportunities that are not yet profitable but are on a credible path to becoming the next core; and the third horizon comprises options on genuinely new businesses whose viability is uncertain and whose returns, if any, lie far in the future. The value of the framework is that it makes the temporal balance of the portfolio visible, and its central warning is that organizations naturally over-invest in the first horizon because its returns are immediate and measurable, while starving the second and third horizons whose returns are deferred and uncertain, thereby mortgaging the future to optimize the present.

The discipline the framework imposes is to fund all three horizons concurrently rather than sequentially, since an organization that waits until the core declines before investing in the next horizon will find that the second-horizon business it needed required years of cultivation it failed to begin. The horizons are not stages a company passes through but parallel investments it must sustain simultaneously, and the product leader’s task is to ensure that the portfolio carries live bets in all three at all times, with the recognition that the horizons themselves are compressing as technological change accelerates.

Core, Adjacent, and Transformational: Allocating Across Novelty

Where the three horizons organize the portfolio by time, the innovation ambition matrix introduced by Nagji and Tuff (2012) organizes it by novelty, distinguishing core initiatives that optimize existing products for existing customers, adjacent initiatives that extend the business into new markets or new capabilities, and transformational initiatives that create new offerings for markets that do not yet exist. The two frameworks are complementary lenses on the same portfolio rather than competitors, since novelty and time correlate but are not identical, and reasoning about both prevents the common error of treating a long-dated incremental project as though it were genuinely transformational.

The empirical contribution of Nagji and Tuff (2012) is the most quoted and least heeded finding in portfolio management, which is that across the companies they studied, a balanced allocation of roughly seventy percent of innovation resources to core, twenty percent to adjacent, and ten percent to transformational correlated with superior share-price performance, while, in a striking asymmetry, approximately seventy percent of the long-term return came from the transformational ten percent. The strategic implication of this asymmetry is profound: the small fraction of the portfolio that organizations most readily cut under pressure is the fraction that generates the disproportionate share of long-run value, which means that the discipline of protecting the transformational allocation is not a luxury of well-resourced firms but the mechanism by which durable returns are actually produced. The authors are careful, and the product leader should be too, that the specific ratio is a reference point rather than a law, since the appropriate allocation varies by industry, competitive intensity, and company stage; the discipline is to know the current allocation, to set a deliberate target, and to manage the gap, rather than to discover after the fact that the portfolio drifted entirely into the core.

Innovation Allocation as an Act of Will

The reason allocation must be treated as a deliberate act rather than an emergent outcome is that the organizational forces acting on a portfolio all push in the same direction, toward the core. Core initiatives have clearer business cases, more confident estimates, more vocal internal advocates, and more immediate metrics, which means that in any unmanaged prioritization process they will crowd out adjacent and transformational work by appearing more rational at every individual decision point. Owing to this systematic bias, a portfolio left to optimize itself will converge on the present, which is why the allocation must be set as a budget and defended as a commitment, insulated from the quarter-to-quarter pressure that would otherwise consume it. The product leader who does not ring-fence the transformational allocation will not have one, regardless of stated intentions, because the sum of locally rational decisions will spend it on the core.

Portfolio Thinking in the Age of AI

The AI transition acts on portfolio thinking in two consequential ways. The first is that it compresses the horizons, moving capabilities that would recently have been third-horizon bets, such as autonomous agents performing end-to-end workflows, into the second and even the first horizon within a single planning cycle, which means that the temporal distance the framework assumes is shorter than it has historically been and the cost of neglecting the transformational allocation is incurred sooner. The second is that it raises the stakes of the transformational bet specifically, because AI-native reconceptions of a category tend to be transformational rather than incremental, which places the most important AI opportunities precisely in the portfolio quadrant that organizational gravity most reliably starves. A product organization that runs its AI work entirely as core optimization, adding features to the existing product, will find that the genuinely transformational AI opportunity was located in the quadrant it declined to fund, and that a competitor willing to make the transformational bet has redefined the category.

The synthesis for the product leader is that portfolio thinking is the antidote to the local optimization that prioritization alone cannot prevent. The agenda is to maintain live bets across all three horizons concurrently rather than sequentially, to allocate deliberately across core, adjacent, and transformational novelty with explicit awareness that the transformational fraction generates the disproportionate long-run return, to defend the transformational allocation as a ring-fenced budget against the organizational gravity that would consume it, and to recognize that the AI transition has both compressed the horizons and concentrated the most important opportunities in the transformational quadrant. A portfolio managed this way will feel less efficient quarter to quarter than one optimized entirely for the core, and it will be the one that is still relevant when the regime changes.

References

Baghai, M., Coley, S., & White, D. (1999). The alchemy of growth: Practical insights for building the enduring enterprise. Perseus Books.

Nagji, B., & Tuff, G. (2012). Managing your innovation portfolio. Harvard Business Review, 90(5), 66–74. https://hbr.org/2012/05/managing-your-innovation-portfolio

Christensen, C. M. (1997). The innovator’s dilemma: When new technologies cause great firms to fail. Harvard Business School Press.

Cost of Delay: The Quantity That Should Govern Sequencing

The single most important concept in economic prioritization is cost of delay, which Don Reinertsen (2009) elevated to the central place in product economics with the instruction that if a team quantifies only one thing, it should quantify the cost of delay. Cost of delay is the value foregone for each unit of time that a valuable outcome is postponed, and its power is that it converts the abstract question of importance into a concrete economic quantity. When a capability would generate a given value per month once shipped, every month of delay forfeits that value irretrievably, which means that the true cost of a feature includes not only the resources to build it but the accumulated value lost while it remained unbuilt. The reason this matters strategically is that teams routinely optimize for the size of the prize while ignoring the meter that runs against them, and a portfolio sequenced without regard to cost of delay will systematically deliver value later than necessary even when every individual decision looked reasonable.

Reinertsen’s (2009) operational contribution is to combine cost of delay with the duration of work into a sequencing rule, weighted shortest job first, which orders work by dividing the cost of delay by the job size so that items with the highest economic urgency per unit of effort are delivered first. The Scaled Agile Framework later formalized the cost-of-delay numerator as a sum of business value, time criticality, and risk reduction or opportunity enablement, divided by job size, which gives teams a tractable means of estimating relative urgency without spurious precision (Scaled Agile, n.d.). The strategic value of this rule is that it makes the meter visible: it forces the team to ask not merely what is most valuable but what is most valuable per unit of time it consumes, which is the only question whose answer maximizes the value delivered across a constrained schedule.

Opportunity Cost: The Discipline of Reasoning About the Road Not Taken

Cost of delay measures the price of postponing a chosen item; opportunity cost measures the price of the items not chosen, and it is the concept that most distinguishes strategic prioritization from backlog management. Every decision to build something is simultaneously a decision not to build everything else the same resources could have produced, and the true cost of any initiative is the value of the most valuable alternative it displaces. The reason this is so easily neglected is that the displaced alternative is invisible: it generates no failure to point to, no metric that declines, only a value that was never created and therefore never missed. The strategic discipline is to make the invisible alternative explicit by requiring, for any significant commitment, an articulation of what the team is choosing not to do as a consequence, since a commitment whose opportunity cost cannot be named is a commitment that has not been genuinely reasoned about.

In the context of AI, opportunity cost has sharpened considerably, because the menu of credible alternatives has expanded and the relative value of items on it is changing quarter to quarter as model capabilities advance. A capability that was uneconomical to build last year because it required bespoke machine learning may now be assembled atop a foundation model in a fraction of the time, which means the opportunity cost of every other backlog item has risen, since the resources spent elsewhere now displace newly cheap and valuable AI capabilities. The product leader who is not periodically re-pricing the backlog against this shifting menu is, in effect, paying an opportunity cost that compounds silently.

Strategic Bets Versus Incremental Bets

The deepest error in prioritization is to apply a single economic logic to two categories of decision that require different logics, namely incremental bets and strategic bets. Incremental bets are improvements to a known product serving a known market, where the value is estimable, the risk is modest, and the cost-of-delay and weighted-shortest-job-first machinery applies cleanly, because the quantities can be estimated with enough confidence to sequence on. Strategic bets are commitments to a new capability, market, or business model where the value is genuinely uncertain, the time horizon is long, and the principal return is not the immediate value but the option the bet creates and the learning it produces. Subjecting a strategic bet to the same near-term economic scoring as an incremental feature will almost always rank it poorly, because its near-term value is low and uncertain by construction, which is precisely how organizations systematically starve the bets that determine their future while feeling rigorous for doing so.

The strategic discipline, therefore, is to separate the two budgets and to evaluate them on different criteria, scoring incremental bets on economic urgency per unit of effort and evaluating strategic bets on the magnitude and durability of the advantage they could create and the cost of learning whether they will. This separation is the operational link between prioritization and the portfolio thinking developed in the next module, since a backlog that mixes the two categories on one ranked list will reliably under-invest in the transformational work, given that incremental items will always present a more favorable near-term ratio.

The Synthesis for the Product Leader

The agenda this module sets for the product leader is to treat prioritization as applied economics rather than as list management. The first discipline is to quantify cost of delay, even roughly, so that the meter running against every delayed item becomes visible and sequencing reflects value delivered over time rather than value in isolation. The second is to name the opportunity cost of every significant commitment, making the displaced alternative explicit so that the road not taken is reasoned about rather than ignored, with particular attention to how the AI transition has raised the value of the alternatives the backlog displaces. The third is to refuse to evaluate strategic bets and incremental bets on a single ranked list, separating their budgets and their criteria so that the organization does not starve its future to optimize its present. A product leader who institutionalizes these three disciplines will find that prioritization stops being a recurring negotiation over a spreadsheet and becomes what it should be, namely the deliberate economic allocation of the only resource that cannot be replenished.

References

Reinertsen, D. G. (2009). The principles of product development flow: Second generation lean product development. Celeritas Publishing.

Scaled Agile. (n.d.). Weighted shortest job first (WSJF). https://framework.scaledagile.com/wsjf

Christensen, C. M. (1997). The innovator’s dilemma: When new technologies cause great firms to fail. Harvard Business School Press.

APIs as Product, Not Plumbing

The most consequential reframing in this module is that an application programming interface is a product with its own users, value proposition, and growth dynamics, rather than a technical afterthought. The clearest demonstration of this principle is the mandate Jeff Bezos is reported to have issued at Amazon, requiring that all teams expose their data and functionality exclusively through service interfaces, that these interfaces be designed to be externalizable as if outside developers would consume them, and that no team communicate through any other path. The strategic effect of this discipline was profound: by forcing every internal capability to be expressed as a clean, externalizable service, Amazon created the architectural precondition for externalizing its computing infrastructure entirely, first internally and then to the world as Amazon Web Services, which became one of the most valuable businesses in technology (Nordic APIs, 2021). The lesson for the product leader is that treating APIs as products, with the same attention to developer experience, documentation, and reliability that one gives a user-facing surface, converts internal capability into a platform for external value creation.

The mechanism by which an API creates leverage is that it lets parties the product does not employ build value on the product’s behalf, which means the rate of value creation is no longer bounded by the product team’s own capacity. The metric that captures this leverage is the number of consumers building on the interface relative to the effort of maintaining it, since a well-designed API that many developers depend upon generates compounding value and switching costs that a closed product cannot match.

Partnerships and the Logic of Complementarity

Partnerships are the second lever, and their strategic logic is complementarity rather than mere co-marketing. A partnership creates durable value when each party supplies something the other cannot easily build and when the combination is worth more to the customer than either alone, which is a more demanding test than the logo-exchange partnerships that fill many slide decks. The product leader’s discipline is to evaluate a prospective partnership by asking what asset the partner controls that the product genuinely cannot replicate, whether the partner’s incentives are durably aligned with the product’s, and whether the integration deepens over time into mutual dependence or remains a shallow connection either party can sever without cost. The partnerships that matter strategically are those that embed the product into a workflow or distribution channel the partner controls, because that embedding becomes a switching cost for the customer and a barrier for the rivalry.

Distribution Leverage: The Force Multiplier PMs Underuse

Distribution leverage is the lever product leaders most consistently underweight, owing to a cultural conviction that a sufficiently good product distributes itself, which is true far less often than builders wish. The strategic reality is that the channel through which a product reaches users is frequently more decisive than the product’s marginal quality advantage, because a product that is slightly worse but embedded in a channel the customer already inhabits will defeat a product that is slightly better but requires the customer to discover and adopt it independently. Ecosystem strategy treats distribution as a deliberate design problem: integrating into the marketplaces, app directories, and platforms where the target customer already transacts converts the platform’s installed base into the product’s distribution, which is leverage no advertising budget can match. The product leaders who understand this seek out the channels their customers already trust and design the product to be discoverable and installable within them, rather than building in isolation and hoping for unaided demand.

Platform Expansion and the Sequencing of Ambition

Platform expansion is the fourth lever and the most ambitious, describing the move from a product that serves a use case to a platform that hosts an ecosystem of use cases built by others. The sequencing of this ambition is where most attempts fail, because a product that opens itself to third-party developers before it has achieved sufficient value and scale on its own offers those developers no audience worth building for, which means the platform’s network effect cannot ignite. The durable pattern, visible across the products that successfully became platforms, is to first win decisively as a product, accumulating the user base that makes the platform attractive, and only then to open the surfaces that invite external builders, so that the platform launches into demand rather than into emptiness. Premature platform ambition is a recurring and expensive error, and the product leader’s discipline is to recognize that platform expansion is earned by product success rather than substituted for it.

Ecosystem Strategy in the Age of AI

The AI transition raises the strategic weight of ecosystem strategy because it simultaneously commoditizes capability and reshapes distribution. As foundation models make raw capability broadly available, the differentiation that survives shifts toward integration depth, namely how deeply a product is embedded in the systems of record, workflows, and data sources where work actually happens, since this embedding is precisely what a competitor renting the same model cannot quickly replicate. At the same time, a new and consequential distribution surface is emerging in the form of agentic systems that act on a user’s behalf, which raises the prospect that the relevant ecosystem to integrate into is no longer only the human-facing application directory but the set of protocols and interfaces through which autonomous agents discover and invoke capabilities. The product leader who anticipates this is asking not only how human users will find the product but how an agent will, and is designing the product’s interfaces to be invokable by autonomous systems, which is the contemporary equivalent of designing for the API economy a decade ago.

The synthesis is that ecosystem strategy has moved from a peripheral concern to a central determinant of defensibility, precisely because the AI transition has eroded the feature-level differentiation on which many products previously relied. The product leader’s agenda is therefore to treat APIs as products, to pursue partnerships on the demanding test of genuine complementarity, to design distribution as deliberately as one designs features, to sequence platform expansion so that it launches into earned demand, and to extend all of this to a world in which agents as well as humans are the users a product must reach. In an era when capability is rented, the ecosystem is the product, and the leaders who internalize this will compete on a dimension their feature-focused rivals do not yet recognize as the battleground.

References

Cusumano, M. A., Gawer, A., & Yoffie, D. B. (2019). The business of platforms: Strategy in the age of digital competition, innovation, and power. Harper Business.

Nordic APIs. (2021). The Bezos API mandate: Amazon’s manifesto for externalization. https://nordicapis.com/the-bezos-api-mandate-amazons-manifesto-for-externalization/

Parker, G. G., Van Alstyne, M. W., & Choudary, S. P. (2016). Platform revolution: How networked markets are transforming the economy and how to make them work for you. W. W. Norton.

A Network Effect Is Not One Thing

The foundational correction is definitional: a network effect exists when each additional user makes the product more valuable to other users, and the strength of the effect, which is what determines defensibility, varies enormously by type. NFX’s taxonomy is useful precisely because it ranks these effects by durability, observing that physical and protocol-based effects tend to be the most defensible because they combine the direct network effect with additional barriers such as capital intensity and embedding, while social and personal-utility effects, though real, are more contestable (Currier, 2018). The product leader’s first task is therefore diagnostic, since the design implications of a marketplace effect, in which buyers attract sellers and sellers attract buyers, differ fundamentally from those of a data network effect, in which usage improves a shared model that benefits all users, which differ again from a personal-utility effect, in which the product becomes valuable because the people one personally needs to reach are present.

Currier (2018) further argues that network effects are best understood as one of a small set of structural defensibilities, alongside brand, embedding, and economies of scale, and that the strongest businesses stack several together so that each reinforces the others. This stacking insight matters for product strategy because it reframes the goal from possessing a single network effect to architecting a system in which a network effect, switching costs, and scale advantages compound, which is far harder for a competitor to assail than any one of them alone.

Marketplace Dynamics and the Cold Start Problem

Marketplaces are the canonical two-sided network effect, and their dynamics expose the central difficulty of all network-effect businesses, which is that the same mechanism that makes them defensible at scale makes them nearly worthless at the start. A marketplace with no sellers offers nothing to buyers and a marketplace with no buyers offers nothing to sellers, so the network effect runs in reverse before it runs forward. Andrew Chen (2021) frames this as the cold start problem and argues that it is solved not by launching the whole network but by igniting a small, dense, self-sustaining cell of the network, an atomic network, in which the effect is locally positive even though the global network is empty. The historical pattern confirms the logic: marketplaces and social products that endured typically seeded a narrow segment first, such as a single city, a single campus, or a single category, and only generalized once the atomic network could stand on its own.

The strategic implication for the product leader is that network-effect businesses require a different sequencing discipline than feature businesses, because the early roadmap must prioritize achieving critical density within a deliberately narrow segment over breadth, and metrics must be read per atomic network rather than in aggregate, since healthy local density can be masked by sparse global numbers and sparse local density can be flattered by broad but disconnected adoption.

Platform Strategy and Defensibility

A platform extends the network-effect logic by opening the product to third parties who build on top of it, converting a product into an ecosystem in which the platform’s value grows with the contributions of complementors rather than only with its own development. Parker, Van Alstyne, and Choudary (2016) characterize the resulting shift as a move from controlling a linear value chain, in which a firm creates value and ships it downstream, to orchestrating an ecosystem, in which the firm’s principal task is to facilitate value-creating interactions among participants it does not own. The defensibility of a platform comes from the combination of the network effect among its participants and the accumulated investment those participants have made in building upon it, which together raise switching costs to a level no feature comparison can overcome. The enduring examples, in which independent developers, complementary hardware, and a large installed base mutually reinforce one another, demonstrate that platform defensibility is a property of the ecosystem’s structure rather than of any single product decision.

Network Effects and Platforms in the Age of AI

The AI transition acts on network effects in two opposing directions that a product leader must reason about carefully. In the first direction, AI threatens certain network effects by lowering the value of aggregated content and the friction of switching, since a sufficiently capable model can synthesize what a content network previously made uniquely available, which weakens the personal-utility and content-aggregation effects that some products relied upon. In the second direction, AI introduces and strengthens the data network effect, in which accumulated usage data trains a model that improves the product for all users, and this effect is particularly powerful because, unlike a rented foundation model, the proprietary data and the specialized model it produces are assets a competitor cannot acquire by renting the same base capability. The most defensible AI products will be those that convert their network into a data network effect, so that scale produces a model advantage that widens with each additional user, while the least defensible will be those whose only network is one that a general-purpose model can now route around.

The synthesis for the product leader is that network effects remain the strongest available defensibility in the digital economy, but that the AI transition has reordered which types are durable and has raised the premium on stacking. A product whose advantage rests on a single contestable network effect is more exposed than its leaders typically believe, because AI is precisely the force that contests it; a product that stacks a network effect with a proprietary data loop, switching costs from embedding, and scale economics builds an architecture that the rivalry, even when armed with the same models, struggles to replicate. The discipline, therefore, is to treat network effects not as a fortunate property the product happens to have but as an architecture the product leader is responsible for designing, diagnosing by type, igniting locally, and reinforcing by stacking, with full attention to how the AI transition strengthens some layers of that architecture and erodes others.

References

Chen, A. (2021). The cold start problem: How to start and scale network effects. Harper Business.

Currier, J. (2018). The network effects manual: 16 different network effects (and counting). NFX. https://www.nfx.com/post/network-effects-manual

Parker, G. G., Van Alstyne, M. W., & Choudary, S. P. (2016). Platform revolution: How networked markets are transforming the economy and how to make them work for you. W. W. Norton.

The Structural Defect of the Funnel

The funnel’s defect is not that it is wrong about conversion; it is that it is silent about reinvestment. A funnel is, in mathematical terms, additive: if marketing delivers a constant number of new prospects each month and conversion rates hold, the business grows linearly, and growth stalls the moment the input spend stalls (Reforge, 2017). This produces a recognizable organizational pathology in which growth becomes synonymous with budget, every increment of growth requires a proportional increment of spend, and the team is perpetually buying its next cohort rather than earning it. The funnel also fragments the organization, because it encourages separate teams to optimize separate stages, each improving its local conversion rate while no one owns the question of how the whole system perpetuates itself.

A growth loop reframes the unit of analysis from the stage to the cycle. Rather than asking how a prospect moves down a funnel, the loop asks how one cohort of users produces the next cohort of users, and it closes the system by specifying how the output of one cycle is reinvested as the input of the next (Reforge, 2017). The difference is the difference between additive and compounding: when each user reliably generates a fraction of a new user, growth is geometric rather than linear, and the system gains momentum from its own scale rather than depleting a budget. The strategic consequence is that loops, because they integrate product, channel, and monetization into a single self-reinforcing system specific to one company, are markedly harder for competitors to replicate than any single funnel optimization.

Why Loops Matter Strategically, Not Just Tactically

The reason this distinction belongs in a strategy module rather than a growth-tactics playbook is that the choice of loop determines the shape of the entire business, not merely the efficiency of its marketing. A product whose dominant loop is content-driven, in which users generate content that ranks in search and attracts new users who generate more content, will build different teams, accumulate different assets, and defend itself differently than a product whose dominant loop is viral, in which users invite other users directly, or one whose dominant loop is paid, in which revenue from current users funds acquisition of the next. Pinterest and Quora grew principally through content loops in which user-generated pages compounded organic discovery; Dropbox grew through a viral loop in which the act of sharing files recruited the recipients; PayPal seeded a referral loop with direct financial incentives that turned each user into an acquisition channel. The strategic act is to identify which loop the product’s value creation naturally produces and to invest in deepening it, rather than attempting to operate every loop weakly.

Virality as a Property of the Loop, Not an Add-On

Virality is frequently misunderstood as a feature to be bolted on, a referral widget added late to a product whose core offers no native reason to share. The loop framing corrects this by treating virality as a structural property: a viral loop compounds only when the product’s core action inherently exposes or recruits new users, such that growth is a byproduct of use rather than a separate behavior the user must be cajoled into. The viral coefficient, the average number of new users each existing user generates, and the cycle time over which they generate them, jointly determine whether the loop compounds or decays, and the durable cases are those where the sharing is intrinsic to deriving value, as collaboration tools demonstrate when inviting a collaborator is simply how the work gets done. Bolted-on referral mechanics rarely compound because they sit outside the value-creating action and therefore decay as soon as the incentive is withdrawn.

Compounding Systems and the AI Transition

The AI transition reshapes growth loops in a way that makes the most powerful loop available to a new and larger class of products, namely the data-and-model loop. In this loop, usage generates data, the data improves the model, the improved model makes the product more valuable, the increased value attracts more usage, and the cycle compounds, with the distinctive feature that the reinvested output is product quality itself rather than only audience or revenue. This is the loop that confers the most durable advantage in AI products, because the accumulated, usage-derived data is the asset competitors renting the same foundation model cannot replicate. A product leader building anything AI-native should ask explicitly whether the product’s usage feeds a model improvement that no competitor can observe, because in its absence the product is renting capability that everyone can rent, and in its presence the product is building the one loop the rivalry cannot copy.

The same transition, however, introduces a sobering counterforce on the distribution side of the loop, which is that the channels many loops depend upon are themselves being reshaped by AI. Loops that compounded through search-indexed user-generated content now contend with AI-generated answers that satisfy the query without delivering the click, which compresses the organic distribution that powered the content loop for a decade. The strategic implication is not that content loops are dead but that the loop must be re-examined against the channel it actually runs on, since a loop whose distribution mechanism is being intermediated by a model will decay even when the product itself is excellent.

The practical agenda, then, is to stop drawing funnels as though they were strategy and to require, for any significant growth investment, an explicit statement of the loop it feeds: what the user does, what that action produces, how the product reinvests that output, and over what cycle time the reinvestment returns as new growth. A funnel optimization that does not strengthen a loop buys a cohort; a loop investment compounds. In a regime where capability is increasingly rented and rivalry is increasingly fast, the compounding system is the closest thing a product has to a structural advantage, and the discipline of building loops rather than funnels is how that advantage is deliberately, rather than accidentally, created.

References

Andreessen Horowitz. (2024). Who owns the generative AI platform? https://a16z.com/who-owns-the-generative-ai-platform/

Chen, A. (2021). The cold start problem: How to start and scale network effects. Harper Business.

Reforge. (2017). Growth loops are the new funnels [B. Balfour, C. Winters, K. Kwok, & A. Chen]. https://www.reforge.com/blog/growth-loops

The Myths That Distort the Concept

The most persistent myth is that fit is binary, a line a product crosses once. It is more accurately understood as a continuum measured per segment, since a product can hold strong fit with one customer profile while holding none with an adjacent one, and the strategic task is to locate the segment where fit is strongest before generalizing. The Superhuman case is instructive precisely because it rejected the binary view: rather than waiting for fit to announce itself, the team treated it as a quantity to be engineered, segmented users by how disappointed they would be to lose the product, and concentrated iteration on the segment and the reasons that moved the metric, raising their measured fit from thirty-three to fifty-eight percent over roughly a year (Vohra, 2018).

The second myth is that fit is a feeling. Andreessen (2007) did write that you can always feel when it is happening, but he paired the feeling with observable consequences, namely usage outrunning the ability to add servers and money piling up faster than it can be spent. The feeling is the lagging shadow of behavioral facts, and a discipline of measurement is what separates teams that know they have fit from teams that hope they do. The third myth, that fit once achieved is permanent, is the most dangerous in the present moment, because the conditions that confer fit are not static, and AI is moving them rapidly.

Signals of Fit: Survey Leading Indicators and Behavioral Confirmation

The strategic value of product-market fit lies in measuring it before the financials confirm it, which requires distinguishing leading from confirming signals. The most validated leading signal is the survey instrument popularized by Sean Ellis, which asks how users would feel if they could no longer use the product, with the benchmark that fit is plausibly present when at least forty percent respond that they would be very disappointed (Ellis, n.d.). Its value is that it is a leading indicator: it tends to anticipate whether retention and growth will be healthy, which means it can be read early enough to act on. The methodological refinement that makes it trustworthy is to ask only users who have genuinely experienced the core product, since surveying the indifferent contaminates the measure, a discipline Superhuman enforced by restricting the survey to recently active users (Vohra, 2018).

The confirming signal, the one that converts belief into evidence, is the shape of the retention curve. A cohort retention curve that declines and then flattens to a stable plateau is the behavioral signature of fit, because it demonstrates that a durable fraction of users find recurring value and stop churning; a curve that descends to zero is the signature of its absence, regardless of how strong acquisition looks (Chen, 2021). The two instruments are complementary rather than redundant: the survey reads fit early and per-segment, the retention curve confirms it in behavior over time, and a product leader who watches only one is either acting on sentiment without proof or learning the truth too late to change course.

Retention Versus Acquisition: The Locus of the Strategic Error

The single most consequential reframing in this module is that product-market fit is fundamentally a retention phenomenon, not an acquisition phenomenon, and that conflating the two produces a specific and common failure mode. Acquisition measures whether the market is willing to try the product; retention measures whether the product satisfies the market once tried. Owing to the abundance of paid and viral acquisition tactics, a product can manufacture impressive top-line growth while retaining almost no one, which presents as success and decays as a leaky bucket. The strategic error is to respond to weak fit by spending more on acquisition, which accelerates the rate at which the addressable market is consumed and disappointed, foreclosing the very audience a later, better version would need. The correct response to weak retention is to fix the product against a defined segment until the curve flattens, and only then to pour acquisition into a bucket that holds.

How AI Both Inflates and Erodes Fit

The AI transition complicates product-market fit in two opposing directions that a product leader must hold simultaneously. On one side, generative capability inflates apparent early fit, because novelty drives a spike of trial and enthusiastic initial usage that can register as strong adoption and even strong survey sentiment before the behavior matures. The risk is mistaking a novelty curve for a fit curve, since AI products are unusually prone to a pattern in which trial is high, the first week is delightful, and retention nonetheless collapses once the novelty fades and the reliability or workflow gaps surface. The corrective is to weight the flattening of the retention plateau over the height of the initial spike, and to measure fit on the cohort that has lived with the product long enough for novelty to have decayed.

On the other side, AI erodes fit that was genuinely attained, which is why permanence is the most dangerous myth in this regime. A product that earned a forty-percent very-disappointed score did so relative to the alternatives that existed when the score was taken; when a foundation model upgrade or a new agentic entrant raises the alternative, the same product can quietly lose fit without changing at all, because fit is a relation between the product and its substitutes and the substitutes are improving on a steep curve. The strategic implication is that product-market fit in the context of AI must be monitored as a maintained state rather than recorded as an achieved milestone, with the survey and retention instruments re-run on a cadence rather than filed after a single passing result. The product leaders who will struggle are those who declared fit once and built an acquisition engine on top of an assumption that the market has since revised. The ones who endure are those who treat fit as Andreessen (2007) implicitly framed it, as the continuously verified condition of being pulled by the market, and who never stop checking whether the pull is still there.

References

Andreessen, M. (2007). The Pmarca guide to startups, part 4: The only thing that matters. https://pmarchive.com/guide_to_startups_part4.html

Chen, A. (2021). The cold start problem: How to start and scale network effects. Harper Business.

Ellis, S. (n.d.). Using product/market fit to drive sustainable growth.

https://www.startup-marketing.com

Vohra, R. (2018, May). How Superhuman built an engine to find product/market fit. First Round Review. https://review.firstround.com/how-superhuman-built-an-engine-to-find-product-market-fit/

Red Ocean and Blue Ocean as Two Logics, Not Two Maturity Stages

The first clarification the framework demands is that red and blue oceans are not early and late phases of the same market; they are two different strategic logics. Red ocean logic accepts the industry’s boundaries and competitive factors as given and plays to win share within them, which structurally pushes participants toward differentiation at higher cost or cost leadership at lower differentiation, the classic trade-off Porter (2008) described. Blue ocean logic rejects the premise that this trade-off must hold. Kim and Mauborgne (2005) observe that in the markets they studied, the firms that created disproportionate new demand did not choose between value and cost; they pursued both simultaneously by changing which factors the product competed on at all. This pursuit of differentiation and low cost together is what they name value innovation, and it is the cornerstone of the entire framework.

The mechanism by which value innovation escapes the trade-off is specific and worth stating precisely. Cost is reduced by eliminating and reducing the factors an industry has long competed on and over-served; value is raised by creating and elevating factors the industry has never offered. When these two moves are made in the same stroke, the cost structure and the buyer value curve move in the same favorable direction rather than against each other. The instrument Kim and Mauborgne (2005) provide for this is the Eliminate-Reduce-Raise-Create grid, which forces a product team to specify, against the prevailing industry factors, what to eliminate entirely, what to reduce well below the standard, what to raise well above it, and what to create that did not previously exist.

Value Innovation Through the ERRC Grid: A Worked Logic

Consider how this applies to a category saturated with AI features. The instinct in a red ocean is to add: another model, another integration, another panel of generated suggestions, each addition raising cost and cognitive load while the buyer value curve converges with every competitor doing the same. The value-innovation move inverts this. Eliminating the dense configuration surfaces that an intelligent system can now infer reduces both cost and the buyer’s burden of expertise. Reducing the breadth of manual controls that existed only because earlier software could not make decisions removes complexity that no longer earns its place. Raising the reliability and transparency of the system’s outputs addresses the factor that the AI category most under-serves, namely trust. Creating an outcome the category never offered, such as the product completing the job rather than merely assisting with it, opens demand among buyers the category previously ignored. The discipline of the grid is that it requires subtraction, which is the move product teams resist most and which is precisely where the cost side of value innovation is won.

The canonical illustrations remain instructive because they show subtraction and creation operating together. Cirque du Soleil eliminated the animal acts and star performers that drove the circus industry’s cost base, reduced the multi-ring spectacle, and created a theatrical narrative and artistry that drew an adult audience willing to pay theater prices, thereby reconstructing the boundary between circus and theater (Kim & Mauborgne, 2005). Nintendo’s Wii reduced the raw processing power the console industry treated as its central battleground and created motion-based, socially accessible play that opened the market to non-gamers. In each case the firm competed less by reframing more.

Reframing Markets in the Age of AI

The AI transition is generative of blue oceans precisely because it lowers the cost of capabilities that were previously the exclusive, expensive province of specialists, and the strategically interesting question is which non-customers that newly affordable capability can convert. Kim and Mauborgne (2005) argue that blue oceans are found by looking beyond existing demand to the three tiers of non-customers: those who use the category minimally and reluctantly, those who have refused the category, and those who have never considered it. AI reframes markets most powerfully when it converts the second and third tiers by removing the expertise barrier that kept them out. Legal and tax software historically served professionals; an AI-native product that performs the reasoning rather than presenting tools for the professional to operate can address the far larger population who previously could not use such software at all. Design tooling long served designers; products that let non-designers express intent in language reframed the market by absorbing the tier that had refused the category as too difficult.

The caution that belongs alongside this optimism is that an apparent blue ocean built solely on a capability others can also rent is a blue ocean with a short tenancy. Because foundation models are broadly available, a reframing that depends only on access to model capability will be re-entered by competitors who rent the same capability, and the ocean reddens. The durable blue ocean pairs the reframing with an asset the reframing itself generates, such as proprietary data from the newly served customers, a workflow the product now owns end-to-end, or a community of non-customers-turned-customers whose presence compounds. The reframe opens the water; the accruing asset keeps it blue.

What the Product Leader Should Do With This

The practical agenda for a product leader is to institutionalize the blue ocean questions as a counterweight to the organization’s natural red ocean gravity. Roadmap reviews tend to reward parity and incremental superiority because those are legible and safe, which means the reframing move will not happen unless it is deliberately provoked. The provocation is to require, periodically, an explicit articulation of the category’s prevailing competitive factors, an ERRC grid that subtracts as aggressively as it adds, and a named tier of non-customers the reframed product intends to convert. It is also to hold the framework’s limit honestly: blue ocean reframing is harder to execute and riskier to validate than incremental improvement, and not every product is positioned to attempt it, so the framework is best understood not as a mandate to always reframe but as a discipline for recognizing when the larger prize lies in changing the game rather than winning the existing one. In the context of AI, where the temptation to crowd into the same red ocean has never been stronger, that discipline is among the more valuable a product organization can practice.

References

Kim, W. C., & Mauborgne, R. (2004). Blue ocean strategy. Harvard Business Review, 82(10), 76–84. https://hbr.org/2004/10/blue-ocean-strategy

Kim, W. C., & Mauborgne, R. (2005). Blue ocean strategy: How to create uncontested market space and make the competition irrelevant. Harvard Business Review Press.

Porter, M. E. (2008). The five competitive forces that shape strategy. Harvard Business Review, 86(1), 78–93. https://hbr.org/2008/01/the-five-competitive-forces-that-shape-strategy

Why Structure, Not Rivals, Is the Object of Analysis

The first thing extant practice gets wrong is conflating competitive analysis with competitor analysis. Porter’s (2008) central claim is that the long-run profitability of a market is governed by its structure, and that structure is the joint product of five forces: the intensity of rivalry among incumbents, the threat of new entrants, the bargaining power of suppliers, the bargaining power of buyers, and the threat of substitutes. The implication, which is easy to state and hard to internalize, is that you can win every head-to-head feature comparison and still operate in a structurally unattractive market where no participant earns durable returns. A PM who studies only the named competitor on the comparison grid is observing the weather while ignoring the climate.

The reason this lens has survived four decades is that it is mechanistic rather than descriptive. Each force operates through an identifiable channel: suppliers extract value when they are concentrated and switching is costly; buyers extract value when they are concentrated, informed, and price-sensitive; entrants compress margins when barriers are low; substitutes cap pricing power by offering a different way to accomplish the same job. Owing to this mechanistic character, the framework is portable across technological regimes, which is precisely why it can be re-run against the AI transition rather than discarded by it.

Competitive Intensity: When Differentiation Half-Life Collapses

Rivalry intensifies when competitors are numerous and similar, when growth slows, when exit barriers are high, and when products are perceived as undifferentiated. The defining structural shift in AI-enabled categories is that the half-life of feature differentiation has collapsed. When a capability is one prompt-engineering pattern or one model upgrade away from being replicated, the period during which a feature confers advantage shrinks from years to weeks. The 2023–2024 wave of “AI writing assistants,” in which dozens of products converged on near-identical summarize-rewrite-expand functionality within a single product cycle, is a clean illustration of rivalry escalating because differentiation evaporated.

The strategic implication for the PM is that, in the context of AI features, defensibility cannot reside in the feature itself. It must reside in something the rivalry cannot quickly copy: a proprietary feedback loop that tunes the model on usage no competitor can observe, a workflow the product owns end-to-end, or switching costs accrued through accumulated user context. The discipline here is to ask, before committing a quarter to an AI capability, not “can we build this” but “how long until parity, and what compounding asset accrues to us during that window.” Intensity is not a reason to avoid the build; it is a reason to design the build so that shipping it deposits something durable.

Supplier and Customer Power: The New Asymmetry of the Model Layer

The supplier force has been reshaped more dramatically by foundation models than any other. For the cohort of products that wrap a third-party model, the model provider is a supplier of unusual concentration and pricing latitude. When a small number of frontier labs supply the core intelligence on which your value proposition rests, you have, in Porter’s terms, accepted a concentrated supplier whose pricing, rate limits, deprecation schedules, and terms of service propagate directly into your unit economics and your roadmap. Products that discovered their margins inverting after a provider repriced tokens learned this the structural way. The mitigation is not to avoid the suppliers, which would be self-defeating, but to reduce dependence through model abstraction layers, multi-provider routing, and the cultivation of proprietary data that makes smaller or fine-tuned models viable substitutes for frontier capability on the workloads that matter.

Buyer power, meanwhile, has risen in a subtler way. Because generative tools lower the cost of evaluation and even of in-house construction, sophisticated enterprise buyers increasingly treat “build it ourselves with an API” as a credible alternative to purchasing. This is buyer power expressed as a substitution threat from the demand side. The product response is to widen the gap between what a buyer can assemble from raw components and what your product delivers as an integrated, governed, supported system, since the value that survives this comparison is the value buyers cannot cheaply reconstruct.

Substitutes: The Force Most PMs Underweight

Substitutes are the most underestimated force because they originate outside the industry’s competitive set and therefore outside the PM’s habitual field of view. A substitute is not a rival product; it is a different means of accomplishing the customer’s job. The cautionary cases are well known: incumbents in photography, navigation, and travel agencies were displaced not by stronger versions of themselves but by general-purpose platforms that absorbed the job entirely. In the present moment, the most consequential substitute for a large class of single-purpose software is a general-purpose agentic assistant that can perform the underlying task without the specialized interface. When a knowledge worker can instruct an agent to draft, schedule, reconcile, or summarize, the question every PM should sit with is uncomfortable but clarifying: what is the job my product does, and can a sufficiently capable agent now do that job through a different surface. Naming the substitute early is the precondition for designing against it.

Translating the Forces Into Product Decisions

The strategic implications of the framework become actionable when the PM converts each force into a recurring question attached to roadmap and positioning decisions. Rivalry asks what compounding asset a feature deposits before parity arrives. Supplier power asks how exposed the cost structure and roadmap are to upstream providers and what reduces that exposure. Buyer power asks what value survives the buyer’s build-versus-buy comparison. The threat of entrants asks what barrier the product is raising over time, whether through data, integrations, or switching costs, given that AI has lowered conventional barriers such as capital and engineering scarcity. The threat of substitutes asks what job is being done and whether a general-purpose system can now absorb it.

It is worth stating the framework’s limits with the same care as its strengths, since extant critique is fair on this point. The five forces assume relatively stable industry boundaries and underweight the role of complementors, partnerships, and ecosystems, which is exactly where much AI-era value now forms. The pragmatic posture, therefore, is to treat Porter’s model as the analysis of the profit pool’s structure and to pair it with the ecosystem and platform lenses developed in later modules, which address the cooperative dynamics the five forces omit. Used this way, the framework remains what it has always been for the product leader who reads it correctly: not a verdict on who wins the next feature war, but a map of where durable value can accumulate and where it cannot.

References

Andreessen Horowitz. (2024). Who owns the generative AI platform? https://a16z.com/who-owns-the-generative-ai-platform/

Porter, M. E. (2008). The five competitive forces that shape strategy. Harvard Business Review, 86(1), 78–93. https://hbr.org/2008/01/the-five-competitive-forces-that-shape-strategy

Porter, M. E. (1980). Competitive strategy: Techniques for analyzing industries and competitors. Free Press.

The strategic problem with this practice is not that feature comparison is irrelevant—it is not—but that it captures only the most visible and most easily replicated layer of competitive dynamics while systematically neglecting the structural dimensions that determine durable competitive position: strategic positioning, differentiation architecture, market narrative, and the possibility of creating an entirely new category that renders the feature comparison matrix irrelevant by changing the terms on which competition occurs.

Extant research in strategic management and competitive analysis suggests that organizations that achieve durable competitive advantage are not typically those with the richest feature sets in their categories, but those that have established the most coherent and defensible strategic positions—positions grounded in structural advantages that competitors cannot easily replicate and that are reinforced by the market narratives those organizations have successfully embedded in the minds of their customers, analysts, and investors (Porter, 1980; Ramadan et al., 2016). This essay develops a framework for competitive intelligence that attends to these deeper structural dimensions, examining strategic positioning, differentiation architecture, market narratives, and category creation as the primary analytical targets for senior product leaders who want to understand competition at the level that strategic advantage is actually determined.

Strategic Positioning: Understanding Why Competitors Win, Not Just What They Offer

Strategic positioning, in Porter’s (1980) foundational formulation, refers to the choice of competitive arena and the set of activities by which a company delivers a distinctive value proposition to a chosen customer segment in a way that is difficult for competitors to imitate. A competitor’s strategic position is not visible in its feature set; it is visible in the structural logic of its business model, the customer segments it serves and the ones it does not, the organizational capabilities it has built, and the architectural choices it has made about which dimensions of value it will lead on and which it will accept as table stakes.

Understanding a competitor’s strategic position—as distinct from cataloging its features—requires a different kind of analytical work. Rather than asking “what did the competitor build?”, strategic positioning analysis asks: (1) which customer segment is this competitor optimizing for, and what does that choice reveal about the customer problems they believe are most consequential?; (2) what does the competitor’s pricing model, sales motion, and organizational structure reveal about the economic logic they are pursuing?; and (3) where is the competitor choosing not to compete—what trade-offs have they accepted, and what customer needs are they explicitly or implicitly leaving unaddressed?

The third question is often the most strategically valuable. Trade-off analysis reveals the structural constraints that a competitor’s strategic position creates, and those constraints are frequently the basis for viable differentiation strategies that the competitor cannot respond to without undermining their own position. Southwest Airlines’ decision to compete exclusively on price and convenience in point-to-point domestic air travel—and to explicitly not offer international routes, assigned seating, business class, or hub-and-spoke connections—created a strategic position that full-service carriers could not easily match because matching it would require dismantling the very organizational architecture that made their full-service positions viable. The same structural logic applies in technology product markets: a competitor’s strategic trade-offs are not merely limitations to note, but potential sources of differentiated positioning for any product leader who understands them with sufficient precision.

In the AI-powered product landscape, strategic positioning analysis has become more consequential and more complex simultaneously. The proliferation of AI products in 2023–2025 generated competitive landscapes in which dozens of products offer broadly similar AI-powered capabilities—and in which the surface-level feature comparison matrix shows minimal differentiation across the competitive set. The strategic positioning analysis that reveals the actual structure of competition in these landscapes must attend to the data advantages that different competitors have built, the organizational contexts they are most deeply integrated into, the customer trust they have established through track record and compliance posture, and the platform strategies they are pursuing that will determine the structural competitive landscape two to three years ahead—not the feature additions they shipped last quarter (AI PM Tools Directory, 2026; Presta, 2026).

Differentiation Architecture: Building Positions That Compound

Differentiation is not a feature; it is a structural characteristic of the relationship between a product and its chosen customer segment. A product is differentiated when it offers a set of capabilities or experiences that customers in the target segment value significantly and that competitors cannot replicate without substantial investment, structural change, or a fundamentally different organizational model. The strategic question for competitive intelligence is not “are we different from competitors on this feature?” but “is our differentiation grounded in structural advantages that compound over time, or is it based on temporary feature leads that competitors can close with sufficient investment?”

Extant research and practitioner analysis identify three primary sources of compounding differentiation in technology product markets. The first is proprietary data: the accumulation of behavioral, operational, or domain-specific data through customer engagement that enables continuously improving product performance in ways that competitors without equivalent data cannot match. This form of differentiation is structural rather than merely technical, because it compounds with use and cannot be replicated simply by hiring the same engineers or purchasing the same infrastructure. Netflix’s recommendation system and Spotify’s personalization engine are the canonical examples of proprietary data as compounding differentiation; in each case, the competitive advantage is not the algorithm but the data asset that makes the algorithm valuable (ResearchGate, 2024; Spotify Technology S.A., 2025).

The second is network effects: the dynamic by which the value of the platform increases for each participant as the number of participants grows, creating a competitive moat that becomes progressively more difficult to overcome as the network scales. Network effects are not available in all product categories—they require structural conditions in which participants benefit from other participants’ presence or activity—but in categories where they are available, they are among the most durable sources of competitive differentiation, owing to the self-reinforcing nature of the advantage (Bain & Company, 2025).

The third is switching costs created by deep workflow integration: the degree to which a product has become embedded in the customer’s operational processes, data architecture, and organizational practices in ways that make migration costly, disruptive, and organizationally risky. This form of differentiation is particularly prevalent in enterprise B2B software markets, where products that have achieved deep integration with customer data environments, organizational processes, and employee workflows generate retention rates and renewal dynamics that are fundamentally different from those achievable by products that sit at the edge of the customer’s operational architecture (Reforge, 2024).

For competitive intelligence purposes, the analytical task is to assess—for each significant competitor—which of these three sources of compounding differentiation they are building, at what stage of development each is, and what the trajectory of their advantage is over the next two to three years. A competitor that has achieved shallow adoption and has not yet built significant data advantages, network effects, or switching costs is in a fundamentally different strategic position than a competitor that has accumulated three years of behavioral data, has a growing ecosystem of integrations and partnerships, and has achieved deep workflow integration in its core customer base—even if their current feature sets are comparable.

Market Narratives: The Strategic Importance of the Story That Precedes the Product

One of the most underappreciated dimensions of competitive intelligence—and one of the most consequential for strategic positioning—is the market narrative: the story that a product organization tells about the problem its category addresses, the reason existing solutions are inadequate, and the vision of the future state that its approach uniquely enables. Market narratives are not marketing copy; they are strategic claims about how the market should be understood, what the central problem is, and which dimensions of solution quality are most consequential. The organization that establishes its narrative as the dominant framework through which customers, analysts, and investors understand the market has achieved a structural advantage that is invisible in a feature comparison matrix but shapes the evaluation criteria that competitors are judged against.

The strategic dynamics of market narrative are well characterized in the competitive intelligence literature. Organizations that define the narrative first—that establish the vocabulary, the problem framing, and the evaluation criteria through which the market is understood—force competitors into a defensive posture: responding to a framing that was designed to favor the narrative-setter’s product. Salesforce’s “no software” campaign and cloud CRM narrative in the early 2000s is a canonical example. By establishing “software-as-a-service” as the primary evaluation criterion for CRM, and by framing on-premise software as a legacy approach that created unnecessary cost and complexity, Salesforce shaped the competitive evaluation criteria in a way that favored its architectural approach and positioned incumbent on-premise competitors as structurally disadvantaged rather than merely competitively challenged (Ramadan et al., 2016).

HubSpot’s “inbound marketing” category narrative illustrates the same dynamic in the marketing software market. Rather than competing against established marketing automation platforms on feature dimensions—where incumbents had substantial advantages—HubSpot established a new evaluative framework (”inbound vs. outbound”) that centered the discussion on a dimension where HubSpot’s approach was differentiated and where the incumbent’s architectures were structurally ill-suited to compete. The competitive intelligence implication is that understanding a competitor’s narrative strategy—the specific framing choices they are making, the vocabulary they are propagating, and the evaluation criteria they are attempting to establish as market standards—is as strategically important as understanding their product roadmap.

In the current AI landscape, market narrative competition is particularly intense, because the category is young enough that narrative leadership is still contestable. Organizations competing for narrative leadership in the AI era are making strategic framing choices that will shape competitive evaluation for years: “AI copilot vs. AI agent” (framing the primary dimension as user augmentation versus autonomous task execution), “general AI vs. domain-specific AI” (framing the primary dimension as breadth versus depth), and “AI platform vs. AI product” (framing the primary dimension as ecosystem openness versus product coherence). Product leaders who monitor these narrative choices and understand their strategic logic are better positioned to make their own narrative investments with the precision and timing required to establish a defensible position in the evolving competitive landscape (Competitive Intelligence Alliance, 2025).

Category Creation: The Most Ambitious and Most Defensible Competitive Strategy

At the far end of the competitive intelligence spectrum lies category creation—the strategic ambition not to win within an existing competitive category, but to define a new category in which the creating organization is, by definition, the leader. Ramadan, Peterson, Lochhead, and Maney’s (2016) Play Bigger articulates the structural logic of category creation with unusual clarity: organizations that create new categories and successfully establish their defining role in those categories capture a disproportionate share of market value, because the market gravitates toward category leaders rather than distributing value proportionally across competitive participants.

The strategic insight that distinguishes category creation from product positioning is the recognition that the product and the category must be developed simultaneously: the product defines the category, and the category defines the terms on which the product is evaluated. Organizations that attempt to enter existing categories with differentiated products are competing on a terrain that was defined by someone else, for criteria that were established by incumbents, and against evaluation standards that were designed to favor the products already present. Organizations that define new categories—by identifying a problem that no existing category adequately addresses, naming it in a way that is memorable and evangelizable, and establishing the evaluation criteria for the category in a way that favors their approach—are competing on terrain they have defined, for criteria they have established.

The practical challenge of category creation is that it requires simultaneous investment in product development and market development—the organization must build the product that addresses the category problem while also building the organizational and market infrastructure (analyst relationships, customer success stories, educational content, partner ecosystem) required to establish the category in the minds of customers and investors. This dual investment requirement is significantly more resource-intensive than a pure product strategy, but the potential returns are also significantly higher: organizations that achieve category leadership capture, on average, approximately 76% of the category’s market capitalization, leaving only 24% to be distributed among all other competitors (Ramadan et al., 2016).

For product leaders who are evaluating whether category creation is the appropriate strategic ambition for their product, several analytical questions are structurally essential: (1) is there a genuine problem that existing categories are systematically failing to address—not merely a feature gap but a structural inadequacy in the existing categories’ approach?; (2) is the organization willing and able to make the sustained investment in market development required to establish a new category, which typically spans three to five years before the category definition achieves market consensus?; and (3) does the organization have, or can it develop, the point of view—the intellectual framework for the new problem and the new solution approach—that will be required to establish narrative leadership in the emerging category?

In the AI era, category creation opportunities are emerging at an unusual rate, as AI capabilities create genuinely new solution approaches to problems that existing categories have addressed with non-AI architectures. Agentic AI as a category—distinct from AI copilots, AI tools, and traditional automation—is an example of a category that is currently being defined in real time, with multiple organizations making competing claims about the appropriate framing, the essential evaluation criteria, and the defining product architectures. Product leaders who understand the structural dynamics of category creation, and who are positioned to make the investments required to establish category leadership, are competing for one of the most valuable strategic positions available in the current technological landscape.

References

AI PM Tools Directory. (2026). The future of AI in product management: 2026–2030 predictions. https://aipmtools.org/articles/future-of-ai-product-management

Bain & Company. (2025). Platform strategy: A guide to platform business models. https://www.bain.com/insights/solution-spotlight/platform-strategy/

Competitive Intelligence Alliance. (2025). 11 competitive intelligence trends in 2025. https://www.competitiveintelligencealliance.io/11-competitive-intelligence-trends/

Multidisciplinary Frontiers. (2025). A theoretical model for strategic market positioning. Frontiers in Management Research, 2(2), 130.1. https://www.multidisciplinaryfrontiers.com/uploads/archives/20251004144434_FMR-2025-2-130.1.pdf

Porter, M. E. (1980). Competitive strategy: Techniques for analyzing industries and competitors. Free Press.

Presta. (2026). AI product strategy 2026: The founder’s guide to AI-native growth. https://wearepresta.com/ai-product-strategy-2026-the-founders-guide-to-ai-native-growth/

Ramadan, A., Peterson, D., Lochhead, C., & Maney, K. (2016). Play bigger: How pirates, dreamers, and innovators create and dominate markets. HarperBusiness.

Reforge. (2024). The product strategy stack. Reforge Blog. https://www.reforge.com/blog/the-product-strategy-stack

ResearchGate. (2024). Strategy for growth and market leadership: The Netflix case. https://www.researchgate.net/publication/374545358_Strategy_for_Growth_and_Market_Leadership_The_Netflix_Case

Sendview. (2025). The competitive intelligence industry: Market landscape, growth drivers, and future outlook. https://sendview.io/guides/guide-to-the-competitive-intelligence-industry

Spotify Technology S.A. (2025). Form 6-K, FY2025. U.S. Securities and Exchange Commission. https://www.sec.gov/Archives/edgar/data/0001639920/000114036125002936/ef20042791_ex99-1.htm

Stackmatix. (2024). Competitive positioning framework: How to own your category. https://www.stackmatix.com/blog/competitive-positioning-framework

The intellectual history of JTBD is instructive for understanding its strategic depth. Tony Ulwick conceptualized the core framework in 1990, applying Six Sigma’s outcome-measurement logic to the innovation process and formalizing it as Outcome-Driven Innovation (ODI) in 1999 (Strategyn, 2024). Clayton Christensen, introduced to the framework by Ulwick, elaborated and popularized it in The Innovator’s Solution (2003), developing the “milkshake example” that became one of the most cited illustrations in product management literature. Bob Moesta and Chris Spiek subsequently developed the “Forces of Progress” model and the “Switch Interview” methodology, focusing on the precise moment at which customers switch from one solution to another and the psychological forces that govern that transition. Alan Klement’s “jobs-as-progress” theory extended the framework into its most expansive formulation: that a “job” is not merely a task to be completed but a form of progress toward an improved version of the customer’s situation—an aspiration that encompasses functional, emotional, and social dimensions simultaneously (Klement, as cited in GoPractice, 2024).

This essay develops the strategic application of JTBD across three dimensions: the tripartite structure of functional, emotional, and social jobs and its implications for product design and positioning; the outcome-driven thinking methodology and how it reframes competitive analysis; and the switching trigger dynamics that determine when and why customers adopt new solutions—with particular attention to the AI era’s implications for each.

Functional, Emotional, and Social Jobs: The Full Architecture of Customer Motivation

The simplest formulation of JTBD—customers hire products to get jobs done—is accurate but dangerously incomplete if it is taken to mean only functional jobs. Every customer situation that motivates a product search contains at minimum three distinct job dimensions: a functional job (the concrete task the customer needs to accomplish), an emotional job (the internal feeling the customer wants to achieve or avoid in the process), and a social job (the way the customer wants to be perceived by others in the context of the task). Neglecting the emotional and social dimensions—as is common in product teams with an engineering-dominant culture—produces products that are technically capable but psychologically or socially misaligned with what the customer is actually trying to achieve (GoPractice, 2024; UXCrush, 2026).

The functional job is the dimension that product teams most readily attend to, because it is the most directly observable and the most naturally connected to the language of product requirements. A business professional who “hires” a presentation software product has a functional job: producing a visually coherent slide deck within a limited time. A team that uses a project management tool has a functional job: coordinating work across individuals with different responsibilities, time zones, and priorities. Defining the functional job precisely—and, crucially, at the right level of abstraction—is the first step in JTBD analysis. Ulwick’s ODI framework is particularly rigorous on this point, insisting that the job should be defined independently of any specific solution, at a level of abstraction that captures the underlying progress the customer is seeking rather than the specific workflow step they currently perform (Ulwick, as cited in Strategyn, 2024).

The emotional job captures what the customer wants to feel—or to avoid feeling—in the course of getting the functional job done. The professional using presentation software does not merely want to produce slides; they want to feel confident that the output reflects well on their capabilities, to avoid the anxiety of discovering a formatting problem at the last moment, and to feel that the time invested was proportionate to the output quality achieved. These emotional dimensions are not peripheral to the product experience; they are central to it. Products that address the functional job well but fail to manage the emotional dimensions—creating anxiety, frustration, or a sense of inadequacy in the course of use—will generate functional satisfaction and emotional dissatisfaction simultaneously, a combination that produces weak retention and poor word-of-mouth despite adequate feature coverage.

The social job captures the dimension that is perhaps most consistently underweighted: what the customer wants others to think about them in the context of the task. The team adopting a new collaboration tool does not merely want to coordinate work more effectively; they also want to signal organizational sophistication, to be seen as technologically current by peers and superiors, and to demonstrate the kind of systematic thinking about team performance that reflects well on the team leader’s judgment. Slack’s early adoption dynamics were driven significantly by social job considerations—teams that adopted Slack were signaling a particular organizational culture and identity, one associated with technical modernity and startup-adjacent practices, that was as motivationally significant for some early adopters as the functional communication improvements the product delivered (Intercom, 2024).

In the context of AI-native product development, the social job dimension has acquired particular strategic importance. The adoption of AI-powered tools in organizational contexts is not governed only by functional performance—how well the AI performs the task—but significantly by the social and identity dimensions of being known as an AI-forward organization, team, or individual. Product leaders building AI tools for knowledge workers should attend carefully to both the functional and social job dimensions: the AI capability must be demonstrably effective at the functional task, but it must also be designed and positioned in a way that allows users to adopt it without compromising the social and professional identity dimensions that govern self-presentation in organizational contexts (Gocious, 2026).

Outcome-Driven Thinking: Reframing the Competitive Arena

The most transformative strategic contribution of Ulwick’s ODI framework is the concept of outcome-driven innovation: the practice of identifying the specific, measurable outcomes that customers are trying to achieve in getting a job done, and using those outcomes—rather than product features or customer-stated preferences—as the primary unit of competitive analysis and product investment decision-making.

In Ulwick’s formulation, a customer outcome is a metric that the customer uses to evaluate how well the job is getting done: “minimize the time required to X,” “increase the likelihood of Y,” “reduce the number of errors in Z.” These outcomes are stable—they do not change when new solutions emerge, because they are properties of the job rather than properties of any specific solution—and they are measurable, because the customer can reliably assess the degree to which a solution moves the outcome in the desired direction. The strategic implication is that competitive analysis, conducted through the outcome lens, reveals the landscape of over-served and under-served outcomes across the existing competitive set—showing not which competitor has the most features, but which specific outcomes the existing solutions address well and which they address poorly.

This outcome-based competitive map has two strategically valuable applications. The first is differentiation: products that identify a cluster of under-served outcomes in a target customer’s job space and build their differentiation around addressing those outcomes will achieve a competitive position that is grounded in genuine customer value rather than feature parity or marketing narrative. The second is disruption detection: organizations that monitor the outcome-satisfaction landscape systematically can identify the early signatures of disruptive competitive entry—specifically, the entrance of competitors who are addressing previously under-served outcomes in ways that the incumbent’s architecture makes difficult to match.

Spotify’s product strategy illustrates outcome-driven thinking applied with unusual consistency. The functional job Spotify addresses—access to music in the right moment—contains a well-characterized set of customer outcomes, including reducing the time required to discover music the listener will enjoy, increasing the likelihood that the music selection matches the listener’s current context and mood, and minimizing the cognitive load of active playlist management. Spotify’s product investments—Discover Weekly, Daily Mix, algorithmic playlist generation, and context-aware recommendations—are coherent expressions of a strategy to lead on the specific outcomes of discovery, context-fit, and effortlessness within the music listening job space (Railsware, 2024). The product has not attempted to lead on all dimensions of the music listening job simultaneously; it has concentrated its competitive differentiation on the outcomes where it has the structural advantage—behavioral data depth and algorithmic personalization capability—that competitors without equivalent data assets cannot easily replicate.

Switching Triggers: The Strategic Anatomy of Customer Change

Perhaps the most directly actionable contribution of the JTBD framework for product strategy is the “Forces of Progress” model developed by Bob Moesta, which provides a structural account of the forces that govern the customer’s decision to switch from an existing solution to a new one. Understanding these forces is essential for product leaders for two reasons: it reveals the conditions under which customers will be most receptive to adopting a new product, and it reveals the incumbent’s structural defenses against competitive displacement.

In Moesta’s formulation, four forces shape the switching decision: (1) the push of the current situation—the degree to which the customer’s dissatisfaction with the existing solution has accumulated to the point of motivating a change; (2) the pull of the new solution—the degree to which the new product’s value proposition creates an attractive vision of the improved situation it enables; (3) the anxiety of switching—the degree to which the customer anticipates difficulty, disruption, or risk in the transition; and (4) the habit of the present—the degree to which the existing solution has become embedded in the customer’s behavioral routine, creating inertia that must be overcome even when the functional case for switching is compelling (Moesta, as cited in Business of Software, 2024).

The strategic implication is that adoption is not determined by the pull of the new solution alone—a fact that is frequently underweighted in product launch strategies that focus primarily on value proposition articulation. The push of the current situation must be sufficient to create the behavioral energy required to overcome switching anxiety and habit inertia. Products that have compelling pull but insufficient push—that are clearly superior to existing alternatives but address a problem that customers have not yet experienced as acutely enough to motivate change—will achieve lower adoption velocity than their functional quality would predict. Products that have strong push—that are entering a market where significant accumulated dissatisfaction with existing solutions creates a receptive customer base—can achieve high adoption velocity even with a value proposition that is only modestly superior to the incumbent.

For product leaders, the practical implication is that switching trigger analysis should be conducted alongside ICP development and problem selection. The question is not only “who experiences this problem most acutely?” but “who is most likely to be actively searching for a new solution right now—and what is the specific accumulated push event that has created their current motivation?” Bob Moesta’s recommended methodology—interviewing customers who have recently switched (rather than habitual users of an established product) to understand the precise sequence of push, pull, anxiety, and habit forces that governed their decision—generates the most actionable insight for this analysis (Business of Software, 2024).

In the AI era, switching trigger dynamics have taken on particular complexity. The rapid improvement of AI capabilities has created a distinctive switching dynamic in markets where AI-powered solutions are displacing incumbents: the accumulated dissatisfaction with incumbent solutions is substantial (owing to the increasingly visible gap between what AI-powered alternatives can deliver and what legacy solutions provide), creating strong push; but the anxiety of switching is also high (owing to concerns about data privacy, workflow disruption, organizational change management, and the risk of dependent on a product category that is evolving rapidly). Product leaders who understand this specific push-anxiety dynamic are better positioned to design adoption pathways—trial environments, gradual migration, outcome-guarantee pricing—that reduce switching anxiety sufficiently to allow the push energy to produce adoptions rather than deferral decisions.

JTBD as a Strategic Lens for the AI Era

The most consequential application of JTBD thinking in the current AI landscape concerns a structural question that the framework is uniquely equipped to illuminate: when AI capabilities automate or enhance the performance of the functional job, what happens to the emotional and social jobs—and are those residual dimensions sufficient to sustain customer motivation for a distinctively human-augmented product experience?

The evidence suggests that the functional job automation enabled by AI is proceeding faster than the emotional and social job implications are being worked through. Products that automate significant portions of the functional job—AI-powered content generation, AI-assisted coding, AI-driven data analysis—face the strategic question of whether the emotional and social jobs that previously required human engagement and judgment are preserved, diminished, or transformed by the automation. A knowledge worker whose functional job is to produce written communications, and for whom that functional job is also a primary mechanism for establishing professional identity and demonstrating intellectual contribution (social job), will relate to an AI writing assistant very differently than a knowledge worker for whom the writing is a means to an end rather than a professional identity signal.

Product leaders who apply JTBD thinking rigorously to their AI product concepts—asking not only “what functional job does this AI capability address?” but “what happens to the emotional and social jobs when AI automates the functional core?”—will be better positioned to design AI products that enhance rather than erode the full architecture of customer motivation. The products that achieve durable adoption in the AI era are likely to be those that enhance human agency and identity in the performance of the emotional and social jobs, while reducing the friction and effort associated with the functional job—an integration of human and AI contribution that is more strategically sophisticated than either pure automation or pure augmentation.

References

Business of Software. (2024). Bob Moesta: Understanding your customer jobs-to-be-done. https://businessofsoftware.org/talks/understanding-your-customer-jtbd/

Christensen, C. M., & Raynor, M. E. (2003). The innovator’s solution: Creating and sustaining successful growth. Harvard Business School Press.

Gocious. (2026). AI in product management guide for 2026 for product leaders. https://gocious.com/blog/ai-in-product-management-guide-for-2026-for-product-leaders

GoPractice. (2024). Jobs to be done theory and frameworks explained: Christensen, Moesta & Ulwick. https://gopractice.io/product/jobs-to-be-done-the-theory-and-the-frameworks/

HowToes. (2025). Jobs-to-be-done: Complete guide to understanding customer needs for breakthrough innovation. https://howtoes.blog/2025/07/01/jobs-to-be-done-complete-guide-to-understanding-customer-needs-for-breakthrough-innovation/

Intercom. (2024). Intercom on jobs-to-be-done. Intercom Books. https://www.intercom.com/resources/books/intercom-jobs-to-be-done

Medium – Strategy Dynamics. (2024). What it takes to switch: Using jobs to be done as a framework. https://medium.com/strategy-dynamics/what-it-takes-to-switch-ded91b1caccb

ProductPlan. (2024). Jobs-to-be-done framework. https://www.productplan.com/glossary/jobs-to-be-done-framework

Railsware. (2024). Jobs to be done examples: Spotify, Duolingo, Uber cases. https://railsware.com/blog/jobs-to-be-done-examples/

Strategyn. (2024). Jobs to be done (JTBD): The original framework by Tony Ulwick. https://strategyn.com/jobs-to-be-done/

Ulwick, A. W. (2005). What customers want: Using outcome-driven innovation to create breakthrough products and services. McGraw-Hill.

UXCrush. (2026). Jobs-to-be-done framework: A UX practitioner’s guide. https://uxcrush.com/jobs-to-be-done-framework

Neither output is strategically adequate. Effective segmentation for product strategy requires a framework that is simultaneously precise enough to guide investment decisions, grounded enough in observable customer behavior to be actionable, and structurally connected to the product’s competitive positioning so that segment choices reinforce rather than contradict the broader strategic logic. This essay develops such a framework by examining three of the most strategically consequential segmentation constructs available to product leaders: the Ideal Customer Profile (ICP) as a strategic focusing tool, the distinction between user personas and economic buyers and its implications for product design and go-to-market strategy, and the structural differences between B2B and B2C segmentation logic and the strategic implications that follow.

The Ideal Customer Profile: Segmentation as Strategic Commitment

The Ideal Customer Profile is not, as it is sometimes treated, a description of the customer the product currently serves most frequently—it is a normative claim about the customer the product is best positioned to create the most value for, and for whom the product can build the most defensible competitive advantage. The distinction is consequential: the customers a product currently serves most frequently are a product of historical go-to-market decisions, early sales efforts, and the specific problems the product happened to address well during its formative period. They may or may not be the customers for whom the product can build the most durable and differentiated position.

Constructing a strategically sound ICP requires attending to several dimensions simultaneously. The first is fit: the degree to which the target customer segment has the problem the product addresses as a genuinely acute, high-priority challenge—not a nice-to-have, but a critical operational or strategic imperative. The second is accessibility: the degree to which the product can reach this customer segment through its current or planned go-to-market capabilities without requiring organizational investments that are disproportionate to the near-term opportunity. The third is expansion potential: the degree to which successful deployment in this segment creates natural expansion opportunities—either within the account (land-and-expand dynamics, where initial deployment creates the conditions for broader organizational adoption) or across the segment (reference customer dynamics, where successful deployment creates social proof that accelerates adoption in the broader segment population).

The fourth and most strategically decisive dimension is defensibility: the degree to which serving this customer segment well allows the product to build competitive moats that are difficult for competitors to replicate. This dimension requires product leaders to think through the mechanisms by which serving the ICP creates structural advantages—whether through proprietary data generated by the customer relationship, through network effects enabled by the segment’s connectivity, through deep workflow integration that creates high switching costs, or through capabilities specifically developed for the segment’s distinctive needs that would not be valuable in other segments (Sybill AI, 2026). Products that identify ICPs primarily on the basis of near-term revenue potential, without adequate attention to the defensibility dimension, tend to discover over time that the segments they entered were also the first segments their competitors targeted—owing to the same accessibility and revenue characteristics that made those segments attractive in the first place.

In practice, ICP development is most useful when treated as a dynamic and continuously refined strategic hypothesis rather than a fixed document. Several conditions warrant deliberate ICP reassessment: (1) churn rate deviation from cohort baseline, which suggests that the product is retaining customers in some parts of its ICP definition significantly better than others; (2) win-rate compression in a previously strong segment, which suggests a competitor is establishing a differentiated position; (3) pricing tier mix shift, which may indicate that different customer types are finding different kinds of value in the product; and (4) category maturity change, which may require the ICP to shift as the market evolves (GrowLeads, 2026). Product leaders who treat ICP as a living strategic hypothesis—refreshing it regularly against these signals—are better positioned to sustain strategic alignment between the product’s development direction and the market dynamics that determine its competitive position.

User Personas and Economic Buyers: The Multi-Stakeholder Architecture of B2B Product Strategy

In B2C product contexts, the user and the buyer are, in most cases, the same individual—the person who experiences the value of the product is also the person who makes the purchase decision and pays the price. This structural simplicity allows B2C product teams to optimize product experience and commercial positioning around a single customer perspective. In B2B product contexts, the structural complexity is significantly greater: the person who uses the product daily, the person who evaluates it and makes the purchase recommendation, and the person who controls the budget and makes the final authorization decision are frequently different individuals with different priorities, different success metrics, and different decision criteria.

Extant practitioner research has documented the typical multi-stakeholder architecture of B2B purchase decisions with considerable consistency. The four roles that appear most frequently in B2B buying processes are: (1) the economic buyer, typically at the C-suite or senior VP level, who controls the budget, evaluates the investment against business outcome expectations, and makes the final authorization decision; (2) the technical buyer, who evaluates the product against technical, security, compliance, and integration requirements, and can exercise veto authority even without final purchase authority; (3) the user buyer, who evaluates the product against the daily workflow requirements of the team that will use it and whose adoption behavior will ultimately determine whether the product delivers its promised value; and (4) the champion, an internal advocate who has a personal stake in the product’s success and actively promotes it within the organizational decision-making process (PandaDoc, 2024).

The strategic implication for product design and go-to-market strategy is that these four stakeholders require different product experiences, different value articulations, and different engagement strategies—and a product strategy that optimizes for one stakeholder type at the expense of others will encounter predictable failure modes. Products that are optimized for the user experience but fail to provide the economic buyer with a clear, quantifiable business outcome narrative will generate enthusiastic user interest that fails to convert to enterprise purchase decisions. Products that address the economic buyer’s ROI framing convincingly but deliver a frustrating daily user experience will generate initial purchase decisions that fail to renew, owing to low adoption and poor user outcomes. Products that satisfy both economic buyers and users but fail to meet the technical buyer’s security and compliance requirements will generate purchase interest that is blocked at the procurement gate.

The persona artifacts that product teams produce should, in the B2B context, explicitly represent all four stakeholder types and should articulate the distinct success metrics, decision criteria, and experience requirements of each. This is a significantly different analytical task than the single-user persona that is adequate for B2C product design—and product teams that apply B2C persona development practices to B2B product strategy will produce artifacts that are useful for one stakeholder type but strategically incomplete for the multi-stakeholder architecture that governs B2B adoption.

A particularly consequential strategic choice in B2B product design concerns the relative investment in user experience versus buyer experience. Products that are optimized primarily for user adoption—with elegant, intuitive interfaces, fast time-to-value, and strong habit-formation mechanics—tend to benefit from bottom-up adoption dynamics, where users adopt the product individually or in small teams and generate organizational demand that reaches the economic buyer from the bottom up. Slack’s initial enterprise penetration followed this logic: individual teams adopted it for team communication, and the resulting organizational network effects created organizational demand that bypassed the traditional enterprise procurement process. Products optimized primarily for buyer persuasion—with strong business case frameworks, detailed security and compliance documentation, and executive-level reporting and analytics—tend to benefit from top-down adoption dynamics, where organizational purchase decisions precede user adoption and create the organizational mandate for deployment.

In the current AI product landscape, the bottom-up adoption dynamic is particularly prevalent among AI copilot and productivity tools—individual knowledge workers adopt AI-powered writing, coding, or research tools on an individual basis, and the organizational demand that results creates enterprise purchase opportunities. The strategic challenge for products pursuing this dynamic is that the individual user experience and the organizational buyer’s value proposition can diverge significantly: the individual user values autonomy, efficiency, and personalization, while the organizational buyer values measurable ROI, governance and compliance, and the ability to monitor and manage usage at scale (Gocious, 2026). Products that successfully navigate this tension—building user experiences that are compelling enough to drive bottom-up adoption while maintaining the governance and outcome-measurement infrastructure that enterprise buyers require—are most likely to convert viral individual adoption into durable enterprise revenue.

B2B Versus B2C Segmentation: Structural Logic, Not Just Scale

The B2B versus B2C distinction is frequently treated as a matter of scale and organizational complexity—B2B deals are larger, sales cycles are longer, and buying processes involve more stakeholders. While these observations are accurate, they miss the more fundamental structural difference: B2B and B2C segmentation are governed by different strategic logics that require different analytical approaches, different data sources, and different strategic use cases.

B2B segmentation is fundamentally firmographic and behavioral at the organizational level. The most strategically productive B2B segmentation dimensions attend to the structural characteristics of the target organization—industry vertical, company size, growth stage, technical infrastructure, organizational structure, strategic priorities—and to the behavioral signals that indicate fit with the product’s value proposition, such as current tool stack, recent organizational changes, hiring patterns, and competitive relationships. These firmographic and behavioral dimensions are more predictive of fit, adoption, and retention than demographic or role-based descriptions of the individual users within the organization, because they capture the organizational context that determines whether the product’s value proposition is structurally relevant and whether the conditions for adoption and retention are present.

B2C segmentation is fundamentally behavioral and attitudinal at the individual level. The most strategically productive B2C segmentation dimensions attend to how individual customers think about and engage with the problem the product addresses—their current workarounds, their motivation to change, their sensitivity to different product design choices, and their social and contextual influences on adoption behavior. Demographic dimensions such as age, income, and geography are useful as proxies for these underlying behavioral and attitudinal characteristics, but they are proxies rather than the thing itself; two demographically similar individuals may have radically different behavioral relationships to a given product category, and a segmentation that relies primarily on demographics will generate a customer profile that is too coarse to drive precise product and go-to-market decisions.

In B2C contexts, a further structural complexity arises when the user and the buyer are different individuals—a condition that is less universal in B2C than in B2B but is consequential in specific categories. Children’s educational technology products, eldercare tools, corporate gifting, and family subscription services all exhibit buyer-user separation in B2C contexts. In these cases, the same multi-stakeholder analysis that governs B2B product strategy—attending separately to the user experience, the buyer’s value articulation, and the organizational or social dynamics that connect them—is required, even though the organizational complexity is lower. Products in these categories that optimize exclusively for the user experience without adequate attention to the buyer’s value proposition (or vice versa) encounter the same structural failure modes as B2B products that ignore one stakeholder type.

In the context of AI-powered products, the B2B/B2C segmentation distinction intersects with the multi-stakeholder architecture in a new way. AI tools that handle sensitive personal or organizational data require product strategies that address not only the user’s and buyer’s value perspectives but also a third stakeholder perspective that is emerging as increasingly influential: the compliance and ethical oversight stakeholder, who evaluates AI products against standards of data privacy, algorithmic transparency, and organizational governance that neither user personas nor economic buyer analyses adequately capture (Gocious, 2026; AI PM Tools Directory, 2026). Product teams building AI-powered products in enterprise B2B contexts who have not yet developed a distinct analytical representation of this compliance stakeholder type are operating with an incomplete map of the multi-stakeholder architecture that governs their adoption journey.

References

AI PM Tools Directory. (2026). The future of AI in product management: 2026–2030 predictions. https://aipmtools.org/articles/future-of-ai-product-management

Askattest. (2026). How to create an ideal customer profile (ICP) in 2026. https://www.askattest.com/blog/articles/ideal-customer-profile

Gocious. (2026). AI in product management guide for 2026 for product leaders. https://gocious.com/blog/ai-in-product-management-guide-for-2026-for-product-leaders

GrowLeads. (2026). ICP model update 2026: 10 B2C and B2B best practices for refreshing your ideal customer profile. https://growleads.io/blog/10-ways-to-improve-your-ideal-customer-profile-strategy-in-2025/

Kalungi. (2024). How to build your B2B ideal customer profile with our free template. https://www.kalungi.com/blog/how-define-b2b-ideal-customer-profile-template-icp

PandaDoc. (2024). Ideal customer profile (ICP) vs buyer persona: Meaning, differences. https://www.pandadoc.com/blog/ideal-customer-profiles/

Ramadan, A., Peterson, D., Lochhead, C., & Maney, K. (2016). Play bigger: How pirates, dreamers, and innovators create and dominate markets. HarperBusiness.

Secret Source Marketing. (2024). Ideal customer profile (ICP) vs. buyer persona: Understanding the key differences. https://blog.secretsourcemarketing.com/double-digit/ideal-customer-profile-vs-buyer-persona-guide

Sybill AI. (2026). Ultimate ICP guide 2026: Build your ideal customer profile. https://www.sybill.ai/blogs/icp-guide

Extant research in entrepreneurship, innovation management, and behavioral economics has generated a rich set of frameworks and empirical findings that illuminate the dimensions along which customer problems should be evaluated. This essay synthesizes the most strategically consequential of these findings into a coherent analytical framework for problem selection—one that attends to the structural distinction between painkillers and vitamins, the interrelated dimensions of frequency, intensity, and willingness to pay, and the behavioral economics literature’s contribution to understanding why customers do and do not act on their own stated preferences.

Painkillers Versus Vitamins: The Most Overused Analogy in Product Management, and Why It Remains Indispensable

The painkiller-vitamin analogy has been so thoroughly circulated in product management discourse that it risks becoming a platitude—invoked reflexively in problem evaluation conversations without the analytical depth that makes it genuinely useful. A more rigorous application of the analogy reveals important nuances that the simplified version obscures.

In its most useful form, the painkiller-vitamin distinction maps onto a structural difference in the customer’s relationship to the problem, not merely the severity of the pain. A painkiller addresses a problem that the customer already recognizes, already experiences acutely, and is already motivated to solve—the solution does not need to educate the customer about the existence of the problem or build the behavioral habit of problem-consciousness; the problem creates its own demand. A vitamin addresses a problem that the customer may acknowledge intellectually but does not feel acutely enough to create urgent behavioral motivation—the solution must not only be effective but must also build and sustain the motivational architecture that drives recurring use.

The strategic implications of this distinction cascade through every aspect of product and go-to-market strategy. Painkiller products typically exhibit faster initial adoption, clearer willingness to pay, and stronger word-of-mouth driven by the relief of genuine pain. Vitamin products typically require longer adoption cycles, more intensive customer education, and a sustained investment in building the habit infrastructure—reminders, streak mechanics, social accountability, measurable outcome feedback—that substitutes for the intrinsic urgency the painkiller customer already possesses. Neither product type is inherently superior from a strategic standpoint; the point is that they require different market entry strategies, different product architectures, and different success metrics—and treating a vitamin product as if it were a painkiller (by assuming that demonstrating effectiveness will be sufficient to drive adoption) is one of the most common strategic errors in B2B software product development.

There is a further nuance that the simple analogy tends to obscure: the category assignment is not intrinsic to the problem but is contextual, varying by customer segment, competitive context, and the customer’s prior experience with the problem space. Slack’s enterprise messaging product was, for one customer segment—teams that were already using fragmented email-and-text workflows and acutely experiencing the coordination cost—a painkiller. For another segment—teams with established internal communication practices that worked well enough—it was a vitamin. The strategic insight is not simply “is this a painkiller or a vitamin?” but “for which segment is this a painkiller, and what is the market size of that segment relative to the vitamin segment?” (Ramadan et al., 2016). The answer to that question shapes the ideal customer profile, the go-to-market strategy, and the investment thesis for the product.

In the context of AI-native products, the painkiller-vitamin distinction has acquired particular strategic importance. The proliferation of AI features and AI-powered workflows in 2023–2025 produced a substantial category of products that were, in the painkiller-vitamin framework, vitamins positioned as painkillers—tools that demonstrably improved certain aspects of user productivity, but whose value did not rise to the level of urgency that would drive the organizational adoption, workflow integration, and sustained usage required for commercial success. Product leaders who apply the painkiller-vitamin lens rigorously to their AI product concepts—asking not “does this AI capability improve user experience?” but “does this AI capability address a problem that users currently experience as urgently enough that they will change their existing workflows to adopt it?”—are more likely to identify the genuinely valuable AI product opportunities from among the larger set of technically impressive but strategically marginal possibilities.

Frequency, Intensity, and Willingness to Pay: The Three-Dimensional Problem Evaluation Framework

Beyond the painkiller-vitamin distinction, a rigorous problem evaluation framework requires attending to three interrelated dimensions: the frequency with which customers encounter the problem, the intensity with which they experience it when they do, and the willingness to pay they exhibit for solutions that address it. These three dimensions interact in complex and sometimes counterintuitive ways that have significant implications for product strategy.

Frequency determines the degree to which a product becomes embedded in the customer’s workflow and behavioral routine. Problems that customers encounter daily tend to produce products with strong habit formation, high retention, and compounding network effects based on the data generated by frequent use. Spotify’s personalization advantage compounds precisely because listening is a daily or near-daily behavior, generating the behavioral signal density required for recommendation algorithms to develop meaningful personalization over time (Railsware, 2024). Problems that customers encounter infrequently—even if intensely experienced when they occur—tend to produce products with weaker habit formation, higher churn risk (owing to the extended intervals between problem encounters during which alternatives can be adopted), and lower data generation rates.

The strategic implication for product leaders is that high-frequency problems tend to produce stronger long-term product positions than high-intensity, low-frequency problems—even when the low-frequency problem is significantly more painful to experience. An annual tax preparation problem is intensely experienced when it occurs, but the low frequency creates a weak behavioral habit, a long window between purchase decisions during which a competitor can win the customer’s next encounter, and limited data generation to support personalization and product improvement.

Intensity captures the depth of the customer’s experienced difficulty with the problem—a dimension that is not always correlated with frequency. Problems of high intensity but low frequency (serious medical conditions, enterprise procurement decisions, legal disputes) tend to produce high willingness to pay per solution encounter but weak recurring engagement. Problems of moderate intensity but high frequency (organizational communication overhead, repetitive data entry, navigating enterprise software complexity) tend to produce lower willingness to pay per interaction but stronger recurring engagement and more durable product dependency.

The interaction between frequency and intensity is strategically revealing: the most commercially attractive product opportunities tend to lie in problems that are both high-frequency and high-intensity—problems that customers encounter regularly and experience acutely enough that they are continuously motivated to invest in better solutions. These problems are, by definition, scarce. Product leaders who are examining a problem along both dimensions and find themselves confronting a high-intensity, low-frequency dynamic should ask whether product design and business model architecture can engineer frequency into the customer’s experience of the solution—through ancillary features, related workflow integration, or a platform approach that creates additional use cases that draw customers into daily engagement.

Willingness to pay is the dimension that most directly connects problem evaluation to commercial viability—and it is the dimension most susceptible to the cognitive biases that Kahneman and Tversky’s (1979) prospect theory and subsequent behavioral economics research have documented. The key insight from this body of research for product leaders is that willingness to pay is not a stable attribute of the customer that can be reliably elicited through direct questioning; it is a judgment that is constructed in context, shaped by the customer’s comparison set, by the framing of the value proposition, and by the reference points against which the proposed price is evaluated (Kahneman & Tversky, 1979; Thaler, 1980).

The practical implication for problem selection is that the willingness to pay exhibited by customers in research settings—interviews, surveys, conjoint analyses—should be interpreted as directional evidence rather than precise measurement. The more strategic question is whether the structural conditions that tend to produce high willingness to pay are present in the problem context: (1) a clear baseline cost of not solving the problem, expressed in terms the customer can readily quantify; (2) a competitive context in which the customer has limited alternative solutions; and (3) a problem severity that the customer is motivated to discuss with budget holders rather than tolerating as an organizational fact of life (Ibbaka, 2024).

Behavioral Economics in Problem Selection: The Gap Between Stated Preference and Revealed Behavior

One of the most consequential and least adequately addressed insights from behavioral economics for product leaders concerns the systematic gap between what customers say they want and what their behavior reveals they will actually pay for, adopt, and continue using. This gap is not a methodological artifact of flawed research; it is a structural feature of human decision-making that Kahneman and Tversky’s (1979) prospect theory, Thaler and Sunstein’s (2008) nudge framework, and a substantial body of subsequent behavioral research have documented with considerable empirical precision.

Several behavioral constructs are particularly consequential for problem selection and product strategy. Loss aversion—the empirically documented tendency for people to weight losses approximately twice as heavily as equivalent gains—has direct implications for how product leaders should evaluate and position customer problems. Problems that customers experience as losses (capabilities degraded, time wasted, revenue foregone, competitive disadvantage accumulated) tend to generate more behavioral motivation and, accordingly, stronger adoption dynamics than problems framed as missed opportunities for gain, even when the objective magnitude of the value differential is comparable. Product leaders who understand this dynamic can use it both in problem selection (prioritizing problems that are experienced as losses rather than deferred gains) and in product positioning (framing the product’s value in terms of loss prevention rather than benefit acquisition, when the underlying problem warrants it).

Status quo bias—the preference for current arrangements that Kahneman, Knetsch, and Thaler (1991) documented as a systematic feature of decision-making—has equally significant implications for problem selection, particularly in enterprise contexts where product adoption requires customers to change established workflows, retire existing tools, or retrain behavioral habits. Products that require customers to abandon significant prior investment in tools, processes, or skills face an adoption friction that is not captured in willingness-to-pay research conducted in the absence of an incumbent solution. Product leaders who evaluate problems without adequately accounting for the incumbent switching cost—the behavioral and organizational inertia that the status quo bias generates—will systematically overestimate adoption velocity and underestimate the investment required to achieve it.

The endowment effect—the tendency for people to value things they already possess more highly than equivalent things they do not—compounds the status quo bias in enterprise software contexts. Customers who have invested in an existing solution, built workflows around it, and developed organizational familiarity with it will evaluate its capabilities more favorably than an objective performance comparison would warrant. This means that the product’s value proposition must overcome not only the functional gap between the incumbent and the challenger but also the behavioral premium the customer places on the incumbent by virtue of existing ownership—a premium that is not rational in the classical economic sense but is highly predictable and operationally significant.

These behavioral dynamics suggest that the most strategically sound problem selection process attends not only to the frequency and intensity of the customer’s experienced problem, but also to the behavioral architecture of the adoption journey—the specific cognitive biases and decision-making patterns that will govern the customer’s evaluation of a new solution and the organizational dynamics that will shape the adoption and retention trajectory. Product leaders who build this behavioral architecture into their problem evaluation process from the outset are better positioned to design products that are not merely valuable in principle but adopted in practice.

The Problem Worth Solving: A Synthesis for the AI Era

In the context of AI-native and agentic product development, the frameworks developed in this essay take on additional strategic significance. The technical ease of building AI-powered products—and the corresponding organizational pressure to demonstrate AI adoption—has created a perverse incentive to identify problems that AI can technically address rather than problems that are strategically worth solving. Product leaders who allow this dynamic to govern their problem selection process will build products that showcase impressive AI capabilities in service of problems that customers are not sufficiently motivated to solve.

The evidence suggests that the most durable AI product opportunities are concentrated in problems that satisfy the full framework outlined here: they are painkiller problems rather than vitamin problems for the target customer segment; they are problems of high frequency and high intensity that generate sufficient behavioral signal to enable the personalization and adaptation advantages that AI capabilities uniquely enable; they generate willingness to pay that is grounded in a clear, quantifiable cost of the unsolved problem; and they create an adoption journey whose behavioral complexity is understood and designed for from the outset (Presta, 2026; AI PM Tools Directory, 2026).

The product leader who asks these questions rigorously—before committing to build—is practicing the kind of problem selection discipline that distinguishes strategic product thinking from technically impressive feature development. The question is not whether the AI capability is impressive. The question is whether the problem it addresses is worth solving.

References

AI PM Tools Directory. (2026). The future of AI in product management: 2026–2030 predictions. https://aipmtools.org/articles/future-of-ai-product-management

Ibbaka. (2024). Core concepts: Willingness to pay. https://www.ibbaka.com/ibbaka-market-blog/core-concepts-willingness-to-pay

Kahneman, D., Knetsch, J. L., & Thaler, R. H. (1991). Anomalies: The endowment effect, loss aversion, and status quo bias. Journal of Economic Perspectives, 5(1), 193–206. https://doi.org/10.1257/jep.5.1.193

Kahneman, D., & Tversky, A. (1979). Prospect theory: An analysis of decision under risk. Econometrica, 47(2), 263–291. https://doi.org/10.2307/1914185

OpenView Partners. (2024). What behavioral economics can teach us about pricing. https://openviewpartners.com/blog/behavioral-pricing/

Presta. (2026). AI product strategy 2026: The founder’s guide to AI-native growth. https://wearepresta.com/ai-product-strategy-2026-the-founders-guide-to-ai-native-growth/

Railsware. (2024). Jobs to be done examples: Spotify, Duolingo, Uber cases. https://railsware.com/blog/jobs-to-be-done-examples/

Ramadan, A., Peterson, D., Lochhead, C., & Maney, K. (2016). Play bigger: How pirates, dreamers, and innovators create and dominate markets. HarperBusiness.

SHS Web of Conferences. (2023). Product features that hit consumers’ pain points may lead to reduced willingness to pay. SHS Web of Conferences, FEMS 2023, 01074. https://www.shs-conferences.org/articles/shsconf/abs/2023/18/shsconf_fems2023_01074/shsconf_fems2023_01074.html

Thaler, R. H. (1980). Toward a positive theory of consumer choice. Journal of Economic Behavior & Organization, 1(1), 39–60. https://doi.org/10.1016/0167-2681(80)90051-7

Thaler, R. H., & Sunstein, C. R. (2008). Nudge: Improving decisions about health, wealth, and happiness. Yale University Press.

Extant research in strategic management and product practice suggests that the organizations that sustain competitive advantage over long time horizons are not those that conduct market analysis most thoroughly at the outset of a planning cycle, but those that maintain a living, continuously updated understanding of the markets in which they compete—including the dynamics that govern those markets’ evolution, the patterns by which disruptive forces enter and reshape them, and the timing risks that determine whether a strategic bet is premature, well-timed, or belated (Christensen, 1997; Moore, 1991). This essay endeavors to develop a structured understanding of four market dynamics that are most consequential for product strategy: the architecture of market sizing through TAM, SAM, and SOM; the structural stages of market maturity; the patterns by which disruption enters and transforms established markets; and the timing risks that determine whether a product strategy is positioned for the market it will face rather than the market that currently exists.

TAM, SAM, SOM: Market Sizing as Strategic Framing, Not Just Financial Arithmetic

The trio of Total Addressable Market (TAM), Serviceable Available Market (SAM), and Serviceable Obtainable Market (SOM) has become a standard fixture of product strategy documents and investor pitch decks, often to the point of ritualistic compliance: the estimates are produced, the opportunity is declared substantial, and the analysis proceeds no further. This represents a significant underuse of what is, when applied with analytical rigor, a genuinely powerful strategic framing tool.

TAM, in its most useful formulation, is not simply a number—it is a claim about the total revenue opportunity available if the product were to achieve 100% market penetration across the entire universe of potential customers who have the problem the product addresses. This framing immediately exposes the most consequential strategic choice embedded in a TAM estimate: the definition of the problem and the customer universe. A product team that defines its TAM narrowly—around the specific solution it has built rather than the underlying problem it addresses—will systematically underestimate the competitive threats that emerge from adjacent solution approaches. Conversely, a product team that defines its TAM too broadly—capturing every organization that theoretically has a related need—will overestimate the addressable opportunity and underestimate the segmentation work required to achieve initial traction.

The SAM, the portion of TAM the product can realistically serve given its current capabilities, geographic reach, pricing model, and sales motion, is where strategic honesty becomes most demanding. SAM forces the product team to answer concretely which customer segments, geographies, and use cases the product is currently equipped to serve, and to confront the gap between the total market and what the product can credibly pursue in the current planning horizon. This gap is not a failure; it is a strategic input that should shape investment priorities in capabilities, distribution, and market development.

The SOM—the portion of SAM the product can realistically capture in the near term, given competitive dynamics, sales capacity, and market awareness—is where market sizing connects most directly to execution planning. SOM estimates are the most frequently inflated of the three, owing to the organizational incentive to demonstrate large near-term opportunity. Extant practitioner analysis suggests that startups with data-backed SOM projections exceeding 15% annual growth attract substantially more investment attention, creating a structural pressure toward optimistic SOM estimation that experienced product and strategy leaders must actively counterbalance (PitchBook, as cited in Topmostads, 2025).

In the context of AI and LLM-powered products, the TAM/SAM/SOM framework requires a significant methodological adaptation. The standard top-down approach to market sizing—starting from an established market category, applying penetration rate assumptions, and deriving an addressable opportunity—is structurally inapplicable to markets that do not yet exist in their current form, or that are being reshaped in real time by AI capabilities. The generative AI market, for example, expanded its estimated TAM from approximately $30 billion in 2022 to $185 billion by 2025, not because market analysts revised their assumptions, but because the market itself was being continuously redefined by capability advances and new use case discovery (Grand View Research, as cited in Topmostads, 2025). For product leaders operating in rapidly evolving AI markets, the bottom-up approach—sizing the market from first principles by estimating the number of customers who have the specific problem, the value of solving it, and the willingness to pay at various solution qualities—tends to produce more reliable and more strategically useful estimates than top-down TAM analysis anchored in historical market categories.

Market Maturity: Navigating the Lifecycle of Competitive Intensity

Market maturity is one of the most consequential contextual variables in product strategy, and one of the most frequently underweighted. The competitive dynamics, customer behaviors, investment requirements, and differentiation strategies that produce success in an emerging market are structurally different from those that produce success in a maturing or commoditizing market—and product leaders who apply the same strategic logic across these different market stages tend to produce systematically poor outcomes.

The product market lifecycle, in its classical formulation, progresses through four stages: introduction, growth, maturity, and decline. Each stage is characterized by a different competitive dynamic and, correspondingly, a different set of strategic imperatives. In the introduction stage, the primary strategic challenge is demand creation—educating the market about the existence of the problem, demonstrating the feasibility of the solution, and achieving sufficient initial traction to attract the resources needed for the next stage. Competitive intensity is low, not because competitors have been defeated, but because the market is not yet large enough to attract organized competitive attention. In the growth stage, the primary strategic challenge shifts from demand creation to competitive positioning: the market has been validated, multiple competitors are entering or scaling, and the product strategy must articulate a clear differentiation logic that makes the product the preferred choice for a defined customer segment. In the maturity stage, the primary strategic challenge is differentiation through depth and integration—most products in the category have achieved feature parity at the core, and sustainable competitive advantage requires building the kind of ecosystem integration, customer dependency, and platform depth that creates structural switching costs rather than merely functional preference.

The strategic implication for product leaders is that they must maintain a clear, current assessment of where their market sits in this lifecycle, and must calibrate their strategic choices accordingly. A product strategy that is appropriate for the growth stage—aggressive feature development, broad customer segment targeting, high investment in market development—is strategically counterproductive in a mature market, where the imperative is depth over breadth and retention over acquisition. Conversely, a mature-market strategy applied in an emerging market—conservative investment, narrow targeting, deep optimization of the current offering—will cede the market development opportunity to more aggressive competitors.

In the current landscape of AI-native product categories, the speed at which market maturity is progressing has accelerated markedly. The enterprise AI assistant category, for example, moved from introduction to early competitive intensity in less than eighteen months between 2023 and 2024, as the rapid commoditization of foundation model access enabled a large number of competitors to enter the market with functionally similar offerings in a compressed timeframe (AI PM Tools Directory, 2026). Product leaders in rapidly maturing AI categories face a compressed window in which to establish the differentiated positioning and customer dependency that will sustain competitive advantage through the maturity stage.

Disruption Patterns: Structural Recognition of How Markets Get Transformed

Christensen’s (1997) disruption theory remains one of the most analytically productive frameworks available to product leaders for understanding the structural dynamics by which new entrants transform established markets. Its central insight—that the attributes along which products improve over time are not always the attributes that existing customers value most, and that the gap between what incumbents can provide and what low-end or new-market customers require creates the structural opening for disruptive entry—has been validated across a broad range of industries and technological contexts.

The practical implication for product strategy is twofold. First, product leaders in established product categories must maintain active surveillance for potential disruptive entrants—specifically, for competitors who are entering the market with offerings that are inferior on the traditional dimensions of product evaluation but are accessible, affordable, or structurally simpler in ways that serve segments the incumbent has underserved or ignored. The classic disruptive pattern—minicomputers disrupting mainframes, personal computers disrupting minicomputers, smartphones disrupting personal computers for many use cases—is not a historical curiosity; it is a recurrent structural dynamic that operates across technology categories with a regularity that product leaders should treat as a baseline expectation rather than an exceptional event.

Second, product leaders in startup and early-growth contexts should actively interrogate the potential disruptive logics available to them in their markets. The most promising disruptive positions are typically found not by asking “how do we build a better version of the existing product?” but by asking “which customer segments are currently excluded from or underserved by existing solutions, and what would it take to serve them with a product that is acceptable on the dimensions they value most?” This question reframes the competitive arena from the incumbent’s perspective to the underserved customer’s perspective—and in doing so, often reveals strategic opportunities that are invisible from the conventional competitive vantage point.

Moore’s (1991) Crossing the Chasm framework provides a complementary lens, focusing specifically on the structural discontinuity that exists between the early adopter segment—which tolerates product immaturity, actively seeks novel approaches, and is motivated primarily by the prospect of competitive advantage from early adoption—and the early majority, which is pragmatic, risk-averse, and requires social proof, reference customers, and a well-defined use case before committing to adoption. Products that fail to cross this chasm—and the majority of disruptive products do fail here—typically do so not because of technical deficiency but because of strategic underdetermination: the absence of a focused, concentrated market entry strategy that builds a reference-customer base sufficient to trigger the social proof dynamics on which the early majority depends.

In the AI product context, the chasm dynamic is playing out with particular intensity in the enterprise segment. Many AI-powered products have achieved strong early-adopter traction with technically sophisticated or innovation-oriented users, but are discovering that crossing to the enterprise mainstream requires a different product posture—more reliability, more security and compliance infrastructure, more integration with existing enterprise systems, and more clearly defined ROI metrics—than the early-adopter segment demanded (Gocious, 2026). Product leaders who understand the structural nature of this transition are better equipped to make the investments that bridge the chasm than those who interpret early-adopter traction as a direct predictor of mainstream adoption.

Timing Risk: The Underappreciated Determinant of Strategic Outcome

Of all the variables that determine the outcome of a strategic bet, timing is among the most consequential and least controllable. Extant research on market entry timing suggests that the optimal entry window for a new product category is neither as early as possible nor as late as possible, but rather at the point where the supporting conditions for market adoption—technology infrastructure, customer awareness, regulatory environment, and complementary product ecosystem—are sufficiently mature to enable a critical mass of early customers to derive value from the offering, while the competitive landscape is not yet crowded enough to render differentiation prohibitively expensive (Christensen, 1997; Moore, 1991).

The structural challenge of timing risk is that it cannot be fully assessed at the time of the strategic bet. The same product, with the same strategy, launched six months earlier or six months later, can produce radically different outcomes—a fact that is systematically obscured by the survivorship bias in strategy case studies, which tend to celebrate the companies that timed their market entries well while underweighting the many organizations that pursued sound strategies at the wrong moment.

Several categories of timing risk are particularly consequential for product leaders to monitor. Infrastructure timing risk describes the condition in which the technology or data infrastructure required for a product to deliver its full value proposition has not yet achieved sufficient maturity, reliability, or cost-effectiveness to support mainstream adoption. Many early AI product failures in the 2011–2015 period were attributable to infrastructure timing risk: the underlying machine learning infrastructure was not yet capable of delivering the product experience that mainstream customers required. The second wave of AI adoption, beginning in 2022, succeeded partly because the infrastructure conditions had changed, not because the original product ideas were wrong.

Adoption readiness risk describes the condition in which the customer mindset, organizational processes, and adjacent product ecosystem have not yet evolved to the point where the proposed product fits into a coherent and viable customer workflow. The failure of many early enterprise collaboration tools in the late 1990s and early 2000s—products that were, in concept, entirely viable—was attributable partly to adoption readiness risk: the organizational practices, hardware infrastructure, and network connectivity required to support collaborative digital workflows had not yet reached the threshold required for mainstream adoption. The same product category, launched a decade later, produced lasting market successes.

For product leaders operating in the AI era, timing risk has acquired a new dimension: the risk of building on a capability that will be commoditized before the product can establish sufficient switching costs to sustain its competitive position. This represents a distinctive form of the classical timing problem—the window between the point at which a capability becomes technically feasible and the point at which it becomes broadly available through commodity infrastructure is narrowing, compressing the available time to build and consolidate a market position before the structural advantage of early access evaporates (Presta, 2026).

References

AI PM Tools Directory. (2026). The future of AI in product management: 2026–2030 predictions. https://aipmtools.org/articles/future-of-ai-product-management

Christensen, C. M. (1997). The innovator’s dilemma: When new technologies cause great firms to fail. Harvard Business School Press.

Christensen, C. M., & Raynor, M. E. (2003). The innovator’s solution: Creating and sustaining successful growth. Harvard Business School Press.

Gocious. (2026). AI in product management guide for 2026 for product leaders. https://gocious.com/blog/ai-in-product-management-guide-for-2026-for-product-leaders

HG Insights. (2025). TAM, SAM, SOM: The complete guide to market sizing. https://hginsights.com/blog/tam-sam-som-the-complete-guide-to-market-sizing/

Moore, G. A. (1991). Crossing the chasm: Marketing and selling high-tech products to mainstream customers. HarperBusiness.

Predictable Innovation. (2024). Crossing the chasm: Framework, meaning & the 6 mistakes everyone makes. https://predictableinnovation.com/methods/crossing-the-chasm-framework-mistakes

Presta. (2026). AI product strategy 2026: The founder’s guide to AI-native growth. https://wearepresta.com/ai-product-strategy-2026-the-founders-guide-to-ai-native-growth/

Ruddock, M. (2024). Crossing the chasm vs the innovator’s dilemma. https://markruddock.com/blog/2024/9/8/crossing-the-chasm-vs-the-innovators-dilemma

Topmostads. (2025). TAM SAM SOM explained: Complete guide to market sizing in 2025. https://topmostads.com/tam-sam-som-explained-market-sizing-2025/

WaveUp. (2026). TAM, SAM, SOM 2026: How to calculate market size. https://waveup.com/blog/tam-sam-som/

Extant research on organizational strategy and innovation management has characterized these differences in terms of the fundamental strategic objectives each context pursues: startups are primarily engaged in the discovery and validation of a business model—the identification of a repeatable, scalable mechanism for creating and capturing value that does not yet exist in a proven form—while enterprises are primarily engaged in the optimization, defense, and expansion of business models that have already been validated (Ries, 2011; Christensen, 1997). This structural difference has implications that cascade through every aspect of product strategy: the kind of information that matters, the kind of decisions that need to be made, the organizational structures that support good decision-making, and the metrics that indicate strategic progress.

This essay endeavors to develop a nuanced account of these differences across four dimensions: the structural constraints that shape strategic possibility in each context, the speed-scale trade-off and how it manifests in product strategy, the distinct dynamics of founder-led versus PM-led strategy and the conditions under which each is appropriate, and the innovation-optimization tension and how product leaders should navigate it across the organizational lifecycle.

Different Constraints, Different Strategic Possibility Spaces

The most fundamental structural difference between startups and enterprises is not resource level—though resource availability matters—but the nature of the constraints that bound strategic choice. Startup strategy is shaped primarily by uncertainty constraints: the core questions of which customer segment will pay for the product, which use cases will drive recurring value, which business model will generate sustainable margin, and which competitive position is achievable given the organization’s resources are all, at the earliest stages, genuinely unknown. The strategic task of a startup is therefore primarily epistemic: to reduce the uncertainty that determines whether the business is viable as quickly as possible, using the minimum resources necessary to generate sufficiently conclusive evidence.

Enterprise strategy, by contrast, is shaped primarily by organizational and structural constraints: the installed customer base, the existing product architecture, the partner and channel ecosystem, the organizational culture and capability set, and the legacy of prior strategic commitments that have hardened into structural dependencies. These constraints are not inherently limiting—they are also the sources of competitive advantage that the enterprise’s market position represents—but they shape the strategic possibility space in ways that product leaders operating in enterprise contexts must understand and account for.

A particularly consequential implication of this difference concerns the cost of being wrong. In a startup operating in genuine uncertainty, the cost of a strategic bet that does not pan out is, in the early stages, primarily opportunity cost—the time and resources invested in validating a hypothesis that turns out to be false could have been invested in validating a different hypothesis. The strategic prescription is therefore to make bets cheaply, validate them quickly, and pivot rapidly when evidence disconfirms the hypothesis. This is the core logic of the lean startup methodology (Ries, 2011) and the approach Marty Cagan’s product operating model prescribes for product discovery (Cagan, 2023).

In an enterprise context, the cost calculus is fundamentally different. The cost of a strategic bet that does not pan out is not merely opportunity cost; it is the cost of the organizational disruption, customer confusion, partner misalignment, and capability misapplication that accompany a strategic pivot in a large, complex organization. This structural asymmetry is one of the primary reasons enterprises tend toward strategic conservatism—not because enterprise product leaders are less innovative, but because the organizational cost of strategic error is genuinely higher in a context where strategic commitments have wide structural ramifications.

The AI era has introduced a new dimension to this constraint analysis. For startups, the availability of powerful foundation models has dramatically lowered the technical constraint on building AI-powered products—capabilities that would have required years of ML research and substantial data assets can now be accessed through API calls. This shifts the binding constraint for AI startups from technical capability to strategic clarity: the organizations that succeed are those that most clearly answer the question of which customer, which use case, and which competitive position they are building toward, not those with the most advanced technical capabilities (Presta, 2026). For enterprises, the AI constraint is different: it is primarily an organizational and data architecture constraint—the challenge of integrating AI capabilities into existing systems, customer workflows, and data environments without disrupting the operational stability that the installed customer base depends on (Gocious, 2026).

Speed Versus Scale: The Fundamental Strategic Trade-Off

The tension between speed and scale is perhaps the most visible and most frequently discussed dimension of the startup-enterprise strategic divide. Startups are structurally configured for speed: small teams, minimal process overhead, direct access to decision-makers, and the urgent pressure of resource constraints create an organizational context in which rapid iteration, rapid customer learning, and rapid strategic adaptation are not merely possible but necessary for survival. Enterprises are structurally configured for scale: large teams, formalized processes, distributed decision-making, and the operational demands of serving large customer bases create an organizational context in which predictability, consistency, and managed complexity are the primary performance requirements.

The strategic implications of this structural difference are consequential. For startup product leaders, the primary risk is not moving too fast—it is spending time and resources on the wrong initiatives before achieving sufficient strategic clarity. The product strategy question is therefore always: “what is the cheapest, fastest way to get conclusive evidence that this is the right bet?” This orientation toward validated learning shapes every aspect of product strategy in the startup context: the choice of customer segments to serve, the features to include in the initial product, the pricing model to test, and the metrics to track.

For enterprise product leaders, the primary risk is the inverse: moving too slowly on strategic bets that require organizational transformation, and allowing the compounding of organizational inertia to delay the investments necessary to sustain competitive position. The product strategy question is therefore: “given the organizational constraints we operate within, what is the sequence of moves that most effectively shifts our competitive position without disrupting the operational stability our customers depend on?” This orientation toward managed transformation shapes enterprise product strategy in ways that can look, from the outside, like strategic conservatism but is often, from the inside, a rational response to the structural cost of organizational disruption.

Instagram’s early strategic evolution is instructive on the startup side. The product pivoted from a location-sharing application called Burbn to a focused photo-sharing application after the founders observed that photo sharing was the most actively used feature in the original product. The pivot was rapid, resource-constrained, and grounded in direct behavioral evidence from users—a textbook illustration of the lean startup approach applied to a genuine strategic question about where to play (ProductPlan, 2024). The strategic clarity that resulted—a single, focused product optimized for one use case—was the foundation of the product’s subsequent growth.

Adobe’s transition from perpetual licensing to the Creative Cloud subscription model illustrates the enterprise side. The transition—which required simultaneously managing the decline of a profitable legacy business model, building the organizational capabilities required to operate a subscription business, and managing customer and channel partner relationships through a period of significant disruption—took several years and required sustained senior leadership commitment. The speed of the strategic move was constrained not by strategic ambiguity (the strategic logic was clear) but by the organizational complexity of executing a business model transformation at scale without destroying the installed customer base that represented the organization’s primary source of revenue during the transition (ToughTongueAI, 2024).

In the context of AI product development, this speed-scale tension has become acute. The pace of capability advancement in foundation models is sufficiently rapid that strategic windows—periods in which a given strategic bet is uniquely valuable before the capability becomes widely available—are opening and closing on a timescale of months rather than years. Startup product leaders, operating with the speed advantage their organizational context provides, are better positioned to pursue these narrow windows. Enterprise product leaders, navigating the complexity of large-scale AI integration, risk arriving at strategic positions that are no longer differentiated by the time the organizational execution is complete (AI PM Tools Directory, 2026).

Founder-Led Versus PM-Led Strategy: Authority, Intuition, and Organizational Context

The distinction between founder-led and PM-led product strategy is one of the most consequential and least analytically examined in the practitioner literature. The prevailing assumption—that as organizations grow, strategy should progressively shift from founder intuition to PM analytical rigor—is too simple and, in some respects, structurally misleading.

Founder-led product strategy is characterized by several distinctive features. First, the founder’s authority over the product is typically unmediated by organizational hierarchy: the founder can make strategic bets quickly, communicate them directly throughout the organization, and hold the organization accountable to them without the negotiation and consensus-building that characterize strategic decision-making in more mature organizations. Second, the founder typically has a concentrated, personally constructed understanding of the customer problem and market context—built through direct customer engagement, competitive analysis, and the lived experience of building the product—that is not distributed across an organizational team. Third, the founder’s risk tolerance tends to be different from an employed executive’s: founders typically bear personal financial risk tied to the outcome of strategic bets, which shapes their willingness to make concentrated, non-consensus bets.

The strategic advantages of founder-led product strategy are well documented in the practitioner literature. Y Combinator’s guidance to early-stage founders emphasizes that the primary strategic asset of a startup in its earliest phase is the founder’s direct understanding of the customer problem—an asset that is progressively diluted as the organization hires and as organizational processes mediate the relationship between decision-makers and the customer (Kraftful, 2025). Paul Graham’s observation that founders should remain as close to the product as long as possible before delegating product decisions is a recognition that the founder’s concentrated market intelligence is a strategic resource that depreciates as organizational distance from the customer increases.

The risks of founder-led strategy are equally well documented. Founders whose concentrated market intelligence is grounded in an early customer set may systematically misperceive the needs of the broader market segment the product must eventually serve. Founders whose risk tolerance is calibrated for the early stage may make strategic bets at scale that are appropriate for the startup context but organizationally destructive in a more mature organizational context. And founders whose product intuition is genuinely excellent may struggle to create the organizational systems and processes that allow the strategy to be understood, communicated, and executed by a growing team.

PM-led product strategy, by contrast, is characterized by the distribution of strategic intelligence across an organizational team, the formalization of strategic decision-making processes, and the progressive institutionalization of the practices—customer research, competitive analysis, data-driven hypothesis testing—that allow strategic choices to be made on the basis of evidence rather than personal intuition. The strategic advantage of PM-led strategy is its scalability: a well-structured product strategy process can generate and evaluate strategic insights at a volume and diversity that exceeds the capacity of any individual founder, and can sustain strategic coherence across a large, geographically distributed organization.

The risk is the loss of the strategic conviction that concentrated founder intuition produces. PM-led strategy processes that are over-indexed on consensus and under-indexed on strategic clarity can produce what Rumelt (2011) characterizes as “bad strategy”—the elaboration of goals and aspirations without the analytical rigor to identify the central strategic challenge and make coherent choices about how to address it. The antidote, in the view of this essay, is not to restore founder-style intuition to PM-led organizations—that is neither possible nor desirable at scale—but to build PM-led organizations that have the analytical rigor to generate genuine strategic insight and the organizational authority to act on it without requiring consensus from every stakeholder.

Innovation Versus Optimization: The Strategic Lifecycle of Product Organizations

The final dimension of the startup-enterprise strategic divide concerns the organization’s position on the innovation-optimization spectrum—and the strategic consequences of misreading that position. Innovation and optimization are not merely different activities; they require different organizational structures, different incentive systems, different metrics, and different kinds of leadership. Organizations that apply optimization logic to contexts that require innovation, or that apply innovation logic to contexts that require optimization, will produce systematically poor outcomes in both directions.

Christensen’s (1997) disruption theory provides a foundational account of the structural dynamics that drive this tension. Established enterprises, in Christensen’s account, systematically underinvest in disruptive innovations—not because of managerial failure, but because of the structural logic of their business model: their most profitable customers are also the customers who benefit most from incremental improvements to existing products, and their organizational processes are calibrated to sustain that optimization logic. The result is a systematic pattern in which enterprises optimize their existing product strategy to the point of structural vulnerability, while startups discover and validate disruptive positions that the enterprise’s organizational logic prevents it from pursuing.

The strategic prescription that follows from this analysis is not that enterprises should abandon optimization in favor of innovation—optimizing the core business is a legitimate and important strategic activity—but that enterprises must develop organizational mechanisms for maintaining a portfolio of strategic bets that includes both optimization of the existing position and exploration of adjacent and disruptive positions. Amazon’s well-documented practice of operating separate organizational units for its core e-commerce business and its innovation portfolio—with different metrics, different resource allocation logic, and different leadership mandates—is a structural response to this challenge (FourWeekMBA, 2025). Google’s “70/20/10” resource allocation framework, which directed 70% of resources to the core business, 20% to adjacent opportunities, and 10% to transformational bets, represents a similar institutional response.

In the context of AI, this innovation-optimization tension has taken on acute strategic urgency. Enterprises that have built their competitive positions on capabilities that AI is progressively automating—knowledge work, customer service, content generation, data analysis—are simultaneously facing an optimization imperative (to integrate AI into their existing products and workflows to maintain cost competitiveness) and an innovation imperative (to identify the new strategic positions that emerge as AI reshapes the value chain in their market). These are structurally different strategic challenges, requiring different organizational postures, and the enterprises that conflate them—treating AI integration as a feature development problem rather than a strategic repositioning challenge—risk arriving at a future in which their existing position has been technically modernized but strategically superseded.

For startups, the AI era presents a mirror-image challenge. The technical ease of building AI-powered products creates an organizational pull toward what might be called premature optimization—the tendency to build elaborate feature sets and operational processes around a product strategy that has not yet been validated as strategically sound. Startups that invest heavily in AI infrastructure, model fine-tuning, and product sophistication before achieving genuine product-market fit are, in effect, optimizing a business model that has not been validated—a pattern that MIT Sloan research identified as responsible for a substantial proportion of startup failures (Product Art, 2024).

The strategic advice that this analysis generates for product leaders at each stage of the organizational lifecycle can be stated with some precision. For early-stage startup product leaders: the primary strategic task is discovery, not delivery; the primary metric of strategic progress is not feature completeness or user count but the degree to which the product’s value proposition has been validated in a repeatable, scalable form; and the primary risk to be managed is the misallocation of strategic attention—spending time and resources optimizing an unvalidated strategic position rather than maintaining the discovery discipline required to find the right position. For enterprise product leaders: the primary strategic task is not innovation at the expense of optimization but the development of organizational capacity to do both simultaneously; the primary metric of strategic progress is the rate at which the organization is building new sources of competitive advantage that compound alongside, rather than at the expense of, the existing position; and the primary risk to be managed is the organizational tendency to treat AI capability integration as a sufficient strategic response to a moment that requires genuine strategic repositioning.

The Convergence Point: What Startups and Enterprises Must Learn from Each Other

The startup-enterprise strategic divide, examined with sufficient analytical rigor, reveals not merely differences but a set of complementary strategic capabilities that each organizational context tends to develop and the other tends to lack. Startups, operating under the pressure of uncertainty and resource constraint, develop extraordinary capacity for rapid hypothesis generation, validated learning, and strategic pivot—capabilities that enterprises systematically underdevelop. Enterprises, operating under the pressure of scale and organizational complexity, develop extraordinary capacity for managed execution, customer relationship depth, and the organizational infrastructure required to sustain competitive position at scale—capabilities that startups systematically underdevelop.

The most effective product leaders—those who sustain strategic effectiveness across the organizational lifecycle—are those who have internalized both sets of capabilities and who can identify, in any given organizational context, which capability is the binding constraint on strategic progress. In the early stage, the binding constraint is almost always discovery discipline: the capacity to generate and validate strategic hypotheses quickly. In the growth and maturity stage, the binding constraint is almost always execution infrastructure: the organizational capacity to scale a validated strategy without losing its strategic coherence.

The age of AI has not resolved this tension; it has intensified it. The strategic windows available to AI-native startups are narrow and competitive. The organizational transformation required of AI-integrating enterprises is substantial and complex. Product leaders in both contexts who develop the strategic clarity to understand which constraints bind them, which capabilities they need to develop, and which strategic logic applies to their organizational position are the ones who will build the products that matter most in the decade ahead.

References

AI PM Tools Directory. (2026). The future of AI in product management: 2026–2030 predictions. https://aipmtools.org/articles/future-of-ai-product-management

Cagan, M. (2023). Transformed: Moving to the product operating model. Wiley.

Christensen, C. M. (1997). The innovator’s dilemma: When new technologies cause great firms to fail. Harvard Business School Press.

FourWeekMBA. (2025). Amazon AWS platform business model in a nutshell. https://fourweekmba.com/amazon-aws-platform-business-model/

General Catalyst. (2025). The early stage founder’s guide to product-led growth. https://www.generalcatalyst.com/stories/the-early-stage-founders-guide-to-product-led-growth

Gocious. (2026). AI in product management guide for 2026 for product leaders. https://gocious.com/blog/ai-in-product-management-guide-for-2026-for-product-leaders

Kraftful. (2025). A YC founder’s guide to product management. https://www.kraftful.com/blogs/pm-guide-for-founders

Pragmatic Institute. (2024). Startups vs. enterprises: Navigating product management in different worlds. https://www.pragmaticinstitute.com/resources/podcasts/product/startups-vs-enterprises-navigating-product-management-in-different-worlds-with-arturo-pina/

Presta. (2026). AI product strategy 2026: The founder’s guide to AI-native growth. https://wearepresta.com/ai-product-strategy-2026-the-founders-guide-to-ai-native-growth/

Product Art. (2024). Why product roadmaps are destroying strategic thinking. Substack.

https://productart.substack.com/p/why-product-roadmaps-are-destroying

ProductPlan. (2024). What product managers can learn from 4 products that flopped. https://www.productplan.com/learn/4-products-that-flopped

Ries, E. (2011). The lean startup: How today’s entrepreneurs use continuous innovation to create radically successful businesses. Crown Business.

Rumelt, R. P. (2011). Good strategy bad strategy: The difference and why it matters. Crown Business.

ToughTongueAI. (2024). 6 product strategy case studies — Apple, Netflix, Meta, Spotify & Amazon. https://www.toughtongueai.com/blog/product-strategy-case-studies

Tech for Non-Techies. (2024). Founder-led vs. product-led growth: How to pick the right path for your startup. https://www.techfornontechies.co/blog/266-founder-led-vs-product-led-growth-how-to-pick-the-right-path-for-your-startup

Extant research in strategic management and product leadership has articulated various framings of this layered architecture, from the classical corporate-business-functional hierarchy of Porter (1980) and Andrews (1971), to the more recent Product Strategy Stack articulated by practitioners at Reforge (2024), to the platform strategy literature that has emerged from the study of multi-sided markets and digital ecosystems (Bain & Company, 2025). What this essay endeavors to offer is a synthesis of these framings that is both conceptually rigorous and practically usable for senior product leaders—a navigational map for understanding which layer they are operating at, what questions that layer is responsible for answering, and how decisions at each layer constrain and enable decisions at the layers above and below.

The five layers examined here are: company strategy, which sets the organizational mission and the portfolio logic for how the company will create and capture value; business strategy, which defines how a particular business unit or product line will compete within a given market; product strategy, which specifies the choices about where the product plays and how it wins within the competitive arena defined by business strategy; platform strategy, which addresses how a product evolves from a discrete offering into an ecosystem that creates value for and captures value from multiple participant types; and execution strategy, which translates strategic choices into a coherent, sequenced portfolio of work. Each of these layers is distinct, and each requires a different analytical posture from the product leader who operates within it.

Company Strategy: The Portfolio Logic of Value Creation and Capture

Company strategy operates at the highest level of abstraction and addresses the most foundational questions an organization faces: (1) what is the organization’s mission—the enduring purpose it endeavors to fulfill?; (2) in what domains, markets, or technologies will the organization invest its resources, and why?; and (3) how does the portfolio of businesses, products, and capabilities the organization operates collectively create and capture value in a way that no single product or business unit could achieve independently?

The defining characteristic of company strategy, in contrast to the layers below it, is that it is inherently a portfolio logic. A company strategy does not optimize for the success of any single product or business; it optimizes for the collective performance of the portfolio and for the organizational capabilities and positioning that create the conditions for sustained competitive advantage across multiple time horizons. Apple’s company strategy—to build an integrated ecosystem of hardware, software, and services that generates compounding switching costs and loyalty across the full arc of a customer’s digital life—is not a product strategy; it is a portfolio logic that governs which products Apple invests in, how they interoperate, and why Apple chooses to control the full stack from chip to cloud (Medium, 2025).

For product leaders, the practical implication of company strategy is that it defines the strategic context within which all product choices are made. A product strategy that is coherent in isolation but misaligned with the company’s portfolio logic will struggle to secure organizational resources, will encounter friction in cross-functional alignment, and will, in the long run, create strategic complexity that weakens rather than strengthens the organization’s overall position. Conversely, a product strategy that is deeply aligned with and expressive of the company strategy can draw on organizational capabilities, brand equity, and distribution advantages that are inaccessible to products operating in misalignment.

In the age of agentic AI, company strategy has taken on renewed importance as organizations grapple with the question of how AI capabilities fit within their broader portfolio logic. The organizations that have navigated this transition most effectively—Microsoft with its Copilot ecosystem, Salesforce with Agentforce, Google with its Gemini integration across Workspace—have answered this question at the company strategy level first: deciding that AI would be woven into the fabric of every product rather than housed in a separate AI product line, and building the organizational capabilities, data infrastructure, and partnership ecosystem required to execute on that logic at scale (Gocious, 2026).

Business Strategy: Defining the Competitive Arena and the Winning Aspiration

Business strategy operates one level below company strategy and addresses the competitive posture of a specific business unit, product line, or market segment. Where company strategy addresses the portfolio logic across domains, business strategy addresses a single domain: the specific arena in which the business unit will compete, the value proposition it will offer to the customer segment it has chosen, and the structural basis on which it intends to achieve a superior competitive position.

Lafley and Martin’s (2013) Strategic Choice Cascade—with its emphasis on Where to Play and How to Win as the heart of strategy—is, in its original formulation, a business strategy framework. The five choices in the cascade (winning aspiration, where to play, how to win, core capabilities, management systems) are choices about how a specific business unit or product line will compete in its chosen market, not about how the parent organization will allocate its portfolio. Understanding this distinction is important for product leaders who apply the framework to their work: they are, in most cases, working at the business or product strategy level, not the company level, and the choices they make must be consistent with, though not determined by, the company’s portfolio logic.

The strategic options available at the business strategy level have been well-characterized in the strategy literature. Porter’s (1980) classic formulation distinguished between cost leadership (achieving a structural cost advantage that allows the business to compete on price without sacrificing margin), differentiation (achieving a product or service quality advantage that allows the business to command a price premium), and focus (targeting a specific segment or niche with a tailored value proposition). While the original formulation has been elaborated and qualified substantially in subsequent decades, the underlying logic—that durable competitive advantage requires a distinctive positioning rather than an attempt to be all things to all customers—remains both analytically sound and practically relevant.

In the context of AI-powered businesses, the business strategy question has a distinctly new dimension. Extant research and practitioner commentary suggest that the primary sources of competitive advantage in AI-native businesses are increasingly concentrated in three areas: proprietary data assets that enable superior model training or grounding, workflow integrations and switching costs that create deep customer dependency, and network effects that increase the value of the platform as the user base grows (Presta, 2026; Reforge, 2024). Business strategies that are not grounded in at least one of these structural advantages face the risk of commoditization as foundation model capabilities continue to advance and access remains widely available.

Product Strategy: The Choices That Define Where a Product Competes and Why It Wins

Product strategy is the layer at which most product leaders spend the majority of their strategic attention, and it is the layer whose definition is most contested and most frequently conflated with adjacent constructs. In the framework developed here, product strategy occupies the space between business strategy—which defines the competitive arena—and execution strategy—which defines how the product team will deploy its resources in pursuit of strategic objectives. Product strategy answers the question: given the business we have chosen to be in and the competitive posture we have adopted, what specific choices about customers, use cases, capabilities, and competitive positioning will the product make in order to win?

The Reforge (2024) Product Strategy Stack offers a useful structural framing of how product strategy relates to the layers above and below it. In Reforge’s formulation, product strategy serves as the connective tissue between company objectives and product team work—it is more specific than company mission but more durable than quarterly roadmap priorities, and it provides the logical structure within which individual product decisions are made. A product strategy, in this framing, specifies (1) the insight about what is true in the market or about the customer that most other organizations have not fully internalized; (2) the strategic bets the product is making based on that insight; and (3) the actions the product team will take, with what resources, in what sequence, to validate and compound those bets.

Amazon Web Services provides an instructive case study of how a genuine product strategy can be articulated and sustained over time. AWS’s product strategy was grounded in an insight—that the infrastructure required to build scalable internet services was prohibitively costly and complex for most organizations to build independently—and a strategic bet: that if Amazon made its own internal infrastructure available as a service, the market would be large, the switching costs would be high, and the data and scale advantages that accumulate with early market leadership would be compounding. The specific product choices that followed—the sequence of service launches, the pricing model, the global infrastructure investment, the developer experience focus—were all expressions of that underlying strategic logic (FourWeekMBA, 2025). When new services were added to the AWS catalog, the strategic question was always whether they strengthened the platform’s ability to be the default infrastructure choice for organizations building on the internet—a product strategy question, not merely a market opportunity question.

Platform Strategy: From Product to Ecosystem, From Value Delivery to Value Orchestration

Platform strategy occupies a distinctive position in the layered architecture because it is not, strictly speaking, a separate level in the hierarchy—rather, it is a strategic evolution available to products that have achieved sufficient scale and market position to credibly pursue an ecosystem logic. A product that transitions to a platform is not simply adding a marketplace or an API; it is fundamentally reconceiving its role in the value chain from a direct value deliverer to a value orchestrator—a participant that creates the conditions for multiple other participants (developers, partners, customers, third-party service providers) to create and exchange value within a governed environment.

The structural characteristics of successful platform strategies have been well documented in the academic and practitioner literature. Network effects—the dynamic by which the value of the platform increases for each participant as the number of participants grows—are the defining economic logic of platform businesses, and they are the primary source of the compounding competitive advantage that platforms achieve relative to products (Bain & Company, 2025). The practical challenge of platform strategy is achieving the critical mass of participants necessary for network effects to become self-reinforcing, which typically requires a deliberate “cold start” strategy—often involving subsidizing one side of the platform to accelerate initial adoption, as Airbnb subsidized hosts, Apple subsidized developers, and Salesforce subsidized the AppExchange ecosystem during its formative period.

In the context of AI and agentic product development, platform strategy has acquired a new dimension of strategic importance. The emergence of agent orchestration platforms—systems that coordinate the actions of multiple AI agents working toward complex, multi-step goals—represents a new category of platform opportunity, one in which the platform creates value by enabling agents built by multiple participants to interact, delegate, and collaborate within a governed environment. Salesforce Agentforce, Microsoft Copilot Studio, and similar platforms are, in effect, pursuing a platform strategy in the agentic AI layer: building the orchestration infrastructure that enables third-party agent developers to create value within a platform ecosystem, thereby achieving the network effects and switching costs that platform businesses enjoy (Salesforce, 2025; Gocious, 2026).

For product leaders navigating the transition from product to platform, the critical strategic questions are: (1) is there a credible network effect available in the domain in which the product competes, and if so, what are the conditions under which it becomes self-reinforcing?; (2) what is the minimum viable ecosystem required to unlock the network effect, and how does the product reach that threshold?; and (3) what governance model will the platform use to balance the interests of ecosystem participants with the platform’s own competitive position? These questions are platform strategy questions, and they require a different analytical posture than product strategy questions—one that attends to the dynamics of ecosystems and multi-sided markets rather than the competitive dynamics of a single product in a single market.

Execution Strategy: Translating Strategic Choice into a Coherent Portfolio of Work

Execution strategy is the layer at which strategic intent is translated into a sequenced, resourced, and measurable portfolio of work. It is not, as is sometimes assumed, merely the roadmap—the execution strategy is the logical structure that determines how work is prioritized, sequenced, and resourced in a way that is consistent with and expressive of the product strategy and business strategy above it. The roadmap is an artifact of the execution strategy; the execution strategy is the reasoning that makes the roadmap coherent.

The distinction matters because execution strategies can be coherent or incoherent independent of whether the individual roadmap items are technically sound. An execution strategy that pursues too many strategic objectives simultaneously, distributes resources too thinly across initiatives, or sequences investments in a way that delays the compounding of the most strategically critical advantages is an incoherent execution strategy—even if every individual item on the roadmap is a sensible response to a genuine customer need. Concentration and sequencing are the defining characteristics of an execution strategy that succeeds in translating product strategy into competitive position.

In practice, execution strategy requires three analytical capabilities from product leaders. The first is the ability to identify the critical path—the sequence of investments that, if made in the right order and with sufficient concentration of resources, most rapidly advances the product toward its strategic objectives. The second is the ability to distinguish between strategic investments (those that build capabilities or position that compound over time) and tactical investments (those that solve immediate problems but do not structurally advance the product’s position). The third is the discipline to protect strategic investment capacity against the constant organizational pressure to reallocate resources toward tactical urgencies.

The interaction between these five layers—company, business, product, platform, and execution strategy—is not unidirectional. Strategy flows downward in the form of direction and constraint, but it also flows upward in the form of evidence, learning, and strategic opportunity surfaced through product discovery and execution. The organizations that navigate this multi-layer architecture most effectively are those that have built organizational practices for both the downward communication of strategic direction and the upward communication of strategic intelligence—creating a feedback system that allows the strategy at every layer to evolve in response to what is learned at the layers below.

Navigating the Layers: A Practitioner’s Compass

The practical implication of this layered architecture for senior product leaders is that strategic clarity requires layer clarity—the ability to diagnose at which level a given strategic question belongs, which layer has the authority and information to answer it, and how the answer at that layer constrains and enables decisions at adjacent layers.

Product leaders who attempt to resolve company strategy questions at the product strategy level—deciding, for example, that the product should enter an entirely new market without a company-level rationale for why that market fits the organizational portfolio—will generate misalignment, resource contention, and strategic confusion. Conversely, product leaders who delegate product strategy questions upward to the company level—waiting for company leadership to specify the product’s competitive positioning rather than developing and advocating for a strategic perspective grounded in deep market and customer understanding—abdicate the analytical responsibility that the product strategy layer properly belongs to.

The age of AI has added a new dimension of complexity to this navigational challenge. The structural changes that AI capabilities enable—and the competitive threats they pose—are relevant at every layer of the strategy architecture simultaneously. Company strategy must decide how AI fits into the organizational portfolio logic; business strategy must decide how AI changes the competitive dynamics of the arena; product strategy must decide how AI strengthens the product’s position in its chosen market; platform strategy must decide how AI enables or requires ecosystem evolution; and execution strategy must decide how AI investments are sequenced relative to other strategic priorities. Product leaders who can navigate these questions at each layer, and who can communicate the layer-specific implications of AI to the relevant organizational stakeholders, are the ones who will be most effective in positioning their products for the decade ahead.

References

Andrews, K. R. (1971). The concept of corporate strategy. Irwin.

Bain & Company. (2025). Platform strategy: A guide to platform business models. https://www.bain.com/insights/solution-spotlight/platform-strategy/

FourWeekMBA. (2025). Amazon AWS platform business model in a nutshell. https://fourweekmba.com/amazon-aws-platform-business-model/

Gocious. (2026). AI in product management guide for 2026 for product leaders. https://gocious.com/blog/ai-in-product-management-guide-for-2026-for-product-leaders

JetSoftPro. (2025). Platform thinking: How products evolve into scalable ecosystems. https://jetsoftpro.com/blog/platform-thinking-ecosystem-strategy/

LaunchNotes. (2024). Platform product strategy: Definition, examples, and applications. https://www.launchnotes.com/glossary/platform-product-strategy-in-product-management-and-operations

Lafley, A. G., & Martin, R. L. (2013). Playing to win: How strategy really works. Harvard Business Review Press.

Medium. (2025). Apple’s ecosystem mastery: How integrated product management built a $3 trillion tech empire. https://medium.com/@productbrief/apples-ecosystem-mastery-how-integrated-product-management-built-a-3-trillion-tech-empire-d49d17d02903

Porter, M. E. (1980). Competitive strategy: Techniques for analyzing industries and competitors. Free Press.

Presta. (2026). AI product strategy 2026: The founder’s guide to AI-native growth. https://wearepresta.com/ai-product-strategy-2026-the-founders-guide-to-ai-native-growth/

Reforge. (2024). The product strategy stack. Reforge Blog. https://www.reforge.com/blog/the-product-strategy-stack

Rumelt, R. P. (2011). Good strategy bad strategy: The difference and why it matters. Crown Business.

Salesforce. (2025). Form 8-K: Investor day press release. U.S. Securities and Exchange Commission. https://www.sec.gov/Archives/edgar/data/0001108524/000110852425000168/ex991-investordaypressrele.htm

Tidemark. (2025). Building a platform ecosystem: Tidemark’s guide to scalable SaaS strategies. https://www.tidemarkcap.com/post/what-does-it-mean-to-be-a-platform-ecosystem-company

Extant research on product and organizational strategy suggests that failure is not primarily a function of poor execution, insufficient resources, or bad market timing, though each of these can be contributing factors. Rather, the preponderance of product strategy failures traces to a cluster of structural and organizational pathologies that are, in principle, avoidable and, in practice, pervasive (Rumelt, 2011; Cagan, 2023). Five of these pathologies are particularly consequential: the feature factory mode of operation, the domination of roadmaps by stakeholder influence rather than strategic logic, the local optimization trap, the failure to achieve or sustain differentiation, and the underappreciated phenomenon of strategy debt—the accumulated cost of strategic decisions deferred, avoided, or made by default.

The Feature Factory: When Output Becomes the Objective

The term “feature factory,” coined by product practitioner John Cutler and subsequently elaborated in both academic and practitioner literature, describes an organizational mode in which the primary measure of product team performance is the rate at which features are built and shipped, rather than the degree to which those features advance measurable outcomes for customers or the business (Cutler, as cited in ProductPlan, 2024). The feature factory is not a caricature of dysfunction; it is a recognizable organizational equilibrium that emerges from the interaction of well-intentioned management practices, measurement systems, and stakeholder expectations.

In the feature factory mode, the planning cadence is organized around delivery commitments rather than problem-solving cycles. Teams are evaluated on whether they shipped what they said they would ship, not on whether what they shipped produced the intended effect. Product managers become, in practice, delivery managers—skilled at translating requests into specifications, managing dependencies, and protecting sprint capacity, but not authorized or equipped to question whether the work being executed is the right work. Cagan (2023) argues that this is the dominant operational mode of the majority of product organizations globally, and that it is fundamentally incompatible with genuine product strategy, owing to the structural conflict between the feature factory’s output orientation and the strategic posture of solving for outcomes.

The organizational data supports the characterization. ProductPlan’s State of Product Management Report (2023) observed that 54% of product roadmaps are structured around outputs—feature completions, release milestones, and capability launches—rather than outcomes. Companies exhibiting this pattern launched, on average, 41% more features than their strategically aligned counterparts while producing 23% less measurable impact on key metrics (ProductPlan, 2024). The paradox is structurally explicable: more features does not mean more value if those features are not selected on the basis of a strategic logic that connects them to a coherent competitive position.

The feature factory problem is compounded in the context of AI-native and agentic product development, where the technical ease of adding AI-powered features—summaries, recommendations, generative content, intelligent search—has created a new variant of the pattern. Organizations that add AI capabilities feature by feature, without a governing strategic logic for how AI strengthens the product’s competitive position, are practicing feature factory development with a more sophisticated technical vocabulary. The outcome is the same: capability accumulation without strategic coherence.

The antidote is not slower delivery; it is the discipline of outcome framing. Teams that begin every planning conversation with the question “what measurable outcome are we trying to move, for which customer, and why does this initiative move it?” are practicing a fundamentally different mode of product development than teams that begin with a feature list. This shift—from output thinking to outcome thinking—is not primarily a process change; it is a cultural and organizational change that requires leadership authorization, measurement system realignment, and a sustained willingness to accept the discomfort of uncertainty during discovery cycles.

Stakeholder-Driven Roadmaps: The Aggregation of Preferences is Not a Strategy

Perhaps the most organizationally embedded pathology in product strategy is the construction of roadmaps through stakeholder aggregation rather than strategic logic. In this pattern, the product roadmap is assembled by collecting requests, priorities, and commitments from sales, customer success, marketing, executive leadership, and key customers, and then organizing them into a sequence that satisfies the most influential voices. The resulting document is presented in the planning cycle as a strategy—and is often internally experienced as one, because it represents a settled consensus among powerful organizational actors.

The structural problem with this approach is not that stakeholder input is invalid—customer insight and sales intelligence are legitimate inputs to strategic thinking—but that the aggregation of preferences does not, in itself, constitute a strategic choice. A roadmap that attempts to satisfy all stakeholder demands simultaneously is, by construction, a roadmap that has declined to make the hard choices that strategy requires. Every item on such a roadmap can be individually justified, and the collective result is an unfocused, internally inconsistent investment portfolio that serves no strategic logic.

Rumelt’s (2011) characterization of “bad strategy” is directly applicable here. The hallmark of bad strategy that Rumelt identifies most frequently in organizational practice is the substitution of goals for strategy—the articulation of aspirations and targets without the logical structure that connects them to a diagnosis of the central challenge and a coherent set of choices about how to address it. A roadmap constructed from stakeholder requests is, in Rumelt’s terms, a list of goals masquerading as a strategy. It tells the organization what it intends to do; it does not tell the organization why these are the right things to do, in this sequence, for this competitive position.

The organizational mechanics that produce stakeholder-driven roadmaps are well understood. In many product organizations, the ability to influence the roadmap is treated as a measure of stakeholder importance, creating a political incentive for sales leaders to argue for customer-requested features, customer success to argue for retention-focused improvements, and marketing to argue for capabilities that support go-to-market narratives. Product leaders who lack the organizational authority or strategic confidence to push back on these pressures default to a prioritization process that is, in effect, a negotiation rather than a strategy exercise.

The case of Microsoft Zune illustrates the downstream consequences of this pattern at the product level. Zune’s roadmap was shaped substantially by the competitive imperative to match iPod features—a classic instance of stakeholder (and competitive) pressure overriding strategic logic. The result was a product that was competitively adequate on features but strategically incoherent: it entered a market where Apple had already achieved deep switching costs through iTunes ecosystem lock-in, with a product that matched the incumbent’s capabilities without offering a structurally differentiated position. The strategic question—”where can we win in digital music, given that Apple owns the current arena?”—was never adequately answered, because the roadmap process was oriented toward competitive parity rather than strategic positioning (DigitalDefynd, 2026).

Local Optimization: The Strategic Cost of Solving the Wrong Problem Well

Local optimization describes the organizational pathology in which teams, divisions, or product lines make choices that are rational at the local level but collectively undermine the strategic coherence of the broader product or organization. It is, in some sense, the strategic equivalent of suboptimization in systems thinking: the parts of the system are individually efficient, but the interactions between them produce a collective outcome that is inferior to what a system-level view would prescribe.

In product organizations, local optimization manifests in several characteristic forms. The first is the prioritization of near-term retention metrics over long-term positioning investments—a pattern in which teams optimize for the metrics they are measured on, which tend to be short-cycle engagement and retention indicators, at the cost of the structural investments that would strengthen the product’s competitive position over longer time horizons. The second is the tendency to solve customer problems at the feature level rather than the architectural level—adding features that address immediate pain points without addressing the underlying systemic causes, thereby accumulating product complexity that constrains future strategic options.

The third and perhaps most consequential form of local optimization is the tendency to scale before achieving product-market fit. MIT Sloan research identified this pattern—switching to growth mode before the core strategic value proposition has been validated—as responsible for a substantial proportion of startup failures, with one systematic analysis attributing approximately 70% of startup failures to premature scaling (Bain & Company, 2025; Product Art, 2024). In enterprise product contexts, the equivalent pattern is the tendency to build organizational scale—hiring, tooling, process complexity—around a product strategy that has not yet been validated as coherent, thereby increasing the organizational cost of the strategic pivot when it becomes necessary.

In the age of agentic AI products, local optimization has acquired a new expression. Product teams that build AI agents optimized for a narrow task—say, email drafting, or meeting summarization—without considering how those agents interact with the broader workflow, data architecture, and user mental model are engaging in local optimization at the product level. The result tends to be a proliferation of task-level AI tools that collectively impose cognitive overhead on users, who must now manage multiple AI assistants with inconsistent interfaces and non-integrated outputs, rather than a coherent AI-augmented workflow (AI Product Management Guide, 2026). Salesforce’s Agentforce architecture represents, in part, a strategic response to this dynamic: rather than building point AI tools, Salesforce built an agent orchestration platform that coordinates AI actions within a unified data and workflow environment, thereby solving the integration problem that local optimization produces (Salesforce, 2025).

Lack of Differentiation: The Convergence Trap and the Erosion of Strategic Position

Differentiation is not merely a marketing concept; it is a structural condition for the sustainability of any product strategy. A product that is not differentiated—that does not offer a set of capabilities or a user experience that is meaningfully superior to available alternatives in the arena it has chosen to compete in—is not strategically positioned; it is merely present in a market. The absence of differentiation does not prevent products from being used; it prevents them from building the kind of customer dependency and switching costs that translate into durable competitive position.

Extant research on competitive strategy, synthesized and applied to product management contexts, suggests that differentiation must be grounded in at least one of three structural sources: (1) a unique capability or user experience that competitors cannot easily replicate without significant investment or structural change, (2) proprietary data or network effects that compound the product’s value as usage grows, or (3) deep integration into customer workflows or systems that creates high switching costs (Bain & Company, 2025; Reforge, 2024). Products that rely primarily on feature richness as their differentiation mechanism are particularly vulnerable, owing to the relative ease with which features can be replicated by well-resourced competitors.

The convergence trap describes the dynamic in which competitors in a given product category progressively converge on the same feature sets, user experience patterns, and positioning language, thereby neutralizing any feature-level differentiation any individual product might achieve. This is structurally predictable in mature product categories: as the competitive set matures, the cost of not having a given feature set increases, driving all competitors to implement similar capabilities, and the differentiating value of any individual feature decays to zero.

In the B2B SaaS context, the convergence trap has been particularly pronounced in categories such as project management, CRM, and collaboration tooling—areas where the core feature sets are now largely commoditized and differentiation, to the extent it exists, is increasingly a function of integration breadth, data platform capabilities, and AI-powered workflow automation rather than core feature superiority. Product organizations that have built their strategies around feature differentiation in these categories are discovering, somewhat belatedly, that the strategic terrain has shifted, and that the next arena of competition is at the platform and data layer rather than the feature layer.

Strategy Debt: The Hidden Cost of Decisions Deferred

Strategy debt is the least discussed and, in the author’s observation, the most insidious of the five pathologies examined here. The concept borrows its structural logic from technical debt—the accumulated cost of shortcuts, compromises, and deferred investments in code architecture that, over time, reduce a system’s capacity to evolve—and applies it to the domain of strategic choices. Strategy debt accumulates when organizations defer difficult strategic choices, make strategic commitments by default rather than by deliberate design, or allow the strategic logic of a product to decay without renewal while continuing to invest in its delivery.

Strategy debt manifests in several characteristic forms. The first is scope creep at the strategic level: the progressive accumulation of adjacent use cases, customer segments, and feature domains that were added opportunistically—in response to enterprise customer requests, competitive threats, or internal advocacy—without being subjected to the strategic filter of “does this choice strengthen our position in the arena we have chosen to compete in, or does it dilute it?” Products that have undergone several cycles of this pattern tend to exhibit what Intercom’s Des Traynor called “product sprawl”—the tendency to attempt to serve too many use cases for too many customer types, ultimately serving none particularly well (as cited in ProductPlan, 2024).

The second form of strategy debt is the accumulation of strategic commitments made by default—the gradual hardening of implicit choices into structural dependencies that constrain future strategic options without ever having been explicitly made. An organization that has built its pricing model, partner ecosystem, and product architecture around a particular customer segment it never explicitly chose—but into which it happened to acquire early traction—has accumulated strategy debt in the form of structural dependencies on that segment that make strategic repositioning costly and organizationally disruptive.

The third form, and perhaps the most directly consequential in the AI era, is the debt that accumulates when a product’s strategic logic is built on a competitive advantage that is eroding. A product strategy that was coherent when it was formulated—because it was grounded in a genuine structural advantage—can become strategically indebted if the conditions that supported that advantage change and the strategy is not updated accordingly. In the context of AI products, organizations that built competitive positions on foundation model access, prompt engineering expertise, or AI-powered features available through standard APIs discovered this form of strategy debt acutely as those advantages commoditized between 2023 and 2025 (Presta, 2026).

Addressing strategy debt requires the same kind of deliberate organizational investment as addressing technical debt: the recognition that the cost of continued deferral exceeds the cost of remediation, the allocation of dedicated strategic renewal capacity, and the willingness to accept short-term disruption to restore long-term strategic coherence. Organizations that treat strategy as a quarterly document rather than a living system are, in effect, allowing strategy debt to compound invisibly—until the structural consequences become visible in the form of declining differentiation, customer confusion, and competitive vulnerability.

Toward Strategic Hygiene: A Practitioner Agenda

The five pathologies examined here—feature factory operations, stakeholder-driven roadmaps, local optimization, differentiation failure, and strategy debt—are not independent; they are mutually reinforcing. Organizations that operate in feature factory mode tend to produce stakeholder-driven roadmaps, which tend toward local optimization at the expense of differentiated positioning, which tends to accumulate strategy debt over time. Addressing any one of these pathologies in isolation produces limited and often temporary improvement; sustained strategic health requires addressing the systemic interactions between them.

For product leaders, the practical implication is that product strategy requires a distinct organizational practice with its own cadence, tools, and leadership authorization—separate from, though connected to, the delivery and planning practices that govern roadmap execution. This practice involves, at minimum, a regular strategic review cycle that asks not “what did we build?” but “what are we winning at, and what choices are we making that compound our position?”; a measurement system that tracks leading indicators of strategic health—customer dependency, competitive differentiation, ecosystem depth—rather than only delivery velocity; and a decision-making framework that explicitly distinguishes between strategic choices (about where to play and how to win) and tactical choices (about what to build next).

Product organizations that develop this practice will not avoid all strategic failures. Strategy is irreducibly a bet made under conditions of uncertainty, and the quality of the bet can only be known in retrospect. But organizations that practice genuine strategic discipline will make better bets, recognize their failures earlier, and adapt their positions more effectively—thereby building the kind of strategic resilience that is the ultimate competitive advantage in an era of rapid technological and market change.

References

AI Product Management Guide. (2026). The AI product manager: GenAI, agents & automation guide 2026. Product Leaders Day India. https://productleadersdayindia.org/blogs/ai-product-management-guide/ai-product-management-guide.html

Bain & Company. (2025). Platform strategy: A guide to platform business models. https://www.bain.com/insights/solution-spotlight/platform-strategy/

Cagan, M. (2023). Transformed: Moving to the product operating model. Wiley.

DigitalDefynd. (2026). 20 product management failure examples. https://digitaldefynd.com/IQ/product-management-failure-examples/

Martin, R. L. (2024). Will artificial intelligence eradicate practitioners of strategy? Medium. https://rogermartin.medium.com/will-artificial-intelligence-eradicate-practitioners-of-strategy-dead2f716e8d

Presta. (2026). AI product strategy 2026: The founder’s guide to AI-native growth. https://wearepresta.com/ai-product-strategy-2026-the-founders-guide-to-ai-native-growth/

Product Art. (2024). Why product roadmaps are destroying strategic thinking. Substack.

https://productart.substack.com/p/why-product-roadmaps-are-destroying

ProductPlan. (2024). The challenge of the feature factory. https://www.productplan.com/feature-factory-challenges/

Reforge. (2024). The product strategy stack. Reforge Blog. https://www.reforge.com/blog/the-product-strategy-stack

Rumelt, R. P. (2011). Good strategy bad strategy: The difference and why it matters. Crown Business.

Salesforce. (2025). Form 8-K: Investor day press release. U.S. Securities and Exchange Commission. https://www.sec.gov/Archives/edgar/data/0001108524/000110852425000168/ex991-investordaypressrele.htm

The confusion is not accidental. It emerges from a conflation of three distinct constructs—vision, strategy, and roadmap—that are structurally related but functionally non-interchangeable. Extant research and practitioner literature have noted this conflation as one of the most consequential sources of misalignment in product organizations (Cagan, 2017; Martin & Lafley, 2013). Addressing this gap requires more than definitional precision; it requires a structural understanding of how these constructs relate to one another, why organizations systematically collapse them, and what a genuine product strategy—as opposed to an elaborated backlog—actually consists of.

The Architecture of Direction: Vision, Strategy, and Roadmap as Distinct Instruments

The most durable way to understand the relationship between vision, strategy, and roadmap is to recognize that they operate at different temporal and epistemic registers. Vision answers the question of what the world looks like when the product has succeeded—it is a future state, deliberately aspirational, often spanning three to five years. Strategy answers the question of how the product will get there—it is a set of deliberate choices about where to compete and how to win in that chosen arena. Roadmap answers the question of what the team will do next—it is the operationalization of strategic choices into sequenced initiatives and investments.

The distinction matters because each instrument requires a different kind of thinking. Vision requires imagination and narrative coherence; it must be compelling enough to orient organizational effort over long time horizons and persuasive enough to align stakeholders who may not yet share the same mental model of the future. Strategy requires analytical rigor and, crucially, the willingness to make bets—to commit to certain arenas and choices while explicitly de-prioritizing others. Roadmap requires execution intelligence—the capacity to translate strategic direction into prioritized, testable, and deliverable work.

When these three constructs are collapsed into a single artifact—as frequently happens when roadmaps masquerade as strategy—the organization loses the ability to think at each level independently. A roadmap without a strategy is simply a list of intentions. A vision without a strategy is inspiration without a path. And a strategy without a vision is optimization without a destination.

Spotify offers an instructive illustration of how these layers can function in genuine coherence. Spotify’s product vision, articulated in its early years, was to be the place where people discover and experience music—not merely to stream it. Its strategy involved explicit choices: to play in the music streaming category rather than podcasting, video, or general media (initially), to win through curation, personalization, and artist relationships rather than exclusively on catalog breadth, and to build its competitive position on behavioral data and recommendation algorithms that competitors without comparable listening history could not easily replicate. The roadmap that followed—investments in Discover Weekly, Wrapped, the podcast expansion, the Loudr and Anchor acquisitions—was legible only in the context of that strategy. Each initiative was a coherent strategic move, not a feature request that happened to get resourced (Spotify Technology S.A., 2025). The roadmap did not constitute the strategy; it expressed it.

Contrast this with the trajectory of many enterprise software products, where roadmaps are negotiated artifacts that reflect the aggregate influence of sales, customer success, and executive preferences rather than strategic choices. In such organizations, the “strategy” is implicitly whatever the roadmap prioritizes—a tautology that forecloses genuine strategic thinking before it can begin.

Why Teams Confuse Delivery with Strategy: The Organizational Mechanics of Drift

Understanding why this confusion persists requires examining the incentive structures and organizational mechanics that reward the appearance of strategy over its substance. Several converging forces are at work.

The first is the measurement problem. Delivery is measurable in ways that strategy is not. Velocity, story points, feature counts, and deployment frequency are legible, trackable, and reportable upward. Strategic progress—the degree to which a product is building a defensible position, deepening customer dependency, or moving toward a distinct competitive advantage—is harder to instrument and slower to manifest. In organizations that have optimized their performance management systems around delivery metrics, the incentive to conflate delivery with strategy is structurally embedded rather than individually chosen.

The second is what Cagan (2023) identifies as the feature team problem: the organizational mode in which product teams function as internal delivery contractors for a backlog defined largely by stakeholders, rather than as empowered problem-solvers authorized to discover and pursue the best solution to a defined outcome. Feature teams can be extraordinarily productive in delivery terms while making no strategic progress whatsoever—indeed, they can actively consume strategic optionality by building technical and product complexity that constrains future choices.

The third force is the compression of planning cycles. As organizations have adopted agile and lean methodologies, the emphasis on shorter feedback loops and iterative delivery has, in many cases, crowded out the slower, more deliberate work of strategic thinking. Quarterly planning cycles that begin with a roadmap rather than a strategy review are a symptomatic artifact of this compression. The organization becomes so practiced at the rhythm of delivery that stepping back to ask whether the collective delivery effort is moving toward a strategically coherent destination begins to feel like an interruption rather than a precondition.

In the context of AI-native and agentic product development, this conflation has become even more consequential. The availability of powerful foundation models has made it technically straightforward to add AI capabilities to virtually any product—and this technical ease has generated an epidemic of AI feature additions that lack any strategic logic. Organizations that add AI summarization, AI-powered search, or AI-generated content to their products without first answering why these capabilities strengthen their strategic position and deepen their competitive moat are, in effect, decorating a strategically underdetermined product with impressive-sounding technology. Extant research and practitioner commentary suggest that AI capabilities divorced from strategic intent tend to produce capability parity rather than differentiation, owing to the commoditization of foundation model access across the industry (Martin, 2024; Presta, 2026).

The “Where to Play / How to Win” Lens: A Framework Whose Time Has Come Again

Among the analytical frameworks that product leaders have found enduringly useful, Lafley and Martin’s (2013) Strategic Choice Cascade—and its central emphasis on the interdependence of “Where to Play” and “How to Win” as the heart of strategy—remains one of the most rigorous. Its application to product strategy, however, requires some translation.

In Lafley and Martin’s formulation, Where to Play refers to the set of deliberate choices about the competitive arena in which an organization will seek to win—encompassing customer segments, geographies, product categories, channels, and value chain positions. How to Win refers to the value proposition and capabilities that enable the organization to achieve a superior, defensible position within that chosen arena. The critical structural insight is that these two choices are not independent: the choice of where to play constrains and shapes what it means to win there, and the honest assessment of how one can win should in turn shape where one chooses to play.

Applied to product strategy, this framework asks product leaders to confront two questions that are deceptively simple but organizationally difficult. First: which customer segments, use cases, market positions, or problem domains does the product explicitly choose to pursue—and, by implication, which does it choose not to pursue? Second: within that chosen arena, what does the product do distinctly well, and why does that create durable value for the chosen customer in a way that competitors cannot easily replicate?

The deliberate answer to the second question is what distinguishes a genuine How to Win from a list of features or capabilities. Amazon Web Services (AWS) did not win in cloud infrastructure by offering a richer feature set than competitors—it won by combining a scale-driven cost structure, an unmatched breadth of services, and a developer-centric culture of rapid iteration that allowed it to compound its position over time. The How to Win was structural and compounding, not merely functional and replicable (Bain & Company, 2025). The product roadmap that followed—continuous service expansion, global infrastructure investment, the developer toolchain ecosystem—was the expression of a strategic logic, not the source of it.

Rumelt’s (2011) complementary concept of the strategy kernel adds further precision to this structural analysis. Rumelt argues that a good strategy contains three interdependent elements: (1) a diagnosis of the central challenge or opportunity the organization faces, (2) a guiding policy that defines how to address that challenge, and (3) a set of coherent actions that collectively implement the guiding policy. What distinguishes a good strategy from a bad one, in Rumelt’s account, is not the ambition of the vision or the sophistication of the roadmap—it is the coherence and logical integrity of the kernel. Bad strategy, by contrast, is characterized by fluff (vague, buzzword-laden language masquerading as direction), failure to diagnose the actual challenge, mistaking goals for strategy, and setting objectives that are incoherent or internally contradictory.

The practical implication for product leaders is that the diagnostic step—the honest characterization of the central challenge—is the most important and most frequently skipped element of the strategic process. Organizations that jump from vision to roadmap without the intermediate work of honest diagnosis produce what might be called aspirational roadmaps: documents that describe what the organization wishes were true rather than what choices need to be made given the actual competitive and organizational reality.

Strong Strategy, Weak Strategy: A Comparative Anatomy

The distinction between strong and weak product strategy is most legible in concrete organizational examples, where the structural differences become visible rather than merely definitional.

Strong strategy: Netflix’s streaming pivot and original content bet. Netflix’s transition from DVD rental to streaming in 2007 and its subsequent investment in original content beginning in 2013 represent a textbook illustration of Where to Play and How to Win applied in sequence. The Where to Play choice—streaming video, globally, delivered directly to consumers—was made before the competitive dynamics of the streaming market had fully crystallized, and it required deliberate de-investment in the DVD business that was, at the time, still profitable. The How to Win choice—to compete on content breadth, algorithmic personalization, and progressively on original content that could not be replicated by other streaming services—was a coherent strategic response to the structural dynamics of the market, where content was the primary switching cost and catalog was the primary differentiator. The result was a product strategy that was not merely ambitious but structurally sound: each strategic choice reinforced the others, and the roadmap of investments that followed was internally coherent (ResearchGate, 2024).

Weak strategy: Google Wave and the problem of absent diagnosis. Google Wave, launched in 2009, is an instructive counterexample. The product represented a substantial technical investment and a genuinely innovative collaboration platform—yet it failed not because of poor execution but because of the absence of a clear diagnosis of the problem it was solving. The product attempted to address too many use cases for too many customer types simultaneously—email replacement, document collaboration, instant messaging, and social networking—without a coherent answer to either Where to Play (which segment was the primary customer?) or How to Win (why was this the superior solution for that segment?). The product sprawl that resulted was a direct consequence of strategic underdetermination, not execution failure (ProductPlan, 2024).

Weak strategy in the AI era: the LLM wrapper problem. The 2023–2025 period generated a particularly illustrative instance of weak strategy at scale: the proliferation of AI products that were, in substance, thin layers of prompt engineering over publicly available foundation models. Absent a clear Where to Play choice and a differentiated How to Win, these products competed on the capabilities of underlying models rather than on any structural advantage of their own. As foundation model capabilities commoditized and access became widely available through standard APIs, the strategic hollowness of this positioning became structurally inevitable. The organizations that built enduring positions in the AI era were those that made explicit choices about which customer segment and use case they were serving, and built proprietary data assets, workflow integrations, and switching costs that compounded over time (Presta, 2026).

Strong strategy in the AI era: Salesforce Agentforce. Salesforce’s Agentforce platform illustrates what strong strategy in the age of agentic AI looks like. Rather than adding AI capabilities as a product feature, Salesforce made an explicit strategic choice to evolve its platform from a system of record and system of engagement to a system of action—where AI agents execute end-to-end workflows within the Salesforce data environment. The How to Win was grounded in a structural advantage that competitors without Salesforce’s installed base and data depth could not easily replicate: proprietary customer data accumulated over decades within CRM, Service Cloud, and Marketing Cloud, which could be used to ground agent behavior in ways that generic AI tools could not. Agentforce became Salesforce’s fastest-growing organic product, and the strategic logic—playing in enterprise customer workflows and winning through proprietary data and platform lock-in—was coherent and defensible (Salesforce, 2025).

Strategy as a Living System: The Continuous Work of Strategic Renewal

The final and perhaps most consequential reframing for senior product leaders concerns the temporal nature of strategy. There is a persistent organizational tendency to treat strategy as a document—something produced at the beginning of a planning cycle, reviewed at the next, and in the interim treated as a constraint rather than a guide. This tendency is compounded in organizations that have adopted agile delivery practices without equivalent investment in agile strategic renewal.

Extant research in organizational strategy suggests that the most effective product strategies are treated as living systems—continuously updated in response to new market intelligence, competitive moves, and evidence from the product itself, while maintaining structural coherence in the core choices of Where to Play and How to Win (Reforge, 2024). The distinction is between strategic rigidity (refusing to update choices in the face of evidence) and strategic drift (abandoning choices at the first sign of difficulty without distinguishing between evidence of a wrong choice and evidence of a hard one).

In the context of AI and LLM-powered products, the pace at which the competitive landscape shifts—new foundation model capabilities, new entrants, new customer expectations—suggests that the renewal cadence for product strategy should be more frequent than in pre-AI product contexts, without sacrificing the structural coherence that distinguishes strategy from reactive feature development. Product leaders who conflate responsiveness with strategic drift will find themselves building products that are perpetually catching up to the market rather than defining it.

The study of product strategy, at its core, is the study of deliberate choice under conditions of uncertainty and competitive pressure. What product strategy actually means—as distinct from roadmap, backlog, or vision—is a coherent set of decisions about where to compete and why the product can win there, grounded in an honest diagnosis of the organizational and market reality, and expressed through a set of reinforcing actions that compound the product’s position over time. Organizations that achieve this clarity do not merely build better products. They build products that matter—that are not easily replaced, not easily replicated, and not easily forgotten by the customers they choose to serve.

References

Cagan, M. (2017). Inspired: How to create tech products customers love (2nd ed.). Wiley.

Cagan, M. (2023). Transformed: Moving to the product operating model. Wiley.

Lafley, A. G., & Martin, R. L. (2013). Playing to win: How strategy really works. Harvard Business Review Press.

Martin, R. L. (2024). Strategy and artificial intelligence. Medium. https://rogermartin.medium.com/strategy-artificial-intelligence-6f719015b8fc

Murphy, A. (2024). A product strategy is not a vision and roadmap. Ant Murphy Newsletter. https://www.antmurphy.me/newsletter/a-product-strategy-is-not-a-vision-and-roadmap

Presta. (2026). AI product strategy 2026: The founder’s guide to AI-native growth. https://wearepresta.com/ai-product-strategy-2026-the-founders-guide-to-ai-native-growth/

Reforge. (2024). The product strategy stack. Reforge Blog. https://www.reforge.com/blog/the-product-strategy-stack

ResearchGate. (2024). Strategy for growth and market leadership: The Netflix case. https://www.researchgate.net/publication/374545358_Strategy_for_Growth_and_Market_Leadership_The_Netflix_Case

Rumelt, R. P. (2011). Good strategy bad strategy: The difference and why it matters. Crown Business.

Salesforce. (2025). Form 8-K: Investor day press release. U.S. Securities and Exchange Commission. https://www.sec.gov/Archives/edgar/data/0001108524/000110852425000168/ex991-investordaypressrele.htm

Spotify Technology S.A. (2025). Form 6-K, FY2025. U.S. Securities and Exchange Commission. https://www.sec.gov/Archives/edgar/data/0001639920/000114036125002936/ef20042791_ex99-1.htm

ProductPlan. (2024). The challenge of the feature factory. https://www.productplan.com/feature-factory-challenges/