How checklists actually get written
Not on the quiet afternoon that never comes — during the task itself, twenty minutes at a time. Ten of them documents most of a role.
Every company has a documentation plan, and it's usually the same one: “when things calm down.” Things don't calm down — and writing procedure from memory is miserable anyway, which is why the plan quietly fails everywhere it's tried.
The version that works skips memory entirely. The next time a recurring task comes up — month-end invoicing, onboarding a customer, closing out a job — narrate it into a document while doing it. Fifteen numbered steps, screenshots optional, about twenty extra minutes. Then hand it to someone else and watch where they stumble. Every stumble is an edit, and after two passes the checklist knows things memory never did.
Ten of these covers most of a role — which is the real point. A business where the steps live in one person's head can't take a vacation, can't hire smoothly, and can't survive a two-week flu. Twenty minutes at a time buys the way out — not on some quiet afternoon, but inside work that was getting done anyway.
Filed under Operations & Systems