HOSPITALITY INSIGHTS · OPERATIONS & FLOW
This is a 6th Sense Hospitality operational investigation into the people who quietly hold restaurant shifts together. Through a Friday-night service, we explore why decisions gather around one experienced manager, how that arrangement behaves under pressure, and why an apparent bottleneck is not automatically a failure.
Diagnosing Restaurant Staff Dependency: What Is Your Senior Anchor Actually Holding Together?
It's 7:45 PM. Everybody Needs Sarah.
It's Friday evening.
The restaurant is packed. The printer at the kitchen pass is spitting out tickets without a pause. Waiters are moving between tables, drinks are leaving the bar, and the kitchen is pushing out orders.
Table 14 wants to swap mashed potatoes for grilled asparagus.
The server turns around, walks across the dining room and joins three colleagues already waiting to speak to Sarah, the shift manager.
Sarah answers the first question, approves something for the second employee and gives the server an answer about the asparagus.
The queue disappears.
Thirty seconds later, a runner carrying two cocktails approaches Sarah.
"Table 6 says this one tastes strange."
Another server arrives with a question about a bill.
And just like that, a new queue forms.
Sarah answers both questions. Everyone moves on.
From the outside, the restaurant looks busy and well organised.
Sarah certainly knows what she's doing.
But something interesting is happening.
Everybody seems to need Sarah.
Is that a problem?
Not necessarily.
Perhaps Sarah is exceptionally efficient. Perhaps the restaurant deliberately gives her responsibility for certain decisions. Perhaps her experience is exactly what keeps service running smoothly.
Or perhaps something else is happening.
Everybody sees the manager holding the shift together.
But what, exactly, is she holding together?
The Strait of Hormuz in Your Restaurant
Consider the Strait of Hormuz.
It is one of the world's most important shipping passages, connecting the Persian Gulf with the Gulf of Oman and the wider ocean.
A substantial share of the world's oil shipments passes through this relatively narrow stretch of water.
The ships themselves may be enormous. Their engines powerful. Their navigation equipment sophisticated.
But they still depend on a particular passage to reach their destinations.
Now imagine the conditions changing.
Traffic increases. A vessel slows down. Navigation becomes more difficult. A delay affects ships waiting behind it.
The narrow passage hasn't necessarily changed.
The conditions under which it must operate have changed.
And suddenly, the wider network's reliance on that passage becomes much more important.
But here's the question.
Is the passage itself the problem?
Or are we seeing what happens when a large system relies on a limited route under particular conditions?
Now return to Sarah.
At 7:45 PM, four employees are waiting for her.
Is Sarah the bottleneck?
Or is she the reason the restaurant is still functioning?
You cannot answer that question simply by counting the people standing around her.
What Happens at 8:00 PM?
Let's follow three possible versions of the same Friday evening.
Scenario One: Sarah Clears the Traffic
By 8:00 PM, the restaurant is even busier.
The questions keep coming.
Sarah answers them quickly, the servers return to their tables, and food continues leaving the kitchen.
Nobody waits long enough for service to suffer.
The queue around Sarah looks dramatic, but the operation is handling its workload.
Her central role may be working exactly as intended.
Scenario Two: The Queue Begins to Grow
At 8:00 PM, nine employees have approached Sarah within a few minutes.
A table wants to split its bill.
A guest is unhappy with a cocktail.
The kitchen needs clarification on an order.
A waiter is waiting for permission to change a side dish.
Sarah is now dealing with a guest complaint.
The waiter returns to the kitchen without an answer.
The food waits.
Another employee joins the queue.
This time, the same arrangement is producing a different result.
But we still don't know why.
Scenario Three: Sarah Steps Away
At 8:05 PM, Sarah receives an urgent telephone call.
She leaves the dining room for fifteen minutes.
One waiter continues serving without difficulty.
Another knows exactly how to handle a guest complaint.
But two employees wait because they cannot complete particular decisions without Sarah.
One of those decisions might require her authority for a legitimate reason.
The other might be a question that nobody has ever bothered to answer clearly.
Same restaurant. Same team. Same manager.
Different circumstances.
And three very different pictures of operational dependency.
The Headache: What Can You Do Tonight?
Suppose you're the owner watching that second queue form.
You don't have the luxury of stopping Friday service to investigate your entire management structure.
Your immediate concern is straightforward.
Food needs to leave the kitchen. Guests need attention. Employees need answers.
You want the shift to keep moving.
So start with one small question:
Which question keeps returning to Sarah tonight?
Perhaps it's the same side-dish substitution.
Before the next rush, Sarah can clarify the existing rule with the team.
If a substitution is already permitted, make sure the servers know which substitutions are allowed, subject to kitchen availability, allergen requirements and any relevant restrictions.
If Sarah's approval is genuinely required, keep that control in place and make the approval route clear.
The immediate objective is not to redesign the restaurant.
It's to prevent avoidable confusion over one recurring question.
That may reduce interruptions tonight.
It may not.
And even if the queue disappears, you still haven't established why it formed in the first place.
Relieving the headache and understanding its cause are two different jobs.
When Your Best Employee Becomes the Senior Anchor
Sarah may have worked at the restaurant for eight years.
She knows the regular customers.
She remembers which menu items cause confusion.
She knows which chef can handle a special request and which ingredients are running low.
She remembers decisions made three months ago that nobody wrote down.
And whenever something unexpected happens, someone says:
"Ask Sarah."
Over time, Sarah becomes the person everyone relies on.
Not necessarily because she's controlling.
Not necessarily because the employees are incapable.
And not necessarily because the restaurant has a broken management structure.
It may simply be how the operation has developed.
We call this the Senior Anchor.
An experienced person around whom important operational knowledge, decisions or responsibilities have gathered.
A Senior Anchor can be extremely valuable.
The question is not whether Sarah should stop being important.
The question is what happens to the operation when the demands placed on her change.
Four Possible Reasons Everyone Asks Sarah
Consider the same question about replacing mashed potatoes with grilled asparagus.
- Missing Information
The substitution is permitted, but the server doesn't know it.
- Unclear Authority
The server knows the substitution is possible but isn't sure whether they may approve it.
- Established Habit
The server has always asked Sarah, even when the answer was available elsewhere.
- Intentional Control
Sarah is required to approve the substitution because of food cost, preparation requirements or another operational rule.
From across the dining room, all four situations look remarkably similar.
A waiter approaches Sarah.
Sarah answers.
The waiter walks away.
Yet the reasons behind those identical actions are different.
And those differences matter.
Diagnosing Restaurant Staff Dependency Without Blaming the Team
Here's where many restaurant owners get caught.
They see employees constantly asking the manager questions and conclude:
"My staff need to take more initiative."
Perhaps they do.
But perhaps they are following the exact rules the restaurant has established.
Or perhaps the rules have never been made clear.
A manager answering twenty questions during a shift is an observation.
It doesn't establish that twenty unnecessary interruptions occurred.
A waiter waiting three minutes for approval is also an observation.
It doesn't establish whether that approval was unnecessary.
What happened is not automatically an explanation of why it happened.
That is why diagnosing restaurant staff dependency begins with separating what you can see from what you assume.
For your next busy service, try something simple.
Watch one recurring question.
Notice where it starts, who receives it and whether work actually stops while the answer is being obtained.
Don't change everything.
Don't announce that you've discovered a management failure.
Just pay attention to what happens.
You may discover that the queue is harmless.
You may discover that an existing rule is unclear.
Or you may discover that the delay everyone notices is only the final visible part of something happening elsewhere.
That's the point at which the investigation becomes interesting.
What If Sarah Isn't the Problem?
Imagine discovering that Sarah spends much of Friday evening answering questions about menu changes.
You might conclude that she needs to delegate more decisions.
But what if the kitchen changes ingredient availability several times during service without updating the floor?
The servers keep asking Sarah because she is the only person receiving the information.
Removing her approval role would not automatically correct the information gap.
You could give every server more authority and still have the same underlying condition.
The decisions might simply be made faster—with outdated information.
That's why the person standing closest to a delay isn't necessarily responsible for creating it.
And why an operational improvement that appears sensible may be irrelevant to the condition you actually need to address.
Before You Change the System, Find Out What You're Looking At
The queue around Sarah has given you something valuable.
A signal.
You can see that information, decisions or responsibility are repeatedly passing through one person.
But you haven't yet established whether that arrangement is working as intended, where the pressure originates or whether anything needs changing.
And that is where a broader operational diagnostic can become useful.
The €7 Gearbox Audit
The Gearbox Audit is a 10-minute digital diagnostic designed to examine operational friction across four areas:
- Shift Flow
- Guest Standard
- Internal Workflow
- Strategic Drift
It is not a dedicated Senior Anchor Scan.
It examines a broader operational picture, helping you identify which area deserves closer attention.
The queue around Sarah may be your first visible signal.
The underlying condition may sit somewhere else.
The audit is a diagnostic instrument—not a promise to fix the operation or replace your judgement.
You've seen the queue. Now examine the operation behind it.
EXPLORE THE €7 GEARBOX AUDIT →
Frequently Asked Questions
What is restaurant staff dependency?
Restaurant staff dependency occurs when particular activities, decisions or information rely heavily on specific employees. It may be an intentional arrangement or something that has developed over time. The important question is how that dependency affects the operation under the conditions in which it must function.
Is relying on an experienced manager a bad thing?
Not automatically. Experienced managers provide valuable knowledge, judgement and coordination. The concern is not simply that employees rely on them, but whether that reliance causes avoidable interruptions or leaves essential work unable to continue when circumstances change.
How can I reduce staff dependency during a busy shift?
- Start with the recurring questions that are delaying work.
- Clarify existing information and approval rules where it is safe and appropriate to do so.
- Avoid removing necessary controls simply to speed up service.
- A temporary improvement in flow doesn't necessarily resolve the underlying dependency.
How can I tell whether my manager is becoming a bottleneck?
Look beyond how often employees approach the manager. Observe whether work actually waits, how long decisions take and what happens when demand increases or the manager is occupied. A busy manager isn't automatically a bottleneck.
Can restaurant software solve staff dependency?
Software may make information easier to access or decisions easier to communicate. But if the underlying problem is unclear authority, missing information or an unsuitable process, adding technology may not address it. Establish the job the technology needs to perform before deciding whether it belongs in the operation.
What happens if the Senior Anchor is absent?
That depends on what the operation relies on them to provide. Some responsibilities may already be covered by other employees. Others may depend on individual knowledge, access or approval authority. The absence reveals which activities can continue and which require further examination.
The Next Friday Is Coming
Next Friday, Sarah may be standing in exactly the same place.
The restaurant may be just as busy.
Employees may still approach her with questions.
And everything may work perfectly.
Or the queue may begin to grow.
The important difference is that you now know what deserves your attention.
Everybody can see the person holding the shift together. The real question is what they're holding together—and under which conditions.
If your team starts to guess, the money has already left the building.
6th Sense Hospitality · NAVIGATOR Method™ — Powered by Signal Mapping
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.
