In short
Asking everyone to respond faster rarely makes decisions move faster. Most of the delay sits between people: repeated approvals, information requested too late, and unusual cases passed from one group to another. Three ideas shorten the route without deciding blindly: remove gates that never affect the answer, create a simple lane for everyday cases, and give exceptions a clear way out.
The aim is not speed at any cost. It is a decision made at the right level, with the few facts that matter, in time to support the service.
A simple picture
Picture two lanes leading to the same finish. The first runs through several gates. At each one, the driver slows down, shows the same papers and waits for another green light. The second lane has one check, placed where it genuinely protects the journey. Both lanes are meant to be equally safe, but only one avoids needless waiting.
At work, the gates are signatures, panels and requests for detail that have been added after an incident or simply through habit. A useful check is one that can still improve the choice, prevent a serious error or protect a significant commitment.
Idea 1 — A gate is useful only if it can change the answer
Start with a frequent decision and ask two questions about every approval: what does this person check, and how often does that check alter what happens next? If nobody can answer clearly, the gate may provide comfort rather than protection.
This does not mean removing every second pair of eyes. A large financial commitment, a legal duty or a serious risk deserves a check. Three signatures examining the same point, however, mainly create a queue. It is often possible to keep one named reviewer with a clear test, then inform everyone else once the decision is made.
The questions keep the discussion practical. They focus on the value of the gate, not the seniority of the person who has traditionally held it.
Idea 2 — Everyday cases need a ready-made lane
A decision moves quickly when four things are known before it arrives: the exact question, the minimum facts required, the person who decides and the expected time. Without them, the request stops at every gate while somebody looks for another piece of information.
Take a modest customer discount. If every request goes to a director, the customer waits and managers reread almost identical cases. A simple rule might let the sales lead decide up to a stated limit, provided margin and contract length pass two clear tests. Directors then see only the cases outside that lane. The check remains, but it is applied once and in the right place.
A short guide is enough to make this lane easy to use. Keep it to one page and test whether somebody who did not write it can follow it.
Idea 3 — Exceptions need a clear exit
Even a good lane will meet unusual cases. The danger is letting them fall into an improvised route. Decide in advance when a matter must be raised: an amount above the agreed limit, a customer risk, a legal doubt or an effect across several services. Also name who will decide and the longest acceptable wait.
Keep a simple note of exceptions for a few weeks. When the same case appears regularly, it is no longer a true exception; the rule needs to change. In this way, the lane becomes smoother through experience while the useful check stays intact.
A practical start for leaders and service heads
Choose one recurring decision that currently takes more than five days. Draw its real journey, including time spent waiting. Write down what each gate checks. Keep one main check, define the four elements of the everyday lane, and agree two or three precise reasons for raising a case. Test the route for one month.
Takeaway
Faster decisions do not require opening every barrier. Replace a series of gates with one well-placed check, a clear lane for everyday cases and a planned exit for exceptions. Work moves sooner while the protections that matter remain in place.
If an important decision still gets lost between several approvals, let us look at its real journey.