Leadership Through Change/November 9, 2026/5 min read

    By Rob Cupello, CMC

    The Decisions Your Team Should Be Able to Make Without You

    Delegated tasks still stall when authority is unclear. Give one recurring decision an owner, practical boundaries and an escalation trigger, then review how it works.

    You finish a meeting, open your messages and find a small queue waiting for you.

    Can we move that delivery? Can we handle this customer request? Can we send the revised proposal? Can we go ahead with the approach we discussed?

    Each question seems reasonable. Together, they can turn the leader into the place where work waits.

    It is tempting to respond with, “I wish people would take more ownership.” Before saying that, I would ask whether they actually know what they are allowed to decide.

    Delegating a task and delegating a decision are different things. You can give someone responsibility for the work while keeping so much authority that they still need you at every turn.

    Start with the approvals that keep coming back

    For a week, notice which decisions arrive at your desk repeatedly. Don't create a complicated tracking system. A short list is enough to start a useful conversation.

    Which requests genuinely need your judgment? Which need information only you currently have? Which come to you because that is how things have always worked?

    Include the waiting involved. A decision that takes you thirty seconds may leave someone else unable to move for an afternoon. The cost isn't only the time you spend answering.

    Then ask the team why they escalate. Perhaps the boundary is unclear. Perhaps two managers have different expectations. Perhaps the last person who made a reasonable call was corrected in front of everyone.

    Those are different problems. Telling people to be more confident won't resolve all of them.

    Separate the decisions by consequence

    Some choices are relatively easy to reverse. Others create commitments that are expensive, difficult or inappropriate to undo.

    Resequencing routine work within an agreed deadline is different from promising a new delivery date to a major customer. Choosing an approved supplier is different from entering a new contract. The person closest to the task may be able to make one decision while needing help with the other.

    Reversibility is useful, but it isn't the only consideration. Customer impact, cost, expertise and responsibilities to other people also matter.

    The aim is to make authority clear enough that people can use their judgment. It isn't to transfer every difficult decision away from the leader.

    Make the boundary usable

    “Use your best judgment” can be an invitation. It can also be a guessing game.

    Imagine a hypothetical service team handling a customer's request to rearrange work. The team lead is responsible for the schedule but asks the owner before agreeing to any change. Everyone is frustrated: the owner wants fewer interruptions, and the team lead doesn't want to make a promise they cannot keep.

    They could define the decision this way: the team lead can rearrange work within agreed customer commitments when capacity is available and other confirmed work is unaffected. A change that needs additional resources or alters another customer's commitment must be escalated before it is promised.

    That is a fictional example, not a report of a client engagement. The useful part is the distinction. The team lead has room to act, and everyone knows when another conversation is needed.

    Build a one-page decision-rights sheet

    Choose one recurring decision and complete five fields together:

    Decision: What specific choice are we discussing? Owner: Who can make it and is accountable for following through? Boundary: What conditions must remain true? Escalation trigger: What changes require another person's involvement? Review date: When will we check whether this arrangement is working?

    For the scheduling example, the owner is the team lead. The boundary is available capacity within existing commitments. The escalation trigger is a request that exceeds that capacity or affects another promise. The review date might be two weeks after trying the arrangement.

    The wording should be plain enough that two people would interpret it the same way. If “reasonable cost” produces five different answers, it needs a clearer definition.

    Also decide who handles an escalation and how quickly they need to respond. A beautifully written boundary is not much help when the next decision still disappears into someone's inbox.

    Give people what they need to decide

    Authority without information can put someone in a difficult position. Before handing over a decision, check that the owner can see the relevant commitments, resources and customer context.

    They may need a short explanation of how you weigh the tradeoffs. Talk through a typical case and an exception. Ask what would make them pause and what they would do if you were unavailable.

    This is where a leader's experience can become useful to the team. Explain the reasoning that usually stays in your head, rather than supplying the answer to every new request.

    You may discover that someone needs practice or support before taking full ownership. That is a practical development need, not proof that delegation cannot work.

    Review the pattern without taking every decision back

    At the review date, look at what happened. Did work move with less waiting? Were commitments kept? Which exceptions were escalated? Did anyone discover a boundary that was too vague?

    Ask whether a disappointing outcome came from poor judgment, missing information or an unclear agreement. A reasonable decision can still produce an imperfect result.

    If every imperfect result causes the leader to reclaim authority, the team learns that asking first is the safest option. Review decisions fairly and tighten the arrangement where the evidence warrants it.

    You don't need to redesign the whole organization this week. Pick one decision that regularly lands on your desk. Agree on an owner, usable boundaries and a review date, then give the arrangement a chance to work.

    What decision still reaches your desk that your team could own with clearer boundaries?

    Back to all articles Share on LinkedIn

    Related articles

    We use Google Analytics to understand how this site is used. You can turn analytics off here. Privacy policy