A decision that takes nine months is a decision against the people waiting.
We measure ourselves on reach, coverage, and spend. We rarely measure the lag between a need being known and a choice being made. Yet that lag is where much of our impact quietly disappears. A budget reallocation that sits in review through one season arrives in the next. An approval that clears after the road closes was, in practice, a refusal. The people on the other end do not experience our caution as prudence. They experience it as time they did not have.
We have made slowness feel safe.
The honest cause is not indifference. It is an incentive structure that rewards the avoidance of visible error far more than it rewards a timely call. A delayed decision rarely surfaces in an audit. A fast decision that goes wrong does. So we add another sign-off, another committee, another clearance window, and each one is defensible on its own. Stacked together, they produce a system where waiting is the safest career move and no single person ever owns the cost of the wait. We optimized against the wrong risk, and we did it sincerely.
The fix starts with naming that the cost of delay is real and giving it an owner. Every decision of consequence should carry a visible clock and a named decision-maker, so the question shifts from “who approved this” to “who is accountable for the time it took.” When lateness carries a name the way error already does, behavior moves.
Speed and judgment are not opposites.
We often talk as if moving faster means thinking less. The reverse is usually true. The slowest processes we run are not the most rigorous. They are the most diffuse, spreading responsibility so thin that no one can act. Judgment lives in clear ownership, not in the number of hands a decision passes through. One accountable person with good information and a deadline will out-decide a committee with neither, almost every time.
We can build for this, and the moves are practical.
Pre-authorize routine choices so they never reach a committee at all. Agree decision thresholds in advance, when no one is under pressure, so that when the moment comes the answer is already half made. Treat “no decision yet” as a status someone must explain, not a neutral default we drift into. And run the occasional after-action review on decisions that came too late, beside the ones that went wrong, so the organization learns to count both as failures worth preventing.
None of this asks us to be reckless. It asks us to stop treating the clock as someone else’s problem. We are good at managing money and reporting on results. We can be just as good at managing the one resource we keep spending without ever counting it.
So let us treat the speed and quality of our decisions as an outcome we own. For the person waiting, that is exactly what it is.