Why "Boil the Ocean" can create friction
People use familiar workplace shorthand because it feels efficient in the moment. The problem is that a familiar phrase can still leave the real ask, the real stakes, or the expected next step unstated.
That gap gets more expensive in Slack and email, where the reader cannot rely on tone or a quick follow-up question to fill in the missing context.
Clarity Score: 4.2/10
Clear scores workplace language across directness, specificity, tone safety, and async clarity. "Boil the Ocean" lands here because:
- Directness: 4/10. It communicates that the scope is too large, but not what part of the plan is the problem.
- Specificity: 3/10. The phrase needs a concrete recommendation about what to cut, defer, or sequence.
- Tone Safety: 5/10. Between peers it can sound colorful. In tense conversations, it can sound like a joke at someone else's expense.
- Async Clarity: 5/10. In text, it works only if the message includes a narrower path forward.
A clearer version of the same message
If you want to keep the intent but remove the guesswork, a stronger version looks like this:
This plan is trying to ship onboarding, billing cleanup, and analytics in one sprint. Let us cut analytics and keep the first release to onboarding plus billing fixes.
What people hear when you say "Boil the Ocean"
Most teams already know what the phrase is trying to say. The problem is that it often becomes the entire feedback instead of the start of the useful feedback.
If the scope is too big, the next sentence should narrow it. Otherwise the phrase just labels the issue without helping solve it.
3 Clearer Alternatives
Different situations call for different rewrites. These examples keep the original intent while making the message easier to understand on first read.
Direct
Best when: when the scope is too broad
This is too much for one sprint. Let us cut analytics and ship onboarding first.
It pairs the critique with a concrete reduction in scope.
Diplomatic
Best when: when you want to preserve momentum
I think we can get this over the line faster if we narrow phase one to the signup flow and save reporting for phase two.
It keeps the tone constructive while still challenging the scope.
Async-Friendly
Best when: when you want a written scope decision
Current proposal covers three workstreams. Recommend phase one = auth plus setup, phase two = reporting. If we agree, I will update the roadmap doc.
It turns a vague warning into a concrete proposal the team can approve.
Before and After in Slack
The stronger version works better because the reader can see the request, the timing, and the expected response in one pass, even if the message is slightly longer.
Before:
This feels like boiling the ocean.
After:
This is too wide for the timeline. I recommend we limit phase one to auth plus setup and move reporting to phase two.
What changed
The rewrite still challenges the scope, but it does so in a way that helps the team act instead of react.
Common questions about "Boil the Ocean"
What does boil the ocean mean at work?
"Boil the ocean" means trying to do too much at once. In workplace conversations, it is usually a warning that the scope is unrealistic, but it often stops short of naming what to remove.
Is "boil the ocean" rude?
It can be. The phrase is often used as shorthand criticism, and without specifics it can sound dismissive rather than helpful.