Cash management SUS report
- Astrid Decrop
- Habeeb Azeez
Due date | 19 September 2024 |
|---|---|
Epic | |
Task | |
Designer | @Habeeb Azeez |
Useberry |
Document summary
This is a document containing the findings/results of the usability test for the cash management product carried out in September 2024.
Objectives
The primary objective of this unmoderated usability test is to evaluate the product's usability, focusing on three key metrics: SUS score, time on task, and success rate. This test will establish a usability benchmark for the product and inform future improvements.
Success metrics
SUS score
Time on task
Success rate
Test plan
Test environment
A remote moderated test which was performed on mobile with Figma prototypes.
Tasks
Core journey | Tasks |
|---|---|
Cash Requester Onboarding | Imagine you are a POS agent who needs cash to perform daily transactions, Using this interface, register yourself as a cash requester. |
Request for cash | Imagine you are a POS agent who needs cash to perform daily transactions, Using this interface, request for cash and also assume that you have gotten to the pick up location so you can go through the process of picking up the cash. |
Cash Supplier Onboarding | Imagine you are a business owner who always has excess cash and you need the cash mopped up easily. Using this interface, register yourself as a cash supplier. |
Attend to the requester | Imagine the requester has gotten to your location to pick up cash. Using this interface, attend to the requester. |
Participants
Participant information
Number of participants | 7 participants per journey. |
|---|---|
Selection criteria | Participants were selected based on the familiarity with the manual cash mop up process to ensure they represent the target audience. |
Recruitment process
Recruitment channels: Whatsapp groups where the requester and the suppliers are currently using for the manual mop up process.
Usability metrics and results
Success rate definition
Cash requester onboarding: This task is successful if a user can onboard themselves as a cash requester. and get to the dashboard.
Request for cash and Pick it up: This task is successful if a user can request for cash and and as well go through the process of picking up the cash.
Cash supplier onboarding: This task is successful if a user can onboard themselves as a cash supplier and get to the dashboard.
Attend to the requester: This task is successful if a user can go through the mop up process and get to the transaction completion page.
SUS score
Time on task
The time it takes participants to complete each journey. Shorter times generally indicate better usability. This metric helps to measure efficiency.
Cash requester onboarding: 54 seconds.
Request for cash: 4 minutes 19 seconds.
Cash supplier onboarding: 2 minutes 11 seconds
Attend to requester: 2 minutes 43 seconds.
The time taken criterion is not accurate because most participants paused to attend to customers, and internet issues occurred while they were testing, which prevented Useberry from loading tasks on time. Additionally, they were explaining the screens to us (moderators) to give us insight into their thought process, as it was a moderated test.
Success rate
Following the criteria listed above for success rate
Cash requester onboarding: Successful
Request for cash: Successful
Cash supplier onboarding: Successful
Attend to requester: Successful
Results
Core journey | SUS score | Time on task | Results/outcome | Comments |
|---|---|---|---|---|
Cash requester onboarding | 86.5 | 54 seconds | Successful |
|
Request for cash | 86.5 | 4 minutes 19 seconds. | Successful |
|
Cash supplier onboarding | 87.5 | 2 minutes 11 seconds | Successful |
|
Attend to the requester | 87.5 | 2 minutes 43 seconds. | Successful |
|
Post-test qualitative questionnaire feedback
Participants provided additional insights through open-ended post-test questions:
Common pain points | The product is slow {Useberry was taking time to load, hence the frustration and the need for this comment} |
|---|---|
User suggestions | They want a case where they can identify as both requester and supplier. |
Recommendations for improvement
Based on the test findings, the following recommendations are proposed to improve the product’s usability:
Design changes
To fix the UX writings to communicate the processes or flows better
Long-term recommendations
Consider a scenario where a user is both a requester and a supplier.
Conclusion
Summary
The usability test revealed that while most of the users understand the ways to navigate through the flows, there is still a need to revisit the flow for when a requester gets to the supplier’s location and this can only be improved when we get accurate data or insights when the product launches a pilot test with real life data as some of these flows are still assumptions.
Next Steps
The design team will implement the recommended changes and prepare for a follow-up usability test to measure improvements in SUS, time on task, and success rate.