problem-statement

A clear problem statement separates what needs to change from how to change it, turning vague requests into crisp, testable definitions that guide effective solution exploration during project kickoff.

An X-Y problem occurs when a proposed solution feels misaligned with underlying needs. Framing analysis surfaces current framing, identifies X-Y problems, and highlights gaps between requested outcomes and actual requirements.

You reframe a vague request by providing the current framing and applying an iterative validation process. This captures hard and soft constraints to produce a testable problem statement for decision-making.

The best way to validate constraints during problem framing is to run quick framing tests. This supports iterative reframing by capturing hard and soft constraints to ensure the problem statement remains testable.

Yes, structured problem framing works when proposed solutions feel misaligned. It enforces a structured problem-statement format that separates the underlying need from the requested outcome to guide effective solution exploration.

You need a problem statement format when you face vague requests or an X-Y problem. It enforces a structured definition of what needs to change, preventing premature solution exploration before requirements analysis is complete.