Daily & Weekly KPI Huddle Template — Agenda, Roles, RAG Rules, and Minute Template

Purpose and quick instructions

This template helps teams run fast, dependable KPI huddles that convert metrics into owned actions every day. Use the daily huddle for quick operational alignment and immediate obstacle removal. Use the weekly deep-dive to investigate persistent issues, align on improvements, and clear escalations.

Core rules to prevent meeting theater

• Timebox strictly (15 min daily, 45 min weekly). Start and end on time.
• Metric owners bring facts and one recommended action or request.
• Every action must have an owner, due date, and clear acceptance criteria.
• Limit attendees: facilitator, scribe, metric owners, and 1–2 escalation owners.
• Keep dashboards concise — only show metrics that can be influenced by the team.

Pre-huddle data pack (what to bring)

Each metric owner prepares a one-row data card for the huddle including:

• Metric name and owner
• Reporting period (e.g., today vs yesterday, week-to-date)
• Current value and target
• Short trend (▲ / ▼ / →) and % change
• Primary cause hypothesis (one sentence)
• Recommended next action (who, what, by when)
• Escalation required? (yes/no and reason)

Roles & responsibilities

• Facilitator: Keeps time, enforces rules, calls escalation when needed.
• Scribe: Records actions in the meeting minute template and updates the board.
• Metric Owners: Present data card, recommend actions, accept ownership for follow-up.
• Escalation Owner / Manager: Accepts escalations and assigns resources or decisions.

15-minute Daily Huddle — Agenda & facilitator cues

1. 00:00–00:30 (30s) Quick welcome & two-sentence purpose. (Facilitator: "Objective — surface exceptions and commit to actions in 15 minutes.")
2. 00:30–03:00 (2.5 min) Safety & immediate stop-the-line items (any LOTO, near-misses, hazards). (All: shout now.)
3. 03:00–10:00 (7 min) Metric run — metric owners present data cards (max 60–90s each): current, trend, hypothesis, recommended action. (Facilitator: enforce the 90s rule.)
4. 10:00–13:00 (3 min) Rapid actions: confirm owners and due dates for items raised. If an item needs more investigation, tag for weekly deep-dive or create a short A3.
5. 13:00–14:30 (1.5 min) Escalations: any item meeting escalation criteria goes to the escalation owner. (Facilitator: read escalation matrix.)
6. 14:30–15:00 (30s) Quick close: confirm actions, owners, and time of next huddle. (Scribe: repeat actions aloud.)

45-minute Weekly Deep-Dive — Agenda

1. 00:00–03:00 Opening: review purpose and top 3 metrics that need discussion.
2. 03:00–15:00 Deep review of metric #1: facts, timeline, root-cause hypotheses, and data gaps.
3. 15:00–27:00 Deep review of metric #2 (same pattern).
4. 27:00–35:00 Improvement & containment planning: decide short-term containment and long-term countermeasures (A3 or PDCA owners assigned).
5. 35:00–42:00 Resource & escalation decisions: agree on requests to managers, cross-functional support, or external approvals.
6. 42:00–45:00 Review action tracker, confirm owners, and schedule follow-up checkpoints.

Red / Amber / Green (RAG) rules — example thresholds & actions

Define RAG per metric using objective thresholds tied to targets and tolerance. Example:

• Green: Within ±3% of target. No action required beyond monitoring.
• Amber: Between 3% and 10% off target — quick containment needed and action owner assigned for 24–72 hours.
• Red: >10% off target or safety/quality stop — immediate containment, root-cause analysis, and escalation to weekly huddle or management.

Escalation triggers (examples): persistent red for 2 consecutive daily huddles; amber without progress after 3 days; any red tied to customer impact or safety incident.

Meeting minutes template (copy into your board)

Leading vs. Lagging indicators — what to track

Choose a balance of leading (predictive) and lagging (outcome) metrics so the team can act before outcomes deteriorate.

• Lagging examples: customer on-time delivery, PPM defect rate, lost-time injuries, throughput, cycle time.
• Leading examples: % of preventative maintenance completed on schedule, number of open production defects older than 24 hours, changeover readiness checklist completion, first-pass yield checks, operator training hours, safety observations closed within 48 hours.

Rule of thumb: each lagging metric should have at least one leading metric the team can influence within 24–72 hours.

Example KPI set for an operations team

• Safety: near-miss reports closed within 48h (leading) / LTIFR (lagging)
• Quality: defect escapes to customer (lagging) / 1st-pass yield (leading)
• Delivery: on-time delivery % (lagging) / orders released on schedule (leading)
• Reliability: equipment availability % (lagging) / planned maintenance compliance (leading)

Quick facilitator script snippets

Opening: "Today we’ll surface exceptions and commit to actions in 15 minutes. Metric owners: present one fact, one hypothesis, one recommended action."

If someone drifts into status: "Thanks — we’ll capture that as a follow-up. For now, give one sentence and an action."

Closing: "Scribe, read back the actions and owners. If you’re escalated, expect a decision in the next 24 hours."

Preventing common problems

• Avoid long presentations — use the one-row data card per metric.
• Don’t review historical charts without a clear decision to make.
• Limit the action backlog — older unresolved items must be escalated or closed.
• Use visuals (whiteboard or digital board) with clear RAG indicators and action owners.

Suggested ways to use this template

1. Copy the meeting minute table into your shared board and make it the single source of truth for actions.
2. Create a simple daily form (one-line per metric) for metric owners to submit the pre-huddle data card before the huddle starts.
3. Use the weekly deep-dive agenda to convert repeated reds into A3s or PDCA cycles with owners and due dates.

Tip: Start small. Run the daily huddle for two weeks, then adopt the weekly deep-dive for the top 2–3 persistent issues.