How should communication between manager and staff work?

The basic rule: clear, respectful, timely, and specific

Communication between a manager and staff should be clear, respectful, timely, and binding. In my restaurant, that means nobody should have to guess whether I am sharing an idea, making a request, or giving an actual instruction. I try to say what needs to happen, by when, who is responsible, and who makes the final call. Staff must also be able to ask questions, raise problems, and admit mistakes without being embarrassed in front of others. Good communication is not endless talking. It is a reliable working structure that helps everyone do the job well.

I separate four kinds of communication on purpose: a short operational instruction during service, a professional question about a task, an organisational agreement for the next shift, and a personal conversation about performance or behaviour. Many conflicts start because all four get mixed together in the same chat, the same hallway moment, or the same stressed exchange at the pass. If a server needs a fast decision on table coverage, that is one thing. If repeated lateness has to be addressed, that needs privacy, calm, and documentation. That distinction makes communication fairer and much more effective.

During service: brief in the moment, detailed afterward

In the middle of service, communication has to stay short and useful. I expect direct sentences with a clear work purpose: “Table 14 drinks first,” “Hold the mains,” or “Maya covers the terrace tonight.” Long explanations during a rush only create noise. The same applies to criticism. If a mistake is actively harming service, I correct it immediately and factually. If it is not urgent, I leave the teaching part for later. For example, if a receipt detail is missed once, I solve the guest situation first. The learning conversation comes after the pressure drops, not in front of the dining room.

Short communication during service must be balanced by proper follow-up afterward. After a busy shift, ten focused minutes can be enough: what worked, where did we get stuck, and what do we change tomorrow. That is where improvement really happens. Otherwise, manager communication becomes nothing but commands. If I notice that allergy details are still being passed around verbally too often, I do not just ask people to “communicate better.” I change the path of the information. Important organisational notes need a defined, findable process instead of shouts across the room or scattered private messages; in Bonzumo, I mainly keep shifts, roles, and personal documents organised to support that structure.

Good leadership means setting expectations before judging results

Staff can only work reliably if I define expectations clearly before the shift, not complain vaguely afterward. “Please be attentive tonight” is too weak to guide behaviour. “Prioritise quick first drink contact in your section, keep walkways open, and tell me immediately if waiting times build up” is something a team member can actually act on. The same is true for responsibility. Whoever closes the shift must know what must be fully completed, what only needs preparing, and where open questions belong. I therefore connect responsibility to visible, checkable points rather than to general impressions.

A typical example is a new shift leader running an evening for the first time. If I only say, “You are in charge tonight,” I create uncertainty. A fairer approach is to define the frame: who may move tables, who handles complaints up to which point, when I should be called, and which updates must be actively shared with kitchen and bar. Responsibilities should also match the system setup. BonZumo supports roles and permissions, which helps me organise who may see or do what instead of leaving authority as a purely verbal claim. That makes communication more stable because responsibility is not guessed; it is structured.

Questions must be welcome, or mistakes go underground

A quiet team is not always a healthy team. Sometimes it only means people no longer dare to ask. That is risky in hospitality. I want staff to raise a question as soon as an instruction is unclear, contradictory, or impractical in the real flow of service. That is not resistance. It is professional work. The most useful questions are short and solution-oriented: describe the situation, name the missing decision, and offer an option if possible. For instance: “The booking for six has arrived, their planned table is still occupied, I can seat them in area B instead. Is that fine?” That kind of question keeps speed and clarity together.

As the operator, I have to create the atmosphere that makes those questions possible. If someone asks once and I react with irritation, next time I will get silence instead of warning. That is how hidden errors start: missed guest requests, wrong priorities, and time problems nobody flags early enough. When the same questions come back repeatedly, I do not treat them only as individual weaknesses. I check the process itself. If reception often hesitates over table changes, then the real problem may be an unclear table workflow, not a weak employee. A structured setup helps here, especially when reservations and seating need a shared overview like A well-prepared service starts with a clear table plan.

Criticism belongs in private; praise can guide the whole team

Public criticism usually costs more trust than it creates order. My rule is simple: urgent correction can happen briefly in the moment, but real criticism happens later in private. Then I speak about observable behaviour, not character. I do not say, “You are unreliable.” I say, “You were not in your section at the agreed time twice this week, so others had to take over your tables.” That is more precise, more respectful, and easier to improve. Staff should leave a feedback talk knowing exactly what needs to change, not feeling personally diminished.

Praise works the other way around. If someone handles a complaint calmly, rescues a weak handover, or helps a new colleague through a hectic hour, I am happy to name that in front of the team. Not as theatre, but as orientation. It shows what good cooperation looks like here. The trap is false positivity. Praise cannot replace structure, and friendliness cannot replace decisions. If I constantly praise but rarely clarify, I become vague. If I only criticise, people withdraw. Good communication from a manager holds both together: clear limits when something fails and visible appreciation when someone strengthens the service.

Fixed channels prevent chaos from shouts, chats, and half-knowledge

Communication often fails less because of bad intentions and more because too many channels are used for the wrong things. If scheduling questions land in private messenger groups, shift swaps happen verbally, time questions are asked in passing at the bar, and important instructions remain only in the head of one supervisor, conflict is almost guaranteed. I therefore define which channel is used for what. Immediate operational decisions belong in the shift itself. Planned organisational topics need a documented place. Personal matters such as performance, conflict, or absences belong directly with the responsible person, not in a group chat. That protects both speed and confidentiality.

The same principle applies to information we will need again later. Shift plans, roles, time records, and staff documents should not depend on who happens to remember them. I prefer one shared basis that people can actually find and use. BonZumo supports shift planning, time tracking, roles, and a personal document inbox, which gives organisational communication a stable frame instead of leaving it buried in messages. But software alone does not create fairness. My team still needs to know who maintains information, who approves changes, and from which moment a note or plan is considered binding.

How I organise fair communication in everyday restaurant work

In practice, I use a simple rhythm. Before the shift, we do a short briefing on the day’s situation, special bookings, priorities, and responsibilities. During the shift, communication is brief and decision-oriented. After the shift, I clear disruptions, handovers, and learning points. Repeating issues are discussed in a weekly pattern instead of being emotionally re-fought every evening. Individual conversations are reserved for performance, development, or conflict topics that need more calm. This only feels fair if I keep my own promises as well. If I say I will give feedback, I do it. If someone explains a mistake, I listen seriously to the explanation before I judge it.

My own rule of thumb is this: organise publicly, correct personally, improve together. Imagine the kitchen says courses are being released too tightly and production keeps bunching up. I do not just complain about “poor communication.” I check with service and the pass where information is missing. Is the problem handover, unclear leadership, or lack of visibility on order status? Then I change the process, not only the tone. So the best communication between manager and staff is not the most talkative one. It is the one that makes work clearer, decisions faster, and people safer to speak honestly.