The decision was not wrong. It was just three weeks late. And three weeks late, in most competitive markets, is indistinguishable from wrong.

The Slowness Tax

There is a metric that almost no organisation formally tracks but almost every organisation pays: decision latency. It is the time that elapses between when a decision could be made and when it actually is made. Every day of decision latency has a cost. Projects that cannot start. Contracts that cannot be executed. Vendors who grow impatient. Opportunities that expire while the relevant document sits in an inbox waiting for a sign-off that has not been prompted.

West Monroe’s 2026 Speed Wins research, which surveyed 214 C-suite executives and 1,000 managers at US companies with at least 250 million dollars in annual revenue, found that nearly three in four leaders estimate their organisations lose up to 5 percent of annual revenue due to slow decision-making and delayed execution. The researchers named this the Slowness Tax: a measurable, recurring revenue drain caused not by wrong decisions but by slow ones.

The same research found that the largest contributors to decision slowness are not technology gaps or skills shortages, as executives tend to assume. They are excessive approval layers, unclear decision rights, and risk-averse leadership behaviours. These are process architecture problems, not capability problems. The people involved are capable of making the decision quickly. The system makes it slow.

How Approval Layers Multiply as Organisations Grow

The approval structures that create bottlenecks in growing businesses are almost never designed to be slow. They are designed for control, and control is a legitimate objective. The problem is that control structures built for a team of twenty do not scale to a team of two hundred without modification, and modification rarely happens proactively. It happens reactively, after the slowness has already become visible and damaging.

As organisations grow, three things happen to approval processes simultaneously. The volume of decisions increases faster than the number of approvers. The decisions become more diverse, requiring approvers who are further from the original work to make judgements about it. And the approval chain grows longer as each layer of new management adds a new sign-off requirement that nobody has removed from a previous layer.

A growing business does not usually decide to create an approval bottleneck. It creates one by not deciding to remove the approval layers that stop being appropriate as the organisation scales.

The Commercial Cost Nobody Has Calculated

According to analysis by Creative Bits on the economics of approval bottlenecks, knowledge workers in a typical mid-sized organisation waste between 30 and 40 percent of their time waiting for decisions or clarifications instead of executing work. At a loaded cost of 60 dollars per hour and 100 knowledge workers, 30 minutes of daily approval-related waiting costs the organisation more than 3,000 dollars per day. Across a working year, that exceeds 750,000 dollars in productivity lost to waiting, not to bad decisions, but to slow ones.

The commercial cost extends beyond internal productivity. When a contract requires approval from three layers of management and the approval cycle takes three weeks, the counterparty experiences that delay as a signal: this organisation is slow to commit. For a sales negotiation where momentum matters, a three-week approval cycle can be the difference between closing the deal and losing it to a competitor whose internal process is faster.

Where the Bottleneck Actually Forms

Approval bottlenecks almost never form at the decision itself. The approver is usually capable of making the decision quickly when the document reaches them in the right form, with the right context, at the right moment. The bottleneck forms in the infrastructure around the decision: the routing of the document to the right person, the notification that it is waiting, the escalation when it has been waiting too long, and the record of the decision once it has been made.

1. Routing failure
The document leaves the person who completed it and enters a generic email inbox or shared drive where the intended approver may or may not notice it. There is no system-generated notification. There is no priority signal. The document waits.

2. Notification failure
The approver does not know the document is waiting unless someone tells them. In email-based approval processes, the telling is another email, which may itself wait in an inbox. The approval waits for the notification. The notification waits for someone to remember to send it.

3. Escalation failure
When the approval is overdue, there is no automatic escalation. The person waiting must manually identify that the timeline has been exceeded and manually contact someone with authority to unblock it. The escalation process is itself a manual overhead that adds delay to a process that is already delayed.

4. Record failure
When the approval is eventually given, it exists as an email reply or a verbal conversation rather than a system record. The audit trail for the decision is a thread in someone’s inbox that may not be retrievable when it is needed.

What Structured Approval Routing Changes

Structured approval routing replaces all four failure points with system-governed events. The document is routed automatically to the correct approver the moment it is ready. The approver receives a direct, actionable notification. If the approval is not recorded within the configured SLA window, the system escalates without human intervention. When the decision is made, it is recorded in a timestamped, identity-linked audit trail that is immediately accessible without reconstruction.

The approver’s decision is not changed. The quality of the decision is the same. What changes is the time between when the decision is needed and when it is made, and the completeness of the record that confirms it was made correctly. Explore Flowmono to see how this works.