Topic: Grocery shopping
Through persona, you can relate more on how’s the persona behaves/ reacts to your product. Persona is the target group of audience that you aim to get your empathy with.
Does getting more persona means better for your project?
– More persona means your project need to target more group of audience which you have high possibility of pleasing no one in the end.
Katia conducted 3 brief interviews in front of us and we were told to write each of the observation on a sticky note during the interview. After that we grouped relevant ones together and synthesised the whole picture.
Note: Separate themes by goals, not behaviors. It’s possible that not all post-its will fall into a big grouping, and that’s okay.
Warning: A lot of Post-it notes ahead
Developing a persona let you less likely to create the product for yourself only and it keeps you to be focus more to your key users.
Defining user goals and user flows
How Might We (HMW)
For me, HMW is a better way to refine problem statement where you are more focus on solving the problem in a more user-oriented way. However, you still need to beware from setting your HMW too wide or too narrow.
- It suggests the area of focus, but still offers the chance to address the problem in several ways.
- To specify the size of the problem. Keep asking “How” to narrow scope, and “Why” to broaden scope.
How many or when we should use HMW?
– Preferably 1 HMW for 1 goal of the project
There are many aspects we can start with HMW
- Opposite: HMW make price comparing at shopping even easier?
- Assumption: HMW entirely remove the wait time in shopping?
- Adjectives: HMW make lining up at cashier more enjoyable instead of boring?
- Analogy from needs/context: HMW make supermarket like a museum(filled with nutrition info)?
- Change POV: HMW encourage food wastage in shopping?
- Break POV into pieces: HMW make each person has better personalise grocery experience?
Here are few thoughts we came out with HMW:
Problem statement & Hypothesis
[Persona name] needs a way to [user’s need], because [insight].
Example: [Madam Wong] needs a way to [compare food quality and cost], because [she want to have a balanced food nutrition for her family].
We believe that [doing this], for [these people], we will achieve [this outcome].We will know this to be true when we see [this feedback/quantitative measure/qualitative insight].
Example: We believe that [by providing a monthly newsletter of healthy food and choice], for [these people], we will [enlighten users more on nutrition with product recommendation].We will know this to be true when we see [the increment in user purchases].
Quantitative outcome is the thing that we need to evaluate the product is a success or not. By providing hypothesis, it helps in transitioning into a realistic output.
From: We need to have a personalised news for user.
To: We want to show user-customized news sources only to user.
This was an interesting session. Everyone of us was told to fold the paper into 8 parts and we drew all the ideas in each of those.
First, we started of with bad ideas, any bad ideas about grocery shopping. I was actually impressed with some of bad ideas like
– Customer shops with roller blades
– Drone delivery for grocery
While some are:
– Use cat to do the delivery (LOL)
– Put all the discount items (TV, fruits, clothes together) for customer to shop at one go
For good ideas, it doesn’t really need to be a detailed illustration as the sketching session is supposed to let your creativity juice flows better and you could even get your good ideas inspired by bad idea with just a few tweaks!
There’s usually 3 parts of the user flow you can covered:
- Trigger influence
What I have learned
Providing user flow gives client a better view/ coverage on how’s people will interact with your solution with actions and forms a bigger picture. When you draw your solution, it becomes clearer and it helps you to explain as well on how the flows involved in the app. Through today class, I reexamined my language learning project to focus on main problem statement(with HMW) and came out with the user flow.