Editorial note: This article is a fictional reconstruction of situations businesses may face. Its purpose is to inform and raise awareness about possible risks and responses. People, events, data and outcomes should not be interpreted as actual cases, verified facts or results achieved by LC. Each organization needs its own assessment.
“I already delegated that,” Andres says while answering a delivery question, approving a change and correcting a proposal. In this fictional story, he leads a business built around his experience. The team does the work, but decisions keep returning to him. What would make delegation more than redistributing tasks?
The task changed hands. The decision did not
Andres asked Elena to coordinate deliveries. He explained how to update the file, but not what she could promise a customer when delays arise. She asks about every case because she does not know her decision boundaries. From outside, it may look like a lack of initiative; from her position, deciding could mean breaking a promise.
Their first agreement would clarify the expected outcome: current information, accountable owners and customer responses for delivery commitments. Then they would define which decisions Elena can make to support it.
Three boundaries that make autonomy possible
They could separate decisions into three groups: those Elena can make, those requiring consultation and those requiring immediate escalation. Updating a delivery status is not the same responsibility as changing a commercial commitment. Boundaries must fit the role and operation.
Andres would also need to share the necessary information. Asking for judgment about a delivery date makes little sense if only he knows availability. Autonomy requires access, context and understandable limits alongside a task assignment.
Support the work without taking it all back
Imagine a short midweek review. Instead of silently correcting the file, Andres would ask how Elena handled a case, which alternatives she considered and where she was uncertain. They could clarify a rule before the problem recurs.
If an error appears, they would distinguish missing information, an unclear boundary and an execution skill that needs practice. That conversation helps adjust support. Automatically reclaiming every decision would preserve the dependency they are trying to change.
Success does not mean the questions disappear
In this story, progress would mean Elena can explain a decision, recognize when to escalate and maintain follow-up with the available tools. New questions would still arise. The team would turn what they learn into a short guide they can use and update.
Start with one responsibility in your own business. Define the outcome, decision boundaries and review point. You do not need to transfer all your experience in a day; the next decision needs reasoning that someone else can understand.
Delegation works better when you share the outcome, the reasoning and the boundaries for deciding.
BRING IT TO YOUR BUSINESS
Three questions to get started.
- Which decision keeps coming back after I assign the task?
- Does the person have enough context, information and authority?
- How will we review a case without my taking all the work back?
Does this sound like a challenge in your business? We can start with a conversation.
Talk to LC↗