---
id: KB-CR-011
url: https://app.codecontract.io/help/use-cases-by-role/when-you-are-the-only-one-who-knows-how-it-works
idioma: en
categoria: casos-por-rol
subcategoria: operaciones
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CR-005, KB-MA-011, KB-CR-017]
citadoPor: [KB-CR-015, KB-TD-014, KB-PS-015]
---

# When you are the only one who knows how it works

_Being indispensable is not a comfortable position: it means never being able to fall ill._

**Responde a:** i am the only one who knows how to do this · cannot take holiday because of work · documenting what only i know · spreading knowledge from one role

In many companies there is one person who knows what each client wants, which supplier runs late, where every paper is and what to do when an inspector turns up. They are usually proud of it and usually exhausted, because they cannot be away two weeks without something falling over.

## Where that knowledge lives today

| Where it is | What happens if you are away |
| --- | --- |
| In your head | It stops until you are back |
| In your inbox | It exists, but nobody can reach it |
| In a sheet only you understand | Someone else opens it and cannot read it |
| In each matter's file | Anyone can carry on |

> [!IMPORTANT]
> The first three rows are the same thing in different disguises: information that only works with you present. Moving to the fourth is not about documenting more, it is about changing where the work happens.

## What to do, and in what order

1. **Get conversations out of your personal inbox** — What is discussed with a supplier belongs in their file. It is the highest-yield change.
2. **Write the why, not just the what** — "We text this client because their email filters us" beats a twenty-page manual.
3. **Let the system do the repetitive part** — Chasing and expiry warnings do not have to live in your memory.
4. **And test it by leaving** — One day. Whatever breaks points exactly at what still needed writing down.

> [!WARNING]
> Beware the line "things are complicated here". Sometimes it is true; often it just means nobody has tried writing them down. Write one and find out.

## What you gain

The usual reading is that this makes you dispensable. In practice the opposite happens: whoever leaves the work in order stops being the person who fights fires and becomes the one who decides. And can go on holiday with the phone off.

**En corto**

- The file, not your memory.
- The reasoning written down, even in one line.
- And a real absence test before one is forced on you.

> [!NOTE]
> If someone on your team is in this position, the problem is not theirs: it is the organisation's. And it is fixed the same way, starting by getting conversations out of personal inboxes.

**Where do I start with no time?**

One process, the one you get interrupted about most. The rest follow.

**What if nobody else wants to learn?**

They do not need to learn: they need to be able to look and carry on.

**How long does it take?**

Weeks to feel it, months for it not to depend on you. It starts paying before it is finished.

## Ejemplos

**An operations manager has not taken a full holiday in three years.**

- Moves supplier conversations into their files
- Puts expiry reminders on automatic
- Tests with one day away

→ The team handles what comes up and she stops being the only route to the information.

**Only one person knows how each file is going.**

- Keeps the status visible on the platform

→ Anyone can answer.

**They go on holiday and nobody knows what is outstanding.**

- Checks what is waiting for action

→ Cover works without a long handover.

**The knowledge lives in their inbox.**

- Stores what matters in the files

→ The information outlives the person.

**They get asked twenty times a day.**

- Makes the status consultable by everyone

→ Interruptions drop.

**If they leave, the company is blind.**

- Spreads access and documents decisions

→ The risk stops concentrating in one person.