Process Improvement Meeting Agenda Template (Timed, 75 Minutes)
Use this process improvement meeting agenda to fix one broken process at a time. It runs 75 minutes, moves from the measured problem to root cause to a small pilot, and ends with an owner and a date for each change.
Used by 300,000+ individuals and teams. Free trial, no credit card required.
Process improvement meeting agenda: the template
Nine timed items that take a team from a measured problem to a tested change. Examples show the level of detail to aim for, so replace them with your own process.
Process improvement meeting agenda
- Process under review: [Process name]
- Process owner: [Name]
- Date and time: [Date, start time]
- Location or link: [Room or video link]
- Facilitator: [Name]
- Note taker: [Name]
- Asistentes: [People who do the work, process owner, one customer of the process]
- Baseline metric: [Current cycle time, error rate or cost]
-
0:005 minGoal and scope of the session
Name the one process in scope and what is out of scope. State the target the group is working toward.
EjemploScope: invoice approval, from receipt to payment. Target: cut cycle time from 7-days to 7.PropietarioFacilitator -
0:0510 minCurrent process and baseline data
Walk the process as it actually runs, step by step, with the measures you have. Use a real recent example.
EjemploAverage 7-days. 22% of invoices bounce back once for a missing purchase order number.PropietarioProcess owner -
0:1510 minPain points from the people who do the work
Each person names the step that costs them the most time. Write them on one list without debating yet.
EjemploApprovers get invoices by email with no due date. AP re-keys the same data into two systems.PropietarioFacilitator -
0:2515 minRoot cause analysis
Pick the top two pain points and ask why five times, or draw a fishbone. Stop at a cause the team can change.
EjemploWhy late? Waiting on approval. Why? Approver never sees it. Why? No alert. Cause: no routing rule.PropietarioFacilitator -
0:4015 minImprovement ideas and ranking
Generate ideas, then rank each by impact and effort. Pick one or two to try first.
EjemploAuto-route by cost centre (high impact, low effort). Replace re-keying with an import (high impact, high effort).PropietarioEquipo -
0:555 minPilot plan and success measure
Define a small test: where, for how long, and which number tells you it worked.
EjemploPilot routing rule on one cost centre for 3 weeks. Success: cycle time under 9 days.PropietarioProcess owner -
1:005 minRisks and what could go wrong
Name who is affected by the change and what could break. Decide how you will notice early.
EjemploRisk: approvers ignore alerts. Check: open rate on week 1.PropietarioEquipo -
1:055 minOwners, dates and follow-up
Assign each action an owner and a date. Book the review meeting now.
EjemploRule set up by Dana, 12 Feb. Review pilot results on 5 March.PropietarioProcess owner -
1:105 minRead-back and close
Read out decisions and actions. Say when the written summary will be sent.
EjemploSummary and updated process map go out tomorrow by 3 pm.PropietarioNote taker
Elementos de acción
| Task | Propietario | Due |
|---|---|---|
| Set up the cost centre routing rule for the pilot | Finance systems lead | 12 Feb |
| Pull 30 days of invoice cycle time data as a baseline | Process owner | [Date] |
| Send the updated process map to everyone who handles invoices | Note taker | Next working day |
| Schedule the pilot review meeting | Facilitator | [Date] |
Copy-ready agenda text
Paste this into Google Docs, Word, Notion or an email. Replace anything in [brackets].
PROCESS IMPROVEMENT MEETING AGENDA
Process under review: [Process name]
Process owner: [Name]
Date and time: [Date, start time]
Location or link: [Room or video link]
Facilitator: [Name]
Note taker: [Name]
Attendees: [People who do the work, process owner, one customer of the process]
Baseline metric: [Current cycle time, error rate or cost]
TIMED AGENDA (75 minutes)
0:00 Goal and scope of the session (5 min) | Owner: Facilitator
Name the one process in scope and what is out of scope. State the target the group is working toward.
0:05 Current process and baseline data (10 min) | Owner: Process owner
Walk the process as it actually runs, step by step, with the measures you have. Use a real recent example.
0:15 Pain points from the people who do the work (10 min) | Owner: Facilitator
Each person names the step that costs them the most time. Write them on one list without debating yet.
0:25 Root cause analysis (15 min) | Owner: Facilitator
Pick the top two pain points and ask why five times, or draw a fishbone. Stop at a cause the team can change.
0:40 Improvement ideas and ranking (15 min) | Owner: Team
Generate ideas, then rank each by impact and effort. Pick one or two to try first.
0:55 Pilot plan and success measure (5 min) | Owner: Process owner
Define a small test: where, for how long, and which number tells you it worked.
1:00 Risks and what could go wrong (5 min) | Owner: Team
Name who is affected by the change and what could break. Decide how you will notice early.
1:05 Owners, dates and follow-up (5 min) | Owner: Process owner
Assign each action an owner and a date. Book the review meeting now.
1:10 Read-back and close (5 min) | Owner: Note taker
Read out decisions and actions. Say when the written summary will be sent.
ACTION ITEMS
Task | Owner | Due
[Task] | [Name] | [Date]
How to run this meeting
-
Bring one real example, not a diagram on its own
Pick a recent case that went badly and trace it through the process. People see waste faster in a real case than in a clean flowchart.
-
Invite the people who do the work
Managers describe the process as designed. The people doing it know where it breaks. Include at least one person from each step, plus one customer of the process.
-
Fix the cause, not the symptom
Do not let the group jump from pain point to solution. Spend the root cause slot asking why until you reach something you can change, then rank ideas.
-
Start with a small pilot
Ask for a three to four week test with a number that decides success. A small pilot is easier to approve and cheaper to reverse than a full rollout.
Capture the root cause discussion without losing the room
Process improvement sessions move fast between data, ideas and decisions, and the reasoning is what you want to keep. Speak AI records the session and writes up the discussion and the follow-ups.
- Record the session on Zoom, Google Meet or Microsoft Teams, or upload the recording of an in-person workshop.
- Get a transcript with speakers labelled, so you can find who described each pain point.
- Get an automatic summary of the baseline, root causes and the ideas ranked highest.
- Get action items with owners and dates pulled out, ready to track against the pilot.
See how the Asistente de reuniones con IA y el Tomador de notas con IA work, or start with a free account.
Preguntas frecuentes
What is a process improvement meeting?
A process improvement meeting is a working session where the people who run a process measure it, find the root cause of delays or errors, choose a change and plan a small test. It ends with owners, dates and a way to check the result.
What should be on a process improvement meeting agenda?
Goal and scope, the current process with baseline data, pain points, root cause analysis, ranked improvement ideas, a pilot plan with a success measure, risks, and owners with dates. Time each item and name who leads it.
Can you give me an example of a process improvement?
A finance team adds an automatic routing rule so invoices go to the right approver, cutting cycle time from 7-days to 9. Another example is replacing a manual copy step between two systems with a scheduled import.
What are the core principles of continuous improvement?
Measure the current state, involve the people who do the work, find root causes before choosing fixes, test changes in small steps, check the result against data, and repeat. Improvement is a loop, not a one-off project.
How long should a process improvement meeting be?
Seventy-five minutes works for one process: about 25 minutes on data and pain points, 30 on root cause and ideas, and the rest on the pilot and actions. Split larger processes into two sessions rather than rushing.
Run the session, then let Speak AI write up the findings
Book a demo to see how Speak AI turns a workshop recording into a summary, decisions and action items, or try it free on your next meeting.