Writing a repeatable task that actually gets done

Small, specific, and ordered the way you actually work.

Updated June 2026 · 2 min read

Every abandoned checklist has the same two problems: it is longer than the time you have, and it describes outcomes rather than actions.

Make it fit the gap you actually have

A task built for a clear hour will be skipped on every day that does not contain one, which is most days. Build for the ten minutes you reliably have and let good weeks overshoot.

A step is something you do, not something you achieve

Instead ofWrite
Do outreachOpen the shortlist
Follow up with peopleOpen Sent, filter to due
Update the sheetPaste the three names into column A

The test is whether someone else could do the step without asking a question. If not, it is a goal wearing a checkbox.

Put the friction in the step

If a step needs a link, the step should carry the link. If it needs a line of text, the step should hold the text ready to copy. Every detail you have to go and find is a place the task can stall.

A checklist that makes you open a bookmark folder is a checklist you will do four times.

Order it the way your hands work

Group by the tool, not by the topic. Three things in the browser then two in the spreadsheet beats alternating, even when alternating is more logical on paper.

Let the reminders be reminders

Some steps are not actions at all — they are the thing you always forget. Keep them in the list but do not make them tickable. A note that says "check the invoice number matches" belongs there without pretending to be work.

Questions

How long should a task be?
Short enough that finishing it is the normal outcome. If you routinely stop halfway, it is two tasks.
Should a task ever be finished?
The blueprint never is. Each day it produces a run, and the run is what you finish.

Start with one task

The whole working product is free. Reports and the extension are $5 a month, and only if you want them.