Stop Repeating Yourself: A Seven-Day Log

Here's a small experiment, and it takes exactly one week.

Keep a note on your phone. Every single time you catch yourself repeating an instruction you know you've already given, once, twice, or fifty times before, add a line. "Told the driver again about the school pickup time." "Reminded the housekeeper, again, that the whites and colors go separately." "Said, for what feels like the hundredth time, that guests are coming Thursday."

Don't judge it while you're logging it. Just write the line and move on.

At the end of seven days, read the list back. Most admins are surprised twice. First, by the sheer number, usually somewhere between fifteen and forty repeated instructions in a single week. Second, by how few of them were actually new information. Almost everything on the list was something the other person had already been told, sometimes recently, sometimes months ago, and had simply forgotten, misremembered, or never had a way to check back on.

This is worth doing before you try to fix anything, because it turns a vague feeling, "I feel like I'm always repeating myself," into an actual, countable list. A list is something you can act on.

A few things the list usually reveals: instructions that were only ever said once, out loud, with nothing written down anywhere, so there was never anything to check back against. Instructions given to the wrong person because the right person wasn't in the room that day. Instructions that changed slightly over time without anyone updating the version everyone was working from.

None of that is a staff problem. It's a system problem, and it shows up as "I have to say everything twice" because there's no version of the instruction that outlives the moment you said it. A task that gets written once, delivered directly to the right person in their own language, and stays checkable after the fact, only has to be said once. That's the entire idea behind how Paz delivers a task.