Not Every Decision Should Wait Outside the Manager’s Door

In some organizations, even the smallest move requires approval. A team wants to change the timing of a message, send a test version of a sales proposal to a limited group, reorder a few tasks, or try a simpler way of recording information. The usual response is: “Coordinate with the manager first.” Even when it is said with quality control in mind, that sentence can shut down the engine of execution.

The problem is not only the time spent waiting. When every decision ends up on one desk, the manager becomes a bottleneck; the team learns to pass questions upward instead of thinking; and important decisions get lost among a pile of minor requests. The organization may look more cautious, but in practice it has merely become slower.

The answer is not to make approval faster for everything. If the approval queue is poorly designed, speeding it up is like adding another service counter to a process that should not have so many people in line in the first place. The right question is not, “Who needs to approve this?” A better question is, “If this decision is wrong, what will it cost us to reverse it?”

Before categorizing, one thing needs to be clear: being reversible does not mean the cost is zero. A “two-way” decision means the cost of reversing it, compared to the value and speed gained, is tolerable and recoverable — not that it costs nothing. From this perspective, decisions usually fall into two understandable categories. The first consists of two-way decisions: we decide, observe the result, and correct course if necessary with limited cost and damage. The second consists of one-way decisions: decisions that are difficult, expensive, or damaging to reverse because they create major financial commitments, legal consequences, safety risks, serious harm to customer trust, or a fundamental shift in business direction.

This distinction does not mean being simplistic. Some small decisions can be high-risk in particular circumstances. Changing wording in an internal channel may be reversible, while changing the same wording in a sensitive customer communication or a formal commitment may not be. So do not categorize the task itself; categorize its consequences and the cost of reversing it.

A few simple questions are enough for a practical diagnosis. If this decision turns out to be wrong, can it be corrected within a reasonable period? Would correction require winning back a customer, a difficult negotiation, meaningful expense, or undoing a formal commitment? Does it create safety, legal, or reputational risk? Does it truly close off future options? The heavier the answers, the more the decision needs higher-level approval.

A two-way decision should not enter the managerial approval queue; it should be made at the level where the information and execution responsibility sit. This is important: taking a decision out of the approval queue does not mean abandoning it. The team must know what it can decide, within what boundaries, using what information, and when it must escalate the matter.

Without these boundaries, “authority” quickly becomes ambiguity. One person assumes they can make any change, while another waits for approval for the very same change. The result is usually one of two outcomes: either work stops, or decisions become scattered and inconsistent. Good delegation is not vague freedom; it is a clearly defined decision right within a clearly defined boundary.

You do not need to design a complex chart to begin. For one team, you can create a short list of recurring decisions: which ones the team owns, which ones only require notification, and which ones require approval before execution. The value of this list is not in being exhaustive. Its value is in turning an unclear conversation into an operating rule.

For example, a sales team can decide how to follow up with customers, prioritize leads, use follow-up formats within brand guidelines, or propose a limited experiment. But a discount outside the defined range, an unusual delivery commitment, a change in payment terms, or a promise that affects operational capacity should have a clearer approval path. The difference between these groups is not people’s job titles; it is the cost of reversing the decision.

The same logic works in operations. Reordering tasks, testing a checklist, or adjusting an internal workflow may be reversible. But a change that affects safety, product quality, delivery commitments, or traceability is no longer just a minor improvement. A manager should not enter every small change, but they should know which boundaries must not be crossed without review.

One common mistake is for the manager to see themselves as the safe destination for every decision. The team, seeking to reduce personal risk, transfers the decision upward. In the short term, this looks rational: if the outcome is bad, responsibility has moved higher. Over time, however, the team loses its judgment muscle and the manager becomes occupied with decisions that neither require their knowledge nor make good use of their time.

To break this pattern, a manager should sometimes return the question instead of answering immediately: “What would the cost of reversal be if this is wrong?” “What makes this decision reversible or irreversible?” “What options do you have within your current authority?” These questions are not a way to avoid responsibility. They teach judgment, provided the manager does not later punish the team for an acceptable mistake.

An acceptable mistake means the decision was made within defined boundaries, available information was considered, the result was observed, and correction happened in time. If every reversible mistake is met with blame, the team quickly learns that authority exists only on paper. Then everything goes back up for approval, and the organization calls that fear “precision.”

Of course, speed is not a virtue by itself. A one-way decision cannot be pushed downward under the slogan of agility. Decisions such as long-term commitments, sensitive contracts, difficult choices affecting customers, high-risk operational changes, or decisions involving the organization’s reputation should deliberately be made more slowly and with more scrutiny. The important difference is that this slowness should be reserved for matters that are genuinely sensitive.

A manager who wants to apply this model should start with one real bottleneck: a place where small requests repeatedly get stuck. Collect the recurring decisions at that point, review the cost of reversing each one with the team, write down the authority boundaries, and create a clear path for exceptions. Then, after some time, examine which decisions are still being escalated without good reason. Usually, the issue is not too few meetings; it is unclear decision boundaries.

A fast organization is not one where managers say “yes” more quickly. It is one where people do not wait for “yes” at all on decisions that can be corrected. In that organization, managers spend their time on decisions that truly carry a cost of reversal, and teams learn to decide within clear boundaries, observe the result, and adjust. It may be a small change in authority design, but its effect shows up directly in execution speed.

Decision speed does not come from removing every control. It comes from putting control in the right place. If every decision must pass through the manager’s door, that door will sooner or later become a wall. But when reversible decisions are made where the work happens, managerial approval regains its real value: protecting the decisions that truly must not be made carelessly.

This week, look at one approval queue in your work. Not to see who is slow, but to identify which decisions should not be in that queue at all. This change, more than a new tool or another meeting, can give time back to the team.

When small decisions are made on time, the manager also gains room to think instead of sign off; to design boundaries better instead of responding to every request; and to build a system that works without constantly stopping at their desk rather than becoming the center of everything.

This is where system building goes beyond forms and processes — and connects back to what was said earlier about delegation: delegation means transferring responsibility within a clear boundary, not just spreading tasks among people. A good system does not merely create referral paths; it recognizes what should not be referred in the first place. An organization that takes this distinction seriously becomes both more accountable and faster, without sacrificing judgment for speed.

In the end, the management question is simple: which decision can be corrected at limited cost if it is wrong? If the answer is clear, that decision probably does not need to wait outside the manager’s door.

Take reversible decisions out of the approval queue, but do not do it through a broad and vague announcement. Define the boundaries, make the red lines clear, review outcomes, and let the team decide within its territory. At first, this may feel like losing control. But it is often the first step toward building real control: control based on clear rules and team learning rather than the manager’s constant presence.

Good management is not about gathering every decision on the manager’s desk. Its craft lies in identifying the decisions that should never have needed to pass over that desk in the first place.