Every business pays an execution tax.
The question is how much.
You will not find it as a line item in the P&L.
You will see it in the distance between a decision and an outcome.
In meetings waiting for decisions.
In decisions waiting for information.
In managers waiting for executives.
In teams waiting for somebody to clarify who owns the issue.
In problems that disappear from one meeting and return three weeks later.
In the same five executives becoming involved whenever anything important happens.
The organisation is moving.
People are busy.
Calendars are full.
Yet execution feels harder than it should.
That is the execution tax.
And in many businesses it has less to do with the quality of the people than with the way decision-making has been designed.
Busyness is not execution
Some organisations create an extraordinary amount of activity.
Leadership meetings.
Operational meetings.
Steering committees.
Project meetings.
Weekly reporting.
Monthly reporting.
Action registers.
Dashboards.
Escalations.
Emails.
Workshops.
Reviews.
None of those things is inherently wrong.
The problem is that activity can create the appearance of execution while concealing the absence of it.
A business can have excellent people working extremely hard and still have poor execution performance.
That usually happens when organisational effort is being consumed by friction.
The same decision gets discussed several times.
Accountability is shared rather than owned.
Actions do not have consequences.
Information arrives too late.
Priorities continually change.
People are empowered in principle but not in practice.
Senior leaders become the final approval point for routine matters.
Issues escalate because the organisation has never been explicit about who has the authority to resolve them.
The organisation does not have an effort problem.
It has a conversion problem.
It is struggling to convert management effort into outcomes.
Decision velocity matters
We talk a lot about revenue growth, margins, cash conversion and productivity.
We talk far less about decision velocity.
Yet the speed at which a business can make sound decisions and turn them into action has a direct effect on almost all of them.
Consider two otherwise similar businesses.
In the first, operational decisions sit in email chains, move through several management layers and frequently require executive intervention.
In the second, decision rights are clear, people know the commercial boundaries within which they can act, and exceptions are escalated only when they genuinely require escalation.
Both businesses may employ equally capable people.
But they do not have the same execution capacity.
One is spending organisational energy deciding how to decide.
The other is using that energy to execute.
That difference compounds.
A slow decision today delays an action tomorrow.
That action may delay revenue, extend working capital, postpone corrective action, slow a customer response or allow an operational problem to continue.
The cost of a slow decision is therefore rarely limited to the decision itself.
A decision-making framework is not another approval matrix
Businesses often recognise this problem and respond by creating a decision-making framework.
That can help.
But many frameworks become another document rather than a different way of operating.
A RACI chart is produced.
Delegations are documented.
Approval limits are circulated.
The organisation now has more governance.
But decisions remain slow.
Why?
Because effective management decision making requires more than documenting authority.
A useful decision-making framework needs to answer at least five questions:
Who owns the decision?
Not who contributes to it.
Not who needs to know.
Who has the obligation to make it?
What information is required?
Not every piece of information that might be useful.
What is actually necessary to make a sufficiently good decision?
What are the boundaries?
At what point can the owner act without escalation?
What financial, operational or risk threshold changes that?
By when must the decision be made?
A decision without a time expectation can remain open indefinitely.
What happens after the decision?
Who executes it?
How is completion made visible?
When is the outcome reviewed?
Without those elements, a framework can clarify governance without improving execution.
Decision rights are an operating-system issue
One of the clearest signs of a business that has outgrown its operating model is excessive upward escalation.
At first, this can look like strong leadership.
The CEO knows everything.
The founder is involved in everything.
The executive team solves problems quickly.
People know that if an issue becomes difficult, somebody senior will step in.
It can work remarkably well for a period.
Then the business grows.
More customers.
More employees.
More sites.
More decisions.
More complexity.
But senior management capacity does not grow at the same rate.
What once felt responsive becomes a bottleneck.
People begin waiting.
Managers learn that the safest decision is to escalate.
Executives complain that their teams are not taking accountability.
Teams complain that executives remain involved in everything.
Both can be right.
The underlying issue is often that decision rights were never redesigned as the business scaled.
The executive team becomes organisational middleware
This is one of the most expensive patterns in a growing business.
Senior leaders begin bridging gaps in the operating model themselves.
Sales and operations disagree?
An executive resolves it.
Commercial and finance cannot align?
An executive resolves it.
A customer exception does not fit the process?
An executive resolves it.
Responsibility between functions is unclear?
An executive coordinates it.
Information cannot be reconciled?
An executive asks for another report.
The executive team slowly becomes human middleware.
It connects functions the operating model does not connect properly.
This can make the organisation appear functional for much longer than it actually is.
The cost is enormous.
Executive capacity is consumed by integration work.
Strategic issues receive less attention.
Middle management does not develop authority.
Decisions accumulate at the top.
And the business becomes increasingly dependent on a small number of people.
Meetings are often a symptom, not the disease
When execution weakens, businesses often add meetings.
It makes intuitive sense.
If coordination is poor, communicate more.
If accountability is weak, review more often.
If visibility is poor, introduce another reporting cycle.
Sometimes this is exactly what is required.
But sometimes the meeting is simply compensating for an unresolved design problem.
A meeting exists because ownership is unclear.
Another exists because systems do not provide visibility.
Another exists because two functions have conflicting objectives.
Another exists because nobody trusts that actions will happen unless senior management checks.
Eventually, the business has a dense meeting architecture surrounding a weak execution architecture.
Everyone attends.
Everyone discusses.
Everyone leaves with actions.
The same problems return.
A useful execution cadence should accelerate accountability.
It should not substitute for it.
Good execution has consequence
One feature distinguishes high-performing operating rhythms from administrative ones.
Consequence.
If an action is committed to, something happens if it is not delivered.
Not punishment.
Consequence.
The issue becomes visible.
The constraint is understood.
Ownership remains clear.
A new commitment is explicit.
Repeated failure triggers intervention.
Without consequence, action registers become historical records of good intentions.
This sounds basic.
Yet it is remarkable how many organisations maintain sophisticated reporting systems while tolerating unresolved commitments week after week.
Visibility without consequence does not create accountability.
The fastest organisation is not the one making the fastest decisions
Decision velocity should not be confused with impulsiveness.
The objective is not to make every decision immediately.
Some decisions deserve analysis.
Some should be challenged.
Some require board involvement.
Some have irreversible consequences.
The goal is to make decisions at a speed appropriate to their significance.
Routine, reversible decisions should generally be fast.
Material, difficult-to-reverse decisions should receive more scrutiny.
The problem occurs when an organisation treats everything as if it belongs in the second category.
That is when governance begins to consume execution.
A strong decision-making framework therefore distinguishes between:
routine decisions,
material decisions,
exceptions,
and genuinely strategic decisions.
Not everything needs the executive team.
Not everything needs consensus.
Not everything needs another meeting.
You can measure the execution tax
If I wanted to understand the execution health of a business, I would not start by counting meetings.
I would follow a sample of important decisions.
When did the issue first become known?
When was ownership established?
How long until a decision was made?
How many people became involved?
How many times was the matter discussed?
Did it escalate?
Why?
How long between the decision and execution?
Was the outcome completed?
Did the same issue recur?
That journey tells you far more than the meeting calendar.
It exposes decision bottlenecks.
It exposes unclear accountability.
It exposes unnecessary escalation.
It exposes information gaps.
It exposes whether managers genuinely have authority.
And importantly, it starts to show where management capacity is being consumed.
Execution speed is designed
People often describe fast businesses as having a particular culture.
Entrepreneurial.
Commercial.
Decisive.
Accountable.
Those characteristics matter.
But execution speed is also a structural outcome.
Clear decision rights create speed.
Reliable information creates speed.
Defined ownership creates speed.
A disciplined execution cadence creates speed.
Appropriate delegation creates speed.
Escalation thresholds create speed.
Consequences create speed.
A business cannot indefinitely ask people to “be more accountable” while maintaining an operating model that requires them to seek approval for every meaningful decision.
Nor can it ask executives to become more strategic while continuing to route routine operational decisions to them.
Eventually structure wins.
The real cost of poor decision making
The visible symptom is frustration.
The commercial consequences run deeper.
Slow pricing decisions delay revenue.
Slow customer decisions affect service.
Slow operating decisions perpetuate cost.
Slow capex decisions constrain capacity.
Slow performance decisions tolerate underperformance.
Slow working-capital decisions consume cash.
Slow corrective decisions allow problems to compound.
That is why decision making is not merely a leadership capability.
It is an operating-performance capability.
And why the quality of a decision-making framework should ultimately be judged by what happens after it is introduced.
Did decisions move closer to the work?
Did unnecessary escalation reduce?
Did management capacity increase?
Did commitments happen faster?
Did execution performance improve?
If not, you may have documented the organisation.
You have not changed it.
Every business pays the tax
Some execution tax is unavoidable.
Coordination takes time.
Good governance has a cost.
Risk needs to be managed.
Important decisions require debate.
The goal is not to eliminate organisational friction completely.
It is to stop paying for friction that creates no corresponding value.
That starts by recognising a simple distinction.
A busy organisation is not necessarily a high-performing organisation.
High-performing businesses are not always doing more.
Often, they require less organisational effort to achieve the same outcome.
Their people spend less time working around the business.
And more time moving it forward.
That is the difference between activity and execution.
And it is where the execution tax becomes visible.