Blue Ocean Strategy: Value Innovation Reframed for the AI Era
Red Oceans Get Redder Faster—and the Strategy Canvas Quietly Encourages Exactly the Wrong Move
This is one of RoadmapOne ’s articles on Strategy for Product Leaders .
Blue Ocean Strategy, by W. Chan Kim and Renée Mauborgne, is a framework for creating uncontested market space rather than competing in feature-crowded markets. Its core tools are value innovation, the strategy canvas (which plots competitive factors against offering level), and the Four Actions Framework / ERRC grid (Eliminate, Reduce, Raise, Create). In 2026, the framework’s intuition holds but the feature-based canvas misleads: durable blue oceans now come from segment, channel, and workflow choices rather than feature differentiation.
Blue Ocean Strategy, published by W. Chan Kim and Renée Mauborgne in 2005, is one of the most widely-read strategy books of the last twenty years. Its central idea—that the best way to win is to create uncontested market space rather than fight for share in bloody, feature-competing “red oceans”—has reshaped a generation of product strategy conversations. The framework gave strategists vocabulary (value innovation, strategy canvas, four actions framework), case studies (Cirque du Soleil, [yellow tail] wine, the Nintendo Wii), and a methodology that felt creative rather than defensive.
It was a genuinely important book. It is also increasingly unsafe to follow the strategy canvas literally, for a reason the authors could not have anticipated: the primary tool they gave strategists—a chart that plots product attributes along a horizontal axis of feature intensity—almost perfectly encourages the thing that no longer works, which is winning through feature differentiation. In 2005, that was defensible. A feature advantage could hold for two or three years while competitors reverse-engineered and caught up. In 2026, a feature advantage holds for weeks. Your red-ocean competitor can clone your “raised” and “created” features with AI tooling faster than your sales team can explain them. The strategy canvas, used as intended, guides teams toward exactly the wrong move.
This article takes the framework seriously—and then argues that product leaders in 2026 need to read it through a significantly different lens than the one the book provides. The shape of the canvas is still useful. The idea of value innovation is still valid. But the feature axis is a trap, and the real blue oceans today aren’t drawn by eliminating or raising product attributes. They’re drawn by channel, segment, and workflow choices—the dimensions AI cannot commoditise.
TL;DR: Blue Ocean Strategy’s core intuition—create uncontested market space rather than fight in feature-crowded markets—is as valid as ever. The problem is the tool. The strategy canvas plots features on a horizontal axis, which invites teams to draw their blue ocean as a differentiated feature set. In 2026, that’s the exact wrong move. Anyone can clone your feature set in weeks with AI. The real blue oceans today are about channel (who you reach and how), segment (who you serve and how specifically), and workflow (what you integrate into), not features. A bad salesperson always asks for more features; a good salesperson sells what they have. A bad product strategist draws a differentiated feature canvas; a good one finds the segment the incumbents won’t serve and the channel the incumbents can’t access.
What Is Blue Ocean Strategy?
Blue Ocean Strategy distinguishes two kinds of market space:
- Red oceans — existing industries where competitors fight for known demand by differentiating features, prices, and brands. Competition is bloody (hence “red”), margins compress, and innovation degenerates into an arms race along a set of widely-agreed dimensions.
- Blue oceans — uncontested market space, often created by combining attributes in a new way that makes the conventional red-ocean competition irrelevant. The blue-ocean competitor doesn’t try to out-feature incumbents; it changes the game so the incumbents’ features stop mattering.
The book’s central strategic tool is the strategy canvas, a two-dimensional chart that plots industry competitive factors (features, attributes, services) along a horizontal axis against offering level on the vertical axis. You draw your own offering, then draw the competitors’, then draw a new offering that visibly departs from the industry curve—typically by eliminating or reducing some attributes while raising or creating others. The Four Actions Framework (Eliminate / Reduce / Raise / Create — known as ERRC) is the mechanism for generating that new offering.
Kim and Mauborgne illustrate with Cirque du Soleil—a circus that eliminated star performers and animal acts (expensive, low-value in their analysis), reduced things like multiple arenas, raised the theatrical quality, and created refinement, artistic music, and story-driven shows. The result wasn’t a better circus and wasn’t a theatre production. It was uncontested space between them. Cirque du Soleil grew into a billion-dollar business without a direct competitor for years.
It’s a beautiful case. It’s also part of the trap, because the case is always presented as if the differentiated feature profile was what made Cirque du Soleil blue-ocean. Re-read it: the feature-level ERRC decisions followed from a deeper choice about the segment (adult audiences who’d otherwise go to theatre) and the channel (high-ticket urban theatre venues, not suburban circus tents). Cirque du Soleil didn’t find a blue ocean by drawing a better feature curve. It found a blue ocean by picking a segment and a channel nobody else was serving, then redesigning the feature set to fit. The feature canvas is the output, not the input.
The Four Actions Framework (ERRC)
The Four Actions are:
- Eliminate — which industry-standard attributes should be removed entirely?
- Reduce — which should be reduced below the industry standard?
- Raise — which should be raised above the industry standard?
- Create — which attributes, absent from the industry, should be created?
Applied well, ERRC produces a value curve that visibly departs from the industry norm—not a me-too-but-better product, but a genuinely different shape of offering. Applied badly, it produces a slightly-different feature list dressed up in the language of innovation. Most applications I’ve seen in product organisations are the latter. Teams enthusiastically “create” a feature their competitors don’t have, ship it, and watch the competitors copy it within a quarter. The feature doesn’t create a blue ocean. It rearranges a red one.
Why the Strategy Canvas Encourages the Wrong Move
Here is the awkward truth about the strategy canvas: its horizontal axis is a feature list. It was designed that way deliberately. The authors saw products as bundles of attributes, and innovation as reshaping the attribute bundle. In a world where attributes took years to copy, that produced genuinely durable differentiation. In a world where attributes take weeks to copy, it does not.
This is the AI-era trap. A team sits down, draws the industry value curve (competitor attributes, industry-standard levels), draws their own curve (slightly elevated on a few attributes, slightly reduced on others), and spends six months building toward their canvas. They ship. And the competitor ships a matched version six weeks later. The blue ocean that existed at the moment of the canvas exercise doesn’t exist by the time the product reaches the market.
A bad salesperson always asks for more features; a good salesperson sells what they have. The same is true of strategists. A bad strategist draws a differentiated feature canvas and expects the canvas itself to produce the advantage. A good strategist uses the canvas as diagnostic—to see what the industry is fighting over—and then picks a blue ocean outside the attribute axis entirely. The winning blue ocean in 2026 is usually not a different feature curve. It is a different segment the incumbents don’t serve, a different channel they can’t access, or a different workflow they don’t integrate with. Features flow from the segment/channel/workflow choice; they do not make it.
What Red Oceans Look Like in the AI Era
Red oceans in 2026 look different from red oceans in 2005. The intensity of feature competition has not just persisted; it has accelerated. What used to take eighteen months for a competitor to copy now takes six weeks. What used to take six months now takes two. The “bloody” aspect of the red ocean has become one-sided: a new entrant with AI tooling can race along the feature curve faster than the incumbent can refresh their roadmap. This means:
- Feature-based moats are dead. Any differentiation based on the feature axis will be matched within a release cycle. Teams investing in feature parity or feature leadership are investing in a moat that evaporates on contact.
- Price-based moats are dead. When marginal build cost approaches zero for every competitor, price wars become possible from new entrants who have no sunk costs to defend. The incumbent’s margin structure cannot be saved by cutting price.
- The red ocean, paradoxically, is bigger. Categories that used to have three or four meaningful players now have ten or fifteen AI-native entrants, each of which can credibly claim feature parity within weeks of launch.
The implication for Blue Ocean Strategy is that the need for blue oceans is more acute than ever. The tool for finding them just needs updating.
Where the Real Blue Oceans Are in 2026
Blue oceans in 2026 come from three dimensions the AI wave cannot erode:
1. Segment
Pick a customer segment the incumbents won’t serve profitably. This is classic segment-focus strategy (see Porter’s Generic Strategies ) and it is arguably the most reliable source of blue-ocean opportunity in software today. Vertical SaaS—the Toast (restaurant) / Veeva (pharma) / Procore (construction) pattern—is blue ocean through segment specialisation. The incumbent horizontal tool (a generic CRM, a generic project-management system) cannot tailor deeply enough to each vertical to compete. The specialist wins not by having better features than the generalist but by having exactly the features a specific segment needs, built with deep understanding of that segment’s workflows and vocabulary. AI does not erode this advantage—the segment understanding is cumulative and hard to fake.
2. Channel
Pick a distribution channel the incumbents can’t or won’t access. This is the most under-appreciated blue-ocean strategy in software, and it’s the one the strategy canvas completely obscures because channel is not a feature. Shopify built its blue ocean not by having better e-commerce features than Amazon but by accessing a channel Amazon could not: long-tail independent retailers who didn’t want to be on Amazon’s terms. Substack’s blue ocean was a channel choice—direct newsletter subscriptions—not a feature choice. The product features followed from the channel. In 2026, channel blue oceans are where most new scale comes from: partnerships, embedded distribution, marketplace positioning, developer-community access, regulatory-gated verticals.
3. Workflow
Integrate into a workflow the incumbents don’t touch. Cursor’s blue ocean wasn’t better code generation than GitHub Copilot; it was integration into the developer’s IDE workflow in a way the incumbent tools were not. The workflow integration is the moat. Once the tool lives inside the user’s daily routine, the switching cost (see 7 Powers ) makes the position defensible in a way feature differentiation cannot. For workflow-native products, the feature set is contingent on the workflow—you build whatever makes the workflow better, and the feature list is different from competitors’ because the workflow is different.
These three blue-ocean dimensions have something in common: they are all invisible on the strategy canvas, which plots features. The canvas will never tell you to serve a different segment, use a different channel, or embed in a different workflow, because those decisions are above the canvas. A product team that stays inside the canvas finds only red-ocean blue oceans—rearranged features that get copied in weeks. A product team that thinks about segment, channel, and workflow first and uses the canvas second finds blue oceans that persist.
Revisiting Cirque du Soleil
Re-read the Cirque du Soleil case through the segment/channel/workflow lens and the real insight emerges. Cirque du Soleil did not out-innovate circuses on the circus attribute axis. It redefined what market it was in.
- Segment: adult theatregoers, not families with young children.
- Channel: urban theatre venues with high ticket prices and long runs, not suburban travelling tents with low ticket prices and short visits.
- Workflow: a night out at the theatre with dinner and drinks, not a day out at the circus with the kids.
The ERRC moves (eliminate star performers, raise theatrical quality, create artistic music) were the consequences of those upstream choices, not the source of the blue ocean. If you only saw Cirque du Soleil through the strategy canvas, you’d think they’d done a clever feature redesign. If you see them through the segment/channel/workflow lens, you’d see they’d found a market nobody was serving and then designed the product to fit.
Teams applying Blue Ocean Strategy in 2026 should follow the same sequence: pick the segment, channel, or workflow blue ocean first, then use the canvas to engineer the feature profile that fits. Do it in the other order—start with the canvas, assume features will make the market—and you produce a red ocean in blue wrapping paper.
Using the Strategy Canvas Correctly
Given the trap, the strategy canvas is still worth drawing. Just use it for diagnostic purposes, not prescriptive ones:
- Draw the industry value curve. This shows what the industry is fighting over—the shared assumptions everyone competes on. The more consistent the competitors’ curves are, the redder the ocean.
- Ask: which of these attributes nobody is asking for? The industry fights over them because the industry has always fought over them. Customers in a new segment may not care. Eliminating them isn’t a feature decision; it’s a signal that you’re looking at a different market.
- Ask: what’s not on this canvas that matters to someone the industry isn’t serving? This is the question that produces real blue oceans. Segment, channel, and workflow attributes don’t appear on the industry canvas because the industry hasn’t been fighting over them.
- Only then draw your blue-ocean curve. And accept that the curve isn’t the moat; the segment/channel/workflow decision is.
Applied this way, the canvas is a diagnostic of red-ocean-ness, not a tool for designing feature differentiation.
Blue Ocean Alongside the Other Frameworks
Blue Ocean Strategy sits naturally alongside the other frameworks in this cluster:
- Playing to Win answers where will we play and how will we win? Blue ocean is a specific type of Where to Play answer—pick a market space that nobody else is in. The ERRC grid is a tool for a specific type of How to Win answer, but only one of many.
- 7 Powers asks what durable moat does this blue ocean actually produce? A blue ocean without Power underneath it is just an empty market the incumbents will enter as soon as you prove it’s real. The best blue-ocean strategies build Switching Costs or Network Economies simultaneously with market creation.
- Wardley Maps ask what does the terrain look like, and which components are in genesis vs commodity? A blue ocean often involves a genesis-stage component that the incumbents’ product-stage capabilities can’t address. The map surfaces that.
- Good Strategy Bad Strategy asks what’s the specific diagnosis this blue ocean engages? A blue ocean without a named challenge is usually just a generic product in a new niche; a blue ocean with a sharp diagnosis is a defensible position.
Use Blue Ocean Strategy as the segment/channel/workflow creativity layer in the stack. Don’t expect it to also be the durability-testing layer, the terrain-mapping layer, or the diagnosis layer. Those come from elsewhere.
Blue Ocean and the Roadmap
Once you have found a blue-ocean segment, channel, or workflow, the work is to build coherently against it. Tag each Objective with the specific blue-ocean dimension it serves. Does this feature depend on the workflow integration that defines the blue ocean, or is it a red-ocean feature we’re building because the sales team asked for it? Does this Objective reach the new segment, or is it another feature for the existing segment? When the capacity grid in RoadmapOne is tagged this way, a review becomes possible: is our capacity actually serving the blue-ocean we chose, or is it drifting back into red-ocean feature-parity work?
Almost always, it drifts. Red-ocean requests—from sales, from existing customers, from internal stakeholders—are louder than blue-ocean work. The tagging discipline is the thing that makes the drift visible and forces the capacity conversation.
FAQ
What are the six principles of Blue Ocean Strategy?
Kim and Mauborgne identify six principles: four formulation principles — (1) reconstruct market boundaries, (2) focus on the big picture not the numbers, (3) reach beyond existing demand, (4) get the strategic sequence right — and two execution principles — (5) overcome key organisational hurdles, (6) build execution into strategy. Together they cover how to discover a blue ocean and how to actually ship against it, on the argument that good strategy requires both formulation and execution discipline.
What is a strategy canvas?
A strategy canvas is the central diagnostic tool of Blue Ocean Strategy. It is a two-dimensional chart that plots a set of industry competitive factors (features, attributes, services) on the horizontal axis and the offering level on the vertical axis. Competing products are drawn as curves across the factors, showing where the industry is fighting. A blue-ocean offering produces a visibly different curve — typically by eliminating or reducing some factors while raising or creating others. Useful as a diagnostic of red-ocean-ness; dangerous when used as the sole prescription for blue-ocean design.
What is Blue Ocean Strategy?
Blue Ocean Strategy is W. Chan Kim and Renée Mauborgne’s framework for creating uncontested market space (blue oceans) rather than competing in feature-crowded existing markets (red oceans). Its central tools are value innovation, the strategy canvas (a chart comparing offering levels across competitive factors), and the Four Actions Framework / ERRC grid (Eliminate-Reduce-Raise-Create). The framework was popularised in the 2005 book of the same name.
What is the Four Actions Framework?
The Four Actions Framework, also known as the ERRC grid, is a tool for creating a new value curve: Eliminate which factors the industry takes for granted, Reduce which factors well below industry standard, Raise which factors above industry standard, Create which factors the industry has never offered. The goal is a value curve that visibly departs from the industry norm—producing value innovation rather than feature-parity competition.
Is Blue Ocean Strategy still relevant in 2026?
The core intuition (create uncontested market space) is as valid as ever. The primary tool (the strategy canvas, which plots features along a horizontal axis) is increasingly misleading, because features are now cloned by competitors in weeks rather than years. In 2026, the durable blue oceans come from segment (who you serve), channel (how you reach them), and workflow (what you integrate with) — dimensions that don’t appear on the feature-oriented canvas. Use the canvas diagnostically, not prescriptively.
What is an example of a 2026-era blue ocean?
Vertical SaaS businesses like Toast (restaurants), Veeva (pharma), and Procore (construction) illustrate segment blue oceans — they serve verticals the horizontal incumbents cannot tailor for profitably. Shopify’s long-tail independent-retailer positioning was a channel blue ocean against Amazon. Cursor’s IDE-workflow integration is a workflow blue ocean against standalone coding assistants. None of these are differentiated feature curves on a canvas. All of them are segment/channel/workflow choices that the feature canvas would obscure.
How does Blue Ocean Strategy differ from Playing to Win?
Playing to Win is a complete strategy cascade — Winning Aspiration, Where to Play, How to Win, Capabilities, Management Systems. Blue Ocean Strategy is one specific approach to the Where to Play question, and the ERRC grid is one specific tool for How to Win. Blue Ocean sits inside Playing to Win as a tactical option. Playing to Win is the strategy framework; Blue Ocean is a creativity tool you can use within it.
How do I apply Blue Ocean Strategy to product management?
Start with segment, channel, or workflow — not features. Ask: who do the incumbents structurally fail to serve?, what channel can I access that they can’t?, what workflow do they not integrate into? Once you have a blue-ocean answer at that level, use the strategy canvas to engineer the feature profile that fits the segment/channel/workflow. Then tag every Objective on your roadmap with the dimension it serves, and review capacity allocation quarterly to confirm you haven’t drifted back into red-ocean feature-parity work.
Conclusion
Blue Ocean Strategy’s central idea—create uncontested market space rather than fight in feature-crowded ones—is more important in 2026 than it was in 2005, because red oceans now get redder faster than ever before. The primary tool the book gave us—the strategy canvas—is increasingly misleading, because its horizontal axis plots features and features are no longer durable moats.
The real blue oceans in 2026 are segment, channel, and workflow. Pick a segment the incumbents can’t serve. Pick a channel they can’t access. Pick a workflow they don’t integrate with. Then, and only then, use the canvas to engineer the feature set that fits. A bad salesperson asks for more features; a good one sells what they have. A bad strategist draws a differentiated feature canvas; a good one finds the market nobody else is serving and designs the product to fit it. Use the framework; don’t let it use you.