Deadlines Set by Hope

Chronic crunch is usually not a delivery failure. It is a commitment process that produces dates unrelated to capacity, repeatedly.

How dates get set badly

Backwards from a desired outcome. The date comes from an event, a promise, or a quarter boundary, and the plan is fitted to it.

Estimates compressed on the way up. Each layer removes contingency to look confident, so the final number bears no relation to the original.

The optimistic case treated as the plan. Estimates describe a range and the best case gets committed.

No allowance for the unplanned, although the unplanned occurs every time.

Previous overruns not incorporated. The same team overran the last four times and the next estimate assumes it will not.

Why it produces burnout specifically

It removes control. The people who will do the work did not set the date, and their estimate was overridden.

It guarantees failure or heroics, and heroics get celebrated, which sets the standard.

It is repeated, so the crunch has no end. One hard push before a launch is survivable; a permanent state of being behind is not.

It damages efficacy. Consistently missing dates, or hitting them only through unsustainable effort, teaches people that competent work is not enough.

An honest commitment process

Estimate as a range, with the assumptions written down.

Commit to the range, or commit to the pessimistic end and deliver early.

Include the unplanned allowance from historical rate, explicitly, as a line rather than as hidden padding.

Record who compressed an estimate and on what basis, which makes the compression visible and therefore rarer.

Track estimate against actual and use the ratio. A team that historically takes 1.4 times its estimate is not bad at estimating; it has a known multiplier that should be applied.

Protecting the trough

The distinction that determines whether intensity is sustainable.

Intense periods are fine when followed by genuine recovery.

Recovery means reduced load, not just the absence of a deadline. A team that finishes a launch and starts the next the following Monday has not recovered.

Plan the trough into the schedule as an explicit period, or it will not happen.

Protect it when the next urgent thing arrives, which is the hard part and the entire point.

What to say when the date is fixed

Sometimes the date genuinely cannot move — a regulatory deadline, a contractual date, an external event.

Say so, and name it as fixed.

Then flex something else: scope, quality bar, or added capacity. If nothing can flex, the plan is a hope.

Acknowledge the cost rather than pretending there is none. People will do a hard push for a real reason, once, if it is named as such and if the recovery follows.

What they will not sustain is being told every quarter that this one is exceptional.

The signal to watch

How often the exceptional push happens.

Twice a year is a demanding job. Every month is the operating model, and calling it exceptional is the thing that makes it corrosive rather than merely hard.

Tracking the estimate multiplier

An objective measure that replaces arguments about whether a team estimates badly.

Record estimate and actual for every piece of work of meaningful size.

Compute the ratio, by team, over a period.

A team that consistently runs at 1.4 times its estimate is not bad at estimating. It has a known and stable multiplier, and applying it produces accurate plans.

Apply the multiplier openly rather than asking people to estimate better.

Watch the ratio over time. Rising indicates growing interruption, unplanned work or complexity; falling indicates the opposite.

This also removes the incentive to pad estimates, since the correction is applied transparently rather than being something individuals have to smuggle in.

Planning the trough

Recovery does not happen unless it is scheduled and defended.

After an intense period, plan a reduced-load period, explicitly, in the same plan.

Define what reduced means, or it will be interpreted as normal.

Say no to the next urgent thing during it, which is the entire difficulty.

Where the trough is repeatedly consumed, the operating model is continuous intensity and should be described that way.

A team that has not had a trough in a year is not in a busy period. It is in its normal state, and the language should change to match.