Gravity

product design & product management

A grid of app screens showing an Supply Chain Finance loan app

OVERVIEW

What is Gravity

Gravity provides a decentralised identity platform based on blockchain technology to enable secure and easy data sharing. This can be applied to different use cases. One of them is supply chain financing (SCF).

Gravity’s supply chain finance solution builds trust among financial service providers, suppliers and shopkeepers through data sharing and unlocks financing opportunities in Africa.

We help micro & small retail businesses access finance by enabling them to set up a financial profile that they can use to apply for business loans. These profiles allow lenders to improve the credit scoring of merchants and thus lower the interest rates.

The Problem

After realising the potential of using the decentralised data-sharing platform to enable access to working capital, Gravity wanted to build a solution tailored to supply chain finance.

Users & Audience

Shopkeeper: Has a micro/small business and is interested in buying goods on credit

Distributor/Supplier: Sells FMCG goods to retail

Lender: Gives digital micro loans

Roles & Responsibilities

As the only designer on our team at the time, my responsibilities were to design the UI and UX for this specific use case of the application. This meant leading and executing the entire design process from start to finish.

Scope & Constraints

The aim of this project was to understand the FMCG supply chain and it's actors, determine a process flow for the SCF solution and design and implement the user interface that the small businesses would be using.

Constraints were to provide good UX while still abiding to W3C standards/decentralised identity standards. In addition, the difficulty was that we needed to build a product that can provide credit quickly and seamlessly fits in the delivery and sales process in this fast moving sector without wasting anyone's time.

Process

User Interviews

As the first phase of the design process and after an extensive desk research on digital loans and FMCG supply chain, I conducted a survey with 117 micro- and small businesses. I wanted to get a better understanding of the problem, in particular the shopkeeper’s needs around access to working capital.

I also got in touch with various FMCG distributors as well as digital lenders to make sure their pain points are also taken into account and needs are met.

What did I find?

Shopkeepers:

Access to working capital is a big challenge
Only 29% of distributors sell goods on credit
99% of shops interviewed keep records, however hardly anyone digitally

Distributors:

• Distributors have a digital purchase history of each and every customer
Payment is usually on delivery
Time of interaction at point of delivery is max 5min

Lenders:

Lenders don’t extend affordable loans to small businesses because they can’t access their business transaction data and use it for credit scoring
More data leads to a higher accuracy in credit scoring which results in lower interest rates
Good KYC is important for them

This validated our hypothesis that by leveraging the purchase history distributors have about their clients and making this transaction data available for lenders, we can create a win-win-win situation for all parties. Shops get affordable loans, distributors sell more goods and improve their customer relationships and lenders are able to tap into a new market at a lower risk.

Personas

Based on the research and interviews, I identified and drafted user personas for the 3 key user types:

Digital lender
Shopkeeper
Distributor of FMCG goods

User Journey

After detailed discussions with lenders, distributors and shopkeepers, I mapped out the user journeys for each actor within the ecosystem. After that I was able to bring them together into one overall user journey that determined the final layout of our solution:

Wireframes

Then, I focussed on creating the shopkeeper interface. A mobile application that would allow them to get loans and buy on credit.
I designed low fidelity wireframes to be able to get an overview and try out many different design options. Through the wireframes I was able to define the specific flows and basic features of the application. This also helped me to notice early on that we have to compromise and look for work arounds that would improve user experience but still allow us to remain a decentralised identity platform.

What were the main flows?
Sign up (creation of digital identity on blockchain)
Identity verification (National ID + phone number)
Add credit-relevant data to the wallet (KYC, Mpesa statement, purchase history with distributor)
Loan application (sharing of data with lender)
Buy goods on credit (paying for goods with the loan)
Loan repayment

Usability Testing

For the first round of usability testing I designed clickable prototypes and tested the flows with shopkeepers nearby the office. The feedback I received was good. The shopkeepers mentioned it was easy to use and straightforward.

A second round of usability testing was conducted after the feedback had been incorporated from the first test. By now the designs had been implemented and shipped to production. I joined one of the sales agents of our FMCG partner on their route and tested the flows with 8 shops.

I encountered quite a few issues in particular during the sign up flow:

The sign up flow took 10-15min for many of the shops which was extremely long.

The reasons for that were:

Account creation i.e. wallet deployment on the blockchain took very longIdentity verification failed for a lot of users. The selfie was not accepted and picture of ID was not accepted, therefore the identity verification could not be completed successfully

This was not good. Firstly, the sign up is a crucial flow where a lot of mobile users can be lost. Secondly, a busy shopkeeper needs to be able to sign up within minutes in between clients.

Outcome & Learnings

We managed to lay out the concept for a functioning lending ecosystem and design and implement one interface for one of the 3 actors.

I learnt that it’s important to replicate the real environment as closely as possible during controlled testing. When testing the product with the shopkeepers directly, the majority of them were not able to carry out the identity verification flow and the wallet deployment. This was due to the type of browser version or android version they had. After implementing the app I had only tested with my device and my colleagues’ and co-workers’ devices and then proceeded to go and test with the shopkeepers directly.

Having an additional controlled testing round after implementation of the product at the office with test users that had similar devices to the end users would have spared us and the shopkeepers the time and frustration during the testing on the ground.

Have A Project?