---
id: KB-TD-018
url: https://app.codecontract.io/help/day-to-day/the-work-nobody-owns
idioma: en
categoria: trabajo-diario
subcategoria: bandeja
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TD-006, KB-TD-001]
citadoPor: [KB-TD-013]
---

# The work nobody owns

_What has no owner appears in nobody's inbox, which is why it surfaces late and always from outside._

**Responde a:** files nobody is handling · we missed a deadline · work with no assigned owner · how to review what has no owner

A well-set-up inbox shows what is yours: what you owe, what you are waiting for and what is running out of time. It works so well that it creates a perfect blind spot — what belongs to nobody appears in no inbox, and therefore does not exist until someone outside calls.

## Where orphan work comes from

| Origin | Why it ends up ownerless |
| --- | --- |
| Someone left or changed role | Their work stopped showing for them and showed for nobody else |
| It was created automatically | A rule opened it and there was nobody to assign it to |
| It came in through an unusual channel | It arrived as a loose reply and nobody claimed it |
| It belongs to everyone | «Someone is on it» is the fastest way for nobody to be |

> [!IMPORTANT]
> The fourth row does the most damage and is the least obvious: **a shared owner works exactly like no owner**. When something belongs to a whole team, each person reasonably assumes another is watching it, and the alert that fires four times is ignored four times. What gets shared is the workload; the owner is always one person, even when three do the work.

## The five-minute review

1. **Once a week, look at what has no owner** — A short list if checked regularly, a very long one if not.
2. **Assign each item to someone, even provisionally** — A provisional owner spots the problem; none does not.
3. **And look at whatever has been still longest** — What has not moved in weeks is usually what belongs to nobody.

> [!WARNING]
> The moment this fires is always the same: **when someone leaves**. Removing their permissions is quick and everybody remembers; sharing out what they were carrying requires knowing what they carried, and that is only knowable while they are still there. Half an hour with that person before they go is worth weeks of archaeology afterwards.

## How to stop it being created

**En corto**

- Every file is born with an owner, even if it changes later.
- So is anything an automatic rule creates: with nobody obvious, it goes to a default person.
- And when someone goes on holiday or leaves, their work is reassigned rather than orphaned.

> [!NOTE]
> Having an owner does not mean it gets done on its own: it means there is someone to ask about it. That is the difference between an oversight and a problem nobody discovers.

**What if we genuinely do not know whose it is?**

Assign it to whoever will find out. That already counts as an owner.

**Does assigning everything create work?**

Less than a missed deadline you then have to explain.

**How often should we review it?**

Weekly while there is a backlog; after that, the monthly tidy-up is enough.

## Ejemplos

**A company finds a missed deadline on a file handled by someone who has left.**

- Reviews ownerless work weekly and reassigns whenever someone departs

→ The blind spot disappears, because everything shows up in one specific person's inbox.

**Some tasks belong to no department and have gone months undone.**

- Assigns an owner, even provisionally
- Gives them a review date
- Checks monthly what is still ownerless

→ Orphaned work stops piling up quietly.

**Everyone assumes somebody else is doing it.**

- Records the assignment

→ Nobody doubts whose it is.

**It is assigned to a department and nobody specific picks it up.**

- Assigns to a person, not an area

→ There is somebody to ask.

**The ownerless task blocks a file.**

- Checks which files depend on it

→ Priority is decided knowing the impact.

**The matter is closed without anyone doing it.**

- Records that it was decided not to, and why

→ The omission is a documented decision.