Who this is for
You share one delivery with a small team, and the work crosses between people — a spec goes to engineering, a draft goes to legal, a config goes to ops. Everyone is competent. Things still fall in the seams.
Not a fit if you work alone on a personal checklist with no shared outcome.
How the gap actually opens
Nobody decides to drop something. It happens in small, reasonable steps.
At kickoff, someone says “we'll sort out who does the migration.” It sounds like a decision. It is not written anywhere, and the meeting moves on.
On Tuesday, you ask a colleague to pick up the vendor spec. They reply “sure.” You hear *I own this now.* They mean *I'll look at it after the release.* Both readings are fair.
In week two, the person quietly holding the piece goes on leave. Their part was never on anyone's board, so nothing appears to be missing.
In week three, the delivery slips. There is a meeting. Two capable people say the same sentence in slightly different words: *I thought you owned it.*
Everyone in that room did their job. The finish line simply never had a name on it.
Why “someone's on it” keeps failing
Ownership that lives in hallway memory, a chat thread, or a kickoff deck holds fine while things are calm. It dissolves the moment there is pressure, a handover, or a person out of the office — exactly when you need it.
The board does not help, because a board tracks tasks, and the thing without an owner is usually not a task yet. It is a gap between tasks.
What changes with a living goal tree
Goalpen puts ownership on the outcome itself — on the Goal, not in meeting notes.
Name the shared delivery as the Goal and put one real accountable person on that root. Not a committee: a name. Hang the branches people actually touch underneath, so a handoff is a visible node rather than a message that scrolled away. When a piece is waiting on someone, the wait sits on the node next to the owner, which is what makes a stall show up in week one instead of week three.
Then standup gets a shorter shape. Open the tree and ask two questions: who owns the root, and what is waiting on whom?
A quiet way to start — about two minutes
Pick one shared delivery that slipped, or nearly did, in the last month. Open or create the Goal and set a single owner on the root. Hang the real branches, including the one that stalled in the handoff. Use that tree at the start of the next standup, before anyone reconstructs the story from memory.
Next step
Try naming the owner on one shared Goal this week. Prefer to talk it through first? Use Contact us. Want the numbers first? Skim Pricing. No hard sell either way.