No task announces that it's late. Deadlines pass silently, and the project keeps looking fine to everyone not staring at that exact row — until a client asks about the thing that was due last Tuesday, and now it's a fire and an embarrassment.
Photo: zoutedrop, CC BY 2.0
Why humans are bad at this job
Chasing requires noticing (someone scanning every due date daily), remembering (again Thursday if nothing moved), and consistency (chasing your best developer as reliably as your intern). People do all three badly — not from laziness, but because nagging is socially expensive and infinitely deferrable. It's also a real profit leak: chase time produces nothing billable.
The loop that works
- Before the deadline — a reminder to the assignee. Most lateness is forgetting, and this one message clears it.
- At the deadline, no movement — ask, don't accuse: is it done-but-not-updated, underway, or blocked? Each answer routes differently.
- Overdue and unresponsive — escalate to the PM with context: how late, what it blocks, what the assignee's carrying. The human enters with judgment, the machine having done the noticing.
- Client-facing deadline at risk — the PM decides how to tell the client honestly, before they ask.
The machine is better than a person here precisely because it's socially free: no awkwardness, no favoritism, no Friday-afternoon decay. Escalations become rare and meaningful instead of constant and ignored — and workload patterns (who's always overloaded, whose estimates always slip) finally become visible instead of anecdotal.
← All posts