When several people could answer, deciding who actually does

It fails in two directions, and they look nothing alike

Put one person on the receiving end and the arrangement is obvious: they go. Put three on it and two distinct failures appear, often in the same week.

Nobody goes. Each person sees the message, assumes one of the others is closer, freer or already moving, and waits. This is well documented outside the home — it is why first-aid training teaches you to point at one person rather than shout for help — and it gets worse as the group grows, not better.

Everybody goes. Two people drop what they were doing for the same request. This one is less discussed because it looks like enthusiasm, but it is expensive: it burns goodwill in the people who came for nothing, and it teaches the person who asked that a small request causes a commotion. That is a reliable way to stop them asking.

Both come from the same missing piece. Nobody can see what anyone else is doing.

Make the answer visible, not just the request

Most setups broadcast the request and then go quiet. Everyone learns that a message arrived and nothing about what happened next — so each person reasons in the dark and reasons differently.

The fix is dull and effective: say out loud that you are taking it, in the same place the request arrived, before you set off. One word will do.

Request: Kitchen — I need a hand

Reply, immediately: mine

That single word removes both failure modes at once. Nobody assumes it is covered when it is not, and nobody sets off for something already handled. It has to come before you go, not after you arrive, which is the part people get wrong — by the time you have arrived, the second person is already halfway there.

Name a default person for each part of the day

Visibility fixes the collision. It does not fix the pause where everyone waits to see who claims it, which is the one the person who asked actually feels.

Agree in advance who is first for each block: weekday mornings, evenings, weekends, whatever shape your week has. The default person goes without waiting. Everybody else moves only if the default says they cannot, or if nothing has happened after an agreed few minutes.

This is a lighter thing than a rota. Nobody is on duty and nobody is off the hook — it only settles who moves first, which is the only question that was causing the delay.

“Whoever is nearest” is not an arrangement

It sounds like the sensible default and it is the most common cause of the pause. Nobody knows where anybody else is, so everybody estimates, and the estimates disagree. The person who is genuinely nearest is often the one who assumes somebody else must be nearer.

Distance is worth using as a tiebreaker once somebody has claimed a request out loud. It does not work as the rule that decides who claims it.

Tell the person who asked, not just each other

Coordination is usually treated as a conversation between the responders, with the person who asked left watching a device that has gone quiet. From where they sit, “somebody claimed it and is walking over” and “nobody has looked at their phone” are the same thing: silence.

A short reply back to them — on my way, five minutes — is worth more than it looks. It ends the uncertainty, and it removes the reason people press a second time or give up and do the thing themselves.

Look at who actually went, every so often

Load distributes itself unevenly and quietly. The person who answers fastest gets asked most, not because anyone decided that, but because they are reliably first — and they are usually the last to say so.

If you can see who answered, look back over a couple of weeks now and then. It is a much better basis for a conversation than anybody’s impression, and it tends to be a surprise to at least one person in the group. It is also the only way the person carrying the most gets to find out without having to complain first.

What this page will not tell you

We build software for sending a short message to somebody who agreed to receive it. That is the entire extent of what we know, and these pages stay inside it.

• How to divide care between family members fairly. That is a conversation about money, distance, work and history, and no page written by a software company should have an opinion about it.
• Rotas, contracts, or anything a staff team has to satisfy an employer or a regulator with.
• What to do when the disagreement is really about something else. Often it is, and that needs a person rather than a process.
• Anything about the level of support somebody needs, which is between them and whoever assesses it.