What a Common Cold Taught Me About Project Crashing

There is a strange irony in trying to finish a construction project on time.

The closer you get to handover, the more everything seems to happen at once.

That is where we are with the Ndagani Modern Market.

We are in what project managers call project crashing: adding resources, working longer hours and pushing activities harder because the original programme is no longer good enough. The handover date is getting close, and suddenly every unfinished item looks like it has a personal relationship with the deadline.

Then I caught a common cold.

Nothing dramatic. No hospital admission. No medical emergency. Just the ordinary misery of a blocked nose, a sore throat, a little coughing and that general feeling that your body has decided to reduce your productivity by 60 percent.

But it reminded me of something I should probably have known already.

A project can crash for the same reason a human being can.

You can keep pushing.

You can add more people.

You can work longer hours.

You can demand faster decisions.

But there is a point where the system simply needs to recover.

The Last Mile Is Expensive

Construction has taught me that the last few percent of a project can consume a disproportionate amount of energy.

The major structure may be complete. The walls are standing. The roof is on. Most of the work looks finished.

Then come the small things.

A door that needs adjustment.

A fitting that hasn't arrived.

A section of painting that needs another coat.

A drainage issue.

Cleaning.

Testing.

Corrections.

And suddenly the project that looked 95 percent complete has acquired another hundred things that need attention.

It is much like having a cold.

You may feel that you are almost well, but that last cough has decided it has taken permanent residence.

Crashing Has a Cost

When we crash a project, we are essentially buying time.

We bring in additional labour.

We extend working hours.

We move resources from one activity to another.

We make decisions faster.

Sometimes we spend more money to protect the deadline.

There is nothing inherently wrong with that.

A deadline is a deadline.

But the lesson from my cold was simple: more pressure does not always produce more output.

At some point, tired people make mistakes.

And mistakes near the end of a project can be particularly expensive because there is little time left to correct them.

You can save two days by rushing a task and then lose five days correcting what was done badly.

That is not crashing.

That is simply crashing into another problem.

The Market Has Its Own Deadline

At Ndagani, we are now in that uncomfortable space between almost there and not there yet.

The temptation is to look at the calendar and tell everyone to run faster.

But the better question is:

What absolutely has to be done, and what is the smartest way to get it done?

That means prioritising the critical path, removing bottlenecks, making decisions quickly and putting resources where they actually change the completion date.

It also means resisting the temptation to confuse activity with progress.

A site can be extremely busy and still not be getting closer to handover.

Anyone who has spent time on a construction site knows this.

You can have twenty people running around and somehow achieve less than five focused people would have achieved.

Perhaps the Cold Was Useful

My common cold will eventually disappear.

So will the pressure of this project.

The market will be handed over, people will occupy their stalls, and most of the things that currently seem urgent will become memories.

That is another lesson construction keeps teaching me.

Deadlines matter.

Budgets matter.

Quality matters.

But so does knowing when pushing harder is actually helping and when it is simply making everybody tired.

As we push towards handover at Ndagani, I am reminded that the final stretch requires urgency, but it also requires judgment.

You don't finish a project simply by working harder.

You finish it by knowing what needs to be done, what can wait, where to put the resources and when to stop creating new problems while trying to solve the old ones.

And, occasionally, by accepting that the project manager with a blocked nose may need a cup of tea and twenty minutes of silence.