Weekly KPI Huddle Agenda & Facilitation Script

Purpose and How to Use This Template

This agenda and facilitation script help teams run a lightweight weekly KPI huddle that keeps metrics tied to owners, decisions, experiments, and follow-ups instead of becoming metric theater. Use the 45-minute format as a repeatable cadence: review data, surface important changes, make accountable decisions, launch or update experiments, and capture clear next steps.

When to run

• Weekly, same day and time to build rhythm.
• Keep attendance limited to metric owners, relevant contributors, and one facilitator/coach.

Roles

• Facilitator: Keeps time, enforces structure, reads the script prompts, and records huddle outputs.
• Metric Owner: Responsible for the metric, brings context, proposes actions/experiments.
• Coach/Leader (optional): Helps escalate cross-team decisions or resource needs and supports follow-through.

45‑Minute Agenda (fixed structure)

1. Data Check — 10 min

   Quick pass through each metric's current value, trend, and data quality. Aim for crisp signals — avoid long storytelling here.

2. Highlight & Explain — 10 min

   Owners call out one thing that matters (positive or negative). They explain likely causes briefly and surface any evidence or anomalies.

3. Decisions & Actions — 15 min

   Decide one concrete action per important metric change, assign an owner, and set an expected outcome and a review date.

4. Experiment Updates — 5 min

   Quick status on active experiments. Note learnings and whether to continue, stop, or scale.

5. Wrap & Escalations — 5 min

   Confirm owners, deadlines, and any escalations to leadership or other teams.

Facilitation Script (copyable prompts)

Use these short prompts to keep the huddle focused and efficient.

• Opening (30s): "Welcome. Quick round: data check, highlights, decisions, experiments, wrap. We'll keep a tight clock — I'll call time when needed."
• Data Check prompt (per metric, 60–90s): "Metric name — current value and trend. Any data-quality concerns?"
• Highlight & Explain prompt: "Owner, what single thing about this metric should the team notice this week? Briefly: what changed and why do you think that happened?"
• Decision prompt: "What do we decide to do now (action/experiment), who owns it, and when will we check back?"
• Experiment update prompt: "Active experiments — one-sentence result/learning. Continue, stop, or scale?"
• Wrap prompt: "Confirm owners, deadlines, and any leader escalations. Anything critical left unsaid?"

Signal vs. Icicle Detection Heuristics

Help the team distinguish noise from meaningful signals. Use these heuristics during the Highlight & Explain stage.

• Signal (worth action):
  • Consistent trend across multiple days/weeks or correlated metrics.
  • Change matches a recent known cause (process change, supplier issue, campaign start).
  • Has measurable customer or safety impact, or affects committed targets.
• Icicle (likely noise or data issue):
  • Single-day blips without correlation elsewhere.
  • Known data collection or integration issue.
  • Outlier explained by one-off event with no expected continuing effect.

Facilitator action: if a highlight looks like an icicle, ask for simple confirmation or a quick data-check task rather than launching a full experiment.

One‑Page Output Template (record during the huddle)

Copy this exact structure into your meeting notes or into an interactive form later. Make one line per decision/experiment.

Coach / Escalation Notes (short)

• If cross-team resources are required or the action removes a blocker for another team, note escalation and prepare a one-paragraph request for leadership with impact and options.
• Use coaching questions when owners avoid decision-making: "What's the smallest safe step we can take this week to test your hypothesis?"
• Track repeated missed commitments. If an owner misses commitments twice, schedule a short coaching check-in outside the huddle to diagnose root cause.

Pre-Huddle Checklist (owners & facilitator)

• Owners validate data quality and have one highlighted insight prepared.
• Facilitator sets timer, shares the output template, and confirms attendee list.

Post-Huddle Follow-up

• Publish the one-page output within 24 hours and tag owners, actions, and check dates.
• Facilitator checks that actions are visible in owners' to-do lists or team backlog.
• At the next huddle, reopen only the items whose check dates are due or any items flagged as escalations.

Tips & Common Pitfalls

• Keep the meeting to 45 minutes—length creep kills repeatability.
• Resist narrative drift: numbers should prompt decisions, not long status reports.
• Limit experiments to a small number; too many dilute learning and accountability.

Next Steps: Making this Interactive

This HTML template is designed to be immediately useful as a facilitator script and meeting note. Consider converting the One‑Page Output Template into an Interactive form so each huddle submission is saved as structured data for history, dashboards, and follow-up automation.