The Decision Bottleneck: What Is Waiting for Approval Costing Your Business?
Share this post
An Emergent Africa perspective on decision intelligence, accountability and strategy execution
A commercial proposal waits for a pricing exception. A critical appointment remains unsigned. A maintenance intervention moves between operations and finance. A technology investment returns to the executive committee for another discussion.
Each item has an explanation. Someone needs more information. Another stakeholder must be consulted. The next committee meeting is approaching.
Meanwhile, the business keeps paying.
Customers wait. Employees improvise. Benefits move further into the future. Management time disappears into follow-up emails, revised presentations and repeated discussions.
“Awaiting approval” sounds like an administrative status. It can conceal a material commercial exposure.
For boards and executive teams, the challenge is to understand which decisions are waiting, why they are waiting, and how much value is being lost while they remain unresolved.
This paper draws on research and perspectives from McKinsey, Bain, BCG, Deloitte and PwC. The practical framework and illustrative calculations that follow are Emergent Africa’s synthesis, rather than a methodology attributed to those firms.
- The cost that rarely has its own line in the management accounts
Businesses measure production downtime, overdue receivables, customer complaints and expenditure variances. They should apply comparable discipline to decisions that prevent resources from being deployed or benefits from being realised.
Consider an efficiency initiative with a credible implementation plan and an identified operational owner. Its financial case has been reviewed, but approval slips from one meeting to the next.
The project may still appear in the strategic plan. Its expected savings may remain in the forecast. Its status may be amber rather than red.
Yet the date on which those savings can begin has changed.
A similar problem arises when a customer proposal needs an exception that nobody feels authorised to approve. The sales team continues to forecast the opportunity, even as the customer’s willingness to wait declines.
The financial consequences surface elsewhere: weaker margins, missed revenue, higher operating costs or disappointing cash conversion. The approval process itself may never be identified as the cause.
This creates an accountability gap. Teams must explain their results, while the decisions necessary to achieve those results remain outside their control.
An unresolved decision should therefore have an owner, an age, a required resolution date and an assessment of its commercial consequences.
- What the research tells us about decision performance
McKinsey’s 2019 publication Decision making in the age of urgency, based on a 2018 survey of 1,259 participants, reported that only 20% said their organisations excelled at decision-making. Some 61% said most of their decision-making time was used ineffectively.
The research also challenged the assumption that speed necessarily compromises quality:
“faster decisions tend to be higher quality”
These were survey associations, rather than evidence that accelerating any individual decision will improve its outcome. Nevertheless, they suggest that strong decision practices can support both speed and quality.
Deloitte’s Getting decision rights right highlights ambiguity over who decides as a source of delay. It recommends clarity about the decisions required, the people authorised to make them, and the processes supporting them. Its organisational research connects stronger design maturity with better business outcomes, although that relationship should not be interpreted as a financial return attributable solely to approval reform.
The implication for executives is practical: asking people to work faster will achieve little if they lack authority, reliable evidence or a clear route to resolution.
Decision performance must be designed into the organisation.
- Where waiting becomes expensive
The cost of delay takes several forms. Understanding the distinctions helps leaders avoid both understatement and inflated business cases.
Commercial opportunities weaken. A delayed quotation, contract amendment or delivery commitment can make a customer reconsider. Where an order is permanently lost, the relevant starting point is usually the contribution the business would have earned, adjusted for the probability of winning it.
Operating costs continue. Delaying an intervention that would reduce waste, overtime or outsourced expenditure extends the period during which those costs are incurred. Whether they can later be recovered depends on the nature of the intervention.
Cash remains tied up. Unresolved customer disputes, inventory decisions and supplier reconciliations can delay cash release. The cash balance affected is not itself the cost: financing expense, collection risk and reduced financial flexibility require separate consideration.
Delivery becomes more expensive. A decision that misses a procurement window may require expedited freight, contractor remobilisation or revised scheduling. A short approval delay can create a much longer implementation delay.
Management capacity is consumed. Employees chase signatures, recreate papers and repeat explanations. Even when salaries do not change, this work displaces activity that could serve customers or improve operations.
Strategic options narrow. A delayed pilot may miss a customer buying cycle. An acquisition opportunity may close. A skilled candidate may accept another offer. Some opportunities cannot simply be moved into the next reporting period.
These categories should be assessed separately before being combined. Otherwise, a business may count the same underlying loss several times.
- Distinguish productive scrutiny from avoidable waiting
Some decisions deserve extended analysis. A major acquisition, a safety-critical intervention or a substantial capital commitment requires evidence, challenge and appropriate approval.
The useful distinction is between time spent improving a decision and time spent waiting for something to happen.
A decision may take 30 working days from submission to resolution while receiving only a few hours of substantive attention. The remaining time could involve diary availability, repeated handovers, unclear ownership or uncertainty about the next step.
Executives should examine both:
- Active decision time: analysis, consultation, challenge and deliberation.
- Waiting time: periods when no substantive work advances the decision.
Long active analysis may be justified. Long unexplained waiting deserves scrutiny.
There is also a legitimate case for postponement when new information is expected to materially change the choice. That postponement should be explicit: what evidence is missing, when it will arrive, who will obtain it, and what waiting will cost.
“Deferred” is a decision only when its rationale and consequences are understood.
- Why approval bottlenecks persist
One common cause is the gradual accumulation of controls. Each additional approval may have been introduced for a reasonable purpose, but few organisations regularly test whether all of them still add value.
Another is uncertainty about authority. Several executives may have relevant expertise, while nobody knows who has the final decision.
A third is organisational behaviour. Managers who have experienced criticism for exercising judgement may learn to escalate even routine matters. Formal delegation exists, but practical permission does not.
BCG’s work on organisation design distinguishes external complexity from internally created “complicatedness”. It describes how excessive layers and poorly designed structures can slow decisions and weaken cooperation. The lesson is to examine how roles, incentives and working practices operate together, rather than assuming that a revised organisation chart will solve the problem.
Conflicting objectives can reinforce the delay. Sales may prioritise revenue, finance may protect margin, and operations may defend capacity. All three perspectives matter. A decision stalls when nobody is accountable for resolving the enterprise trade-off.
The bottleneck often sits between functions, where responsibility is shared but authority is uncertain.
- Establish the economics of the pending decision
A useful decision paper should show what happens if the organisation acts, declines or waits.
Start with five questions:
- What benefit or risk reduction depends on this decision?
- When could that benefit realistically begin?
- How does a delay change the expected outcome?
- What additional costs arise during the delay?
- What uncertainty could further analysis resolve?
For an illustrative operational improvement, assume:
- Expected net operating savings of R600,000 per month.
- A six-week avoidable approval delay.
- Implementation cannot begin until approval.
- For simplicity, six weeks is treated as 1.5 months.
Approximately R900,000 of savings would move beyond the original delivery schedule.
That amount is benefit deferred relative to the plan, not automatically a permanent lifetime loss. If the initiative can operate for longer later, some benefits may be recovered. If it has a fixed end date, the missed savings may be unrecoverable.
Now assume a separate R8 million cash release is delayed by 45 days. At an illustrative annual financing rate of 12%, the simple financing cost is:
R8,000,000 × 12% × 45 ÷ 365 = approximately R118,356.
The R8 million remains the delayed cash release; R118,356 is the estimated financing cost under these assumptions.
Finance should validate the assumptions, distinguish timing effects from permanent losses, and prevent double counting. These examples are illustrations, not industry benchmarks.
For major investments, compare the discounted cash flows of acting now and acting later, including any benefit from better information. The objective is a defensible estimate, not a dramatic headline.
- Prioritise the decisions that matter commercially
The oldest item in the approval queue is not necessarily the most urgent.
A small operational decision might block an entire production schedule. A larger capital proposal may have little immediate consequence if implementation cannot begin for several months.
Priority should reflect the combination of:
- Value affected.
- Rate at which that value deteriorates.
- Risk created by waiting.
- Dependencies blocked.
- Reversibility of the decision.
- Readiness of the supporting evidence.
A helpful executive question is: What changes if we decide next week instead of this week?
Sometimes the answer is very little. Sometimes it is the loss of a customer, a shutdown window or a supplier commitment.
This approach also exposes false urgency. An inadequately prepared proposal should not bypass scrutiny simply because its sponsor has labelled it critical.
The decision owner should distinguish urgency created by commercial circumstances from urgency created by poor preparation.
- Make decision rights explicit
Bain’s RAPID® framework separates five roles: Recommend, Agree, Perform, Input and Decide. Its value lies in distinguishing participation from authority and execution responsibility.
Bain also makes the timing requirement clear:
“Every major decision needs timetables and deadlines.”
An organisation does not need to adopt a particular framework to apply the underlying discipline.
For every important recurring decision, people should know who prepares the recommendation, whose input is necessary, which formal approvals apply, who makes the final choice, and who implements it.
Where a committee or board holds authority, that collective authority should remain explicit. Someone should still own preparation and progression of the item.
Consultation also needs boundaries. Relevant stakeholders should have a defined opportunity to contribute. Required legal, safety or other specialist approvals must be preserved. General consultation should not expand indefinitely because another person would prefer to attend.
Clear decision rights reduce the need to renegotiate the process every time a similar issue arises.
- Match the approval process to the decision
Different decisions require different levels of scrutiny.
A frequent, reversible operational choice within approved limits should follow a different route from an irreversible commitment with material financial or reputational consequences.
A practical design considers financial exposure, reversibility, uncertainty, strategic significance and the consequences of error.
Routine decisions can often be delegated within clear parameters. Cross-functional decisions need a defined route for resolving trade-offs. Major commitments need deliberate challenge and the appropriate executive or board authority.
Delegation should include:
- The scope of the authority.
- The limits within which it may be exercised.
- The evidence required.
- The exceptions that trigger escalation.
- The review arrangements after implementation.
Financial thresholds alone are insufficient. A relatively small transaction may carry significant safety, customer or reputational implications.
Equally, a substantial routine commitment already covered by an approved strategy and budget should not automatically repeat the entire strategic debate.
The approval route should reflect the actual decision being made.
- Fix the evidence that keeps returning for reconciliation
Some decisions wait because the organisation cannot agree on its own facts.
Finance and sales use different customer definitions. Procurement cannot consolidate supplier exposure. Product margins depend on inconsistent cost allocations. Business units classify the same activity differently.
The meeting then becomes an exercise in reconciling information.
Master data management is relevant because shared customer, supplier, product and organisational records underpin many of these choices. Consistent identifiers, ownership and definitions can reduce repeated reconciliation.
This does not mean master data alone resolves every evidence problem. Forecast assumptions, transaction quality, analytical methods and the freshness of information also matter.
For each recurring decision, identify the minimum trusted information required. Establish who owns it, how current it must be, and what uncertainty remains.
The aim is to make the evidence dependable enough for the decision at hand.
A pricing exception may need a reliable view of customer exposure, contribution margin and delivery capacity. It should not require a new enterprise-wide data exercise every time.
- Use decision intelligence to compare consequences
A dashboard can show that performance is deteriorating. Executives still need to determine what to do.
Decision intelligence connects evidence with a specific choice. It makes alternatives, assumptions, constraints and likely consequences easier to assess.
For a pricing decision, that might mean comparing the contribution, capacity implications and customer risk of accepting, modifying or declining a proposal.
For a capital decision, it could mean testing demand, implementation timing and operating assumptions across several scenarios.
PwC’s June 2026 perspective on AI performance highlights organisational foundations including trusted data, clear accountability and decision speed. Its argument supports an important distinction: better technology depends on an organisation’s ability to use its outputs effectively.
AI may help prepare summaries, identify anomalies or compare options. Its output still requires appropriate validation and ownership.
Faster analysis will have limited commercial value if the resulting recommendation enters the same unresolved approval queue.
Technology should support a defined decision process, with clear evidence standards and authority.
- Connect the decision to execution
Approval is an important milestone. Value appears only when the decision is implemented successfully.
A decision record should therefore capture:
- The choice made and its rationale.
- The assumptions supporting it.
- The accountable implementation owner.
- The resources committed.
- The next action and deadline.
- The expected business outcome.
- The conditions that would justify reconsideration.
This creates continuity between strategic intent, executive judgement and operational delivery.
It also prevents repetitive reopening. A decision may need to change when evidence changes, but it should not return to debate simply because a stakeholder missed the original discussion.
Where the decision is to stop or decline an initiative, close the loop. Release resources, update forecasts and communicate the consequences.
Ambiguity after approval can be as costly as ambiguity before it.
A strategy execution platform is useful when it supports this connection between priorities, ownership, dependencies and performance reviews. Its value depends on the management discipline built around it.
- Measure speed alongside quality and outcomes
A shorter approval cycle is meaningful only if the organisation maintains decision quality and delivers the intended benefits.
Useful measures include:
- End-to-end time from initial request to decision.
- Time from a complete submission to decision.
- The proportion of elapsed time spent waiting.
- Decisions overdue against agreed dates.
- Reasons for delay or return.
- Implementation started by the agreed date.
- Outcomes achieved against the original assumptions.
- Decisions reversed because of avoidable errors.
Track both the typical experience and unusually long delays. An average can conceal a small number of commercially damaging cases.
Measure preparation time as well as approval time. Otherwise, a process may appear faster merely because delays have moved upstream.
Avoid turning the number of decisions approved into a target. Declining a weak proposal promptly may create more value than approving it quickly.
The purpose of measurement is to improve judgement, flow and delivery.
- Start with a focused 90-day intervention
A business can begin without redesigning its entire governance model.
Days 1–30: Establish the evidence.
Select two or three recurring decision categories with visible commercial consequences. Review a manageable sample of recent cases and reconstruct what happened.
Record elapsed time, handovers, requests for additional information, waiting periods and implementation consequences. Speak to the people who prepare decisions as well as those who approve them.
Days 31–60: Redesign and pilot.
Clarify authority, required evidence, response expectations and escalation routes. Simplify redundant approvals while retaining necessary controls.
Introduce a short decision brief that includes the recommendation, alternatives, uncertainty and cost of waiting. Test the revised approach in one business unit or process.
Days 61–90: Assess and extend.
Compare results with the baseline. Examine decision quality, implementation progress and the experience of users.
Resolve unintended consequences before expanding. Finance should review claimed benefits and distinguish recovered capacity from actual cash savings.
Assign a permanent owner to sustain the process. Without ownership, familiar habits can quickly return.
- Questions for the next executive meeting
Seven questions can reveal whether decision delays deserve closer attention:
- Which unresolved decisions are currently preventing us from delivering our most important commitments?
- What are the commercial consequences of another week or month of waiting?
- Does each decision have a clearly authorised decision-maker or decision body?
- Are we waiting for evidence that could change the choice, or for administrative availability?
- Which recurring decisions could be delegated within clearer limits?
- Where does inconsistent information repeatedly delay resolution?
- After approval, can we see who acted and whether the intended result followed?
The answers need not be perfect to be useful. Difficulty answering them is itself a reason to investigate.
The Emergent Africa perspective
Emergent Africa’s approach brings together strategy execution, decision intelligence and trusted business data.
Strategy execution establishes the outcomes that matter and the responsibilities required to deliver them. Decision intelligence helps leaders evaluate options and consequences. Master data management strengthens the shared information on which many decisions depend.
Meridian, Emergent Africa’s strategy execution platform, can form part of this broader approach to connecting strategic priorities, accountable ownership and performance review. The starting point is understanding where decisions obstruct delivery and what management practices need to change.
An effective intervention begins with a concrete business question: where is avoidable waiting affecting revenue, margin, cash, risk or strategic progress?
From there, the organisation can clarify authority, improve evidence and establish a disciplined connection between decision and action.
A leadership team should be able to explain why an important decision is taking time and what that time is buying.
Where the answer is better evidence, sound challenge or necessary assurance, the time may be well spent.
Where the answer is an unclear mandate, another handover or an unavailable meeting slot, the business should know what it is paying.
What is waiting for approval costing your business—and who is accountable for resolving it?
References
- McKinsey & Company. Decision making in the age of urgency. 30 April 2019. Survey fieldwork conducted in February 2018.
- Deloitte Insights. Getting decision rights right. 28 February 2020.
- Boston Consulting Group. A New Approach to Organization Design. 2016.
- Bain & Company. The five steps to better decisions.
- PwC UK. The organisational gap: why AI performance is a leadership problem, not a technology one. June 2026.
The financial examples are hypothetical. The paper’s recommendations are Emergent Africa’s synthesis; the cited firms have not endorsed them.