A guided SIPOC and process-map builder for Lean Six Sigma Yellow Belt learners.
▶ Live tool: https://alfredang.github.io/sipoc/
Built for the WSQ course Certified Lean Six Sigma Yellow Belt (CLSSYB) Training (TGS-2025053922), Lab 3 — and the Case Study that assesses it.
Because draw.io already exists and is better at drawing things.
The point of this tool is that it knows the Lean Six Sigma rules and coaches you against them. It enforces the 5–7 step rule, uses the exact pain-point vocabulary the assessment marks against, generates the swimlane from your actor assignments rather than making you redraw it, and validates your work against the same checklist your lab uses.
Every feature exists to teach or enforce something. That is also why the symbol palette is deliberately limited to the six symbols the course teaches — a bigger palette invites decoration over method.
Enter Process → Outputs → Customers → Inputs → Suppliers. Working outward from the process is the discipline being taught; it stops you inventing inputs nobody actually uses. A Free edit toggle unlocks direct editing once you know the method.
The grid stays locked until you set an explicit start and stop point. Boundary disputes are where most SIPOCs fail, so the tool makes you agree them first.
- Fewer than 5 → "a SIPOC usually needs at least 5 steps"
- 5–7 → "good, this is the right level"
- 8+ → "drifting into a detailed process map — consider combining steps"
This is the single most common Yellow Belt error, so the feedback is prominent. It warns, never blocks.
Tag any process step with Waiting · Rework loop · Unclear ownership · Duplicate entry · Missing decision rule — the exact five categories the Case Study lists. A live counter tracks progress toward the required minimum of three.
Assign an actor to each step and the tool builds the swimlane automatically. A handoff is any point where consecutive steps change actor — these are detected for you, drawn as red arrows, and collected into a table that flags any handoff missing an owner on either side. That is exactly what Lab 3 asks you to check.
A flowchart using only the six taught symbols — terminator, process step, decision, flow, data, delay. Set a Delay and the tool suggests the Waiting pain point, because queues are where the waste hides.
Validates the same rules your lab and assessment are marked against, and tells you exactly what is missing:
- Process name, start and stop points set
- All five columns populated
- 5–7 process steps
- At least 3 pain points tagged
- Every handoff owned on both sides
PNG (2× resolution), PDF (via print), JSON save/load, and a shareable link that packs your whole SIPOC into the URL. Work autosaves to your browser as you go.
One click loads the Contoso Service Desk ticket-assignment SIPOC used in the course deck — a correct, complete reference that passes its own validation. Useful as a starting point, and as an instant demo for trainers.
Just open https://alfredang.github.io/sipoc/. No install, no sign-up, no account.
It is a single HTML file with no dependencies and makes no network requests — nothing you type leaves your browser, and it works offline once loaded.
| Tool | What it does |
|---|---|
| SIPOC & Process Map | This tool — Define phase |
| 5 Whys | Root-cause chain builder |
| Fishbone | Ishikawa cause-and-effect diagram |
| Pareto Chart | Collaborative brainstorm, vote and live chart |
| NovaSPC | Run charts, SPC charts, process capability |
Everything lives in index.html — HTML, CSS and vanilla JavaScript in one file. No build
step, no package manager, no framework. To work on it, open the file in a browser and edit.
Deployment is automatic: pushing to main triggers the GitHub Actions workflow in
.github/workflows/deploy.yml, which publishes to GitHub Pages.
See BUILD-INSTRUCTIONS.md for the full specification, including the rationale behind each feature and what was deliberately left out.
Powered by Tertiary Infotech Academy Pte Ltd