Customer-Obsessed Businesses Should Inspect Their Approval Queues

An employee can understand a customer's problem, know a sensible response and still be unable to act because the decision is waiting for approval. The customer does not experience that delay as governance. They experience a business that has recognised the issue but has not resolved it.

Approval is sometimes necessary. It can protect significant commercial commitments, specialist decisions and situations outside an employee's competence. The problem begins when routine, low-variation decisions travel through the same queue as genuinely exceptional ones, or when nobody knows who is available to make the call.

Find the decisions customers are waiting for

Look at recent cases involving refunds, substitutions, booking changes, service recovery or other adjustments relevant to your business. Record what decision was needed, who could make it, how long it waited and what happened during the delay.

Distinguish decision time from processing time. A response may take minutes to authorise but hours to reach the person with authority. That points towards a different solution from a case requiring careful investigation or specialist advice.

Ask whether the same decision is being approved repeatedly with little variation. If managers almost always reach the same answer, the organisation may be able to define a clearer rule or limited authority for the frontline team. The evidence should determine the boundary rather than a general campaign to remove controls.

Put authority beside the relevant knowledge

The person closest to the customer may understand the immediate situation, while another colleague understands the operational or commercial consequences. A good decision process makes those perspectives available without forcing the customer to coordinate them.

Specify what employees can decide independently, what information they need and when to escalate. Where a limit applies, explain whether it concerns value, capacity, precedent, specialist judgement or another genuine constraint. Clear reasoning makes the boundary easier to apply consistently.

Provide cover for the approver's absence. A process that works only when one manager is on duty is a dependency, not a reliable control. The customer promise should not expire at the end of that person's shift.

Review decisions after the event where appropriate

For suitable decisions within agreed limits, retrospective review can support learning without making every customer wait. Managers can examine patterns, identify misunderstandings and adjust guidance. This requires clear scope and should not be used for decisions that genuinely need prior specialist approval.

Employees also need to know how the organisation will respond to a reasonable decision made within the agreed boundary. If managers reverse such decisions unpredictably or criticise people for using authorised discretion, the team will return to seeking permission for everything.

Count the cost of waiting

Approval delays create work: follow-up contacts, repeated explanations, management interruptions and sometimes additional recovery. Include that effort when assessing the process. A control that appears costless in one department can impose a substantial burden on the rest of the journey.

The FUSION Score can help start a wider conversation about whether the brand promise is supported by leadership and operating choices. Inspecting approval queues gives that conversation a concrete place to begin. A customer-focused business makes thoughtful decisions possible at the point where they are needed.

Illustrative photograph; pictured people and businesses are not case studies in this article. Photo source: Pexels.