<?xml version="1.0" encoding="utf-8"?>

Putting it all together

Putting it all together Bad Practice
Putting it all together Best Practice

Great problem framing combines all these elements into a coherent narrative. Start with synthesis to understand the landscape. Form clear hypotheses based on patterns in the data. Write problem statements that capture both user and business perspectives. Connect everything to measurable objectives.

The process is iterative. Initial hypotheses might be wrong. Problem statements may need refinement as you learn more. OKRs might shift based on new insights. This flexibility is a strength, not a weakness. It shows you're learning and adapting based on evidence.

Remember that problem framing is a team sport. Include designers, engineers, and stakeholders in the process. Different perspectives lead to better problem definitions and more creative solutions. When everyone understands the problem deeply, they can contribute more effectively to solving it.[1]

Pro Tip: Document your problem framing process to help others understand your thinking and build on your work.

Improve your UX & Product skills with interactive courses that actually work