From Pain Points to Problem Statements That Teams Can Execute

Pain points are observations. Problem statements are decisions. The Define phase exists to convert one into the other without losing fidelity to the user.

Step 1: Cluster without judging

Group pain points by theme - frequency, severity, and context. Resist the urge to pick a favorite solution too early. Affinity mapping works because it makes patterns visible before politics enters the room.

Step 2: Name the user and the need

A usable problem statement names who is affected, what breaks down, and why it matters. Vague statements like "improve onboarding" are not problems - they are project titles.

Try this structure:

[User] needs a way to [need] because [insight from empathy work].

Step 3: Attach success criteria

Define what "solved" looks like in measurable terms. Adoption, time saved, error rate, NPS movement - pick metrics that match the pain. Without success criteria, teams debate forever in Ideate.

Step 4: Socialize before you build

Share the problem statement with stakeholders who were not in the room. Alignment at Define saves weeks in Develop and Implement.

This is the bridge between empathy and execution. Get it right, and ideation becomes focused. Skip it, and you get feature factories.