Decision latency: The performance cost nobody budgets
Ask leaders in African banks and service organizations what frustrates them most, and one answer returns with remarkable consistency: decisions take longer than they should. Not the big strategic calls – those get attention, sponsors, deadlines. The everyday ones. A pricing exception. A hiring approval. A response to a client escalation. Each individually small, each individually explainable, and together forming one of the most expensive line items no budget ever shows.
The cost is real even though it is rarely counted. While a decision waits, work waits with it: client responses slip, dependent tasks idle, and capable people spend their energy managing the waiting – following up, escalating, re-explaining context to whoever the decision has moved to next. In markets where operating conditions are already demanding, that lost speed is not an inconvenience. It is competitive position, leaking quietly, every week.
What decision latency actually signals
The instinctive explanations blame individuals: a risk-averse manager, an overloaded executive, a culture of caution. Sometimes those are real. But when delay shows up across an organization – in different departments, under different managers – it stops being a story about persons and becomes a story about conditions. Decision latency is usually the visible symptom of a small set of invisible causes: unclear decision rights, so items travel upward by default because nobody is certain they may decide; leaders operating under such load that their queue, not their judgment, sets the pace; communication practices that deliver decisions without the context that lets the next level act on them; and the quiet fear of deciding wrongly in environments where mistakes are remembered longer than delays.
Notice what these causes have in common: none of them is a knowledge problem. The people involved usually know what the right decision is. The conditions around the decision are what slow it down – and this is why decision latency belongs to the Intention vs Experience Gap. Leadership intends empowerment and speed; the daily experience of work delivers queues.
Why the usual responses fall short
Organizations typically respond with structure or exhortation: a new approval matrix, a delegation-of-authority document, a town hall about ownership. These are not wrong, but they address the paper version of the problem. An approval matrix does not change what happens when a manager under pressure faces an ambiguous case at 5 p.m.; a speech about empowerment does not change the memory of what happened to the last person who decided boldly and missed. Decision speed is a capability exercised under real conditions – and capabilities under conditions are exactly what isolated interventions fail to change.
What changes it
The work that actually moves decision speed starts by making the pattern visible: where decisions stall, at which level, and what the people involved experience at those moments – which is precisely what a structured diagnostic across the whole organization surfaces. From there, the levers are specific: leaders develop the practices of deciding and delegating under pressure; teams build the clarity and trust that let decisions stay where they belong; and the organization’s workload realities are adjusted so that the people expected to decide have the capacity to. None of these levers works alone. Together, applied in live work rather than workshop settings, they do – and the change is measurable, in the operational signals and in the experience of the people who no longer wait.
mHub helps organizations close the gap between what leadership intends and what their people experience – through the structured implementation of our Workplace Performance System.