The owner was standing at the pass, answering a supplier call, approving a refund, fixing a roster and carrying two plates at once.
From the dining room it looked heroic. From the numbers it was expensive.
Every time the owner rescued a task, the team learnt the same lesson: wait. Do not decide. Do not own it. Ask the person who is already doing six jobs.
That is not a lazy team. It is a venue trained to escalate everything upward.
The difference between being useful and being required
Owners often tell me, “I just care more.” Usually that is true. It is also irrelevant to the operating problem.
A venue needs an owner’s judgement on the things that change its direction: pricing, a senior hire, a supplier decision, a lease problem, a major customer complaint. It does not need the owner to approve every minor refund, place every order or solve every close.
When the owner is required for routine work, the business has no operating rhythm. It has one very tired person standing between the team and a decision.
Start with the interruptions, not a giant org chart
For one week, write down every question that lands with the owner. Do not judge it yet. Just capture it.
Then put each interruption in one of four buckets:
Keep: owner judgement genuinely required.
Delegate: someone has the authority but has not been told they can use it.
Document: the answer is the same every time and should live in a one-page procedure.
Remove: the task exists because of an old habit, a bad report or an unnecessary approval.
The surprise is rarely the volume. It is the repetition. The same questions return because the answer was said, not made usable.
Give people boundaries, not vague responsibility
“Take ownership” is not an instruction. It is a nice sentence that leaves a manager exposed.
Try this instead: the duty manager may resolve a guest issue up to an agreed value, alter a roster within an agreed hours cap, and approve a supplier substitute from an agreed list. Anything outside those boundaries is escalated with the facts, not the panic.
That is how a team becomes capable without making reckless decisions.
The weekly owner test
Pick one shift each week that the owner does not work. Before it begins, the manager knows the sales target, staffing plan, booking notes, product availability and escalation boundaries.
Afterwards, ask three questions:
What required owner input that should not have?
What decision was made well without the owner?
Which answer needs to become a checklist or a boundary?
Do not use the first imperfect shift as proof the owner must stay. Use it as a list of the operating system you still need to build.
Turn interruptions into operating rules
| Interruption | Decision owner | System to create |
|---|---|---|
| Minor guest recovery | Duty manager within an agreed boundary | Clear recovery limit and log |
| Supplier substitute | Kitchen lead against approved specification | Approved-substitute list |
| Roster change | Manager within an agreed hours cap | Escalation and coverage rule |
| Repeat question | Named role | One-page decision rule |
Illustrative operating checklist. Replace with verified venue inputs.
Further reading
Official guidance for accommodation and food-service businesses
The real outcome
The point is not to make the owner invisible. It is to stop the venue from becoming fragile every time the owner is sick, travelling or simply has to think.
If you leave a shift and the room stays consistent, that is not losing control. That is finally having it.
Find the first repeatable decision
Do not start by rewriting every role description. Start with the questions that arrive more than once in the same week: a supplier substitute, a guest recovery, a call-in sick, a broken menu item or a last-minute table move. Those are usually the places where a person is waiting for permission rather than missing capability.
For each repeat, write a one-sentence decision rule. It should say what the duty manager may do, what information they need to check and the point at which they call the owner. A rule such as “use an approved substitute if it meets the spec and does not change advertised allergen information” is far more useful than “use your judgement”.
The aim is not to remove judgement. It is to stop judgement being required for the same ordinary issue every day. When a manager can see the boundary, they can act calmly in front of the team and guest. When they cannot, every small problem becomes an interruption.
Give managers the information that makes authority usable
Authority without information creates a different problem. A manager cannot make a sensible decision on a refund, roster change or substitute if the service standards, hours target, product list or guest history live only in the owner’s head.
Before service, the manager should be able to find the day’s bookings, product constraints, labour plan, important notes and escalation contacts in one place. It can be a short service board, not a complicated dashboard. The test is simple: could someone covering the shift use it without a long phone call?
Then make the follow-up equally simple. Ask the manager to record what happened, the decision made and anything that needs a new rule. This is how a venue gradually turns individual rescues into a reliable operating system.
A 30-day start that does not overwhelm the team
Week one is observation. Capture the interruptions, but do not try to solve all of them. Week two is boundaries: choose the two most repeated decisions and write the approved response. Week three is practice: run the manager through those decisions before service, then let them use the boundary. Week four is review: look at what still went to the owner and ask whether it needed to.
Keep the change visible. A small operations board with “decision, boundary, owner, review date” is enough. It turns delegation into a practical part of the shift rather than a promise made in a meeting.
Expect a few awkward decisions while the system is new. The owner’s job is not to immediately take back control. It is to help the manager review the facts, adjust the boundary if needed and make the next decision easier. This is how confidence becomes operational, not motivational.
If your venue feels like it needs you for every small decision, start with a bounded operations audit. The job is to find the repeating interruptions and decide what should be delegated, documented or removed.
