Compression is how you buy a shorter duration with money, risk, or both. It is not a pep talk and it is not 'the team will try harder.' If the date must move in, name the technique, name the path, and name what you are spending.
Crashing: pay to shorten the critical path
Crashing adds resources — people, overtime, a second vendor shift, a faster machine — to critical activities to cut duration. You spend cost to buy calendar time. Do it only on the current critical path, and only on work that actually shortens when you add hands. Plot crash cost per day saved. Pick the cheapest days first. Stop when the next day costs more than the date is worth.
Overtime is the crash people reach for because it needs no requisition. It works for a week. After that you are buying defects and slower thinking at a premium rate. If the business case for the date cannot survive paying for an extra person or a descoped increment, it cannot survive a month of tired heroes either.
Brooks's observation still applies: adding people to late work can make it later while they ramp and while communication paths multiply. Crash early, on separable work, with a named onboarding plan. Crashing in the last fortnight is often just a more expensive way to miss the same milestone.
Fast-tracking: overlap work that wanted to be sequential
Fast-tracking changes logic: you start a successor before its predecessor is finished — SS instead of FS, or a lead on an FS link. Design is still moving while build starts; training materials are written against a product that is not stable. You spend risk and rework to buy time. The date may improve. The defect log will have opinions.
Fast-track only where a wrong assumption is cheap to reverse. Overlapping two vendor contracts before the interface is signed is how you pay twice. Overlapping test-case design with a stable API draft is often fine. Write the assumption you are violating. If you cannot, you are not fast-tracking. You are gambling and calling it a schedule strategy.
Rework is the silent duration you did not put on the Gantt. A 30 percent chance of a two-week redo is not 'absorbed by the team.' Put a buffer or a decision gate on the overlap. Fast-tracking without a gate is how overlapping work becomes overlapping failure.
The quality and risk cost — pay it on purpose
Every compression trades against quality, cost, or residual risk. Crashing can dilute review, split ownership, and create 'who changed that' defects. Fast-tracking can build on a design that will move. Neither is immoral. Pretending the trade is free is. Put the residual risk in the register with a trigger: defect rate, interface churn, overtime hours.
Do not compress a path that is not critical, and do not compress to hide a scope conversation. If the date is sacred, something else is not — usually scope. A thinner Increment on the original date is often cheaper than a fully fantasised scope delivered by crash and prayer. Offer both options. Let the sponsor spend the money or the features.
Record the decision. When someone later asks why quality dipped or why the second path is now critical, 'we had to hit the date' is not an answer. 'We crashed activities 14 and 22 at $X per day, accepted rework risk on the API overlap, and rejected a scope cut on 3 May' is an answer. Compression without a paper trail is just a rumour that the plan got tighter.
Summary & next steps
Crash: add cost to shorten critical work that actually divides. Fast-track: overlap sequential work and pay in risk and rework. Only the current critical path can move the date. Name the trade, log the residual risk, and write the decision down.
Next: baselining the schedule — freeze the thing you have just been tempted to keep editing, then put change control on the door.