Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Due date

19 September 2024

Epic

Jira Legacy
serverSystem Jira
serverIdd0d6ed90-58df-3426-9502-a536b04baef8
keyDS-34

Task

Jira Legacy
serverSystem Jira
serverIdd0d6ed90-58df-3426-9502-a536b04baef8
keyDS-71

Designer

Alison Eyo

Useberry

Insert links

Document summary Insert brief summary here

This document outlines the efforts undertaken and results obtained in verifying the usability of core user journeys within the Moniepoint transfer feature.

Objectives

As part of our ongoing efforts to improve the user experience and align our products with strategic goals, we have identified the System Usability Scale (SUS) score as a key performance indicator (KPI) for user satisfaction. Additionally, we will be tracking two other critical usability metrics: time on task and success rate. These metrics will provide a comprehensive view of how well our product supports primary user goals across web and mobile platforms.

...

  • SUS score

  • Time on task

  • Success rate

Test plan

Note

Delete this info panel, this is only for guidance.

Add link to test plan for example; https://docs.google.com/document/d/1IJSsiOfUI6HE8F8_SOF7Xuc0oS7dTuSG-O8YZwqNhb0/edit?usp=sharing

...

Test plan

...

Attach the original test plan for reference - insert link

Core user journeys

Note

Delete this info panel, this is only for guidance.

  • Identify and define core user journeys relevant to different user personas.

  • Focus on tasks critical to user satisfaction and aligned with the product's value proposition.

  • Include a rationale for why these journeys were selected and how you selected these.

[insert text here]

Persona

Core journey

Rationale

Name of persona + description

Name of the core journey + description

Why this journey was selected + how you selected this journey

Name of persona + description

Name of the core journey + description

Why this journey was selected + how you selected this journey

Name of persona + description

Name of the core journey + description

Why this journey was selected + how you selected this journey

Name of persona + description

Name of the core journey + description

Why this journey was selected + how you selected this journey

Name of persona + description

Name of the core journey + description

Why this journey was selected + how you selected this journey

Name of persona + description

Name of the core journey + description

Why this journey was selected + how you selected this journey

Name of persona + description

Name of the core journey + description

Why this journey was selected + how you selected this journey

Test environment

Note

Delete this info panel, this is only for guidance.

Outline the approach you took - wether it was moderated or unmoderated test, remote or in-person, which platform it was performed on (mobile, web, POS), interactive prototypes or testing account, etc.

[insert text here]

Tasks

Note

Delete this info panel, this is only for guidance.

Provide details on the tasks participants were asked to complete. Ensure tasks align with real-world scenarios that users of the product would encounter.

[insert text here]

Core journey

Tasks

View history & print receipt

A customer that recently made a transaction of N15,000.00, has come to ask you for a re-print of that receipt. Proceed to give the receipt

Note: imagine this to be a POS terminal

Test plan

Transfer Test Plan

Core user journeys

Persona

Core journey

Rationale

Adebayo (35y/o)
Small business owner who frequently makes payments to various suppliers and contractors

Initiating a transfer to new recipient

This journey represents 90% of transfers, making it critical for user satisfaction and app utility. It was selected based on comprehensive analysis of user behavior data.

Emeka (40y/o)
Manager who regularly pays the same set of vendors for his company

Sending money to a saved beneficiary

While less common than new recipient transfers, this journey is important for understanding how the app supports repeated transactions and user convenience

Chinwe (28 y/o)
Values automated financial management

Setting up a recurring transfer

This journey is crucial for users who need to make regular payments. It was chosen to evaluate the app's ability to handle more complex, long-term transfer setups.

Fatima (32y/o)
Executive assistant who manages multiple accounts and transfers

Managing/deleting a recurring transfer

Essential for providing users control over their automated transfers. It was selected to assess the flexibility and user-friendliness of the recurring transfer feature

Oluwaseun (45y/o)
Business accountant who keeps detailed records of all financial transactions

Reviewing transfer history/downloading statements

Critical for user trust and financial management. It was chosen to evaluate the app's transparency and ability to provide clear transaction records.

Amina (38y/o)
HR Professional responsible for processing company payroll

Performing bulk transfer to multiple recipients

Important for business users who need to make multiple payments efficiently. It was selected to assess the app's capability to handle complex, multi-recipient transfers

Test environment

The initial plan was to conduct moderated tests using a live testing account.
However, due to geographical constraints, this approach would have limited our participants to users from only one of the 36 states.

To overcome this limitation, we opted for unmoderated, remote testing using mobile interactive prototypes accessible on both mobile devices and web browsers. This method allowed for broader geographical coverage and more diverse participant inclusion. Upon completing each core journey test, participants were asked to answer a series of questions and indicate their satisfaction level, providing valuable quantitative and qualitative feedback.

Tasks

Core journey

Tasks

[journey name]

[journey name]

...

Participant D

Amaka

Age

22

Occupation

NYSC corp member (service year)  

Tech savviness

High

Fintech usage

Primarily uses personal banking apps like Kuda and ALAT for saving, budgeting, and personal transfers. Also utilises fintech apps for peer-to-peer transfers and mobile payments.

Primary devices

Android phone (Samsung A32)

Key insights

Amaka prefers fintech apps that offer budgeting tools and savings features. She values gamification and rewards systems, such as cashbacks and referral bonuses, to increase engagement. Her main frustration comes from long transaction processing times or unexpected app downtimes. Security and user-friendly onboarding are important factors for her trust in the app.

Participant DE

Babatunde

Age

50

Occupation

POS operator  

Tech savviness

Moderate

Fintech usage

Relies heavily on mobile money apps like Paga and Moniepoint to run his POS business, facilitating cash withdrawals, deposits, and transfers for customers. He also uses traditional banking apps for reconciling the daily balance.

Primary devices

Android phone (Itel A56)

Key insights

Babatunde’s biggest concern is the reliability of the fintech app or platform, especially in high-traffic areas. He prefers platforms with low transaction failure rates and quick settlement times. Instant customer support is crucial when POS systems encounter issues, and he values platforms with lower transaction fees.

Recruitment process

...

Delete this info panel, this is only for guidance.

...

Participants were selected based on specific demographic criteria to ensure representation of the target audience.

...

Recruitment channels included [insert recruitment methods: online panels, customer database, etc.].

...

[insert text here]

Usability metrics and results

...