Process Improvement: How to Fix the Way Work Gets Done
Process improvement means changing how work is done so it is faster, cheaper or more reliable, then making the new way the normal way. Here is a seven-step method, the main methodologies in plain English and a worked example.
Every growing business has a few processes that everyone knows are broken. Invoices go out late. New hires spend their first week asking the same questions. A job gets scheduled twice, or not at all. People work around the problem instead of fixing it, because fixing it never feels urgent until something goes badly wrong.
Process improvement is the habit of fixing those things on purpose. You pick one piece of work, find out why it goes wrong, change it, check that the change helped and make the new way the normal way.
This guide covers what process improvement is, a seven-step method you can use without any special training, the common methodologies in plain English, a worked example and the step most teams skip.
What process improvement is
A business process is any repeatable piece of work with a start and an end: sending a quote, onboarding a client, closing the month, hiring a technician. Process improvement means changing that work so it is faster, cheaper, more reliable or easier to do well.
It usually targets one or more of these:
| Goal | What it looks like |
|---|---|
| Speed | Less waiting between steps, fewer handoffs, shorter cycle time |
| Quality | Fewer errors, less rework, fewer customer complaints |
| Cost | Less time spent per job, fewer tools or steps that add nothing |
| Consistency | The same result no matter who does the work |
| Capacity | The same team handles more volume without burning out |
The last two matter most for small businesses trying to grow. A process that only works when the owner does it is not a process yet. It is a person.
Signs a process needs improving
You do not need a dashboard to know where to start. Look for:
- The same mistake keeps happening. Wrong prices on quotes, missed follow-ups, forgotten steps.
- Work waits. Tasks sit in someone’s inbox for days before the next person can act.
- People ask the same questions. Especially new hires, and especially the questions only one person can answer.
- Results depend on who does it. One person gets it right, another does not.
- Workarounds everywhere. Personal spreadsheets, sticky notes and “just message me when it’s done.”
- Customers notice. Complaints, chasers and “I already sent you that.”
How to improve a business process in seven steps
Step 1: Pick one process
Start with one process, not a company-wide initiative. Choose the one that hurts most and happens often. A process that runs fifty times a month and fails ten percent of the time is a better target than one that runs once a year.
Write down, in one sentence, what better would look like: “Every new client gets a kickoff call booked within three business days of signing.”
Step 2: Map how it works today
Draw the process as it actually runs, not as it is supposed to run. Get the people who do the work in the room, because the owner’s version is rarely the real one. A simple swimlane map works well. Our guide to process mapping walks through it step by step.
Mark every handoff, every wait and every place someone has to ask a question. Those marks are where the problems live.
Step 3: Measure where it stands
Pick one or two numbers that match your goal from Step 1: how long it takes from start to finish, how often it goes wrong, how many times it bounces back for rework. You do not need precision. A tally of the last twenty runs is enough to know whether a change helped.
Without a starting number, every fix will feel like it worked.
Step 4: Find the root cause
The obvious cause is usually a symptom. Ask “why” until you reach something you can change. This is often called the five whys, though the number is a guide, not a rule.
For example: kickoff calls are booked late. Why? The project lead does not know the contract is signed. Why? Sales marks the deal won in the CRM but nobody is notified. Why? Nobody owns the handoff. The fix is not “book calls faster.” It is “make one person accountable for the handoff and trigger it automatically.” A RACI matrix is a quick way to settle who owns a step like this.
Common root causes in small businesses:
- No clear owner for a step or handoff
- Steps that exist only in one person’s head
- Missing information at the point of work
- Too many approvals for low-risk decisions
- Tools that do not talk to each other, so people re-key data
- A procedure that exists but is out of date
Step 5: Design a fix and test it small
Pick the simplest change that addresses the root cause. Then try it on a small scale before you roll it out: one person, one location, one week of jobs. This is the heart of the PDCA cycle (Plan, Do, Check, Act), covered below.
Good fixes tend to remove things rather than add them: one fewer approval, one fewer handoff, one checklist instead of three emails.
Step 6: Make the new way the standard
This is the step most teams skip, and it is why improvements fade. If the new way lives only in a meeting note or in the heads of the people who were there, the process drifts back within weeks.
Write the improved process down as a standard operating procedure. Replace the old version rather than adding a new one next to it, so there is only one answer to “how do we do this?” Our guide on how to write an SOP covers the format, and the SOP template gives you a starting point.
Then tell the people who do the work what changed and why. A short note on the reason makes the change far more likely to be followed. See how to get employees to follow SOPs for more on that.
Step 7: Review and repeat
Give the process an owner and a review date. Check your number from Step 3 after a month. If it improved, keep going. If it did not, go back to Step 4.
Then pick the next process. Process improvement works as a habit, one process at a time, far better than as a one-off project.
The PDCA cycle
PDCA, also called the Deming cycle, is the simplest structure for testing a change. It is a loop:
| Stage | What you do | Example |
|---|---|---|
| Plan | Decide the change and what result you expect | “If the project lead is notified when a deal is won, kickoff calls will be booked within three days” |
| Do | Try it on a small scale | Turn on the notification for one account manager’s deals for two weeks |
| Check | Compare the result with your starting number | Were those calls booked faster than before? |
| Act | Adopt, adjust or drop the change | Roll it out to everyone and update the onboarding SOP |
Then the loop starts again with the next problem. The point is that every change is a test, not a decision you are stuck with.
Process improvement methodologies in plain English
You will see these names a lot. You do not need to adopt any of them formally, but each has a useful idea worth borrowing.
| Method | Core idea | Useful for small businesses |
|---|---|---|
| PDCA | Plan, Do, Check, Act: test changes in small loops | Yes. The easiest place to start |
| Lean | Remove waste: waiting, rework, extra steps, unnecessary movement | Yes. Spotting waiting and rework on a process map is quick |
| Six Sigma | Reduce variation and defects using data, often through DMAIC (Define, Measure, Analyze, Improve, Control) | Partly. The structure helps; the statistics are often more than you need |
| Kaizen | Small, continuous improvements suggested by the people doing the work | Yes. Makes improvement everyone’s job, not a project |
| Business process reengineering | Redesign a process from scratch rather than tweaking it | Occasionally, when a process is broken beyond patching |
What they all share: understand the current process, find the real cause, change it deliberately and lock in the result. The “Control” in DMAIC and the “Act” in PDCA are the same idea as Step 6 above.
Worked example: quote turnaround at a fictional home services company
The example below uses a fictional company to show how the steps fit together.
Ridgeview Heating and Cooling, a fictional twelve-person HVAC company, kept losing jobs because quotes went out slowly. The owner suspected the technicians.
- Pick: Quote turnaround. Goal: every quote sent within one business day of the site visit.
- Map: The technician took photos and notes on site, texted them to the office manager, who typed a quote, then sent it to the owner for pricing approval, then emailed it to the customer.
- Measure: Over the last twenty site visits, most quotes took three to four days. Most of that time was waiting for the owner’s approval.
- Root cause: Every quote, even routine replacements at standard prices, needed the owner’s sign-off. The owner was on job sites most of the day.
- Test: For two weeks, quotes using standard price-book items under a set amount went straight out from the office manager. Only custom or larger quotes went to the owner.
- Standardize: The new rule, the approval threshold and the steps for building a quote from the price book were written into the quoting SOP. The old version was replaced. Technicians got a short checklist of the photos and measurements the office needs.
- Review: The office manager owns the SOP, with a review every six months or whenever prices change.
The fix was not “work faster.” It was removing an approval that added nothing for routine work, then writing the new rule down so it held.
Common process improvement mistakes
- Starting too big. “Fix operations” is not a project. “Cut quote turnaround to one day” is.
- Skipping the current-state map. You end up improving the process you imagine, not the one people run.
- Fixing symptoms. Telling people to “be more careful” rarely fixes a missing owner or a missing step.
- Changing everything at once. If five things change and the result improves, you will not know which one mattered.
- No starting number. Without a baseline, you cannot tell whether the change helped.
- Not writing the new way down. The most common reason improvements fade. The old procedure stays in the folder, new hires learn from it and the problem comes back.
- Leaving out the people who do the work. They know where the process breaks, and they are the ones who have to follow the new version.
Process improvement and SOPs work together
Improvement and documentation are two halves of the same loop. Mapping shows how work happens. Improvement changes it. The SOP is where the change lives so it survives the next busy month, the next hire and the next person leaving.
| Stage | Tool |
|---|---|
| See how the work runs today | Process map |
| Settle who owns each step | RACI matrix |
| Change the process and test the fix | PDCA |
| Lock in the new way | SOP |
| Catch the next problem early | Owner, review date and feedback from the people doing the work |
If you are improving several processes as part of a bigger push to make the business run without you, our guide to systemizing your business covers the wider sequence.
How SOPCompass helps
You can run process improvement with a whiteboard and a spreadsheet. Where SOPCompass helps is the part that usually fails: writing the improved process down and keeping it current.
- Capture the new way quickly. The AI assistant interviews the person who does the work by text or voice and drafts the SOP, or you can record the task once and get the steps with screenshots. Nothing is saved until a person approves it.
- Update the old version instead of adding another. When the process changes, edit the existing SOP. Version history keeps what it said before, so you can compare or restore if a change does not work out.
- Hear from the people doing the work. Comments on steps let anyone flag the exact step that is out of date or causing trouble, which is often where the next improvement comes from.
- Make sure people see the change. Assign the updated SOP to the people affected, with a note on what changed and a due date, and see who has completed it.
- Know when to look again. Every SOP can have an owner and a review interval. On the Business plan, Insights shows each owner which of their SOPs are due for review, and surfaces questions your team asks that your SOPs do not answer yet.
What it will not do: it will not find the root cause for you or decide which fix to try. That still takes the people who know the work, a map and an honest look at where things go wrong.
Where to start today
Pick the process that caused the most recent complaint, from a customer or from your team. Write one sentence describing what better looks like. Tally how the last twenty runs went. Then sit down with the people who do the work and ask why it goes wrong, until you reach something you can change. Test the fix for two weeks, and if it works, write it down as the new standard before you move on.