Define the Problem

The foundational step in problem-solving: precisely articulating WHAT the problem actually is before attempting solutions. Problem definition includes: (1) Stating the GAP between current state and desired state. (2) Identifying the ROOT CAUSE (not just symptoms). (3) Specifying the CONSTRAINTS (time, budget, resources). (4) Clarifying WHO the problem belongs to (stakeholders). (5) Defining SUCCESS CRITERIA (how you'll know the problem is solved). As a mental model: most problem-solving failures trace back to poor problem definition—solving the wrong problem perfectly is worse than solving the right problem imperfectly. Einstein: 'If I had an hour to solve a problem, I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.'

When to use it

When problem-solving is failing because the wrong problem is being solved; when symptoms are being treated rather than root causes; when problem scope needs explicit boundaries; when success criteria need definition before solution generation.

How it can help

Invest disproportionate time in problem definition before generating solutions. The practice: (1) Write the problem statement explicitly—vague problems produce vague solutions. (2) Ask 'why?' five times to move from symptoms to root cause. (3) Define the boundaries: what's IN scope and OUT of scope? (4) Specify measurable success criteria before seeking solutions. (5) Validate the problem definition with stakeholders before proceeding. For entrepreneurs: the most common startup failure is building a solution to the wrong problem. Customer discovery IS problem definition.