The Analyst's Path

Boiling the ocean

Boiling the ocean is unprioritised, exhaustive analysis that eats all the available time without ever landing a defensible answer. It rarely looks like a mistake, because from the inside it feels like diligence. The most telling sign is a team that can't state a one-day answer. The fix is the diminishing-returns test: ask whether one more hour of this analysis would change the recommendation, and stop when the answer is no.

3 min readPart of Hypothesis-Driven Problem SolvingOpen in course mode

Advertisement

Boiling the ocean is the standing name for the failure all of this is built to prevent: unprioritized, exhaustive analysis that eats all the available time without ever landing a defensible answer. It rarely announces itself as a mistake. From the inside, it feels like diligence. You'll recognize the symptoms. Data pulls keep expanding ("let me just check one more cut"). Decks grow every week while real insight doesn't. Days go on an elaborate model whose precision the question never required. Work continues on branches a five-minute check would have eliminated. Most telling of all, the team can't state a one-day answer, because it never let itself commit to one.

What causes teams to boil the ocean?

Each of those symptoms traces back to the absence of one of the four tools you've just built, and that's why the four work as a system:

  • Without a day-one hypothesis, there's nothing to prioritize against. Every branch of the issue tree looks equally worth investigating, so the team investigates all of them, equally, forever.
  • Without a driver tree and its bridge, the team can't cheaply tell which lever moved. So it re-derives the same conclusion three different inconclusive ways, when one clean decomposition would have done.
  • Without a minimum killing analysis, nobody ranks cheap tests against expensive ones. The instinct defaults to "more data is always better," and the slowest, most expensive analysis gets run first because it feels the most rigorous.
  • Without a one-day answer, no one is ever forced to say out loud, "here is my current best guess." A team with no stated position can't notice when today's work no longer moves that position, and that's the moment further analysis has stopped paying for itself.

Advertisement

How do you stop boiling the ocean?

Beyond holding the four tools, there's a practical fix you can apply at any hour, the diminishing-returns test. Ask yourself: would one more hour of this specific analysis change the recommendation? The moment the answer is no, stop. The analysis isn't finished in some absolute sense, since there's always one more cut you could run. You stop because the marginal hour has stopped buying anything the client is paying for. Time-boxing each piece of analysis before you start it ("half a day on this, then reassess") applies the same test in advance, so you don't have to rely on willpower to notice it mid-stream. The four tools and this test together are the complete standing defense against the most expensive habit in this profession.

Advertisement

Part of the course

This page is part of Hypothesis-Driven Problem Solving (CN1.02), in Phase 1: Accounting: the language of business. The module's flashcards and its quiz are in the app.