1. Energy on the Go
Week 2 – User Research

2. Agenda Previous week User Research Design Implications
Methodology
Results
Design Implications
Project Planning

3. Previous Week - Tasks
User Research
Redesign of some features

4. Previous Week - Effort User Research Design Development:
Pre-Research – questionnaire preparation: 2h
Formative user study: 5h
Post-Research – result report : 3h
Design
Design Implications:
Development:
Research of OutSystems Platform: 10h
Architecture definition: 4h

5. User Research

6. UR – Methodology
Uncovering the Mental Model
Wizard of Oz
Think-Aloud

7. Uncovering the Mental Model
From a user perspective, it is specially important to understand the main screen of the application since all of the tasks have this same starting point.
User was prompted to detail every element, top to bottom, left to right.
User was questioned if he/she was sure or was just guessing.

8. Wizard of Oz / Think-Aloud
Four tasks were given to the users, each for specific features of our application
Testing team was composed of three elements:
One element simulated the behavior of a device.
One element prompted the user whichever he felt the need to.
One element took notes of the interaction.
The main goal was to understand the way users think when using our application in order to address and improve design issues.

9. UR – Demographics

10. UR – Tasks
Go to your profile to see how far away you are from your next goal and see in which month you had a bigger activity.
Remove device SmartBand Xiaomi Mi 1 from your devices
Add device Apple Watch to your devices
Share your achieved discount on your social networks

11. UR – Results (Tasks)

12. UR – Results (Perception)

13. Design Implications

14. Design Implications
Users found out that the screens for sync data and manage devices were ambiguous.
We’ll merge both screens into one, allowing the user to add, remove or edit the devices.
Users found out that the “Synchronize” action was not perfectly clear – if it was between devices or to the server, for instance.
We’ll present the information in a way to emphasize that the sync action is with other devices

15. Design Implications
When sharing to social networks, users found out weird to have all options automatically selected.
We’ll present all the available options and then the user will manually select to which social networks they will share.
The “tick” of Synchronize was not self-explanatory of the purpose
We’ll give the option to swipe the device name (on the device list) and give the user three options: add, remove or sync.

16. Design Implications
It was not clear for the users the time interval for calories, kilometers and steps on the main screen
We’ll indicate the timeframes for which the data refers to. Other possible option is to allow the user to configure the timeframe.
On the graph, the units and scale were missing
On the graph, if it’s Monday and the user is on the weekly view, he’s unable to compare data
We’ll allow the user to scroll on the graph

17. Overview / Conclusions
The possibility of getting discounts on their electricity bill was pointed out as an “ignitor” for the users to start using this application.
Ease of access to the data on the profile
The tasks were intuitive and relatively easy to do
Some mistakes were made during the usage of the application but the users were quickly able to navigate on it without further mistakes.
The amount of information provided to the users was considered relevant and enough (calories, kilometers and steps).

18. Project Planning

19. Next week Design and Development team will be the main actors
Design team will adapt the designs based on user feedback
Development team will implement the low-functionality prototype
User Research will be in support of these two teams

20. Thank you.