The fastest way to get a working continuous improvement plan template is to copy the one below into Word, Excel, or Google Sheets and fill it in five steps. You set a goal and baseline, rank your problems, find root causes, build an action plan, and track results. Each step maps to one block of the template, and each comes with a filled-in example so you can see what a good entry looks like. You do not need to sign up for anything or download a file.
Most blank templates fail for the same reason. They give you empty boxes and no guidance on what belongs in them. Teams write goals like "improve quality," skip the baseline, and list actions with no owner or due date. Three months later the plan sits in a folder, and nobody can say whether anything got better.
This guide fixes that. Lean Six Sigma Experts has done improvement work since 2011, and the structure below follows the logic of real projects: a measurable goal, data before changes, root causes before solutions, and a review rhythm that keeps the plan alive. You will see what the template contains, work through the five steps with one running example, and then set it up in the format you prefer.
What a continuous improvement plan includes
A continuous improvement plan is a short document that states what you will improve, how you will measure it, who does what by when, and how you will lock in the gain. A good template forces those answers onto one to three pages, so the plan stays readable and actually gets used.
The five steps behind the template
Every block of the template follows the Plan, Do, Check, Act cycle, the core of nearly every improvement method from Kaizen to Six Sigma’s DMAIC. If you wondered what the five steps of the continuous improvement process are, this is the practical version: set the goal, rank the problems, find the causes, act, then check and standardize. The table shows how they line up with the template.
| Step | Template block | PDCA phase | Question it answers |
|---|---|---|---|
| 1 | Goal and baseline | Plan | What are we fixing, and where are we now? |
| 2 | Problems and priority | Plan | Which problems come first? |
| 3 | Root causes and countermeasures | Plan | Why does it happen, and what will we change? |
| 4 | Action plan | Do | Who does what by when? |
| 5 | Results tracker and standardize | Check, Act | Did it work, and what do we keep? |
Fill in the overview block (owner, team, process, dates) before step 1. It takes five minutes and prevents the most common failure, a plan that nobody owns.
The template to copy
Copy the text below into your tool of choice. In a spreadsheet, give each numbered block its own tab. In Word, give each block a heading and turn the pipe-separated lines into tables with one column per field.
CONTINUOUS IMPROVEMENT PLAN
1. OVERVIEW
Plan owner:
Team members:
Process or area:
Plan period (start to end):
Next review date:
2. GOAL AND BASELINE
Problem statement:
Metric:
Baseline (value and date range):
Target:
Deadline:
Business reason:
3. PROBLEMS AND PRIORITY
Problem | Impact (1-5) | Effort (1-5) | Priority | Owner
4. ROOT CAUSES AND COUNTERMEASURES
Problem | Why 1 | Why 2 | Why 3 | Why 4 | Why 5 | Root cause | Countermeasure
5. ACTION PLAN
# | Action | Owner | Start | Due | Resources | Status | Notes
6. RESULTS TRACKER
Date | Actual | Target | Variance | What we learned | Next decision
7. STANDARDIZE AND CLOSE
What changed in the standard work:
Documents updated:
People trained:
Next cycle focus:
Seven blocks sound like a lot, but most blocks hold two to six lines. The one-page version is the goal and baseline block, the action plan, and the results tracker. Add the rest as the plan matures.
A plan with a measurable goal, a baseline, and a named owner for every action beats a long plan without them.
Plan, process, or performance improvement plan?
This template covers the improvement of a process, product, or service. You may also see it called a process improvement plan. Searchers sometimes ask how a "PIP" should be written, but in an HR setting that term usually means a performance improvement plan for one employee. That is a different document with different stakes, so check with your HR team before reusing this one for it.
For a process plan, the writing rules are simple. Use short sentences, put a number in every goal, and give every action one owner. The five steps below show what that looks like in practice, using one running example: a distribution plant that ships too many orders late.
Step 1. Set a goal and baseline
Step 1 gives you a goal with a number, a deadline, and a starting point. Write the problem statement first, pull the baseline from real data second, and set the target last.
Write a problem statement with a number in it
A usable problem statement names the process, the gap, and the cost. "Improve shipping" fails because nobody can tell when it is done. "18% of orders ship after the promised date" works because anyone can measure it. Use one metric per plan. Two metrics split the team’s attention, and the second one usually hides a trade-off against the first.
Here is the goal block filled in for the running example.
| Field | Example entry |
|---|---|
| Process or area | Outbound shipping, Plant 2 |
| Problem statement | 18% of orders ship after the promised date, causing complaints and expedited freight costs |
| Metric | On-time shipment rate |
| Baseline | 82%, average of the last 12 weeks |
| Target | 95% |
| Deadline | 6 months after the plan start date |
| Business reason | Late orders drive complaints, and rush freight cuts margin |
Capture the baseline before you change anything
The baseline is the current value of your metric, measured over enough time to be stable. As a rule of thumb, use 8 to 12 weeks of data for a weekly metric. A short window can catch one unusually good or bad week and mislead you. Write the date range next to the number so nobody argues about it later.
If the data does not exist, spend the first two weeks collecting it with a tally sheet or a simple report. Then set the target. Look at your best four-week stretch in the past year. A target slightly beyond it is ambitious but credible, and your team will believe it.
If you cannot state the baseline and the date range behind it, you do not have a goal yet, only a wish.
Step 2. List and rank the problems
Step 2 turns a pile of complaints into a ranked list. Collect every problem that could plausibly explain the gap, score each on impact and effort, and pick the top one to three for this cycle.
List every problem that feeds the gap
Ask the people who do the work. A 30-minute walk through the process, often called a gemba walk, plus a short huddle with the team will surface more than any report. Give each problem one sticky note or one spreadsheet row, and aim for 10 to 20 entries. Where you can, attach a count, such as how many of the late orders each problem explains.
Write problems as observable events, not opinions. "Pick lists print late" can be checked. "The warehouse is disorganized" cannot. Observable wording also makes the next step, root cause analysis, much faster.
Score by impact and effort
Score impact from 1 to 5 for how much of the gap the problem explains, and effort from 1 to 5 for the cost, time, and approvals needed to fix it. Priority is impact divided by effort. Use a spreadsheet formula, or divide by hand. The team should agree on each score together, not average private guesses.
| Problem | Impact | Effort | Priority |
|---|---|---|---|
| Pick lists print late | 4 | 1 | 4.0 |
| Orders wait for credit approval | 5 | 2 | 2.5 |
| Carrier pickup times missed | 3 | 2 | 1.5 |
| Packaging materials run out | 4 | 3 | 1.3 |
In the example, the plant takes the top two problems into this cycle. Park the rest on a backlog tab for the next cycle instead of deleting them. A short focus list is what makes the plan finishable.
Work on the one to three problems with the best impact for the effort, and write the rest on a backlog instead of chasing everything at once.
Step 3. Find root causes and countermeasures
Step 3 moves from symptoms to causes, then to changes worth testing. Run a 5 Whys on each selected problem, write the root cause in one sentence, and attach a countermeasure to it.
Run a 5 Whys on each problem
Start with the problem and ask why it happens. Answer, then ask why again, until you reach a cause you can act on. Five rounds is a guide, not a rule. Stop when the answer is something your team can change. Each answer must be a fact you can verify, not a guess.
Here is the template row for "pick lists print late."
| Level | Entry |
|---|---|
| Why 1 | The pick list print job runs at 9:45 a.m. |
| Why 2 | It waits for the office team to release the day’s orders |
| Why 3 | Orders are released in one batch after the credit check |
| Why 4 | Credit holds are reviewed by hand, once each morning |
| Why 5 | No rule exists to auto-approve accounts in good standing |
| Root cause | No auto-release rule for accounts in good standing |
| Countermeasure | Auto-release those orders, and review only flagged ones by hand |
Notice that the two selected problems share one root cause. This happens often. When it does, combine them into one line with one countermeasure, so the plan stays short and the fix is tested once.
Choose countermeasures you can test
A countermeasure is a change you try and measure, not a permanent decision. Good ones pass three checks:
- It addresses the root cause, not the symptom.
- You can test it on a small scale first, such as one customer group or one shift.
- You can see its effect in your metric within weeks, not quarters.
In the example, the plant adds a second countermeasure: print pick lists in hourly waves instead of one daily job. That is cheap to test and does not depend on the credit rule. Resist the urge to write ten countermeasures. Two or three tested well will move the metric more than ten started and abandoned.
Fix the root cause, not the symptom, and treat every countermeasure as a test you will measure, not a decision you have already made.
Step 4. Build the action plan
Step 4 converts countermeasures into dated, owned actions. A continuous improvement plan lives or dies in this block, because an action without an owner and a due date is only an intention.
Write actions that one person can finish
Start each action with a verb, assign one owner, and set a start and due date. If an action takes longer than two weeks, split it. Include the resources, such as IT hours, budget, or access to data, so surprises show up in week 1 and not week 6. The example uses week numbers because the plan start date is not fixed.
| # | Action | Owner | Start | Due | Resources | Status |
|---|---|---|---|---|---|---|
| 1 | Pull 12 weeks of order release times | Ops analyst | Wk 1 | Wk 1 | ERP report | Done |
| 2 | Draft auto-release rule for accounts in good standing | Finance manager | Wk 2 | Wk 3 | Credit policy | Open |
| 3 | Get controller sign-off on the rule | Finance manager | Wk 3 | Wk 4 | None | Open |
| 4 | Pilot the rule on one customer group for 2 weeks | Ops supervisor | Wk 5 | Wk 6 | IT support, about 4 hours | Open |
| 5 | Switch pick list printing to hourly waves | Warehouse lead | Wk 5 | Wk 7 | Print job settings | Open |
| 6 | Update the shipping standard work document | Ops supervisor | Wk 9 | Wk 10 | Document template | Open |
Use four status values only: Open, In progress, Done, and Blocked. Anything more elaborate gets ignored.
Check capacity, risks, and approvals
Add up the hours the plan asks of each owner. If your finance manager has four actions in the same two weeks and a month-end close, the plan is already late. Spread the work or move a date now, while it costs nothing.
Then name what could block you. Typical blockers are an approval, a system change, or a skill the team lacks. If your team has never run a Kaizen event or built a value stream map, plan a training action before the improvement action. The Lean Online Training Modules from Lean Six Sigma Experts cover Kaizen events, 5S, and value stream mapping, so a short learning step can sit in the plan as its own line item. Keep the action log visible, ideally on a shared tab or a whiteboard, so anyone can see what is overdue.
Every action needs a verb, one owner, and a due date. Without all three, it is only a wish on your list.
Step 5. Track results and standardize
Step 5 tells you whether the plan worked and locks in the gain. Record actual results against milestones on a fixed schedule, decide what to do after each review, and update the standard work when a change proves itself.
Track results on a fixed rhythm
Fill the results tracker at the same time every week or every two weeks. Record the actual metric value, the milestone for that date, and the variance. Variance is actual minus target, in percentage points for a rate. The two columns that matter most are "What we learned" and "Next decision." They turn a number into a management action.
Here is the tracker for the running example, with interim milestones between the 82% baseline and the 95% goal.
| Date | Actual | Milestone | Variance | What we learned | Next decision |
|---|---|---|---|---|---|
| Week 6 | 84% | 85% | -1 pt | Pilot cut the batch wait. Missed carrier pickups are now the largest cause | Roll the rule out to all good-standing accounts |
| Week 12 | 90% | 90% | 0 pts | Hourly waves are holding. Credit holds are down to flagged orders | Keep both changes. Add carrier pickup to the backlog |
| Week 20 | 96% | 95% | +1 pt | Goal reached for three weeks in a row | Move to standardize and close |
A negative variance is not a failure. It is a prompt to ask why and to adjust. Teams that only report green numbers stop learning.
Standardize what worked and start the next cycle
Once the metric holds at target for several weeks, complete block 7. Update the written standard work or procedure, train the people affected, and record who now owns the process. Standardizing is the Act step of PDCA. Skip it, and the process drifts back within months because the old habits are still in the documents.
Keep tracking the metric for at least a quarter after you close the plan, with a lighter check, such as monthly. Then pull the top item from your backlog, and the cycle restarts at step 1 with a new baseline. That is what makes the improvement continuous.
A change that is not written into the standard work will not last, so update the document before you close the plan.
Set it up in Word, Excel, or PDF
You can run this plan in any tool your team already uses. Excel or Google Sheets suits teams that track numbers weekly, Word suits plans reviewed in meetings, and PDF is the format for sharing a finished plan.
Excel or Google Sheets
Create one tab per numbered block and freeze the header row on each. Keep the dates in real date format so formulas work. These formulas assume the column order of the template above.
Problems tab, cell D2 (priority): =B2/C2
Results tab, cell D2 (variance): =B2-C2
Action plan tab, cell H2 (overdue flag): =IF(AND(E2<TODAY(),G2<>"Done"),"Overdue","")
Add conditional formatting that colors the overdue flag red and the Done status green. Both programs support these formulas. A pivot table or simple chart of the results tab gives you the trend line for review meetings.
Word and PDF
In Word, give each block a heading, then build the tabular blocks as tables so the columns line up. Keep the goal and baseline block on page 1 so a reader sees the target first. When the plan is final, use File, Save As, and choose PDF for a version that nobody edits by accident. Keep the editable Word file as the working copy and re-export after each review.
Adjust the template to your team size
The structure stays the same, but the depth changes. Small teams can run the plan on one page and review it in a 15-minute weekly huddle. Larger organizations should add a sponsor line to the overview block and a monthly leadership review. Manufacturing teams often add a safety and quality check to every countermeasure. Service teams often add a customer-impact note.
Two mistakes recur across all of them. The first is starting with solutions before the root cause step. The second is letting the tracker go stale after the first month. Put the review date on the calendar before you finish filling in the template.
Start your first cycle
A continuous improvement plan works when it stays small and specific: one metric, a baseline, a short problem list, root causes, owned actions, and a review rhythm. Copy the template, fill the overview and the goal block today, and use the five steps to get through the rest in a few short sessions.
If you want a second pair of eyes on your goal, your priorities, or your action plan, contact Lean Six Sigma Experts for a free 30-minute assessment with no obligation. You can also ask about training your team to run the cycles on their own.