A 15-minute Kaizen meeting is a short team huddle for improving one recurring problem in how work gets done. Bring one recent example. Leave with one small test, an owner, a measure, and a review date. Start the next meeting by checking what happened.
Use this agenda once you have a specific problem to discuss. If the team needs help finding one, start with these Kaizen activities for teams.
The 15-minute Kaizen meeting agenda
| Minutes | What to do | Question to ask |
|---|---|---|
| 0–3 | Review the last test. Decide whether to keep, adapt, or stop it. | What happened compared with what we expected? |
| 3–6 | Describe one recurring problem using a recent example. | Where did the work wait, repeat, or come back incomplete? |
| 6–11 | Choose one small change the team can test safely. | What can we try on a few cases before the next meeting? |
| 11–15 | Record the owner, scope, measure, and review date. | Who will do what, and how will we tell whether it helped? |
At the first meeting, use the opening three minutes to agree on the purpose and check the example. Ask people to bring details beforehand. A timer helps the facilitator leave enough room to decide who will do the work.
Worked example: approvals keep coming back incomplete
A five-person operations team notices that approval requests often arrive without the decision date or a link to the document. In the last ten requests, four needed a follow-up. The team agrees to test a three-line request format: decision needed, decision date, document link. Priya will put it in the team’s shared channel and use it for the next ten routine requests. Urgent escalations continue through the existing route.
At the next huddle, one of ten requests needed a follow-up. The team checks whether those ten requests were comparable and asks whether the template added much effort. Since the sample is small, they keep the test running for another ten requests before making it the default.
Copy this one-test meeting record
| Field | Fill in during the huddle |
|---|---|
| Problem and example | What happened, and which step caused the delay or rework? |
| Test and scope | What will change, and which cases are included? |
| Owner | Who will run the test and bring back the result? |
| Baseline and measure | What are we counting before and during the test? |
| Review date and decision | When will we decide whether to keep, adapt, or stop? |
When to move the discussion out of the meeting
If the team cannot agree on what happened, ask one person to gather two or three examples and bring them back. If the change needs another team’s approval, assign someone to discuss it with that team. Use the existing escalation process for immediate safety, customer, or compliance issues.
For more candidate problems to bring to your first huddle, see these office Kaizen ideas with before-and-after examples. Put the next review on the calendar before you end the meeting.



