Definition

Now we're going to take those insight statements and 0:00 reframe them into problem statements. 0:02 Identifying and defining the design problem is an important step 0:05 that will set the direction and focus for you and the rest of your team. 0:09 Defining problem statements is done by combining your knowledge about the user 0:13 you're designing for. 0:17 Their needs and the insights which you've come to know in your research. 0:18 Look at your insight statements, particularly the ones that are problems 0:22 users have, and start writing problem statements. 0:26 Once you've written them down, decide which problem or problems you and 0:29 your team are going to focus on. 0:33 In a real life situation, you will also need to consider the goals of your company 0:35 and see how that impacts the problems your team should be solving. 0:40 For our project, let's focus on the problem 0:43 users need a mobile solution that is familiar, visually appealing, and 0:46 trustworthy for buying, selling, or browsing items on Craigslist. 0:51 The last exercise before we get into the ideation phase is 0:55 to create how might we statements. 0:59 These statements are created by rephrasing and framing your problem statement 1:01 as several questions by adding how might we at the beginning. 1:05 You can also break the larger problem statement into smaller actionable and 1:09 meaningful questions. 1:13 Your how might we questions should generate a number of possible answers and 1:14 will become a launchpad for your ideation sessions. 1:18 From our problem statement, start listing some how might we questions, and 1:21 keep in mind that these statements should be broad enough to allow for 1:25 a variety of solutions. 1:28 If you find it helpful, in a new frame, 1:30 create a problem statement worksheet where you can put your problem statement, 1:32 key insights, how might we statements, and design principles in one place. 1:36 This can help you quickly refer back to your research 1:41 as you begin the ideation phase. 1:44