Why Your Chase List Got Longer
Ask an operations manager what they actually did last week and a large part of the honest answer is chasing people.
Not deciding. Not fixing the process. Sending the third message about something agreed a fortnight ago.
The role nobody budgets for
Six hours a week is fifteen percent of a manager's time. Across six team leads that is close to a full-time role whose entire output is reminding adults of things they already agreed to.
Nobody budgets for that role. Everybody funds it. It does not appear in a headcount plan because it is distributed across people hired to do something else, and it is invisible in a cost model for the same reason.
The ratio that moved
The chase list is a function of how much work is in flight. How much work is in flight is no longer set by how fast people can produce it.
Drafts, analyses, first-pass reports and summaries now arrive at a rate a model sets, not a rate headcount sets. That is the point of the tooling and it is working as intended.
What did not scale is the number of people who can vouch for any of it. That number is exactly what it was in 2023. A person who can put their name to a piece of work takes years to develop and cannot be provisioned.
So the ratio of things-needing-a-human-to-stand-behind-them to humans-available-to-stand-behind-them has moved, hard, in one direction. Nothing in the tooling touched the second number.
What the overflow actually looks like
A manager at fifteen percent chasing in 2023 is not at fifteen percent now. She is at whatever fifteen percent becomes when the pile doubles and she does not.
The overflow does not announce itself. It does not arrive as a complaint, or as a missed target, or as anything a dashboard has a column for. It shows up as things nobody chased.
That is the hard part. An item that was chased and refused is visible. An item that was never chased looks exactly like an item that is fine, right up until the moment it does not.
Which items fall out is not random either. A manager under pressure chases what is loudest, nearest, or owed to the person most likely to ask again. Quiet work owed to a patient colleague goes to the back of the queue every single week, and the back of the queue is where things stay until they become somebody else's incident.
Why the standing meeting made it worse
The usual remedy is a weekly call where everyone confirms where they are. It feels like the responsible thing to do and it has two properties nobody intends.
It batches. Something agreed on Tuesday is not confirmed until the following Monday, so the detection window for anything going wrong is a week wide regardless of how urgent the item was. A two-day task and a two-month task get the same check-in cadence.
And it rewards the confident. In a round-robin the person who speaks clearly and briefly sounds on top of their work, and the person who is genuinely stuck takes longer and sounds worse. The meeting therefore surfaces the opposite of what it was called to surface, and does it in front of an audience, which is the single best way to ensure nobody volunteers that they are behind.
An hour a week across eight people is another full day of management time, spent collecting information that a reply to a request would have produced for free.
Taking the chasing out of her hands
Every item carries who accepted it and by when. Anything still unanswered at that time surfaces by itself, with the asking and the silence attached to it.
The part worth noticing is what this does to the social cost. Chasing is unpleasant because it implies doubt: the third message about a fortnight-old commitment is, whatever its wording, an accusation. Managers ration it for exactly that reason, and the rationing is where the gaps come from.
When overdue work moves up the chain on its own, nobody decided to doubt anyone. A window passed. The escalation carries no opinion about the person, which is precisely why it can be allowed to happen every time rather than only when someone has the appetite for it.
Questions
Why are managers spending more time chasing people?
Because the volume of work in flight is now set by how fast tools produce it, while the number of people who can vouch for that work is unchanged. The ratio between the two moved, and chasing is what absorbs the difference.
How much time does chasing actually cost?
Six hours a week is fifteen percent of a manager's time. Across six team leads it adds up to roughly a full-time role, distributed among people who were hired for something else, which is why it never appears in a headcount plan.
How do you reduce follow-up and chasing at work?
Record the acceptance rather than the assignment, with a time attached, and let anything unanswered escalate by itself. An automatic escalation carries no accusation, so it can run every time instead of only when a manager has the appetite for the conversation.
Do weekly check-in meetings fix the chasing problem?
They batch it and they reward confidence. Something agreed on Tuesday waits until Monday to be confirmed, so the detection window is a week wide whatever the urgency, and in a round-robin the person who is genuinely stuck sounds worst in front of an audience.
Why do managers avoid chasing even when they should?
Because a third message about a fortnight-old commitment reads as an accusation whatever its wording, so managers ration it. The rationing is where the gaps come from, and it is why an escalation that carries no opinion about the person can be allowed to run every time.