---
id: KB-TD-014
url: https://app.codecontract.io/help/day-to-day/delegating-without-losing-control
idioma: en
categoria: trabajo-diario
subcategoria: tareas
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TD-006, KB-CR-011]
citadoPor: [KB-CL-017]
---

# Delegating without losing control

_Sharing out the work and still knowing how it is going, without asking every day._

**Responde a:** delegating without losing visibility · how to know if delegated work is progressing · sharing files across a team · following up without micromanaging

Delegation nearly always fails the same way: whoever delegates loses visibility and recovers it by asking, and whoever received the work reads those questions as distrust. It is not a people problem: the state of the work is not anywhere both can look.

## What to make clear when delegating

1. **What "finished" means** — Not "handle this supplier's onboarding", but what must be done to call it closed.
2. **Which decisions they can take and which not** — It prevents both paralysis and unpleasant surprises.
3. **By when** — With a date. "Whenever you can" competes with everything else and loses.
4. **And where progress will be visible** — The point almost nobody agrees, and the one that makes daily questions unnecessary.

> [!IMPORTANT]
> The fourth point replaces supervision. If the state is visible in the file, the delegator looks whenever they want without interrupting, and the doer does not have to report. Both gain the same thing: they stop talking about status and start talking about problems.

## What to look at, and how often

| What | How often | Why |
| --- | --- | --- |
| Whatever has been stuck longest | Weekly | That is where the problem is, not in what is moving |
| Whatever is due soon | Weekly | It is the only genuinely urgent thing |
| Everything else | Not needed | Looking at it is micromanagement by another name |

> [!WARNING]
> If you find yourself reviewing every delegated file, you have not delegated: you have shared out execution and kept the duty to watch, which is the part that eats time.

## When something gets stuck

**En corto**

- Ask about the obstacle, not the progress.
- And if the obstacle is another person, that is where you step in.
- What does not work is reassigning without asking first.

Reassigning a stuck file without talking usually solves that case and spoils the next: the person it was taken from will stop flagging when something gets difficult.

> [!NOTE]
> If a file has no named owner it is not delegated: it is in the air. "The team" answers for nothing, and that is always discovered late.

**What if I delegate to someone new?**

More detail on what "finished" means, same review frequency.

**Should several people share a file?**

One answers and others help; two owners is none.

**How do I know if I am micromanaging?**

If you are asking about things you could look at yourself, you are.

## Ejemplos

**A manager delegates fifteen files and ends up asking about them every morning.**

- Agrees what "finished" means and where progress is visible
- Reviews only what is stuck and what is due

→ Stops asking, and the team starts flagging obstacles on its own.

**Supplier onboarding is delegated and every file is still reviewed one by one.**

- Assigns files to whoever handles them
- Checks the overall status instead of case by case
- Keeps review for what falls outside the pattern

→ Control is kept without repeating the work of whoever does it.

**It is delegated and nobody knows what criteria to apply.**

- Writes the criteria into the template

→ Decisions are the same whoever takes them.

**It is delegated and what gets stuck drops out of sight.**

- Reviews what is stalled once a week

→ The blockage is visible without looking at everything.

**Whoever receives the delegation cannot close files.**

- Adjusts permissions to the delegated work

→ The delegation genuinely works.

**It is delegated and then corrected behind their back.**

- Discusses the correction with whoever handles it

→ The criteria get learned rather than the error repeated.