What Is a Problem Statement in Six Sigma?

A problem statement is a short description of what is wrong, written in observable and measurable terms — free of causes, free of blame, and free of solutions. It says what is happening, where, since when, and how large the gap is between current and required performance. In Six Sigma it anchors the project charter, and its discipline is mostly a discipline of restraint: describing the pain without smuggling in a diagnosis.

How it works

A strong problem statement answers a handful of questions. What is the defect or failure, in plain terms? Where and when does it occur? How is it measured, and what is the current level? Why does it matter — to the customer, in cost, risk, or delay? Everything else is left out on purpose. Naming a cause pre-empts the Analyze phase before any data has been examined. Naming a solution pre-empts the entire project.

The test is simple: could a skeptical outsider verify every clause? “Morale is low” fails the test. “Customer complaint calls about billing errors have doubled since March” passes — provided the call logs back it up. If a clause cannot be checked, it is an opinion wearing a statement’s clothes. Length is a signal too: a statement that runs past four or five sentences is usually carrying analysis it should not yet contain.

An example in practice

An illustrative case: a regional insurance office is troubled by slow claims. The first draft reads: “Claims take too long because adjusters are overloaded and we need more staff.” It contains a cause, a solution, and no numbers. The rewrite: “Over the last quarter, routine auto claims took an average of 19 days from filing to decision against a service standard of 10, and roughly a third of claimants called at least once to ask about status.” Now the Measure phase can confirm it, Analyze can explain it, and nobody has committed to hiring anyone.

• Embedding a cause — “because” is usually the first word to delete
• Prescribing a solution before the analysis has run
• Using judgment words like “too slow” or “unacceptable” instead of measurements
• Blaming a team or a person, which turns the project political on day one
• Describing the problem so broadly that any outcome could be claimed as success

If your problem statement contains a solution, you have written a conclusion, not a problem.

Writing problem statements is taught early because everything downstream depends on it. Yellow Belt ($129, about 14 hours) covers the structure alongside the rest of the Define toolkit, and Green Belt has you drafting and defending your own through a full simulated DMAIC project. It is a skill of subtraction more than addition — and one that interviewers notice quickly.