Operating problem
How the work is structured
Existing routines are observed first and checked for unnecessary friction. Standards are then organised around operating moments: shift start, mise en place, greeting, order taking, handover, complaint, payment and closing. Each SOP stays short enough to be used. Checklists do not replace leadership, but they create visible control points.
Operational detail
A standard must be precise enough to remove ambiguity and short enough to be used in daily operations. The aim is not to document every detail, but the moments where quality is most often lost: shift start, handover, special guest requests, complaints, payment and closing.
We first observe what already works well and retain routines that make sense. Only then are checkpoints, ownership and concise working instructions added and tested during a real shift.
Documents are organised around operating moments and roles. The purpose is not to create more administration, but to give the team a clear reference for situations where quality would otherwise vary from one shift to the next.
Decisions in daily operations
Handovers receive particular attention. Quality often drops not because employees do not understand good service, but because important information disappears between shifts, stations or departments. Standards therefore capture only what the next role genuinely needs: open guest issues, reservation details, sold-out items, technical constraints or prioritised tasks. Supervisors receive a small set of observable quality markers. This allows feedback immediately after a situation rather than an abstract discussion about “service quality” weeks later. Standards remain a management tool rather than becoming documentation for its own sake.