Boiling the Ocean

What does “boiling the ocean” mean?

Boiling the ocean describes a strategy or project so ambitious in scope that it is impossible to complete with available resources — the equivalent of trying to heat the entire ocean instead of a kettle. The phrase, common in consulting and corporate strategy, captures a recurring startup failure: solving everything for everyone instead of solving one thing for one segment.

Where founders boil the ocean

• Market scope: “We serve SMB, mid-market and enterprise across 5 industries” — every segment has different needs and the team cannot serve any of them well.
• Product scope: initial MVP includes 20 features rather than the one feature that solves the binding constraint.
• Geographic scope: launching simultaneously in 10 markets with no anchor customer in any.
• Persona scope: targeting both developers and executives in the same product — they buy differently and want different things.

Why it happens

• Optionality preservation: founders unwilling to disqualify markets in case the chosen one is wrong.
• Investor-driven scope creep: ambitious TAM stories that require breadth.
• Lack of conviction: small bets feel safer than concentrated ones, even when concentration is correct.
• Misreading “platform”: mature companies become platforms; early ones become focused tools first.

How to detect it

• The team cannot describe the target customer in one paragraph.
• The roadmap addresses needs from multiple segments without ranking.
• The pitch deck TAM is over $50B but no segment is >$1B addressable for this product.
• Every customer requires custom work because the product fits no one cleanly.

Do: narrow ruthlessly — one segment, one workflow, one job-to-be-done; defer everything else until the chosen wedge is proven.
Don’t: let “but we could also serve X” delay shipping for the primary segment — optionality without execution is just procrastination.