Short checklists.

If I do something more than twice, I write the steps down.

A lot of my week is made of tasks that repeat. Closing out a month. Setting up a new account. Publishing a page. Handing something to a colleague in another time zone. None of it is hard. That is exactly the problem. Easy work is the work I am most likely to do from memory, and memory is where steps quietly go missing.

So I keep short checklists. Not manuals, not long documents with headings and diagrams. Five to ten lines, in plain words, in the order I actually do them. The kind of list you can read in under a minute and follow without thinking too hard.

The rule I use is simple: the second time I do something, I notice. The third time, I write it down. By then I have done it often enough to know the real steps, not the ones I imagined the first time. And I have usually forgotten one of them at least once, which tells me where the list matters most.

A good checklist is mostly about the boring parts. The step everyone knows but nobody remembers. Confirm which currency the report is in. Check that the link opens on a phone. Tell the person waiting that it is done. These are the things that slip when the day gets busy, and they are the things that cause the follow-up emails.

I keep the lists close to the work. If the task happens in a spreadsheet, the checklist sits in the first tab. If it happens in a folder, there is a short text file at the top. The point is that the list is in front of me when I start, not somewhere I have to remember to go looking.

Lists also make handoffs kinder. I work across Latin America and the United States, with people in eCommerce, payments, and health companies, and not everyone is awake at the same time. When I pass something along with a checklist, the other person doesn’t have to guess what I meant or wait for me to wake up. They can see what is done, what is left, and what I usually check before calling it finished.

The lists change. When a step stops being useful, I cross it out. When something goes wrong that a step would have caught, I add it. A checklist that never changes is probably not being used. One that gets a small edit every few weeks is doing its job.

I don’t follow them perfectly. Some days I skip the list because I am sure I remember, and most of the time I do. The times I don’t are the reason the list exists.

There is a quiet relief in it, too. When the routine steps are written down, I don’t have to carry them around. That leaves more room for the parts of the work that actually need thinking. The checklist handles the ordinary. I get to pay attention to the rest.

If you want to try it, pick one task you did this week that you will do again next week. Write down the steps while they are fresh. Keep it short. Use it once and fix whatever was wrong. That’s all a checklist needs to be.