Weekly Operations Huddle — Data Pack, Agenda & Decision Template

Purpose

Use this template to run a short, decision-focused weekly operations huddle that turns data into prioritized actions and experiments. The goal is sustained improvement: identify the highest-impact issues, assign owners, resourcing, measurement, and a review date so improvements do not drift.

Outcomes

• Shared situational awareness on safety, service, quality, and margin.
• Clear, prioritized actions and experiments with owners, due dates, and success metrics.
• A short list of follow-up items for the week and decisions that unblock work.

Who & Cadence

Weekly, 45–60 minutes. Invite the operations leader (chair), a shift lead or FOH manager, kitchen lead/chef, finance or controller (or their data designee), and a continuous improvement or quality representative when available. Keep the group small — 5–8 people works best.

Prework (what attendees should prepare before the meeting)

• Distribute the Data Pack 24–48 hours before the meeting.
• Each functional owner highlights the top 1–2 variances or incidents they want discussed (submit as a one-slide summary—see slide template).
• Bring any relevant recent guest feedback or inspection notes.

Minimal Data Pack (what to include every week)

Keep the pack small and consistent so trends are visible. Prefer one chart per slide with a short caption and one-line interpretation.

• Sales: rolling 4-week sales by daypart (+ vs plan/forecast %).
• Labor: labor % vs target and vs last week; hours by role; overtime events.
• Food Cost: weekly food cost % vs target and major drivers (top 5 ingredients by variance).
• Waste & Spoilage: waste kg/$ by cause category and top contributors.
• Incidents & Safety: number and severity of incidents (near misses, complaints, food safety events) and status of open investigations.
• Service & Guest Experience: ticket times, order accuracy rate, Net Promoter Score or key review trends.
• Inventory Variance: any unexplained shrinkage or supplier delivery issues.
• Open Experiments & Actions: status summary of committed experiments from prior weeks.

Focused Agenda (45–60 minutes)

1. 0–5 min — Quick Check-in & Safety

   Chair opens with one safety moment and confirms attendance and objectives.

2. 5–15 min — One-Page Snapshot

   Present the 1-page dashboard (top 5 metrics). Chair reads the headline: What's the single thing we need to fix this week?

3. 15–40 min — Prioritized Deep Dives (10 min per item)

   Choose up to 2–3 issues (safety incidents, quality deviations, margin shocks, or persistent customer pain). For each:

   • Owner presents a one-slide problem brief (see template).
   • Quick root-cause summary (use the 5 Whys or short fishbone).
   • Decide on one immediate action or experiment, owner, resources, measurement, and due date.
4. 40–50 min — Open Experiments & Learnings

   Review progress on experiments: what improved, what didn't, and next steps.

5. 50–60 min — Actions, Owners & Review Plan

   Confirm actions in the Action Log, set the date for review, and identify any blockers requiring escalation.

One-Slide Problem Brief (use this for each deep-dive)

Keep to a single slide with these sections (headline only — one short sentence):

• Headline: e.g., "Lunch ticket times up 22% vs target last 3 weeks — causing lost covers."
• What changed / evidence: key data points (2–3 bullets or small chart).
• Immediate impact: guest experience, cost, safety, or compliance.
• Initial root-cause hypothesis: 1–2 lines (e.g., prep mismatch; POS routing change).
• Proposed action/experiment: short A/B or countermeasure with owner, resources, and time-box.
• Success metric: how we'll know it worked (ticket time down X or fewer complaints).

Sample Quick Root-Cause Slide (template text)

Action & Experiment Log (meeting output format)

Use this table each meeting (capture as a simple list if you don't use a formal tool):

• Action/Experiment: short description
• Owner: name
• Start Date / Due Date:
• Resources Needed: who/what
• Success Metric / Target: how measured
• Review Date: which weekly huddle will review
• Status: Not started / In progress / Complete / Blocked

Suggested KPIs & Visuals (one chart per slide)

• Sales by daypart: 4-week rolling line chart with % vs forecast annotation.
• Labor % vs sales: stacked bar showing role mix.
• Food cost %: weekly trend and table of top 5 variance contributors.
• Waste by cause: Pareto chart.
• Ticket time distribution: box plot or percentile chart for peak windows.
• Open actions: simple list with color-coded status.

Meeting Roles & Facilitation Tips

• Chair: runs the meeting, enforces timeboxes, surfaces decisions.
• Data owner: ensures the data pack is prepared and slides are formatted consistently.
• Action manager: maintains the Action Log and follows up mid-week where needed.
• Keep discussions short: accept an action/experiment when consensus exists; escalate unresolved trade-offs to the operations leader after recording options.

Common Pitfalls & How to Avoid Them

• Data-heavy meeting: limit slides to the minimal pack and require a one-line interpretation for every chart.
• No ownership: always attach an owner and a review date to every action.
• Too many actions: limit to 3 active experiments at a time to keep focus.
• No measurement: define a success metric before starting an experiment.

Using This Template with Platform Capabilities

This template works as static guidance, but becomes more powerful if paired with platform features:

• Turn the Action & Experiment Log into a tracked Interactive form so owners can update status between meetings (see capability suggestions below).
• Create a standard Data Pack slide collection in the domain so each location produces consistent charts automatically.
• Use saved meeting artifacts (slides + action log) as the organization's memory so successful experiments can be copied between locations.

Quick Starter Checklist (before you run the first improved huddle)

1. Create the 1-page snapshot dashboard and a 6-slide data pack template.
2. Assign data owner; schedule automatic data exports or manual pull 24–48 hours before the meeting.
3. Decide where the Action Log will live (spreadsheet, domain action tracker, or Interactive form).
4. Run the first huddle with only one deep-dive to practice the format and timing.

Templates Attached (copyable)

• One-page snapshot layout (headline + 5 KPI tiles).
• One-slide problem brief (structure shown above).
• Action & Experiment log (fields listed above).

Image search phrase: weekly operations meeting