Document summary
Document summary is to evaluate the usability, functionality, and overall user experience of the redesigned UI screens for critical savings flows. Ensure the screens align with customer needs and expectations, identify potential pain points, and validate the interface before full implementation.
Objectives
The objective of this test is to ensure that the redesigned Moniepoint savings UI meets customer expectations by delivering an intuitive, efficient, and user-friendly experience. It aims to validate critical savings features such as creating, topping up, withdrawing, rolling over, and breaking savings plans. By evaluating user interactions with the new designs, identifying pain points, and gathering actionable feedback, the plan ensures readiness for implementation and alignment with customer needs.
Success metrics
SUS score
Time on task
Success rate
Test plan
Test plan | https://docs.google.com/document/d/1bimOGb3iRgPprkGI5Ns8ps7tq3ffO2dMJEzbnJGht_g/edit?usp=sharing |
|---|
Core user journeys
Persona | Core journey | Rationale |
|---|---|---|
Test environment
Interactive figma prototypes of the product was the product was tested on mobile and desktop devices in a remote and unmoderated setting. However testers had the liberty to ask questions when required.
Tasks
Core journey | Tasks |
|---|---|
Create savings plan | A user with interest of creating a savings plan, has to navigate to savings sections, select a savings type, Enter details of savings, review terms and condition and then create plan. |
Top-up savings plan | A user with interest of toping up into a savings plan, has to navigate to savings sections, select savings plan, click on top-up and enter amount, enter transaction pin and confirm. |
Withdraw on maturity | A user with interest of withdrawing from a matured savings plan, has to navigate to savings sections, select matured savings plan, click on withdraw and enter amount, enter transaction pin and confirm. |
Rollover savings plan | A user with interest of rolling over a matured savings plan, has to navigate to savings sections, select matured savings plan, click on rollover, enter transaction pin and confirm. |
Break savings plan | A user with interest of breaking a savings plan, has to navigate to savings sections, select savings plan, click on break savings, enter transaction pin and confirm. |
Participants
Participant information
Number of participants |
|
|---|---|
Demographics |
|
Selection criteria |
|
Participant profiles
Participant A | Kenneth |
|---|---|
Age | 39 |
Occupation | QA Ananlyst, Akwa Ibom |
Tech savviness | Experienced |
Fintech usage | Uses mobile banking apps (GTBank, Access Bank) for daily transactions. |
Primary devices | Android phone |
Key insights | Kenneth is a QA analyst, uses gtbank to save earnings on a monthly basis, saves foe emergencies, kids school fees and towards buying a landed property. |
Recruitment process
For a savings product usability test, the recruitment process typically involved the following steps:
Defining User Profiles: We identified the target audience based on demographics such as age, income level, and familiarity with financial services, focusing on people who use or are likely to use savings products.
Criteria for Selection: Set specific inclusion criteria, such as experience with savings, digital literacy, and access to mobile or internet banking. Excluded participants who may have insider knowledge of savings product.
Sample Size: Recruited a balanced mix of users, typically 5–10 participants, ensuring diversity in age, tech-savviness, and geographic location within Nigeria.
Usability metrics and results
Success rate definition
SUS score
SUS is a standardised questionnaire used to measure the usability of a product, using a 10 questions 5-point scale to generate a score between 0 and 100, with higher indicating higher usability.
The average SUS score is typically 68. A score of 68 or higher is generally considered acceptable or better than average. Above 70 is good, and above 80 is excellent.
Time on task
The time it takes participants to complete each journey. Shorter times generally indicate better usability. This metric helps to measure efficiency.
Personal savings
Create flexible savings: Users are expected to complete this journey within 3 minutes.
Create locked savings: Users are expected to complete this journey within 3 minutes.
Create fixed savings: Users are expected to complete this journey within 2 minutes.
Break savings plan: Users are expected to complete this journey within 2 minutes.
Cancel savings plan: Users are expected to complete this journey within 2 minutes.
Top up savings: Users are expected to complete this journey within 2 minutes.
Withdraw from savings: Users are expected to complete this journey within 2 minutes.
Manage savings: Users are expected to complete this journey within 2 minutes.
Rollover savings: Users are expected to complete this journey within 2 minutes.
Business savings
Create flexible savings: Users are expected to complete this journey within 3 minutes.
Create locked savings: Users are expected to complete this journey within 3 minutes.
Create fixed savings: Users are expected to complete this journey within 2 minutes.
Break savings plan: Users are expected to complete this journey within 2 minutes.
Cancel savings plan: Users are expected to complete this journey within 2 minutes.
Top up savings: Users are expected to complete this journey within 2 minutes.
Withdraw from savings: Users are expected to complete this journey within 2 minutes.
Manage savings: Users are expected to complete this journey within 2 minutes.
Rollover savings: Users are expected to complete this journey within 2 minutes.
Create SAYT plan: Users are expected to complete this journey within 2 minutes.
Pause SAYT plan: Users are expected to complete this journey within 1 minutes.
Change SAYT withdrawal frequency: Users are expected to complete this journey within 1 minutes.
Withdraw from SAYT savings: Users are expected to complete this journey within 2 minutes.
Success rate
Personal savings
Create flexible savings: this journey is considered successful when customer is able to create the savings plan within 3 minutes with a success rate of 68% and above.
Create locked savings: this journey is considered successful when customer is able to create the savings plan within 3 minutes with a success rate of 68% and above.
Create fixed savings: this journey is considered successful when customer is able to create the savings plan within 2 minutes with a success rate of 68% and above.
Break savings plan: this journey is considered successful when customer is able to break the savings plan within 2 minutes with a success rate of 68% and above.
Cancel savings plan: this journey is considered successful when customer is able to cancel the savings plan within 2 minutes with a success rate of 68% and above.
Top up savings: this journey is considered successful when customer is able to top-up the savings plan within 2 minutes with a success rate of 68% and above.
Withdraw from savings: this journey is considered successful customer is able to withdraw from the savings plan within 2 minutes with a success rate of 68% and above.
Manage savings: this journey is considered successful when customer is able to manage the savings plan within 2 minutes with a success rate of 68% and above.
Rollover savings: this journey is considered successful when customer is able to rollover the savings plan within 2 minutes with a success rate of 68% and above.
Business savings
Create flexible savings: this journey is considered successful when customer is able to create the savings plan within 3 minutes with a success rate of 68% and above.
Create locked savings: this journey is considered successful when customer is able to create the savings plan within 3 minutes with a success rate of 68% and above.
Create fixed savings: this journey is considered successful when customer is able to create the savings plan within 2 minutes with a success rate of 68% and above.
Break savings plan: this journey is considered successful when customer is able to break the savings plan within 2 minutes with a success rate of 68% and above.
Cancel savings plan: this journey is considered successful when customer is able to cancel the savings plan within 2 minutes with a success rate of 68% and above.
Top up savings: this journey is considered successful when customer is able to top-up the savings plan within 2 minutes with a success rate of 68% and above.
Withdraw from savings: this journey is considered successful customer is able to withdraw from the savings plan within 2 minutes with a success rate of 68% and above.
Manage savings: this journey is considered successful when customer is able to manage the savings plan within 2 minutes with a success rate of 68% and above.
Rollover savings: this journey is considered successful when customer is able to rollover the savings plan within 2 minutes with a success rate of 68% and above.
Create SAYT plan: this journey is considered successful when customer is able to create the savings plan within 2 minutes with a success rate of 68% and above.
Pause SAYT plan: this journey is considered successful when customer is able to rollover the savings plan within 1 minute with a success rate of 68% and above.
Change SAYT withdrawal frequency: this journey is considered successful when customer is able to change withdrawal frequency of the savings plan within 1 minutes with a success rate of 68% and above.
Withdraw from SAYT savings: this journey is considered successful when customer is able to withdraw from the savings plan within 2 minutes with a success rate of 68% and above.
Results
Personal savings
Core journey | SUS score | Time on task | Success rate | Comments |
|---|---|---|---|---|
Rollover savings | 72 | 2m 57.4s | 83% | Journey seems easy to understand by users. |
Create fixed savings | 70.3 | 382m 56.5s | 71% | Result was skewed by a user that spent too much time answering SUS questionnaire. |
Create locked savings | 71.3 | 3m 25.1s | 60% | 40% of participant dropped off during prototype test |
Create flexible savings | 69.7 | 37m 20.8s | 60% | 33% of participant dropped off during prototype test |
Break savings plan | 70.7 | 5m 15.2s | 70% | The average time spent on the journey is a lot, a place to improve |
Cancel savings plan | 76.3 | 2m 45.3s | 60% | The low success rate may be attributed lots of drop-off at different points during the test. |
Top up savings | 78.5 | 1m 29.3s | 71% | flow was simple and straightforward based on feedback |
Withdraw from savings | 67.1 | 2m 39.8s | 88% | High success rate, but SUS score suggests journey can be improved |
Manage savings | 75.5 | 2m 7.3s | 83% | The high success rate and SUS score suggests journey was easy and straightforward for users to achieve their goals |
Business savings
Core journey | SUS score | Time on task | Success rate | Comments |
|---|---|---|---|---|
Rollover savings | 70 | 1m 35.6s | 75% | Flow looking straightforward and easy for users based on feedback |
Create fixed savings | 78 | 1m 51.4s | 83% | Journey seems smooth, no negative feedback |
Create locked savings | 72.9 | 5m 18.1s | 75% | Journey was smooth, but the time on task can be improved |
Break savings plan | 77.1 | 1m 39.7s | 100% | Journey seems smooth, no negative feedback |
Create flexible savings | 75.8 | 102m 32.7s | 71% | Some testers were stuck at some point during the test, leading to them spending too much time to eventually achieve the flow |
Cancel savings plan | 85.5 | 1m 26.9s | 100% | Journey was easy for users, no negative feedback |
Top up savings | 78.1 | 2m 1.9s | 100% | Journey was easy for users, no negative feedback |
Withdraw from fixed savings | 84.2 | 1m 30.6s | 67% | Journey seems smooths, drop offs at the start and prototype sections highly skewed the results for the success rate |
Withdraw from locked savings | 78.8 | 1m 12.1s | 86% | Flow looking straightforward and easy for users based on feedback |
Withdraw from flexible savings | 72.9 | 3m 59.3s | 75% | Journey was easy for users, no negative feedback |
Manage savings | 77.5 | 1m 23.2s | 100% | Journey was easy for users, no negative feedback |
Create SAYT plan | 76.4 | 2m 34.7s | 78% | Journey was easy for users, no negative feedback |
Pause SAYT plan | 72.5 | 32m 46.3s | 75% | A tester was stuck at the over section during the test, leading to them spending too much time to eventually complete the flow |
Change SAYT withdrawal frequency | 67.1 | 1m 56.0s | 100% | The poor SUS score indicates the journey needs to be improved |
Withdraw from SAYT savings | 85.5 | 1m 28.2s | 56% | The low success rate stems from high drop off rate after the instructions section of this test |
Post-test qualitative questionnaire feedback
Participants provided additional insights through open-ended post-test questions:
Common pain points | Some participants complained about difficulty finding some buttons, especially when it come to breaking or canceling a savings plan. Participants also mentioned that the “copy” used in some places were not clear enough. |
|---|---|
Positive feedback | Some participants talked about how short the journeys are, they can create a savings plan very quickly, top up and withdraw from a plan quickly. |
User suggestions | A suggestion that stands out was the use of better “copy” to convey messages clearer |
Recommendations for improvement
Based on the test findings, the following recommendations are proposed to improve the product’s usability:
Design changes
Overall look and feel of the product needs to be improved to give the product better aesthetics which influences customer decision while using the product.
Declutter congested sections and components to help customers make decisions better and faster, which improve success rates.
Quick wins
Update the “copy” to covey information better..
Long-term recommendations
Consider a more comprehensive redesign of the create savings plan journey, especially focusing on reducing the number of steps needed to create a savings plan.
Conclusion
Summary
The usability test revealed that while the product performs adequately in most areas, there are specific pain points related to savings plan creation journey and copy used in overall in the product. By focusing on these areas, we can significantly improve the user experience.
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.
Add Comment