The Demand

Before your next shift, watch one server for one table and count the invisible calls they make — the read within sixty seconds, the arc they build, the tone they recalibrate, the silence they manage, the recovery they absorb. Name at least three of those calls out loud to that server after the shift, specifically, so they know you saw the creation and not just the delivery. Decide whether your hiring, training, and recognition currently treat servers as conduits or as creators — and pick one to change this week.

The Work

Name the server and table you watched:

The invisible calls you counted:

The read within the first sixty seconds — what table type did they identify:

The arc they built — where did they pace, push, disappear, or recover:

The tone they calibrated and recalibrated across the meal:

The recovery they absorbed, if any — what went wrong upstream and how did the table not feel it:

Conduit or Creator — diagnose your operation:

Does your hiring conversation currently test for menu memorization or for reading rooms and making calls under pressure:

Does your training manual teach the inputs only, or does it apprentice new servers under ones who already create:

Does losing a strong server get treated as a scheduling problem or as losing a specific creator with specific reads:

The one change — hiring, training, or recognition — you will make this week to treat the server as a GX Creator, not a conduit: