Chasing People Is Not Management

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.

Both sides pay

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, over-promising 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 chasing 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.

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 a nudge from software lands differently

The objection here is reasonable: isn't an automated reminder just a colder version of the same thing? 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 asks “is this done, or do you need more time?” at the moment you yourself said it would be done, there's nothing to interpret. It isn't suspicious, it isn't pointed, it didn't choose you. It's a clock going off — and the option to say “I need more time” is right there, which is a genuinely different conversation from being caught out.

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 automatic 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 that's a question a team can answer without anybody's status being at stake.

• The person who promised gets asked, not the manager who'd have to relay it.
• The asking happens at the time it was due, not when somebody happens to remember.
• “I need more time” is a first-class answer, given before the deadline rather than after it.
• Nobody gets shouted at for a promise 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.