The definition

A problem statement is a short description of the gap between where you are now and where you need to be. It says what is wrong, for whom, and how much it matters. It does not say how to fix it.

A good statement has four parts:

• The current state. What is happening today, in facts and numbers.
• The desired state. What should be happening instead.
• The gap. The distance between the two, measured if possible.
• The impact. What it costs the business or the people involved if the gap stays open.

Why it has two jobs

First, it aligns people. A team of ten holds ten private versions of the problem until one shared sentence replaces them. Second, it sets the boundary. It tells the team what the project will touch and what it will leave alone. Without a boundary, scope grows quietly until the project collapses under its own weight.

The logic

Every later step borrows from this one. Your research questions, your solution options, your budget and your success measures all come from the statement. If the statement is wrong, all of them are wrong. They will still look professional. That is why errors here are the most expensive errors in a project.

A worked example

Weak: "Our onboarding is bad." This says nothing measurable. Bad for whom? Compared with what?

Stronger: "New customers take 21 days on average to finish setup, against a target of 7 days. 30% of them leave before day 14. Each lost customer costs about Rs 40,000 in yearly revenue."

Now you can see the current state, the target, the gap and the impact.

Common mistakes

• Writing a goal instead of a gap. "Improve onboarding" is a wish, not a problem.
• Leaving out the number. Without a number, nobody can tell when you are done.
• Writing for yourself. If only your team understands it, it is not yet a shared statement.