← All posts
Automation & AIProcess improvement

How to Streamline a Business Process, Step by Step

Most of the gain comes from deleting steps. The software comes last.

Ask three people in an office how a new customer gets set up and you’ll often get three answers. One person emails the details to accounting. Another types them into the CRM first. A third keeps a spreadsheet “just in case.” All three versions work, mostly, and all three take longer than they need to.

To streamline a process is to get the same result with fewer steps, fewer hand-offs and less waiting. The tempting first move is to buy software. The better first move is to look hard at the steps themselves, because automating a messy process just makes the mess run faster.

This post covers how to find the process worth fixing first, and then how to fix it.

Before you start: find where the hours go

Most offices don’t lose time in big, visible chunks. They lose it in five-minute pieces: looking for a file, retyping an order into a second system, chasing an approval. Twenty minutes a day doesn’t sound like much, but across roughly 250 working days it comes to about 83 hours, more than ten full working days, for one person.

To find those minutes, ask everyone, or at least one person from each role, to keep a simple log for two weeks: what slowed them down (“couldn’t find the signed contract,” “retyped the order into QuickBooks”), roughly how long it cost, and whether it happens daily, weekly or now and then. A shared spreadsheet or a Teams channel is enough. Tell people it’s about the work, not about them, or it will come back empty.

The entries usually fall into a few groups: looking for things, typing the same thing twice, waiting on someone, technology getting in the way, and not knowing how a rarely done job works. For each item, multiply minutes lost each time by how often it happens by how many people it affects. As an example with made-up numbers: six people each spending ten minutes a day looking for documents is about 250 hours a year, while one person rekeying timesheets for 30 minutes every Friday is about 26. Note anything that also costs money, customers or a compliance deadline.

Then score each item high, medium or low for size and for effort to fix. Big and easy goes first. Big and hard goes on the plan for later in the year. Not everything needs the six steps below: slow computers, printers and phones belong with your IT provider or copier dealer (bring the log; numbers are harder to brush off than complaints), and a few changes cost nothing at all:

  • Agree on one place for shared files and stop saving work to personal desktops.
  • Turn recurring emails (“please approve,” “here is this week’s report”) into templates.
  • Write down the steps for any job done less than monthly, the next time someone does it.

Repeat the log once a quarter. Some problems only become visible once a bigger one is out of the way.

Step 1: pick one process and name its result

Take the top item from your log, or choose one process that happens often and annoys people: invoice approvals, new customer setup, time-off requests, quotes, new hires. Fix one at a time; each change asks people to work differently, and too many at once means none of them sticks. Then write one sentence saying what it produces and when it’s finished. “A new customer is set up in the CRM and accounting, has received a welcome email and has an account manager assigned.”

That sentence matters more than it looks. It tells you which steps are part of the job and which are habits that grew up around it.

Step 2: map what really happens

Sit with the people who do the work and write down every step, in order, the way it actually happens rather than the way the procedure says it should. For each step, note:

  • who does it;
  • which system, form or piece of paper is involved;
  • how long the step takes when someone is actually working on it;
  • how long the work waits before the next step starts.

Sticky notes on a wall or a list in a spreadsheet is enough. You don’t need flowchart software.

The last column is usually the surprise. A process that takes 40 minutes of actual work often takes four days end to end, because most of the time it is sitting in someone’s inbox. Our post on optimizing business workflows is about that waiting time and how to cut it.

Step 3: question every step

Go down the list and ask four questions of each step, in this order. Manufacturing engineers have used this sequence for decades, and it works just as well on paperwork.

Eliminate

Does this step need to happen at all? Look for copies nobody reads, approvals nobody has ever refused, reports that exist because someone asked for one once in 2019, and data typed into a system nobody uses. Deleting a step is the cheapest improvement there is.

Combine

Can two steps become one? If one person checks the form and a second person enters it, perhaps the person entering it can check it as they go. Every hand-off you remove takes the waiting time with it.

Reorder

Would a different order catch problems sooner? Checking that a form is complete before it’s routed, rather than after three people have handled it, saves everyone downstream.

Simplify

What’s left, can it be made easier? A form with fewer fields, a dropdown instead of free text, a template instead of a blank page.

Automating a messy process just makes the mess run faster.

Step 4: write the new version down

Once you’ve cut it back, write the new process down in plain words: who does what, in what order, with which form or system, and what to do when something doesn’t fit. A one-page checklist beats a 20-page procedure nobody opens.

This is also when you decide the exceptions. What happens when a customer has no tax ID yet? Who decides when an invoice doesn’t match the order? If you don’t answer these now, every exception becomes a new email thread.

Run the written version for a couple of weeks before you change anything else. People will find the gaps quickly, and they’re easier to fix on paper than in software.

Step 5: automate what’s left

Now look at what software could take over. The best candidates are steps that follow rules and involve moving information between systems:

  • copying details from a form into the CRM and accounting;
  • sending a request to the right approver and reminding them;
  • filing a signed document in the right folder;
  • sending the welcome email.

Steps that need judgment, such as deciding credit terms for a new customer, stay with a person. The software’s job is to make sure the request reaches them with everything they need and doesn’t get lost. Our post on rule-based workflow processing covers how to turn the written process into rules a system can follow.

Step 6: check it worked

Compare the new process with the old one on two simple measures you can count yourself:

  1. Time from start to finish. From the moment the request came in to the moment it was done.
  2. How often it goes wrong. Requests sent back, details corrected, customers who had to call to chase.

If both went down, move on to the next process. If not, go back to the map; usually a step you thought was gone has crept back in.

Do you need Lean or Six Sigma?

You’ll come across a lot of named methods: Lean, Six Sigma, Kaizen, business process reengineering. They’re real and useful in large organizations with dedicated improvement teams. For an office of 10 to 100 people, the core ideas are the ones above: see the process as it is, remove waste, make it consistent, and measure. You can borrow the ideas without the training program or the vocabulary.

Where we come in

The log and steps one to four are work you can do yourselves with a wall and some sticky notes. Step five is where we usually help: we build the automation in Make or Power Automate, connect it to the systems you already use, and look after it afterwards. Our business process automation page shows what that covers. When your log points at slow computers, printers or phones instead, our free technology review looks at those and gives you a written report. Either way, bring the log or the map. It makes the conversation shorter.

More on Automation & AI

Let's build your foundation.

Tell us where your business is today and we'll help map the next step.