All postsAlle Beiträge
Ops   Jul 3, 2026 · 5 min read

"Ownership" is the most overloaded word in operations

Ownership ist das überladenste Wort in Operations

Watch a leadership meeting and count how many times the word "own" appears. Then ask each speaker what they meant. You'll get four answers from four people: I'm accountable for the outcome. I decide. I do the work. I report on it. Those are different jobs, and conflating them is why ownership disputes are the slowest meetings in the company.

The four ownerships

  1. Accountable owner — carries the outcome to the board. One person.
  2. Decision owner — has authority to choose between options. Often the same as accountable, often not.
  3. Delivery owner — runs the work. Usually a different person.
  4. Reporting owner — keeps the status truthful. Usually a fourth person.

Most goal-tracking tools have one "owner" field. That single field forces a fiction. The truth — who decides, who delivers, who reports — gets pushed into Slack threads and tribal memory.

What to do

Stop using "owner" as a single label. Insist that every objective names accountable, decision, delivery and reporting in writing. It feels heavy. It saves the next six meetings.

The Vindaris view

Ownership is a structure, not a name. Build the structure into the system and the ambiguity disappears.

Beobachte ein Führungsmeeting und zähle, wie oft das Wort „besitzen" fällt. Du bekommst vier Antworten: Ich bin verantwortlich. Ich entscheide. Ich liefere. Ich berichte. Das sind vier Jobs.

Die meisten Tools haben ein einziges „Owner"-Feld — und erzwingen damit eine Fiktion. Benenne stattdessen explizit: Accountable, Decision, Delivery, Reporting. Es fühlt sich schwer an. Es spart die nächsten sechs Meetings.