When we design how we are going to work, we design for an imaginary person. Someone who will remember the plan, stay motivated, and follow through on what they meant to do. We build for our best self, the one making the plan, full of intention and clarity.
That person does not show up on most days. The person who actually has to run your system is tired, distracted, and has forgotten half of what you so carefully decided. If you build only for your best self, you are building for someone who rarely arrives.
Key Takeaways
- We design our systems for an imaginary best self, who remembers the plan, stays motivated, and follows through.
- The person who actually runs your system is tired, distracted, and has forgotten half of what you carefully decided.
- Anything your system needs you to recall is a weak point, because you will eventually forget it at the worst time.
- The next step should be visible, not remembered; the trigger should live in your environment, not in a mental note.
- Test your system on a bad day, not a good one; the bad day is the real examiner of whether the design actually holds.
The person who forgets is the real user
Here is the shift. The version of you that matters most is not the one making the plan. It is the one who has forgotten it. The one who, three weeks from now, will not remember why you set things up this way, what the next step was supposed to be, or even that a system existed at all.
That person is not a failure of discipline. That person is normal. Memory fades, attention scatters, and intentions made on a clear morning do not survive a heavy week intact. A system that assumes otherwise is built on sand.
Design so memory is not required
The fix is to stop relying on remembering. Anything your system needs you to recall is a weak point, because you will eventually forget it at the worst time.
So put it outside your head. The next step should be visible, not remembered. The reason for a choice should be written down where you will find it, not stored in a memory that will fade. The trigger that starts an action should live in your environment, a place, a time, an object, not in a mental note you are hoping to keep. A good system works even when you have forgotten it exists, because it does not wait for you to remember. It simply presents the next thing.
How to build for the forgetful version
Walk through your system and ask one question at each step. What happens here if I have forgotten everything? If the answer depends on you suddenly recalling something, that step will fail. Replace the memory with a written cue, a visible prompt, or a fixed place.
Then test it on a bad day, not a good one. The good day will forgive almost any design. The bad day, the forgetful, depleted, distracted day, is the real examiner. If your system carries you through that, it will carry you through anything.
This is what System means in the Method: infrastructure built for the version of you who shows up on an ordinary day, not the one who wrote the plan.
Build for the version of you who forgets. It is the most honest, and the most forgiving, thing you can do for yourself.
