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-73

Designer

Williams Andem

Useberry

Insert linksWithdrawal, Purchase, Deposit, End-Of-Day Summary, Purchase, Transaction History

Document summary

Insert brief summary here.

...

  • 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.

...

Test plan

POS Test Plan

Core user journeys

The primary goal for the POS channel team for this FY 2024 is to generate 5x the cost of producing a POS terminal in revenue. For this reason, the following user journeys - not all, that play a major role in achieving this goal, were identified and scenarios created for usability testing:

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.

Retail business owner

Make a purchase transaction

This journey is traditional to this retail businesses as it’s their primary method for collecting payment

POS Agent

Make a withdrawal transaction

This journey was selected because its one of the most important aspect and revenue generator for a POS Agent

Retail business owner & POS Agent

Accept a POS transfer

Journey allows businesses receive transfers on their terminals

Retail business owner

View history & print receipt

This journey is integral for transaction integrity and transparency

POS Agent

Make a deposit transaction

One of the goals of Agency banking is to ease banking by extending banking services to areas where physical banks are not present for convenience. This journey is essential for facilitating that convenience

Retail business owner & POS Agent

Print End-Of-Day Summary

This journey was selected because Business owners rely on this for bookkeeping

Test environment

The test was unmoderated and conducted remotely using interactive prototypes - emulating the Topwise MP35P POS terminal device. The interactive prototypes were set up on Useberry tests - allowed Users test via their mobile & web browsers. At the end of each core journey tests, participants were presented with post-test questionnaires as well a SUS questionnaires.

Tasks

[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

Make a withdrawal transaction

A customer has come to you to withdraw money. What would you do?

Note: imagine this to be a POS terminal

Make a purchase transaction

A customer comes to your store, buys some items and wants to make payment for those items using a debit card. What will you do?

Note: imagine this to be a POS terminal

Accept a POS transfer

Accept N20,000.00 from Lawrence Hassan

Note: imagine this to be a POS terminal

Make a deposit transaction

A customer has come to you to deposit money into a beneficiary account. What would you do?

Note: imagine this to be a POS terminal

[journey name]

[journey name]Print End-Of-Day Summary

It's the close of day and you want to print the summary report for the day for bookkeeping, what would you do?

Note: imagine this to be a POS terminal

Participants

Participant information

Participant A

Chinedu

Age

35

Occupation

SME owner (fashion retail)  

Number of participants

Indicate the total number of users involved (5 - 8 participants Participants per journey).

Demographics

Include relevant demographic information such as age range, gender, location, experience level, job role, familiarity with the product, or other factors depending on the target audience.

Selection criteria

Describe the criteria used for selecting participants. Were they existing users, new users, or a mix of both?

Participant profiles

Note

Delete this info panel, this is only for guidance.

If applicable (otherwise delete section), provide a few short participant profiles to offer context - see examples below.

  • 18 - 34 years

  • Lives in Nigeria

  • Business owner/Sales Rep/Others

Selection criteria

  • Good internet speed

  • Have used or not used a POS terminal

  • Lives in Nigeria

  • Has basic tech knowledge

Participant profiles

Participant A

Taiwo

Age

31

Occupation

Sales Manager (Hospitality) & Business Owner (Cosmetics)

Tech savviness

Moderate

Fintech usage

Uses mobile banking apps (GTBank, Access Bank) for daily transactions and a POS terminal for customer payments. Prefers platforms that offer quick, reliable transfers and clear transaction histories.  

Primary devices

Android phone (Tecno Camon 16Oppo

Key insights

Chinedu Taiwo is a seasoned Sales person having experienced working in both Retail and Agency banking businesses. Her day-to-day heavily relies on his POS terminal for business operations and uses fintech apps to track transactions. He is often frustrated by network downtime with POS systems and values transparency in fees. Easy-to-read transaction reports and the ability to quickly reconcile daily sales are critical for his businesscollecting payments and facilitating transactions. She prefers platforms that offer quick, reliable transactions and dispute resolution.

Participant B

HalimaEmmanuel

Age

27 32  

Occupation

Market traderBusiness Owner (Retail)

Tech savviness

LowHigh

Fintech usage

Uses mobile money apps like OPay and PalmPay for personal savings, transfers, and accepting payments from customers. Not particularly tech-savvy, but uses these services due to their ease of access and lower transaction fees compared to traditional banks.

Primary devices

Android phone (Infinix Hot 10)

Key insights

Halima needs simple, straightforward fintech solutions with minimal steps to complete transactions. She Moniepoint banking for business transactions. He uses Moniepoint primarily due to the ease of onboarding and the ability to use his business name as the account name

Primary devices

IPhone 13 Mini

Key insights

Emmanuel relies on fast and seamless fintech solution for collecting payments. He values reliability, especially when receiving payments from customers. She finds features like SMS confirmations and immediate access to funds critical for trust in the service.

Participant C

TundeSophia

Age

4024

Occupation

Corporate accountant (mid-sized firm)  Sales Rep

Tech savviness

High

Fintech usage

Uses digital banking platforms and business fintech solutions for managing payroll, supplier payments, and invoicing. Regularly interacts with multiple banking platforms for business transactions.  Has avid experience using POS terminals. She uses Palmpay POS terminal to collect payments

Primary devices

Windows laptop, iPhone 13IPhone 8

Key insights

Tunde requires fintech solutions that streamline business transactions and offer integration with accounting software. He values features like automated invoicing, bulk payments, and detailed reporting, but he finds it frustrating when banking platforms lack API integrations with their business software. Efficiency and robust security features are critical for business operations.Platform reliability, dispute resolution, efficient and responsive customer service is primary for Sophia

Participant D

AmakaOla

Age

2227

Occupation

NYSC corp member (service year)  Director (Beauty & Cosmetics)

Tech savviness

High

Fintech usage

Primarily uses personal traditional banking apps like Kuda and ALAT for saving, budgeting, and personal transfers. Also utilises fintech apps for peer-to-peer transfers and mobile payments.for paying for inventory purchase and collecting payments from customers

Primary devices

Android phone (Samsung A32)IPhone 15

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 D

Babatunde

Age

50

Occupation

POS operator  

Ola is particular about platform reliability and instant transaction reconciliation most especially when she is showcasing her business in a fast-paced marketplace like Trade fairs. Ola prefers simplicity to ease the learning curve for new employees

...

Participant D

Haruna

Age

36

Occupation

Business Owner (Retail & Agency)

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. Uses Moniepoint POS for retails and agency transactions. He uses Moniepoint because of platforms

Primary devices

Android phone (Itel A56Tecno)

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

Note

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.].

  • Screeners were used to ensure participants met the following criteria:
    - regularly interact with [specific technology/product. type]
    - other criteria related to the specific test such as being a current customer, not being a customer, using a competitor’s product, etc.

He uses Moniepoint POS because of the platform’s network reliability, transaction dispute resolution and speedy reconciliation. Whilst he is able to resolve some frequent issues that arise in the course of collecting payments, for other issues, he relies on his account manager

Recruitment process

Initially sent out a participant recruitment questionnaire but later reached out potential participants that fit my criteria via cold texting and physical visit. Each participants were privately messaged and sent a document containing journeys that a particular to their business types (ie. Retail, POS Agents). To get an holistic view the usability of the Moniepoint POS, I opted to reach out to not only Moniepoint POS customers, but also POS customers of other Banking services as well as persons that have not used the POS terminal before.

Usability metrics and results

Success rate definition

...

Delete this info panel, this is only for guidance.

Success criteria:

...

A task is considered successful if the participant completes it as intended within the defined parameters, without assistance, and within a reasonable time frame.

...

Measurement:

  • Success rate will be calculated as the percentage of participants who successfully complete each task according to the predefined criteria.

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 time it takes participants to complete each journey. Shorter times generally indicate better usability. This metric helps to measure efficiency.

  • [insert journey name]Make a withdrawal transaction: users should/are expected to complete this journey within 1 minute.

  • Make a purchase transaction: users should/are expected to complete this journey within X minutes1 minute.[insert journey name]

  • View history & print receipt: users should/are expected to complete this journey within X minutes1 minute.[insert journey name

  • ]Make a deposit transaction: users should/are expected to complete this journey within X minutes.[insert journey name]1 minute.

  • Print End-of-Day Summary: users should/are expected to complete this journey within X minutes1 minute.[

  • insert journey name]Accept POS transfer: users should/are expected to complete this journey within X minutes1 minute.

Success rate

[designer to define success for each journey]

  • [insert journey name]Make a withdrawal transaction: this journey is considered successful when [specify].[insert journey name]if the participant is able to complete a withdrawal transaction within 1 minute or less.

  • Make a purchase transaction: this journey is considered successful when [specify].[insert journey nameif the participant is able to complete a purchase transaction within 1 minute or less.

  • View history & print receipt]: this journey is considered successful when [specify].[insert journey name]if the participant is able to complete this journey within 1 minute or less.

  • Make a deposit transaction: this journey is considered successful when [specify].

  • [insert journey name]: this journey is considered successful when [specify].

Results

Note

Delete this info panel, this is only for guidance.

SUS score

The average SUS score was [insert score], with [brief interpretation: e.g., this score falls within/above/below the industry benchmark].

Analysis: the SUS score reveals [positive/negative] aspects of user satisfaction, particularly related to [insert key findings].

Time on task

The average time to complete key tasks was [insert time].

Analysis: tasks such as [task 1] took longer than anticipated due to [insert reason], indicating potential usability challenges.

Success rate

The overall success rate was [insert percentage]. This indicates that [insert percentage of participants] were able to successfully complete the core tasks without assistance.

Analysis: certain tasks such as [specific task] had a lower success rate due to [insert reasons], while others were completed with high efficiency.

...

Core journey

...

SUS score

...

Time on task

...

Success rate

...

Comments

...

[journey name]

...

e.g. 60

...

1m 30s

...

%

...

Brief key feedback or observation for this journey

...

[journey name]

...

Brief key feedback or observation for this journey

...

[journey name]

...

Brief key feedback or observation for this journey

...

[journey name]

...

Brief key feedback or observation for this journey

...

[journey name]

...

Brief key feedback or observation for this journey

...

[journey name]

...

Brief key feedback or observation for this journey

...

[journey name]

...

Brief key feedback or observation for this journey

Post-test qualitative questionnaire feedback

Note

Delete this info panel, this is only for guidance.

Post-test questionnaire:

After completing the tasks, participants will be asked additional targeted questions to gather specific feedback on their experience. These questions will be presented BEFORE the SUS questionnaire, for example:

  • Was there anything confusing or frustrating about the sign-up process?

  • How easy or difficult did you find the sign-up process?

  • Did you encounter any difficulties in reading or understanding the text or labels during the tasks?

  • Were there any features or elements that stood out as particularly helpful or problematic?

  • Did you experience any challenges with the colour scheme or visual elements?

  • Do you have any additional comments or suggestions for improving this experience?

These questions will help uncover specific areas of concern or satisfaction that may not be fully captured by the SUS score alone.

  • if the participant is able to complete this journey via the transfer method or card transfer method within 1 minute or less.

  • Accept POS transfer: tthis journey is considered successful if the participant is able to complete this journey within 1 minute or less.

Results

Core journey

SUS score

Time on task

Success rate

Comments

Make a withdrawal transaction

97

29.6s

100%

  • Users found the withdrawal process generally intuitive and easy

  • They had no difficulty in reading and understanding the texts during the task as they were legible and bold

  • There was no challenge with the colour scheme and had no additional comments

Make a purchase transaction

86.7

34.6s

83%

  • 1 user dropped off due to network

  • Users found the purchase process generally intuitive and easy

  • One user explained that it was easy because an account manager had already explained how it works

  • The “Default Account” option when selecting an account type, particularly stood out as helpful because that way customers are not asked for their account type all the time

  • They had no difficulty in reading and understanding the texts during the task

  • There was no challenge with the colour scheme and had no additional comments as everything was straight forward

Accept a POS transfer

85.4

28.8s

100%

  • Users found the process generally intuitive and easy

  • They had no difficulty in reading and understanding the texts during the task

  • There was no challenge with the colour scheme and had no additional comments

View history & print receipt

85

29.1s

100%

  • Users found the process generally intuitive and easy

  • They had no difficulty in reading and understanding the texts during the task

  • There was no challenge with the colour scheme

  • Whilst there was complaint generally, one user suggested we explore simplicity for the dashboard user interface

  • 1 user suggested a more simplified user interface for the dashboard. Made reference to the MPOS style UI

Make a deposit transaction

93

1m 4s

100%

  • Users found the process generally intuitive and easy

  • 1 user found it confusing as there were two features with the transfer name

  • They had no difficulty in reading and understanding the texts during the task

  • There was no challenge with the colour scheme

  • Took 4s longer than expected due to Participants network

Print End-Of-Day summary

74.2

2m 44.5s

100%

  • 1 user expected the feature to be in “admin”, didn’t think it would be in “services“.

  • Users had difficulty finding the feature suggesting that it shouldn’t be in “services“

  • The difficulty find the feature led to the extended time in completing the task

Post-test qualitative questionnaire feedback

Participants provided additional insights through open-ended post-test questions:

Insert suggestions for improvement or areas where users struggled but offered solutions.

Common pain points

List any recurring issues, frustrations, or confusion that participants mentioned.

Positive feedback

Summarise any positive comments about the product or specific features.

User suggestions

  • Users found it difficult find the “Print End-Of-Day“ of day feature

  • Difficulty navigating back to the home screen

Positive feedback

  • Users like the text legibility

  • The “Default Account” option when selecting an account type, particularly stood out as helpful because that way customers are not asked for their account type all the time

  • Generally, there was no challenge with the colour scheme

User suggestions

  • Find a better place for the “End-of-Day feature“

  • Some suggested that the feature should be visible at first glance

  • A more simplified user interface for the dashboard (reference to the MPOS style UI)

Recommendations for improvement

Based on the test findings, the following recommendations are proposed to improve the product’s usability:

Design changes

...

[Task/feature]: revise [UI component, workflow, etc.] to streamline the user journey and reduce time on task.

...

  • Revise the current POS terminal architecture

  • Explore navigations for the POS terminal

  • Naming explorations for some features

Quick wins

  • Minor adjustments to [insert feature or task] that can be implemented without major development effort.will be made:

    • Navigation back to home on the screen

Long-term recommendations

  • Consider a more comprehensive redesign of [specific user journey]the POS terminal app, especially focusing on [insert issue]the architecture.

Conclusion

Summary

The usability test revealed that while the product performs adequately in most areas, there are specific pain points related to [specific feature]. By focusing on these areas, we can significantly improve the user experience.

...