The Thing That Broke And Nobody Reported

The tap has been awkward for two months. Everyone knows the trick. Nobody has mentioned it.

Not carelessness — a calculation. Reporting it takes longer than working around it, so nobody reports it.

Why reporting loses

There is nowhere to report it to. ⚠️ The most common reason. No place, so it becomes "tell the manager when you see them", which is not a system.

Nothing happened last time. Someone reported something, it was not fixed, and the lesson was learned by everybody who watched.

It feels too small. Individually true. Collectively it is the state of your venue, and guests experience the accumulation rather than any single item.

The workaround exists. ⚠️ The trap. Once there is a trick, the fault is invisible — and it gets taught to new staff as though it were the correct method.

What the accumulation costs

Everything takes longer. Small delays multiplied by every use, every night.

New people learn the workarounds as the job. ⚠️ Nobody tells them it is broken, so they carry it forward, and after a year nobody remembers it was ever different.

Guests notice the sum. Not the tap. The general sense that things here are slightly worn, which is a real and unattributable impression.

Something eventually fails properly. Usually at the worst moment, and usually the thing that had been awkward for months.

Making reporting cheaper than coping

One place, always available. ⚠️ On the screens people already use — anything requiring a different app, a form, or finding a manager will lose to the workaround every time.

Ten seconds, one line. What, where. No detail requirement, no category — every field added reduces reports.

Anyone can report. No filtering by seniority. The person who notices is the person who uses it.

Say what happened. ⚠️ The one that determines whether anyone reports again. Fixed, scheduled, or declined — all three are acceptable. Silence is not.

The quarterly sweep

Reporting only catches new faults. The old ones have workarounds and are invisible.

Once a quarter, ask: what do we work around? ⚠️ Phrase it exactly that way — "what is broken" gets nothing, because staff have stopped classifying these as broken.

The list will be longer than expected, and most of it will be quick.

Do the quick ones that week. Visibly. The visibility is what makes the next sweep produce answers.

Prioritising

Not everything, and not by how annoying it is:

Anything that will fail worse if left. Usually cheap now, expensive later.

Anything a guest can see or touch. ⚠️ Weighted higher than staff-side annoyances, uncomfortable as that is.

Anything costing time on every use. Small × frequent is frequently the largest total.

Anything with a safety dimension. Immediately, regardless of cost.

Reporting loses on cost, every time

Working around it  ten seconds
Reporting it   two minutes of deciding who, where, and how to phrase it

⚠️ And nothing comes back. Report twice with no visible outcome and the third time you work around it — which is arithmetic, not attitude.

---

Three costs of letting it pile up

The workaround becomes the method  new staff learn it as the way things are
Faults overlap        you can no longer tell which one causes what
Reporting itself stops    the expensive one

⚠️ The third is not about equipment at all. A place where small things go unreported is a place where large things will also go unreported, and that is discovered at the worst possible moment.

---

Make reporting cheaper than coping

Reportable from where they are standing  no walking
One sentence         no form
Answered when fixed      the report closes

⚠️ The third is what keeps the other two working. 　 ⇒ Reply even when it cannot be fixed. "We are not fixing this" is a 　 　 far better answer than silence, because silence teaches people to 　 　 stop.

---

The quarterly walk

Waiting for reports  finds what people bothered to report
Walking around   finds what they stopped reporting

⚠️ Look for workarounds, not for faults. A handwritten note, a chair in an odd place, a thing everyone verbally warns each other about — each one marks something that was never reported. 　 ⇒ Fifteen minutes, quiet hour, together.

---

Sort by nights, not by price

Not by cost  Not by age
But by how many nights somebody works around it

⚠️ A small nightly cost outweighs a large one-off, and it is the category that never reaches the top of a list sorted any other way.

---

---

Three to hold

Faults reported per month. ⚠️ Low is not good — it means people have stopped bothering, and the faults are still there.

Days from report to resolution. The number that determines whether reporting continues.

Items on the last workaround sweep, and how many are fixed. The measure of whether any of this is real.

Where the record has to sit

A fault reported verbally to whoever was nearest is not recorded. It has to sit where the person who fixes things will look, with a date, or the report is indistinguishable from not having mentioned it.

tasteck keeps tasks on the staff-facing screens people already use during a shift, so a fault has somewhere to go that is not a conversation.

Nobody hid it. Reporting it was slower than working around it, and your team is doing the arithmetic correctly.

---

Read next

• The Second Time Something Breaks
• The Report You Should Read Every Monday
• Two Venues, One Owner, and No Comparable Numbers
• The Maintenance You Only Do When It Breaks
• The Report Nobody Reads