What is it?
A SIPOC is a simple way of seeing the boundaries of a process before diving into the detail. It helps everyone agree where the work begins, where it ends, what flows through it and who depends on the outcome.
What's it really for?
There is something oddly reassuring about drawing five boxes before anyone starts mapping the process. It feels almost too simple, until you realise half the room was not talking about the same process in the first place.
You know when…
The whiteboard is already half full when somebody asks where the process actually begins. The room goes quiet. Three different answers arrive almost immediately, all delivered with complete confidence.
It turns out everyone has been improving a different process.
Have a go
- Agree where the process begins and ends.
- Write five to seven high-level process steps.
- Add the inputs and the suppliers that provide them.
- Identify the outputs, the customers and what they need.
Why it works
When people describe a process, they usually start somewhere different. One person begins with the customer, another with the first email, and someone else with a meeting that happened three weeks earlier. A SIPOC quietly solves that problem by giving everyone the same frame of reference. Once the boundaries are visible, the conversation becomes much easier because people are finally talking about the same piece of work.
Look for…
Pay attention to the conversations around the edges. Disagreement about where something begins or ends usually points to an opportunity. Also notice whether customers receive what they need, or simply what the process happens to produce.
Watch out…
A SIPOC is not meant to contain every task, decision and exception. If it begins to resemble a railway timetable, you have probably wandered into process mapping. Keep it at the level where the whole system can still be understood at a glance.
Worth noticing…
Most processes do not become complicated because the work is complicated. They become complicated because nobody agrees where they begin.
Try next…
Use a Process Map when the team is ready to follow the work in more detail. Use a Value Stream Map when delay, waiting or flow has become the more interesting question.