Opening the book…
Begin with the current process. Create a SIPOC with people who perform the work and people who supply or receive its outputs. A supervisor may know the procedure, while an analyst knows where submissions wait. Compare their accounts with observation and records. Keep a proposed future process separate so that an intended improvement is not mistaken for current practice.
1. State the process purpose and the question being investigated.
2. Agree on the starting and ending events.
3. Describe the process in a few major steps.
4. Identify the outputs and the customers who use them.
5. Confirm what those customers require.
6. Identify the necessary inputs and their suppliers.
7. Check the map against actual work and revise it with the people involved.
The following completed SIPOC summarizes the hypothetical enzyme testing process. The columns describe the same overall process; entries at the same height are not separate pathways. The normal sequence is shown in the process column. The exception output represents formal closure when testing cannot proceed, rather than an informal message while a submission remains open.
Process boundary: first receipt of a submitted sample through issue of a reviewed report or formal closure notice. Purpose: provide reviewed test information for a batch decision, or clearly document why the requested testing could not be completed. A passing report supports review; it does not automatically authorize shipment.
Read the map by checking relationships. Does each important input have an identified supplier? Does each output have a customer? Does the process produce what that customer needs? A missing entry can signal unclear responsibility or a requirement that has never been discussed.
For example, production supplies the sample and request; materials support provides reagents; document management supplies the current approved method. The authorized batch decision maker receives the report, while production receives relevant follow-up or closure information. These connections explain the lists in the five-column map.
Suppose an initial draft omits the test request. Adding it identifies information the laboratory needs; it does not establish why requests are missing. Compare actual submissions with the approved requirements and investigate the conditions associated with the gaps.
SIPOC does not show every task, decision, exception, or possible cause of failure. It also does not prove that a process is controlled or that a supplier performs well. A detailed flowchart, direct observation, and reliable records may be needed next. The map guides the investigation; evidence supports the conclusions.
Measure different outcomes separately. Report turnaround describes submissions that produce reviewed reports. Closed or returned submissions need their own counts and reasons. Combining quick rejections with completed reports could make average completion time look better while fewer customers receive usable results.
This page titled 5.5: Creating and interpreting a SIPOC diagram was last modified on Fri, 06 Nov 2026 11:38:14 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by Emalee MacKenzie.
The book could not be loaded just now.