Delay Has a Price
What does waiting cost, and who is counting it?
The idea
Postponing a decision is itself a decision, and it carries a cost that is rarely counted.
In the real world
Waiting a quarter to hire means a quarter of the work not done.
Going deeper
Not deciding is a decision, and it carries costs that are spread out and unattributed while the risks of deciding are concentrated and visible. That asymmetry is why deferral feels safe.
Deferring a hire costs a quarter of that role's output, the compounding delay to everything downstream, and the candidates who take other offers. None of it appears on any ledger, and nobody is ever blamed for it, whereas a bad hire is a specific identifiable error. Writing down the monthly cost of waiting puts the two on the same footing.
Where it stops applying
Delay genuinely reduces uncertainty when meaningful information is arriving. The cost is only wasted where waiting is not actually buying anything.
Why it matters
It puts not deciding on the same ledger as deciding, instead of treating it as the safe default.
Try this today
For one deferred decision, write what each further month costs.
Test yourself
A team defers a hiring decision for a quarter to gather more information. What is on the cost side of that choice?
Show the answer
A quarter of the output that role would have produced, plus the compounding delay to everything downstream, plus candidates who take other jobs. Deferral feels free because its costs are spread and unattributed, while the risk of deciding is concentrated and visible.
Learn this in the feed Answering from memory, then again days later, is what makes it stick.