Youno

Tasks in. Work done. youno.si

← All insights
Team & People

How to Delegate Tasks to Employees and Follow Up Without Chasing

Every “any update?” costs something on both sides. The manager loses focus, and the person being asked loses a little trust that anyone believed them.

Anurag JoshiAnurag JoshiFounder, Youno2 Sept 20267 min read

There's a particular kind of busy that feels like managing and isn't. It's 4 PM, you've got twenty minutes, and you spend them sending eight messages that say some version of *“any update?”*. It feels like the responsible thing to do. It produces, by itself, nothing at all.

How to delegate a task so it gets done

Most chasing starts at the moment work is handed out. A job given as “Ramesh, ye dekh lena” has no deadline and no clear result, so the follow-up is built in from the start. Delegating a task to an employee well takes one message with three parts:

  1. Who. One named person, not “someone please”. Tag them if the group is busy.
  2. What. The result you want, in one line: “Send the revised quote to Patil”, not “look into the Patil thing”.
  3. By when. A time they can say yes to: “by 4 PM”, “before the truck leaves”, “kal subah tak”.

Then let them answer. “Haan, 4 baje tak” is a clear yes. “Dekhta hoon” is not, and it is better to ask once more now than to chase later. Said once, in the group, where everybody can see it, that message is the whole hand-off. What happens after it is the rest of this article.

What constant follow-up costs both sides

The cost to the manager is obvious enough: the time, and more importantly the fragmentation. Chasing eight people generates eight replies arriving over the next two hours, each one a small interruption, each one requiring a decision about whether to chase again.

The cost on the other side is the one that doesn't get counted. Being asked “any update?” about something you clearly said you'd do carries an implication, however gently it's phrased: that somebody wasn't sure you'd do it. Once, fine. Three times in a week, and a reasonable person starts to feel supervised rather than trusted. The eventual response is not better delivery. It's defensive reporting: long status messages, overcommitting to buy room, and a general shift from doing the work to being seen doing the work.

Ask a good person for a status update often enough and you'll train them to manage you instead of the job.

Most follow-up is a visibility problem

Here's the part that makes this worth fixing rather than just enduring. Sort a week of chases into two piles and the split is stark.

TypeWhat it's really askingCould software have answered it?
“Any update on the Patil quote?”Is it done yet?Yes
“Did the blade arrive?”Has the blocking thing cleared?Yes
“Is Sharma's 3B filed?”What's the state of a known item?Yes
“The client is unhappy about the delay. How do you want to handle it?”Help me decideNo. That's management
“You've missed this twice now, what's going on?”Something needs addressingNo. That's management
Two kinds of follow-up

The first three are not management. They're queries against a database that happens to be made of people. The last two are the actual job (judgment, context, a difficult conversation), and they are the ones that get squeezed out when a manager's follow-up budget is spent on the first three.

Why an app's reminder lands better than “any update?”

The objection here is reasonable: isn't an automatic message just a colder version of the same chase? In practice it isn't, for a reason that's about people rather than technology. A message from a person carries tone, and tone has to be interpreted.

When your boss asks at 4 PM whether something's done, you read the phrasing, the timing, whether he asked you before anyone else. When a system simply tells you a job is yours (“New task from Anil: Send Shakti's challan”), there's nothing to interpret. It isn't suspicious, it isn't pointed, it didn't choose you. It's a plain statement of what was said in the chat. And when you finish, you tap Done, add a line if you like, and the person who asked is told. Nobody had to ask “is it done?”

The second-order effect matters more than the first. When routine chasing stops being something a manager does, the times he *does* follow up personally start to mean something again. That signal had been diluted by being used for “any update?” forty times a week.

This isn't about less accountability

Worth saying plainly, because it's the natural worry: making the chase unnecessary makes commitments more visible, not less. What changes is that the visibility stops being personal. The question isn't “does the boss trust me”, it's “is this done yet”, and the list answers that without anybody's status being at stake.

  • Whoever it's for is told directly, not through the manager who'd have to relay it.
  • The list shows what's still open and who it's for, so nobody has to ask.
  • When something is done, the person who asked is told, and the chat keeps a line saying so.
  • Nobody gets shouted at for something that vanished into message history, because it didn't.

What to do with the time

Owners who stop doing the mechanical chase usually report the same odd first week: it feels like something is missing. That's the loss of a visible, effortful activity that was standing in for management. The useful version of the question is what the twenty minutes at 4 PM are now for, and the answer is almost always the two rows at the bottom of that table, the ones that were never getting enough attention.

Anurag Joshi

Written by Anurag Joshi, Founder, Youno, Youno. General guidance on running a team, not professional or legal advice for a specific situation.

Youno: the work chat that remembers

Ready to stop holding everyone's work in your head?

Free to start · Ready in ten minutes · No card