Defining boundaries, inputs and outputs with SIPOC
5 min read
Lesson objectives
Define process boundaries and supplier-input-output-customer links for a service request.
Reading tools
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
SIPOC summarises suppliers, inputs, process, outputs and customers. It is not an inventory of every employee movement. It helps a team agree on the journey's boundaries and the needs of its parties before detailed mapping. Set start and end events first. Then write four to seven high-level verb-and-object stages, such as receive request, check completeness, decide, fulfil and communicate. If the middle column needs dozens of steps or every exception, you are trying to force a detailed flowchart into a scope tool. If you put ‘purchasing department’ in the output column, you have confused the recipient with the thing delivered.
A supplier need not be a commercial vendor. An employee supplies a purchase request; a finance system may supply a budget code. A particular approval may also be a prerequisite. Describe an input with a testable acceptance condition: ‘a request with item description, quantity and cost centre’ is more useful than ‘a form’. Distinguish the final beneficiary from an internal receiver. Sourcing receives an authorised request, whereas the trainer who needs materials receives a fulfilment outcome or a reasoned rejection. This distinction prevents a map from ending at an internal handoff while the beneficiary's need is still open. Check the proposed columns with people at each stage; one document may omit a real handoff or required input.
Give each output a simple acceptance condition and someone who receives it. If the output is an approved purchase request, decide whether this completes the process being studied or becomes an input to a subsequent sourcing process. Do not merge the two by accident. A request missing required information returns for completion; it has not been fulfilled. A request outside scope may legitimately close if the reason is recorded and told to its originator. Owners, suppliers and beneficiaries may use ‘complete’ differently. Agreement about the closure condition matters more than a polished diagram. Treat SIPOC as a hypothesis to compare with case logs, not as proof that work actually follows the proposed stages.
Lesson summary
Defining boundaries, inputs and outputs with SIPOC: apply the method to case evidence and check the result and its limits.