How to Stop Repeating the Same Mistakes: One Line on Next Time's List Instead of a Resolution
The same mistake comes back not because you weren't careful, but because what you learned isn't where you start the work next time. Four steps — write it down, find the cause one level down, turn it into a line on the list you'll use, start from that list — and where to make the fix for each kind of mistake.
The same mistake usually comes back not because you weren’t careful enough. It comes back because what you learned isn’t where you start the work next time. So the method isn’t “be more careful next time.” It’s turning the mistake into one line on the list you’ll use next time.
There are four steps: write it down right after, find the cause one level down, turn it into a line on the list, and start the next round from that list.
This fits work that repeats — the quote you send every month, the class you run for each cohort, the video you shoot every week. Work that has a next time.
Why resolutions don’t hold
Right after a mistake, what went wrong is vivid. The trouble is that next time is weeks away. What you’ll have in hand then is the same list as last time, and the resolution isn’t written on it.
“Be careful” doesn’t say when, or what to do. “Open the attachment before sending” can go on a list and be checked off.
The four steps
1. Write it down right after
A day later, all that’s left is “something didn’t go well.” A line or two right after is enough.
- What happened — “The quote went out with last month’s unit price.”
- When you found out — “The customer pointed it out in their reply.”
2. Find the cause one level down
Ask “why?” once or twice. Look for the answer in the process, not the person.
- “Why did last month’s price get in?” → I copied last month’s file.
- “Why didn’t I catch it?” → There was no point before sending where the price gets checked.
Stop at “I’m sloppy” and there’s nothing to fix. Stop at “there was no check” and there is.
3. Turn it into a line on the list
Write the cause as an action for next time, and put it on the list you look at while doing that work.
- “Before sending, put the price sheet and the quote side by side and compare the unit prices.”
Decide where it goes, too. This line belongs at “right before sending,” not under “drafting.”
4. Start the next round from that list
If the corrected list sits somewhere and next time you start by copying the old file, nothing has changed. The place you fixed and the place you start from have to be the same.
Where to fix depends on the kind of mistake
| The mistake | Where to fix it | Example |
|---|---|---|
| Something was left out | A line on the materials or check list | “Spare battery” on the bag list |
| The order was wrong | The order of the steps | “Confirm venue” before “send details” |
| There wasn’t enough time | Move that item earlier | Booking the guest a week out instead of three days |
| You couldn’t decide in the moment | Write “if this, then that” in advance | “If the mic can’t be heard, switch to the spare” |
| You didn’t know how | Write the method on that step, or attach a photo | A photo of the light position |
We covered the “if this, then that” form of the fourth row in Implementation Intentions.
An example: the class reminder message
Someone who runs one-day classes sent the reminder the evening before, left out the parking directions, and got several phone calls the next morning.
- Write it down — “Parking directions missing; four calls on the day.”
- Cause — The reminder was written from scratch each time.
- One line — Keep the reminder text on the list, and add “check that parking, what to bring, and start time are in it” to the day-before items.
- Next time — Start the next class from the corrected list.
When the same class comes around two months later, there’s no need to remember the parking directions. They’re on the list.
Common mistakes
- Ending at “be careful.” A sentence that can’t go on a list won’t be there next time.
- Stopping at the person. “Not thorough enough” is a judgment, not a cause.
- Adding one-off things. Put in every circumstance of that day and the list gets long enough that you stop reading it. Add only what will happen again.
- Writing in one place and starting from another. The retrospective is in a notebook; the next round starts from the old file.
- Writing down only the big ones. Small frictions repeat more often. “Ten minutes connecting the printer” is a line too.
If it’s your first time
Work you’ve never repeated has no list to fix. In that case, before you start, use a premortem to write down “if this went badly, what caused it?” We covered a frame for looking back afterward in the KPT retrospective, and how to put repeating work on one page in How to Write an SOP.
Making the place you fix the place you start
Of the four steps, the one that breaks most often is the fourth: starting the next round from the corrected list.
In fecit, the app we’re building, repeating work lives as a template, and each round is a task made from that template. When you complete the task, you write what went well and what to change next time in the review. The materials you added, the step order you changed, and the lines you rewrote along the way show up in template improvement, which puts the task and the template side by side so you can pick what’s worth keeping and send it back to the template. “If this, then that” goes in Response Rules.
The next task is made from the corrected template, so the place you fixed and the place you start are the same.
Wherever you write it, the next time something goes off, write one line for the list instead of “be careful.”