Named owner: why a department cannot own anything

Ask who owns a shared mailbox, an integration or a supplier relationship and the common answer is a department. That answer is comfortable and useless: departments do not notice renewal dates, do not answer questions and cannot be asked why something was not done. A named owner is one person, by name, and almost every chronic operational failure traces back to something that did not have one.

What a named owner is accountable for

• Keeping the thing current — reviewing it on its date and acting when the underlying situation changes.
• Answering questions about it, which is what makes ownership visible in daily life.
• Approving or refusing changes, because the ability to refuse is what prevents drift.
• Noticing deadlines attached to it: renewal, expiry, notice periods.
• Handing it over explicitly when they leave, rather than leaving it to be discovered.

Why shared ownership fails

Not because people are careless but because diffusion of responsibility is reliable. When two people own something, each reasonably assumes the other is watching, and the thing that fails is always the one neither believed was theirs. The failure is usually invisible until a deadline passes — an auto-renewal, an expired certificate, a permission nobody revoked — at which point everybody involved can honestly say they thought somebody else had it. Naming one person does not make them do more work; it makes the gap visible before it costs something.

Ownership must be recorded somewhere other than in the thing itself. "The owner is whoever is listed in the document" fails the moment the document is lost, archived or superseded — which is exactly the moment somebody needs to ask.

Assigning ownership that survives

1. Record the person, not the role, and keep the role beside it — roles help reassign, names make it answerable today.
2. Tell them. A surprising share of unowned things have an owner who was never informed.
3. Give them the authority to refuse changes, or the ownership is nominal.
4. Put ownership transfer into the leaver checklist, as a step with a successor named.
5. Review the ownership list itself on a date, because it decays exactly like everything else it tracks.
6. Mark genuinely unowned things as unowned rather than assigning a plausible name — a false owner is worse than an acknowledged gap.

The question that finds the gaps

Pick ten things that would hurt if they failed — an integration, a supplier, a mailbox, a certificate, a backup — and ask who owns each. The ones where the answer takes more than a few seconds, or arrives as a department, are your list. It takes a quarter of an hour and reliably finds at least one thing that has been nobody's job for years.

Ettex Records keeps the owner as a field on whatever is being tracked — documents, suppliers, assets, integrations — alongside the review date, so the two questions a register has to answer are answered in the same row. Filtering for a blank owner is the fastest audit available.