How to delegate tasks so they actually get done
Delegation fails at the handover, not at the follow-up. By the time you are chasing, the mistake has already been made — something the task needed was missing when you sent it, and no amount of asking will supply it retrospectively.
Six things make the difference. Most badly delegated work is missing at least two.
Key takeaways
- One owner. Two owners is zero owners.
- A due date, not "soon". Undated work is invisible to every reminder and every report.
- A definition of done, agreed before they start.
- The authority to finish it — delegating a task without the decisions it needs is delegating a queue.
- Blocked has to be sayable. Silence is the most expensive status.
- Chasing is a system's job, on a schedule you announced in advance.
What does a task need before you send it?
Six things. If any are missing, you have created a conversation rather than a task.
| What it prevents | |
|---|---|
| One named owner | The diffusion where everyone assumes someone else has it |
| A due date | Work that is never late because it was never due |
| A definition of done | Delivered work that is rejected, then resented |
| Enough context to start | A day lost to finding out what you meant |
| Authority to decide | A task that stalls waiting for you |
| An agreed way to report | You asking, which is the thing you were trying to avoid |
Read that list as a checklist you run in ten seconds before hitting send. It is faster than the follow-up conversation it replaces.
Why does "one owner" matter so much?
Because responsibility shared between several people is genuinely ambiguous, and everyone involved knows it.
This is why posting a job in a group chat produces so little. A message addressed to fourteen people is addressed to nobody in particular, and the reasonable assumption for each reader is that someone better placed will pick it up. It is not laziness; it is a correct reading of an unclear instruction.
Naming one owner removes the ambiguity completely — not by making anyone more diligent, but by removing the interpretation in which it was someone else's. The same work, addressed to one person, gets done. See WhatsApp groups vs a task tracker for why chat makes this worse.
When should you assign to a group instead?
When the work genuinely applies to everyone — and then you should assign it as a group task, not post it in a group.
Some things really are for all fourteen people: acknowledging a new policy, counting stock, running the opening checks. The right handling is to point one task at a department, a branch, a chosen set of people, every department head or the whole company, so that each person gets their own copy while you keep a single master row showing progress.
That gives you "eleven of fourteen done, and here are the three" instead of counting emoji. What it does not do is let you avoid deciding who owns something — if the work is one job, name one person.
How do you pick the right owner?
Choose for authority and proximity, not for availability.
The most common error is assigning to whoever seems least busy. That optimises for the wrong thing. Ask instead:
- Can they finish it without coming back to you? If not, either delegate the decision too or keep the task.
- Are they close to the information? Someone who already has the context spends an hour where someone else spends a day.
- Is this a stretch, and did you say so? Deliberate stretch work is development. Accidental stretch work is a failure waiting to happen.
How do you follow up without micromanaging?
Let a system chase on an announced schedule, and read status instead of asking for it.
This is the part that changes how delegation feels. Chasing done by a person reads as distrust of that person, and it consumes your attention. Chasing done by a rule that treats everyone identically reads as process, and consumes none.
A ladder that works: a notification before it is due, a message when it lands, firmer chasing through the first day late, and after that a daily note to the department head until it closes. Announce this at the start so nothing is a surprise, then leave it alone. The mechanism is covered properly in why your reminders get ignored.
Then read, rather than ask. A day view grouped overdue-first, a board with a Waiting-on column showing how many days something has sat, and a weekly report of who closed what. Every one of those answers a question you would otherwise have interrupted somebody to ask.
Why does "blocked" need to be a real status?
Because the alternative is silence, and silence is indistinguishable from progress until the deadline.
If the only two states are "not done" and "done", a person stuck waiting on someone else has no way to tell you except by messaging — which feels like admitting failure, so they often do not. Making Waiting-on and Blocked into ordinary, visible states removes the social cost of saying so. You find out on day one instead of day nine, and the days spent stuck get counted automatically.
Treat a rise in blocked work as information about your process, not about the person who reported it. Punish the report and you will stop receiving it.
A note on giving work back
Reassigning is not a failure. It is data.
When something has been chased to the top of the ladder and has not moved, sending more messages is not the missing ingredient. Reassign it, and let the record show it. Every reassignment being logged means the later conversation is about a sequence of events rather than two people's memories — which is a much better conversation for everyone.
Sitatu handles the handover and the chasing: assign to a person, a department or a branch, let the ladder escalate on WhatsApp, and read the seven report tabs instead of asking. See the features page or start a free trial. The wider picture is in WhatsApp task management: the complete guide.
Frequently asked questions
What makes delegation fail?
An incomplete handover. Most failed delegation is missing one of six things: a single owner, a due date, a definition of done, the context needed to start, the authority to act, or an agreed way to report progress. Following up harder does not supply any of them.
Should you delegate to a person or a team?
To a person, unless the work genuinely applies to everyone — a compliance acknowledgement, a stock count, an opening checklist. In that case assign it to the group properly so each person gets their own item and you keep one row showing overall progress.
How do you follow up without micromanaging?
Let a system do the chasing on a fixed, announced schedule, and read status rather than asking for it. Chasing done by a rule that treats everyone the same reads as process; chasing done by you reads as distrust.
What should you do when a delegated task is blocked?
Make blocked a visible state rather than a silence. If someone can mark a task as waiting on something or blocked, you find out early and the days it has been stuck are counted for you.