HOSPITALITY INSIGHTS · OPERATIONS & FLOW
Part of the Operations & Flow series — examining where movement, information and capacity begin to break down when hospitality operations come under load.
A restaurant bottleneck is easy to see.
Orders pile up.
Guests wait.
The pass fills.
Servers start asking where their food is.
Someone calls for another pair of hands.
The manager jumps in.
Everybody moves faster.
Naturally, everybody looks at the place where the queue has formed.
That's not necessarily where the problem is.
After more than 30 years inside hospitality operations, this is one of the things I have learned to distrust:
The place where pressure becomes visible is not always the place where pressure was created.
That's why restaurant management bottleneck analysis shouldn't begin with:
Who is too slow?
It should begin with:
What is preventing the operation from moving?
Those are two completely different questions.
Think About a Motorway
Imagine traffic has stopped.
You're sitting in a queue with hundreds of cars.
From where you're sitting, the problem appears obvious.
Too many cars.
But five kilometres ahead, perhaps two lanes have become one.
That's the constraint.
Adding another car behind you doesn't solve it.
Telling everybody to drive faster doesn't solve it.
And blaming the driver directly in front of you certainly doesn't solve it.
You have to find the point where flow changed.
Restaurants behave in much the same way.
The queue may be visible at the pass.
But that doesn't mean the problem started at the pass.
Something may have changed earlier in the operation.
A delay.
A dependency.
A decision.
A piece of information that didn't move.
Capacity that stopped matching demand.
The important distinction is simple:
Don't analyse only where the queue ends. Ask where the flow changed.
A Bottleneck Doesn't Have to Look Broken
When people hear “bottleneck,” they often imagine something obviously failing.
A slow grill.
A broken printer.
A bartender who can't keep up.
A POS terminal taking too long.
Those can certainly become bottlenecks.
But some of the most expensive constraints look completely normal.
Imagine four cooks can each produce their part of an order quickly.
Excellent.
But every completed plate has to pass through one person before leaving the kitchen.
If that person can only clear orders at a certain rate, adding another cook may achieve very little.
You've increased capacity before the constraint.
The bottleneck hasn't disappeared.
You've simply created a bigger queue in front of it.
That's why adding staff to a struggling restaurant can sometimes produce:
More bodies. More movement. More communication. Same constraint.
Headcount is not automatically capacity.
Watch What Starts Waiting
Pressure has an interesting habit.
It makes things wait.
People wait.
Orders wait.
Ingredients wait.
Plates wait.
Information waits.
Decisions wait.
Payments wait.
And when something that normally moves suddenly begins waiting, the operation is telling you something.
It isn't necessarily telling you what the problem is.
That's an important distinction.
It is giving you evidence.
The mistake is seeing the evidence and immediately naming the cause.
The Screaming Printer
This is one of my favourite operational traps.
The printer starts screaming.
Tickets keep coming.
The rail fills.
Everybody looks at the printer.
But the printer may be doing its job perfectly.
It's simply showing you that demand is arriving faster than the operation can currently absorb it.
The screaming printer is a signal.
Don't confuse the signal with the cause.
The same thing happens all across hospitality operations.
The visible problem attracts the attention.
The underlying constraint can remain untouched.
Bottlenecks Move
Suppose the grill really is the constraint.
You increase its capacity.
Problem solved?
Perhaps.
Until food begins reaching the pass faster than the pass can handle it.
Now the pass becomes the constraint.
Improve that and collection may become the next one.
The bottleneck moved.
That isn't necessarily failure.
It's what happens in interconnected systems.
One limitation can hide another.
Remove the first and the next becomes visible.
That's why there is rarely one permanent restaurant bottleneck “fix.”
Volume changes.
Menus change.
Teams change.
Technology changes.
Guest behaviour changes.
The operation changes.
And the point where the operation struggles can change with it.
Sometimes Your Strongest Employee Becomes the Queue
Everybody asks Maria.
Maria knows where everything is.
Maria fixes the till.
Maria handles complaints.
Maria approves the void.
Maria knows what happened to Table 14.
Maria knows how everything works.
Excellent employee.
Potentially dangerous dependency.
Because information and decisions are now travelling through one person.
As volume increases, Maria receives more questions.
More decisions.
More interruptions.
Eventually part of the operation can only move as quickly as Maria can respond.
Maria isn't the problem.
The dependency is.
Adding another employee doesn't necessarily increase capacity if that employee also has to ask Maria.
Again, the visible problem and the actual constraint aren't necessarily the same thing.
Sometimes the Queue Is a Person Standing Still
There is another moment worth watching.
Someone stops.
Not because they're lazy.
Not because there is nothing to do.
They simply don't know the next correct action.
So they look around.
They ask.
They wait.
I've called this the Statue Effect.
It demonstrates something important about operational flow.
Not every constraint is physical.
Sometimes information itself becomes the constraint.
Five people may be physically capable of continuing.
But if all five require one answer before they can act, adding a sixth person hasn't solved very much.
That's why one of my core principles remains:
“If your team starts to guess, the money has already left the building.”
The guessing is the clue.
It tells you that under the current conditions, the operation is no longer giving people enough clarity to keep moving confidently.
More Staff Can Still Mean the Same Capacity
Service is struggling.
The instinct is understandable:
We need another person.
Sometimes you absolutely do.
But more labour does not automatically create more usable capacity.
If a station can physically accommodate two people, adding a third may create more crossing, reaching, waiting and communication without increasing output.
Now the spreadsheet says:
More labour.
While the floor says:
Same capacity.
This is where Operations & Flow connects directly with Revenue & Cost.
A labour problem on the financial report may actually have begun as a flow problem on the floor.
The visible expense isn't necessarily where the problem started.
More Data Doesn't Automatically Mean More Understanding
Restaurant operators now have access to extraordinary amounts of data.
Ticket timestamps.
POS transactions.
Labour reports.
Kitchen display data.
Sales intervals.
Stock systems.
Scheduling platforms.
All useful.
But measuring fifty things doesn't guarantee that you'll see the constraint.
You can measure something with extraordinary precision while still measuring the wrong thing.
Technology can tell you what happened.
The harder question is often:
What does it mean?
The tool should follow the question.
Not the other way around.
A Bottleneck Can Become Expensive Somewhere Else
A constraint doesn't only affect the place where it occurs.
Everything depending on that point begins to feel it.
The kitchen waits.
The server waits.
The table waits.
The next seating may wait.
Staff compensate.
Mistakes can increase.
Management jumps in.
Additional labour may be added.
Complimentary items may be used to repair the guest experience.
Eventually the financial consequence can appear somewhere completely different from the original constraint.
Labour.
Waste.
Overtime.
Lost throughput.
Lower margin.
The number appears later.
The operational event happened first.
That's why attacking the visible cost without understanding what produced it can make things worse.
You may be treating the financial consequence while leaving the operational cause untouched.
Stop Asking Who Is Slow
One change in language can completely change what you see.
Instead of:
Who is slow?
Try:
Where is flow slowing?
Instead of immediately asking:
Do we need more staff?
Consider first:
What is currently preventing the capacity we already have from moving?
And when the operation works perfectly well at 5:30 but begins behaving differently at 7:30, don't automatically assume the people changed.
The load changed.
And that matters.
Because peak hour doesn't necessarily create the weakness.
Very often, it reveals it.
The Queue Is Evidence. Not the Diagnosis.
When tickets are stacked across the rail, it's tempting to believe you've found the problem.
You haven't necessarily.
You've found evidence.
Remember the motorway.
The traffic jam you can see from your windscreen may be kilometres away from the lane closure that created it.
A restaurant queue can behave exactly the same way.
You can add another employee.
Buy another screen.
Push the kitchen harder.
Change the schedule.
And still leave the original constraint untouched.
Because the difficult part isn't seeing that the operation is struggling.
The difficult part is finding where the struggle actually began.
That's the difference between reacting to pressure and understanding it.
Good operations don't come from making everybody move faster.
They come from understanding what prevents the operation from moving when the load rises.
When Peak Hour Changes the Operation
If your restaurant works normally until volume rises, the problem isn't simply that you're “busy.”
Something changes under load.
The Peak Hour Stabilizer is designed to help you work on that condition rather than simply react to its symptoms.
But stabilising the operation starts with knowing where the pressure is actually showing up.
That's why the process begins with the Peak Hour Load Scan — When Peak Hour Changes the Operation
If your operation works normally until volume rises, being “busy” may not be the real problem.
Something is changing under load.
The Peak Hour Stabilizer is designed to help you work on that condition rather than simply react to what becomes visible.
But first you need to know where the pressure is actually beginning to affect the operation.
That's why the process uses focused scans for different operational areas — because a problem showing up on the floor may not have the same starting point as one appearing at the bar or kitchen pass.
Pinpoint first. Stabilize second.
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.
