agentleFS
deciqAIdeciqAI/knowledge-skills/blue-ocean-strategy/SKILL.md

blue-ocean-strategy

Skill13 starsChanged 4 months agoMITView on GitHub

Activate when: user asks 'how do we stop competing on price?', 'what new market can we create?', 'is there a way to differentiate and cut costs at the same time?', describes an industry where all competitors look identical and margins are eroding, or a team is choosing a market entry angle to avoid head-to-head competition.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the Value Innovation Audit: map competition → identify non-customers → apply ERRC → validate canvas.

    line 41
  2. Distinctive:

    Buyer utility validation: Stop-rule: do non-customers say "never seen anything like this" — or "that's nice, but I still wouldn't switch"?

    line 48
  3. Distinctive:

    One sentence test: If the new value prop requires more than one sentence for a non-customer, the canvas lacks divergence — iterate.

    line 80

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blue Ocean Strategy

Overview

Most competitive strategy assumes industry boundaries are fixed. Blue Ocean Strategy's core claim: that assumption is optional. Kim and Mauborgne studied 150 strategic moves across 30 industries over 130 years — lasting high growth came from reconstructing market boundaries, not competing harder within them.

The mechanism is the ERRC grid (Eliminate, Reduce, Raise, Create): Eliminate+Reduce drive cost below industry average; Raise+Create drive buyer value above it — breaking the differentiation/cost trade-off simultaneously. The critical input is the non-customer lens: blue oceans are found by studying people who refuse the category, not existing customers.

Compose with: porters-five-forces before; disruptive-innovation as complementary lens; pricing-strategy after ERRC; first-mover-advantage for defense window.

When to Use

Apply when: visible industry convergence (products similar, price is primary differentiator, margins eroding); team choosing market entry angle to avoid commoditized competition; product losing pricing power despite feature improvements; a team asks how to avoid competing head-to-head with AI-native incumbents or trillion-dollar platforms on a commoditized general capability (e.g., "everyone's shipping the same AI chatbot — where's the uncontested space?", AI capex arms race, saturated AI adoption); someone asks "how do we stop competing on price?" or "what new market can we create?"

When NOT to use: competitive dimensions fixed by law/safety standards; early-stage startup without sufficient market exposure to identify non-customer patterns; company lacks execution capability for a new value proposition; blue ocean with network-effect protection already exists — use disruptive-innovation.

Coaching Novices (Adaptive Front Door)

  • Engine mode: user has a specific industry, named competitors, strategic question → run The Process directly.
  • Coach mode: user asks "what is this / does it apply to me?" → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

  1. One-line what-it-is. Blue ocean asks which value dimensions to eliminate, reduce, raise, and invent — so you stop competing on the same terms entirely.
  2. Check fit. Match against When to Use / When NOT to use.
  3. Elicit their real case. "Which industry, which competitors, and what value dimensions is everyone competing on today?"

[WAIT — do not advance until user responds]

  1. One step at a time. Map the current strategy canvas first; only advance to Six Paths after canvas is visible.

[WAIT — do not advance until user responds]

  1. Close by naming the payoff. Identify the value dimension they found that could be eliminated without buyer resistance.

[WAIT — do not advance until user responds]

The Process

Run the Value Innovation Audit: map competition → identify non-customers → apply ERRC → validate canvas.

  1. Current strategy canvas (As-Is). Score 6–8 competitive factors for each major competitor (1–5). Make red-ocean convergence visible.
  2. Three tiers of non-customers. (a) Soon-to-be: using but dissatisfied; (b) Refusing: using substitutes; (c) Unexplored: never considered. Ask each: "What would make this product worth using?"
  3. Six Paths. (1) Substitute industries; (2) Strategic groups; (3) Buyer chain; (4) Complements; (5) Functional vs. emotional; (6) Trends. Generate 2–3 candidate opportunities per path.
  4. ERRC grid. Eliminate / Reduce / Raise / Create. Check: Eliminate+Reduce savings > Raise+Create costs? If not, this is differentiation, not value innovation.
  5. Target canvas (To-Be). Validate: Focus (3–4 dimensions); Divergence (different curve shape from competitors); Tagline (one sentence a non-customer understands).
  6. Buyer utility validation. Stop-rule: do non-customers say "never seen anything like this" — or "that's nice, but I still wouldn't switch"? If the second, iterate ERRC.

Output Template

Current Canvas: factor table with competitor scores + red-ocean zone assessment
Non-Customer Map: soon-to-be / refusing / unexplored + shared dissatisfaction
Six Paths: opportunity per path → primary opportunity selected
ERRC Grid: Eliminate / Reduce / Raise / Create + arithmetic check
Target Canvas: To-Be scores + Focus / Divergence / Tagline check
Buyer Utility: utility gaps closed + non-customer response + stop-rule decision

→ Method in Action: Cirque du Soleil (1984) · Yellow Tail Wine (2001) → 2026 lens: Escaping the red ocean of general AI chatbots via vertical/agentic AI (2024–2026)

Innovation Packs

DomainCanvas convergence (what everyone competes on)ERRC emphasisCommon failure
Consumer goods / food-bevbrand prestige, category expertise, range breadthEliminate conventions buyers don't value (Yellow Tail: removed the wine-knowledge requirement); Create ease of selectioneliminating complexity that was never the non-customer's stated reason for refusing — restructuring for convenience, not their value
B2B softwarefeatures, integration depth, enterprise complianceEliminate customization depth / reduce onboarding friction / raise time-to-value / create self-serve"Create" quietly rebuilds enterprise machinery non-customers don't need — Eliminate is underperforming
Healthcarefacility scale, specialist breadth, coverage networksRaise/Create convenience and access while Eliminating facility overheadtreating regulatory minimums as eliminable "industry assumptions" — they are fixed, map them before ERRC
Travel / airlineshub networks, seat classes, in-flight amenitiesEliminate lounges, meals, seat classes; Raise departure frequency; Create point-to-point speed priced against driving (Southwest)benchmarking rival carriers instead of the substitute (the car) — Path 1 skipped

Contribute a pack for your domain — see the template at the repo root.

Applying It Well

  • Canvas before grid. Make the red ocean visible first — teams that skip to ERRC over-weight Raise and under-weight Eliminate.
  • Eliminate is the discipline. Force at least two items into Eliminate. Eliminating costs without losing buyer value funds the value jump.
  • Non-customers over customers. Non-customers reveal structural problems; existing customers suggest incremental improvements.
  • One sentence test. If the new value prop requires more than one sentence for a non-customer, the canvas lacks divergence — iterate.
  • Blue oceans turn red. Build switching costs and network effects from day one. Use first-mover-advantage.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Fake moveReality
[D] Calling slight differentiation "value innovation"Requires simultaneously lower cost AND higher buyer value. Better product at higher cost = differentiation. ERRC arithmetic must close.
[D] ERRC grid with empty Eliminate/Reduce rowsOnly Raise+Create means costs go up — product improvement, not blue ocean.
[D] Competitor benchmarking treated as strategy canvasCanvas maps buyer-perceived factors, scored by buyer experience — not features from a spec sheet.
[D] "Found a blue ocean" before non-customer testingWithout refusing and unexplored non-customer exposure, it's a hypothesis, not an audit.
[D] Confusing "no competition" with "no market"No competitors may mean demand must be created. Mistaking it for validated demand leads to over-investment in market education.
[D] Canvas parallel to competitors but spiking on one factorThat is a red-ocean differentiation move. All three properties (focus, divergence, tagline) must pass.
[D] Six Paths used as brainstorm not structured analysisEach path has a specific question — answer it precisely, or you get noise instead of insight.
[D] Assuming the blue ocean will stay blueImitators arrive. Treat value innovation as a window, not a shield.
→ Add [O] entries here after each real use — paste the actual failure patternWhat went wrong and why

Red Flags

  • Canvas overlaps substantially with competitors — divergence property absent
  • ERRC Eliminate row is blank or uncommitted
  • Non-customer research absent — analysis based only on current customers
  • Value proposition requires more than one sentence to explain
  • Raise+Create costs exceed Eliminate+Reduce savings — model doesn't close
  • Opportunity is in a space where a network-effects incumbent already operates

Verification

  • Current canvas drawn with buyer-perceived scores, convergence visible
  • Non-customers researched across ≥2 tiers, shared dissatisfaction identified
  • Six Paths applied with specific structural question per path
  • ERRC Eliminate+Reduce substantively populated, arithmetic checked
  • Target canvas passes all three properties: focus, divergence, tagline
  • Non-customer utility validation complete — "never seen this before" confirmed or ERRC iterated
  • Imitation timeline estimated, moat-building actions identified

Part of deciqAI Knowledge Skills — 253 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/blue-ocean-strategy · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/blue-ocean-strategy.json

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.