---
id: KB-TD-016
url: https://app.codecontract.io/help/day-to-day/when-almost-everything-waits-on-someone-else
idioma: en
categoria: trabajo-diario
subcategoria: tareas
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TD-015, KB-CF-005]
citadoPor: [KB-TD-017]
---

# When almost everything waits on someone else

_Half your list does not move because it is not up to you. How to handle that without living in pursuit._

**Responde a:** my work depends on others replying · managing tasks blocked by third parties · cannot progress until they send it · organising work with many waits

Documentation work has a feature that makes it exhausting: most of what you have open does not depend on you. It is waiting on a supplier, an adviser, a client. And a list full of things you cannot push creates the feeling of falling behind even when you are doing everything possible.

## Separate what can be separated

| State | What it means | What to do with it |
| --- | --- | --- |
| Mine to act on | I can move it now | This is your real list, and it is usually short |
| Waiting on someone outside | Already requested, with reminders running | Do not look daily: look when it is due |
| Waiting on someone inside | It depends on a colleague | The only thing to unblock by talking |
| Stuck for no reason | Nobody is pushing and nobody is waiting | Decide: restart or close |

> [!IMPORTANT]
> The fourth row pollutes everything else and gets the least attention. While files sit stuck with nobody knowing why, any count of "pending" mixes real work with noise — and the feeling of being swamped comes as much from the noise as from the work.

## What changes when you work this way

1. **Put chasing on automatic and out of your head** — If the reminder goes by itself, waiting stops being your task.
2. **Fix when you look at what is waiting** — Once a week. Looking daily does not speed it up and wears you down.
3. **And put an end to every wait** — "If it is not here by Friday, I do X". Without that end, the wait is infinite by definition.

> [!WARNING]
> The real strain does not come from having things waiting: it comes from not knowing which are waiting on someone and which have simply gone quiet through neglect. Once those two are distinguishable at a glance, the same amount of pending work weighs half as much — and that is not an impression, it is that you stop mentally re-checking what is already handled.

## How to talk about it with whoever asks

**En corto**

- "Requested on the 3rd, with two reminders" is a professional answer.
- "I'm waiting" on its own does not sound like one, even though it is the same.
- And if you get asked often, give them access to the status instead of answering.

The third solves the whole case when the asker is a manager or a client: once they can look, they stop asking, and you stop interrupting what does depend on you.

> [!NOTE]
> If separating the list shows that what is yours to do is very little and you are still short of time, the problem is not the workload: it is the constant interruption to report on the rest.

**What if the one not replying is a client?**

Same criterion, different tone: the end of the wait exists all the same, it is just communicated differently.

**How many reminders before escalating?**

Two, spaced. By the third it stops being chasing and becomes a decision.

**Should things stuck for months be closed?**

Yes, noting why. A file closed with a reason informs; one left open without a reason does not.

## Ejemplos

**A manager has sixty open files and the constant feeling of never advancing.**

- Separates what is theirs from what is waiting and closes what is stuck for no reason
- Leaves chasing on automatic and reviews waits weekly

→ Their real list turns out to be eight items, and they clear it in two days.

**Of twenty open files, sixteen wait on somebody outside and the team feels stuck.**

- Separates what waits outside from what waits inside
- Works the short list that does depend on you
- Lets the reminders work the long one

→ The sense of being blocked lifts because your own list is short and moving.

**What is waiting on third parties is reviewed daily.**

- Reviews it once a week

→ Time goes on what does depend on you.

**Daily chasing means the supplier stops reading.**

- Spaces out the reminder cadence

→ The nudge works again.

**A file has waited two months and nobody decides.**

- Sets an escalation or closing criterion

→ The file does not stay open forever.

**Management asks why nothing is moving.**

- Shows what waits inside and what waits outside

→ The conversation happens with data.