Problem Statements in UX Discovery
<aside> 🔥 Summary A problem statement is a concise description of the problem to be solved. Writing problem statements at the beginning of the discovery process can create alignment and buy-in around the problem to be solved and provide direction in subsequent discovery activities. To construct problem statements, focus on who the problem affects, how it does so, and why it’s important to solve the problem.
</aside>
In the discovery phase of a UX project, a problem statement is used to identify and frame the problem to be explored and solved, as well as to communicate the discovery’s scope and focus.
Running discoveries can be challenging. Many teams start discovery research with little direction as to what problem they want to solve. When this happens, discoveries meander and result in dwindling team and stakeholder morale. Worse still, some discoveries begin with investigating solutions, rather than the problems those solutions are intended to solve. (Remember: if you’re investigating only solutions in a discovery, you’re not doing a true discovery!)
To avoid these issues, spend time upfront to identify and frame the problem. The better a problem is articulated, the easier and more effectively it can be solved. One device that help teams to frame a problem is a problem statement.