Bummer! This is just a preview. You need to be signed in with a Basic account to view the entire video.
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.
What is the problem you're trying to solve?
It helps to include a problem statement.
A problem statement can be constructed like this.
A user role who feels a negative feeling about something
needs to do something but faces an obstacle.
In this project I have two problem statements, one for each user role.
A student who feels excited about joining the apprenticeship
program needs to sign up but faces confusion about what to expect.
And a Treehouse employee who feels excited about recruiting for
apprentices needs to manually set up accounts and access levels.
But faces an exceedingly large pool of candidates and
is concerned about the ability to scale this procedure.
Stating the problem helps everyone get on the same page, and
it avoids any confusion about the task at hand.
Include any data that helps inform the problem.
For example, in this slide I included the qualitative data I was hearing.
These quotes helped me understand the pain points.
Next, state the goals.
The success of your solution will depend on how the team defines success, and goals
help align everyone to judge the solution based on the same success metrics.
Define the goals by answering this question.
How will you know if the design is successful?
Is the goal to increase the sign-up rate or to increase conversions?
It helps to provide actual numbers to target, so that success can be measured.
But it's okay if you don't have numerical targets.
As you can see here, my goals weren't numbers driven.
It helps to go deeper into the goals and include any requirements and constraints.
Usually the goals don't go into the details.
So it's helpful to include that on a separate slide.
Then state the assumptions.
Is there anything you're assuming to be true as you come up
with a design solution?
For my project, I assumed that most people interested in the apprenticeship program
don't have a Treehouse account.
That allowed me to not get too preoccupied with
optimizing the transfer of an existing student account to an apprentice account.
I still provided a method for transferring, but
I prioritize the most common use case.
That wraps up this section.
Next, we'll research the problem.
You need to sign up for Treehouse in order to download course files.Sign up