Daily Improvement Huddle Guide (frontline)

Purpose

This short guide helps frontline teams run a predictable, 10-minute daily improvement huddle that surfaces yesterday's problems, plans the day, assigns owners, and tracks small experiments. The emphasis is on speed, focus, visible metrics, accountability, and learning so improvements stick rather than fade.

What success looks like

• Huddles start and finish on time (10 minutes).
• One or two concrete experiments or countermeasures are started each week.
• Clear owners and short timeboxes for experiments.
• Visible metrics guide decisions and highlight trends, not noise.
• Escalations are rare and follow agreed thresholds.

Suggested 10-minute agenda (use as a running script)

1. 0:00–0:30 — Quick welcome & purpose

   Facilitator: "Two quick outcomes: make sure the day is set up to win, and confirm one thing we'll try to improve this week."

2. 0:30–3:30 — Yesterday at a glance (data + highlights)

   Review 2–4 metric cards and one short story: wins, customer issues, safety or quality incidents.

3. 3:30–5:30 — Safety / Food quality / Urgent issues

   Raise any safety, allergen, or serious guest-impacting problems. Escalate immediately if thresholds met (see rules below).

4. 5:30–8:00 — Plan the day & assign owners

   Identify today’s key risks (e.g., low stock, short staff, a banquet) and assign owners for mitigation.

5. 8:00–9:00 — Quick round: blockers

   Each area gives one short blocker (kitchen, FOH, bar, receiving). If it needs deeper work, record it as an experiment or escalation.

6. 9:00–10:00 — Commitments & experiments

   Confirm who owns the experiment or action, the measure, and when you'll check back. Close the huddle.

Huddle roles and norms

• Facilitator: keeps time, reads the script, calls for decisions.
• Timekeeper: gently enforces the agenda (can be same person at small sites).
• Scribe / Huddle Owner: records actions, owners, experiment entries, and next-check date.
• Escalation owner: named manager who receives escalations that meet thresholds.
• Norms: start on time, keep updates short (15–30 seconds), speak to facts, focus on corrective experiments not blame.

Metric cards to display (keep to 3–5 visible cards)

Design metric cards so the team can read them at a glance. Use a simple label, today's value, trend (up/down), and a short threshold color (green/amber/red).

• Sales / Covers — yesterday vs. forecast; use to spot unexpected demand or staffing gaps.
• Ticket time / Throughput — average time from order to ready; target & recent trend.
• Orders on-time / Accuracy — percent of orders delivered correctly and on time.
• Waste / Spoilage events — count or pounds; escalate if above threshold.
• Active experiments — number of running experiments and their lead measure.

Example metric-card text

Experiment log template (one-line entries; keep experiments small)

Use a single-row format that the scribe can update after the huddle. Record entries in whatever system you use (whiteboard, spreadsheet, or an interactive form).

1. Experiment name: short descriptive title (e.g., “Portion cue at pass”)
2. Hypothesis: If we do X, then Y will improve by Z%
3. Owner: person responsible
4. Start date / Check-back date: max 7 days for small experiments
5. Measure: the single number you’ll watch (ticket time, waste count, incorrect orders)
6. Result / decision: Pass / Learn / Stop and next steps

Example entry:

Escalation rules (keep them clear and simple)

Escalate to the named escalation owner when any of these occur:

• Safety incident or food-safety risk (immediate escalation).
• Allergen exposure or confirmed customer illness linked to the operation.
• Equipment failure causing >30 minutes downtime for critical line items.
• Inventory stockout of a core menu ingredient expected to impact >25% of orders.
• 3 or more similar guest complaints in a single service period about the same issue.
• Waste incidents above the site’s agreed daily threshold (example: ≥4 events).

When escalating, record: who, what, immediate mitigations taken, and when the escalation owner acknowledged it.

One-page checklist — preparation & follow-through

Before the huddle (facilitator / scribe)

• Confirm metric cards are up-to-date and visible.
• Open experiment log and have last entries ready to review.
• Invite any relevant area owners who must be present (kitchen lead, FOH lead, receiving).
• Prepare one short win and one issue to call out.

During the huddle

• Stick to the agenda and timeboxes.
• Limit discussion — if it needs more time, move to a short follow-up working session and leave a clear owner.
• Record owner, metric, and check-back date for each experiment or action.

After the huddle

• Update the experiment tracker with new entries and owners.
• Communicate any operational changes or urgent risks to staff on shift.
• Follow up on yesterday’s experiments and mark results in the log.
• If escalated, confirm the escalation owner’s next steps and expected timeline.

Tips to keep huddles effective

• Keep the visual displays simple — one value, trend, and status color per card.
• Rotate facilitators occasionally to build leadership capability.
• Celebrate small wins briefly to keep morale and engagement high.
• Limit active experiments to a manageable number (2–5) so follow-through happens.
• Use check-back dates; short timeboxes create learning and momentum.

Quick facilitator prompts

• "What did we learn yesterday that matters for today?"
• "What’s the single greatest risk for this service period, and who owns it?"
• "What will we try this week, how will we measure it, and who will check back?"

Making this a living practice

Start with the one-page checklist and the simplest set of metric cards. After two weeks, review whether the huddle produces useful experiments and adjustments. If not, shorten or refocus the metric set, tighten escalation thresholds, or reduce experiment scope so the team can complete learning cycles faster.

This guide is intended to be practical and adaptable. Teams should tailor metric cards and escalation thresholds to their menu, service model, and risk tolerance.