---
title: "The Annoyance Worksheet: Turning One Bad Afternoon Into a Rule"
canonical: https://dxdev.com/blog/2026-04-30_annoyance-worksheet-turning-one-bad-afternoon-into/
datePublished: 2026-04-30
---
Seven small mistakes hit me in one sitting while I closed out a file from an office I wasn't in: a filing spot that didn't exist, a summary missing the one number I needed to check, a step that a shortened record called outstanding when it was already done, a multi-part instruction garbled inside a quick note, a deletion refused because a copy was still checked in at a second location, a form that needed four hidden fields, and the same approval requested five separate times. Each one was cheap on its own. Together they made a list worth more than the paperwork.

I didn't file those seven under "lessons learned" and move on. I wrote each one down as a rule the process should follow from now on, so nobody has to remember to be careful about it later. Here's the worksheet, in the order I hit them.

| What went wrong | What I used to do | The rule now |
|---|---|---|
| I reached for a filing spot that doesn't exist at this office | Guessed, and the guess was wrong | Ask where things actually go here, every time, instead of assuming it matches the other office |
| A summary I was handed left out the one number I actually needed to check | Trusted the summary | For anything I'm signing off on, ask for the real number, not someone's shorthand version of it |
| A shortened summary told me a step still needed doing. It had already been done | Trusted the shortened version | Check the real, unshortened record before redoing a step a summary claims is outstanding |
| I crammed a complicated, multi-part instruction into a quick note instead of giving it its own page, and it garbled halfway through | Kept trying to phrase it more carefully | Anything with more than one part gets its own document, never squeezed into a quick note |
| The system refused to let me clear a finished item because a copy of it was still checked in at a second location | Assumed the refusal was a glitch and tried to force it | Clear the copy at every location first. A refusal to delete is often the system protecting you, not blocking you |
| Nobody told me a form needed four extra fields until after I'd submitted it | Filled in what I could see and hoped | Check for hidden requirements before submitting, not after it bounces back |
| I got asked to confirm the same approval five separate times | Answered five separate prompts | One yes covers the whole task. Stop asking again unless something genuinely changes |

None of these seven were dramatic on their own. The blank form field cost maybe ninety seconds once I noticed it, the garbled note cost a re-send, the phantom already-done step nearly cost a full re-run of work that was already finished. Strung together in one sitting, seven small costs stopped feeling small.

Pain you can point at and describe in one sentence is a spec. That's the whole reframe. Every row on that worksheet became either something the process now does for me without being asked, or something it stops and flags before I can make the mistake again.

I was the only person checking this task start to finish, which is exactly why the worksheet mattered. Nobody else was going to notice the phantom already-done step, or that the refused deletion was correct rather than broken. Three weeks from now, tired, doing the same task from a different desk, I won't remember any of these seven on my own. The worksheet will.