HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 Fixxlar User Tests"

From IS480
Jump to navigation Jump to search
Line 48: Line 48:
 
<!--User Testing 2 Start-->
 
<!--User Testing 2 Start-->
  
<div style="background: #E5A400; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.03em;font-size:16px;id:UT1"><font color=#ffffff><center><i>User Testing 2 (24 September 2016)</i></center></font></div>
+
<h2><div style="background: #E5A400; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.03em;font-size:16px;id:UT1"><font color=#ffffff><center><i>User Testing 2 (17 September 2016 - 5 October 2016)</i></center></font></div></h2>
&nbsp;
+
 
 +
<!--User Testing 2C Start-->
 +
 
 +
<!--COMMENT OUT FOR NOWWWWWWWWWWWWWWWWWWWWWWWWWWW
 +
<h3><u>User Testing 2C</u></h3>
 +
<b>Venue:</b> FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)<br/>
 +
<b>Date:</b> 4 October 2016 - 5 October 2016, Tuesday - Wednesday <br/>
 +
<b>Time:</b> 6:00pm - 8.00pm <br/>
 +
<b>Duration:</b> ~30 minutes <br/>
 +
<b>Number of Participant(s):</b> 5 (TBC) <br/>
 +
 
 +
<h4>Objectives:</h4>
 +
*To gather feedback on the user interface of web application for Customers
 +
*Identify possible usability issues with primary functions of Fixir Customer Web Application Module
 +
 
 +
<h4>Scope for User Testing 2C:</h4>
 +
*Signing up and logging in as Fixir's customer
 +
*Submitting and accepting quotation request
 +
*Opting for valet services
 +
*Verify repair completion
 +
 
 +
<h4>Target Participants & Rationale:</h4>
 +
* Participants of this second user testing would be drivers who have worked with Fixir
 +
 
 +
<h4>Method of Conduct: </h4>
 +
* [https://docs.google.com/document/d/1_3AvzFCgjb5n6zkjKyVuHopsPPBhWRUV6xuHXv6wFWc/edit# User Testing 2C (Participant's Tasklist for Customers)]
 +
* [https://docs.google.com/document/d/1pGhJXbQqDJ9fzjcgauNqS6yKy4SfQOQRQjBT18w3Gu8/edit User Testing 2C (Customers Overall Feedback)]
 +
 
 +
<h4>Goals and Results: </h4>
 +
 
 +
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 +
|-
 +
|-
 +
! style="color:#ffffff; background-color:#E5A400;" width="30pt" align="center" | S/N
 +
! style="color:#ffffff; background-color:#E5A400;" width="400pt" align="center" | Goals
 +
! style="color:#ffffff; background-color:#E5A400;" width="400pt" align="center" | Results
 +
|-
 +
|style="text-align: center;"| 1 || Participants should be able to sign up and login as a new Fixir customer.
 +
|style="background-color:#A3E4D7"| Successful. Participants had no trouble signing up and logging in.
 +
|-
 +
|style="text-align: center;"| 2 || Participants should be able to submit quotation request for their vehicle.
 +
|style="background-color:#A3E4D7"| Successful. All participants were able to submit quotation requests for the particular vehicle they created.
 +
|-
 +
|style="text-align: center;"| 3 || Participants should be able to accept final quotation from a workshop which they are keen to engage.
 +
|style="background-color:#A3E4D7"| Successful. All participants were able to accept final quotation.
 +
|-
 +
|style="text-align: center;"| 4 || Participants should be able to mark repair as "completed"
 +
|style="background-color:#A3E4D7"| Successful. All participants were able to complete the request.
 +
|-
 +
|}
 +
 
 +
 
 +
<h4>User Test Findings:</h4>
 +
 
 +
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 +
|-
 +
|-
 +
! style="color:#ffffff; background-color:#E5A400;" width="300pt" align="center" | Function / Task
 +
! style="color:#ffffff; background-color:#E5A400;" width="500pt" align="center" | Observation / Comments
 +
|-
 +
|style="text-align: center;"| Signing up and Logging in
 +
||
 +
* Generally easy and self-explanatory. Participants had no trouble accomplishing this task.
 +
|-
 +
|style="text-align: center;"| Submitting Quotation Request
 +
||
 +
* Step-by-step guide is useful, but not all drivers know how to categorise their repair.
 +
* Additional service description tab may contradict the general category. 
 +
|-
 +
|style="text-align: center;"| Accepting Estimated Quote from Workshop
 +
||
 +
* UI is easy for price comparison
 +
* Straightforward
 +
|-
 +
|style="text-align: center;"| Accepting Final Quote from Workshop
 +
|| 
 +
* Easy to use
 +
|-
 +
|style="text-align: center;"| Repair Completed
 +
||
 +
* Straightforward
 +
|}
 +
 
 +
<h4>Follow-ups / Improvements Made:</h4>
 +
*to be updated
 +
BLOCK OUT UNTIL HEREEEEEEEEEEEEEEEEEEEEEEEEEEE-->
 +
 
 +
<!--User Testing 2B Start-->
  
<h2><u>User Testing 2B</u></h2>
+
<h3><u>User Testing 2B</u></h3>
 
<b>Venue:</b> FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)<br/>
 
<b>Venue:</b> FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)<br/>
<b>Date:</b> 1 October 2016, Saturday <br/>
+
<b>Date:</b> 24 September 2016, Saturday <br/>
 
<b>Time:</b> 10:00am - 3.00pm <br/>
 
<b>Time:</b> 10:00am - 3.00pm <br/>
 
<b>Duration:</b> ~30 minutes <br/>
 
<b>Duration:</b> ~30 minutes <br/>
<b>Number of Participant(s):</b> 5 (TBC) <br/>
+
<b>Number of Participant(s):</b> 5 <br/>
  
<h3>Objectives:</h3>
+
<h4>Objectives:</h4>
*To gather feedback on the user interface of Valet Driver’s web application
+
*To gather feedback on the user interface of Valet Driver’s web application - to be compatible with mobile site too
*Identify possible usability issues with functions of Valet Module
+
*Identify possible usability issues with functions and usability of Valet Module
  
<h3>Scope for User Testing 2B:</h3>
+
<h4>Scope for User Testing 2B:</h4>
 
*Logging in and out as Valet Driver
 
*Logging in and out as Valet Driver
 
*Viewing all "New Requests"
 
*Viewing all "New Requests"
 
*Accepting valet requests
 
*Accepting valet requests
 
*Updating status of valet requests at various stages
 
*Updating status of valet requests at various stages
 +
*Verifying compatibility on mobile site
  
<h3>Target Participants & Rationale:</h3>
+
<h4>Target Participants & Rationale:</h4>
 
* Participants of this second user testing would be our sponsor (from Fixir team, who will be acting as valet drivers when the business rolls out), and also valet service providers.  
 
* Participants of this second user testing would be our sponsor (from Fixir team, who will be acting as valet drivers when the business rolls out), and also valet service providers.  
  
<h3>Method of Conduct: </h3>
+
<h4>Method of Conduct: </h4>
 
* [https://docs.google.com/document/d/1BjbjSOPNEGbUUL-gmGUruYdf19GB3qh3x8gkkhb56J8/edit#heading=h.3ax1qmguz9gx User Testing 2B (Participant's Tasklist for Valet Driver)]
 
* [https://docs.google.com/document/d/1BjbjSOPNEGbUUL-gmGUruYdf19GB3qh3x8gkkhb56J8/edit#heading=h.3ax1qmguz9gx User Testing 2B (Participant's Tasklist for Valet Driver)]
 
*[https://docs.google.com/document/d/1RKa0iSUCRzxdWAl3TvkUE2Fq51B_ifz6zZWPPrJ79zM/edit#heading=h.6vp7h5kkxjel User Testing 2B (Valet Driver Overall Feedback)]
 
*[https://docs.google.com/document/d/1RKa0iSUCRzxdWAl3TvkUE2Fq51B_ifz6zZWPPrJ79zM/edit#heading=h.6vp7h5kkxjel User Testing 2B (Valet Driver Overall Feedback)]
  
<h3>Goals and Results: </h3>
+
<h4>Goals and Results: </h4>
  
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
Line 88: Line 176:
 
|-
 
|-
 
|style="text-align: center;"| 2 || Participants should be able to view all valet requests which have not been replied.  
 
|style="text-align: center;"| 2 || Participants should be able to view all valet requests which have not been replied.  
  |style="background-color:#A3E4D7"| Successful. All participants were able to view all the valet services without guidance.
+
  |style="background-color:#F9E79F"| Successful. All participants were able to view all the valet services without guidance. However, it was not very mobile-friendly/readable.  
 
|-
 
|-
 
|style="text-align: center;"| 3 || Participants should be able to accept the valet request which he/she is keen on taking up.  
 
|style="text-align: center;"| 3 || Participants should be able to accept the valet request which he/she is keen on taking up.  
Line 98: Line 186:
 
|}
 
|}
  
<h3>User Test Findings:</h3>
+
<h4>User Test Findings:</h4>
  
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
Line 112: Line 200:
 
|style="text-align: center;"| Accepting Valet Request
 
|style="text-align: center;"| Accepting Valet Request
 
  ||  
 
  ||  
* It is easy to view all the available requests, and allow valet drivers to accept whichever job he is keen on taking.  
+
* It is easy to view all the available requests on desktop, but zooming is required for mobile version.
 +
* Valet drivers are able to accept whichever job he is keen on taking.  
 
* Would be a bonus to be able to track the current distance and the time of travel of the designated vehicle, from the valet driver's current location.  
 
* Would be a bonus to be able to track the current distance and the time of travel of the designated vehicle, from the valet driver's current location.  
 
|-
 
|-
Line 121: Line 210:
 
|-
 
|-
 
|}
 
|}
 
+
<h4>Follow-ups / Improvements Made:</h4>
 +
[[Image:Fixxlar Changes to UI valet.png|900px]]
  
 
<!--User Testing 2A START-->
 
<!--User Testing 2A START-->
  
<h2><u>User Testing 2A</u></h2>
+
<h3><u>User Testing 2A</u></h3>
 
<b>Venue:</b> FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)<br/>
 
<b>Venue:</b> FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)<br/>
<b>Date:</b> 24 September 2016, Saturday <br/>
+
<b>Date:</b> 17 September 2016, Saturday <br/>
<b>Time:</b> 12:00pm - 2.00pm <br/>
+
<b>Time:</b> 12:00pm - 5.00pm <br/>
 
<b>Duration:</b> ~30 minutes <br/>
 
<b>Duration:</b> ~30 minutes <br/>
<b>Number of Participant(s):</b> 5 (TBC) <br/>
+
<b>Number of Participant(s):</b> 5 (Fixir administrators), 3 (Workshop administrators) <br/>
  
<h3>Objectives:</h3>
+
<h4>Objectives:</h4>
 
*To gather feedback on the user interface of web application for Fixir Administrator
 
*To gather feedback on the user interface of web application for Fixir Administrator
 
*Identify possible usability issues with functions of Admin Module, Quotation Request Module, Search Module, Valet Module
 
*Identify possible usability issues with functions of Admin Module, Quotation Request Module, Search Module, Valet Module
 +
*Allow workshops to retest UT1, with the improved UI we have done after acceptance
  
<h3>Scope for User Testing 2A:</h3>
+
<h4>Scope for User Testing 2A:</h4>
 
*Logging in and out as Fixir Administrator
 
*Logging in and out as Fixir Administrator
 
*Viewing of all quotations and valet services between customers and workshops
 
*Viewing of all quotations and valet services between customers and workshops
Line 142: Line 233:
 
*Viewing, adding, updating, deleting staffs
 
*Viewing, adding, updating, deleting staffs
 
*Viewing, adding, updating, deleting valet companies
 
*Viewing, adding, updating, deleting valet companies
 +
*Receive feedback from the same workshop administrators with our new UI
  
<h3>Target Participants & Rationale:</h3>
+
<h4>Target Participants & Rationale:</h4>
* Participants of this second user testing would be our sponsor (from Fixir team).
+
* Participants of this second user testing would be our sponsor (from Fixir team) for Fixir Administrator.
 +
* Participants of first user testing from workshops.  
  
<h3>Method of Conduct: </h3>
+
<h4>Method of Conduct: </h4>
 
* [https://docs.google.com/document/d/1zEVZUDmabUzHpeAN628g9uUeOjl4NgTPUrjBqaLy3k8/edit# User Testing 2A (Participant's Tasklist for Fixir Administrator)]
 
* [https://docs.google.com/document/d/1zEVZUDmabUzHpeAN628g9uUeOjl4NgTPUrjBqaLy3k8/edit# User Testing 2A (Participant's Tasklist for Fixir Administrator)]
 
* [https://docs.google.com/document/d/1rP5eyWc__KaqvLr-NKt9UzXl43v7ZuEEFgdZDSrCLLU/edit#heading=h.6vp7h5kkxjel User Testing 2A (Fixir Administrator Overall Feedback)]
 
* [https://docs.google.com/document/d/1rP5eyWc__KaqvLr-NKt9UzXl43v7ZuEEFgdZDSrCLLU/edit#heading=h.6vp7h5kkxjel User Testing 2A (Fixir Administrator Overall Feedback)]
 +
* [https://docs.google.com/document/d/1OBUiZvxem5351UXawDF78DCHn9FcdabZQXBbo0cRd34/edit# User Testing 1 (Participant's Overall Feedback for Workshop Administrator)]
  
<h3>Goals and Results: </h3>
+
<h4>Goals and Results: </h4>
  
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
Line 176: Line 270:
 
|style="text-align: center;"| 6 || Participants should be able to view, add and edit valet companies.  
 
|style="text-align: center;"| 6 || Participants should be able to view, add and edit valet companies.  
 
  |style="background-color:#A3E4D7"| Successful. All participants were able to view, add and edit valet companies.  
 
  |style="background-color:#A3E4D7"| Successful. All participants were able to view, add and edit valet companies.  
 +
|-
 +
|style="text-align: center;"| 7 || Workshop administrators should be able to retest with new UI.
 +
|style="background-color:#A3E4D7"| Successful. All participants gave positive feedback that it is much clearer and easier to understand after the change.
 
|-
 
|-
 
|}
 
|}
  
  
<h3>User Test Findings:</h3>
+
<h4>User Test Findings:</h4>
  
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
Line 214: Line 311:
 
* Valet tab is simple and easy to use
 
* Valet tab is simple and easy to use
 
* May be good to include a range field for Revenue Share, when adding or editing a valet shop
 
* May be good to include a range field for Revenue Share, when adding or editing a valet shop
 +
|-
 +
|style="text-align: center;"| Workshop Administrator Page
 +
||
 +
* Well implemented, process flow looks much clearer now.
 +
* Participants (workshop administrators) have a better understanding of the next step.
 
|-
 
|-
 
|style="text-align: center;"| Miscellaneous  
 
|style="text-align: center;"| Miscellaneous  
Line 220: Line 322:
 
|}
 
|}
  
<h3>Follow-ups / Improvements Made:</h3>
+
<h4>Follow-ups / Improvements Made:</h4>
 
[[Image:Fixxlar_Changes_to_UI_UT2.png|900px]]
 
[[Image:Fixxlar_Changes_to_UI_UT2.png|900px]]
  
Line 227: Line 329:
 
<!--User Testing 1 Start-->
 
<!--User Testing 1 Start-->
  
<div style="background: #E5A400; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.03em;font-size:16px;id:UT1"><font color=#ffffff><center><i>User Testing 1 (6 August 2016)</i></center></font></div>
+
<h2><div style="background: #E5A400; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px;letter-spacing:-0.03em;font-size:16px;id:UT1"><font color=#ffffff><center><i>User Testing 1 (6 August 2016)</i></center></font></div></h2>
 
&nbsp;
 
&nbsp;
<h2><u>User Testing 1</u></h2>
+
<h3><u>User Testing 1</u></h3>
 
<b>Venue:</b> FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955) & Respective Workshops<br/>
 
<b>Venue:</b> FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955) & Respective Workshops<br/>
 
<b>Date:</b> 6 August 2016, Saturday <br/>
 
<b>Date:</b> 6 August 2016, Saturday <br/>
 
<b>Time:</b> 10.00am - 2.00pm <br/>
 
<b>Time:</b> 10.00am - 2.00pm <br/>
 
<b>Duration:</b> ~30 minutes <br/>
 
<b>Duration:</b> ~30 minutes <br/>
<b>Number of Participant(s):</b> 6 (TBC) <br/>
+
<b>Number of Participant(s):</b> 6 <br/>
  
<h3>Objectives:</h3>
+
<h4>Objectives:</h4>
 
*To gather feedback on the user interface of Workshop Administrator’s web application
 
*To gather feedback on the user interface of Workshop Administrator’s web application
 
*Identify possible usability issues with functions of Account Module, Quotation Request Module, Dashboard Module  
 
*Identify possible usability issues with functions of Account Module, Quotation Request Module, Dashboard Module  
  
<h3>Scope for User Testing 1:</h3>
+
<h4>Scope for User Testing 1:</h4>
 
* Logging in and out as Workshop Administrator
 
* Logging in and out as Workshop Administrator
 
* Changing of password
 
* Changing of password
 
* Viewing and replying of quotation requests
 
* Viewing and replying of quotation requests
  
<h3>Target Participants & Rationale:</h3>
+
<h4>Target Participants & Rationale:</h4>
 
* Participants of this first user testing would be our sponsor (from Fixir team), and also workshop administrators (from Dynamic Mechanics, Maximus Racing, ZG Motors, Premier One etc) whom we had spoken to during our market research.  
 
* Participants of this first user testing would be our sponsor (from Fixir team), and also workshop administrators (from Dynamic Mechanics, Maximus Racing, ZG Motors, Premier One etc) whom we had spoken to during our market research.  
  
<h3>Method of Conduct: </h3>
+
<h4>Method of Conduct: </h4>
 
* [https://docs.google.com/document/d/1wYHSllUpvvWRmLqeryP0QmJIBn77lGSAaGi8vnr5yws/edit# User Testing 1 (Participant's Tasklist for Workshop Administrator)]
 
* [https://docs.google.com/document/d/1wYHSllUpvvWRmLqeryP0QmJIBn77lGSAaGi8vnr5yws/edit# User Testing 1 (Participant's Tasklist for Workshop Administrator)]
 
* [https://docs.google.com/document/d/1OBUiZvxem5351UXawDF78DCHn9FcdabZQXBbo0cRd34/edit# User Testing 1 (Participant's Overall Feedback for Workshop Administrator)]
 
* [https://docs.google.com/document/d/1OBUiZvxem5351UXawDF78DCHn9FcdabZQXBbo0cRd34/edit# User Testing 1 (Participant's Overall Feedback for Workshop Administrator)]
  
<h3>Goals and Results: </h3>
+
<h4>Goals and Results: </h4>
  
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
Line 272: Line 374:
 
|}
 
|}
  
<h3>User Test Findings:</h3>
+
<h4>User Test Findings:</h4>
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 
{| class="wikitable" style="background-color:#FFFFFF; width: 900px;" align="center"
 
|-
 
|-
Line 320: Line 422:
 
|}
 
|}
  
<h3>Follow-ups / Improvements Made:</h3>
+
<h4>Follow-ups / Improvements Made:</h4>
 
[[Image:Fixxlar Changes to UI 1.png|900px]]
 
[[Image:Fixxlar Changes to UI 1.png|900px]]
 
<!--User Testing 1 End-->
 
<!--User Testing 1 End-->

Revision as of 02:42, 5 October 2016

Fixxlar-logo.png


Fixxir-Home.png   HOME

Fixir-about-icon.png   ABOUT US

Fixir-Overview-icon.png   PROJECT OVERVIEW

Project management-icon.png   PROJECT MANAGEMENT

Fixir-documentation-icon.png   DOCUMENTATION

 

 


User Testing 2 (17 September 2016 - 5 October 2016)



User Testing 2B

Venue: FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)
Date: 24 September 2016, Saturday
Time: 10:00am - 3.00pm
Duration: ~30 minutes
Number of Participant(s): 5

Objectives:

  • To gather feedback on the user interface of Valet Driver’s web application - to be compatible with mobile site too
  • Identify possible usability issues with functions and usability of Valet Module

Scope for User Testing 2B:

  • Logging in and out as Valet Driver
  • Viewing all "New Requests"
  • Accepting valet requests
  • Updating status of valet requests at various stages
  • Verifying compatibility on mobile site

Target Participants & Rationale:

  • Participants of this second user testing would be our sponsor (from Fixir team, who will be acting as valet drivers when the business rolls out), and also valet service providers.

Method of Conduct:

Goals and Results:

S/N Goals Results
1 Participants should be able to login and logout successfully as a Valet driver, and also change password. Successful. Participants tried changing the passwords and logging in with the new accounts created.
2 Participants should be able to view all valet requests which have not been replied. Successful. All participants were able to view all the valet services without guidance. However, it was not very mobile-friendly/readable.
3 Participants should be able to accept the valet request which he/she is keen on taking up. Successful. All participants were able to accept the valet requests which he/she wants to.
4 Participants should be able to edit and update all the status of the valet service at different point in time. Successful. All participants were able to update the status, although some commented that it may be a little troublesome to update the status at every point in time, but understand that it is necessary for a "live" update on the status of the customer's vehicle.

User Test Findings:

Function / Task Observation / Comments
Login/Logout & Change of Password
  • Generally easy and self-explanatory. Participants had no trouble accomplishing this task.
Accepting Valet Request
  • It is easy to view all the available requests on desktop, but zooming is required for mobile version.
  • Valet drivers are able to accept whichever job he is keen on taking.
  • Would be a bonus to be able to track the current distance and the time of travel of the designated vehicle, from the valet driver's current location.
Updating of Status
  • Generally easy and self-explanatory.
  • Some valet drivers feel that they may miss out updating the app, and it will be perfect if it is automated, tracked using the valet driver's phone to determine the status of that vehicle.

Follow-ups / Improvements Made:

Fixxlar Changes to UI valet.png


User Testing 2A

Venue: FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955)
Date: 17 September 2016, Saturday
Time: 12:00pm - 5.00pm
Duration: ~30 minutes
Number of Participant(s): 5 (Fixir administrators), 3 (Workshop administrators)

Objectives:

  • To gather feedback on the user interface of web application for Fixir Administrator
  • Identify possible usability issues with functions of Admin Module, Quotation Request Module, Search Module, Valet Module
  • Allow workshops to retest UT1, with the improved UI we have done after acceptance

Scope for User Testing 2A:

  • Logging in and out as Fixir Administrator
  • Viewing of all quotations and valet services between customers and workshops
  • Viewing, adding, updating, deleting workshops
  • Viewing, adding, updating, deleting staffs
  • Viewing, adding, updating, deleting valet companies
  • Receive feedback from the same workshop administrators with our new UI

Target Participants & Rationale:

  • Participants of this second user testing would be our sponsor (from Fixir team) for Fixir Administrator.
  • Participants of first user testing from workshops.

Method of Conduct:

Goals and Results:

S/N Goals Results
1 Participants should be able to login and logout successfully as a Fixir Administrator, and also change password. Successful. Participants tried changing the passwords and logging in with the new accounts created.
2 Participants should be able to view all quotation requests and valet services which have not been replied. Successful. All participants were able to view all the quotations and valet services without guidance. However, some commented that it does not make sense as information is too cluttered.
3 Participants should be able to view, add and edit workshops under Fixir. Successful. All participants were able to view, add and edit workshops.
4 Participants should be able to add workshop accounts. Successful. All participants were able to view all the quotations without guidance.
5 Participants should be able to view, add and edit employees. Successful. All participants were able to view, add and edit staffs including those from Fixir and workshop administrators.
6 Participants should be able to view, add and edit valet companies. Successful. All participants were able to view, add and edit valet companies.
7 Workshop administrators should be able to retest with new UI. Successful. All participants gave positive feedback that it is much clearer and easier to understand after the change.


User Test Findings:

Function / Task Observation / Comments
Login/Logout & Change of Password
  • Generally easy and self-explanatory. Participants had no trouble accomplishing this task.
Quotation Requests Overview
  • Instead of having all requests cluttered together, it may be good to segregate them by workshops, so that Fixir administrators know which workshop has not been replying the quotations.
  • Include option to view requests from a particular workshop.
  • It would be good to name the general quotations and valet services.
Workshops Tab
  • Search is very easy to use
  • Addition of workshop is generally easy too.
  • Opening hours of workshop can be tedious, but participants understand that it is only one-time off, and this gives maximum flexibility.
  • Display of opening hours is easy to read.
Staff Tab
  • Would be good to have an option to see the kind of employee a particular user is - but the greyed out buttons of "edit" and "delete" is suggestive
  • Adding of employee is relatively easy
Valet Tab
  • Valet tab is simple and easy to use
  • May be good to include a range field for Revenue Share, when adding or editing a valet shop
Workshop Administrator Page
  • Well implemented, process flow looks much clearer now.
  • Participants (workshop administrators) have a better understanding of the next step.
Miscellaneous
  • Loading of page is relatively slow

Follow-ups / Improvements Made:

Fixxlar Changes to UI UT2.png


User Testing 1 (6 August 2016)

 

User Testing 1

Venue: FIXIR’s office (BASH, #03-01, 79 Ayer Rajah Crescent, Singapore 139955) & Respective Workshops
Date: 6 August 2016, Saturday
Time: 10.00am - 2.00pm
Duration: ~30 minutes
Number of Participant(s): 6

Objectives:

  • To gather feedback on the user interface of Workshop Administrator’s web application
  • Identify possible usability issues with functions of Account Module, Quotation Request Module, Dashboard Module

Scope for User Testing 1:

  • Logging in and out as Workshop Administrator
  • Changing of password
  • Viewing and replying of quotation requests

Target Participants & Rationale:

  • Participants of this first user testing would be our sponsor (from Fixir team), and also workshop administrators (from Dynamic Mechanics, Maximus Racing, ZG Motors, Premier One etc) whom we had spoken to during our market research.

Method of Conduct:

Goals and Results:

S/N Goals Results
1 Participants should be able to login and logout successfully as a Workshop Administrator, and also change password Successful. Participants tried changing the passwords and logging in with the new accounts created.
2 Participants should be able to receive a quotation request sent by the “customer” from his/her mobile application, and reply accordingly. Successful. All participants were able to reply a quotation without guidance.
3 Participants should be able to manage all services requests. Partially reached. Some participants required guidance to navigate to "Manage Services" page.

User Test Findings:

Function / Task Observation / Comments
Login/Logout & Change of Password
  • Generally easy and self-explanatory. Participants had no trouble accomplishing this task.
Dashboard View
  • Request page may be able to replace the current dashboard
  • General dashboard may have too much information which may not be the most relevant
  • "Final Quote Accepted" may have higher precedence over "New Requests" as workshops have to prepare for the repair which will be coming in
Viewing of Specific request
  • Colour of vehicle may not be required
  • Quotation amount should be clearer (with or without GST)
  • Information is messy, with car info, service info, and customer details all mixed up
  • One Motoring link can be placed under the license plate number, for users to extract relevant vehicle information like chassis number, year of registration etc.
  • Chat button can be more prominent
Replying Estimated Quotation
  • Easy to use
  • Estimated quotation vs diagnostic price is clear
  • Have an option to reply exact price if it is clear cut
Replying Final Quotation
  • Final quotation and estimated time of completion should be keyed in at the same time
  • Estimated time should be dynamic (able to update), as accident claims may take more than 2 weeks' time, which is difficult to estimate. If there are too many walk-in/urgent cases, it will be good to have the option to contact customers to reschedule less urgent appointments.
  • Difficult to navigate to Manage Services page after final quotation is accepted by user - does not seem like the same process flow
  • Devise a way for price breakdown to show how the final quotation came about
Miscellaneous
  • On Request page, search bar should be named "search" instead of "filter"
  • Scheduling and rescheduling would be useful, with chat function as another layer of communication
  • In the long run, it may be good to have a report for each request logged in case any mishaps/conflicts arise
  • Auto-refresh is disruptive to user, as pop-up requests may be dismissed
  • Separate time and date input field
  • Sidebar should be highlighted to indicate the current page

Follow-ups / Improvements Made:

Fixxlar Changes to UI 1.png