When the Answer Is Next Door

A group ordered a round of hot drinks in a city-centre bar.

“We’ve run out of milk, sorry.”

Fair enough. Things run out. Deliveries are late. Forecasts are wrong. Someone orders six flat whites when you were expecting a quiet Tuesday.

Except there was a convenience store next door.

And suddenly “we’ve run out of milk” means something slightly different.

Because the problem isn’t really that there’s no milk. There’s plenty of milk. It’s about ten metres away.

The problem is that nobody went to get it.

The interesting bit isn’t the milk

It would be easy to file this under poor stock control. But that’s not really what’s interesting.

The bar probably had a perfectly sensible system for ordering milk. On this occasion, the system failed. That happens.

What matters is what happened next.

From the customer’s point of view, the solution was almost comically obvious. Pop next door. Buy a bottle of milk. Make the drinks.

Instead, the failure of the normal system became the customer’s problem.

Nobody running the business had necessarily decided that should happen. The member of staff may have been following the rules perfectly. Perhaps they weren’t allowed to leave the bar. Perhaps they couldn’t spend company money without permission. Perhaps it simply didn’t occur to them that buying milk next door was something they were allowed to do.

But customers don’t see any of that.

They just see a shop full of milk next door and a bar telling them they can’t have coffee.

Rules work brilliantly. Until they don’t.

Most hospitality businesses need systems.

You need ordering procedures, staffing rules, spending controls and recipes. You can’t run a business by having everybody improvise all day.

But hospitality has an awkward habit of producing situations nobody wrote a procedure for.

The coffee machine stops working. An ingredient disappears. Somebody wants something that isn’t quite on the menu. A delivery doesn’t turn up.

Eventually, somebody has to make a judgement.

And this is where the difference between following the system and understanding what the system is trying to achieve becomes important.

If the instruction is simply “follow the process”, the milk has run out and that’s the end of the story.

If the instruction is “within reason, solve the customer’s problem”, somebody starts looking next door.

Owners do this without thinking

Imagine the owner had been behind the bar.

Would they have said, “Sorry, no milk”?

Maybe.

But there’s a decent chance they’d have stuck £2 in somebody’s hand and said, “Can you nip next door?”

They wouldn’t regard this as a bold act of entrepreneurial leadership. They probably wouldn’t even remember doing it by the end of the day.

That’s because the owner already understands something the employee may not.

They know what matters.

They know which rules are important and which can bend. They know that spending a couple of quid to keep a table of customers happy is probably a sensible trade. And crucially, they know they’re allowed to make that decision.

The challenge is getting that understanding out of the owner’s head and into the business.

“Look after the customer” isn’t enough

Most hospitality operators would probably say they want staff to look after customers.

The problem is that this is easy when everything is working.

The real test comes when looking after the customer requires someone to depart slightly from the normal routine.

That doesn’t mean giving everyone unlimited discretion.

There can still be sensible boundaries around spending money, leaving a position unattended or making decisions that affect the wider operation.

But inside those boundaries, staff need to know that solving straightforward problems is part of their job.

More importantly, they need to know they’ll be backed when they do it.

Because if using initiative carries a small risk of getting told off while doing nothing carries no risk at all, doing nothing is the rational choice.

And now you’re out of milk.

Small problems tell customers big things

The financial loss from that round of hot drinks was trivial.

The more interesting cost was the story the incident told about the business.

Not necessarily a dramatic story. Nobody needs to storm out, write a furious review or vow never to return.

It’s subtler than that.

Maybe the group doesn’t stay for another round. Maybe somebody suggests a different bar next time. Maybe, when faced with two nearby options a few weeks later, this one feels just a little less appealing.

Customers know almost nothing about how a hospitality business actually operates. So they build their impression from the tiny bits they can see.

And strangely enough, a missing bottle of milk can tell them quite a lot.

What this looks like in practice

Give people enough clarity and authority to solve reasonable customer problems without waiting to be told exactly how.

Use real examples rather than vague instructions about “great service”. Talk about the missing ingredient, the unusual request or the minor problem that could have been fixed before the customer had to accommodate it.

Set some boundaries. Perhaps that means a modest amount staff can spend without approval. Perhaps it means clarity about when somebody can leave their position. Perhaps it simply means making clear which decisions genuinely need a manager.

Then comes the important bit.

When somebody makes a reasonable decision within those boundaries, back them.

Even if it isn’t exactly what you would have done.

Because the goal isn’t to produce employees who can perfectly predict the owner’s answer.

It’s to produce people who understand what the business is trying to achieve well enough to find their own.

Sometimes that means following the system.

And sometimes it means going next door for a bottle of milk.