Day 4: The Problem Statement | User Research

The importance of understanding the problem I am trying to solve

What is a problem statement?

This helps me identify the gap between the current state (i.e., the problem) and the desired state (i.e., the goal) of a process or a product.

Before we proceed, I realized and wanted to share that this is done in the second stage of the design thinking process. Let us briefly go over it to provide more context.

The "define" stage is where I establish a clear idea of exactly which problems I am solving for the user. I then shape this into a problem statement, which will act as my northern star throughout the design process.

Design Thinking?

This fosters an outside-the-box approach with an emphasis on creativity, innovation, and the needs of the user. This pushes me to redefine the problem space and seek out challenges that are worth solving.

Design thinking is an interactive and non-linear process that involves these steps:

  1. Empathize

  2. Define

  3. Ideate

  4. Prototype

  5. Test

Difference between Wicked and Tamed problems

Tamed problems can be solved by applying a tried-and-tested algorithm or logic. Wicked problems do not have a final solution as they need to be tackled from multiple angles, and sadly, the more I try to solve them, the more problems I expose.

Now, let's return to learning about the problem statement.

Understanding the basics

  1. Who am I working with?

  2. Who am I working for?

  3. Who can be potential stakeholders?

What is the business objective?

  1. What is supposed to be achieved with the product?

  2. What is the main goal?

  3. What are the values?

  4. What are the priorities?

The product/solution

  1. What is the product/solution

  2. In what context or environment will it be used?

  3. Why would someone use it?

  4. How would it be used?

Key takeaways/learnings

I learned about a simple structure for crafting a problem statement: (A user) need (need) to accomplish a (goal). I also learned about "wicked" and "tamed" problems. And lastly, finding the right balance in a triangle consisting of business needs, the user, and technical feasibility.

References

We are not necessarily inclined to go looking for problems. I do not want my design to miss the mark. Hence, I have to define the problem.