A new hire is asked to fix a report the manager calls "not useful". No one explains what is wrong with it. The new hire spends the weekend redoing the whole report from scratch. Nobody asked which part had failed.
What a problem statement is
It sounds simple, but most people skip it. They feel the problem as frustration, delay or confusion, and they reach straight for a fix. A fix aimed at a feeling rarely hits the right target.
Problem statement: One sentence that names what is wrong, using specific facts, without proposing a solution.
Think of the new hire and the "not useful" report. Without a clear statement of what is wrong, any revision is a guess. The same thing happens in teams, projects and everyday decisions. Effort goes into solutions before anyone has agreed on the problem.
Why one sentence works
A single sentence makes vagueness visible. Try to write "everything is a mess" as a fact, and you notice at once that it says nothing. The limit pushes you towards specifics: a number, a date, a named gap. You need those before any solution can make sense.
Scope boundary: A line around the problem. It names what is inside your focus and at least one thing that is not. Without it, a problem tends to grow until it feels unsolvable.
Complaint or problem statement?
Vague complaint
- Describes a feeling or a general situation.
- 'The meetings waste everyone's time.'
Fact-based problem statement
- Names a specific gap or shortfall you can measure, with no solution inside it.
- 'Our weekly meeting overruns by 25 minutes because there is no agenda.'
*A stranger reading your statement should understand exactly what needs solving, without asking follow-up questions.*
One rule to remember: If your statement contains a solution, it is not a problem statement yet. Remove the solution and ask: what is broken, and what fact proves it?