Blurry Roles and the Things That Fall Through
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Some problems in a business aren't anyone's fault, exactly — they happen in the gaps. A task that sits between two people's roles, where each assumed the other had it, so no one did. A customer who slips through because it wasn't clearly anyone's job to follow up. When roles are blurry, things don't get dropped through negligence; they get dropped because they were never clearly anyone's to hold. Blurry roles create a specific kind of failure: the dropped ball no one is responsible for, because responsibility was never clearly assigned.
CLEAR ROLES BLURRY ROLES
[ Person A owns X ] [ A does some of X... ]
[ Person B owns Y ] [ B does some of X... ]
nothing between them [ ← things fall here → ]
→ nothing falls → the gap swallows the ball
─────────────────────────────────────────────────────────
Dropped balls live in the space between undefined roles.Owner symptoms
Things fall through the cracks, and no one's clearly at fault.
"I thought you had it" is a familiar phrase on your team.
The same kinds of tasks keep getting dropped in the handoffs.
Why this happens
In a small business, roles form organically — people just start doing whatever needs doing — and for a while that flexibility works. But it leaves gaps: areas where responsibility overlaps or, worse, where no one clearly owns anything. When something lives in that gap, everyone reasonably assumes someone else has it, so it drops. It's not a people problem; it's a definition problem. Without clear roles, the handoffs and the in-between spaces have no owner.
Common mistakes
Letting roles stay implicit because "everyone just pitches in."
Assuming overlap is safe when it actually creates gaps.
Blaming individuals for drops that are really role-definition failures.
How experienced operators think about it
They pay special attention to the seams — the handoffs and the in-between areas where things fall. Their instinct when something gets dropped isn't to find who to blame but to ask whose was that supposed to be, and was it ever clear? They make roles clear enough that every important thing has a definite owner, especially at the handoffs. Clarity about who owns what, to them, prevents more problems than any amount of reminding.
Practical actions
Map where things get dropped — the recurring cracks.
Clarify who owns what, especially at handoffs and overlaps.
Assign the in-between work explicitly, so gaps have owners.
Fix the role, not the person, when a drop is really a definition failure.
Questions every owner should ask
Where do things repeatedly fall through on my team?
Is it clear, for every important thing, exactly who owns it?
Are my "dropped ball" problems really role-clarity problems?
Frequently asked questions
Why do things keep falling through the cracks?
Usually because roles are blurry, so work that lives between people has no clear owner — everyone assumes someone else has it. Clarifying who owns what, especially at handoffs, closes the gaps.
Should everyone have a rigid job description?
Not rigid, but clear. Flexibility is fine; ambiguity about who owns key outcomes and handoffs is what causes drops. Aim for clarity on the important things, not bureaucracy.
Related articles
My Team Waits for Me — the pillar.
Why No One Owns the Outcome but You — the ownership root.
Setting Clear Expectations — defining what each role must deliver.
Try a free Weekly Focus assessment
If things keep falling through the cracks, clearer roles usually fix more than more reminders do. Throne of Profit's free Weekly Focus assessment is a no-cost way to find the gaps.