One of the most common mistakes we see at the start of a project is underestimating its scope, especially when it’s planned as a series of isolated work packages. Projects incorporating a ‘waterfall’ approach, where each phase relies on the one before it, can easily stall at a particular stage when dependencies are not managed.
An individual project manager is unlikely to be aware of the full implications of delays across the various workstreams they are overseeing. To run large-scale programmes effectively, someone in the organisation needs to review each project as part of the broader portfolio. This holistic perspective helps leaders spot overlapping timelines and interdependencies across workstreams and departments, reducing the risk of bottlenecks and delays.
For example, in one project we encountered, a high-stakes initiative planned in isolation hit delays, setting off a domino effect that impacted other key programmes. We helped the project team step back, take stock of parallel projects, spot the dependencies, and rework their plans.
By shifting away from a rigid, single-track approach, they managed to keep the workflow steady and reduce the risk of setbacks.