How often to repeat an instruction before changing the system?

The most useful rule comes down to one number: three. Once you have repeated the same instruction three times, to different people or to the same person without effect, it is no longer a reminder issue but a system issue. The instruction exists in your head, not in anything the team runs into at the moment of the task. Fixing it means writing it down once, tying it to a role and making it show up at the right time.

The hotel pan that never gets covered

Saturday, 11:40. You walk through the kitchen at your first site. A pan of sauce has been left uncovered next to the pass. You tell the station cook, who apologizes. The Tuesday before, you told a commis at your other site. Three weeks earlier, it was in your Sunday night voice message.

Nobody is acting in bad faith. Each time, the instruction was understood, acknowledged, then lost. It never had an address: no responsible role, no time, no medium. It lived only in your mouth, and your mouth cannot be in three kitchens at 11:40.

Why a repeated instruction is not a transmitted instruction

Four causes show up almost every time.

• It has no recipient. "We should cover the pans" points at nobody. A useful instruction starts with a role: "the prep commis covers."
• It has no moment. An instruction without a time gets forgotten. One that arrives at the end of prep, in the hourly list, gets done.
• It lives in a channel that scrolls away. Voice message, group chat, an offhand remark: it all sinks into the stream. The next day, nobody can find it.
• It has no reason. Without the "why," everyone adapts it. The commis who knows that an uncovered pan attracts flies and a failed health inspection will follow it for longer.

Six steps to replace repetition

1. Count for two weeks. You, on your phone, note every instruction you repeat. No judgment, no sorting: a counter.
2. Keep three instructions. The ones that come up most. Not ten. Three.
3. Write each one in four lines. The goal, the exact action, the mistake to avoid, and the proof it is done (wrap on the pan, a photo, a signed box).
4. Assign it to a role, not a person. The role survives departures and replacements.
5. Put the instruction where the task happens. In the opening checklist, in the new hire's welcome, in the training for the station. If it does not arrive on its own, it will not be applied.
6. Stop repeating it for a month. That is the test: if the lapse comes back, it is not the medium, it is its location or its timing that needs to change.

The decision table

What you observe	What it tells you	What you change
Same instruction repeated to different people	No shared medium	Write it once, assign it to a role
Same instruction repeated to the same person	Wrong moment or wrong place	Move it to the task it concerns
Instruction followed only when you are there	No proof is asked for	Add a minimal proof
Instruction applied differently from one site to another	Several versions in circulation	One source, one revision date
Instruction forgotten after someone leaves	It lived in a single head	Pass it on through the role, not the person

Common mistakes

• Writing a ten-page procedure for a ten-second instruction. Nobody will open it. Four lines.
• Sending the new version by message without removing the old one. You create two truths.
• Picking ten instructions at once. The team retains none of them. Three, then three more.
• Confusing a reminder with a check. You add one more verification when the problem was the missing medium.

To see what happens when a procedure fails in an informal channel, read why a procedure buried in WhatsApp is not a procedure. If your instructions are already on a list but change nothing, see why restaurant checklists often change nothing. When the instruction is understood but applied differently depending on who supervises, the issue becomes training new hires differently at every location. And if you worry that everything walks out the door with a departure, look at what leaves with your best manager.

What to measure

• The number of times you repeat each of your three instructions in a month. It should trend toward zero without you running more checks.
• The delay between a changed instruction and its application at every site. You read it by asking one team member at each site to show the version they follow.
• The number of versions of the same instruction in circulation. One is the target.

Where Tsuno comes in

Tsuno starts from a promise: "You've already said it. Tsuno remembers." What you keep repeating (a task, an instruction, a typical day) is written once, assigned to a role, then passed on through checklists, training and the welcome of new hires. You can then ask in plain language what was done or not, and at which site, and Tsuno answers from the recorded facts. Tsuno does not judge people: if an instruction is not applied, we look at the process or the training. The general principle is detailed on the Tsuno solution page.

Key takeaways

Three repetitions is the signal. Beyond that, you are no longer passing something on, you are compensating. Write the instruction once, give it a role, a moment and a proof, then stop repeating it to check that the medium holds.