When a BPO team is told to “map the process”, it usually opens a flowchart tool and starts drawing boxes. Two hours later there are sixty shapes and no agreement on what the process even is. My view, and I will argue it, is that most teams should draw a SIPOC first and a swimlane map second, and that the reverse order explains a lot of wasted workshops.
What each one shows
A process map is a picture of how work moves from a start to an end. Both of these are process maps, but they sit at opposite ends of detail.
SIPOC stands for Suppliers, Inputs, Process, Outputs, Customers. It is a table of five columns, the process column holding only four to seven high-level steps. It says who gives us what, what we do in broad terms, and what we hand to whom. A swimlane map is a flowchart divided into horizontal lanes, one per role or team (agent, team leader, back office, client), so you can see every step, every decision and every hand-off, and who owns each one.
Take an invoice-processing desk in a finance back office. The SIPOC might read: suppliers are vendors and the client’s procurement team; inputs are invoices, purchase orders and goods receipt notes; process is receive, validate, match, route for approval, post, pay; outputs are posted invoices and payment advice; customers are the client’s finance controller and the vendor. Five minutes of reading and you understand the shape of the work.
The case for starting with SIPOC
First, it forces agreement on boundaries. Where does this process start, where does it end, who is the customer? Teams are often surprised to discover that two managers have different answers. A swimlane drawn on top of that disagreement will bake it in.
Second, it surfaces the edges, which is where problems hide. Many failures happen at the input: invoices arriving without a purchase order number, forms with missing fields. The supplier and input columns make you ask what quality of input you are promising to accept and whether anyone has told the supplier. A detailed internal flowchart tends to focus on what we do, and quietly assume the inputs are fine.
Third, it is cheap. It can be built in a single meeting with the people who run the work, and even a senior person can read it in a minute. That matters when you are explaining a process to a new client, a new manager, or an auditor.
The case for the swimlane
The counter-argument deserves a fair hearing. SIPOC is too high-level to find waste. It cannot show that an invoice waits two days in an approver’s queue, or that three people each re-key the same field. The swimlane makes hand-offs visible, and hand-offs are where delay and error concentrate. In a swimlane you can count the times work crosses a lane. If a single invoice crosses six lanes, you have found an investigation. It also documents decision points: what happens when the amount does not match the purchase order? Who may approve a variance, and up to what value?
For transitions, a swimlane is nearly essential. When a process moves from one location to another, the receiving team needs to know exactly who does what at each step. A SIPOC will not carry that.
Where I land
Draw the SIPOC first, every time. It is an investment of an hour that makes the next ten hours more productive. Then draw the swimlane, but only for the part of the process that matters: the stretch where the problem lives, not the entire end-to-end flow. A full-process swimlane for a thirty-step process is a wall poster that nobody reads.
There is an honest exception. If the process is already well understood and the question is purely about waste or delay, going directly to a swimlane, perhaps with time stamps on each step, can be faster. And in a regulated process where an auditor expects documented steps, the swimlane is not optional.
Drawing either one honestly
The largest mistake in both is mapping the process as it is supposed to work, not as it does. Sit with the people doing the work, or watch them. Ask what they do when the system is down or the form is incomplete. Those workarounds are part of the real process, and they are often where the time goes. Two other habits help: label the steps with verbs (“validate invoice”, not “validation”), and write down roughly how long each step takes and how long work waits between steps. Waiting time is frequently several times larger than working time, and a map that omits it flatters the process.
One last practical note. A process map is a working document with a shelf life. If nobody updates it after the next system change, it turns into a historical drawing. Give the map an owner and a review date, or accept that you will be drawing it again next year.
Figures and names in the examples are illustrative.
Leave a Reply