Template

Weekly Operations Huddle — Agenda, RCA Worksheet & Experiment Tracker

Structured, saveable huddle template that turns weekly KPIs into short RCAs, owned experiments, resource requests, and clear escalations so improvements stick.

Interactive Tool

Weekly Operations Huddle — Agenda, RCA Worksheet & Experiment Tracker

Purpose

This short, practical huddle helps teams turn weekly performance signals into clear experiments, ownership, and follow-up so improvements survive the day-to-day. Use this template to capture evidence, agree hypotheses, design small tests, assign owners, and record resources or escalations.

When & Who

Run weekly. Timebox 30–45 minutes. Suggested roles: facilitator (keeps the huddle on track), scribe (enters this form), data owner (brings KPIs), and experiment owners (follow up on actions).

How to use the RCA approach here

Focus on evidence first, form a concise hypothesis about the root cause, propose a small countermeasure (an experiment), and define simple metrics to test whether the countermeasure worked. Prefer quick, reversible tests over large changes. Avoid blame — document facts and ask why the process allowed the issue to occur.

Enter the week start date (ISO format).
Which store, kitchen, or team is this for.
Percent actual sales vs plan (enter number only).
Labor cost as percentage of sales.
Food cost as percentage of sales.
Record waste quantity or cost for the week (e.g., 12 kg or $120).
List up to three incidents to discuss (title and one-line summary).
Short title describing the incident.
Brief factual summary. Avoid blame; stick to observations.
Receipts, timestamps, CCTV, POS anomalies, counts, or witness notes that support the summary.
A concise statement linking evidence to a suspected root cause.
After discussion, record the agreed root cause; be specific about process, training, tools, or supplies.
Describe a small, time-boxed test to address the root cause (who will do what, when).
How will you measure success? Use simple, observable metrics.
Who is accountable for running the experiment and reporting back.
When the owner will report results.
Tick yes if this needs regional or corporate attention.
If escalation is needed, what should be included (risk, impact, suggested support).
List any experiments not tied to the incidents above.
Describe the test, sample size, timing, and controls if applicable.
List equipment, supplies, training, or support needed to run experiments or prevent recurrence.
Summarize items that need higher-level attention and suggested urgency.
Capture improvements, bright spots, or team achievements to reinforce behavior.
Concise action list with owner and due date—used to populate next week's agenda.
Anything the facilitator wants to record about the conversation, team dynamics, or barriers to implementation.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.