Throughput: Reporting, Goal Setting & Ops Opportunities
Goal: Create a clear, shared way to measure and improve “throughput” (how efficiently we move guests through the restaurant without sacrificing quality), so we can serve more guests when demand is high, reduce excessive waits, and improve consistency. To do that, the team agreed the first step is alignment on the right metrics + reporting, so Operations can then coach, train, and performance-manage against those metrics. There’s also a second, related initiative: retail wine sales in the Tasting Room. Specifically creating a practical “activity-based” metric (similar to Wine Club invite rate) so it’s not just “sell more retail wine,” but something measurable and coachable.
1.26.26 (Bryan): Today we kicked off our Throughput workstream under “Traffic with Purpose” and aligned that the first step is to agree on a small set of core throughput metrics and build reporting the field can actually use. We discussed candidate measures (guest experience time, kitchen ticket times, table turns) and surfaced key data challenges—especially defining true capacity day-to-day given OpenTable configuration changes and inconsistent status/timestamp signals. Next, we’ll map the end-to-end guest journey, identify which steps are controllable and supported by reliable data.
1.26.26 (Bryan): Today we kicked off our Throughput workstream under “Traffic with Purpose” and aligned that the first step is to agree on a small set of core throughput metrics and build reporting the field can actually use. We discussed candidate measures (guest experience time, kitchen ticket times, table turns) and surfaced key data challenges—especially defining true capacity day-to-day given OpenTable configuration changes and inconsistent status/timestamp signals. Next, we’ll map the end-to-end guest journey, identify which steps are controllable and supported by reliable data.
Prism · Cooper’s Hawk Strategy · Mid-Year Review FY26