Weekly KPI Huddle Agenda (template & facilitator notes)

Purpose

Run a timeboxed weekly operations huddle that turns data into prioritized learning: confirm what the numbers say, identify one or two opportunity areas, break down the problem to a clear next experiment, assign owners and commitments, and record follow-up. Designed for a 30–45 minute cadence.

Time & Rhythm

Recommended length: 30–45 minutes. Ideal weekly slot: same day/time each week (e.g., Monday 9:00). Keep to the schedule—short, focused, repeatable.

Roles

• Facilitator (huddle lead): Keep time, steer the flow, surface decisions, and ensure owners are assigned.
• Data Owner: Prepares and presents the brief KPI snapshot (POS, inventory, labor).
• Shift/Area Owners: Attend to context, accept assignments, and report experiment progress next week.
• Scribe: Records experiments, owners, due dates, and publishes quick notes after the huddle.

Pre-meeting checklist (what must be ready before the huddle)

• Data Owner posts KPI snapshot (2–4 slides or a one-page dashboard) 1 hour before the meeting.
• Owners bring quick context for any KPI outliers flagged in the snapshot.
• Scribe prepares the experiment log and access to last week’s commitments.
• Facilitator confirms agenda and timeboxes.

Agenda (30–45 minutes)

1. Quick check-in & outcome focus (2–3 min) — Remind the group of the huddle's purpose and the target outcomes for today.
2. Data snapshot (8–12 min) — Data Owner shows 3–6 KPIs (trend + variance vs target). Stick to facts; use visuals and one-sentence headlines per KPI.
3. Escalations & urgent issues (3–5 min) — Rapidly surface any items that meet escalation thresholds (see rules below). Decide immediately if an escalation action is needed or if it will be owned as an experiment.
4. Problem breakdown (8–10 min) — Pick 1–2 highest-impact items. Rapidly clarify: what changed, who is affected, and one likely root cause. Use a timeboxed 5-whys or quick A3-lite approach—stop when you have a testable hypothesis.
5. Experiment review & new experiments (8–10 min) — Review status of ongoing experiments (quick updates: one-sentence result + learnings). For new problems, define a short experiment: hypothesis, metric to watch, owner, timeframe, and expected effect.
6. Owners, commitments & close (3–5 min) — Confirm owners, concrete next steps, deadlines, and who will update the dashboard. Scribe repeats assignments aloud. Record in the experiment log and assign follow-up publication.

Recommended KPIs by role (select 3–6 per huddle depending on focus)

General Manager / Owner

• Weekly sales vs plan
• Gross margin (food & beverage)
• Labor % of sales
• Net promoter score / guest satisfaction trend

Kitchen / Chef

• Food cost % (rolling week)
• Recipe/portion variance rate
• Ticket time during peak
• Remake / waste count by reason

Front of House / Service

• Order accuracy %
• Average table turnaround time
• Guest wait time (seated or order-to-serve)

Operations / Inventory

• Inventory variance %
• Receiving exceptions
• Spoilage rate

Escalation rules (quick decision guide)

Use these to decide whether an item is handled as a huddle experiment or escalated to a rapid-response team:

• Severity A — Escalate immediately: Food safety risk, regulatory failure, active guest safety/staff harm, major equipment failure causing service stoppage.
• Severity B — Fast track outside huddle: Sales drop >15% week-over-week with no clear cause, major supply disruption for a core item.
• Severity C — Huddle experiment: KPI variance within operational range but persistent (e.g., food cost up 1–3%, remakes up 5%) — handle as an experiment with owner and timebound test.

Experiment Log (template)

Facilitator notes — keep it focused

• Begin by reading the top 2–3 KPI headlines aloud; facts first, interpretation second.
• Timebox tightly. If a problem needs more investigation, assign an experiment and park deeper analysis for an ad-hoc working session.
• Ask: "What would count as success for this week?" Turn vague desires into measurable outcomes.
• Limit active experiments to 3–5 items across the team to avoid diffusion of effort.
• Encourage concise updates: one-sentence result + one learning. If the learning is uncertain, state the evidence you need.
• Use the parking lot for ideas that are important but not immediate—capture them and assign someone to triage.

Suggested Norms & 'Working Agreements'

• Data-first discussions: bring the numbers, not anecdotes.
• Decisions are owner-driven and timebound; owners report back next huddle.
• Be candid about uncertainty—experiments are explicit bets, not blame.
• Keep the tone: curious, analytic, supportive.

Follow-up & publishing

1. Scribe publishes a 3-line summary to the team channel within 1 hour: KPI headlines, experiments added/closed, owners and due dates.
2. Owners update experiment status as data arrives (use the experiment log). Close experiments with a one-sentence learning and the next decision.
3. Track recurring issues — if an experiment fails repeatedly, escalate for deeper problem-solving or process redesign.

Coaching tips for improving cadence over time

• Start strict with timeboxes for the first 6–8 meetings; loosen only when the team reliably hits outcomes.
• Rotate the facilitator quarterly to build capability and perspective.
• Celebrate quick wins publicly—small changes compound.
• After 90 days, audit the huddle’s impact: how many experiments led to measurable improvement? Use this to adjust KPIs and focus.

Quick templates (one-sentence prompts)

• Data headline: "This week sales are X vs plan; the change is driven by Y."
• Problem statement: "Ticket times in dinner service increased by X% because Y."
• Experiment hypothesis: "If we do X for Y days, we expect metric Z to change by N%."

How this can map to THE capabilities

Capture experiments in a shared interactive experiment log (use the platform's form + submission capability) so entries are stored, searchable, and visible across locations. Connect the KPI snapshot to a dashboard so the Data Owner can publish the one-page view before the huddle. Consider packaging this agenda and the experiment log as a small toolkit within your domain so locations can copy, adapt, and run consistent huddles.

One-page facilitator checklist (for use before and during the huddle)

1. Confirm KPI snapshot uploaded (Data Owner)
2. Open last-week experiment log (Scribe)
3. Start on time; read headlines
4. Pick 1–2 priority items for experiments
5. Assign owners, timeboxes, and publish notes