How to stop chasing your team for updates

Nobody enjoys this. You don't enjoy asking, they don't enjoy being asked, and the answer is usually "yeah, it's in hand" — which tells you nothing.

The chasing isn't a discipline problem. It's what happens when progress is invisible, and asking is the only instrument you've got.

Why chasing doesn't work anyway

Even when it's answered honestly, a verbal update is a bad instrument.

• It's a snapshot that's out of date immediately.
• It only covers what you thought to ask about — the jobs you'd forgotten are exactly the ones at risk.
• It interrupts the work to report on the work.
• It rewards whoever is best at sounding on top of things, which isn't the same as being on top of things.

And it scales terribly. Chasing five people is annoying. Chasing fifteen is a full-time job.

Replace asking with seeing

The goal is a shared list where progress is a by-product of doing the work, not a separate reporting exercise.

That needs four things visible without anyone writing a report:

• Who owns each job
• When it's due
• Whether it's moving, done, or blocked
• What's overdue

Once those are true, "where are we with the Hartley job?" becomes a thing you look up rather than a thing you ask. The daily status conversation mostly evaporates.

Make "blocked" a first-class status

This is the highest-value single change, and most teams miss it.

A lot of what you're chasing isn't late through neglect — it's waiting on a customer, a supplier, a delivery, or a decision from you. If your list only distinguishes "not done" from "done", all of that looks identical to inactivity.

Give blocked work its own status, with a note on what it's waiting for and when to check back. Suddenly a large slice of your chasing disappears, because you can see the job isn't stalled — it's parked, deliberately, with a date on it.

You'll also discover how often the blocker is you.

Don't replace chasing with surveillance

There's a wrong version of this, and it backfires.

If people feel the list exists to monitor them, they'll manage the list rather than the work — updating statuses defensively, marking things in progress that haven't started, and avoiding recording anything that might look bad.

The framing that works: this exists so nobody has to remember everything, and so nobody gets chased. That's true, and people can tell the difference between a system that removes interruptions and one that adds scrutiny.

Two practical rules that keep it honest: don't use the list to criticise people in front of others, and treat "blocked" as useful information rather than an excuse.

Keep one short, structured check-in

Visible work removes most conversations, not all of them. Keep one — short, same time each week, and structured around the list rather than around people.

Three questions, ten minutes:

• What's overdue, and is it genuinely stuck?
• What's blocked, and who can unblock it?
• What's coming up that we're not ready for?

Notice none of these is "what are you working on?" You can already see that. The meeting is for the things the list can't resolve on its own.

What changes

Within a couple of weeks you should notice:

• You stop asking for status, because you can see it.
• People stop pre-emptively reporting, because they know you can see it.
• The remaining conversations are about blockers and decisions — which is what your attention is actually worth.

The relief is usually mutual, and it comes faster than people expect.