Checklists people actually read
A checklist is not a list of things to do. It is a list of things that get forgotten.
The Checklist module holds repeatable procedures: the steps for a release, an onboarding, a monthly close, a client handover. It works well for those and badly for everything else, and knowing the difference is most of the value.
A checklist is not a to-do list
A to-do list is what you plan to do once. A checklist is what you do every time, and it exists because the steps are known and still get missed.
So a checklist item should never be the interesting part of the work. "Design the new page" does not belong on one. "Check the page on a phone before sending it" does — it is small, it is skippable, and skipping it is how the last three problems happened.
Long lists get ticked, not read
Past roughly nine or ten items, people stop reading and start clearing. You can watch it happen: the last third of a long checklist is always completed faster than the first third, regardless of what the steps say.
If yours is longer, it is usually two checklists wearing one name — a preparation list and a delivery list, say. Split them and let each be used at the moment it applies. A checklist used at the wrong time is a checklist ticked from memory.
Write each item as a check, not a task
"Backups" is not an item. "Confirm last night's backup completed" is. The difference is that the second one has an answer — yes or no — and you cannot tick it honestly without going to look.
Where it matters, say what good looks like inside the item. "Confirm the export has more than 0 rows" survives being read at eleven at night by someone who did not write it, and that is the real test of every checklist.
Write them after something goes wrong
The best checklists are not designed, they accrete. Something is missed, it costs an afternoon, and the fix is one line added to the list so it is never missed again.
This also keeps them short, because nothing gets added speculatively. If you cannot point to the time an item would have saved you, it is probably decoration — and every decorative item makes the necessary ones slightly less likely to be read.
Questions people actually ask
What belongs on a checklist and what does not?
Small, skippable steps that get forgotten — not the interesting part of the work. “Design the new page” is a task; “check the page on a phone before sending” is a checklist item.
How long should a checklist be?
Under about nine or ten items. Past that people stop reading and start clearing. A longer list is usually two checklists sharing one name — split them and use each at the moment it applies.
How should items be worded?
As a check with a yes-or-no answer, not a topic. “Backups” is not an item; “confirm last night's backup completed” is, because you cannot tick it honestly without looking.
