Buying Back Time: A Practical Guide to Crashing and Fast-Tracking
Every project manager eventually faces the same uncomfortable conversation: the deadline has not moved, but the work has fallen behind. In 2021 this was painfully common — material deliveries slipped, key people were out sick, and approvals that used to take a day took a week. When the calendar will not budge, you reach for schedule compression. Two techniques do the job, and they are not interchangeable.
Start with the critical path
Schedule compression only works on the critical path — the longest chain of dependent activities that determines the project's finish date. Compressing a task that is not on the critical path buys you nothing; the project still ends when the critical path ends. So before you do anything, confirm which activities are actually driving the end date. Compress the wrong tasks and you will spend money and effort to shorten a path that has slack to spare.
Crashing: add resources to shorten duration
Crashing means adding resources to critical-path activities to finish them faster — more people, overtime, a second shift, or a faster (and usually pricier) supplier. The logic is simple: throw effort at the bottleneck. The catch is that crashing almost always costs more and often delivers diminishing returns. The tenth person on a task may add far less than the second did, and beyond a point you hit coordination overhead — the famous problem that adding people to a late task can make it later.
Find the cheapest time to buy. Identify the critical-path activities where adding resources shortens duration for the least added cost per day saved. Crash those first.
Compress in small steps. Shorten a little, re-check the critical path, and repeat. Compressing one path can make a different path critical, changing where the next dollar should go.
Watch the budget and the people. Overtime and rush fees add up, and burned-out teams make errors. Crashing trades money and risk for time.
Fast-tracking: overlap work that was sequential
Fast-tracking means performing activities in parallel that were planned to run one after another. You start the next phase before the previous one is fully complete — beginning construction drawings before the design is fully signed off, for instance. Fast-tracking usually does not add cost, which makes it attractive, but it adds risk. If the earlier activity changes, the overlapping work may have to be redone. You are betting that the upstream task is stable enough to build on before it finishes.
Choose fast-tracking when the dependency is partly discretionary — the overlap is uncomfortable but not physically impossible.
Choose crashing when activities are hard-linked and cannot overlap, but more resources genuinely move the work faster.
Expect fast-tracking to increase rework risk and crashing to increase cost; neither is free.
Re-run the critical path after every change — compression shifts where the constraints live.
Decide deliberately, not in a panic
The worst compression decisions get made in a hurry, the morning after someone notices the slip. Slow down long enough to ask: which path drives the date, can these tasks safely overlap, and do we have money or risk tolerance to spend? Often the right answer is a blend — fast-track where the risk is acceptable, crash the one or two activities where it is not. Document what you traded away, because a compressed schedule is a promise with conditions, and stakeholders deserve to know them.
When a critical deadline is at risk and the trade-offs are not obvious, XNM's program & project delivery advisory can help you compress the schedule without quietly multiplying your cost or risk.