Your Process Shouldn’t Need Someone to Remember It

Answering the same question three times.

My first thought was: I already explained this. Maybe I needed to write it more clearly. Maybe someone missed the training. Maybe people just needed to remember.

Then it clicked. This was not a people problem. It was not a training problem either.

The process only worked if someone remembered the answer and was around to give it. Human memory had become part of the process design.

Once I noticed it, I saw the pattern everywhere: the same question coming back, “Can you remind me?” messages, information copied by hand, and one person being the only one who knows what happens next.

Those things are easy to treat as normal admin work. They are usually signals that part of the process is still living in someone’s head.

That does not mean every repeated question needs a giant automation project. Sometimes the fix is a clear note, a visible status, a template, or one next step where the work already happens.

The point is to stop making memory hold together something the process should handle on its own.

If I answer it twice, I should probably build it once.