Series · read in order · 6 parts · ~100 min
Never chasing again.
Chasing usually isn't a discipline problem. It's what happens when an ask arrives as one line inside somebody's paragraph, and nothing about that moment makes it answerable later. The parts run in order and start there: what has to be true when the ask lands, and which part of it stays yours. Then the second message to a thread that's gone quiet, and how to read the silence before you send it. What to record when work leaves your desk, and how to check on it without checking up on anyone. What decides the day a reminder fires. What proves a task is finished, and which way a system should be wrong when it guesses. The last part is for anyone whose tools already work: ten alerts, all of them correct, and the morning they ruined anyway.
- 01
What turns an ask into a loop you can close
An ask arrives as one line inside somebody's paragraph. What has to be true at that moment for the loop to close later, and which part of it stays yours. - 02
Bringing a quiet thread back before it dies on you
A thread gets harder to answer every week it sits. How to read the silence, what the second message has to carry, and when to close the loop yourself. - 03
Keeping track of what you handed to somebody else
Work leaves your desk without leaving your list. What to record at the moment you hand it over, and how to check on it without checking up on anyone. - 04
Email reminders that arrive while there is still time
A list waits to be opened. A reminder comes to you. What decides the day one should fire, what it has to carry, and when to send one to somebody else. - 05
A task list that notices what you already finished
Closing a row is the step nobody performs. What actually proves a task is finished, which way a system should be wrong about it, and who confirms. - 06
Ten correct alerts, and the morning they cost you
Every prompt is true and the Monday is still ruined. Why filtering cannot fix that, what the delivery interval is worth, and what gets to interrupt you.