Process Optimization Step by Step: From As-Is Mapping to Measurement

Why do so many process optimization projects fizzle out?

The resolution usually follows a bad month. Too many complaints, delivery times that are too long, too much overtime. The owner decides to “optimize the processes.” What follows is a workshop with many sticky notes, a list of twenty measures, and after a few weeks the day-to-day business, which covers everything up again.

The failure rarely has to do with a lack of will. What is missing is a narrow focus. A company has dozens of workflows, and whoever wants to improve all of them at once improves none. On top of that, often nobody is responsible for the initiative and nobody records how success will be measured.

A workshop with 31 practitioners involved in process projects at small and medium-sized enterprises shows what they themselves consider decisive (Lückmann and Feldmann, 2017). The participants named 117 individual impact factors, which the authors condensed into 64 success factors. The most important areas were project integration, project controlling, and stakeholder management, followed by risk management, HR topics, and organizational culture. The authors themselves speak of a preliminary insight. It is nevertheless notable that no method and no tool sits at the top.

The guiding question of this guide is therefore: how does a small business improve a workflow so that the change sticks in daily work and can be measured? To answer it, we go through the four steps from the as-is analysis to the bottleneck, the target process, and measurement, and finally clarify what small businesses should do differently.

Anyone who wants to optimize “the processes” has not chosen one yet.

How does process optimization work in four steps?

Process optimization means changing a recurring workflow so that it reaches its result faster, with fewer errors, or with less effort. The method consists of four steps that repeat. It is called the four-step loop here: as-is, bottleneck, to-be, measurement.

1. As-is mapping

   You record how the workflow actually runs today, with owners, working times, and idle times.

2. Bottleneck analysis

   You find the one spot that slows down the entire workflow, and its cause.

3. To-be process

   You describe what the workflow should look like after one targeted change at the bottleneck.

4. Measurement

   You compare a number defined in advance before and after the change and decide whether the change stays.

The rough durations apply to a manageable workflow in a small company and are rules of thumb for orientation, not measured values. What matters is the ratio: a few hours of analysis, then four weeks of trial. How this loop differs from selecting software is explained in the article on process before tool.

Step 1: How do you map the as-is process?

Choose a workflow that occurs frequently and whose result the customer notices. The example used here is complaint handling. Trace five completed cases from receipt to resolution and ask the people involved about exactly these cases.

• Every step has a name and exactly one owner.
• The actual working time is recorded for every step.
• The idle time until the next step begins is recorded for every step.
• It is noted how many cases are currently waiting before each step.
• Loops are marked: where did a case go back, and why?

The article on how to visualize your sales process shows how to put the result on one page in readable form. The template there can be applied to any workflow.

Step 2: How do you find the bottleneck?

A workflow is as fast as its slowest point. This point is called the bottleneck. You recognize it by the cases piling up in front of it while the steps behind it wait for work. The “cases waiting” column from the as-is map shows it immediately.

Finding the bottleneck is half the work. The other half is the question of the cause. Three kinds occur especially often in small companies.

• Capacity: A person or machine has too little time for this step because they are responsible for other things too.
• Rule: An approval, a signature, or a consultation is mandatory although it changes something in only a few cases.
• Information: The step cannot begin because details are missing and first have to be obtained.

In the example, engineering waits in most complaints for photos and serial numbers that nobody asked for at receipt. It is an information bottleneck. More staff in engineering would change little. The bottleneck analysis for sales describes what the same analysis looks like for selling. Which bottlenecks slow down an entire company is covered in the article on growth brakes.

Step 3: How do you design the to-be process?

The to-be process is not a new workflow built from scratch. It is the existing workflow with one targeted change at the bottleneck. Everything else stays as it is. That way you can say later what made the difference.

Two findings from research argue for placing this step before any digitalization. Ward and Zhou (2006), using data from a survey of manufacturers, found that lean practices significantly reduce lead time and that the influence of IT integration runs through these practices. Hao and colleagues (2026) examined listed Chinese companies from 2009 to 2019. Among early adopters of digital transformation, financial performance declined because sharply higher administrative costs from the friction between legacy and new digital structures outweighed the advantages on the revenue side. Both papers concern larger companies. For a small company, they at least suggest caution about letting old and new workflows run side by side.

Step 4: How do you measure the success of process optimization?

The number is defined before the change and measured for the first time before the change. If you only think afterwards about how to recognize success, you will always find something that looks better. Suitable numbers are those that can be counted without effort.

After four weeks there are three possible decisions. The change stays because the number has improved. It is adjusted because the direction is right and the extent is not. Or it is withdrawn. The third decision is not a failure. It shows that the cause lay elsewhere and leads back to step 2.

A fixed place for this number is the weekly team meeting. Ten minutes are enough, as the agenda in the article on weekly planning in the team shows. Why a few numbers help more than many is covered in the article on data-based decisions.

What should small companies do differently in process optimization?

The well-known methods of process improvement come from large corporations, and they cannot be transferred one to one. A survey of managers from 433 manufacturing enterprises in the Czech Republic (Pech and Jelínková, 2025) shows that the adoption of lean principles depends on company size. Large enterprises have an advantage when it comes to more demanding principles such as standardization and visualization. Small and medium-sized companies rely more on universal principles such as respect for employees.

A smaller survey among manufacturers in the precision and electronics industry in Singapore (Yeoh, Marques, and Silva, 2026) arrives at a similar picture with 36 responses. About half of the companies find it difficult to implement lean methods. The authors name a lack of experience, skills, and knowledge as barriers. Management support is described as vital, and internal resources and organizational culture are considered more critical than tools and external expertise. The sample is small and limited to one industry, but the direction matches the finding by Lückmann and Feldmann.

• Start small. One workflow, one bottleneck, one change. The loop replaces the major project.
• Lead from the front. In a small company, the owner is the management support. If the owner does not look at the number weekly, nobody will.
• Let the people involved do the design. Whoever carries out the step every day usually already knows the cause of the bottleneck.
• Use simple means. A spreadsheet, a tally sheet, and a fixed appointment are enough for the first passes.

The next step

1. Choose a workflow that occurs frequently and where customers regularly ask for updates.
2. Trace five completed cases and fill in the as-is table.
3. Count the cases waiting before each step and name the bottleneck and its cause.
4. Agree on a single change, one owner, and one number you will count for four weeks.
5. Put the date for the decision in the calendar before you begin.

After the first pass you know the method, and the second goes faster. An obvious next workflow is the handoff from quote to order, which is covered in the article on optimizing order processing. If you regularly improve one workflow after another, you rebuild more over a year than any one-off major project.

Back to the opening question: an improvement sticks when it is limited to a single workflow, starts at the bottleneck, has one owner, and is measured by a number that is decided on at a fixed date. Methods and tools help, but they replace neither the narrow focus nor the responsibility.