Count how many times a day someone at your firm asks "did anyone follow up on this?" That question is not small talk. It is a sign that ownership was never actually assigned, only assumed, and [tasks falling through the cracks](https://legalboards.com/workflow-automation) are what happens when an assumption turns out to be wrong.
Why Ownership Defaults to the Wrong Person
In most firms, a task without an explicit owner does not stay unowned for long. It gets picked up by whoever is most senior, most available, or loudest in the moment, not necessarily whoever it was meant for. That might work once. It does not hold up across a full caseload.
The problem shows up in two directions at once. Some tasks get done twice, because two people each assumed the other had not started. Other tasks get done by nobody, because everyone assumed someone else had it covered. Both outcomes come from the same root cause: ownership that lives in people's heads instead of somewhere visible. This is the same structural gap behind many of the [law firm coordination problems](https://legalboards.com/resources/blog/law-firm-coordination-problems) that surface once a firm grows past the size where everyone can track everyone else's work by memory.
This is rarely a hiring or effort problem. Skilled, hardworking staff still lose track of ownership when the system does not force clarity. The gap is structural, not personal.
Why This Is More Expensive Than It Looks
Every "who's on this" question costs more than the thirty seconds it takes to ask. It interrupts whoever answers, in the middle of their own work. It delays the actual task while the question gets resolved. And it repeats, for different tasks, multiple times a day, across every case the firm is running.
None of that shows up as a line item. It shows up as a general sense that the firm is busy but not necessarily moving, and as partners spending time playing traffic controller instead of doing the work only they can do. A firm running on "who's on this" is running on interruption as its coordination mechanism, and interruption does not scale past a handful of people. This is usually the job [office managers](https://legalboards.com/for-office-managers) end up absorbing by default, since they are the ones fielding the interruptions when nobody else has an answer.
What This Looks Like at Different Firm Sizes
At a five or six person firm, this friction is barely noticeable, because the whole team fits in one conversation and everyone roughly knows what everyone else is doing. Somewhere between fifteen and thirty people, the informal system starts to crack: there are enough cases and enough staff that no single person holds the full picture anymore, but the firm is often still running the same "just ask around" habits it had at half the size.
This is also where [whats-task-chain-automation](https://legalboards.com/resources/blog/whats-task-chain-automation) becomes relevant rather than theoretical. A task chain, the sequence of handoffs a piece of work moves through from intake to close, only works if each link in the chain has a name attached to it. Without that, growth does not make the firm more capable, it makes the coordination problem worse, because more people means more possible places for a task to land on nobody's desk.
What Ambiguous Ownership Actually Signals
If ownership is not visible without asking, the firm is running on memory and hierarchy instead of a system. That works fine when the team is small enough that everyone can hold the full picture in their head. It breaks the moment the firm adds a person, a case type, or a busy season, because memory does not scale and hierarchy just means the most senior person becomes the bottleneck for every unclear task.
This is not an argument for more process for its own sake. It is a description of what "who's on this" actually costs once you count it across a week instead of treating each instance as a one-off.
What to Do About It
The fix is not more meetings to clarify ownership after the fact. It is making ownership visible before the question gets asked, so a task with an unclear owner is caught immediately instead of surfacing three weeks later when a client calls asking for an update nobody can give. That system is worth building deliberately, not left to whoever happens to notice the gap first. For the practical version of what that looks like day to day, see [what it actually looks like when every task has one clear owner](https://legalboards.com/resources/blog/what-one-clear-task-owner-looks-like).
**The cost isn't the task. It's every interruption spent figuring out who's supposed to be doing it.**
Frequently asked questions
Why does task ownership become unclear as a law firm grows?
Small teams can track ownership informally because everyone holds the full picture in their head. As the firm adds people and cases, that informal tracking breaks down, and tasks default to whoever is available or senior instead of whoever was actually assigned.
What does it cost when nobody knows who owns a task?
Every unclear task generates interruptions to figure out ownership, delays while that gets sorted out, and sometimes duplicated or dropped work when two people or nobody act on the same assumption.
Is this a training problem?
Not usually. Skilled staff still lose track of ownership when the system relies on memory instead of making ownership visible. The fix is structural, not a matter of training people to remember better.
How can a firm tell if this is happening?
Track how often someone asks "who's handling this" or "did anyone follow up" in a normal week. If the answer is more than a handful of times, ownership is living in people's heads instead of somewhere visible.
Does this mean every task needs a formal assignment process?
It means every task needs exactly one visible owner, not a formal process for its own sake. The goal is removing the guessing, not adding paperwork.
If your firm spends more time asking who owns a task than doing the task, see how visible ownership closes that gap → [app.legalboards.io/register](https://app.legalboards.io/register)
