Define: Chartering, VOC, and Project Scope
Define: Chartering, VOC, and Scope
The Define phase fixes the project's reason, boundaries, and customer requirements before data collection. The ICBB exam tests whether you can turn a vague improvement idea into a charter with a measurable gap, a validated CTQ, and a SIPOC that exposes scope.
Core rules and concepts
- Problem statement: describe what, where, when, and magnitude; never name a cause or solution.
- Goal statement: baseline, target, and deadline; tie the target to customer or business impact.
- Scope: state process start/stop, in-scope products or lines, and explicit exclusions.
- Business case: quantify COPQ (scrap, rework, warranty, inspection, expediting) and link it to a strategic objective.
- VOC to CTQ: translate customer statements into measurable requirements with operational definitions and specification limits.
- SIPOC: list Suppliers, Inputs, Process (5-7 high-level steps), Outputs, Customers; use it to confirm boundaries.
- Roles: sponsor or champion removes barriers, process owner owns the post-project process, Black Belt leads, team members do the work.
Worked example
A claims team has 82% first-pass acceptance; rework costs $240,000 per year. The charter targets 95% first-pass acceptance by Q4, in commercial claims only, excluding Medicare. CTQ: a clean claim accepted on first submission, defined as no missing or invalid field and payer acceptance without rework. Reasoning: the 82% baseline makes the 13-point gap measurable; the exclusion prevents scope creep; the operational definition makes the CTQ auditable; COPQ justifies the project.
Traps that cost marks
Vague problem statements ('claims are bad'), goals without a baseline or deadline, causes embedded in the problem, scope that covers the whole enterprise, CTQs that are not measurable, skipping SIPOC, and a sponsor who never reviews the charter. A tollgate review should confirm charter, VOC/CTQ, SIPOC, team, and risk before Measure.