Every Task Carries Exactly One Name
The rule: one task, one name
Every task in Vitae Dux carries exactly one named owner. Not a team, not a channel, not "whoever picks it up." A person, by name, visible to everyone who can see the task. The same rule applies up the chain: every project has one owner, and every goal has one owner.
That is the whole rule. Everything else on this page is what follows from it.
Why one name and not two
When two people own a task, each can reasonably believe the other has it. Nobody decided to drop it. It just became nobody’s job, quietly, and the board looked fine the entire time. We wrote a whole field report on that failure shape in why agency deliverables slip.
A single name removes the ambiguity that makes dropped work possible. The owner is not necessarily the person doing all the work. They are the person who can tell you where it stands, and who raises a hand the day that answer stops being true.
Shared responsibility sounds generous and works badly. Single ownership sounds strict and works kindly: nobody gets surprised in a Friday meeting, because the name was on the work all week.
What the owner actually owns
Three things, and only three:
The answer. At any moment, the owner can say where the task stands. In Vitae Dux that answer lives on the task itself: its workflow stage, its due date, its blockers.
The flag. If the task cannot move, the owner logs a blocker the day it appears: a decision that has not been made, a dependency on someone else, missing information, a person, or a technical wall. Blockers are first-class records, not comments that scroll away.
The handoff. If the owner cannot carry it, they hand it to a named someone. The task never floats. When a teammate leaves, their work moves to a visible unassigned state that every role can see, with the reason attached, so departure never silently deletes responsibility.
How Vitae Dux enforces it
Most tools let you leave the assignee blank. Vitae Dux treats ownership as structure, not etiquette.
Ownership rolls up: tasks into projects, projects into goals, so when work ships, the goal moves without anyone compiling a status deck. Roles are enforced at the database layer, with admin, member, and viewer permissions that decide who can reassign what. And the weekly Accountability Score turns follow-through into a grade from A+ to F, computed from what actually happened: completions, punctuality, blockers raised and resolved.
The score is the part people feel first. It is one number for the team, moved only by finished work. When the number dips, the question is never "who do we blame," it is "which name needs help this week," and the board already shows you.
What changes in week one
The first thing teams notice is that the status meeting gets shorter, because the questions it existed to answer are already answered on screen. Who owns this? It says. Where is it stuck? The blocker says. Did we keep our word last week? The score says.
The second thing is quieter: the "I thought you had it" conversation stops happening, because the condition that produces it, a task with two believable owners, cannot be represented in the system at all.
Try it on your own board
Open the live demo, no account needed, and look at any task: there is a name on it. Or create a free account, put your real work in, and give every task one owner. The Free plan needs no card.
If you want the argument in full, start with accountability vs project management.