Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Problem Statements

Download as pdf or txt
Download as pdf or txt
You are on page 1of 9

USER PROBLEM

& HYPOTHESIS
STATEMENTS

Dr. Will Kurlinkus


PROBLEM STATEMENTS
• Problem Statement: Clear description of the user need that needs to
be addressed by your design.
• Establish goals: what your user really needs
• Understand constraints: what’s preventing users from
accomplishing their goal?
• Define deliverables: What can we create to resolve the constraints
and help achieve the goal?
• They generally contain a user name (from your persona),
characteristic (some motivating attribute-–they are busy, they are
cheap, the love exploring art), user need (the goal your user is trying
to accomplish), and problem insight (these are pain points).
SCENARIO: COFFEE
ORDERING APP
• Anika is an intern at a tech company. She has to
take the coffee order every morning for 6-10
colleagues including what drinks and food they
want. She then has to get the coffee and deliver it
back to them. People often don’t know what drinks
are available, what’s on the menu, and their orders
sometimes get mixed up. The ordering process ends
up taking an extra long time, especially since she
has to call them in.
THE 5 W’S OF PROBLEM STATEMENTS
• Who is experiencing the problem? Knowing your users and their background is key to creating successful solutions
for them.
• What are the pain points you’re trying to solve? Determining a user’s pain points early allows you to answer the rest
of these questions and clarify the context of the pain points.
• Where is the user when they’re using the product? A user’s physical context matters to your design.
• When does the problem occur? Maybe it’s right after the end of a long and tedious process, or maybe it’s something
that happens daily. Knowing when the problem occurs can help you better empathize with the user’s feelings.
• Why is the problem important? Knowing how this problem affects your user’s experience and life will help to clarify
the potential consequences.
• How are users reaching their goals by using the product? Understanding how users reach their goals allows you to
map the user journey that they take through your product.
HYPOTHESIS STATEMENTS

• Hypothesis Statement: Our best educated guess of what we think the solution to a design
problem might be. These are often framed as if/then statements: If (action) then (outcome).
• Sample Problem Statement: Amal is an athlete who needs to sign up for workout classes
because the class he wants always fills up fast.
• Sample If/Then : If Amal downloads the gym’s app, then he will be able to reserve a spot in
his favorite class in advance.
• Design Attribute Definition: Amal needs an app that allows him to reserve his favorite class in
advance and notifies him of the first opportunity to sign up.
WHAT APP
FEATURES MIGHT
COME FROM THIS
HYPOTHESIS
STATEMENT?

You might also like