For over a hundred years, the Gantt chart has been the default tool for planning projects. Many teams open one on day one of every project. The problem is that the way we work has changed significantly, and a tool built on the assumption that a plan set at the start will stay the same until the end is simply flawed.
In this article, we look at what the data says about project delivery, where a detailed schedule fails, what effective teams do instead, and when a Gantt chart still makes sense.
How a Gantt chart actually works
A Gantt chart is simply a project plan drawn on a timeline. Each task gets its own bar showing when it starts, how long it takes, and when it ends. The bars are linked to one another, so if task E can only start after task G is finished, the chart shows it right away. If you want to learn more, we explain what a Gantt chart is here.
This kind of plan works when you know in advance what needs to be done and in what order, and little or nothing changes along the way. That's why Gantt charts work great in construction, manufacturing, or event planning. It's a different story when a project is "alive": the client changes their mind, priorities shift every few days, and half of the tasks only surface during the work.
What the data says about project delivery
According to the 10th State of Project Management report by Wellingtone (March 2026), only 36% of organizations complete projects on time most of the time or always. Many projects are still delayed, even though planning is standard practice.
The scale of the problem is also shown in a study by Bent Flyvbjerg and Alexander Budzier of the University of Oxford, published in Harvard Business Review. They analyzed 1,471 IT projects. The average budget overrun was 27%, but one in six projects turned out to be a "black swan": costs grew by an average of 200%, and the schedule slipped by almost 70%. The key takeaway is that the average hides the risk. A plan based on the average doesn't protect you from rare but extremely costly deviations.
The latest PMI report (Pulse of the Profession 2026) focuses on project complexity. In its summary, the answer to complexity is sensing the situation, experimenting, and course-correcting, not a rigid plan. According to the same summary, where teams handled complexity effectively, 88% of projects were rated as very or extremely successful, compared with 14% in teams that handled it poorly or not at all. PMI also reports that 31% of complex projects fail to deliver the full scope of intended benefits, more than twice the 12% in the 2024 study.
Where a detailed Gantt chart fails
A plan gets outdated faster than you can update it. Every delayed task, change of priority, or new client request invalidates part of the chart, and a single shift can drag the whole chain of dependent bars with it.
Maintaining the schedule becomes a job in itself. Moving bars, re-linking dependencies, and checking dates takes time that could be spent on the project itself. Wellingtone reports that 72% of professionals spend half a day or more every month manually compiling reports, and 44% are dissatisfied with reporting in their PMO. The data doesn't apply only to Gantt charts, but it shows well how much work goes into manually maintained statuses and plans. A team that stops updating the chart has a worse problem than having no schedule at all, because decisions are still made based on outdated data.
Dependencies instead of clarity. Mapping every dependency was the strength of this format. In dynamic projects, however, a Gantt chart doesn't perform as well, because it creates a tangle of links that ultimately nobody understands.
Planning instead of learning. A six-month plan is created when we know the least about the project. Opportunities and problems appear along the way, and a rigid schedule treats them as disruptions rather than information.
What effective teams do instead: layered planning
Instead of mapping out the whole project down to the day, good teams plan on three levels. Each has its own rhythm and doesn't get in the way of the others.
- Once a quarter: where are we headed. You decide what you want to achieve, which deadlines are truly important, and where people and money will go.
- Once a month: does it still make sense. You look at what's going well and what isn't moving forward. You also check whether something new has appeared: a risk or an opportunity that wasn't visible before.
- Every week: what are we doing now. You pick a few top tasks, remove whatever is blocking the team, and notice what went well. If something changes, you adjust the plan for a few days, not for half a year.
This way you always know what matters most and you don't drown in details that will change in two weeks anyway.
The PMI data confirms this, although it doesn't say you should give up planning. According to the report, projects run with some structured approach succeeded in 72% of cases, versus 61% with none. Even so, 35% of professionals used no such approach in their most recent complex project. So it's about a lightweight structure that makes it easy to change the plan.
"What about large projects?"
A common counterargument is that large projects are too complicated to go without a detailed plan.
The solution? Plan only the key points, not every step.
It's enough to put the hard deadlines in your calendar, such as handing a finished stage over to the client, launches, or deliveries of materials from partners. These are the dates that other people actually depend on.
The team arranges everything else between those points as they go. If something goes differently along the way, you only correct the stretch up to the nearest key deadline, instead of redoing the whole plan.
How to move away from rigid schedules
- Plan in three steps, not a year ahead. Set goals for the quarter, check once a month whether they're still relevant, and every week take on only what you're doing right now.
- Track only critical dates. Instead of putting every small task in the plan, mark only the hard deadlines (delivery, launch, stage handovers). Arrange everything else along the way.
- Use a simple app. If moving one deadline takes an hour of clicking, the tool is getting in your way. A change should take a few seconds.
- Talk every week. A short weekly call is enough to catch any problem.
- Leave a buffer for surprises. Never plan your time at 100%. Something always comes up: someone gets sick, a client changes their mind.
- Focus on the result, not a pretty file. The goal is a finished project, not a perfectly drawn chart that will be out of date in two weeks anyway.
When a Gantt chart still makes sense
The claim that "Gantt charts are dead" isn't 100% true. Interest in this tool is still huge: the combined monthly search volume for related phrases reaches as much as 96 thousand. Interestingly, thousands of people a month still search for the basics (what is a gantt chart – 5.6k searches) and for steps on how to create one in popular tools (how to make a gantt chart in excel – 2k searches). This clearly shows that despite its flaws, the Gantt chart remains hugely popular and won't be forgotten anytime soon.
Solutions like this still work great when:
- the scope is fixed and the order of tasks is well known,
- several people or suppliers depend on exact start and end dates,
- you want to show a client a simple overview of the timeline.
A lightweight, milestone-level chart that you can edit in a few minutes is a communication tool. A three-hundred-row schedule with every dependency is a maintenance burden. If you need a lighter version, our guide on how to create a Gantt chart shows step by step how to build one. The Gantt chart template for Google Sheets gives you a ready-made, easy-to-edit version, so that updating it doesn't become a separate project.
Quick summary
Gantt charts were created in a world where plans were meant to stay unchanged. Today plans change, and the teams that succeed are the ones that expect it. Plan the big picture quarterly, adjust monthly, execute weekly, and keep your schedule simple enough that updating it takes minutes, not hours.
Sources
- Wellingtone, The State of Project Management 2026 (10th edition), press release of March 16, 2026: wellingtone.co.uk/publications/state-of-project-management-research/
- B. Flyvbjerg, A. Budzier, Why Your IT Project May Be Riskier Than You Think, Harvard Business Review, September 2011: papers.ssrn.com/abstract=2229735
- PMI, Pulse of the Profession 2026: Driving Success in Complex Projects: pmi.org/learning/thought-leadership/driving-success-in-complex-projects
