MTN App

myMTN App

Sponsored by: MTN Ghana

With MyMTN app, users can top up airtime, purchase data bundles, pay bills and much more. The app also ensures customers have access to information about MTN’s products and services.

*To comply with NDA, some details in this case study have been modified or omitted. The content reflects my own work and views, not necessarily those of MTN Ghana. Linked materials may point to evolving live products or prototypes by MTN Ghana.*

Project roles:

Low - high fidelity wireframe, secondary research, user flows, journey mapping.

Team:

Dora Opare, Kelvin Tyron

Tools:

Balsamiq, Figma

Overview

The process of topping up airtime from an MTN mobile network can be an arduous and time consuming process. In a typical case, the user must either buy a scratch card or top up from USSD. This could include finding scratch card vendors, following prompts and feedback from USSD to top up an account.

Challenges

Design Challenges

How might we help make the topping up airtime process more efficient for users?

Research

Secondary Research Round 1

With an interest in Application Programming Interfaces (APIs) we dove into secondary research centered around the instances where APIs can improve top up challenges. We sought to assess the level of maturity of existing technologies used by Telcos to enhance the process of airtime top ups from a mobile network. Our research resulted in the following insights:


1• Value depends on integration: Significant factors such as APIs and database communications impact expectations and perceived value.


2• Scattered industry adoption: While an increasing amount of people are adopting the use of application driven interfaces, the application of these interfaces are wide-ranging in only a mere handful of industries

myMTN app
Ideation

Creating concepts

We then began ideating, creating different concepts to work from. To narrow down to our concept that we would move forward with, we considered the following criteria:


Feasibility
We wanted to chose the concept that aligned the best with the current capabilities of the platform.


Need
We wanted to make sure there was a need for this type of product that was currently not met


Research

Secondary Research Round 2

Based on our criteria, we ultimately decided to narrow down helping users of the MTN mobile network that would love to top up airtime from their device. We conducted further secondary research on this space and came to the following insights:


1• Prolonged Turnover Rate: Users often have to move to and fro looking for scratch card vendors, which makes it difficult to renew their airtime once exhausted, prolonging the process.


2• Time Intensive Process: Current solution which is the USSD,although incorporates automaticity, has a time limit for a top up transaction, therefore, requiring users to dial the prompt over and over once they reach the time limit and USSD times out.

User journey

Before beginning the design process, we used a journey map to walk through our user’s needs and the interactions that they would have with the product.

 User journey

Laurine runs an online business. Business is booming but Laurine is now having trouble topping up airtime to stay connected with clients.

User journey

With myMTN app, Laurine is able to top up airtime easily on her mobile network and to other networks. When the airtime runs out, she goes to her app and taps airtime.

User journey

She then selects the network and amount to which she would love to top up airtime for. (MTN, Vodafone, AirtelTigo, Glo)

User journey

Laurine can decide to then buy for herself or gift the airtime to a friend or family member.

User journey

Laurine can make payment with MTN Mobile Money (MoMo) which is embedded within the app. She can check her balance before making payment as well.

User journey

After successful payment, Laurine or the recipient is credited with the airtime purchased.

Requirements

Technical Requirements

myMTN uses an Application Programming Interface (API) to complete the task of enabling users to top up airtime when they run out. A request is sent to the API which takes care of the airtime top up at receiver end and deduction at sender side.

Prototyping

We developed a low fi prototype and went on to test with potential users. Through testing the prototype, we reached three insights to drive our final design direction.


01• User Approval is paramount : As a requirement for forming trust, users want to give their final approval

02• Worry Free : Users feel that the product takes some of the pressure off because the top up process becomes less involved allowing them to focus on their client’s needs.

03• Precision Matters : While automation can create ease, any potential for error causes users to worry about accuracy.

low fidelities
Features

Final Product