When the Critical Path Hides: Lessons from a Stalled Recovery Project
In early 2021, a mid-sized public agency restarted a facility upgrade that had been paused for most of the previous year. The team was relieved to be moving again, and the Gantt chart looked reassuring: dozens of bars, most of them green, a finish date that satisfied the steering committee. Two months in, the project was three weeks late and no one could explain why. The bars that turned red were never the ones anyone worried about.
The names and details below are anonymized, but the pattern is common, especially when work resumes after a disruption. The schedule had grown busy, and the critical path, the chain of activities that actually determines the finish date, had quietly slipped out of view.
What the team got wrong
The project manager had inherited the plan from a predecessor and trusted the software to flag what mattered. But float had been masked by manual date constraints, several tasks carried 'must start on' dates left over from the original pre-pandemic plan, and a few key dependencies had never been linked at all. The tool was calculating a critical path, but not the real one.
Hard constraints everywhere. Imposed start and finish dates overrode the logic, so the network could not flex. The schedule showed slack that did not exist.
Missing dependencies. A long-lead mechanical order was sitting as an island task with no successor links, so its slippage never propagated into the finish date.
Watching the wrong tasks. Status meetings focused on visible, on-site work because it was easy to see, while the true driver, a supplier delivery, lived in a spreadsheet no one reviewed weekly.
How they found the path again
Recovery started with a clean network. The team stripped out every constraint that was not a genuine external commitment, relinked the logic so each activity had a real predecessor and successor, and re-ran the forward and backward pass. The longest chain through the network, now driven by the mechanical delivery and its installation sequence, was the critical path all along. With remote and hybrid working still the norm, they also agreed that whoever owned a critical activity would report on it directly each week, rather than relying on a single coordinator to chase everything.
Build the network on logic first, then add only the date constraints you can defend.
Treat zero-float chains as the project's spine and review them every cycle, not just when they go red.
Protect the path with buffer where you can, and escalate the moment a critical task moves, not after it has slipped.
Re-baseline deliberately after a major disruption so 'green' means current reality, not last year's plan.
Within a month the project had a defensible finish date again. Nothing about the work had changed; what changed was that the team could finally see which work governed the outcome and which work simply filled the chart.
If you are restarting a delayed project and need confidence that your schedule reflects reality, XNM's program & project delivery advisory can help you find and protect the path that matters.