Business Process Expert·9 min read
What is a SIPOC?
A SIPOC is a high-level summary of a process that identifies its Suppliers, Inputs, Process, Outputs, and Customers on a single page. The name is an acronym of those five columns, read left to right.
Its job is not to show every step. Its job is to define the scope and boundaries of a process so that everyone agrees on where it starts, where it ends, what it needs, and who it serves - before anyone spends time on a detailed process map. Think of it as the one-slide brief you agree on first.
What a SIPOC looks like
A SIPOC is a five-column grid. Each row is one thread through the process. Here is a recruitment example - read a single row across to see how a supplier feeds an input, which a process step turns into an output for a customer.
The Process column always holds only 5-7 high-level steps. Everything more granular belongs in the detailed map that comes after.
"The single most common mistake is stuffing twenty steps into the Process column. A SIPOC is a telescope, not a microscope. If you can't say the process in five to seven verbs, you've scoped too much - split it into two SIPOCs."
The five columns explained
S - Suppliers
The people, teams, systems, or organizations that provide the inputs. A supplier can be internal (another department, a database) or external (a vendor, the customer themselves). Ask: "Where does each input come from?"
I - Inputs
The materials, information, or resources the process consumes to do its work. An approved requisition, a completed form, raw materials, a signed contract. Inputs are what the process needs before it can run.
P - Process
The 5-7 high-level steps that transform inputs into outputs. Use verb-noun labels ("Screen candidates", "Make offer"). This is the deliberately coarse view - the point is scope, not detail.
O - Outputs
The products, services, or information the process produces. A shipped order, a filled role, an approved invoice. Outputs are what the process delivers - the reason it exists.
C - Customers
Whoever receives the outputs. Like suppliers, customers can be internal or external. The next team downstream, the paying customer, a regulator. Ask: "Who cares that this output was produced?"
Why SIPOC comes before detailed mapping
A detailed process map answers "how does this work, step by step?" A SIPOC answers the questions you must settle first: what is in scope, what is out, and who the process touches. Teams that skip it end up arguing about boundaries halfway through a mapping workshop.
In Lean Six Sigma, SIPOC is a standard deliverable of the Define phase of DMAIC. It sits next to the project charter and turns a fuzzy improvement idea ("fix recruiting") into an agreed scope ("the process from approved requisition to signed offer"). But you do not need a Six Sigma project to benefit - any team scoping a process can use it.
- -It fits on one page, so it is easy to get sign-off from stakeholders.
- -It surfaces suppliers and customers early - the parties most often forgotten.
- -It creates a shared vocabulary before the detailed work begins.
How to build a SIPOC
Counterintuitively, you do not fill in the columns left to right. Start in the middle and work outward - it is far easier to reason about.
Name the process (P)
Write the 5-7 high-level steps in the Process column first. This anchors everything else and forces you to agree on scope. If you cannot get it down to seven steps, your scope is too big.
List the outputs (O)
What does the process produce? Name the tangible results the last step delivers.
Identify the customers (C)
For each output, ask who receives it. That gives you the Customers column and a reality check on whether each output actually has a taker.
List the inputs (I)
What does the first step need to begin? Information, materials, approvals. These are your inputs.
Trace the suppliers (S)
For each input, ask where it comes from. That fills the Suppliers column and completes the picture. Read each row across to sanity-check it.
From scope to improvement
A SIPOC is where improvement starts. Once you can see the suppliers, inputs, steps, outputs, and customers on one page, you can decide where to focus: which handoffs are fragile, which inputs arrive late, which steps could become AI-assisted or automated.
From there you drop into a detailed process map of the steps worth changing, then design and document the fix. You can sketch that detailed view in the Crismo modeler for free.
Common pitfalls
Too much detail in the Process column
Keep it to 5-7 steps. Detail belongs in the map that follows, not the SIPOC.
Confusing inputs with suppliers
An input is the thing (a form, materials). A supplier is who provides it. Keep them in separate columns.
Forgetting internal customers
Customers are not only paying customers. The next team downstream is a customer of your outputs too.
Keep going
Frequently asked questions
What does SIPOC stand for?▼
SIPOC stands for Suppliers, Inputs, Process, Outputs, and Customers - the five columns of the diagram, read left to right.
What is a SIPOC used for?▼
A SIPOC scopes a process at a high level before detailed mapping. It defines where the process starts and ends, what it needs, what it produces, and who supplies and receives - so everyone agrees on boundaries first.
How many steps should the Process column have?▼
Five to seven high-level steps. If you need more, your scope is too broad - split it into two SIPOCs. Detail belongs in the process map that comes after.
In what order do you fill in a SIPOC?▼
Start in the middle. Name the Process steps first, then Outputs, then Customers, then Inputs, then Suppliers. Working outward from the process is much easier than left to right.
What is the difference between SIPOC and a process map?▼
A SIPOC is a one-page scope summary with only 5-7 steps. A process map shows the detailed, step-by-step flow including decisions and exceptions. SIPOC comes first and sets the boundaries.