On this page
This post is about one small thing: when you have an AI run a checklist every week and the list only ever grows, how to add a fixed step that takes things off.
I’m one person running weekly routine checks with an AI, but if your small team has a weekly meeting agenda, a month-end closing list, or a few sheets you check every week, it’s probably the same. Below: why the list keeps getting longer, what I wanted it to look like, and what happened the first time I ran the review.
Want AI working in your own job, not just in demos? See the 3-month 1-on-1 program →
The longer the list, the less anyone dares touch it
I’ve run into three situations.
First, the same step says “nothing this week” in the weekly report several weeks in a row. It isn’t broken. It just has nothing to report, but it still runs every week and takes up the AI’s time and my attention when reading.
Second, the rule and the run frequency don’t match. One step’s rule was “if all three conditions are met, act within 24 to 48 hours”, but the whole list only runs once a week, so it could never catch up. The detector behind it had gone nine nights in a row without a single hit before I realized it should have been shut down long ago.
Third, the same content written twice. I kept a separate dated file every week, and all three of its sections were already copied into the weekly report. I barely read it.
All three share one cause: adding a step is easy, and there’s always a reason each time. Removing one is nobody’s job.
What I wanted: subtraction with a fixed entry point
I wanted removing to come up at a set time, the same way adding does. So I added a subtraction review to my monthly routine. The rules are short:
- Look back over the last four weekly reports and count how often each step says “nothing this week”, “zero hits” or “postponed”.
- If a step comes up empty for three weeks running, or is postponed three weeks running, decide on the spot: run it less often, or drop it. Change the list right then, not next time.
- Then ask one more thing: is this step’s output copied into another document? Empty and postponed steps are easy to see. Duplication isn’t.
One more rule came after I got burned: before you take something off the list, make sure something real will trigger it elsewhere. Having its own file doesn’t count. It needs a date, a schedule or an event.
I once moved a regularly sent newsletter off the list, reasoning that it had its own project file and ran on its own rhythm. Six days later I found that rhythm had never been written down as a date or a trigger. Once it left the list, nobody called its name when its issue came due. I moved it back.
What the first run found
The first time I ran the review, no whole step had been empty three weeks running. But the first half of one step, comparing the filenames in my two AI tools’ config folders, had found zero gaps for three weeks straight, from week 39 to week 41. I moved that half from weekly to monthly.
Before demoting it I looked back at August. Over those five weeks it turned something up every single week, so keeping it weekly was right at the time. Since then the comparison has been scripted to list differences automatically each week, and I only rule on them in the first week of the month, scanning for new items the other weeks.
So a review doesn’t always end in deleting something. This time it ended in running a step less often, and there were numbers to check it against.
That’s it.