Businesses know how to calculate salaries, margins, equipment costs, logistics, and even minutes of server downtime. But there is one expense that rarely appears in financial reports: the time when everything is ready to move forward — except the decision.
10:17 AM.
The supplier sends a message:
The equipment is in stock.
The price is confirmed.
We can hold the reservation until the end of the day.
Good news.
The client has approved the configuration.
The technical team has validated the specification.
The commercial terms are clear.
The budget is available.
Only one thing remains:
one internal approval.
The email is sent.
Now we wait.
11:06 AM
No response.
Nothing unusual.
Everyone has meetings.
12:43 PM
The supplier asks:
“Any update?”
Not yet.
2:18 PM
The person responsible for approval replies:
“Everything looks fine. Let’s have Finance review it as well.”
The email goes to Finance.
3:37 PM
Finance asks one question.
The question goes to Procurement.
Procurement forwards it to Sales.
Sales checks with the supplier.
The supplier responds twenty minutes later.
The answer travels back through the same chain.
5:11 PM
Every question has been answered.
But the person who needs to give the final Approved has already left for the day.
Tomorrow.
The Next Morning, 9:24 AM
Approval arrives.
The order can finally be placed.
The supplier receives:
“Please proceed.”
A few minutes later, the reply comes back:
Unfortunately, the stock was allocated yesterday.
The equipment can still be ordered.
But the lead time is now six weeks.
How Much Did Those 23 Hours Cost?
At first glance, nothing.
No equipment failed.
There was no cyberattack.
No penalty was issued.
Employees received the same salaries.
No accounting system created a line called:
“Loss caused by waiting for approval — $X.”
So, from the company's perspective, it may appear that nothing happened.
But something did.
The company lost the available stock.
The delivery timeline changed.
The account manager now has to speak with the client again.
Procurement re-enters the process.
The engineer has to validate an alternative.
The supplier prepares a new quotation.
The price may change.
The exchange rate may change.
The client may not be willing to wait six weeks.
One day of waiting has created several additional days of work.
We are very good at calculating the cost of action. We are surprisingly bad at calculating the cost of inaction.
Businesses Have a Massive Hidden Expense: Waiting
Look at an ordinary working day inside almost any organization.
Someone is waiting for:
approval.
a PO.
budget confirmation.
a signature.
Legal.
IT.
the client.
the supplier.
the director.
Finance.
system access.
an account to be created.
a contract to be approved.
And here is the interesting part:
At any individual moment, nobody appears to be doing anything wrong.
Finance has every right to verify the numbers.
Legal should review the contract.
The CEO is busy.
Procurement is following procedure.
IT needs additional information.
Every participant can be behaving rationally.
And yet the process as a whole can be catastrophically slow.
The Problem Is Not How Many People Are Working on the Task
We are used to measuring work through activity.
How many hours were worked?
How many tickets were closed?
How many calls were made?
How many quotations were sent?
How many contracts were processed?
But there is another unit of time that matters to a business:
How much time passes between an opportunity appearing and a decision being made?
Imagine two competitors.
Both receive the same supplier offer on Monday morning.
Both have the budget.
Both have the same technical expertise.
Both receive the same price.
Company A makes the decision in three hours.
Company B takes four days.
On paper, they may look equally efficient.
In the market, they are already two very different companies.
One moves.
The other waits.
This Leads to a Metric Few Companies Measure: Cost of Waiting
The cost of waiting is not simply the salaries paid while employees are inactive.
It is much broader than that.
Imagine a decision is delayed by three days.
During those three days:
stock may disappear;
the price may change;
the exchange rate may move;
a discount may expire;
a production slot may be taken by another customer;
a specialist may move to another project;
the client may start talking to a competitor;
the deadline gets closer;
logistics may become more expensive;
the team may have to repeat work that was already completed.
That is why the cost of waiting often grows non-linearly.
The first hour may cost almost nothing.
The twenty-fourth may be extremely expensive.
There Is a Major Difference Between “Execution Time” and “Elapsed Time”
Consider a typical contract approval.
Legal actually works on the document for:
47 minutes.
Finance:
22 minutes.
Procurement:
31 minutes.
CEO:
6 minutes.
Total actual work:
1 hour and 46 minutes.
But from receiving the contract to signing it:
9 days.
Where did the remaining eight days and twenty-two hours go?
Nowhere.
They existed between people.
Inside inboxes.
In queues.
Waiting for meetings.
Inside phrases such as:
“I’ll look at it tomorrow.”
“We need one more approval.”
“Remind me after lunch.”
“I thought this had already been approved.”
This is why making the work itself faster does not necessarily make the company faster.
AI Can Prepare a Document in 30 Seconds. A Human May Still Take Three Days to Approve It.
This is one of the most interesting paradoxes of modern automation.
Companies invest heavily to reduce:
20 minutes to 2 minutes;
2 hours to 15 minutes;
one day to one hour.
AI writes.
CRM routes automatically.
ERP calculates.
Workflows send notifications.
Dashboards update in real time.
Then the result reaches a human.
And sits in an inbox for 17 hours.
We automated the work.
We did not automate the decision.
As a result, an organization can have incredibly fast technology and still remain organizationally slow.
The slowest part of a modern digital company may not be inside the system. It may exist between two decisions.
But Speed Does Not Mean Removing Control
There is an obvious mistake we could make here.
We could conclude:
“Then remove the approvals.”
No.
Many approvals exist for very good reasons.
Financial control matters.
Cybersecurity review matters.
Legal matters.
Procurement matters.
Technical validation matters.
Especially when dealing with major contracts, infrastructure, sensitive data or significant financial commitments.
The problem does not begin when a decision is reviewed.
The problem begins when an organization does not know how long that review should take or who has the authority to end it with a decision.
That distinction matters.
Every Important Decision Needs an Owner
In many organizations, you can find five people who have the authority to say:
“I disagree.”
And nobody who clearly has the authority to say:
“The decision is made. Move forward.”
That creates a strange organizational architecture.
Responsibility is distributed.
Authority is blurred.
Everyone can see the risk.
Nobody owns the decision.
Then the endless cycle begins:
Finance → Legal → Procurement → IT → Management → back to Finance.
Everyone adds another comment.
The document gets better.
The decision gets later.
Ask One Simple Question Inside Your Company
Not:
“Who participates in the approval process?”
Ask:
“Who exactly makes the final decision?”
A name.
Not a department.
Not a committee.
Not “management.”
A person.
If that question cannot be answered quickly, the process already has a problem.
There Is Another Form of Waiting That Can Be Even More Expensive: Waiting to Act on Bad News
Imagine an engineer realizes on Monday that a project will probably miss its deadline.
But it is not 100% certain yet.
So they wait.
On Tuesday, the probability is now 70%.
They inform the manager.
The manager wants to find a solution before escalating.
Wednesday.
The supplier confirms the delay.
On Thursday, the information reaches the director.
On Friday, the client is finally informed.
The problem appeared on Monday.
The organization officially reacted on Friday.
The company did not lose four days because of the problem itself.
It lost four days because of the speed at which information and decisions moved through the organization.
That is Cost of Waiting too.
A Company’s Speed Is Not the Same as Its Employees’ Speed
This distinction is important.
Fast employees do not automatically create a fast organization.
You can build an excellent team where everyone answers emails within ten minutes — and still take weeks to make decisions.
Why?
Because organizational speed is not determined only by how quickly people work.
It is determined by how quickly work moves between people.
Waiting usually lives in those transitions.
CEOs Should Look Not Only at KPIs, but at Queues
Most dashboards show what has happened.
Revenue.
Margin.
Pipeline.
Tickets.
Projects.
Costs.
But imagine opening a different dashboard:
What is currently waiting for a decision?
Not simply a task list.
Instead:
What is waiting?
Since when?
For whom?
Why?
What is the financial or operational consequence of the delay?
At what point does the absence of a decision become critical?
A CEO might suddenly see a very different organization.
Not the company that is working.
The company that is waiting.
You Can Start Without Buying Another IT System
Take ten important processes from the last few months.
For example:
a procurement;
a contract;
a hire;
a commercial proposal;
an IT project;
a payment;
a pricing change;
a supplier selection;
an incident;
a customer escalation.
Reconstruct the timeline for each.
When did it begin?
When was someone actually working on it?
When was it waiting?
For whom?
For how long?
Why?
The result may be uncomfortable.
Perhaps a process took ten days from start to finish.
But the actual work required only four hours.
Then you do not have a productivity problem.
You have a flow problem.
And Those Are Two Completely Different Problems
If the problem is productivity, make the work faster.
Automate it.
Train people.
Use AI.
Improve the system.
If the problem is flow, different things need to change:
handoffs;
approval levels;
decision rights;
financial thresholds;
escalation rules;
ownership;
response times.
Many organizations try to solve the second problem using tools designed for the first.
They buy faster technology.
And end up completing a task faster — only for it to arrive in the waiting queue sooner.
What Can Companies Actually Change?
You do not need a massive transformation project to begin.
Start with a few rules.
First: decisions need deadlines too.
If a quotation must reach the client on Friday, an approval cannot simply say:
“Please review when you have time.”
The decision itself needs a deadline.
Second: define the decision owner.
Who has the final word?
Third: create appropriate financial thresholds.
A $1,000 purchase should not necessarily follow the same approval path as a $1 million contract.
Fourth: escalation should happen before the deadline, not after it.
If a decision must be made within 24 hours, the organization should not discover the problem in hour 25.
Fifth: measure waiting time, not only execution time.
Sometimes that single metric completely changes management's understanding of a process.
There Is One More Question Companies Should Ask More Often
When someone says:
“We need more time to make this decision,”
ask:
“What new information do we expect to have?”
It is an extremely useful question.
Additional time makes sense when tomorrow will bring new information.
A new calculation.
An engineer's conclusion.
A client response.
A legal opinion.
A revised price.
A test result.
But if tomorrow we will know exactly what we know today, then another 24 hours is not analysis.
It is simply a delayed decision.
4:42 PM
Let us return to our original order.
The equipment is no longer in stock.
The account manager has found an alternative.
It costs 7% more.
The engineer has validated the configuration again.
The client has been informed about the changed delivery timeline.
Finance has recalculated the economics.
Procurement has requested a new price.
The supplier has issued a new quotation.
Six people are now working again on a task that was almost complete yesterday.
In the reporting system, all of this will look like work.
And technically, it is.
But much of that work exists only because at 10:17 yesterday morning, the organization could not make one decision in time.
We Have Spent Years Measuring the Cost of People. Perhaps It Is Time to Measure the Cost of Time Between Them.
The next era of business may not necessarily belong to companies with the largest teams.
Or those with the most AI.
Or the most expensive ERP.
Or even those whose individual employees work the fastest.
The advantage may belong to organizations that can rapidly turn:
information → into a decision → and a decision → into action.
Because the market does not care how many hours your team spent discussing something.
The market sees when you finally make the move.
So the next time an important document sits in an inbox marked “Waiting for Approval,” look at the clock.
Not because someone is necessarily working too slowly.
But because another mechanism may already be running:
the Cost of Waiting.
And perhaps the most important question is no longer:
“How long will it take us to complete this work?”
It is:
“How much is every hour costing us while we wait to move it forward?”