Goal
MTB wanted to make a sleek and seamless e-wallet app which can provide secured payment system for their customers.
Research
Before we started designing MTB Pay, we tried to get domain knowledge via interviewing target users, doing competitive analysis of the competitors in the market, having meetings with stakeholders for their needs & wants.
- Research began by understanding how customers currently handled banking tasks and daily digital transactions.
- There were fraud cases rising locally within e wallet platforms, so we had to take responsibility in creating a secured digital platform for users and MTB.
- Users also wanted a simple one which can help efficiently in their daily life.
After thorough analysis of research data, I defined problems by thinking with "How Might We" approach. I also created user personas that represented target users for MTB Pay. An early stage of Information Architecture was designed as per brainstorming process and it evolved and refined more as the we dived into design phase.
Design
Brainstorming was back and forth since we were going with the Agile methodology. Before diving into a design tool, I had the opportunity to ideate by sketching. Some ideas got approved, some got rejected. But most of the ideas that solved users' pain points came into the design phase.
On design phase, there was five parts -
- Crafting low-fidelity wireframes - this phase was the most cost-effective, so that iteration could be done as much as necessary as per stakeholder's feedbacks.
- Creating brand visuals - MTB Pay was designed from the scratch and it required logo, brand identity, colors and slogans.
- Building a design system - It aims to uniform the user interface specs and act as an adaptable system of guideline & components, helping our team and developers to effectively and efficiently. I also wrote design documentations and annotations necessary for each usage.
- Polishing high-fidelity wireframes - Approved low-fi wireframes were transformed into high-fi user interfaces with the newly built design system.
- Creating prototypes - In order to present and get early feedback from stakeholders and developers, prototypes were created which also validated the user flows.
Testing
- Initial staging app was tested for UX performances and identifying issues. I wrote test plans and test cases to ensure that our product met the stakeholder's high expectations.
- Upon delivering a complete design work for MTB Pay, I had the chances to test with potential users. I did moderated testings - instructing users and watching closely how they reacted. Initial feedback was quite great although there were some concerns about displaying data. I took notes, shared with my team and re-iterated on finding solutions for the user's feedbacks.
- After multiple rounds of design changes and implementation, the product was successfully launched into the market.
