Insights

SIPOC diagram: how to build one, with a template and example

A SIPOC gives a team one agreed picture of a process before anyone tries to fix it. Here is what each column means, how to run the workshop, a template to copy and a worked order to cash example.

By Christopher Fagan, Managing Partner, PEF Consulting Partners

£13bnlargest programme delivered
19 yrssenior systems delivery
5 continentsdelivered across
£25msaving on a single programme

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

SIPOC stands for suppliers, inputs, process, outputs and customers. It is a one page table that maps a process at a high level: who provides what, the five to seven main steps, what comes out and who receives it. Teams use it to agree a process’s scope and boundaries before measuring or improving it.

It is deliberately simple, and that is the point. Many process problems start with people describing the same process in different ways, and a single shared map makes those differences visible in an hour rather than three weeks into a project.

What a SIPOC diagram is for

Before anyone measures a process, automates it or outsources it, they need to agree what the process is. Where does it start and stop? Who feeds it, and who depends on what it produces? Those questions sound basic, but the first workshop on an improvement project often reveals that finance, operations and IT each have a different answer.

The diagram gives everyone the same frame. It is short enough to fit on one slide, so a sponsor can read it, and structured enough to show where the handoffs and dependencies sit. It also tells you who needs to be in the room for the next stage of the work.

Suppliers, inputs, process, outputs, customers: the five columns

  • Suppliers. Whoever provides the inputs. They can be external, such as a customer placing an order or a carrier, or internal, such as the sales team or another system.
  • Inputs. The information, materials or decisions the process needs to start and run, such as an order, a price list, a credit limit or stock.
  • Process. The main steps, usually five to seven, each written as a verb and a noun, such as ‘check credit’ or ‘issue invoice’. This is the spine of the process, not the detailed map.
  • Outputs. What the process produces: a delivered order, an invoice, a payment matched to the right account.
  • Customers. Whoever receives the outputs. That means the paying customer, but also internal customers such as the finance team, the auditors or a regulator.

Many teams add requirements next to the inputs and outputs, describing what good looks like for each. An invoice is an output; an invoice that is accurate, on time and matches the delivery note is a requirement. That extra detail is where improvement targets usually come from.

Where it comes from: Six Sigma and the define phase

The technique is usually traced to the total quality management movement of the late 1980s. Six Sigma later made it a standard tool in the define phase of DMAIC, the cycle of define, measure, analyse, improve and control. In define, the team agrees the problem, the process and its boundaries before collecting any data, and a one page map from suppliers to customers is the quickest way to get there.

You do not need a Six Sigma programme to use it. It works just as well at the start of a system implementation, a shared service design or an outsourcing decision, anywhere people need to agree on a process before they change it.

How to build one in a workshop

A first version takes about an hour with the right people: someone who does the work, someone who receives the output and whoever owns the process. Work through it in this order.

  1. Name the process and set its boundaries. Agree the event that starts it and the event that ends it. ‘From customer order received to cash allocated’ is a boundary; ‘sales’ is not.
  2. Map the process steps first. Five to seven high level steps, verb and noun. Resist detail at this stage.
  3. List the outputs of those steps, then the customers who receive each one.
  4. List the inputs each step needs, then the suppliers who provide them.
  5. Add requirements where you can. What does each customer need from each output, and what does the process need from each input?
  6. Test it with people who were not in the room. A supplier or customer who disagrees with their row has told you something useful.

Starting in the middle, with the process, is the usual advice because it anchors the conversation. Some teams prefer to start from the customer and work backwards, a variant sometimes called COPIS, which keeps attention on what the customer actually receives. Either order works, as long as the map gets finished.

A SIPOC template you can copy

Above the table, write one line that sets the boundary: this process starts when a named event happens and ends when another does. Then fill in the process column first, work outwards to outputs and customers, and finish with inputs and suppliers.

SuppliersInputsProcessOutputsCustomers
Who provides each input? Internal teams, external organisations or systemsWhat the process needs to start and run, and what good looks like for eachFive to seven main steps, verb and noun, from the agreed start to the agreed endWhat the process produces, and what good looks like for eachWho receives each output, internal and external
Supplier 1Input 1Step 1 (start)Output 1Customer 1
Supplier 2Input 2Step 2Output 2Customer 2
Supplier 3Input 3Step 3Output 3Customer 3
Supplier 4Input 4Step 4Output 4Customer 4
Supplier 5Input 5Step 5 (end)Output 5Customer 5

The rows do not need to line up. Each column is a list in its own right, and one supplier can provide several inputs or one output can go to several customers.

SIPOC example: order to cash

This worked example is hypothetical: a building products wholesaler selling on account to trade customers. The boundary runs from a customer order being received to the cash being allocated against the invoice. For a fuller description of the process itself, see our guide to order to cash.

SuppliersInputsProcessOutputsCustomers
Trade customerPurchase order with items, quantities and delivery address1. Receive and enter the orderConfirmed sales orderTrade customer
Sales teamPrice list and agreed discounts2. Check credit and price the orderOrder released or heldWarehouse
Credit controlCredit limit and account status3. Pick, pack and despatchDelivery note and despatched goodsTrade customer
WarehouseAvailable stock4. Deliver and capture proof of deliverySigned proof of deliveryFinance team
CarrierProof of delivery5. Raise and send the invoiceAccurate invoiceTrade customer
Customer’s bankPayment and remittance advice6. Collect paymentPayment receivedFinance team
7. Allocate cash and chase overdue accountsCash allocated, aged debt reportCredit control, management accounts, auditors

Even at this level, the map raises useful questions. Credit control appears at both ends: it supplies the credit limit at the start and receives the aged debt report at the end, so if that report is late or wrong, tomorrow’s credit decisions are made on stale data. Invoicing depends on proof of delivery coming back from the carrier, and when that input is slow or incomplete, invoices wait and so does the cash. Those two points are where a team would start measuring.

The same map for meter to bill

The approach transfers well to an energy supplier’s meter to bill process, and the differences are instructive. Suppliers include industry parties as well as internal teams: metering and data services, industry registration systems and the pricing team. Inputs are meter readings or half hourly consumption data, tariffs and rates, and customer account details. The process runs from reads received, through validation and estimation, to bill calculation, exception review and issue, and the outputs go to collections, finance and regulatory reporting as well as to the customer.

What a meter to bill map usually exposes is how many inputs arrive from outside the supplier’s control, and how much of the process exists to cope with inputs that are late, missing or wrong. That exception handling is where cost and complaints build up. To put a number on it, try the billing exception cost calculator, and for background on the process, read energy billing explained.

Billing is also where weak handoffs turn into money. Christopher Fagan led the recovery of a £160m+ billing imbalance that surfaced at a Big Six energy supplier once its Kraken migration was live, and problems on that scale are rarely visible from inside any one team, which is exactly why a shared view of the whole process matters.

When to use it and when not to

Use it at the start of any process improvement, system implementation or outsourcing decision, whenever people need to agree which process they are talking about. It is particularly useful when a process crosses several teams or organisations, because nobody owns the whole of it and each team sees only its own part. It also makes a good first artefact for a newly appointed process owner.

It is the wrong tool when you need detail. It will not show decision points, rework loops, waiting time or who does each step; for that you need a swimlane process map. Nor will it diagnose causes. Once the map has shown where the problem sits, a fishbone diagram or a wider root cause analysis is the natural next step.

Common mistakes

  • Too much detail. Twenty process steps means you have drawn a process map in the wrong format. Keep to five to seven and park the rest.
  • Vague boundaries. If the start and end are not agreed, scope arguments will run for the rest of the project.
  • Only external customers. Internal customers, such as finance, auditors and the regulator, often have the strictest requirements.
  • Inputs with no supplier. An input nobody is named as providing is an input nobody is accountable for.
  • Drawn by one person at a desk. The value comes from the disagreement in the room. A map drawn alone just records one view.
  • Filed and forgotten. The map should frame the measures, the improvement scope and the process ownership that follow.

Where it fits in wider process improvement

A one page map opens the work rather than closing it. It frames the measurement and analysis that follow, it helps define process ownership in a new operating model and it shows where a process meets its neighbours, such as procure to pay on the supply side. At a higher level, a value chain analysis shows how the main processes of a business fit together and which of them matter most to cost and competitive position.

Our operational excellence work often starts with exactly this kind of shared picture. The difference is what happens next: we stay to redesign the process with your team and build the change into systems and ways of working, rather than handing over a map and leaving.

Common questions

What is a SIPOC?

A SIPOC is a one page, high level map of a process. The letters stand for suppliers, inputs, process, outputs and customers. It lists who provides what to the process, its five to seven main steps, what it produces and who receives the results. Teams use it at the start of improvement or system projects to agree the scope and boundaries of a process.

What does SIPOC stand for?

SIPOC stands for suppliers, inputs, process, outputs and customers. Suppliers provide the inputs, the process turns them into outputs through a handful of main steps, and customers receive the outputs. Many versions also record requirements for the inputs and outputs, describing what good looks like. Read in reverse, starting from the customer, the same tool is sometimes called COPIS.

How do you create a SIPOC diagram?

Agree the name and boundaries of the process first: what starts it and what ends it. Then list five to seven high level steps, followed by the outputs and the customers who receive them, then the inputs and the suppliers who provide them. Add requirements where you can, and test the draft with people who supply or receive the process but were not in the workshop.

Is SIPOC part of Six Sigma?

Yes. SIPOC is a standard tool in the define phase of the Six Sigma DMAIC cycle, where a team agrees the problem, the process and its boundaries before collecting data. It is usually traced back further, to the total quality management movement of the 1980s, and it is widely used outside Six Sigma in lean, process redesign and system implementation work.

What is the difference between a SIPOC and a process map?

A SIPOC is a scoping tool. It shows a process in five to seven steps, with its suppliers, inputs, outputs and customers, on one page. A detailed process map, usually drawn in swimlanes, shows every step, decision, handoff and loop, and who does each one. Most teams build the SIPOC first and use it to decide which part of the process to map in detail.

Related reading: Fishbone diagram, Root cause analysis, Order to cash explained and Operational excellence.

Need an outside view of a broken process?

We can run the mapping workshop with your team, find where the handoffs fail and help you fix them in the process and the system, not just on paper.

Book a confidential conversation

Sources: Pande, P. S., Neuman, R. P. and Cavanagh, R. R., The Six Sigma Way, 2000; George, M. L., Rowlands, D., Price, M. and Maxey, J., The Lean Six Sigma Pocket Toolbook, 2005

PEF TRACK RECORD£13bnLargestprogramme led5Continentsdelivered across19 yrsSystems delivery£25mLargestsingle saving
CF

Written by Christopher Fagan

Managing Partner, PEF Consulting Partners

Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.