Alyssa Towns
Alyssa Towns works in communications and change management and is a freelance writer for G2. She mainly writes SaaS, productivity, and career-adjacent content. In her spare time, Alyssa is either enjoying a new restaurant with her husband, playing with her Bengal cats Yeti and Yowie, adventuring outdoors, or reading a book from her TBR list.
What is boil the ocean?
"Boil the ocean" is an idiom commonly used in business settings and startup culture to describe taking on an impossible or unnecessarily difficult task or project. The connotation of this term is negative and should inspire reconsideration of a business decision or project.
When it comes to managing complex initiatives, the right project management software can make a difference, helping teams break down overwhelming goals into structured, achievable steps rather than trying to tackle everything at once.
TL;DR: Boil the ocean definition, importance, and examples
“Boiling the ocean” happens when teams try to do too much at once without clear priorities or constraints. Instead of driving impact, these efforts often lead to missed deadlines, wasted resources, and team burnout — making it critical to simplify goals and focus on what actually moves the needle.
Where does “boil the ocean” come from?
The phrase “boil the ocean” comes from a metaphor describing an impossible task— heating an entire ocean to its boiling point.
Its exact origin is unclear, but it gained popularity in business and consulting circles in the late 20th century as a way to describe unrealistic project scope.
Some sources loosely attribute the phrase to humorist Will Rogers, who jokingly suggested boiling the ocean as a solution to a complex problem — highlighting the absurdity of the idea.
Today, the expression is widely used in corporate and project management contexts as a warning to stay focused, prioritize effectively, and avoid overcomplicating work.
What happens when teams try to boil the ocean?
When teams try to boil the ocean, projects often fail due to unclear priorities, unrealistic expectations, and resource constraints.
Catching this early helps teams:
- Adjust timelines, budget, and resources
- Refocus on high-impact work
- Improve execution and delivery success
Without intervention, these projects typically suffer from delays, burnout, or complete failure.
How to avoid boiling the ocean?
Avoiding “boiling the ocean” comes down to clear prioritization, realistic planning, and controlled execution. By focusing on high-impact work, breaking down large goals, aligning resources, and preventing uncontrolled project expansion, teams can keep initiatives achievable and on track.
- Narrow critical efforts. Business leaders should identify the most vital work that teams must focus on to maximize impact, while avoiding spreading resources too thin. Prioritizing efforts can help teams alleviate the burden of taking on too many high-priority initiatives at once.
- Turn goals into smaller, manageable projects. Teams may find it challenging to track and follow large visions and strategic ideas. They may seem grandiose and impossible to achieve. Business leaders and managers should lean on project managers to break down more significant concepts into actionable plans.
- Allocate the right team and resources. Team members with mismatched skill sets or insufficient qualifications might feel a project is impossible. To combat this, leaders should assign the appropriate people, resources, and budgets to projects to increase the likelihood of success.
- Manage scope creep. Projects quickly turn into larger initiatives when scope creep comes into play, and a growing scope can put the end goal out of reach. Project managers should watch for signs of scope creep and address them as they arise.
What are some examples of boiling the ocean?
“Boiling the ocean” can show up in different ways across teams and industries, from overambitious strategies to expanding project scopes and misplaced effort. These examples illustrate how it plays out in real-world scenarios.
Here’s what it looks like in practice:
- Example 1: Overambitious strategy rollout. An executive team revises multiple company strategies during a year-end off-site. They aim to rewrite, finalize, and roll out the changes across a 1,000-person organization before the holidays. The timeline is unrealistic given the scale. This leads to rushed execution and poor adoption.
- Example 2: Expanding project scope mid-way. A marketing team starts with a simple two-page website redesign. Midway, the scope expands to include multiple pages and user experiences without adjusting the timeline. The project quickly becomes unmanageable. Deadlines slip as expectations grow.
- Example 3: Overinvesting effort in low-impact tasks. An employee spends excessive time searching for missing receipts for an expense report. Despite low chances of recovery, they continue digging through multiple locations. The effort outweighs the potential benefit. Time is lost on a low-impact task.
Related read
Frequently asked questions about boil the ocean
Here are frequently asked questions around the idiom "boil the ocean".
Q1. Is “boil the ocean” always negative?
Yes, the phrase is typically used to highlight poor planning or unrealistic expectations in projects.
Q2. What causes teams to boil the ocean?
Common causes include unclear goals, lack of prioritization, expanding project requirements, and pressure to deliver large-scale results quickly.
Q3. How is it different from ambition?
Ambition is goal-oriented and strategic, while “boiling the ocean” reflects a lack of focus and feasibility.
Learn how to apply traditional project management principles to plan, execute, and deliver projects with clarity and control.
