← All articles

Define Done Right: Why Most Six Sigma Projects Fail Before They Start

By XNM Technologies · July 30, 2021 · 2 min read
Define Done Right: Why Most Six Sigma Projects Fail Before They Start

Define is the first phase of DMAIC, and it is the one teams are most tempted to rush. The pressure is understandable: in the supply-disrupted, recovery-minded climate of mid-2021, leaders wanted results, not scoping workshops. But a weak Define phase does not save time — it defers the cost to the Measure and Analyze phases, where a team can spend weeks collecting data for a problem no one ever clearly stated. Done well, Define sets a boundary so tight that the rest of the project almost runs itself.

What a bad Define phase looks like

Bad Define phases share a tell: nobody can state, in one sentence, what is wrong and how you will know it is fixed. The charter exists, but it is aspirational rather than operational.

  • The problem statement names a solution ('we need a new system') instead of a measurable gap.

  • Scope is unbounded — 'improve the whole intake process' with no in/out boundaries.

  • There is no baseline number and no target, so success is a matter of opinion.

  • The customer and their critical-to-quality requirements are assumed, not asked.

  • No sponsor has actually committed people, time, or authority to the work.

What a good Define phase looks like

A strong Define phase produces a charter you could hand to a stranger who would then understand the problem, its size, and its boundaries. It is built on evidence, not anecdote, and it is signed by someone with the authority to act on the result.

  1. Write a neutral problem statement. State the gap in measurable terms — 'order-to-ship time averages 9 days against a 5-day target' — with no implied cause or solution.

  2. Bound the scope explicitly. Use an in-scope/out-of-scope list and a SIPOC so everyone agrees where the process starts and ends.

  3. Listen to the voice of the customer. Translate what customers actually said into critical-to-quality (CTQ) requirements with measurable specifications.

  4. Set a baseline and a goal. Anchor the project to a current performance number and a realistic, time-bound target the sponsor accepts.

  5. Secure a real sponsor. Confirm the business case and that the sponsor will remove barriers and release the people the project needs.

A useful gate before leaving Define: read the charter aloud to someone outside the team. If they can repeat back the problem, its magnitude, and what is out of scope, you are ready for Measure. If they ask 'so what exactly are you fixing?', stay in Define. The hour you spend tightening the charter is the cheapest hour in the entire project.

If your improvement initiatives keep stalling because the problem was never sharply framed, XNM's strategic advisory can help you scope the work so that effort lands where it matters.