← All work

Case study 02 · Fintech inside a B2B2C app

Retailer loan: rewriting a bank’s language for the shop counter

A loan for small retailers whose businesses were hit by COVID-19 and Sri Lanka’s economic crisis. The backend could only take English, so every word had to work for someone reading in their second language.

Live · 2023 Moderated usability testing
My role
Flow design, prototype, test planning and moderation
Timeline
Oct 2022, design to agreed changes in 2 weeks
Product
Retail Hub, with Dialog’s finance arm
Constraint
English-only backend

01

A loan, inside the app retailers already use

Retailers use Retail Hub every day to sell reloads, activate SIMs and take bill payments. Many had been hit hard by COVID-19 and then the economic crisis. Dialog’s finance subsidiary proposed a loan, applied for in Retail Hub and repaid automatically from the retailer’s One wallet, to help them get back on their feet.

The borrower is the retailer, not their customers. That sounds obvious, but it turned out to matter.

  1. 1 · Start

    Find the tile · NIC and One wallet number · pick a number · OTP

  2. 2 · Configure

    Loan amount · repayment period

  3. 3 · Identity

    NIC front and back · selfie

  4. 4 · The form

    Personal · contact · employment · other info · guarantor

  5. 5 · After

    Confirm · submitted · video verification call · guarantor confirms by SMS

15 steps from the home screen to a guarantor’s confirmation. Most of the effort sits in stage 4.

The constraint

English only

Retail Hub is available in Sinhala and Tamil, but the loan system behind this flow could only handle English. Translation wasn’t an option, so the English itself had to be simple enough for most retailers to follow.

02

Testing in the shops, not the office

I designed the flow, built a high-fidelity prototype from the development-ready screens, then planned and moderated the tests. The prototype covered the happy path only, so the study tested comprehension and expectations, not edge cases.

Retailers
5
Cities
5
In person
1
Remote, live
4

One session ran in a retailer’s shop in Pettah, Colombo. The other four ran live and remotely, with regional supervisors setting up each retailer on site. Every session was moderated by the UX team.

Four questions

Understand

Can they make sense of the form fields and guidance?

Anticipate

What do they expect from the feature?

Perceive

How do they feel about it?

Use

What usability issues get in the way?

03

A good headline, and what was underneath

The headline

5/5found the loan tile and started on their own
5/5said the feature would help them
4/5could understand and manage the flow alone
0major usability issues

Underneath

They could get through the form. They were misreading what it asked.

1 understood comfortably 3 stuck on a few fields 1 held back by language

Most were surprised a guarantor was needed. Some felt Dialog already knew their business, so why ask? Tax and PEP questions came from nowhere. One retailer thought he’d be lending to his customers.

04

One field, three answers

The field

Monthly income

Retailer A read it as

“My Dialog sales each month”

Retailer B read it as

“My whole shop’s income”

Retailer C read it as

“All of my income”

The field got answered every time, just with three different meanings. A task-completion test would call that a pass. For a lender, it’s three different numbers.

That became the lens for the rest of the analysis: not only can they fill it in, but what do they think it means. The same pattern showed up in “Surname” and “Other names as per NIC”, words that looked familiar but were read differently.

05

Ten words that got in the way

Some terms were simply unfamiliar banking language. Others looked familiar and were read the wrong way, which is harder to spot.

Unfamiliar

Eligible Guarantor Mailing address Secondary contact no US tax payer Politically exposed person Disbursement

Familiar, but misread

Surname Other names as per NIC Monthly turnover

How the wording changed

Before
After
You are eligible for a loan upto Rs.100,000
You can take a loan up to Rs.100,000
You are required to provide a guarantor
You need a guarantor for this loan
I have a different mailing address
My current address is different
Address line 1 · Address line 2
House no · Street address
Secondary contact number
Alternative contact number (optional)
Average monthly turnover
Average monthly income
Guarantor contact
Guarantor mobile number
1 month after loan disbursement date
1 month after loan received date
Recovered through your One wallet
Deducted from your One wallet

06

Six changes, beyond the words

I proposed every change and took them to a forum of the business owners, who agreed them. Words were only part of it. These six fixed how the screens behaved.

Retail Hub home screen with yellow feature tiles. An arrow shows the “Loan” tile renamed to “Retailer loan”.

A · Say who it’s for

“Loan” became “Retailer loan”

One retailer read the tile as a way to give loans to his customers. Two words fixed the audience.

Retailer loan entry screen with NIC number, One wallet number and a CAPTCHA. An arrow shows the “Login” button changed to “Continue”.

B · Don’t make it feel like a new account

“Login” became “Continue”

Retailers were already logged in to Retail Hub. A second “Login” made them unsure which number to use. Now it reads as the next step: “Enter your NIC number & One wallet number to continue.”

Loan configuration screen before and after. Before: plain text saying “You are eligible for a loan upto Rs.100,000.00” and “You are required to provide a guarantor”. After: a highlighted panel at the top saying “You can take a loan upto Rs.100,000.00” and “You need a guarantor for this loan” with an info icon.

C · Put the deal-breaker first

The guarantor rule moved up and stood out

Retailers skipped it or only saw it when asked, then got surprised later. It now sits in a highlighted panel at the top, in plain words.

Personal details before and after. Before: NIC and mobile number shown as greyed-out input fields. After: shown as plain text, “NIC number: 987654321V” and “Mobile number: 077 567 5643”, above the title and name fields.

D · Read-only should look read-only

Disabled fields became plain text

Retailers tried to fill in the greyed-out NIC and mobile fields, or asked if they had to enter them again. Showing them as “NIC number: 987654321V” ended the question.

Personal details before and after. Before: the OTP-verified mobile number shown as fixed text. After: an editable mobile number field with the hint “Provide a mobile number to call you”.

E · Design for the shop

Ask for a number we can actually call

The number that passed OTP is often a SIM inside a reload machine. It can receive a code but no one answers it. The form now asks: “Provide a mobile number to call you.”

Application submitted screen before and after. Before: “Please keep your NIC and billing proof documents with you.” After, highlighted: “Please keep your NIC and a Water bill with you.”

F · Say exactly what to prepare

“Billing proof” became the actual document

The success screen now names the document the retailer chose earlier, such as “Please keep your NIC and a Water bill with you”, ready for the video verification call.

Figma · Research board

See the findings, every screen and each change side by side

The research matrix, the before and after screens, and the decisions as they were agreed.

Open in Figma

07

Asking less, not just asking better

Rewording a confusing question helps. Removing a question nobody needs to answer helps more. Retailers kept saying Dialog already knew them, and they had a point.

A

The “Other information” step was removed from the app. US tax, PEP and account-purpose questions confused most retailers, and some answered “No” without understanding them.

B

Account purpose fixed to “Loan repayment”. The account only exists to repay the loan, so the retailer shouldn’t have to choose.

C

Employment questions challenged. Retailers coming into this flow are already vetted by Dialog, and some saw these questions as redundant. I asked whether they could be fixed values or pulled from the retailer’s existing profile.

08

What was agreed, and what stayed open

Agreed

15 changes
  • Tile renamed to “Retailer loan”
  • Login → Continue, with an instruction line
  • Eligibility and guarantor message simplified and highlighted
  • Disabled NIC and mobile fields → read-only text
  • A separate number to call the retailer on
  • Mailing address → current address
  • Specific address labels, for retailer and guarantor
  • Alternative contact number, now optional
  • Turnover → income
  • Other information step removed
  • Account purpose fixed to loan repayment
  • Guarantor contact → guarantor mobile number
  • Disbursement → received
  • Repayment and fee copy simplified
  • The exact billing document named on submission

Raised, not decided

Open
  • Also place the loan in the side menu
  • Replace CAPTCHA with a check that the request came from Retail Hub
  • One “Name as per NIC” field, split during the verification call
  • Pull employment details from the retailer’s profile
  • An early settlement option
  • A loan without a guarantor for established retailers

Logged with the business owners so they weren’t lost.

09

Outcome

Design → agreed
2 weeks
Changes agreed
15
Live
2023

The design was finalised in October 2022 and went live around September 2023, once the backend was ready. [ADOPTION OR APPLICATION NUMBERS, IF YOU CAN SHARE THEM]

What I took from it

A clean usability result can hide a comprehension problem. Now I ask people what a field means, not just whether they can fill it in.

For Homey

Why this matters at Homey

Conveyancing is full of the same kind of words. “Disbursements” is on every quote, and onboarding asks about source of funds and politically exposed persons. Buyers and sellers aren’t lawyers, and many are doing this for the first time.

The approach carries over: test what people think a question means, cut what you already know, and tell them exactly what happens next.

Case study 01

A scalable KYC module for a TRCSL-regulated telco

← Back to home ↑ Back to top