UX, or user experience design, is all about solving a user problem, so establishing a clear idea of exactly what problem your app will be solving for your ideal user is an important step in creating a great app.
Once you have a firm understanding of this problem you’ll shape it into a problem statement that will act as your north star throughout the design process. It should be actionable for designers and provide a clear description of the issue that the designer seeks to address.
When considering the problem your app will be solving It can be helpful to think of the problem as an unmet need - by designing a solution that meets this need, you’ll satisfy the user and ensure a great user experience.
Throughout this process keep in mind the following characteristics of a good problems statement
There are a couple of methods you can use to condense everything you know about your user problem into a single, concise statement.
Asking the right questions will help you put your finger on the right problem statement. With all your findings from the empathize phase in one place, ask yourself the four Ws: Who, what, where, and why?
Another question-based strategy, the five whys technique, can help you delve deeper into the problem and drill down to the root cause. Once you’ve identified the root cause, you have something that you can act upon; somewhere specific to focus your problem-solving efforts.
Using our daily huddle board project and the problems surrounding remote work as an example, here’s how you can use the five whys to break down the problem and understand how to create a solution.
Why are companies failing at remote work? -> They aren’t communicating properly
Why are they not communicating properly? -> They don’t have the proper tools and practices
Why are their current tools and practices not working? -> They aren’t quick and easy to understand/utilize
Why aren’t the current tools easy to use? -> They don’t follow a quick and easy formula that helps with team alignment.
Why aren’t they able to get quick and easy alignment? -> They need to be guided in a simple, easy format
The root cause here is the need for a simple and easy format, so your solution might focus on this. Your problem statement could be:
You can state this problem in a number of different ways. For example, our problem can also be stated from the users perspective:
I am a manager of a small team, but I’m struggling because we are now working remotely and am hearing that people are not feeling connected. I need a way to communicate regularly with my team members, motivate them to complete their projects, and create a culture of openness and honesty.
I am an employee and I’m feeling disconnected from all the teams in my company. I’m working from home and don’t know what's going on within the company.
Now that you’ve crafted your problem statement you’re ready to move on to User Journey Mapping!
