A process improvement roadmap is a short, ordered list of the processes you will fix, in what order and what done looks like for each.
That’s all it needs to be. The ones that fail tend to be long lists of everything that could be better, with no order and no owner.
Here is how we build one with a client, usually in a single working session.
What should a process improvement roadmap include?
For each process on it: the problem in one sentence, what it costs, who owns the fix, what done looks like and roughly when. Most roadmaps worth following fit on one page and hold three to five processes, not thirty.
How do you build a process improvement roadmap?
- List the core processes. The ten to twenty recurring processes the business runs on: quoting, onboarding a customer, billing, hiring and so on. Keep each to a short name.
- Score each one. Rate how often it goes wrong, what that costs and how much it depends on one person. A simple 1 to 3 on each is enough.
- Pick the first three. Take the highest scores you can realistically fix in a few weeks each. A high score you can’t touch for six months goes later.
- Define done for each. Write what will be true when the process is fixed, such as “a new hire can quote a standard job without help.”
- Put them in a sensible order. Document before you automate, and fix the process that feeds another before the one that depends on it.
- Name an owner and review it quarterly. Each fix needs one person on your side who owns it. Revisit the roadmap every quarter and add the next process when one is done.
How do you prioritize process improvements?
A three-way score keeps it honest and fast. Here is the version we use:
| Factor | 1 | 2 | 3 |
|---|---|---|---|
| How often it goes wrong | Rarely | Monthly | Weekly or more |
| What it costs when it does | Minor | Rework or delay | Lost revenue, customers or compliance |
| How much it depends on one person | Anyone can do it | Two people can | Only one person can |
Add the three numbers. Anything scoring 7 or more is a strong candidate for the first round. Our list of 10 process improvement ideas is a good place to look for what the fix might be once a process makes the cut.
What order should the fixes go in?
Usually documentation first, then simplification, then automation. A process that isn’t written down can’t be reliably improved or automated, because nobody agrees on what it is.
That is why so many roadmaps start with SOP Documentation and move into Workflow Automation once the process is stable.
How do you keep the roadmap moving?
One fix at a time, finished and handed over before the next starts. Roadmaps tend to stall when five improvements start at once and none of them finish. A named owner, a definition of done and a quarterly review do most of the work.
If you want help building the roadmap or working through it, that is our process improvement work.
Common questions about process improvement roadmaps
How long should a process improvement roadmap be?
Usually one page, with three to five processes in the current round. A longer list tends to spread attention too thin and nothing gets finished. Keep a separate parking lot for everything else, and promote the next process from it when one on the roadmap is done.
How often should the roadmap be reviewed?
Quarterly works for most small businesses. Check what was finished, re-score anything that has changed and pull the next process in from the parking lot. Reviewing more often tends to turn into re-planning instead of fixing.
Who should own the process improvement roadmap?
One leader should own the roadmap itself, and each process on it needs its own owner, usually the person closest to the work. Without a named owner for each fix, the roadmap becomes a list of good intentions.
