Every owner who chases has the same theory: the team needs more discipline.
It is almost never true. Chasing is structural. If the only way to find out whether something happened is to ask, then a completely willing, competent team will still produce a chasing habit — because you have given yourself no other way to know.
The fix is not pressure. It is removing the reason to ask.
Why chasing happens
Three conditions produce it, and you usually have all three at once.
Completion is invisible. The task was assigned verbally or in a message thread. Nothing anywhere changes state when it is finished. The only sensor is you.
Ownership is plural. "The warehouse team will handle it" means nobody specific has it. Shared ownership reliably becomes nobody's ownership, and it takes a phone call to discover that.
The deadline lives in your head. You remember it was due Tuesday. Whether anyone else does is untested until Wednesday.
Notice that none of these are about the team's character. Fix the three conditions and the chasing mostly stops on its own.
Four changes that actually work
1. One name per task
Not a department, not a role, not two people. One person, by name, who is accountable for the outcome.
This feels bureaucratic for about a week and then becomes the thing everyone relies on. When ownership is unambiguous, people stop waiting to see whether someone else picks it up — which is the main cause of silent delay.
Where work genuinely needs two people, split it into two tasks with two owners rather than co-assigning one.
2. Make completion produce evidence
"Done" reported verbally is not information. "Done" with a photo of the closed shutter, a temperature reading, or a signed handover is.
This is the highest-leverage change on the list and the one most people skip. Evidence does three things at once: it removes the follow-up question entirely, it makes standards concrete rather than assumed, and it protects the person doing the work when something goes wrong later.
Keep it proportionate. A photo takes four seconds. A form with eleven fields will be filled in dishonestly within a fortnight.
3. Move reminders into the channel people already use
The most common failure of any operations tool is that it requires a login. Field staff, drivers, shift workers and shop teams will not open a dashboard.
If your team lives in WhatsApp, the reminder needs to arrive in WhatsApp and completion needs to be confirmable from there. Adoption is almost entirely a function of how many steps stand between the person and the action. Every extra step costs you compliance, and it costs you most from exactly the people whose work you most need visibility into.
4. Review exceptions, not everything
Once completion is tracked, resist the urge to look at all of it. A dashboard showing forty green processes is noise, and after two weeks you will stop opening it.
The useful view is the short one: what is overdue, what failed its check, what has no owner. Three to five items. That is a five-minute morning review instead of a forty-minute status meeting, and it is the difference between a system you keep using and one you abandon in month two.
What changes, and how quickly
The realistic sequence, based on how these rollouts tend to go:
Week one to two is worse, not better. Making work visible surfaces things that were quietly broken. Expect to discover that a process you thought ran daily runs twice a week. This is the system working, though it does not feel like it.
Week three to four the habit sets. Completion rates climb because people can see what is expected of them, which for many is genuinely new information.
Month two is when the owner notices. Not because a dashboard looks good, but because a day passes without anyone needing to ask them something.
The part nobody mentions
There is a version of this that fails, and it fails for a predictable reason.
If the first thing you do with completion data is confront people about missed items, you have built a surveillance tool. Compliance will hold for a few weeks and then quietly rot — checklists get ticked without the work being done, and you end up worse off than before, because now you have data you trust and shouldn't.
The framing that works: the system exists to catch problems, not people. When something is overdue, the first question is what blocked it, and often the honest answer is that the process was unrealistic. Teams accept tracking when it reliably produces "what's in your way?" instead of "why haven't you?" — and when it stops them being interrupted five times a day.
Get that right and you do not need to enforce adoption. People prefer a system that answers for them over a manager who keeps asking.