Where You See the Problem Is Rarely Where It Started
It was 21:00 on a warm Friday night.
The bar was in complete meltdown.
Guests at the counter were waving credit cards, phone lines were ringing out unanswered, ticket slips were spilling off the printer onto the floor, and drink times for seated tables were creeping past 20 minutes.
The general manager walked past, saw the chaos, and made a swift, logical assumption:
The bar staff are underperforming, and we have more demand than we are currently capturing.
His solution?
He walked into the back room, grabbed armfuls of terrace chairs, and dragged them outside to set up extra seating.
If the house was this full, he reasoned, more capacity meant more revenue.
Within 15 minutes, the entire operation collapsed.
Here is what the manager missed.
The venue had hired three bartenders and given each of them four completely incompatible jobs to run simultaneously:
- Take telephone orders
- Handle guest payments
- Serve the live bar counter
- Produce all floor drinks
The bartenders weren't slow.
They were physically trapped in a structural bottleneck.
By dragging out more terrace chairs, the manager didn't fix the engine—he stepped on the accelerator while the transmission was falling out onto the highway.
He looked at where the failure became visible and tried to treat the surface symptom.
The terrace looked like unused revenue.
The bar saw something completely different: more orders entering a system that was already struggling to process the ones it had.
More demand wasn't the opportunity. At that moment, more demand was load.
The Dashboard Principle: Where the Symptom Appears Does Not Tell You Where the Fault Began
When a warning light flashes on your car's dashboard, you do not pull over, open the instrument cluster and replace the dashboard bulb.
The dashboard did its job.
It gave you a signal.
But the actual fault—a loose belt, a dead sensor, a fluid leak—may be sitting somewhere completely different inside the machine.
Hospitality operations work the same way.
A kitchen printer screaming at 20:15 tells you something.
It does not automatically tell you that the kitchen is the problem.
A queue at the bar tells you something.
It does not automatically tell you that the bartenders are too slow.
A manager being called every five minutes tells you something.
It does not automatically tell you that the team needs more training.
The visible breakdown is the dashboard light.
The question is what caused it to come on.
[ Visible Breakdown ]
↓
Where the stress becomes visible
Bar · Kitchen · Pass · Floor · Manager
Trace the operational signal backwards
↑
[ Point to Investigate ]
Where the condition may have started
Workflow · Information · Responsibility · Setup · System Design
Sometimes the fault really is where the symptom appears.
Sometimes it began ten minutes earlier at another station.
Sometimes it began hours earlier during setup.
And sometimes what looks like an employee problem is the predictable result of the way the operation was designed.
You don't know until you trace it.
A Diagnostic Tool Doesn't Actually Diagnose
There is a language problem here.
Operators often search for a hospitality operational diagnostic tool because they want something that will tell them what is wrong.
The phrase makes sense. We use similar language around cars, computers, medicine and machinery.
But there is an important distinction.
Imagine walking into a doctor's surgery because you don't feel well.
The doctor may take your blood pressure, run a blood test, check your temperature or put you on a scale.
Those instruments produce readings.
They do not diagnose you.
A blood-pressure monitor cannot look at a reading and prescribe medication.
A weighing machine cannot look at your weight and tell you why you weigh what you do.
The measurement is real.
What that measurement means still has to be interpreted.
Only then can a diagnosis be made.
And only after diagnosis should somebody start talking about prescription or treatment.
Hospitality operations are no different.
The queue at the bar is a symptom.
Twenty-minute drink times are measurements.
Three bartenders simultaneously answering phones, taking payments, serving counter guests and producing floor drinks are observations.
Those are signals.
They give us evidence.
But none of them, on their own, is the diagnosis.
The sequence matters:
SYMPTOM → MEASUREMENT / SIGNAL → INTERPRETATION → DIAGNOSIS → PRESCRIPTION → INTERVENTION
Skip one of those stages and an operator can end up prescribing a solution before understanding the problem.
That is exactly what happened that Friday night.
The manager saw the symptom.
He interpreted it immediately.
Then he prescribed an intervention:
More chairs. More guests. More revenue.
He went from symptom to prescription without properly examining what the operation was telling him.
And the result was predictable.
He added load to the very system that was already signalling that it could not carry the load it had.
So Why Call It a Hospitality Operational Diagnostic Tool?
Because that is the language operators use when looking for something that can help them understand what is going wrong.
But at 6th Sense Hospitality, we make the boundary clear:
The tool does not diagnose your business for you.
It helps you gather and structure the signals from which a diagnosis can eventually be made.
Think of it as the instrument in the doctor's hand—not the doctor, and certainly not the prescription pad.
That distinction isn't semantics.
It changes what you do next.
Don't Confuse the Reading with the Diagnosis
When an operator sees a breakdown during service, the instinctive reaction is intervention.
Add more staff.
Buy a bigger printer.
Open more seating.
Change the rota.
Lecture the team before tomorrow's shift.
Replace the software.
But fixing what you can see before understanding what produced the signal can create two expensive problems.
First, you can spend money treating the wrong part of the operation.
Adding labour hours, buying equipment or changing software may increase overhead without removing the condition that produced the problem.
Second, you can make the original bottleneck worse.
That is exactly what happened when more chairs were dragged onto the terrace.
The manager saw demand and added capacity at the guest end.
But the production end had no capacity left to absorb it.
He didn't remove the bottleneck.
He fed it.
A useful operational reading therefore shouldn't begin with:
“How do we fix this station?”
It should begin one step earlier:
“What exactly are we seeing—and what happened before it arrived here?”
Tracing the Signal: A 3-Step Reading
Before spending money or changing the operation in response to a live service problem, separate the signal from your interpretation of it.
- Acknowledge the Signal
Treat the visible breakdown as evidence that something deserves attention—not proof that you already know the cause.
Long wait times are a signal.
Missed calls are a signal.
Ticket backlogs are a signal.
A manager repeatedly being pulled into routine decisions is a signal.
Staff beginning to guess is a signal.
Record what happened before deciding why.
- Trace Backwards
Move backwards from the point where the problem became visible.
What happened 10, 20 or 60 minutes earlier?
What fed work into this station?
Where did the information come from?
Who made the previous decision?
Did something wait, get repeated, require clarification or depend on somebody's memory?
You are not yet looking for someone to blame.
You are reconstructing the route the signal travelled.
- Identify Where to Investigate
Now ask whether the evidence points towards the station where the problem appeared—or somewhere else in the operating chain.
You may be looking at an execution problem.
You may be looking at a hand-off problem.
You may be looking at conflicting responsibilities.
You may be looking at a system-design problem.
Or you may still not have enough evidence to know.
That last answer is perfectly acceptable.
A reading is valuable because it gives you a better question.
It does not need to manufacture an answer.
The Bartenders Weren't the Diagnosis
Go back to that Friday night.
Three bartenders.
Four competing responsibilities each.
Telephone orders were competing with guests physically standing at the bar.
Payments were competing with drink production.
Floor tickets were competing with both.
Every new guest added another demand to the same constrained system.
From outside the bar, the visible signal was:
Slow service.
The easy interpretation was:
Slow bartenders.
But observing the mechanics exposed a different question:
Could three people realistically execute these competing responsibilities simultaneously under that level of demand?
That is a much more useful question.
And it could not be answered by staring harder at the queue.
The Reading Comes Before the Diagnosis
This is the distinction that matters.
A tool doesn't need to tell you:
“Here is exactly what is wrong with your business.”
And it certainly shouldn't promise:
“Do this and your profits will increase.”
Its first job is more fundamental.
It should help you distinguish between what you are seeing and what you actually know.
That is the same reason a warning light exists in a car.
The light isn't the mechanic.
It isn't the repair.
And it isn't the diagnosis.
It tells you:
Something here deserves investigation.
The same applies to a weighing machine.
The number on the scale is a measurement.
It doesn't explain why the number is there.
It doesn't diagnose the person standing on it.
And it doesn't prescribe what should happen next.
The reading comes first. Interpretation comes next. Diagnosis comes after that.
That distinction can be enough to stop an operator from spending thousands fixing the wrong thing.
Get a Structured First Reading
You don't need a massive consulting engagement every time something in the operation feels wrong.
Sometimes you need a structured way to stop reacting to the surface symptom and examine what is actually happening.
The €7 Operational Diagnostic Tool gives operators a structured starting point for examining live service friction, recording what is actually happening and tracing operational signals backwards before deciding what those signals mean.
Despite the name operators commonly search for, the tool itself is not the diagnosis.
It gives you the reading. You still have to interpret what the reading is telling you.
Only then should you decide what—if anything—needs to change.
Before you drag more chairs onto the terrace, make sure your engine can actually turn the wheels.
Explore the €7 Operational Diagnostic Tool.
“If your team starts to guess, the money has already left the building.”
The NAVIGATOR Method™ — powered by Signal Mapping.
Trust the signal. Question your interpretation.
Article by
Amos J. Amolo
Amos Jactone Amolo is the founder of 6th Sense Hospitality and an Operations System Designer with more than 30 years of experience across food & beverage, live events, catering and venue operations. He still actively owns and operates hospitality and event businesses, so his observations are not based on what the industry used to look like. They are being tested on the floor today.
His perspective was built — and continues to be tested — in live operating environments where decisions happen in real time. He watches what changes when an operation comes under pressure: where timing slips, information stops moving, responsibility becomes unclear and people begin compensating for a system that is no longer helping them.
Just as importantly, he watches the customer. Changing drinking habits, new expectations around food, shorter attention spans and the increasingly visual way guests make buying decisions are already changing how hospitality needs to operate.
That thinking forms the foundation of 6th Sense Hospitality: look beyond the obvious symptom and find where people, process, technology, money and decision-making have stopped working together.
His core philosophy is simple:
“If your team starts to guess, the money has already left the building.”
Through 6th Sense Hospitality, Amos develops practical diagnostics and operational systems that help operators see what is actually happening inside their businesses — before workarounds become accepted as normal.
Not theory. Still operating. Still observing. Still testing what actually works.
Disclaimer
The content published by 6th Sense Hospitality is provided for informational and educational purposes and reflects practical hospitality experience and operational analysis. It is not intended as legal, financial, tax, HR, or other professional advice. Business circumstances vary, and readers should seek appropriate professional advice where necessary.
