The Second Time Something Breaks
The first failure is bad luck. The second is information, and almost every venue treats them identically — fixing the symptom twice and never asking why it came back.
The question
"Why did the fix not hold?"
⚠️ Almost never asked, because the second failure is treated as a fresh event rather than as evidence about the first repair.
Three answers, and they need different responses:
The fix was a workaround. It addressed the symptom. Which was correct at 22:00 and was never followed up in daylight.
The cause is upstream. The thing that breaks is not the thing that is wrong — and repairing it will produce a third failure.
It is wear. Genuinely repeating, and the answer is a schedule rather than a repair.
Why the second time is where the information is
The first failure has no pattern. ⚠️ Nothing to learn from a single event — and reacting to one is frequently over-reacting.
The second gives you an interval. Six weeks, or a night of the week, or after a particular event. The interval is the diagnosis.
And a third is now predictable. ⚠️ Which makes it preventable, and that only becomes true at the second occurrence.
What stops it being noticed
Different people fixed it. ⚠️ Neither knows the other did — the most common reason, and it is a records problem rather than an attention problem.
Nothing was written down the first time. So there is no second time — there are two first times.
The gap was long enough to forget. Six weeks is long enough, and it is the typical interval for exactly the faults that matter.
The small habit
Write down what broke and what was done. ⚠️ Two lines — and the second line is the one people skip.
Check for it before fixing. ⚠️ Ten seconds: has this happened before? If the answer is yes, the response is different.
Mark the second occurrence explicitly. "Second time — needs a real look", so it is not quietly closed like the first.
Escalating properly
At the second occurrence, the response should change:
Stop patching. ⚠️ The third patch is more expensive than the diagnosis, and by then it has failed on a busy night.
Ask who else it affects. Frequently something else is failing for the same reason, and nobody has connected them.
Decide the interval you can tolerate. If it will keep happening, a schedule is a legitimate answer — planned, in a quiet week, rather than at 22:00 on a Saturday.
The first time costs more than you log
The fix 20 minutes
The disruption one shift running short-handed
The invisible cost nobody wrote down that it happened
⚠️ The third is what makes the second time expensive. You pay the learning cost twice because the first payment left no receipt.
One line is enough
Date. What broke. What was done. Who did it.
⇒ ⚠️ Four fields, thirty seconds. Anything longer will not be written during service, and during service is the only time the details exist.
Three failures that look like one
Same symptom, different cause three separate problems
Same cause, different symptom one problem wearing disguises
Same cause, same symptom the one worth fixing properly
⚠️ Without a log you cannot tell these apart, so every occurrence gets treated as the first one.
Who decides it is now a pattern
Nobody decides it never becomes a pattern
Anyone decides everything becomes a pattern
One person decides one line gets drawn consistently
⚠️ Pick the number, not the feeling. Three occurrences in a month is a pattern; two is a coincidence. Whatever you choose, choose it in advance.
The repair that creates the next failure
Quick fix buys tonight, costs the record
Documented fix costs ten minutes, buys the next person
⚠️ Undocumented quick fixes accumulate into a system nobody understands. The person who fixed it will not be here in six months.
The question after every quick fix
"If this happens on my night off, does anyone know what I did?"
⇒ If no, write the line. That is the whole discipline.
What to do when it breaks the third time
1. Stop fixing it the same way
2. Read the three log entries together
3. Decide: fix properly, replace, or accept and plan around
⚠️ The third option is legitimate and rarely chosen. Some things break regularly and cost less to absorb than to solve — but that has to be a decision, not a default.
The same thing failed again. It was fixed six weeks ago.
It gets fixed the same way, by the same person, with the same relief — and nobody asks the only question that matters.
Three to hold
Faults recurring within three months. ⚠️ The list is short and it is the priority list.
Whether the previous fix was recorded. If not, recurrence is invisible by construction.
Time between occurrences. ⚠️ Shortening is the signal to stop patching — and it is only visible if both were written down.
Where the record has to sit
Recognising a recurrence requires the first occurrence to be findable by whoever handles the second — which is frequently a different person on a different shift. In one person's memory, every failure is the first one.
tasteck keeps tasks and notes on the records staff open during a shift, so what broke last time is visible when it breaks again.
It is not bad luck twice. It is the same fault twice, and the only reason it looks like luck is that nobody wrote down the first one.
Related reading
Related articles
Who Types The Request In
A guest asks for somebody by name. Between that sentence and the figure on your monthly sheet, three or four people handle it. Every one of them is a place where it can quietly vanish.
What One More Regular Is Worth
Venues in this trade know what a quiet Tuesday costs them. Far fewer can say what one additional regular is worth over a year — which is the only number that tells you what you can sensibly pay to find one.
What a Listing Is Worth To One Room
A single-room salon and a twelve-room clinic get the same price from the same portal. Only one of them can work out whether that price is defensible, and it is the small one — because the arithmetic is smaller.
Map out your operations in 5 minutes
Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.
Your answers are not stored. The assessment runs entirely in your browser.
Try tasteck free for 30 days
No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.
- No card required
- Free data migration support
- All features unlocked for 30 days