Dashcam usability testing
Time: 2013
Total working time: one month
Team members: me (made the prototype and conduct the usability testing) and one colleague helps to take photos and videos
Method: Prototyping, usability testing, card sorting, system usability scale
Domain: Automotive
Usability testing:
It divided into two parts. One by a questionnaire for icon recognition to evaluate whether users feel the same meaning by the GUI design. One by task simulation, seven tasks set for the test from saving an emergency video to change settings.
Card sorting:
There are lots of settings. We need to make sure users can easily find their intended item under a specific category they can understand.  
System usability scale (SUS):
PM'd like not only qualitative results but quantitative results as well. SUS followed after the usability testing.
Through the test, some setting items need to regroup. Fortunately, the founded issue still in the design phase that means the R&D doesn't need to rework the structure. Also, some icons need a redesign. Furthermore, some terms should address in the user manual for better understanding.  
The test also established the later touched versions information architecture base.
Outcome
Contact Lydia
View next
More works
Card sorting designed in digital form for easy data analysis later.
The icon questionnaire is in digital form and designed by 1:1 scale.
The usability testing setting.
The digital prototype flow planned on paper in advance to get right hyperlink later.
The digital prototype stores in a smartphone and placed in a real vehicle environment.
“The first touched version dashcam requires a usability testing.”
“We have to make sure icons are easy to be understood in the real situation.”
“The prototype implemented on a smartphone to make workable UI.”
It is the first time we design a touched version dashcam (car driving recorder) on our own.  The UI is different from our current product line. Thus, this study tends to find usability issues of the incoming product at pre-stage to avoid some development problems might happen later, such as restructure UI flow.
Purpose
For touch purpose, current UI design changes each function into an icon for users easy to select. On 2.5” touchscreen, the visual area is quite small, and all texts under each icon are even smaller and hard to read from the arm distance (the distance between driver and where s/he locates a car DVR). Thus, we have to make sure icons are easy to be understood. Users can select a function they want mainly by icons, but not texts.
For safety consideration, we cannot ask participants do the testing on the road. Also, the working model is not ready, only UI design ready. Hence, how to simulate the real situation and environment become the challenge.
Challenge
Prototyping:
The prototype tries to simulate the "real" situation as accurately as possible. The UI design used Google Slides to implement on a small screen smartphone by 1:1 scale as the real product. It mounted on the windshield in a car for participants to interact in the actual environment including the right distance and under right light source.
Challenge
The digital prototype flow planned on paper in advance to get right hyperlink later.
The digital prototype stores in a smartphone and placed in a real vehicle environment.
The icon questionnaire is in digital form and designed by 1:1 scale.
The usability testing setting.
Card sorting designed in digital form for easy data analysis later.
Dashcam usability testing
Time: 2013
Total working time: one month
Team members: me (made the prototype and conduct the usability testing) and one colleague helps to take photos and videos
Method: Prototyping, usability testing, card sorting, system usability scale
Domain: Automotive
Purpose
It is the first time we design a touched version dashcam (car driving recorder) on our own.  The UI is different from our current product line. Thus, this study tends to find usability issues of the incoming product at pre-stage to avoid some development problems might happen later, such as restructure UI flow.
Challenge
For touch purpose, current UI design changes each function into an icon for users easy to select. On 2.5” touchscreen, the visual area is quite small, and all texts under each icon are even smaller and hard to read from the arm distance (the distance between driver and where s/he locates a car DVR). Thus, we have to make sure icons are easy to be understood. Users can select a function they want mainly by icons, but not texts.
For safety consideration, we cannot ask participants do the testing on the road. Also, the working model is not ready, only UI design ready. Hence, how to simulate the real situation and environment become the challenge.
Method
Prototyping:
The prototype tries to simulate the "real" situation as accurately as possible. The UI design used Google Slides to implement on a small screen smartphone by 1:1 scale as the real product. It mounted on the windshield in a car for participants to interact in the actual environment including the right distance and under right light source.
Outcome
Through the test, some setting items need to regroup. Fortunately, the founded issue still in the design phase that means the R&D doesn't need to rework the structure. Also, some icons need a redesign. Furthermore, some terms should address in the user manual for better understanding.  
The test also established the later touched versions information architecture base.
Contact Lydia
View next
More works
Usability testing:
It divided into two parts. One by a questionnaire for icon recognition to evaluate whether users feel the same meaning by the GUI design. One by task simulation, seven tasks set for the test from saving an emergency video to change settings.
Card sorting:
There are lots of settings. We need to make sure users can easily find their intended item under a specific category they can understand.  
System usability scale (SUS):
PM'd like not only qualitative results but quantitative results as well. SUS followed after the usability testing.
“The first touched version dashcam requires a usability testing.”
“We have to make sure icons are easy to be understood in the real situation.”
“The prototype implemented on a smartphone to make workable UI.”
The digital prototype flow planned on paper in advance to get right hyperlink later.
The digital prototype stores in a smartphone and placed in a real vehicle environment.
The icon questionnaire is in digital form and designed by 1:1 scale.
The usability testing setting.
Card sorting designed in digital form for easy data analysis later.
Purpose
It is the first time we design a touched version dashcam (car driving recorder) on our own.  The UI is different from our current product line. Thus, this study tends to find usability issues of the incoming product at pre-stage to avoid some development problems might happen later, such as restructure UI flow.
Challenge
For touch purpose, current UI design changes each function into an icon for users easy to select. On 2.5” touchscreen, the visual area is quite small, and all texts under each icon are even smaller and hard to read from the arm distance (the distance between driver and where s/he locates a car DVR). Thus, we have to make sure icons are easy to be understood. Users can select a function they want mainly by icons, but not texts.
For safety consideration, we cannot ask participants do the testing on the road. Also, the working model is not ready, only UI design ready. Hence, how to simulate the real situation and environment become the challenge.
Method
Prototyping:
The prototype tries to simulate the "real" situation as accurately as possible. The UI design used Google Slides to implement on a small screen smartphone by 1:1 scale as the real product. It mounted on the windshield in a car for participants to interact in the actual environment including the right distance and under right light source.
Outcome
Through the test, some setting items need to regroup. Fortunately, the founded issue still in the design phase that means the R&D doesn't need to rework the structure. Also, some icons need a redesign. Furthermore, some terms should address in the user manual for better understanding.  
The test also established the later touched versions information architecture base.
View next
More works
Contact Lydia
Usability testing:
It divided into two parts. One by a questionnaire for icon recognition to evaluate whether users feel the same meaning by the GUI design. One by task simulation, seven tasks set for the test from saving an emergency video to change settings.
Card sorting:
There are lots of settings. We need to make sure users can easily find their intended item under a specific category they can understand.  
System usability scale (SUS):
PM'd like not only qualitative results but quantitative results as well. SUS followed after the usability testing.
“The first touched version dashcam requires a usability testing.”
“We have to make sure icons are easy to be understood in the real situation.”
“The prototype implemented on a smartphone to make workable UI.”
Dashcam usability testing
Time: 2013
Total working time: one month
Team members: me (made the prototype and conduct the usability testing) and one colleague helps to take photos and videos
Method: Prototyping, usability testing, card sorting, system usability scale
Domain: Automotive