Principles of Product Management: Blue Ocean vs Red Ocean Strategy, Disruptive Innovation (Christensen), Jobs-to-be-Done (JTBD)

Blue Ocean vs Red Ocean Strategy, Disruptive Innovation (Christensen), Jobs?to?be?Done (JTBD)

Blue Ocean vs Red Ocean Strategy, Disruptive Innovation, Jobs-to-be-Done (JTBD) – Study Guide

What This Is

These are three interlinked frameworks for identifying and capturing untapped market opportunities. Blue Ocean Strategy (BOS) helps you create new demand in uncontested markets (e.g., Cirque du Soleil reinventing the circus). Disruptive Innovation (Christensen) explains how startups or incumbents can upend industries by serving overlooked customers (e.g., Netflix vs. Blockbuster). Jobs-to-be-Done (JTBD) reframes product development around the "job" users "hire" a product to do (e.g., "I hire a milkshake to keep me full during my commute"). Together, they help PMs avoid competition, build defensibility, and align product decisions with real user needs.

Real-world example: When Square launched its card reader in 2010, it applied all three: - Blue Ocean: Created a new market for small merchants (vs. fighting Visa/Mastercard for enterprise clients). - Disruptive Innovation: Served "non-consumers" (street vendors, farmers' markets) ignored by traditional POS systems. - JTBD: Solved the job of "accepting payments anywhere" (not just "processing transactions faster").

Key Terms & Frameworks

Blue Ocean Strategy (BOS)

• Red Ocean: Existing market space with defined rules, intense competition, and shrinking profits (e.g., ride-hailing in 2023).
• Blue Ocean: Uncontested market space where demand is created, not fought over (e.g., Tesla’s early focus on electric luxury cars, not competing with Toyota/Honda on price).
• Four Actions Framework (ERRC Grid):
• Eliminate (What factors does the industry take for granted that can be removed?)
• Reduce (What can be cut below industry standards?)
• Raise (What can be elevated above industry standards?)
• Create (What can be introduced that the industry has never offered?)
• Example: Nintendo Wii (Eliminated complex controllers, Reduced graphics, Raised motion interactivity, Created family-friendly gaming).
• Value Innovation: Aligning innovation with utility, price, and cost positions to create a leap in value for buyers and the company. Formula: Value Innovation = Buyer Value-+ Cost ? (e.g., Southwest Airlines: Eliminated meals/seat assignments, Reduced turnaround time, Raised frequency, Created low-cost air travel).

Disruptive Innovation (Clayton Christensen)

• Disruptive Innovation: A product/service that starts at the low end of a market (or creates a new one) and moves upward, eventually displacing incumbents (e.g., digital cameras disrupting film, then smartphones disrupting digital cameras).
• Sustaining Innovation: Improvements to existing products for mainstream customers (e.g., iPhone 14 vs. iPhone 13). Not disruptive.
• Low-End Disruption: Targets overserved customers with a "good enough" product at a lower price (e.g., Dollar Shave Club vs. Gillette).
• New-Market Disruption: Creates a market where none existed by serving non-consumers (e.g., Canva for non-designers).
• Disruption Formula: Disruption = (Performance < Incumbent) + (New Dimension of Value) + (Lower Cost/Accessibility) (e.g., Airbnb: Performance (hotel quality) was initially worse, but it offered "local experiences" and lower prices).

Jobs-to-be-Done (JTBD)

• Job: The progress a user is trying to make in a specific circumstance (e.g., "I need to feel connected to my team while working remotely").
• Functional Job: The practical task (e.g., "Send a message to my team").
• Emotional/Social Job: How the user wants to feel or be perceived (e.g., "Look professional in front of my boss").
• Job Statement Template: When [situation], I want to [motivation], so I can [expected outcome]. (e.g., "When I’m commuting, I want to pass the time, so I can arrive at work less stressed.")
• Forces of Progress (JTBD Framework):
• Push: What’s driving the user to seek a solution (e.g., "My current tool is too slow").
• Pull: The allure of a new solution (e.g., "This new app promises 2x speed").
• Anxiety: Fears holding the user back (e.g., "Will this new tool be hard to learn?").
• Habit: Inertia keeping the user in place (e.g., "I’m used to my old workflow").
• Outcome-Driven Innovation (ODI): A JTBD method where you:
• Identify the job.
• Uncover desired outcomes (metrics users care about, e.g., "minimize time spent onboarding").
• Prioritize outcomes by importance and satisfaction.
• Design solutions to over-serve the most underserved outcomes.

Step-by-Step / Process Flow

1. Identify a Blue Ocean Opportunity

Action: Use the ERRC Grid to analyze your industry. - Step 1: List all factors the industry competes on (e.g., for taxis: price, car cleanliness, driver rating, app UX). - Step 2: Apply ERRC: - Eliminate: What can you remove? (e.g., Uber eliminated "hailing a cab" and "cash payments"). - Reduce: What can you cut below industry standards? (e.g., Uber reduced car quality requirements for drivers). - Raise: What can you elevate? (e.g., Uber raised transparency with real-time tracking). - Create: What can you introduce? (e.g., Uber created surge pricing and driver ratings). - Step 3: Validate with users: "Would you switch to a product that does X but not Y?"

2. Assess Disruptive Potential

Action: Use Christensen’s Disruption Checklist. - Step 1: Identify non-consumers or overserved customers (e.g., "Who isn’t using our product because it’s too complex/expensive?"). - Step 2: Map the "performance oversupply" (e.g., "Do users care about 90% of our features?"). - Step 3: Design a "good enough" solution for the low end (e.g., "Can we build a stripped-down version for $10/month?"). - Step 4: Test if incumbents will ignore you (e.g., "Will Salesforce care if we target SMBs with a basic CRM?").

3. Apply JTBD to Product Development

Action: Run a JTBD Interview and synthesize insights. - Step 1: Recruit users who recently "hired" or "fired" a product (e.g., "Why did you switch from Excel to Notion?"). - Step 2: Ask about the circumstance (e.g., "What were you doing when you realized you needed this?"). - Step 3: Uncover the job (e.g., "What were you trying to accomplish?"). - Step 4: Dig into outcomes (e.g., "What would make this 10x better for you?"). - Step 5: Map the forces of progress (e.g., "What almost stopped you from switching?"). - Step 6: Prioritize outcomes using ICE or RICE (e.g., "Which outcome is most important but least satisfied?").

4. Combine All Three for a Product Strategy

Action: Align BOS, Disruption, and JTBD into a roadmap. - Step 1: Use JTBD to identify a high-priority job (e.g., "I need to collaborate on documents in real time"). - Step 2: Apply BOS to create a blue ocean (e.g., "What if we eliminate file versioning and reduce collaboration barriers?"). - Step 3: Assess disruptive potential (e.g., "Can we serve non-consumers like freelancers with a free tier?"). - Step 4: Build an MVP targeting the job (e.g., Google Docs: real-time editing, free, no file conflicts).

Common Mistakes

Mistake 1: Confusing Blue Ocean with "First-Mover Advantage"

• Correction: Blue Ocean isn’t about being first—it’s about creating uncontested demand. First-movers often fail (e.g., Webvan vs. Instacart). Focus on value innovation, not speed.
• Why: Being first doesn’t guarantee defensibility; creating a new market does.

Mistake 2: Assuming Disruption = "Better Technology"

• Correction: Disruption is about business model innovation, not tech. Example: Netflix disrupted Blockbuster with mail-order DVDs (not streaming) by targeting "non-consumers" (people who didn’t go to video stores).
• Why: Tech alone doesn’t create new markets; accessibility and cost do.

Mistake 3: JTBD = "User Needs" or "Pain Points"

• Correction: JTBD is about the progress users want to make, not their stated needs. Example: Users don’t "need" a drill; they need a hole in the wall. Don’t ask, "What features do you want?" Ask, "What are you trying to accomplish?"
• Why: Users often misdiagnose their own needs (e.g., "I need a faster horse" vs. "I need to get from A to B faster").

Mistake 4: Ignoring the "Forces of Progress" in JTBD

• Correction: Don’t just focus on the "pull" (desired outcomes). Address anxieties (e.g., "Will this break my workflow?") and habits (e.g., "I’m used to Excel"). Example: Slack reduced anxiety by offering a free tier and integrations with existing tools.
• Why: Even the best solution fails if users are afraid to switch.

Mistake 5: Prioritizing Features Over Outcomes in JTBD

• Correction: Don’t build features; solve for outcomes. Example: Instead of "Add a dark mode," ask, "How can we reduce eye strain for users working at night?" (Outcome: "Minimize screen glare").
• Why: Features are means to an end; outcomes are the end.

PM Interview / Practical Insights

1. "How would you apply Blue Ocean Strategy to [our product]?"

• Trap: Jumping to "eliminate features" without analyzing the industry.
• Answer:
• Map the industry’s competitive factors (e.g., for a project management tool: price, integrations, UI complexity).
• Apply the ERRC Grid to identify what to eliminate/reduce/raise/create.
• Propose a blue ocean move (e.g., "Eliminate Gantt charts, Reduce integrations to 3 core ones, Raise collaboration speed, Create AI-generated project summaries").
• Validate with users: "Would you switch to a tool that does X but not Y?"

2. "Is [Product X] disruptive? Why or why not?"

• Trap: Calling any innovative product "disruptive" (e.g., "iPhone was disruptive!"—it was sustaining for Apple).
• Answer:
• Disruptive if: It started at the low end (e.g., Tesla’s Roadster was not disruptive; Tesla’s Model 3 was) or created a new market (e.g., Airbnb for non-hotel travelers).
• Not disruptive if: It’s a sustaining innovation (e.g., iPhone improving camera quality) or targets mainstream customers (e.g., Peloton for fitness enthusiasts).

3. "How would you use JTBD to improve [Feature Y]?"

• Trap: Focusing on the feature, not the job (e.g., "Improve the checkout flow" vs. "Help users complete their purchase faster").
• Answer:
• Identify the job (e.g., "I need to buy a gift for my mom’s birthday").
• Interview users who recently "hired" or "fired" the feature (e.g., "Why did you abandon your cart?").
• Uncover outcomes (e.g., "I want to find the perfect gift in <5 minutes").
• Prioritize the most underserved outcome (e.g., "Reduce time to find a gift").
• Propose a solution (e.g., "Add a 'Gift Finder' quiz that narrows options in 2 clicks").

4. "How do you balance Blue Ocean and Disruptive Innovation?"

• Trap: Treating them as mutually exclusive.
• Answer:
• Blue Ocean creates new demand; Disruptive Innovation captures it by serving non-consumers.
• Example: Zoom (Blue Ocean: "Eliminate travel for meetings," Disruptive: "Serve non-consumers like small teams with a free tier").
• Action: Use BOS to identify the market, then apply disruption to enter it (e.g., "Can we serve this market with a lower-cost, simpler solution?").

Quick Check Questions

1. Your team wants to add a "social feed" to a productivity app to increase engagement, but early tests show it hurts NPS. How do you decide?

• Answer: Kill the feature. JTBD teaches that engagement is a lagging indicator of solving the core job (e.g., "Help me get work done"). If NPS drops, users are telling you the feature distracts from the job. Double down on outcomes (e.g., "Reduce time to complete tasks") instead of vanity metrics.
• Why: Engagement-value. Focus on the job, not the feature.

2. A stakeholder says, "We need to add AI to our product to stay competitive." How do you respond?

• Answer: Ask, "What job does AI solve for our users?" If the answer is "It’s cool," it’s a red ocean move (competing on tech, not value). If it’s "Help users write emails 2x faster," it’s a JTBD opportunity. Validate with users: "Would you pay for this?"
• Why: Tech for tech’s sake is a red ocean trap. Tie it to a job.

3. Your competitor launches a feature that copies your Blue Ocean move. How do you respond?

• Answer: Double down on value innovation, not competition. Example: When Lyft copied Uber’s ride-hailing, Uber created Uber Eats (a new blue ocean). Use the ERRC Grid to find the next uncontested space (e.g., "Eliminate delivery fees, Reduce wait time, Raise food quality, Create group ordering").
• Why: Blue Ocean is about creating demand, not defending it.

Last-Minute Cram Sheet

1. Blue Ocean = Create demand (ERRC Grid: Eliminate, Reduce, Raise, Create).
2. Red Ocean = Fight for demand (compete on price, features, or tech).
3. Value Innovation = Buyer Value-+ Cost ? (e.g., Southwest Airlines).
4. Disruptive Innovation-Better tech (it’s about business model + non-consumers).
5. Low-End Disruption: "Good enough" for overserved customers (e.g., Dollar Shave Club).
6. New-Market Disruption: Serves non-consumers (e.g., Canva for non-designers).
7. JTBD = Progress, not features (e.g., "Hire a milkshake for a long commute").
8. Job Statement: When [situation], I want to [motivation], so I can [outcome].
9. Forces of Progress: Push, Pull, Anxiety, Habit (address all four to drive adoption).
10. Trap: "First-mover advantage"-Blue Ocean (e.g., Webvan failed; Instacart succeeded by focusing on value innovation).