Sit in on any leadership meeting and quietly tally how many times the word "own" gets used. Then, when the meeting ends, ask each person who said it what they meant. You will get four different answers from four different people, all of them correct, all of them incompatible. I'm accountable for the outcome. I have the authority to decide. I run the actual work. I report on it to the leadership team. These are four genuinely different jobs, and the fact that we use one word for all of them is why ownership disputes are the slowest, most circular conversations in the company.
The dispute usually doesn't look like a dispute. It looks like a polite agreement that breaks two weeks later, when it turns out the two people who both said "I own it" meant entirely different things, neither of which covered the seam between them. That seam — the thing nobody owned because both parties assumed the other did — is where the work fell through.
The four ownerships hiding inside one word
When you actually unpack what people mean when they say they own something, you get at least four distinct roles. They sometimes collapse into one person, but more often they don't, and the trouble starts when nobody bothers to check.
The accountable owner is the one who carries the outcome upward — to the CEO, to the board, to the room where the score is read. If the objective misses, this is the person whose performance review reflects it. There is exactly one accountable owner per outcome. More than one means none.
The decision owner has the authority to choose between options when the team disagrees or new information arrives. Sometimes this is the same person as the accountable owner; often it isn't, because accountability lives at one level and decision-making lives at another. The CMO might be accountable for the brand refresh while the head of brand has the call on which agency to use. Confusing the two means escalations that should be quick become long.
The delivery owner is the person actually running the work — the line of code, the customer conversation, the launch checklist. They are usually closer to the team than to the leadership room, and their ownership is operational rather than strategic. Conflating delivery ownership with accountability is how you end up with senior leaders micromanaging delivery details, or junior leaders being held to outcomes they have no authority over.
The reporting owner keeps the status truthful and current. This sounds trivial. It isn't. The reporting owner is the person who refuses to let yellow stay yellow forever, who pushes back when the update is vague, who makes sure the leadership team knows what's actually true rather than what's diplomatic. In many companies, no one has this role explicitly, and so the status drifts.
Why one "owner" field forces a fiction
Most goal-tracking tools — and most planning templates — have exactly one owner field. That single field is the problem. It forces every objective to have one name on it, which means three of the four ownerships have to be implicit, which means they get pushed into Slack threads, hallway conversations, tribal memory, and the muscle memory of "well, obviously X handles that part."
The cost of this isn't just confusion. It's that the implicit ownerships drift, and there's no mechanism to catch the drift. The person who was implicitly the decision owner moves on. The new person assumes the named owner has decision rights. The named owner thinks they're accountable but not decisive. The team waits for somebody to decide. Weeks pass. The objective doesn't move. The next quarterly review notes that the initiative is yellow, and nobody can quite explain why.
This pattern is so common that most leaders have stopped noticing it. They've adapted by running parallel conversations — the official meeting where the named owner reports, the side conversation where the actual decision gets made, the third conversation where the delivery team escalates because they need a call. The work eventually happens, but at a coordination cost that nobody is accounting for.
What it looks like to do this properly
Stop using "owner" as a single label. Insist that every meaningful objective — every initiative big enough to appear in a quarterly review — has all four roles named explicitly and in writing. Who is accountable. Who decides. Who delivers. Who reports. Sometimes those collapse into two people. Sometimes one person carries three of them. Occasionally one person carries all four, and that's fine. The point isn't to multiply names. The point is to make the assignment conscious instead of assumed.
It feels heavy at first. The first time you do this on a real initiative, the conversation gets uncomfortable, because you discover that several initiatives don't actually have a clear decision owner, or that the person you assumed was accountable doesn't think they are. That discomfort is the point. It's the conversation that should have happened when the initiative was created, surfaced now instead of three months later when the deadline slips.
After two or three quarters of doing it this way, the heaviness disappears, because the meetings that used to spend their first thirty minutes re-litigating who's on the hook now spend that time on substance. You've front-loaded the ownership conversation into the planning step, where it costs an hour, instead of paying it back in dozens of smaller frictions throughout the quarter.
The Vindaris view
Ownership is a structure, not a name. One field in a tool is not enough scaffolding to carry the weight that "owner" actually has to bear in a complex organisation. Build the four roles into the system explicitly, make them inspectable, make it impossible for an objective to enter the plan without all four assigned, and a whole category of recurring ambiguity disappears.
The slowest meeting in your company is almost certainly the one trying to figure out who is supposed to do what. The fastest move you can make this quarter is to stop having that meeting by making the answer structural.