Operational Process Improvement, How to Map Your Company's Processes and Eliminate Waste

Many business owners reach the decision to buy a new system after months of strain. Orders are late, approvals get stuck, and the team works long hours without the results improving, so new software looks like the fastest way out. But a system installed on top of a confused process does not fix it. It makes the confusion faster and more expensive.

That is why operational process improvement is the step that comes before any investment in technology. It means understanding how work actually moves through your company, from the first request to the last step, then removing whatever adds no value and rearranging what remains so the work gets done in less time and with fewer errors. What we often see at Reform is that the problem is rarely the software itself. It is the process the software was placed on.

In this article we walk you through it step by step, from choosing the first process and mapping it as it runs today, to measuring its time and waste, then redesigning it and writing it as a standard procedure, and finally automating the parts that have settled. It is part of the bigger picture we explain in the guide to digital transformation and business development for companies.

The article in five points

Fix the process before buying any system, because automating chaos produces faster chaos.
Start with one repetitive, painful process that can be measured and has a clear owner with the authority to change it.
Map the process as it runs today with a swimlane map that shows who does what, and the inputs and outputs of each step.
Measure cycle time, waiting time and the rework rate before any change, so you know how much it improved afterwards.
Write the new process as a standard operating procedure, or SOP, then automate only the parts that have settled, and review the results after 30 and 90 days.

How to choose the first process to start with

The common mistake is trying to improve everything at once. A company has dozens of processes, from sales and purchasing to hiring and collections, and trying to fix them all together wears the team out without a clear result. It is better to choose one process, succeed with it, then carry what you learned to the others.

A process makes a good starting point when it has these qualities.

Repetitive, happening daily or weekly, so the effect of any improvement shows quickly.
Painful, a source of complaints from customers or the team, or a clear drain on the company's time and money.
Measurable, with a defined start and end, so you can calculate the time between them.
Limited in scope, passing through two or three departments rather than the whole company.
Owned, meaning one person has the authority to change it and is accountable for the result.

Processes that often suit a first round include the order cycle from receipt to delivery, booking and billing in medical facilities, collecting payments from customers, and purchase approvals. Choose only one, and write in a single line where it starts and where it ends, so the scope does not grow while you work.

How to map the process as it actually runs today

Most companies have a picture of their processes that differs from reality. The manager describes the steps as they were set years ago, while the team works another way, full of accumulated exceptions and temporary workarounds. The goal at this stage is to map what actually happens, not what should happen.

The swimlane map in its simplest form

The simplest tool for this is the swimlane map. On a board or a large sheet of paper, draw horizontal rows, one row for each role involved in the process, such as the customer, sales, the warehouse and accounts. Then place each step in the row of whoever performs it, and connect the steps with arrows in the order they happen. Every arrow that crosses from one row to another is a handoff from one person to another, and these points in particular are where time is usually lost.

For each step, note three things, the input it needs, such as a request, a form or an approval, the output it produces, and where the information is kept, whether in a system, a spreadsheet or a WhatsApp message. Clearly mark the decision points where the path branches, such as accepting or rejecting an order.

How to gather the right information

Do not draw the map in the management office. Sit with the people who actually do the work, and ask each of them to explain what they do when the request reaches them, and what they do when something is missing. The most accurate method is to follow one real transaction from start to finish, a single order or a single booking, and record every station it passed through and how long it stayed there. You will usually discover steps nobody mentioned, because they have become habits the people repeating them no longer notice.

How to measure cycle time, waiting and rework before any change

Without starting figures, you will not know whether the improvement worked. You do not need a complex system to measure. You need a sample of real transactions and the timing of each station in them. These are the three most important measures.

Cycle time is the time from the start of the process to its end as the customer sees it, such as the time from receiving an order to delivering it.
Waiting time is the time a transaction sits with nobody working on it, waiting for an approval, a piece of information or its turn.
The rework rate is the number of transactions sent back to an earlier step because of an error or something missing, divided by the total number of transactions.

When you compare cycle time with the time the actual work took, the real picture appears. A transaction may spend days in the cycle while the actual work on it takes no more than an hour or two, and the rest is all waiting. That gap is where most of the room for improvement lies, because reducing waiting is far easier than asking employees to work faster.

To make the figures reliable, take a sample of at least twenty transactions in a normal period, not in a peak season and not in an unusually quiet week. Also record how many times the transaction passed between people and how many times the same data was entered, because both will help you in the next stage.

What the types of waste in office work are and how to spot them

Waste is any step that consumes time or effort without adding value the customer feels or the company needs. In factories it is easy to see in piled up stock and idle machines, but in office work it hides in email, spreadsheets and messages. This table shows its most common types.

Type of waste	How it shows in daily work	First step to fix it
Waiting for approvals	A request waits days for the signature of a manager who is traveling or busy	Clear authority limits, and a stand in who approves during absence
Entering data more than once	The same order is typed in WhatsApp, then in a spreadsheet, then in the accounting system	One source of data that all later steps draw from
Too many handoffs	The transaction passes between five people for work two could do	Merging consecutive steps with one person
Searching for information	An employee asks colleagues about an order's status or the latest version of a file	One known place for each piece of information
Rework	An invoice is corrected because the customer's details were incomplete	An entry form with mandatory fields and an early checkpoint
Unused reports	A weekly report is prepared with effort and nobody reads it	Ask whoever receives it which decision they make based on it, and stop it if there is none

Spotting it is simple. Take your map and mark each step with one of three colors, the first for a step that adds value for the customer, the second for a step the company needs, such as a financial check, and the third for a wasteful step that can be removed or reduced. You will usually find more steps in the third color than you expected.

Three practical examples of operational process improvement

These are illustrative examples of common situations, showing how the steps above apply to different processes in different sectors.

The order cycle in a distribution company

A distribution company in Cairo receives its customers' orders from sales representatives by phone and WhatsApp. A sales employee types the order into a spreadsheet, sends it to accounts to check the credit limit, then to the warehouse, and the order comes back to sales if one of the items is out of stock. Mapping it shows that the order moves between departments several times, and that the longest wait is at the credit limit check. The improvement here is for the representative to see the customer's balance and the stock status before confirming the order, and for credit to be checked by hand only when an order exceeds the allowed limit.

Booking and billing in a clinic

A clinic in Manama takes bookings by phone, the receptionist writes them in a notebook and then in the system, and when the patient arrives their details are typed again to issue the invoice. The result is waiting at reception and errors in names and insurance details. The improvement starts with entering the data once at booking, checking insurance details the day before the appointment rather than on arrival, and sending a reminder that asks the patient to confirm attendance. Waiting at reception drops, fewer appointments are missed, and the invoice comes out right the first time.

Collections in a service company

A maintenance company in Riyadh completes its jobs on time, but collecting what it is owed takes weeks. When the process is mapped, it becomes clear that the invoice is issued only after the technician hands the paper visit report to the office, and that nobody follows up on invoices due until the end of the month. The improvement is for the technician to upload the report from the site as soon as the visit ends, so the invoice is issued the same day, with a weekly review of receivables that gives each invoice an owner and a date to contact the customer.

How to redesign the target process

Once you know where time is lost, draw a second map of the process as you want it to be. Do not start from zero but from the current map, and at each step ask these questions in order.

Can it be removed? If it adds no value for the customer and the company does not need it, remove it.
Can it be merged? Two consecutive steps done by two different people can often be done by one.
Can it run in parallel? Some steps do not depend on each other, so there is no need to wait for one to finish before starting the other.
Is the decision in the right place? Move the approval to the nearest person who has the information, and set a clear limit for what needs senior management.
Are the inputs complete from the start? One clear form at the beginning of the process prevents most cases of rework later.

Then try the new process on a small scale, one branch, one team or one type of order, for two or three weeks. Collect feedback from the people running it, and adjust what is needed before rolling it out. A team that takes part in designing the process is less likely to resist it, because it sees a solution to its own problems rather than new orders from management.

How to write the new process as a standard operating procedure

A process that is not written down gradually returns to what it was, especially when staff change. A written standard procedure is what turns the improvement from one enthusiastic person's effort into a way of working for the whole company, and it makes training any new employee faster and clearer.

A good procedure is short and practical, and usually includes these elements.

The purpose of the procedure and its scope, where it starts and where it ends.
Roles and responsibilities, and who owns and updates the procedure.
The steps in order, each with its owner, its expected duration and its output.
The forms and systems used at each step.
The checkpoints that ensure quality before moving to the next step.
One or two indicators that measure the performance of the process.
A change log with the date of each version.

You can start from the free standard operating procedure SOP template, which includes a table of steps with the owner, timing and output, a quality checklist, and a log of versions and changes. Write the procedure in the language of the people who will follow it, not in consultants' language, and put the new swimlane map at the top, because a picture saves pages of explanation.

Why you should automate only what has settled

Only now does technology come in. Once the new process has run steadily for several weeks and you are sure the team follows it, it becomes clear which steps repeat in the same way every time and which steps need human judgment. The first kind are the candidates for automation.

Steps that are usually automated with a quick return include notifying the next person when a transaction reaches them, routing approvals by value or type, moving data between systems instead of retyping it, reminders for appointments and amounts due, and preparing periodic reports automatically. As for steps that still change every week, automating them now means you will pay to modify them again and again.

So the right order is three steps, simplify, then standardize, then automate. At that point the kind of system you really need becomes clear, and it may be much simpler than you imagined at the start. In our systems and digital transformation service we always begin by mapping the work cycle before proposing any system, whether ready-made or custom-built.

How to measure the results after 30 and 90 days

An improvement that is not measured is forgotten. So before the launch, set two review dates, and use the same measures you collected at the start so the comparison is fair.

After 30 days

The first question here is about adherence, not results. Is the team really working with the new procedure, or have some gone back to the old way? Where are the exceptions the design did not cover? Review a sample of transactions, listen to the people running the process, and adjust the procedure where needed. It is normal for some problems to appear in the first month. What matters is that they are fixed quickly before they become an excuse to go back to the old way.

After 90 days

Now compare the figures with the starting figures. How much did cycle time and waiting time fall? How much did the rework rate drop? Have customer complaints related to this process declined? How many hours a week have the team and management won back? Then write what you learned on one page and decide on the next process. The real value does not come from improving one process, but from this way of working becoming an established habit in the company.

How to start with Reform

If you are not sure which process to start with, that is exactly what we do in the free diagnosis session. In ninety minutes we review with you how work moves through your company and identify the process with the greatest effect on your time and your results, and you then receive a written summary of recommendations and first steps.

Book the free diagnosis session on WhatsApp

To see what the service covers, visit the business development and digital transformation page, or read the full picture in the guide to digital transformation for companies.

Frequently asked questions about operational process improvement

What does operational process improvement mean?

It means reviewing the way work moves through the company, from the first request to the last step, then removing whatever adds no value and rearranging the rest, so the same work is done in less time, with fewer errors and with less effort from the team.

Why should the process be improved before buying a new system?

Because a system runs the process as it is. If the process has extra steps, waiting and rework, the system will run them faster but will not remove them. Improving the process first also shows what you really need from the system, so you choose a simpler and better fitting solution.

What is a swimlane map and how do I draw one?

A swimlane map is a simple diagram with one row for each role involved in the process. Each step is placed in the row of whoever performs it, and arrows connect the steps in order. The map clearly reveals the handoffs between people and the points of waiting and decision.

What are the most common types of waste in office work?

Waiting for approvals, entering the same data more than once, too many handoffs between people, searching for information, rework caused by errors or missing details, and reports that are prepared and used by nobody.

When do the results of process improvement appear?

The first signs appear within the first month, in the form of team adherence and fewer exceptions, while the full comparison with the starting figures for cycle time and the rework rate usually becomes clear about 90 days after the launch.

Is the diagnosis session free?

Yes. The diagnosis session is free and lasts ninety minutes. We review your company's situation and identify the gaps and opportunities, and you then receive a written summary of recommendations with no obligation to continue with us. It can be held online from Egypt or the Gulf.

Mahmoud Saied

Founder and CEO of Reform Group. For more than ten years he has worked with companies in Egypt, Bahrain and Saudi Arabia on what decides their ability to grow, from teams and HR systems to marketing, digital transformation, and websites and apps.

All articles by the author and LinkedIn