Before You Fix Anything: Getting the Define Phase Right
Lean Six Sigma improvement projects follow a five-step sequence known as DMAIC: Define, Measure, Analyze, Improve, Control. The phases are deliberately in that order, and the first one carries more weight than people expect. Define is where a team agrees on what problem it is solving, for whom, and how it will know when the work is done. Skip it or rush it, and everything downstream inherits the confusion.
In early 2022 this matters more than usual. With inflation pushing up costs, materials arriving late or not at all, and teams split between home and office, it is tempting to launch improvement efforts at every visible irritation. Define is the discipline that keeps you from chasing noise. It forces you to name a single problem worth the effort and to bound it before anyone starts measuring.
What the Define phase actually produces
Define is not a kickoff meeting and a slide. It produces a small set of artifacts that the rest of the project leans on. The centrepiece is the project charter — a one-page agreement that any sponsor, team member, or auditor can read and understand.
Problem statement. A factual description of what is wrong, when and where it happens, and its measurable impact. It names no cause and no solution — just the gap. "Invoice approvals take an average of 11 days against a 3-day target, costing roughly $40,000 a quarter in late fees," not "the finance team is too slow."
Goal statement. A specific, measurable target with a deadline. It should be ambitious but grounded — usually a meaningful reduction in the gap, not a vague "improve" or an impossible "eliminate."
Scope. What is in and, just as important, what is out. Pin the process boundaries to a clear start and end point so the work cannot quietly expand.
Voice of the customer (VOC). What the people who receive the output actually care about, translated into critical-to-quality requirements you can measure.
Team and timeline. Who is doing the work, who sponsors it, and a realistic schedule through the remaining DMAIC phases.
Two tools earn their place here. A SIPOC diagram (Suppliers, Inputs, Process, Outputs, Customers) gives everyone a shared, high-level map of the process in a single page. A clear VOC summary keeps the project anchored to what the customer values, not what the team finds interesting to fix.
Where beginners go wrong
Writing a solution into the problem statement ("we need a new approval system") before the data has spoken.
Defining a scope so broad that no team could finish it, then losing momentum by month three.
Treating the charter as paperwork to file rather than a living agreement the sponsor signs and revisits.
Guessing at the customer's needs instead of asking — VOC is gathered, not assumed.
A good test: hand your charter to someone outside the team. If they can restate the problem, the goal, and the boundaries without help, Define is doing its job. If they ask "so what are you actually trying to fix?", you are not ready to measure yet.
Done well, Define takes real conversation and a little discomfort, because it makes a team commit to one problem and let others go. That discipline is exactly what pays off later: a tightly defined project moves faster through Measure and Analyze because nobody is relitigating the basics.
If you want help scoping an improvement effort so it targets the right problem from day one, XNM's strategic advisory can help you frame the charter and set realistic goals.