The meeting ends. The notes are distributed. The action items are listed. One of them reads: "Team to review the proposal and provide feedback."
The team does not review the proposal. Nobody provides feedback. At the next meeting, someone asks about the proposal. Nobody is sure what happened to it.
This is what happens when everybody owns the action item.
The diffusion of responsibility
When a task is assigned to a group rather than a person, each member of the group assumes that someone else will handle it. This is not laziness. It is a predictable psychological response to ambiguous ownership. The more people who are responsible, the less responsible any individual feels.
An action item assigned to "the team" is an action item assigned to nobody.
The anatomy of a collective action item
Collective action items are usually created in one of three ways:
- The organizer does not want to assign it to a specific person. Assigning it to the team feels more collaborative and less like giving someone extra work.
- Nobody volunteered. The action item needed an owner. Nobody stepped up. The organizer wrote "team" to avoid the awkward silence of an unowned task.
- The task genuinely requires multiple people. This is the legitimate case. But even here, one person should be the coordinator — the one who ensures the others contribute.
How to fix it
Every action item needs three things: a specific owner (one person, not a team), a clear deliverable (what done looks like), and a due date (when it needs to be done by).
If a task genuinely requires multiple people, assign a coordinator. "Sarah will coordinate input from the team by Friday" is an action item. "Team to provide input" is a wish.
The rule: If you cannot name the person who will be embarrassed if this does not get done, the action item does not have an owner.