A process improvement roadmap is a sequenced plan that turns a list of problems into scheduled projects with owners, measures and review dates. You build it in seven steps: scope the process, map how it works today, find root causes, prioritize opportunities, test changes, standardize what works, and review on a schedule. People who can run that sequence with confidence are the ones employers trust with improvement work, and a structured certification is the quickest way to learn it. At MSI, our self-paced online programs include the study materials and the exam in one fee.
TL;DR
- A roadmap is not a to-do list. It schedules improvement projects across planning periods so each one builds on the last.
- The core sequence: scope, map, diagnose root causes, prioritize, test, standardize, review.
- Pick the method to fit the problem: DMAIC when you have measurable data, PDCA when you iterate, A3 for narrow problems.
- Changes stick when someone owns them, people are trained, and results are compared with a baseline.
- A certification gives you the vocabulary and tools so you can run this sequence without guessing.
Table of Contents
- What a process improvement roadmap actually is
- The seven steps of a process improvement roadmap
- Which methodology should run your roadmap?
- Writing a continuous improvement plan
- Making changes stick
- Process improvement certifications that support the roadmap
- Start with the certification that fits your roadmap
- Perspective: why we teach the roadmap, not just the tools
- FAQ
- Sources
What a process improvement roadmap actually is
A process is any repeatable set of activities that produces an outcome: onboarding a hire, paying a vendor, shipping an order, closing a month-end. Improving one process is a project. A roadmap is what you need when there are several possible projects and limited time.
A 2015 academic paper on process improvement roadmapping defines a roadmap as improvement projects scheduled across planning periods, each meant to raise the performance of the process in focus. The researchers treat it as a portfolio, which means the order and the combination of projects matter, not just the projects themselves.
Three things separate a roadmap from a wish list:
- A goal it serves. APQC, a nonprofit research body on business processes, describes a value path: a link from process performance through business outputs to organizational goals. It tells you which outcome an improvement supports and how you will measure success.
- A sequence. Some fixes unlock others. Mapping comes before measuring, and measuring before changing.
- Dates and owners. Every item names who is responsible and when it will be reviewed.
The seven steps of a process improvement roadmap
The published guides differ in wording but follow the same arc. IBM’s process improvement guide lists scoping the process, mapping the current state, analyzing bottlenecks and root causes, designing solutions, implementing, monitoring, standardizing and reviewing periodically. The version below folds those into seven steps you can run this quarter.
Step 1: Scope the process and tie it to a goal
Pick one process and write down where it starts, where it ends and what a good result looks like. Start from the business goal, not the pain point. APQC’s team-plan guidance says to begin with the business goal, gather input from stakeholders and staff, and set measurable targets.
A good scope statement fits in two sentences: “Invoice approval, from receipt to payment. We want to cut the time to pay from 14 days to 7 without raising errors.”
Where it goes wrong: scopes that cover an entire department. If you cannot draw the boundaries on a whiteboard, the project is too big.
Step 2: Map the current state
A process map is a step-by-step diagram of who does what, in what order, and where work waits. Draw what actually happens, not what the policy says. Walk the process with the people who do it.
There are several mapping styles, such as flowcharts, swimlane diagrams and value stream maps. Our guide to picking the right process mapping technique shows how to choose between them.
Where it goes wrong: mapping the ideal version. The gaps between the ideal and the real are exactly where the improvements live.
Step 3: Measure and find root causes
Before changing anything, capture a baseline: cycle time, error rate, rework, cost per transaction, whatever your goal names. Then dig for causes rather than symptoms.
Montana State University’s A3 problem-solving guide recommends asking successive “why” questions to reach root causes. If invoices are late, ask why. Approvals are late. Why? The approver does not see the request. Why? It lands in a shared inbox. That last answer is something you can fix.
Basic quality tools help here: check sheets, Pareto charts, cause-and-effect diagrams. Our overview of the 7 basic quality tools covers when to use each.
Where it goes wrong: jumping to a solution because it is familiar. A new software tool will not fix an approval routing problem.
Step 4: Prioritize opportunities
You will probably find more fixes than you can run at once. APQC’s training on prioritizing and implementing process improvement uses techniques such as a 2×2 matrix, a prioritized heat map and a value path, and only then moves to developing the roadmap.
A simple 2×2 plots each opportunity by impact on your goal against effort to deliver. Do the high-impact, low-effort items first. Schedule high-impact, high-effort items as their own projects in later periods. Drop the low-impact, high-effort items.
This is the step that turns a list into a roadmap. You are choosing what goes in the first quarter, the second and the third.
Step 5: Design, test and pilot the change
Do not roll a new process out to everyone on day one. APQC’s continuous improvement guidance recommends testing a proposed change at an appropriate scale where practical and comparing the outcomes with the baseline, without harming quality, service, compliance or another part of the end-to-end process.
A pilot with one team or one product line gives you real data and a chance to adjust. Our piece on launching a continuous improvement culture with one PDCA pilot walks through a small pilot from start to finish.
Where it goes wrong: pilots with no success measure. Decide in advance what result counts as a win.
Step 6: Implement and standardize
When the pilot works, make it the new normal. Montana State’s guide says an implementation plan should assign actions, responsible individuals and due dates, and that actual results should be compared with predicted results.
APQC’s implementation guidance adds the human side: identify ownership and decision rights, communicate purpose and value, involve employees, provide training and resources, update controls and procedures, set measures and review dates, and allow time for adoption.
Update the written procedure, retrain the team and retire the old way. A change that lives only in someone’s head disappears when they change roles.
Step 7: Review and repeat
Set a review date before you finish. At that review, compare results to the baseline, decide whether to keep, scale, adapt or drop the change, and feed what you learned into the next project on the roadmap. This is where a one-off project becomes continuous improvement.
Which methodology should run your roadmap?
You do not have to invent the steps. Established methods already package them. Ohio State’s Fisher College of Business compares problem-solving roadmaps and describes DMAIC (Define, Measure, Analyze, Improve, Control) as the data-driven roadmap for existing processes when measurable data is available. It is the fundamental roadmap of Lean Six Sigma projects.
| Method | Best when | How it works |
|---|---|---|
| DMAIC | You have measurable data and a process that already exists | Five phases from defining the problem to controlling the gains |
| PDCA / PDSA | You want small, repeated tests | Plan, do, check, act, then repeat the cycle |
| A3 | The problem is narrow and one team owns it | One-page structured problem-solving from current state to follow-up |
| 8D | A team is solving a specific quality problem, common in automotive | Eight disciplines for containing and eliminating a defect |
The table follows the Fisher College guidance. The University of California, Irvine recommends PDCA and A3 for mid- to large-scale process improvement projects: plan the current-state analysis and root-cause work, test solutions, check results, then adopt and standardize, and repeat the cycle.
You can also mix them. UNC’s overview of quality improvement in health care notes that the choice depends on the nature of the project and that small iterative tests can combine principles from several methods. A common pattern: use DMAIC to structure the project, and PDCA cycles inside the Improve phase to test solutions.
Writing a continuous improvement plan
A roadmap covers the whole program. A continuous improvement plan covers one cycle inside it. The U.S. Administration for Children and Families publishes a continuous quality improvement plan template that works for any team. In plain terms, it asks you to:
- State the specific challenge.
- Identify root causes.
- Set a SMART goal (specific, measurable, achievable, relevant, time-bound) and name the data source you will use to track it.
- Develop a strategy.
- Plan a road test: how long it runs, who is responsible, what training or technology is needed, the dates, the setting, the participants, the learning questions, and how you will collect and analyze data.
- Assess what you learned and decide whether to maintain, scale, adapt or abandon the strategy.
- Monitor progress toward the goal.
The U.S. Institute of Education Sciences, in its continuous improvement toolkit, notes that multiple PDSA cycles are often needed, with each cycle building evidence about implementation and results before a change spreads more widely. Plan for that. Your first cycle will rarely be your last.
A worked example
Say a small accounts payable team wants faster vendor payments.
- Scope: invoice receipt to payment, goal of paying in 7 days instead of 14.
- Map and measure: the team maps 30 recent invoices and finds the longest wait is for manager approval, with invoices sitting in a shared inbox.
- Prioritize: routing invoices to named approvers is high impact and low effort. A new system is high impact and high effort, so it goes into next quarter.
- Pilot: one approver group tries the new routing for four weeks. Average time to pay is compared with the baseline.
- Standardize: the routing rule goes into the written procedure and the team is trained.
- Review: at 90 days the team checks the result and picks the next item on the roadmap.
The numbers here are illustrative, but the sequence is the one every source above describes.
Making changes stick
Most roadmaps fail in adoption, not in analysis. People need to know why the change is happening, how to do the new thing and who to ask when it breaks. APQC’s guidance points to staff review, training, observation, issue resolution and complete documentation as ways to support adoption.
Communication is part of the work, not an afterthought. Choosing workplace communication tools that fit how your team works makes it easier to share the new procedure, collect issues during the pilot and keep everyone informed at each review.
Two habits help most. Name one owner per roadmap item, with a decision right to adjust it. And publish the baseline and the latest result where the team can see them.
Process improvement certifications that support the roadmap
The steps above are simple to read and harder to run well. Root-cause analysis, process mapping, data collection and statistics are skills, and a structured program teaches them in the order you will use them. For a professional, it also puts a recognizable credential on your resume.
When readers ask which certification is best, the useful question is which one fits their role and stage. Here is how to think about it.
| If you are… | Look for… |
|---|---|
| New to improvement work, or a recent graduate | A foundational program that teaches core vocabulary and the improvement cycle |
| A working analyst or coordinator | A process improvement program covering mapping, root-cause analysis and measurement |
| A manager leading projects | A broader program in process improvement excellence, or a Six Sigma belt level |
| Leading change across teams | Change management or project management alongside improvement skills |
At MSI, our Process Improvement Analyst Certification is built for people who want the working skills of mapping, measuring and improving processes. The Process Improvement Excellence Certification suits those who want to lead that work. If your roadmap leans on the DMAIC method, our Six Sigma certification package gathers the belt levels in one purchase. Our guide to process improvement certifications by career stage compares the bundles in more detail, and our article on process improvement courses for career growth shows how to apply the learning on the job.
If you work in a state agency, ask your continuous improvement office what is available. The Wisconsin state government, for example, publishes a Yellow Belt certificate guidebook describing an agency pathway of six hours of online modules plus eight hours of instructor-led training.
How to choose on cost and fit
You are comparing three things: total cost, time and relevance to your job. Check what the fee covers. Some programs charge separately for training, exam attempts and certificates. Ours does not: every enrollment includes the study materials and the certification exam, so the number you see is the number you pay. Our programs are online and self-paced, so you can study from home around your work, and certificates are issued immediately upon completion. We back them with a 30-day satisfaction guarantee.
Then match the content to your next role. If you want to run projects, look at project management. If your goal is operational excellence, look at Lean Six Sigma. If your organization is changing, look at change management.
Start with the certification that fits your roadmap
Over 300,000 professionals have earned MSI certifications, and 98% recommend our programs. Every program is self-paced, online and all-inclusive, with study materials and the exam in one fee, and many have no prerequisites.
If you are new to this field, begin with a foundation such as our Lean Six Sigma White Belt or Project Management Essentials programs, then build toward Black Belt or a leadership certification as your roadmap grows. Browse the MSI certification programs and pick the level that fits where you are now.
Perspective: why we teach the roadmap, not just the tools
Most of the people we hear from do not lack ideas for improving their work. They lack a sequence they can trust and a credential that shows they can run it.
That is why we built our programs around the full cycle: define the problem, measure it, find the cause, test a fix and lock in the gain. Whether you call it DMAIC, PDCA or a roadmap, the discipline is the same. You learn it once and use it for the rest of your career.
We also believe the barrier to learning it should be low. Everything you need, the materials and the exam, comes in one fee, you study at your own pace, and the certificate arrives when you finish. A new graduate, a manager and a team lead can all start from where they are.
Pick one process this month. Map it, measure it, and run one small test. Then let a certification give you the structure to do it again, bigger and better.
Michael DiLeo, CEO of MSI
FAQ
What are the steps for process improvement?
Scope the process and tie it to a goal, map the current state, measure a baseline and find root causes, prioritize opportunities, pilot the change, standardize it, then review and repeat. Published guides from IBM, APQC and Montana State University follow this same arc with different labels. Each step feeds the next, so skipping the mapping or the baseline makes later results hard to prove.
What is the difference between a process improvement roadmap and a continuous improvement plan?
A roadmap schedules several improvement projects across planning periods and ties them to organizational goals. A continuous improvement plan describes one improvement cycle: the challenge, root causes, SMART goal, strategy, road test and review. The plan is a building block, and the roadmap is the sequence of those blocks.
Which methodology should I use, DMAIC or PDCA?
Use DMAIC when you have measurable data on an existing process and want a structured project. Use PDCA when you want to test small changes repeatedly and learn as you go. Many teams combine them, running PDCA cycles inside the Improve phase of DMAIC.
Which process improvement certification is best for a beginner?
Choose a foundational program that teaches core terms, process mapping and the improvement cycle, with no heavy prerequisites. Our Lean Six Sigma White Belt and Process Improvement Analyst programs are online and self-paced, with materials and the exam included in one fee. From there you can move up to Black Belt or leadership programs.
Sources
- Process Improvement Roadmapping, ICIS 2015 research paper
- APQC: How Can I Develop a Successful Process Improvement Plan for My Team
- APQC: Prioritizing and Implementing Process Improvement
- IBM: What Is Process Improvement?
- Montana State University: Steps of the A3 Process
- Ohio State Fisher College of Business: Problem-Solving Roadmaps
- UC Irvine: Planning for Process Improvement
- UNC: Basics of Quality Improvement in Health Care
- ACF: Continuous Quality Improvement Plan Template
- IES: Continuous Improvement in Education Toolkit
- Wisconsin: Yellow Belt Certificate Guidebook
- Workplace communication tools

