The Queue for Permission

The owner would like the team to show more initiative. The team would like to know which version of initiative will be acceptable today. Between these two perfectly understandable wishes sits a customer waiting for an answer. Nobody is idle. Messages are being written, screenshots forwarded and explanations assembled. The business is busy transporting a decision to the only person allowed to make it.

This can look like a staffing problem. Perhaps people lack confidence. Perhaps they need training. Sometimes they do. But before prescribing a more enterprising attitude, it is worth looking at what happens when someone actually acts. If an ordinary, reasonable decision is repeatedly overturned because the owner would have preferred something else, asking first becomes a practical adaptation. The queue for permission may be something the business has taught itself to build.

A small decision with a long journey

Consider a fictional company arranging customer collections. An employee can see that an order is ready and that a later collection slot is available. A customer asks to move the appointment. The employee still asks the owner, who replies yes between two other calls. Nothing dramatic has happened. Yet the customer waited, the employee paused and the owner became involved in a choice for which the relevant information was already elsewhere.

One such interruption is easy to dismiss. The more useful question is whether the same type of decision travels this route repeatedly. If it does, the business is maintaining a process in which the person closest to the facts prepares the answer and another person releases it. That extra step may have a purpose. Perhaps the visible availability is incomplete. Perhaps a supplier constraint is missing. Or perhaps approval has survived after its reason disappeared.

Do not start by removing the step. Start by finding out what it protects. Ask for a few recent examples and follow the actual journey: what was known, what was missing, who could decide and what changed after approval. A recurring question is useful evidence about the organisation. Calling it a lack of initiative too early can hide the information needed to improve it.

The safest answer may be a question

Imagine that the employee previously moved a collection within the published rules and was then criticised because the customer was considered important. On another occasion, the same request was refused and the employee was told to be flexible. The difficulty is no longer just knowing the timetable. It is predicting an unwritten preference that changes with facts the employee may not possess.

In that situation, “please check with me” offers a clear route to avoiding a disputed choice. The owner may experience the resulting questions as dependence. The employee may experience them as the only reliable way to do the job correctly. Both interpretations can coexist. Repeating “use your judgement” does little if the real standard remains “guess what I would have decided, including what I have not told you.”

This is not an excuse for ignoring instructions or avoiding every responsibility. It is a reason to distinguish unwillingness from an unclear operating environment. Ask what the person believed they could decide and why. If the answer is different from the owner’s understanding, there is something specific to resolve. A conversation about the boundary is more useful than a conversation about personality.

Permission needs edges

An instruction such as “handle routine changes yourself” sounds generous but leaves the important word unexplained. What is routine? For the collection example, the business might permit a trained employee to move a ready order between confirmed available slots, with the customer’s agreement, provided no extra cost or new delivery promise is introduced. This is an illustrative boundary, not a universal policy. Its usefulness depends on the actual operation.

The rule also needs to say when to stop and ask. Missing readiness information, conflicting capacity, a request outside the available hours or a change that affects another customer could require escalation. Safety-sensitive or otherwise consequential decisions may need specialist review, a second check or reserved authority. Delegation is not a competition to eliminate approvals. Some approvals are the service working properly.

The important distinction is between a defined decision and a vague invitation to be brave. Give people the information, access and training the decision requires. Authority to choose a slot is not useful if the availability shown is unreliable. Nor is responsibility for an answer fair if the employee cannot see the commitments already made. Moving the decision without moving the necessary knowledge merely relocates the problem.

A second opinion is different from a second signature

There are good reasons to consult a colleague even when formal approval is unnecessary. Someone may notice a consequence the first person missed. A new employee may want to compare their interpretation with an experienced one. The aim is not to make everyone decide alone. It is to separate help with thinking from a requirement that someone else authorise every ordinary action.

That difference should be visible in the language of the team. “I can make this change, but I would like your view on this unusual detail” is different from “I cannot reply until you say yes.” The former can develop judgement while preserving ownership. The latter may be entirely appropriate where authority is reserved. Confusion begins when the business speaks as though decisions are delegated while operating as though they are not.

In the same way, informing the owner after an ordinary change need not become approval in disguise. If work stops until the owner acknowledges the update, the queue remains. Decide which changes need a simple record, which need notification and which must wait. Keep the record proportionate: enough to explain the action and support continuity, not a small essay defending every sensible choice.

What happens after a reasonable mistake

The decisive moment may arrive when an authorised decision produces an inconvenient result. Suppose the employee used the information available and stayed within the agreed boundary, but the business later discovers a scheduling conflict that was not visible. Correcting the customer’s situation comes first. Then examine where the information or rule failed. Requiring approval for every future change may feel reassuring while leaving the underlying defect untouched.

Equally, a decision made outside an understood boundary needs a different conversation. Was the instruction clear? Was the person trained? Was there a genuine emergency or a missing escalation route? Accountability means examining those facts, not declaring that autonomy makes every outcome acceptable. A boundary only has value if people can rely on it and understand what crossing it means.

The owner also has a distinction to make between a poor decision and a different reasonable preference. If both options were permitted and defensible, replacing the employee’s choice simply to reproduce the owner’s taste can teach the team to seek permission next time. It is possible to explain a better approach without pretending the earlier authority never existed. Change the rule prospectively when necessary, and make the change explicit.

Try it in one ordinary corner

A small business can begin with one recurring, limited decision rather than a company-wide declaration of empowerment. Review recent cases, agree the boundary, confirm the information needed and name an available escalation route. Include a way to pause when facts are incomplete. The first objective is a clearer process, not an impressive claim about a new management culture.

During a short trial, look at whether customers receive answers sooner, whether decisions need correction and how much time staff spend checking or documenting them. Also ask whether people feel pressured to decide when they should ask. Fewer escalations alone is not proof of improvement. It could mean greater clarity, but it could also mean that uncertainty is being concealed. Read the cases, not just the count.

If questions keep coming, treat their pattern as material for the next adjustment. The rule may be too broad, the system may omit crucial information or a new employee may need more practice. Some decisions may properly remain with the owner. Make that explicit rather than presenting the team with freedom it cannot safely use. The point is to place judgement where the facts and capability support it.

The owner’s most valuable absence

There is a particular satisfaction in being needed. An owner who solves a stream of small problems receives frequent evidence that their presence matters. Replacing those interruptions with a functioning rule can feel less productive in the moment: no grateful reply, no rescued appointment, no visible little victory. Yet the customer may have received a good answer without ever discovering that a rescue was once required.

That is not an argument for the owner to disappear or for employees to inherit unlimited risk. It is an argument for designing an ordinary day that does not depend on one person’s continuous availability. Reserved decisions should remain clear, support should remain accessible and performance should remain reviewable. Useful autonomy is bounded and supported. It is not abandonment with a more flattering name.

Before asking why the team will not take initiative, ask what happened the last time it did. The answer may reveal a training need. It may reveal a sensible control. Or it may reveal a queue that everyone has mistaken for diligence. A business does not become more responsible merely because every answer passes through the same pair of hands.