Two People Doing One Job Isn't Coverage, It's a Symptom

ConsultEvo's Evrim Aslan names the pattern precisely: "two people answer the same issue while another customer waits." Adding a second person to a role that looked overloaded should mean more gets covered. In practice it often means the same thing gets answered twice while something else gets missed entirely, because nobody was ever assigned that second thing specifically.

Responsibility isn't ownership

Aslan draws the distinction that explains why: "responsibility means someone contributes to the work. Ownership means one person is accountable for making sure the work moves forward." Many people can be responsible for a client relationship. Exactly one person should own whether a specific question gets answered. Put two people on the same responsibility without deciding which one owns which piece, and the result is "fragmented ownership," not coverage.

What this looks like in practice

The scenario Aslan describes should be familiar to any agency running more than a handful of clients: a client sends a question, and "account management, delivery, and ops each assume someone else will respond." Nobody is being lazy. Each person genuinely believes the question is covered, by someone else, which is exactly why it sits unanswered longer than it would have with one person clearly on the hook.

Why more headcount doesn't fix this

This looks like a capacity problem, so the instinct is the same one behind the hiring trap: add a person. But a second person on an already-ambiguous responsibility doesn't add capacity, it adds a second person who can also assume someone else has it. The same gap shows up when specialization splits an account into three narrow views instead of one whole picture: more people touching the account, nobody accountable for all of it.

What actually closes the gap

The fix isn't reducing headcount back to one person per role, several people can still be involved. It's making sure every specific item, this question, this deliverable, this client request, has exactly one visible owner assigned to it, so "someone else has it" is never a guess anyone has to make. The same principle behind revenue per employee applies here too: the fix a low number points to often isn't the headcount, it's whether the people already there have clear, non-overlapping ownership of what they're responsible for.

Where this fits into the bigger picture

This is the same reasoning behind automating the boring 80% of agency ops: a system that routes work to one named owner removes the guessing a person would otherwise have to do. See how workflow design assigns clear ownership to every item that needs it, instead of leaving "who's got this" as something two people both assume the other already answered.