Business process optimization for SMEs: a 90-day plan for teams with no process department

Large companies have process teams, change managers and consultants on standing contracts. A company with 15 or 60 people has the owner, a few managers and whoever happens to be good with spreadsheets. The processes still matter, perhaps more, because there is no slack to absorb waste. Here is how to approach it with the resources you actually have.

What is different about small and mid-sized firms

• Knowledge lives in people. If one person is off sick, a process stops. Documentation matters mainly as insurance against that.
• Tools grew by accident. Each department picked its own. Data is copied between them by hand.
• Everyone is busy. Any improvement that takes more than a few hours a week from one person will not survive.
• Change is fast. You can try something on Monday and judge it on Friday. This is an advantage. Use it.

Days 1 to 30: look and measure

Week 1. List the ten processes that people complain about or that touch customers or money. Score each on frequency, pain and risk. Pick one.

Weeks 2 to 4. For that one process, collect the baseline: cases per week, elapsed time, rework rate. Sit with the people who do it. Draw the real path on a whiteboard and photograph it. Do not aim for a polished map yet. The audit checklist is a good prompt for the conversation.

Days 31 to 60: fix by removing

Work through the likely fixes in order: remove steps, simplify, reorder, clarify ownership. Many SMEs find the cheapest wins here and need no new software: a shared inbox with an owner, a form with required fields, an approval limit, a weekly ten-minute review. Make the change, write down the new way in one page (see SOP optimization), and tell everyone affected.

Days 61 to 90: automate what is left, then choose the next process

If a repetitive step remains, now is the time to automate it. Start with the smallest useful piece, such as an automatic confirmation or a notification when a status changes. The ten-minute automation is a gentle first example. Re-measure against the baseline. Share the result with the team, including the people who did the work, because the next project depends on their goodwill.

Avoiding tool sprawl

Every new tool is another login, another subscription and another place where data can go wrong. Before adding one, ask three questions:

1. Can a tool we already pay for do this?
2. Who will own it, and what happens when they leave?
3. What is the cost per year, including the time to maintain it?

If you cannot answer all three, delay the purchase.

What to skip

• Formal certifications and large frameworks. Borrow the ideas, such as measuring waiting time and rework, and skip the programme.
• Mapping everything. Map the one process you are working on.
• Large automation projects before you have fixed the process. See fix the process first.

When to ask for outside help

When the process crosses several teams and nobody will own the whole. When you suspect a problem but cannot measure it. Or when you have done the easy fixes and the remaining ones need system integration. An outside view can also settle arguments, because it is not tied to any department. Our process improvement work is designed for teams of 5 to 50 people, and the first process review is free.

Related reading and services