problem-statement

Use an empathy-driven framework to structure your problem statement by articulating who the user is, what they are trying to achieve, the barriers they face, the root cause, and their emotional impact to ensure solutions address genuine needs.

Defining user problems with Jobs-to-be-Done principles requires articulating the problem from the persona's perspective, capturing their goals and barriers to identify the root cause rather than just treating symptoms.

Conduct root cause analysis during product discovery by using an empathy mapping narrative to guide identification of the underlying cause of user barriers, ensuring your team addresses the true problem rather than surface-level symptoms.

You need an understanding of Jobs-to-be-Done and empathy mapping principles to effectively frame a problem definition, as the Skill requires articulating user perspectives and identifying root causes based on research insights.

Use an empathy-driven problem statement before building a new feature to justify development effort to stakeholders, ensuring the team aligns on a user-centric problem that resonates with genuine user needs rather than jumping straight to solutions.