Termites, Not Tornadoes: How Tiny Delays Kill Big Programmes

We all know that there are many reasons why large-scale programmes fail.

If you have ever attended a post implementation review (or similar) you’ll know that the list is a long one, but in this article we’re focusing on the effect of tiny events that are “hidden in plain sight”.

The quieter, more insidious threats: the small delays and minor misalignments that build up over time. These issues are easy to ignore in the moment, but devasting in the long run.

Programme delivery failure is rarely the result of a single catastrophic event. More often, it’s the accumulation of tiny, seemingly insignificant delays that chip away at progress until the programme is beyond recovery. As Frederick P. Brooks Jr. put it in The Mythical Man-Month, projects are more often derailed by termites rather than by tornadoes.

The Digital Age’s Role in Enabling Procrastination

One of the paradoxes of modern programme management is that while technology has made collaboration easier, it has also made progress avoidance effortless. When I started my career in programming 40 years ago email didn’t exist. To pass work on to someone else you had to write down the detail, pass it to a secretary to type up into an “internal memo”, post it in the internal mail system and wait 2 days for the reply. You know what – it was easier and clearly more efficient just to do the work yourself.

In the world as we know it now, a difficult decision can be pushed back with a simple email. A complex deliverable can be re-assigned with a task management update. Rather than resolving issues, it is possible for teams to shuffle work around relentlessly.

This is especially true in remote and hybrid working environments. When people aren’t physically present it may be harder to resolve issues in real time. The old-school approach—where problems were solved in the room—can be replaced by digital paper trails that create the illusion of meaningful activity without any real progress.

Why Tiny Delays Matter More Than Big Disruptions

If a programme suffered a major setback—a system outage, a regulatory change, or a key supplier going bust there would be immediate action. A crisis would be declared, resources would be mobilised, and a mitigation plan executed. But small delays don’t necessarily create the required urgency – they may not even be visible. They are easy to dismiss, easy to accommodate, and easy to normalise.

Over time however, they introduce inefficiencies and unplanned workarounds. Meetings become exercises in re-planning rather than execution. Teams operate in a constant state of catch-up. Confidence erodes, and soon, the programme can become a self-perpetuating cycle of delay management rather than delivery.

The Illusion of Progress

Modern project management tools give us unprecedented visibility and flexibility. Tasks are tracked in Gantt charts, dependencies are mapped out in intricate detail, and workstreams are shifted around at the click of a button. But this very ease of adjustment has led to a dangerous side effect: the illusion that delays are harmless. When a task is moved a day here, a few days there, the impact seems negligible—until it isn’t.

In reality, these micro-delays compound because you are unlikely to have planned to a sufficient level to see all the implications . A one-day delay on a critical dependency might cause a two-day delay in the next phase, which then cascades down the line. Before long, the schedule is irreversibly off track. And because each delay felt insignificant at the time, no single moment triggers an alarm until it’s too late.

How to stop the Termites

Like most of life’s complex problems, you can’t kill off all the termites with simple solutions. However if I had to choose my top 3 “termite swatting” steps they would include;

Treating small, seemingly insignificant delays appropriately.

I once started a new job working for a Programme Director who I had never worked for before. I had my plan, but was used to building a plan with target dates, then effectively ignoring anything not on the critical path. Actually in those days more like ignoring the whole plan. I presented my weekly update and had the dressing down of my professional life when my lack of care for any slippage shone through. A life lesson that I have always been grateful for because that project became the first project I delivered ‘on time and within budget’. It taught me that any delay, no matter how minor, should be scrutinised for its downstream impact. I learnt that success, at least in part results from creating a culture where even a one-day minor slip is viewed as something to be avoided, flagged and resolved proactively – preferably in real-time.

Creating urgency without panic.

Creating a sense of urgency in project delivery is crucial—without it, momentum stalls, deadlines slip, and priorities drift. However, urgency must be managed carefully to avoid panic, which leads to poor decision-making and burnout. The key is clear communication, structured planning, and proactive leadership. A cultural or mindset shift has to be built within the team from “we’ll move it” to “we’ll solve it”. When teams understand the importance of timely action without feeling overwhelmed, they stay focused, motivated, and in control. Not every delay needs to trigger a crisis, but reinforce a heightened awareness of how small slips compound over time.

Encouraging the limiting of unnecessary work shifting.

Just because a task could be completed elsewhere, or can be moved easily doesn’t mean that it should be. While work should always be performed or signed off by those responsible for it, the reality of modern project delivery means that sometimes, it simply makes sense for tasks to be drafted or completed elsewhere if resources allow. Efficiency shouldn’t be sacrificed against the reasonable need for rigid role definitions. Develop a delivery culture based on the team’s pride in continually hitting dates through a combination of collaboration and pragmatism.

Conclusion

Programme failures are rarely the result of a single dramatic event. More often, they stem from the slow, almost invisible accumulation of small, unchecked delays. The termites of minor setbacks eat away at timelines, resources, and confidence until the programme collapses under its own inefficiency.

In a world where work can be effortlessly moved with a few clicks, the challenge isn’t managing change – it’s ensuring that work actually gets done. And that means recognising the danger of tiny delays before they become insurmountable obstacles.

Want to ensure your next project starts on a solid project foundation that delivers results? Get in touch to create an environment for success.