Performance tracking
A daily huddle that unblocks work—not another status meeting
Bring overdue work, missing information and decisions into one short conversation with clear owners.
Everyone is busy, yet the same blocked jobs return to the conversation every morning and nobody knows who can move them forward.
Review exceptions, assign the next action and follow it through. Keep detailed problem-solving outside the huddle.
Make the meeting about today's obstacles
A useful huddle answers a narrow question: what could prevent the team from delivering today's work? Reading every completed task aloud answers a different question and leaves little time for decisions.
In an account published by Lean Enterprise Institute, Cleveland Clinic's improvement team describes moving toward smaller daily huddles where attendees share problems. This is one healthcare organization's experience, not proof of a universal benefit or a benchmark for your business. [1]
Our recommendation is to start with one team and a short fixed timebox. Review what is overdue, what is blocked and what needs a decision. Take an item offline when understanding it requires a longer conversation.
Give each exception a next action
Create a shared list with a work reference, blocker, owner, next action and review time. ‘Waiting for approval’ is a state, not an action. ‘Coordinator asks the approver to confirm scope today’ tells the team what happens next.
Distinguish the person responsible for following up from the person with decision authority. Escalate when the owner cannot resolve the problem within the agreed boundary; do not automatically copy every manager into every issue.
Keep customer, employee and patient details out of a publicly visible board. A reference number and neutral blocker category are often enough for the discussion. Access to the underlying record should remain in approved systems.
Close the loop instead of clearing the board
At the next huddle, check whether the promised action happened and whether the work actually moved. Do not close an exception just because somebody sent an email. Record the outcome or the next step.
Repeated blockers belong in a separate improvement discussion. If missing completion evidence causes delays every day, improve the handoff rather than making the huddle a permanent chasing service.
Keep one visible list rather than a board, a private spreadsheet and an email summary with conflicting statuses. Your existing shared tool can be sufficient for the first trial.
The smallest useful exception list
| Field | What to record |
|---|---|
| Work reference | An identifier, not confidential case details |
| Blocker | The missing information or decision |
| Owner | One person accountable for the follow-up |
| Next action | A concrete action and expected review time |
| Resolution | What changed, or why the item remains blocked |
Suggested local working format; this is not a customer result or a prescribed service level.
Try it in your operation
- Observe your current meeting and count items discussed without a next action.
- Use one exception list for a working week with a fixed timebox.
- Review each open action at the next meeting; move deep investigations outside it.
- Ask the team whether the huddle helped decisions or simply added another reporting task.
How to tell whether it helped
Track the age of blocked items, the share with an owner and next action, and meeting time. Compare like-for-like workload. A shorter meeting alone is not success if unresolved work grows or people stop raising problems.
Sources & review notes
- [1]How We Improved Our Tiered Daily Huddles
Lean Enterprise Institute · November 8, 2019
The huddle design is Be On It's practical recommendation. The cited account is external experience; no improvement percentage or guaranteed outcome is implied.