The accumulation problem
Approval steps are almost always added in response to a specific event — a
payment made in error, a compliance concern raised by an auditor, a request from
leadership to be kept informed. The step is added, the event passes, and the
step remains. Over time, the approval chain reflects the history of every
concern the organisation has ever had rather than a considered view of the risk
that currently exists. The result is a process that is slower than it needs to
be and that consumes the attention of senior staff on decisions that could
safely be delegated to someone with clearly defined authority and documented
criteria.
How to identify redundant steps
The most reliable way to identify redundant approval steps is to ask a simple
question about each one: what would happen if this step were removed? If the
answer is that a genuine control would be lost — a decision would be made
without sufficient oversight, a compliance requirement would go unmet, a
financial risk would be unmanaged — then the step earns its place. If the answer
is that the same information would still be available, the same decision would
still be made correctly, and no material risk would increase, then the step is a
candidate for removal or consolidation. This question feels risky to ask, but
the analysis it prompts is the most direct path to a leaner approval structure.