The Cost Of Saying Yes To Everything

A regular asks for something slightly outside the normal. Somebody says yes, because saying yes is the job.

Six months later there are forty of these, none of them written down, and a new member of staff has no idea that the man at table nine always gets the good glasses.

Every one of them was the right call. Together they are a venue nobody can run without having been there a year.

Three kinds of yes

They look identical in the moment and behave completely differently.

The one-off. Something for tonight. Costs nothing, creates nothing, and correctly disappears. Most requests are this.

The precedent. Granted once, expected forever. ⚠️ The guest is not being difficult — they reasonably assume that what happened last time is how it works. This is where the forty come from.

The improvement. An exception so obviously better that it should stop being an exception. Rare, valuable, and usually spotted by whoever is on the floor rather than by management.

The failure is not saying yes. It is never sorting the yeses into these three.

The question that sorts them

Asked once, at the end of the night, about anything unusual that was granted:

"If we did this for everyone, would it still work?"

Yes → make it the standard. It was an improvement. No, but this guest specifically → write it on that guest's record. It is theirs. No, and it was just tonight → let it go.

⚠️ Thirty seconds, and it is the entire system. The alternative is that the sorting happens implicitly, by memory, unevenly.

Why the forty are dangerous

Not the cost of each. The cost of the accumulation:

They are unevenly known. Some staff know them, some do not, so the same guest gets different treatment depending on who is on — which is worse than never having granted it.

They cannot be handed over. A new manager inherits a room with forty unwritten rules and discovers them by breaking them.

They constrain without being visible. A change to the pricing, the layout, or the menu collides with exceptions nobody remembered until a guest complains.

Writing them down does not make them rigid

The common objection: writing exceptions down turns a warm room into a bureaucracy.

It does the opposite. An exception on the guest's record means the next person can also deliver it. An unwritten exception is not warmth; it is warmth that only works when one specific person is working.

⚠️ What to write is the exception, not a justification. "Prefers the far booth, always sparkling" — not a paragraph about why.

The one to be careful with

Exceptions to the money.

A comped item, a discounted rate, a waived charge. These compound differently: they set an expectation about price, and price expectations are much harder to walk back than service ones.

Anything involving money should be a decision with a name attached and an end date, even if the end date is "review in six months." Otherwise a discount granted once in 2024 is still being honoured in 2027 by people who assume it is policy.

The check worth running once

Ask three long-serving staff to list the exceptions they know about.

⚠️ Compare the lists. The overlap is your actual policy. The non-overlap is the part that fails whenever the wrong person is working — and it is usually larger than anyone expects.

Three to hold

Exceptions recorded against guests. If the number is near zero, they are all in people's heads.

Overlap between staff on the informal ones. How reliably an exception actually gets delivered.

Money exceptions with no end date. The ones that quietly become policy.

Where the record has to sit

An exception in someone's memory works while they are on shift and nowhere else. That is not a documentation problem; it is a delivery problem, and it fails in front of the guest.

tasteck keeps notes against the guest record, so what was granted once is in front of whoever serves them next.

Every yes was right. Nobody was keeping the list, and the list is now the venue.