Learning objective
By the end of this lesson, you can define an observable process boundary and connect outputs to customers before adding workflow detail.
Why it matters
“Customer onboarding” can begin at a verbal promise, signed order, paid invoice or complete configuration request. Each start creates a different denominator. Automation built on the wrong boundary can speed up one team while increasing missing-input work elsewhere.
Core concept: an operational contract
A useful SIPOC establishes:
- one unit of work;
- an observable start and end;
- four to seven major steps;
- outputs with named customers and requirements;
- required inputs with named suppliers.
The map is a contract about scope, not a claim that the process is good.
Visual explanation
Worked example
An account-provisioning team says the process starts when Sales submits a request. A real case shows that requests arrive without verified billing status or integration settings. The team changes the start event to “signed scope, verified billing and accepted configuration available.” The main output becomes a verified workspace that completes the first core task—not merely an account record.
The next detailed map can now measure waiting and exceptions using a stable boundary.
Common mistake
Mistake: filling the process column with departments or thirty activities.
Keep major steps at one level. Use a detailed process or value-stream map after the boundary is agreed.
Quick check
What is the strongest SIPOC start event?
A. “Sales begins.”
B. “A complete, accepted order package enters the provisioning queue.”
C. “The customer is interested.”
D. “The automation runs.”
Answer: B. It is observable and defines what valid work enters the process.
Practical prompt
Choose one recurring process. Write its unit, observable start, observable end, primary output and the customer acceptance condition.
Summary
- Agree boundaries before detail.
- Connect outputs to real customers and requirements.
- Connect required inputs to suppliers.
- Validate the map with normal and exception cases.
Next lesson
Use Value Stream Mapping to measure flow inside the agreed boundary, then FMEA or Bow-Tie Analysis for material failure and control scenarios.