Why the habit dies in week two
The pattern is almost identical everywhere. You ask for an end-of-day update. Everybody sends one for three days. By day nine two people have stopped, by day fourteen it is three, and within a month the only person still sending one is the person who was already organised.
It is tempting to read that as an attitude problem. It is more often a design problem, and the design is yours. An update is a small unpaid piece of admin at the end of a tiring day, and people keep doing small unpaid things only when they can see that they mattered.
So the useful question is not how to make people comply. It is what happened to the first updates they sent.
- Nobody replied, so it looked like it went nowhere
- Nothing changed as a result, so it looked like it changed nothing
- It took too long, because you asked for structure instead of sentences
- Somebody's honest update was used against them, and everybody heard about it
Ask for less than you think
The instinct is to ask for a format: what you did, hours spent, percentage complete, blockers, next steps. Every field you add reduces the number of people who send anything at all, and the fields you added are rarely the ones you actually read.
Two or three lines in their own words is the right ask. It takes fifteen seconds, it can be typed one-handed while walking to the van, and it contains almost everything you needed.
A real update looks like: "Rotors came in and the Civic's done. Transit's still stuck waiting on the turbo. Need to ring Mrs Ali tomorrow." Three sentences, nine seconds, everything you needed.
What to ask for
- What got finished
- What is stuck, and on what
- Anything carrying over to tomorrow
What not to ask for
- Hours or time spent - that is a different conversation, and mixing it in makes the update feel like surveillance
- Percentages complete - nobody knows, so they are invented
- A template or a form - it converts a fifteen-second message into a five-minute chore
- Anything you will not read
The first three weeks decide it
Habits form or fail early, so the effort belongs at the start rather than spread thin over months. Do these five things for three weeks and the habit survives; skip them and no amount of reminding later will rescue it.
- Reply to the first ten. A sentence is enough. "Good - I'll chase the turbo." Silence is what kills it.
- Fix one blocker fast. Somebody reports being stuck; you unstick it within a day and say so. Now reporting problems visibly works.
- Ask at the same time every day. Predictability turns a request into a routine.
- Do it yourself, visibly. Send your own end-of-day update. It stops the whole thing looking like something done to them.
- Do not punish honesty. The first person who admits something slipped sets the tone for everybody. How you react is the entire message.
What to do when it stops anyway
Some people will still stop, and the response most owners reach for - mentioning it in the group chat - is the worst available option. It embarrasses the person, signals to everybody that this is now a compliance exercise, and produces the most minimal update that technically satisfies you.
Chase privately, and know in advance how many times you will do it before you stop chasing and have a different conversation instead.
| What is happening | What it usually means | What to do |
|---|---|---|
| One person stopped | They think it is not read | Reply to their next one, specifically |
| Everybody stopped | Nothing came of it | Fix one visible blocker, then ask again |
| Updates are one word | It feels like surveillance | Ask about blockers, not output |
| Only good news arrives | Somebody got punished | Say plainly that bad news is the point |
| Updates arrive at midnight | They are writing them from memory | Move the ask earlier |
The pattern worth watching for is the fourth row. A team that only reports good news is more dangerous than a team that reports nothing, because it looks like everything is fine right up until it is not.
Chasing without becoming the nag
Somebody has to notice when an update has not arrived and when a job has gone past its date. If that somebody is you, two things happen: it takes a chunk of your morning, and you become the person who nags - which changes how your team talks to you about everything else.
The rules that make chasing tolerable are the same whether a person or a piece of software does it.
- Privately, always. Nobody's late work belongs in a group
- Only about their own work
- Only within working hours - a nine p.m. reminder gets the tool muted and the sender resented
- A fixed number of attempts, then stop and change the conversation
- Never chase somebody about something they told you they are blocked on
That last rule is the one most often broken, and it is the fastest way to teach a team that reporting a blocker changes nothing.
When to hand the chasing to software
Chasing is a good candidate for automation precisely because it is unrewarding, repetitive and damaging to the person doing it. Software has no feelings about sending the same reminder for the third time, and the person receiving it does not resent software the way they resent a manager.
This is the part we built, and the design constraints are the rules above rather than anything clever. Bosun asks for the update at a time you set, chases privately within your working hours, stops after the number of attempts you allow, escalates to you instead of continuing, and never chases blocked work as though it were simple lateness.
- It asks for the end-of-day update, once, at your chosen time - see end-of-day updates
- It can send each person their own week on Monday - what they closed, what is still open - which is the mechanism that makes an update visibly amount to something
- It chases overdue work privately, then escalates and stops - see automatic follow-up
- It reads plain language, so nobody is filling in a form - see daily plans
- It tells you who did not report, so you do not have to notice - see the owner briefing
One warning that applies whatever you use: automating the chasing does not automate the replying. If updates still disappear into nothing, they will stop arriving no matter how politely the reminder was worded.