There are many grey zones. Research helps us to verify our predictions. It makes sure we are on the right track. Hypotheses are the questions we formulate about predictions in our design we want to verify. Start by defining the questions you want answered. Look at your previously established objectives and take out that lists of facts and assumptions you put together with your team. What are your biggest doubts. What do you need to verify before you can go on?
Hypotheses are predictions about user behaviours.
In the case of a music streaming app we could formulate the following hypothesis: People like to share their favorite songs with there friends on social media.
With a weight loss application the hypothesis could be: People like to keep track of their calorie intake with a daily food log.
Hypotheses can investigate an attitude, a behavior or a function and can be categorized in:
- Attitude-related hypothesis
“People who want to lose weight like to hear success stories of other people to get motivated”
- Behavior-related hypothesis
“People who want to lose weight want to share their success with their friends and family”
- Feature-related hypothesis
“People who want to lose weight are more likely to write a food log if they are reminded on a daily basis.”
Don’t make too wide statements. You need to be able to test your hypothesis, so don’t lose yourself in complicated, wast statements which are impossible to confirm or reject. Also, don’t worry if you are not sure into which category your hypothesis falls. Remember, the value in formulating a hypothesis is to structure your thoughts into questions and statements. This effort gives you a clearer vision of your research project.
Make your hypothesis:
ask questions you want answered
make predictions about users’ behavior
formulate refined statements about what you predict
Don’t make too wide statements.
Read on for day 4: Explore like Columbus or evaluate like Galileo