Problem statements without assumed causes

Learning objectives

• Write an evidence-based problem statement.
• Remove blame, assumed causes and preferred solutions.
• Establish urgency using measured impact.

What belongs in the statement

State what is wrong compared with requirement, where and when it was observed, how large the gap is and why it matters. Avoid phrases such as "because operators are careless" or "install automation."

Garment-factory example

"During May–June, Line 12 collar-attachment DHU averaged 9.4 versus the 3.0 target, causing 420 repair hours and two packing delays." This states gap, location, timing, magnitude and impact without naming a cause.

Method

1. Collect baseline evidence.
2. Use 5W2H to check completeness.
3. State the gap and its impact.
4. Test wording with sponsor and process owner.

Common mistakes

• Vague language such as "quality is poor."
• Embedding a preferred solution in the problem statement.