The Ownership Gap: Why Requests to a Group Rarely Get Done
It's rarely about effort. It's about who thinks it's their job.
A request goes out to five people. A few days pass. Nothing comes back.
Not because anyone refused. Not because the task was too hard. The request simply never became anyone's specific job.
This is one of the more overlooked reasons initiatives lose time. It rarely gets flagged as a communication problem or a planning problem. It just shows up as delay.
What Actually Happens When a Request Goes to a Group
When a task is addressed to a team instead of a person, each recipient scans it, assumes someone better positioned will take it on, and moves back to whatever's already in front of them.
The intent behind this is often good. Nobody wants to seem like they're ignoring a colleague, and few people want to claim ownership of something that wasn't clearly theirs to begin with. The result, though, is the same regardless of intent: broad visibility without a clear owner functions, in practice, like no owner at all.
The Cost Shows Up Later, Not Immediately
The first missed deadline rarely feels significant on its own. A leader waits a few extra days, unsure whether the delay is normal lag or an actual problem.
By the time a follow-up happens, the original request has usually been buried under newer messages. What follows is a second, smaller delay: rediscovering who was even supposed to be handling it.
On a single request, this costs a few days. Across a critical initiative with dozens of moving requests, the pattern compounds into weeks that are difficult to trace back to any one cause.
Two Elements Every Request Needs
Correcting this doesn't require new software or an additional layer of process. It requires two specific elements, applied consistently.
- A named owner. Not the team. Not the group. One individual, named directly, responsible for the outcome.
- A named deadline. Not "soon" or "when you get a chance." A specific date, clear enough that both sides know exactly when to expect it.
Without both, a request functions as an assumption rather than a plan, and assumptions are difficult to follow up on because no one is quite sure who should answer for them.
Building This Into How a Team Operates
This approach tends to work best as a habit built into how requests are made, rather than a one-time correction.
A few practical starting points:
- Before sending a request involving more than one person, identify who specifically owns it.
- Replace "let me know if anyone can help with this" with a name and a date.
- If a task genuinely requires input from several people, assign one coordinator responsible for pulling it together, rather than leaving it open to whoever responds first.
- When following up, follow up with the named owner directly. This reinforces that the ownership was real, not symbolic.
None of this removes every delay a team will face. Priorities change, and even well-assigned work can slip. But naming an owner and a deadline eliminates one of the most common and most avoidable causes of stalled work: no one knowing whose job it was in the first place.
At The Soomitz Group, we help operational leaders and their teams build the execution structure, ownership, and rhythm that turn critical initiatives into measurable outcomes, not just completed to-do lists.
A single unclear request rarely feels significant on its own. But across a busy initiative, these small ownership gaps are often what's slowing everything down. Eventually, that shows up as missed deadlines, strained budgets, or a leader having to explain a delay they didn't cause.
Connect with us to explore how we can help.
