At a recent Legalboards Academy session, Gimbal Consulting's Karen Dunn Skinner and David Skinner told the story of a lawyer they'll call Sarah. She'd run her own firm for eleven years. Good reputation. Clients who genuinely loved her. By every external measure, she'd built exactly what she set out to build. You can watch the full Pop the Cork replay on the landing page.
The first thing she said on a call with them was: "I feel like I work for my practice. It's not working for me."
She hadn't taken a real vacation in years. Not because she couldn't afford one. Because she didn't believe the practice would survive without her.
That's not a discipline problem. It's a law firm coordination problem, and it shows up the same way in almost every small and mid-sized firm: the person holding everything together becomes the person everything waits on. For the broader picture, see the law firm coordination problems guide.
You're not the problem. Your firm has no structure to delegate into.
The default explanation lawyers reach for is personal: I need to be more organized, more disciplined, better at time management. But talk to enough firms and a different pattern shows up. The lawyers struggling aren't bad at their jobs. Some of them are the best in the room. They're struggling because of how the practice was built, not because of who they are.
Picture carrying a backpack full of bricks around all day. Eventually your shoulders hurt, you slow down, you get frustrated. Someone looks at you and says: you know what your problem is? Stamina. You just need to build more stamina.
That's not the right question. The right question is why you're carrying the bricks at all.
Most law firm owners spend the majority of their time on work that has nothing to do with why clients hired them, why the practice grows, or why revenue moves. Meanwhile the work that actually drives those three things, the work only they can do, gets whatever hours are left over. That's not a character flaw. It's a coordination problem: nobody defined which work belongs where, so everything defaults to the person already holding it. The broader legal operations foundations guide covers the operating model behind that structure.
The real cost of the wrong work
Most firms never run this number, so here it is.
Say your effective rate for your highest-value legal work is $400 an hour. Say you spend two hours a day on work that someone else could do faster, and for a fraction of the cost. You're not saving money doing it yourself. You're losing it. You're replacing $800 of potential revenue with tasks that could be done for $50 to $100.
Run that across a week, then a month, then a year. For most firms that do this calculation for the first time, the number lands somewhere between $50,000 and $150,000 in revenue absorbed by the wrong work, every single year. Not lost to a slow economy. Not lost to bad marketing. Lost to misallocation: the highest-paid person in the building doing work priced for someone earning a fraction of that rate.
A fast way to check where you stand: list five things you did this week. Sort each into two categories - work that genuinely requires your license, judgment, or expertise, and everything else. If two or three landed in "everything else," you're not unusual. If four or five did, you're not unusual either. You're the bottleneck, and now you know why. Office managers can use the same exercise to make firm-wide workload visible.
Why delegation keeps failing
Most people think delegation means handing someone a task. If they don't do it right, they failed.
That's the myth. The reality is usually the opposite: delegation fails because the work was never clearly defined, the process wasn't documented, and decision-making authority was never actually handed over. Those aren't people problems. They're design problems, which means they can be redesigned. The first step is making sure every task has one visible owner, as this task-ownership model explains. When work changes hands mid-matter, this guide to law firm handoff problems shows where the same gap appears.
A delegation system that holds has three parts.
Clarity. Every delegated task needs a definition of done: what finished actually looks like, what quality standard applies, what the output needs to include. A vague brief produces vague results, every time. "Draft the memo" is not a definition of done. "This memo is finished when the citations are checked, the formatting matches our style guide, and the three most likely scenarios for the client are flagged" is.
A documented process. Every recurring task needs a written record of how the work actually gets done: the steps, the tools, the templates. Without it, you're asking someone to reconstruct your expertise from memory every time they touch the file. That isn't delegation. That's guessing.
Clear decision authority. One of the most common reasons work boomerangs back to the owner is that nobody defined which decisions the delegate is allowed to make alone, and which ones need to come back for a sign-off. When that line isn't drawn, people default to caution and route everything back to you, not because they can't handle it, but because nobody told them they were allowed to.
What holds the system together once it's designed
Design solves the theory. What holds it together day to day is a different question, and it's the one that usually breaks first.
During that same session, Karen put it directly while walking through this exact framework: "This is where a workflow tool like Legalboards can really help. Your instructions, your definitions of done, all of that can be hard baked in, which makes it visible and super easy to follow."
That's the piece most delegation advice skips. A definition of done that lives in your head, or in an old email thread, isn't a system. It's a memory test, and memory is exactly what breaks under a caseload. Structured workflow does for delegation what a documented process is supposed to do on paper: it makes the definition of done, the process, and who owns the next step visible to everyone touching the file, not just the person who wrote it down once. That visibility matters most when a new person joins the team; see how new paralegals slow a law firm down for months and what partners miss about workflow structure.
What to do this week
Pick one task you keep doing yourself that doesn't require your license or judgment. Write down, in one paragraph, what "done" looks like for it. Hand it off with that paragraph attached, and name one decision the person can make without checking with you first.
That's the whole first step. It won't fix the $50,000 problem by Friday. It will show you, immediately, whether the work was actually too complex to delegate, or whether it was just never designed to be handed off in the first place. For most firms, it's the second one.
FAQ
Why does delegation fail even with a good team?
Almost never because of the team. It fails because the task was never given a clear definition of done, a documented process, or real decision-making authority, so the delegate has no way to know what success looks like or what they're allowed to decide on their own.
How do I calculate what the wrong work is actually costing me?
Take your highest effective hourly rate, multiply it by the hours per day you spend on work someone else could do, and compare that to what it would actually cost to have someone else do it. Run the gap across a year. Most firms land between $50,000 and $150,000.
What's the fastest way to fix this without hiring anyone new?
Start with one task already on someone else's plate that keeps coming back to you. Write a one-paragraph definition of done for it and hand over one specific decision they're now allowed to make without asking first.
Watch the full session this piece is drawn from: Gimbal Consulting's Karen Dunn Skinner and David Skinner walk through the complete framework, live, in Pop the Cork: How to Stop Being the Bottleneck. Firms ready to test structured delegation can start a free trial.
