The folder is shared. The group chat has everyone in it. The calendar invite went to the whole family.
And you are still the one who gets the call.
Shared is not distributed
Giving someone access to a folder doesn't move responsibility. It moves the files. Distributing a piece of care takes three things: the context to understand it, the authority to decide, and someone who follows up without being reminded.
The same goes for help. Running an errand isn't the same as answering for the result. The complaint we hear most is exactly that: everyone helps, but no one takes over. Helping is not owning.
Five reasons care still runs through you
When a responsibility keeps coming back, it's usually for one of five reasons:
- Knowledge. It lives in your head.
- Information. It exists, but no one else can find it.
- Access. Someone could do it, but they can't log in, sign or call.
- Next step. They don't know when to act.
- Autonomy. Every exception still comes back to you.
Naming the reason tells you what to fix. A thread stuck on access needs a login or a permission. A thread stuck on knowledge needs to be written down before anyone can take it.
Move it one step up
Pick one thread. Not all of care at once. Then make it findable, then runnable, then shareable. If there is no one to hand it to, reduce it instead.
Which of your threads is stuck on access, and which one is stuck on knowledge?
