You can do everything right and still miss, because you forgot the one thing waiting by the door.
Almost 70 years later, most projects still get this wrong.
Oxford's Bent Flyvbjerg has built the largest database of its kind: more than 16,000 projects across 136 countries. Only 8.5% finished on time and on budget. Just 0.5% also delivered what they promised.
Read that again. More than 9 in 10 run over cost, over schedule, or both.
Here is the part that should bother every leader.
The cure has existed since 1957.
That year, James Kelley and Morgan Walker were building a scheduling system for chemical plants and noticed something simple. In any project, exactly one chain of dependent tasks sets the shortest possible finish date. Delay a single task on that chain, and the whole project slips.
They called it the Critical Path Method.
Think of leaving the house. The alarm, the shirt, the bag, the shoes can all shuffle around. Forget the keys, and none of the rest matters. You are not going anywhere.
That is a critical path. One late link, and the whole thing is late.
Now look at the Sydney Opera House.
Estimated in 1957 at AU$7 million. It opened in 1973, ten years late, at AU$102 million. PMI puts the overrun at 1,357%, still the largest proportional cost increase for any building on record.
The method that could have surfaced that risk had been public for 16 years when work began.
So why do leaders with powerful software keep repeating the mistake?
Because the critical path is uncomfortable. It forces honest durations, mapped dependencies, and a public list of the tasks that cannot slip. Most teams skip all of that and drop dates onto a Gantt chart instead.
A Gantt chart without a critical path is a wish list with a calendar.
So before your next deadline, ask one question.
Can your team name its critical path? Yes or no?
