Why work dies in a group chat

Here is a message that will be sent in a few thousand businesses today, at around twenty to twelve.

“Can someone ring Mrs Diaz back about the warranty?”

Four people read it. All four assume somebody closer to it will pick it up, and all four are right that somebody should. Nobody does. On Friday, Mrs Diaz rings the owner.

Nobody in that story was lazy and nobody lied. The message simply never became one person’s job, and a group chat has no mechanism to make it one.

Diffusion of responsibility, in software form

Psychologists have a name for this and it long predates WhatsApp: the more people who witness something that needs doing, the less likely any individual is to do it. It is why crowds watch and why committees stall.

A group chat industrialises it. Every request goes to everybody, which means every request arrives with the implicit note “somebody deal with this”. And critically, reading a message is not accepting it – but in a group chat the two look identical. Two ticks tell you it was delivered. They tell you nothing about whether anybody took it on.

The important consequence: this gets worse as your team grows, not better. A group of three is nearly self-correcting, because each person knows that if they do not do it, the odds are it falls to them anyway. A group of nine has no such pressure at all.

The fix costs nothing

Never post a request to a group without a name attached, and treat a request without a name as not yet made.

“Ravi, can you ring Mrs Diaz today about the warranty?”

That is the whole change. It feels blunt for about a week and then it feels normal, and the awkwardness is the point – it is the moment somebody either accepts the job or says they cannot. A group request is designed, structurally, to let everybody skip that moment.

Three things make it work properly:

• If you do not know who should do it, that is the real problem. Decide, then ask. A nameless request is usually an undecided one wearing a disguise.
• Ask for one word back. “Yep” or “can’t today” – so that reading and accepting stop looking the same.
• Accept a no. If the first person who says “can’t today” gets a hard time, everybody else learns to read and stay quiet, and you are back where you started with extra resentment.

Then move the work out of the group entirely

Naming people fixes ownership. It does not fix the second problem, which is that you still cannot ask a group chat what is outstanding. There is no query. There is only scrolling, and scrolling finds what you already remember to look for.

So the next step is to stop using the group for work at all. Keep it for coverage, swaps, notices and the social glue, which it is genuinely good at. Move anything with a deliverable or a deadline into a one-to-one chat with the person doing it.

In a one-to-one chat, responsibility is unambiguous by construction: there is one other person, so there is nobody for either of you to assume about. It has a second benefit owners consistently underrate – a reminder about late work becomes private. Nobody has to be told about somebody else’s slipping job in front of the whole team, which changes how people respond to being chased.

What you have and have not solved

With names in every request and work in one-to-one chats, you have fixed ownership and you have made chasing humane. You have not built a list. You still cannot answer “what is overdue?” without asking people, and you are still the only person holding the picture.

For a lot of teams that is fine, and it is worth being honest that these two free changes do most of the work. The point at which it stops being fine is measurable rather than a feeling: count the hours you spent chasing this week, and count the times a customer told you about something before your team did. If those numbers are small, you have already won. If they are not, the problem is no longer discipline.

The full guide to running a team on WhatsApp sets out all four fixes in order of what they cost, starting with the two above.