blue-ocean-strategy
The blue-ocean-strategy skill applies the Blue Ocean Strategy framework to help businesses create uncontested market space through value innovation rather than competing directly with rivals. Activate this skill when users discuss blue ocean concepts, the ERRC framework, value-cost trade-offs, new market categories, underserved segments, or strategies to escape price-based competition. It evaluates business strategies against blue ocean principles and provides specific moves to shift from red ocean competition to creating new demand.
git clone --depth 1 https://github.com/wondelai/skills /tmp/blue-ocean-strategy && cp -r /tmp/blue-ocean-strategy/blue-ocean-strategy ~/.claude/skills/blue-ocean-strategySKILL.md
# Blue Ocean Strategy Framework Strategic framework for creating uncontested market space that makes the competition irrelevant, based on the simultaneous pursuit of differentiation and low cost. ## Core Principle **Don't compete in bloody red oceans. Create blue oceans of uncontested market space.** Most companies fight for share in existing industries; winners create new market space where competition is irrelevant by delivering a leap in value for both buyers and themselves. Competition-based strategy is zero-sum — value innovation creates new demand and breaks the value-cost trade-off. ## Scoring **Goal: 10/10.** Rate any business strategy or value proposition 0-10 against blue ocean principles: clear value innovation, elimination of unnecessary factors, and creation of new demand. Report the current score and the specific moves needed to reach 10/10; low scores mean competing in a red ocean. ## Framework ### 1. Red Ocean vs. Blue Ocean **Core concept:** Red oceans are existing market spaces where rivals fight over shrinking profits; blue oceans are new market spaces where the competition is irrelevant. | Red Ocean Strategy | Blue Ocean Strategy | |-------------------|---------------------| | Compete in existing market space | Create uncontested market space | | Beat the competition | Make competition irrelevant | | Exploit existing demand | Create and capture new demand | | Make the value-cost trade-off | Break the value-cost trade-off | | Align with differentiation OR low cost | Pursue differentiation AND low cost | **Examples:** Airlines competing on routes, amenities, and price are red ocean; Cirque du Soleil inventing a new entertainment form, Netflix replacing rental with streaming, and Nintendo Wii trading graphics power for accessible motion gaming are blue. See: [references/blue-ocean-examples.md](references/blue-ocean-examples.md) for detailed case studies. ### 2. Value Innovation **Core concept:** The cornerstone of blue ocean strategy — pursue differentiation and low cost simultaneously, creating a leap in value for buyers and the company (Value Innovation = Utility × Price × Cost). **Why it works:** Eliminating and reducing over-served factors cuts costs at the same time that raising and creating factors lifts buyer value — value rises more than cost, breaking the trade-off competitors assume is fixed. | Traditional View | Value Innovation View | |-----------------|---------------------| | High value = high cost | High value CAN = low cost | | Differentiate OR cut costs | Differentiate AND cut costs | | Better performance on established factors | New factors; eliminate old factors | **Example — Cirque du Soleil:** eliminated animal shows, star performers, multiple arenas (cost down); reduced thrill and humor; raised venue quality, artistic music and dance; created theme, refined environment, multiple productions. Outcome: priced above circus, costs below theater, a new market. See: [references/value-innovation.md](references/value-innovation.md) for value innovation frameworks. ### 3. Strategy Canvas **Core concept:** The diagnostic tool — plot the factors an industry competes on against the offering level for you and competitors. Red oceans show everyone's curve looking the same; a divergent curve signals a blue ocean. **How to use:** 1. List the industry's competing factors (wine: price, prestige, aging quality, vineyard legacy, complexity, range, marketing) 2. Plot your curve and competitors' — expect near-identical curves in a red ocean 3. Ask: which factors do buyers not actually care about? What could be eliminated, reduced, raised, or created? Where does the buyer experience hurt? **Example — Yellow Tail wine:** | Factor | Industry Average | Yellow Tail | |--------|-----------------|-------------| | Price, prestige, aging quality | Medium-High | LOW | | Vineyard legacy, complexity, range | High | LOW | | Easy drinking | Low | HIGH | | Fun/adventure, accessibility | Low | HIGH | **Result:** A different curve = blue ocean. See: [references/strategy-canvas.md](references/strategy-canvas.md) for templates and examples. ### 4. Four Actions Framework (ERRC Grid) **Core concept:** Four questions that reconstruct buyer value — Eliminate and Reduce cut costs; Raise and Create lift value. | Action | Question | Examples | Effect | |--------|----------|----------|--------| | **Eliminate** | Which taken-for-granted factors add no buyer value? | Cirque: animals, stars; Southwest: meals, seat assignments; IKEA: sales staff, assembly | Cost down; friction removed | | **Reduce** | What can go well below industry standard? | Yellow Tail: prestige, complexity; Salesforce v1: customization | Cost down; over-serving stops | | **Raise** | What should go well above industry standard? | Cirque: artistic value; Dyson: suction, design; Apple: UX | Value up; hard to match | | **Create** | What has the industry never offered? | Netflix: unlimited streaming, no late fees; Uber: live tracking, cashless payment | New demand; attracts non-customers | **Net result:** value increases more than cost — value innovation. **Ethical boundary:** Don't eliminate factors buyers truly value (especially safety or accessibility) — test assumptions before cutting. See: [references/errc-grid.md](references/errc-grid.md) for ERRC templates and exercises. ### 5. Six Paths Framework **Core concept:** Six systematic ways to look beyond existing industry boundaries and spot blue ocean opportunities. | Path | Look across | Example | How to apply | |------|-------------|---------|--------------| | **1. Alternative industries** | Different forms solving the same need | NetJets: alternative to both airlines and jet ownership | Map alternatives → find unmet needs across them | | **2. Strategic groups** | Clusters pursuing similar strategies | Lexus: luxury at accessible price | Find over/under-served needs → position between groups | | **3. Chain of buyers** | Purchasers vs. users vs. i
Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "the project keeps growing", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, fighting feature creep, running a small team, avoiding long-term roadmaps, or killing unnecessary meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", "business logic is tangled with the framework", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", "unit test quality", "my code is hard to read", "this function is a mess", "clean up this code", or "hard to maintain". Also trigger when reviewing pull requests for readability, untangling messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.
Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "viral loop", "referral program", "organic growth", "how do I get people to share this", "nobody is sharing it", or "make this spread". Also trigger when designing shareable features, crafting social campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.
Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.
Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", "conversion funnel", "increase signups", "people add to cart but dont buy", or "improve conversions". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", "cant get mainstream customers", or "our go-to-market plan". Also trigger when a startup has early traction but cant grow beyond initial users, or when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.
Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "which database should I use", "SQL or NoSQL", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", "my queries are slow at scale", or "data is inconsistent across replicas". Also trigger when choosing a datastore, designing data pipelines, or debugging distributed-system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.