5 Process Improvement Steps That Actually Work for Small Businesses
Skip the Six Sigma jargon. Here are 5 practical steps to find and fix broken processes in your small business — starting today.
Process Improvement Without the Jargon
Search “process improvement” and you’ll find enterprise frameworks: Six Sigma, Lean, Kaizen, DMAIC. Great for Fortune 500 companies. Useless for a 10-person business where the owner is also the accountant, HR department, and sales team.
Here’s process improvement for the rest of us — five steps, no certifications required.
Step 1: Find the Process That Hurts Most
You don’t need to improve every process. You need to improve the one that’s causing the most pain right now.
Ask yourself:
- What do I complain about most? “I can’t believe we messed this up again” — that’s your process.
- Where do mistakes happen? Customer complaints, missed deadlines, wrong orders — trace them back to a process.
- What takes way too long? If something takes 2 hours but feels like it should take 30 minutes, the process is broken.
- What depends on one person? If only Sarah can do it, and Sarah is on vacation, that’s a process problem.
Pick one. Just one. The one that makes you say “there has to be a better way.”
Step 2: Document How It Actually Works Right Now
Before you can improve a process, you need to see it. Not how you think it works. Not how it’s supposed to work. How it actually works today.
Watch someone do it. Or if it’s your task, write down every single step as you do it next time. Include:
- Every step, in order
- Every tool or system used
- Every decision point (“if X, do Y; if Z, do W”)
- Every handoff between people
- Every wait time
You’ll immediately notice things:
- Steps that seem unnecessary
- Places where information gets lost
- Handoffs that create delays
- Decision points with no clear answer
For how to write this down effectively, see our guide on how to write a business process document.
Step 3: Find the Waste
Now that you can see the process, look for five types of waste:
1. Waiting. Where does work sit idle? Where is someone waiting for approval, information, or a response before they can continue?
2. Redundancy. Is anyone doing the same thing twice? Entering data into two systems? Checking something that was already checked?
3. Unnecessary steps. Are there steps that exist because “we’ve always done it that way”? Challenge every step: what happens if we skip this?
4. Confusion. Where do people have to ask questions? Where do mistakes happen? These are signs the process isn’t clear enough.
5. Bottlenecks. Is there one person or one step that everything flows through? That’s your constraint. Everything downstream is limited by it.
Circle the waste. You don’t need to fix everything — fix the biggest one.
Step 4: Redesign the Process
Take the documented process and redesign it. Rules:
- Remove steps that don’t add value. If a step exists only because of tradition or fear, cut it.
- Combine steps where possible. If two people touch the same information, can one person handle both?
- Eliminate handoffs. Every time work passes from one person to another, information gets lost and time is wasted. Fewer handoffs = fewer errors.
- Automate the repetitive. If someone is copying data from one place to another, that’s a job for software.
- Add checklists for error-prone steps. If a step frequently goes wrong, add a checklist. Checklists are simple and they work.
- Set time limits. If approvals take 3 days, set a policy: approvals within 24 hours or they’re auto-approved.
Write the new process document. It should be shorter and simpler than the current one.
Step 5: Test, Measure, Repeat
Don’t roll out the new process to everyone on day one. Test it:
- Have one person follow the new process for a week
- Track: Did it take less time? Were there fewer errors? Did anything break?
- Adjust based on what happened
- Roll it out to everyone
- Check back in 30 days — is it sticking?
What to measure:
- Time to complete the process
- Error rate
- Number of questions asked
- Customer complaints related to this process
If the numbers improve, the improvement worked. If they don’t, go back to Step 3 and look for waste you missed.
Real Example: Invoice Processing
Before improvement:
- Customer emails order
- Sales rep writes order on paper
- Paper goes to the office manager’s inbox
- Office manager enters it into QuickBooks (sometimes 2 days later)
- Office manager prints invoice and mails it
- Customer receives invoice in 5-7 days
- Customer calls to ask “where’s my invoice?” at least once a week
Waste found:
- Paper handoff creates delays (2+ days)
- Manual data entry from paper to QuickBooks
- Mailing adds 5-7 days
- Customer calls waste everyone’s time
After improvement:
- Customer emails order
- Sales rep enters it directly into QuickBooks from their phone
- QuickBooks auto-generates and emails the invoice immediately
- Customer receives invoice within hours
Result: Invoice time dropped from 7-10 days to same day. Customer complaint calls about invoices: zero.
That’s process improvement. No framework needed. Just see the waste, remove the waste.
The Ongoing Habit
Process improvement isn’t a one-time project. Build this habit:
- Monthly: Ask your team “what’s frustrating you?” Pick one process to improve.
- When mistakes happen: Don’t blame people. Ask “what’s wrong with the process that allowed this?”
- When you hire: Every time a new person struggles with something, that’s a process documentation gap.
Get Started
Pick the process that hurts most. Document how it works today. Find the waste. Fix it.
What’s the Process For helps you document and share your processes with your team. When you improve a process, update the documentation and everyone’s immediately following the new version. Start free.
Related reading:
Get templates like this in your inbox
We send practical SOP templates and process documentation tips. No fluff, no spam.
You're in! Check your inbox.
Ready to document your processes?
Start creating SOPs your team will actually use. Free to get started.
Start Free TrialKeep Reading
Small Business Operations Checklist: 25 Processes Every Business Needs
A practical checklist of the 25 processes every small business should have documented. Stop running on memory and start running on systems.
guidesHow to Delegate Tasks Without Losing Control (The Process Documentation Method)
Struggling to let go of tasks? Learn how documenting your processes makes delegation automatic — you stay in control without doing everything yourself.
guidesHow to Create a Checklist That People Actually Use (Templates Included)
A practical guide to building checklists your team will follow — from 5-item opening checklists to 50-step audit procedures. With examples.