Picture this scenario: a marketing coordinator needs to publish a social media post. The copy has been written following approved brand guidelines, uses pre-approved imagery, and says nothing remotely controversial. Yet it sits in an approval queue for three days because someone, at some point in the company's history, decided that all external communications require senior management sign-off. The manager who eventually approves it spends fourteen seconds reading it before clicking 'approve' — a formality that cost the organisation seventy-two hours of momentum. This is not governance. This is organisational scar tissue masquerading as diligence.

Manual approvals for low-risk, routine decisions are one of the most pervasive and underexamined sources of wasted time in modern organisations. Research shows cross-functional handoffs cause 60% of process delays, and unnecessary approval layers compound this problem by adding wait states that deliver no meaningful risk reduction while destroying team velocity and autonomy.

The Anatomy of an Unnecessary Approval

Not all approvals are unnecessary. Financial commitments above a threshold, client-facing contracts, and decisions with significant regulatory implications warrant deliberate sign-off. The problem arises when organisations fail to distinguish between decisions that carry genuine risk and decisions that are merely decisions. Over time, approval requirements accumulate through a process of defensive expansion — each time something goes wrong, a new approval layer is added. Layers are never removed because removing oversight feels riskier than maintaining it, regardless of whether that oversight achieves anything.

The anatomy of an unnecessary approval typically contains three elements: a low-risk decision, a pre-existing framework that already governs the outcome, and an approver who adds no substantive evaluation. When the average small-to-medium business has 47 manual processes that could be partially or fully automated, a significant proportion of those involve approval steps that exist purely from institutional habit. The approver rubber-stamps because the decision falls within established parameters — parameters that could serve as the approval mechanism themselves if anyone paused to recognise this.

Consider the compounding effect across an organisation. If five teams each have three unnecessary approval steps in their weekly workflows, and each approval adds an average of one business day in waiting time, that represents fifteen days of accumulated delay per week across the company. McKinsey's operations research confirms this pattern — cross-functional handoffs cause 60 per cent of process delays. Every approval is a handoff. Every handoff is a potential delay. The question leaders must ask is not 'could something go wrong without this approval?' but rather 'does this approval actually prevent anything from going wrong?'

How Approval Culture Quietly Destroys Initiative

The damage from excessive approvals extends far beyond the hours spent waiting. There is a psychological cost that rarely appears in efficiency audits. When employees learn that their professional judgement requires validation for routine decisions, they internalise a message: your expertise is insufficient, your autonomy is conditional, your initiative requires permission. Over time, this produces learned helplessness — teams stop proposing improvements because the approval overhead makes small changes feel disproportionately burdensome.

This erosion of initiative creates a vicious cycle. As teams become less proactive, leadership perceives a need for more oversight, which leads to additional approval requirements, which further suppresses initiative. Companies spend 27 per cent of productive time on process debt — workarounds for broken processes — and unnecessary approvals are a primary contributor to this figure. The irony is acute: the very mechanism intended to ensure quality actually degrades it by removing the conditions under which people take ownership of their work.

European workforce studies consistently show that autonomy is among the top three predictors of employee engagement and retention. When talented professionals find themselves seeking permission for decisions they were hired to make, they begin updating their CVs. Employee turnover costs approximately twice the departing employee's salary, and a significant portion of voluntary departures cite bureaucratic frustration as a contributing factor. The approval that takes a manager fourteen seconds to grant may have cost the organisation a six-figure employee who simply ran out of patience with being treated as incapable of independent thought.

Distinguishing Governance from Theatre

Effective governance is essential. Approval theatre — the performance of oversight without its substance — is not. The distinction lies in whether an approval step genuinely reduces risk or merely creates the appearance of control. A useful diagnostic: if the approver rejects fewer than 5 per cent of requests, the approval step is likely serving a psychological rather than operational function. It makes someone feel in control without actually exercising meaningful discretion.

Process maturity models offer a framework for this distinction. At the ad hoc stage, approvals compensate for unpredictability — when processes are inconsistent, human judgement at each step provides necessary correction. As processes mature to the defined and managed stages, the process itself embodies the standards that approvals were meant to enforce. Documentation, checklists, and clear parameters replace the need for human intervention at routine decision points. Process standardisation reduces error rates by 50 to 70 per cent according to Six Sigma research — often more reliably than a distracted manager scanning a request between meetings.

The Lean methodology principle of separating value-add from non-value-add steps applies directly here. An approval is value-add only when it introduces information, judgement, or perspective that the person requesting approval does not possess. If the approver is simply confirming that established criteria have been met, that confirmation can be built into the process itself through checklists, automated validation, or clear decision boundaries. Standard checklists prevent 50 per cent of errors in complex operations — without requiring anyone to wait three days for a rubber stamp.

The Financial Reality of Approval Bottlenecks

Translating approval delays into financial terms reveals costs that most organisations have never calculated. Take a product development team of eight people earning an average of £55,000 annually. Their fully-loaded hourly cost (including benefits, overhead, and facilities) is approximately £42 per person per hour. If unnecessary approvals create an average of six hours of idle waiting per person per week — through blocked tasks, context-switching, and the cognitive cost of unresolved work — the annual cost is roughly £105,000. For a single team. In a single department.

Process inefficiency costs businesses 20 to 30 per cent of revenue annually according to IDC and Gartner research. Unnecessary approvals contribute to this figure both directly (through waiting time) and indirectly (through the secondary effects of broken momentum). When a developer waits two days for deployment approval on a routine update, the cost is not merely two days of salary. It includes the context-switching cost when they move to another task, the re-familiarisation cost when they return, and the opportunity cost of the feature or fix sitting undelivered.

Workflow automation, when applied to approval processes specifically, delivers remarkable returns. Forrester Research documents an average ROI of 400 per cent within the first year for workflow automation initiatives. Much of this return comes not from eliminating approvals entirely but from converting manual approvals into automated validation — systems that check whether predefined criteria are met and only escalate to human decision-makers when genuine exceptions arise. The approval still exists conceptually; it simply no longer requires a human to perform what is essentially a mechanical verification.

Redesigning Approval Workflows for Speed and Safety

Eliminating unnecessary approvals does not mean eliminating accountability. The goal is replacing slow, manual validation with faster mechanisms that maintain or improve quality outcomes. This begins with an approval audit: list every approval step in your core workflows, document the average time each adds, record the rejection rate, and identify what specific risk each approval mitigates. Any approval with a rejection rate below 5 per cent and no regulatory requirement is a candidate for redesign.

The redesign typically follows one of three patterns. First, pre-approval through clear boundaries: define the parameters within which team members can act autonomously, requiring approval only when those boundaries are exceeded. Second, post-action review: allow execution to proceed immediately but sample outputs for quality review after the fact, intervening only when standards are not met. Third, peer validation: replace hierarchical approval with peer review, which is faster, develops team capability, and often provides more relevant scrutiny than a senior manager reviewing an unfamiliar domain.

Companies with properly documented processes grow twice as fast as those without. Part of this growth differential comes from decision velocity — the speed at which an organisation can move from intention to action. Every unnecessary approval is friction between intention and action. Bain's Digital Enterprise Survey found that only 4 per cent of companies have achieved end-to-end process integration. The remaining 96 per cent contain approval bottlenecks that exist not because they add value but because nobody has been tasked with proving they do not. Assign that task. The results will surprise you.

Creating a Culture of Earned Autonomy

Sustainable reduction of unnecessary approvals requires a cultural shift from permission-seeking to accountability. This does not happen through a single announcement or policy change — it requires leaders to consistently demonstrate trust, reinforce autonomous decision-making, and respond to mistakes as learning opportunities rather than evidence that more oversight is needed. Process owners who review quarterly improve efficiency by 15 per cent year-on-year, and part of that improvement comes from progressively expanding the boundaries of autonomous action as teams demonstrate competence.

The concept of 'earned autonomy' provides a practical framework. New team members or new processes begin with appropriate oversight. As competence is demonstrated and documented, approval requirements progressively reduce. This creates a positive reinforcement loop: team members are motivated to demonstrate capability because capability is rewarded with autonomy. It also ensures that oversight exists where it genuinely serves a purpose — at the boundaries of established competence rather than at every routine decision point regardless of the decision-maker's expertise.

The organisations that will outperform in the coming years are those that understand velocity as a strategic advantage. Speed of execution, speed of decision, speed of adaptation — these are competitive differentiators that cannot coexist with approval chains designed for a more cautious era. Lean process mapping identifies value-add versus non-value-add steps with precision. Apply that lens to your approval workflows and you will find that many steps exist not to prevent errors but to distribute blame. That is not governance — it is institutional anxiety formalised as process. Your team deserves better, and your business requires it.