What is the best way to handle 'Scope Creep' in a Six Sigma Black Belt project?

All answers to this question.

You need to lean heavily on your Project Charter. The Charter is a contract. When executives ask for UI updates, point to the "In Scope / Out of Scope" section. Explain that adding variables increases the complexity of the "Analyze" phase and will delay the results for the primary "Y" (billing defects). If they insist, tell them those requests will be added to a "Future Opportunities" log for a separate project. This validates their input without derailing your current statistical analysis.

   Answered 2024-08-06 by Angela Whitaker

Have you tried using a SIPOC diagram to show them how those extra requests fall outside the specific process boundaries you are currently measuring?

   Answered 2024-08-07 by Gregory Peck

• Gregory, I used the SIPOC in the last meeting, but the Finance Director argued that "Billing" and "Customer Satisfaction" are inseparable. I’m going to try Angela’s idea of the "Future Opportunities" log next. It sounds like a softer way to say "no" while still acknowledging that their concerns are valid for the business.

     Commented 2024-08-08 by Bradley Cooper

Be firm. Six Sigma is about precision. If the scope expands, the data gets muddy, and you'll fail to reach your Sigma level goals. Stick to the primary metric.

   Answered 2024-08-09 by Judith Lawrence

• Precisely, Judith. Muddy data is the enemy of a Black Belt. If you try to measure too many things at once, you’ll never find the true root cause of the billing errors.

     Commented 2024-08-10 by Angela Whitaker