تفویضی که از اشتباه می‌ترسد، به مدیر برمی‌گردد

Many managers say they have delegated work, but what they mean is that someone else should perform it—so long as the outcome matches expectations exactly. At the first predictable mistake, the decision returns to the manager’s desk, the person’s authority is narrowed, and the team learns a clear lesson: you have authority, provided you never actually need to use it.

This pattern is not delegation. It is transferring execution while retaining a monopoly over decisions. A manager may reduce their daily task load, but keeps judgment, approval, and tolerance for consequences for themselves. Then they complain about a slow team, dependent people, and a long approval queue—as if these were natural phenomena unrelated to how they lead.

Valid delegation is tested when a delegated decision produces a less-than-ideal result. If someone decided within their authority, based on available information and professional intent, the organization must distinguish between an acceptable error and irresponsible conduct. An organization that cannot make that distinction will inevitably treat every mistake as proof that the person should not be making decisions.

The issue is not defending mistakes. No team matures by normalizing carelessness, concealment, or indifferent repetition of an error. The issue is that a manager must clarify before delegation which consequences are tolerable, which are not, and at what point the person must escalate the matter before acting. Without these boundaries, “make the call yourself” is merely a polite version of ambiguity.

A low-risk mistake usually has a limited, reversible, and observable consequence. In a hypothetical situation, a team lead might change the order of two internal activities and later discover that the choice caused a brief delay in a noncritical task. The error may be irritating, but it should not automatically mean that all future prioritization must remain with the manager.

By contrast, a decision that creates legal commitments, safety exposure, sensitive reputational damage, or a cost that is difficult to reverse is not low risk. The problem begins when a manager puts these two kinds of decisions in the same basket. They then either demand approval for everything or grant authority recklessly and, after the first damage, return to excessive control. Both behaviors reveal an inability to design authority boundaries.

Before delegating a decision, the manager must name the decision in plain language. Not “improve the process” or “manage the project,” but, for example, “choose the order for handling internal requests during this period.” As long as the decision itself is vague, the scope of authority remains vague, and later conversations turn into exhausting disputes over interpretations.

After naming the decision, its boundaries must be recorded: what the decision is meant to achieve, what lies outside the person’s authority, which resources they may use, who needs to be informed, and which signals require stopping or escalation. This does not need to become an elaborate document. A clear, reviewable agreement is more useful than many burdensome frameworks.

The next step is defining the acceptable error threshold. It should not be replaced with a vague statement such as “be careful.” The manager must specify which kinds of consequences, within what range, are accepted as part of learning. They must also make clear when, and with what information, the person should raise an issue after noticing signs of error.

An error threshold is not permission for indiscipline; on the contrary, it makes accountability more precise. The person understands they are responsible for the outcome of their decision, but their responsibility is not measured by an expectation that they can read the manager’s mind. The manager, in turn, commits not to change the criteria later or punish a decision made within the agreed boundary through hindsight judgment.

Hindsight judgment is one of delegation’s common poisons. Once the outcome is known, everything appears obvious: “It was clear you should not have done that.” No, it usually was not clear. The point is not that managers should avoid analysis; it is that they must assess decision quality using the information and constraints present at the time, not merely the result that emerged afterward.

When a decision has a poor result, the first question should not be, “Who is to blame?” A more useful question is: which assumption was wrong, which signal was missed, which boundary was unclear, and what must change in the next decision? This kind of review does not remove accountability. It turns accountability from a performance of punishment into a capacity for correction.

A manager who takes back decisions after every small error is building a reverse-learning system. People learn not to decide, to minimize initiative, and to push every ambiguity upward. The same manager may then complain about a lack of ownership. Ownership in an environment where every minor failure leads to loss of authority is more slogan than organizational behavior.

The sign of performative delegation is simple: the team waits for approval even on routine choices, because organizational history has taught them that the cost of deciding personally is higher than the cost of waiting. In such an environment, the problem is not a lack of individual courage. People are often behaving entirely rationally; they are following a mechanism the manager created through repeated reactions.

To break this cycle, a manager should not suddenly free every decision. The practical path is to begin with limited, recurring decisions whose scope, resources, and consequences are controllable. Authority in these areas must be real: the person decides, acts, reports the consequence, and is not removed from the field at the first misstep.

A short pre-delegation format can create the needed discipline: What exactly is the decision? What are the goal and acceptable criteria? What constraints exist? Which consequences are intolerable? When is escalation mandatory? How will the result be reviewed? These are not administrative rituals. They are the operating contract of authority—something many managers prefer to evade with the phrase, “Just sort it out.”

The review after a decision should also be regular and nonperformative. The person should be able to explain what information they had, which options they saw, why they chose one, and what they would now do differently. The manager should also explain whether the boundaries and necessary information were truly clear. A one-sided review that only interrogates the person simply reproduces the old fear.

A culture of safe error does not mean a soft environment without demands. A safe environment is one where early reporting of a problem, saying “I do not know,” and correcting a decision have value; while concealment, disregard for boundaries, and repetition of an error without change receive a clear response. Psychological safety without standards is permissiveness; standards without safety are paralyzing.

Real accountability is built by joining these two elements: a person has a defined right to decide and is answerable for how they use it. If you demand only accountability, people will throw authority upward to protect themselves. If you grant only authority, without boundaries and review, you create disorder. Mature delegation is neither uncontained freedom nor control hidden behind attractive language.

Managers can run a simple test: the last time someone made an unsuccessful decision within their authority, how did the organization respond? Was the decision taken away from them? Were the criteria changed afterward? Did anyone examine whether the boundary, information, or escalation path had been incomplete? The answers reveal the reality of delegation better than any responsibility chart.

If the dominant answer is that decisions return to the manager after mistakes, the issue will not be solved by motivating the team. First, the behavioral economics of the environment must change: responsible decision-making, even when the result is imperfect, must not be more costly than expensive indecision. Until then, asking the team for “more ownership” is mostly a demand for courage without providing the right to act.

The practical message is simple: delegate authority with clear boundaries, create a learning path for low-risk mistakes, and restrict authority only when conduct or consequences have genuinely crossed the decision contract. Otherwise, the manager remains the primary bottleneck.