After the handover: don't take it back, don't abandon it
Step 1 / 4·Following up isn't surveillance
0/4 steps done
Learning objectives — after this module you will:
- Set a follow-up rhythm without micromanaging
- React correctly when someone works differently from you
- Handle mistakes without pulling all the work back
Following up isn't surveillance
Keep control without suffocating.
Two ways to follow up
Micromanaging
“Asking about progress daily, demanding constant drafts, reworking the format, calling the moment it goes quiet for half a day.”
The receiver learns you don't trust them, so they stop deciding and ask you about everything — exactly what you wanted to avoid. You spend twice the time you'd have spent doing it yourself.
Pre-agreed checkpoints
“Agreed at handover: 'send a draft on Wednesday, and message me any time if you get stuck'. Between checkpoints you don't ask, unless something changes at your end.”
The receiver has room to work while knowing where support arrives. You still control the risk without spending time every day.
Three follow-up rules
- CHECKPOINTS ARE AGREED AT HANDOVER, not invented halfway through. A checkpoint that appears suddenly always reads as lost trust.
- LONGER WORK NEEDS MORE CHECKPOINTS. A two-week task wants one midpoint; a two-month task wants three or four.
- OPEN THE DOOR EXPLICITLY: 'message me if you're stuck, don't wait for the checkpoint' — many people won't ask because they fear looking incapable.
Key takeaway: Agree checkpoints at handover, don't ask in between, and say explicitly that they can ask any time.