Here is a number that should concern every project manager: nearly 80% of projects fail to deliver on time, within budget, or to the agreed scope.
That is not a niche problem. It is the norm. And the reasons are almost always the same – poor planning, unrealistic promises, weak execution on the ground, and events that nobody saw coming.
This article covers all four. By the end, you will have a clear picture of what goes wrong on projects and exactly what a project manager can do to prevent it.
Why Most Projects Run Into Problems
Research shows that 80% of projects experience cost overruns, time slippages, or both. The causes are almost always predictable – and preventable.
Projects fail for a surprisingly small set of reasons. Here are the most common ones:
- Scope creep: requirements expand after sign-off, and nobody pushes back. What started as a 3-month project quietly becomes a 6-month one.
- Poor planning and estimation: timelines are set optimistically, risks are ignored, and assumptions are never documented.
- Key people leaving mid-project: when the person who knows the most leaves, the project goes with them if knowledge hasn’t been shared.
- Weak stakeholder management: clients change requirements midway; sponsors withdraw support; teams lose clarity on objectives.
- Poor communication: problems exist but nobody tells the right person until it’s too late to fix them.
- Flawed execution: the plan is solid, but the on-the-ground implementation fails to match it.
The table below maps each common failure to a practical PM response:
| Failure Cause | Why It Happens | What the PM Can Do |
|---|---|---|
| Scope creep | Requirements keep expanding after sign-off | Lock scope early; enforce formal change control |
| Unrealistic timelines | Pressure to win the deal leads to overpromising | Use historical data; build in contingency buffers |
| Key resource loss | Critical team members quit mid-project | Cross-train; document knowledge; reduce person dependence |
| Poor communication | Stakeholders not kept informed; team misaligned | Build a communication plan; hold regular structured reviews |
| Weak execution | Good plan, poor ground-level follow-through | Stay close to implementation; conduct last-mile checks |
| External disruptions | Market shifts, political changes, tech failures | Prepare risk matrix; build contingency plans |
Notice that most of these failures are not caused by bad luck. They are caused by things the project manager could have anticipated – and acted on earlier.
The Time and Cost Overrun Trap
Of all the things that go wrong on projects, time and cost overruns are the most visible – and the most damaging to a project manager’s credibility.
The root cause is almost always the same: overpromising at the start.
Why Project Managers Overpromise
The pressure to win a contract, impress a sponsor, or keep a client happy pushes project managers to commit to timelines and budgets that are too tight from day one. It feels like the right thing to do in the moment. It rarely ends well.
The triple constraint – scope, time, and cost – means you cannot change one without affecting the others. Clients who expand scope expect the same timeline. Sponsors who cut budgets expect the same output. Something has to give, and it is usually quality or delivery date.
What Project Managers Can Do Instead
- Use historical data. If similar projects took 6 months, plan for 6 months – not 4. Past performance is the most reliable estimating tool you have.
- Build in contingency buffers. Add 10–20% to time and cost estimates as a buffer for the unexpected. Never reveal the full buffer upfront – it will be consumed immediately.
- Fix the pricing model. Time-and-material contracts give clients flexibility but expose projects to scope creep. Fixed-price contracts protect the timeline but require tightly defined scope. Choose based on how well the requirements are defined.
- Use technology for early warning. Project management tools can flag schedule slippages the moment they begin – not three months later when it’s too late.
- Enforce change control. Every scope change must go through a formal process – documented, assessed for impact, approved or rejected. No informal “just add this one thing”.
The Last Mile Problem – Why Great Planners Still Fail
Here is a pattern that repeats itself across industries: the project plan is excellent, the strategy is right, the stakeholders are aligned – and then the project still fails.
The failure happens at the last mile. The gap between planning and execution.
What Is Last Mile Connectivity?
Last mile connectivity is a term borrowed from logistics – it refers to the final leg of delivery, where goods travel from a distribution hub to the customer’s door. In project management, it means the same thing: the final connection between what was planned in the boardroom and what actually happens on the ground.
Most project managers are good at planning. Far fewer are good at staying connected to implementation.
Where Last Mile Failures Happen
- The implementation team does not fully understand the project’s purpose: they execute tasks without connecting them to the overall objective.
- The project manager adopts a hands-off approach: sitting in an office reviewing reports while the real work is left entirely to subordinates.
- Ground-level feedback is not reaching decision-makers: problems are visible to the people doing the work, but nobody is asking them.
- Implementation experience is missing from the project team: planners plan, but nobody on the team has done this kind of implementation before.
What Project Managers Must Do
- Stay close to execution. Regular site visits, daily standups, or hands-on reviews during critical phases. Know what is actually happening, not just what the reports say.
- Build feedback loops from the ground up. Ask implementation team members directly – what is working, what is not, what is being skipped. Make it safe for people to flag problems early.
- Include implementation expertise in the team. Every project team should have at least one person who has done this kind of work before – not just planned it.
- Conduct last-mile reviews. As the project approaches completion, specifically check whether the ground-level delivery matches the original objectives – not just the task list.
- Do not confuse activity with progress. A team that is busy is not necessarily a team that is delivering. Track outputs, not just effort.
Dealing With Disruptions — Inside and Outside the Project
Even a well-planned, well-executed project can be derailed by events that nobody saw coming. Disruptions are not a sign of poor project management – but how the PM responds to them is.
Types of Disruptions Project Managers Face
Disruptions come in two forms – internal and external:
- Internal disruptions – a key team member resigns, a vendor fails to deliver, the client changes requirements, internal politics shifts priorities, or funding is cut.
- External disruptions – economic downturns, regulatory changes, political instability, technology shifts, or events like a pandemic that change the entire operating context overnight.
The most useful framework for thinking about disruptions is the distinction between Known Unknowns and Unknown Unknowns:
| Known Unknowns | Unknown Unknowns | |
|---|---|---|
| Definition | Risks you know exist but cannot fully predict | Events you had no way of anticipating |
| Examples | Key resource may leave; vendor may delay; scope may change | Global pandemic; sudden regulatory ban; technology becoming obsolete overnight |
| PM approach | Identify, assess probability and impact, build response plans | Build resilience, maintain contingency budget, stay adaptable |
| Can you plan for it? | Yes – risk register and mitigation strategies | Partially – scenario planning and crisis response protocols |
How to Build Disruption Resilience
- Prepare a risk matrix before the project begins. List every risk you can think of, assess its probability and impact, and assign a response owner. Review it monthly, not just at kickoff.
- Maintain a contingency budget. Typically 10–15% of total project cost, held in reserve for unexpected events. Never spend it on scope additions.
- Use data to spot early warning signs. Many disruptions – vendor delays, team burnout, budget drift – show signals weeks before they become crises. Train yourself to look for them.
- Plan for the human side of disruptions. When key people leave, knowledge walks out with them. Document critical processes, cross-train team members, and reduce single points of failure.
- Accept what you cannot control. Unknown unknowns cannot be fully planned for. The PM’s job is to stay calm, assess the situation quickly, make decisions with incomplete information, and keep the team moving.
The best project managers are not the ones who prevent all disruptions. They are the ones who see them coming earlier than others – and respond faster.
The Bottom Line — What the Best Project Managers Do Differently
The difference between projects that succeed and those that fail is rarely about having more resources or better technology. It comes down to how the project manager handles four things:
- They prevent internal failures: by planning carefully, locking scope early, and managing stakeholders proactively.
- They avoid the overrun trap: by estimating honestly, building in buffers, and enforcing change control.
- They close the last mile gap: by staying close to execution, building ground-up feedback loops, and not confusing a good plan with a successful delivery.
- They build disruption resilience: by thinking ahead, preparing contingency plans, and responding quickly when the unexpected happens.
None of this is easy. But all of it is learnable. And the project managers who do these four things consistently are the ones whose projects actually get delivered.
