In my experience on projects across 14 countries, delays almost never arise from an unforeseeable event. They arise from recurring causes, known in advance, that no one addresses because it would require an uncomfortable conversation with the sponsor. Here are the five most frequent causes and the countermeasures that actually work.
1. Non-validated optimistic estimation. The team estimates tasks based on the ideal concentrated work time, ignoring meetings, context switching and interruptions. The practical fix: apply a 20-30% contingency factor to each estimate based on real historical team data, not on an arbitrary percentage from a manual. If you have no historical data, start collecting it from the current project — it is the only way to calibrate future estimates.
2. Unmapped external dependencies. The most common delay comes from a supplier, another team or an external approval that no one tracked as a critical dependency. Countermeasure: every project must have a dependency log separate from the main plan, with a named owner for each external dependency and follow-up date, reviewed weekly — not just at the milestone when the dependency becomes blocking.
3. Silent scope creep. Small 'while we're at it' requests accumulate without ever passing through a formal change request process. Every scope modification, however small, must pass through a mini change control: impact on time, cost, and who approves. If this process seems too bureaucratic for small modifications, the problem is not the process — it is that the small modifications are not really small in aggregate.
4. Absence of a real critical path. Many project plans list activities but do not identify which are actually on the critical path. Result: the team optimizes non-critical activities while those that really determine the end date slip without anyone noticing until late. Use a network diagram (even a simple one) to identify the real critical path and monitor it weekly, not just at milestones.
5. Reactive rather than proactive communication. The sponsor discovers problems when they are already critical, not when there were still options to manage them. The countermeasure is a structured weekly status report with a fixed format: status (green/yellow/red), emerging risks, decisions needed within the next 7 days. The golden rule: if a risk turns yellow, it must be communicated that week, not when it turns red.
6. The method to halve delays. Applying these five countermeasures together on comparable projects, the typical observed delay reduction is between 40% and 60% — not because it eliminates uncertainty, but because it makes it visible and manageable before it becomes a full-blown problem.
FAQ. Do these techniques work for small projects (under 3 months)? Yes, in simplified form: even a dependency log on a shared sheet and a 5-line weekly status report make a measurable difference. Do you need dedicated software? No, the method works with well-structured Excel/Google Sheets. The tool matters less than the update discipline.
If your projects systematically slip and you want to understand which of the five causes is weighing most in your specific case, let us book a 30-minute diagnostic call.
