Decision fitness
Decision latency
Also known as: Decision latency law
How long a decision takes shapes a project's outcome more than the quality of the decision itself.
From Dancing with Change & Fluidity: the author draws on Standish Group research to make a counterintuitive claim, it is not the quality of a decision but the time it takes to make it that, in most cases, decides whether a project succeeds. A project with a one-hour average decision time tends to meet its estimates, while a five-hour average roughly doubles both timeline and cost.
The book returns to this point both for the power of fast group decisions and in its closing chapter for board members: good, slow decisions are, in practice, often more damaging than fast, good-enough ones. That is not an argument for rushed choices, but for decision frameworks (such as RAPID) that make clear in advance who is responsible for what, so a team does not get stuck in endless discussion.
For fit and fast organizing, decision latency is therefore a practical yardstick: an organization that wants to genuinely improve its decision speed looks not only at the outcome of a decision, but above all at how much time passes between the question and the answer.
Discussions about this
Have a question about this topic, or an experience to share? Start a discussion; it stays linked to this page.
Comments on this concept
No comments yet
Be the first to comment.
Want to comment? Log in or join for free.