Define submission pack

Learning objectives

• Assemble a complete Define submission pack.
• Show that problem, scope and success measure are unambiguous.
• Prevent embedded causes or solutions in the problem statement.

Required evidence

• Problem statement (what, where, when, how large, why it matters)
• Business and customer case
• VOC translated to CTQ and operational Y
• Scope and boundary with exclusions
• SIPOC and high-level process map
• Charter with team and RACI
• Stakeholder register
• Milestones and next-gate date
• Initial benefit estimate and top risks

Copy-friendly Define pack checklist

• Problem statement approved by sponsor
• Y and CTQ operational
• Scope, exclusions and guardrails signed
• SIPOC and map reviewed at gemba
• Stakeholder engagement plan
• Charter v1 frozen with date and approvers

Garment-factory example

A defect-repair charter names style family, lines, first-pass inspection point, defect-per-unit denominator, exclusions (sampling defects), baseline period and two guardrail metrics: output and ergonomic load.

Method

1. Draft problem statement in one sentence, remove causes and solutions.
2. Test scope by asking what is deliberately out.
3. Freeze v1 only after sponsor and process owner agree.

Common mistakes

• Percentage claims without a denominator.
• Financial promise before Measure validates baseline.
• Scope creep during Define itself.