State the Problem and Goals2:39 with Hope Armstrong
Now it's time to set up the design problem that you're trying to solve. Describing it in a problem statement allows you to simplify the challenge so it's easy to understand. Clearly articulating the problem gets everyone on the same page.
- Meeting goal
- Problem statement
- User feedback
- Constraints / Requirements
Now it's time to delve into the project. 0:00 What is the problem you're trying to solve? 0:03 It helps to include a problem statement. 0:05 A problem statement can be constructed like this. 0:08 A user role who feels a negative feeling about something 0:13 needs to do something but faces an obstacle. 0:17 In this project I have two problem statements, one for each user role. 0:22 A student who feels excited about joining the apprenticeship 0:27 program needs to sign up but faces confusion about what to expect. 0:32 And a Treehouse employee who feels excited about recruiting for 0:37 apprentices needs to manually set up accounts and access levels. 0:42 But faces an exceedingly large pool of candidates and 0:48 is concerned about the ability to scale this procedure. 0:52 Stating the problem helps everyone get on the same page, and 0:56 it avoids any confusion about the task at hand. 1:00 Include any data that helps inform the problem. 1:04 For example, in this slide I included the qualitative data I was hearing. 1:07 These quotes helped me understand the pain points. 1:12 Next, state the goals. 1:16 The success of your solution will depend on how the team defines success, and goals 1:18 help align everyone to judge the solution based on the same success metrics. 1:24 Define the goals by answering this question. 1:29 How will you know if the design is successful? 1:32 Is the goal to increase the sign-up rate or to increase conversions? 1:35 It helps to provide actual numbers to target, so that success can be measured. 1:40 But it's okay if you don't have numerical targets. 1:44 As you can see here, my goals weren't numbers driven. 1:48 It helps to go deeper into the goals and include any requirements and constraints. 1:54 Usually the goals don't go into the details. 2:00 So it's helpful to include that on a separate slide. 2:02 Then state the assumptions. 2:06 Is there anything you're assuming to be true as you come up 2:08 with a design solution? 2:11 For my project, I assumed that most people interested in the apprenticeship program 2:13 don't have a Treehouse account. 2:18 That allowed me to not get too preoccupied with 2:20 optimizing the transfer of an existing student account to an apprentice account. 2:23 I still provided a method for transferring, but 2:28 I prioritize the most common use case. 2:32 That wraps up this section. 2:35 Next, we'll research the problem. 2:37
You need to sign up for Treehouse in order to download course files.Sign up