Stop rebuilding the same checklist

You finish the task, close the tabs, and tell yourself you'll remember it next time. Then next time comes, and you have to reconstruct where you started.

The fix is not a better memory. It is a checklist someone else could follow, built from the notes you already have.

Start with the rough notes, exactly as they live in your head. Imagine a workshop host's list: export attendee list, print badges, check spelling, get final names. Four actions, plausible order, wrong sequence. The names aren't final, so printing first means reprinting later.

Step one is separating prerequisites from actions. Prerequisites are the things that must already be true: the names are approved, the file is final, the venue is confirmed. Actions are the verbs: export, check, print. Put every prerequisite above the first action and label the section clearly.

Step two is ordering with checkable verbs. "Check spelling of the final names" beats "badges." Each step should be finishable and verifiable by someone who isn't you.

Step three is the walkthrough. Hand the draft to a second person with a permitted sample, not the real data, and watch where they stall. The stall points to hidden knowledge: a step that assumed something only you know. Rewrite that step until the stall disappears.

Step four is the revision loop. Record what a walkthrough exposed, repair the affected step and test it again. Continue revising when the process changes or another operator finds a gap; two runs alone do not establish reliability.

What you end with is one reusable checklist plus its starting conditions, written so the next person begins from the same place you did. You can then check whether it reduces repeated reconstruction in your own use.

Choose one task you keep reconstructing. Write its starting condition first, before step one.