Why every task needs one name

What actually happens on the call

A family talks it through. Someone should ring the county office about the application. It is agreed, out loud, by everybody. Nobody says a name, because saying a name feels like assigning work to a sibling and that is uncomfortable in a way the group avoids.

Two weeks later the application has not moved. Nobody dropped it, because nobody was holding it. Each person remembers the same conversation and remembers it ending in agreement, which it did. What it did not end in was a name.

Why this is structural rather than a failing

Diffusion of responsibility is one of the most reliably reproduced findings about how groups behave: the more people who could act, the less likely any given one does. It is not laziness and it is not indifference. It is what happens by default whenever an action is owed by a group rather than by a person.

Which means it does not respond to trying harder, or to caring more. Families in this situation are already trying as hard as they can and already care a great deal. The only thing that reliably changes the outcome is changing the structure so that agreement is not the last step.

The rule

A task without a name on it is not a task. It is an intention. Care Follow-Through shows unowned work as unowned, prominently and by default, rather than letting it sit in a list looking the same as the work somebody is actually doing.

Claimed, never assigned

The obvious fix is to hand tasks out. We deliberately do not, and this is the design decision this page exists to explain.

An assignment made by a system is a claim about what somebody else's week can absorb, and the system knows nothing about that. It does not know who is between jobs, who is unwell, who is already carrying most of this, or who two of the others are not currently speaking to. Getting that wrong in front of a family under strain does damage that outlasts the task.

So a person takes something on. The system's job is to make the gap visible and to keep it visible until somebody closes it, which is a smaller and much more defensible job.

What an owner is actually promising

Not to do it immediately. Not to do it alone. Only to be the person who knows the current state of it, so the answer to "where are we with the application" is one question to one person rather than a group thread that produces four partial answers.

That is a far lighter commitment than it sounds, and saying so out loud is what makes people willing to take things on. The heaviest part of a shared task was never the task. It was the ambiguity around it.

What happens when nobody takes it

It stays visible and it keeps being named. It does not silently age into the bottom of a list, and it is not reassigned by the system to whoever seems most available. An unowned task that stays unowned for long enough is a genuine signal about capacity, and it usually means the family needs help from outside rather than a better reminder.

This is what Family Observatory is built to hold: the board where an unowned responsibility stays visible until a person takes it, rather than a group thread where agreement is mistaken for a plan.