Sipoc
Sipoc
Sipoc
What is SIPOC?
SIPOC is an abbreviation of:
It provides a “template” for defining a process, before you begin to map, measure, or improve it.
It provides a structured way to discuss the process and get consensus on what it involves before
rushing off and drawing process maps.
1. Agree the name of the process. Use a Verb + Noun format (e.g. Recruit Staff).
2. Define the Outputs of the process. These are the tangible things that the process produces
(e.g. a report, or letter).
3. Define the Customers of the process. These are the people who receive the Outputs. Every
Output should have a Customer.
4. Define the Inputs to the process. These are the things that trigger the process. They will
often be tangible (e.g. a customer request)
5. Define the Suppliers to the process. These are the people who supply the inputs. Every
input should have a Supplier. In some “end-to-end” processes, the supplier and the
customer may be the same person.
6. Define the sub-processes that make up the process. These are the activities that are carried
out to convert the inputs into outputs. They will form the basis of a process map.
SIPOC Example:
Above is a simplified example of a SIPOC. In practice, you may need to include several other
suppliers (e.g. Candidates, Recruitment Agencies) and other customers (HR Dept., Candidates).
Include a Process Purpose statement. Define why the process exists; e.g. the recruit Staff process
exists to provide the right people, with the right skills at the right time. The purpose should reflect a
benefit to the organisation, not simply be a re-statement of the name of the process.
Identify the Process Owner. Decide who is the single, named individual with responsibility for the
end-to end process. That person needs to be involved in any definition and improvement activities.
Define the start and end-points of the process. These will be the first and last activities on the
process map. Note that some processes may have multiple start and end points.
Define any boundaries, or scope limitations for the process. For example, does the process deal
with all types of customer, or just some (e.g. Retail vs. Business Customers)? Or, does the process
only deal with a particular type of transaction (e.g. high risk vs. low risk)? These boundaries can
help you decide whether you need more than one process map, or if everything can be included in
one map.
Getting it right:
To be useful, your SIPOC process definition needs to follow the basic steps listed above. There are
some common errors that people make when defining a process. Here’s how to avoid them…
SIPOC Summary
Sub-process Process
Policies steps Purpose
& Rules
Input Output
Process Name
(Verb + Noun)
Suppliers Customers
Process Owner
Staff & Resources
Process:
Purpose:
Owner:
Boundaries:
Start-point: End-point:
Includes: Excludes: