'The Team Owns It' Is a Recipe for Nobody Owning It
In 1979, Latané and colleagues demonstrated something uncomfortable: people exert less effort when working in groups than when individually accountable. The larger the group, the stronger the effect. Forty-five years of replication have not been kind to the idea that “the team will figure it out.”
The Diffusion Problem
Social loafing happens because individual contributions become less identifiable as group size increases. If six people collectively “own the backlog,” each person’s mental model is: “Someone else is probably handling that.” Multiply across every ambiguous responsibility on a product team and you get drift. Not because anyone is lazy. Because nobody is individually on the hook.
The Scrum Guide’s Product Owner role exists partly as an antidote. One person owns the backlog. One person makes the prioritization call. Stakeholders know who to talk to. Engineers know whose decision to execute against. The role isn’t about authority — it’s about removing the diffusion that causes 40-person programs to move slower than 4-person teams.
Where It Works
Collective ownership works when two conditions hold:
The task is additive. Multiple people can contribute simultaneously and the sum is greater than the parts. Brainstorming, code review, incident response.
Individual contributions remain visible. Even in group work, if people know their specific input will be identifiable and evaluated, loafing drops. Code review works because your comments have your name on them.
Where It Fails
It fails when the task requires a decision, not a contribution. Prioritizing a backlog is a decision task. Someone has to say: this first, that second, this not at all. A committee produces a ranked list where everything is priority one.
It also fails when the task is sequential and blocking. If the product spec isn’t written, engineering can’t start. If “the team” owns the spec, it’s nobody’s job to finish it by Tuesday.
The Practical Rule
For every artifact, decision, and outcome on a product team, ask: “If this isn’t done by Friday, whose name comes up?”
If you can’t name the person, you haven’t assigned accountability. You’ve distributed it — functionally the same as deleting it.
At Comcast, I was the single accountable PO across five Scrum teams. That wasn’t ego. It was an anti-loafing structure. Stakeholders knew exactly who owned the tradeoff call. Sprint goal attainment hit 98% because there was zero ambiguity about who was responsible.
Social Loafing and AI Agents
When AI agents join the workflow, the diffusion risk compounds. If a team of 5 humans and 3 AI agents “owns” a deliverable, who is individually accountable? The human who wrote the prompt? The human who reviewed the output? The PM who defined acceptance criteria?
Every agent-augmented workflow needs an explicit human owner whose name is attached to the outcome. Not the process. The outcome.
One question for your next planning session: can every person in the room name who owns the outcome? If anyone says “the team,” you have a diffusion problem. I fix this. s@spencervaradi.com.