What it means
The phrase comes from the mental image of trying to heat an entire ocean until it evaporates. The point is not that the goal is wrong but that the method is hopeless, because the resources required grow far faster than the value delivered.
In finance and operations meetings it is shorthand for scope that has escaped control. You hear it most often in projects that touch data, systems or process design.
A finance transformation that promises to redesign every report, every control and every system in one release is a classic candidate, as is a budgeting exercise that insists on rebuilding every cost line from zero in a single cycle. The ambition is admirable; the delivery risk is what earns the label.
The financial consequence is real, not just rhetorical. Oversized programmes tie up cash and staff for long periods before producing any measurable benefit, which pushes the payback date far into the future and raises the chance the whole investment is written off.
A project that would return $2 for every $1 spent at a sensible scope can return nothing at all if it is scoped ten times larger and abandoned halfway. The usual antidote is to break the work into a sequence of narrower pieces that each deliver something usable.
Practitioners talk about a minimum viable scope, a pilot site or a first wave, all of which are ways of proving value early and funding the next stage from the result. This also gives finance a real number to test against the business case rather than a promise years away.
There is a fair counter-argument, which is that the phrase can be used lazily to kill any ambitious idea. Some problems genuinely need a wide fix, and slicing them too thinly produces a patchwork that never adds up.
The useful test is whether the work can be staged into pieces that stand on their own, not whether the total ambition sounds large.
In practice
Real-world examples.
Example
A retail chain's chief financial officer reviews a proposal to replace the point of sale system, the inventory system and the general ledger in one twelve month programme. She sends it back with a note that it tries to boil the ocean, and asks for a three stage plan starting with the ledger alone.
Example
A marketing director wants a single dashboard covering every channel, every region and every product line before any of it goes live. The analytics lead argues for one region first, on the grounds that a working regional view this quarter beats a perfect global view that never ships.
Example
During a post-merger integration, the programme office proposes harmonising all forty policies across both companies simultaneously. The integration lead narrows the first wave to expenses, procurement and payroll, because those three drive most of the cash impact and can be finished before the next reporting cycle.
Case study
Seen in the real world.
Meridian Fabrics is an invented manufacturer used here as a purely illustrative example. Its new operations director launched a programme to standardise every process in all nine factories at once, covering scheduling, quality checks, maintenance, procurement and shift handovers. The plan ran to more than three hundred workstreams and required almost every experienced supervisor to spend two days a week in design workshops.
Nine months in, the programme had produced a large catalogue of documented processes and almost no change on the factory floor. Output had actually dipped, because the supervisors who normally solved daily problems were sitting in meetings. The finance team could not point to a single benefit that had reached the profit and loss account.
The board paused the work and restarted it with one factory and one process: maintenance scheduling. That narrow slice delivered a measurable reduction in unplanned downtime within a quarter, and the result was used to justify rolling the same change to the other eight sites. The illustrative lesson was that the original goal was reasonable but the attempt to reach it in one move was not.
Watch out
Common mistakes.
- Using the phrase to dismiss any ambitious plan. The objection is to unstaged scope, not to ambition, and a large goal delivered in sensible waves is not boiling the ocean.
- Assuming a project is safe because each individual task is small. Scope risk comes from the number of moving parts and their dependencies, so hundreds of small tasks running at once can be just as unmanageable as a few enormous ones.
- Slicing a programme into pieces that cannot stand alone. If phase one delivers nothing usable without phase four, you have simply relabelled the same oversized project.
Questions
People also ask.
How do you tell an ambitious plan from one that boils the ocean?
Ask whether it can be cut into stages that each deliver a benefit you could measure and defend on their own; if it cannot, the scope is probably unworkable.
Is this phrase acceptable in formal financial writing?
It is common in meetings and internal memos but reads as slang, so in a board paper or an investment case it is better to write about excessive scope and staging risk.
What is the financial danger of a plan like this?
Cash and staff time are committed long before any benefit appears, which delays payback and raises the chance the entire spend is eventually written off.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%