Study guide
SIPOC & Process Inputs/Outputs
ASQ Certified Six Sigma Green Belt CSSGB
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
CSSGB Exam Facts & Logistics How to Study for an Open-Book ASQ Exam
2 Six Sigma Foundations
Value of Six Sigma & Quality Leaders Organizational Goals & Six Sigma Projects Organizational Drivers, KPIs & Scorecards
3 Lean Principles in the Organization
Lean Concepts Value Stream Mapping & Waste
4 Design for Six Sigma
DFSS Road Maps: DMADV & IDOV FMEA Basics & Risk Priority Number Design FMEA vs Process FMEA
5 Define: Project Identification
Project Selection & DMAIC Fit Process Elements & Boundaries Benchmarking Types SIPOC & Process Inputs/Outputs
6 Stakeholders & Voice of the Customer
Owners & Stakeholders Customer Identification Customer Data Collection CTQ, QFD & Kano
7 Project Management Core
Agile & Top-Down Project Methods Project Charter & Problem Statements Project Scope Tools Primary & Consequential Metrics
8 Planning, Risk & Closure
WBS, Gantt, CPM, PERT & Tollgates Project Documentation Project Risk Analysis & Management Project Closure & Lessons Learned
9 Management Tools & Business Results
Eight Management & Planning Tools DPU, RTY, CoPQ, DPMO & Sigma Level Organizational Communication
10 Team Dynamics & Performance
Team Stages & Negative Dynamics Six Sigma Roles & RACI Brainstorming, NGT & Multivoting Team Communication
11 Measure: Process & Probability
Process Maps & Documentation Basic Probability Concepts Central Limit Theorem
12 Distributions & Data Collection
Statistical Distributions Data Types & Measurement Scales Sampling & Data Collection Plans Descriptive Statistics
13 Graphical Methods & MSA
Graphical Methods Measurement System Analysis & Gage R&R Bias, Linearity, Stability & P/T
14 Process & Performance Capability
Process Performance vs Specifications Process Capability Studies Cp, Cpk, Pp, Ppk & Cpm Short-Term vs Long-Term Capability & Sigma Shift
15 Analyze: Exploratory Data Analysis
Multi-Vari Studies Correlation & Linear Regression
16 Hypothesis Testing
Hypothesis Testing Basics Tests for Means, Variances & Proportions
17 Gap & Root Cause Analysis
Gap Analysis Root Cause Analysis Tools
18 Design of Experiments
DoE Basic Terms Main Effects & Interaction Plots
19 Implementation Planning & Lean Tools
Implementation Planning & Pilots Waste Elimination Tools Cycle-Time Reduction & SMED Kaizen & Kaizen Blitz
20 Statistical Process Control
SPC Basics: Common vs Special Cause Rational Subgrouping Control Chart Selection & Construction
21 Sustaining Improvements & Lean Control
Control Plans Document Control, Training & Audits Plan-Do-Check-Act (PDCA) TPM & Visual Factory
SIPOC & Process Inputs/Outputs
Key Takeaways Explain This Topic AI
SIPOC stands for Suppliers, Inputs, Process, Outputs, Customers—a high-level Define tool that scopes the process before detailed mapping.
Build SIPOC from the middle: name 5–7 high-level process steps, then outputs and customers, then inputs and suppliers.
Inputs and outputs include materials, information, and decisions; relate critical inputs (X’s) to key outputs (Y’s) the project will measure.
A good SIPOC clarifies boundaries, stakeholders, and data sources and feeds the charter, VOC work, and later process maps.
SIPOC is not a value-stream map or a root-cause tool; it is a shared picture of scope and I/O relationships at the start of DMAIC.
Last updated: July 2026
SIPOC & Process Inputs/Outputs
Quick Answer: A SIPOC maps S uppliers, I nputs, P rocess, O utputs, and C ustomers at a high level. Green Belts use it in Define to set boundaries, list I/O variables, and show how suppliers and inputs drive outputs customers care about—before diving into detailed process maps or data collection.
Why SIPOC Matters in Define
After you select a project and draft process boundaries, the team needs a one-page shared model of the work system. SIPOC provides that model. CSSGB BoK II.A.4 expects you to analyze SIPOC relationships: which inputs feed the process, which outputs matter, who supplies and who receives.
SIPOC helps you:
- Confirm start/stop and in-scope steps (usually 5–7 macro steps)
- Identify stakeholders (suppliers and customers) for VOC and RACI later
- List candidate X’s and Y’s for the measurement plan
- Expose missing inputs (no spec, no training, no system signal) that already hint at risk
- Prevent detailed mapping of the wrong process
SIPOC is deliberately high level . If your “process” column has thirty micro-steps, you built a flowchart, not a SIPOC.
The Five Columns
- Column Definition Examples
- Suppliers Entities that provide inputs Vendors, upstream depts, customers (who supply info), systems
- Inputs What is transformed or consumed Materials, data, requests, energy, policies, partial assemblies
- Process Macro steps from start to stop 5–7 action phrases in sequence
- Outputs What the process produces Products, services, decisions, reports, waste streams
- Customers Who receives outputs External buyers, next process, regulators, employees
Relationships to remember:
- Suppliers → provide → Inputs
- Inputs + Process resources/controls → produce → Outputs
- Outputs → go to → Customers
- Customers often also act as suppliers of information (requirements, applications, samples)
Critical-to-quality outputs become project Y candidates. Critical inputs become X candidates for Measure/Analyze. Not every row is “vital few,” but SIPOC is where the inventory starts.
How to Build a SIPOC (Recommended Order)
Many teams fail by listing suppliers first without agreeing what the process is. Use this order:
Name the process and boundaries — Start event / stop event.
Draft Process column — 5–7 high-level steps in verb-noun form.
List Outputs — What exits each end state? Include primary product/service and key information outputs.
List Customers — Internal and external receivers of each major output.
List Inputs — What must enter for the process to run correctly?
List Suppliers — Who provides each input?
Validate with the process owner and team — Walk a real unit of work against the SIPOC.
Link to metrics — Circle the output(s) that define project Y; note consequential outputs.
- Quality checks
- Every major output has at least one customer
- Every major input has at least one supplier
- Process steps are sequential and stay inside the boundary
- Exception paths are acknowledged (or parked as out of scope)
- Language is operational, not slogan-like (“deliver excellence”)
- Input/Output Variable Thinking
Six Sigma models Y = f(X). SIPOC makes that concrete:
- Concept SIPOC home Project use
- Y (output variable) Outputs column Primary metric, CTQ
- X (input / process variable) Inputs + process settings/resources Factors to measure and improve
- Noise Uncontrolled inputs Stratify or error-proof later
- Specifications Requirements on inputs/outputs Defect definitions
Classify I/O for the measurement plan:
- Controllable inputs — Machine settings, staffing model, checklist use
- Uncontrollable but measurable inputs — Ambient humidity, customer-provided document quality
- Standardized inputs — Approved materials, validated forms
- Outputs to protect — Consequential metrics (safety, cost, service) even if not primary Y
Example relationship statements (Define quality):
“Incomplete customer applications (input from Customer-as-supplier) increase underwriting cycle time (output Y).”
“Incorrect BOM revision (input from Engineering) increases assembly rework (output).”
These are hypotheses to verify later—not yet proven root causes—but they prove the team understands I/O linkage.
- Worked Example A — Service Process: Small-Business Loan Decision
- Process name: Consumer-light business loan underwriting (Region West)
- Start: Complete application package received in LOS
- Stop: Decision recorded (Approve / Decline / Conditional)
Suppliers Inputs Process (macro steps) Outputs Customers
Applicant (customer) Application form, IDs, financials 1. Receive & completeness check Completeness status Underwriting team
Credit bureau Credit report, scores 2. Pull credit & risk data Credit file package Credit analysts
Core banking system Relationship history, existing exposure 3. Analyze credit & capacity Risk assessment notes Underwriter
Credit policy team Policy rules, scorecards 4. Apply policy & decide Approve / Decline / Conditional decision Applicant; Sales
Sales / RM Clarifications, collateral info 5. Communicate decision & conditions Decision notice; condition list Applicant; Closing team
Training / QA Desk aids, sampling rules 6. File & QA sample Archived file; QA flags Compliance; Ops QA
Project Y candidates from Outputs: median hours from complete package to decision; % decisions reversed in QA; % packages returned for incompleteness (could be consequential or a leading Y).
Critical input relationships: Document completeness and credit-data latency heavily influence cycle-time Y. SIPOC shows Sales and the applicant as suppliers of completeness—so the project boundary debate (include pre-complete intake or not) becomes explicit.
- Worked Example B — Manufacturing Process: Carton Pack-Out
- Process name: Finished-goods pack-out for SKU Family A
- Start: Pallet of units released from final test
- Stop: Labeled carton staged at shipping dock door
- Suppliers Inputs Process Outputs Customers
- Final test Passed units, test record 1. Receive & verify count Accepted unit lot Pack operators
- Warehouse Cartons, dunnage, labels 2. Select pack configuration Pack kit Pack station
- Planning / ERP Pack BOM, ship order 3. Pack & void-fill Packed carton Labeling
- Label system Label data, printer 4. Label & scan Labeled, scanned carton Shipping
- Quality Pack audit checklist 5. Stage to door Staged carton; scan event Shipping / Customer
- Maintenance Working tape machines (resource) — Pack team
I/O insight: Wrong label data (input from system/order) creates mis-ships (output defect) even if packing is neat. A Green Belt targeting “damage in transit” might circle void-fill and carton strength inputs; a Green Belt targeting “mis-ship” circles label data and scan compliance.
SIPOC vs. Related Tools
- Tool Level Purpose
- SIPOC Macro Scope, I/O, suppliers/customers
- Process map / flowchart Mid/detail Sequence, decisions, rework loops
- Value stream map Flow + time Lead time, inventory, value vs. waste
- Turtle diagram Elements Enablers: who, with what, measures, how
- Project charter Narrative Problem, goal, scope, team—fed by SIPOC
Use SIPOC first; detailed maps later in Measure/Analyze as needed.
- Common SIPOC Mistakes
- Too much detail in the Process column
- Missing internal customers at handoffs
- Listing solutions as process steps (“implement new software”)
- No boundary events — steps float without start/stop
- Outputs without customers or inputs without suppliers
- Treating SIPOC as complete root-cause analysis
- One person builds it alone — loses cross-functional truth
- Green Belt Checklist
- Process name, start, and stop are written above the SIPOC
- 5–7 macro process steps only
- Suppliers and customers include internal parties
- Inputs and outputs cover material and information
- Primary Y maps to a specific output
- At least a few critical I/O relationships are stated in words
- Team and process owner validated against real work
- SIPOC aligns with charter scope and feeds the data collection plan
A solid SIPOC is the handshake between project selection, process boundaries, and everything that follows in DMAIC. Master the columns, the build order, and the I/O relationships, and Define becomes concrete instead of abstract.