Delegate the Task, Keep the Decision, and Nothing Changes

You handed off the client update letters last spring. Someone else drafts every one of them now, and every one still crosses your desk before it goes out. You change a word here, soften a line there, and send it back. Six months later your week looks exactly the way it did before the handoff, and you're starting to wonder whether delegation works at all in a firm like yours. It works. What you handed off was the typing. The decision about whether that letter is good enough to leave the building with the firm's name on it stayed with you, and that decision is where your time was going all along. Of all the ways delegating decisions in a claims firm goes wrong, this is the one I see most: the owner hands off the task, keeps the decision, and gets the look of delegation with none of the relief.

Every Task Has a Decision Inside It

Almost every piece of work in a firm has two parts. There's the doing, which is drafting the letter, pulling the documents, building the schedule, or processing the invoice. Then there's the deciding, which is whether the letter is ready, which file goes first, whether the invoice gets paid or questioned, or whether a new file is one the firm should take at all. The doing is usually the bigger share of the hours. The deciding is what determines whether the work is finished.

When you hand someone the doing and keep the deciding, you've given them a job they can't finish. They do the work, set it on your desk, and wait. The person you hired to take something off your plate has become a preparer, and you've become the reviewer of everything they prepare. Owners tend to call this oversight. From the other side of the desk, it looks a lot more like a line.

The tell is in the language. Listen to how work gets handed off in your firm. "Draft it and let me see it." "Get me the numbers and I'll decide." "Run it by me first." Each of those sentences moves a task and pins the decision in place. Said once, none of them is a problem. Said fifty times a week, they're the reason nothing on your calendar changed.

Why Keeping the Decision Costs More Than Doing the Work

Owners assume a review is quick. Reading a letter takes three minutes and writing it takes thirty, so keeping the review should save twenty-seven. It rarely works out that way.

You review cold. The person who drafted the letter knows the file, and you're reading it between two other things, so you either skim and approve or stop to rebuild the context they already had. The approval step is also a queue. The letter doesn't wait three minutes for you. It waits until you get to it, which on a busy week means days, and the client waits with it. And every change you make teaches the team something. If most drafts come back with edits, the people writing them learn that their draft is a starting point for your version. They stop pushing for the final answer, because the final answer was never theirs to give. Quality drifts down, your edits go up, and the review you kept for safety looks more necessary every month.

That loop is why owners who keep decisions are so sure they need to. The evidence they're looking at was produced by the arrangement itself.

William Oncken and Donald Wass described a version of this in a 1974 Harvard Business Review article, "Management Time: Who's Got the Monkey?" Their monkey is the next move on a piece of work. Every time a manager tells an employee they'll think it over and get back to them, the monkey jumps from the employee's back to the manager's. More than fifty years later, the owners I work with are still collecting monkeys, and most of them arrive attached to a task the owner already delegated.

Information, Permission, Outcome

Handing off a decision isn't all or nothing, and treating it that way is what scares owners off. Mike Michalowicz lays out three levels in Clockwork, and they're the clearest way I know to hand off a decision in stages.

• Information. The team member gathers the facts and brings them to you. You decide.

• Permission. The team member brings a recommendation and asks for approval. You decide whether to accept it.

• Outcome. The team member decides, acts, and tells you what happened.

Most owners who say they've delegated something are running it at permission. That's a sensible place to start, because it lets you see how someone thinks before you let them act on it. It's a bad place to stay. Permission still routes every decision through you, so the queue, the cold reviews, and the teaching effect are all still there. The only change is that someone else fills in the form.

The quickest way to know a decision is ready to move up is to watch how long you take to approve it. If a permission-level request lands in front of you and you can approve it in under two minutes without changing anything, you aren't adding judgment. You're adding delay. That decision belongs at outcome.

This is also where the $1, $10, and $100 work model earns its keep. The value belongs to the person, not the task. Approving a routine letter is $1 work for an owner. For the person who knows the file and the client, deciding the letter is ready is part of the $100 work they were hired to do, and they'll usually make that call better than you would reading it cold at six in the evening.

Hand Over the Decision With the Limits Attached

What owners are actually afraid of is a decision with no edges. Nobody wants a new team member deciding everything about client communication in their first week. So don't hand over everything. Hand over one decision with its limits written down.

Pick a task you've already delegated but still approve, and write one page that answers four questions. What exactly does this person decide on their own? Where are the limits, whether that's a dollar figure, a type of client, a departure from the usual process, or anything that commits the firm to something new? What still comes to you, written as a short list rather than a vague sense of "the important ones"? And how will they tell you what they decided, which should be a weekly summary rather than a message for every item?

Then say it out loud. Tell the person the decision is theirs inside those limits, and tell the rest of the team, so nobody routes around them to reach you. Your job changes from approving each item to reviewing the pattern once a week. If the pattern holds up, widen the limits. If it doesn't, tighten them and explain why.

The limits are what make it safe to let go. A decision with clear edges can go to someone six months into the job. A decision with no edges can't go to anyone, which is why so many of them never leave the owner's desk.

The First Thirty Days Will Go Badly

Nobody gets through this cleanly on the first round, and most don't on the third. The usual pattern is that the owner expects it to go fine, a crisis lands in the first two weeks, and the owner takes every decision back and swears never to try it again. The crisis is real. A letter goes out in the wrong tone, a vendor gets paid when the invoice should have been questioned, or a client calls you directly to complain about a call your team member made.

What you do next decides whether the handoff survives. Taking the decision back teaches the team that the limits were never real, and the next handoff gets harder. Adjusting the limit teaches them where the edge actually sits. Ask what the person knew, what they didn't, and which line on the one-page handoff would have caught it. Fix that line and run the next round. Then weigh the cost of the mistake against the cost of routing every one of those decisions through you for another year. Most of the time it isn't close.

Deciding Who Decides Across the Leadership Team

Clearing your own approvals is a good start. The bigger change comes when your leadership team maps which decisions sit with whom, at which level, and inside which limits, so the whole firm stops waiting on one desk. That's a large part of what we do in a VIP Intensive. Your leadership team spends three days with us at our office, with you in the room for all three, sorting the firm's recurring decisions and settling who owns each one. Fourteen days later, you get a written plan to run it.

If you want to know whether that fits your firm, book a twenty-minute discovery call.