Mapping Blue Ocean Positioning

Given a product/business domain, produce:

1. Two 2x2 positioning maps (four axes total, paired into two maps)
2. Competitor plots on each map
3. Identified low-density quadrants ("Blue Oceans")
4. A feasibility score for each opportunity against organizational strengths

Example invocation: "Find blue ocean opportunities for a mid-size coffee roaster competing against Starbucks, Blue Bottle, and local independents."

Progress:

• Step 1: Define the analysis theme
• Step 2: Establish four evaluation axes
• Step 3: Map the competitor landscape
• Step 4: Identify blue ocean quadrants
• Step 5: Assess barriers to entry
• Step 6: Package findings in a structured template

Step 1: Define the Analysis Theme

State the specific product category or business domain precisely. "Coffee" is too broad; "ready-to-drink specialty coffee beverages" is workable. A narrow, concrete theme keeps axes meaningful and competitors comparable.

Step 2: Establish Evaluation Axes

Choose four criteria that are:

• Binary or spectrum-based (one pole vs. another), e.g., Luxury vs. Casual, Price (High/Low), Functionality (Simple/Complex)
• Unambiguous — any team member should be able to plot a competitor without debate
• High-impact — axes that actually drive customer choice in this category, not cosmetic distinctions

Pair the four axes into two independent 2x2 maps (e.g., Map A: Price × Luxury-Casual; Map B: Functionality × Target-Demographic). Avoid axes that correlate with each other — redundant axes waste a map.

Step 3: Map the Competitor Landscape

Plot every meaningful competitor (3–10 typically) onto both maps using the axes from Step 2. For each competitor, note:

• Approximate quadrant position
• Brief justification (why this placement, not just a guess)

Visualize density per quadrant — this reveals where competitors cluster and where they don't.

Step 4: Identify Blue Ocean Opportunities

Flag quadrants with zero or near-zero competitor presence. For each flagged quadrant:

• Brainstorm 2–3 concrete product/positioning concepts that would occupy that space
• Sanity-check that the quadrant is empty because of opportunity, not because it's a non-viable combination (e.g., "ultra-luxury + disposable" may be empty because nobody wants it, not because nobody's tried it)

Step 5: Assess Barriers to Entry

For each candidate blue ocean, score feasibility against the organization's actual capabilities:

• Brand power — does current brand perception support this positioning?
• Technical/operational capability — can the org actually build/deliver this?
• Capital requirements — what investment is needed, and is it available?
• Speed to market — can this be executed before competitors notice the gap?

Rate each dimension Low/Medium/High and compute an overall feasibility verdict. Discard opportunities with multiple "Low" ratings regardless of market attractiveness.

Step 6: Utilize Structured Templates

Present the final output in a standard format so teams can compare opportunities side by side:

Example 1: Input: "Map the mid-size coffee roaster against Starbucks, Blue Bottle, Dunkin, and local independents." Output:

• Map A axes: Price (Low↔High) × Luxury-Casual
• Map B axes: Convenience (Grab-and-go↔Sit-down) × Customization (Standard↔Bespoke)
• Plotted: Starbucks (Mid-price/Casual, High-convenience/Standard), Blue Bottle (High-price/Luxury, Sit-down/Bespoke), Dunkin (Low-price/Casual, High-convenience/Standard), Independents scattered Mid-High price/Luxury, Sit-down/Bespoke
• Blue ocean identified: High-price/Luxury + High-convenience/Standard — nobody offers premium-positioned, fast grab-and-go
• Concept: Premium canned/bottled single-origin cold brew sold through high-convenience channels
• Feasibility: Brand Medium (roaster has quality cred, lacks luxury cachet), Capability High (existing roasting expertise), Capital Medium (bottling line investment), Speed High
• Verdict: Pursue

Example 2: Input: "Analyze positioning for a new project management SaaS tool." Output:

• Map A axes: Price (Low↔High) × Complexity (Simple↔Enterprise-grade)
• Map B axes: Target team size (Solo/Small↔Large org) × Specialization (Generalist↔Industry-specific)
• Blue ocean candidate: Low-price + Enterprise-grade features — mostly empty since enterprise tools price high
• Feasibility check reveals: Capability Low (team lacks enterprise security/compliance expertise), Capital Low (can't fund compliance certifications)
• Verdict: Discard — real gap exists but barriers to entry are too high for this org currently; flag as "Monitor" for future reassessment