Problem Definition

Problem definition is the discipline of clearly stating what the problem actually is before spending effort on solutions. The statement covers scope, cause, and constraints.

The idea

It is easy to start solving the wrong problem. That is often the one that is most visible, most recently mentioned, or easiest to fix, rather than the one that actually matters. Careful problem definition separates symptoms from the underlying issue, states the problem in neutral terms (without presupposing a solution), and makes explicit who is affected and what “solved” would look like. A well-defined problem statement is usually specific enough that two people reading it would agree on whether a proposed fix actually addresses it.

When to use it

• At the start of any significant project, before brainstorming solutions
• When a team is debating solutions but disagrees on what problem they’re solving
• When a recurring issue keeps getting patched without going away

How to apply it

1. Write the problem as an observation, not a solution (“Users abandon checkout at step 3” rather than “We need a simpler checkout form”).
2. State who is affected, how often, and what the impact is.
3. Separate the symptom from the suspected root cause.
4. Check the definition with someone close to the problem before moving to solutions.

Watch out for

• Defining the problem so narrowly that it presupposes the answer.
• Skipping this step under time pressure and solving the wrong thing faster.
• Letting the loudest stakeholder’s framing stand in for a checked definition.

Related models

• Problem Framing. How you frame the definition shapes which solutions seem obvious.
• Root Cause Analysis. Digs deeper into the cause once the problem is defined.
• Problem Solving. Definition is the first step in the broader process.