Client:
Lastlap
Company:
Pepper Square
Product:
Monkey React Mobile app
Team:
2 UX Designers, 1 Graphic Designers
Duration:
8 months
Duration:
8 months
Understanding business requirements via multiple meetings/sessions with clients.
Researching to understand user behavior, lifestyle, and relation with the finances
Drafting the information architecture and flow of the system to establish a smooth navigation
Delegated research & design documentation to the team
Develop solutions in the form of wireframes, UI design, interactive prototypes, and iterations based on feedback.
Coordinating with the content, Frontend teams to develop solutions in a streamlined process.
Set up regular client meetings, send regular deliveries, monthly timesheets to the client, and communicate feedback to the team
Demo by client team on Finance industry and how people are handling currently and how their company is doing.
Company Vision and strategy
Success criteria
Team Introduction
Project kickoff
Explored and tested the existing web app and mobile application with dummy data provided by the client for a week along with our team.
Got an in-depth walk-through of the current app from the CEO and the Co-Founders, one module for each day, went on for a week and a half. We cleared our silly doubts with the team as we were new to this field and collected all the feedback they received in the past.
Started evaluating the existing app through Heuristic data points based on severity using Jacob Nielsen's Heuristic principles.
Narrowed down the insights from the Heuristic Evaluation that needed to be taken care of in the app.
Jotted down SWOT of the existing product and did market research on related competitors in the same space.
Interviewed around 12 people with Open and closed-ended questions on financial knowledge, money management, tracking expenditures, and any existing method or app they use related to finances, using an empathy map. Documented the Goals, Pain points, and Insights derived from the interview.
Cohort groups and User stories
Based on distinctive user patterns and behaviour, personas were segregated into different cohort groups.
We documented how the app will help to solve their issue and mentioned the possible interaction for that problem on the app.
Created an engagement model to personalize app behavior for different user groups to retain them and encourage frequent engagement.
First, we listed down all the features required along with the client team and team members rated them based on importance for Phase 1, took average on all the feature ratings, and finalized it.
Defined the app structure and user flow based on the personas and prioritized features
We ideated on paper for internal team feedback before jumping on to digital wireframes so that we save time.
Converted the best ideas to wireframes and tested with users before moving into design.
What we expected users to do and what they were doing were totally different for few flows, so user feedback helped a lot in this stage.
Logo Design
Fig 1:
Ideas that create brand recall
Fig 2:
Usage of the logo in various platforms and devices.
Defined style guide - Typography, UI elements, Fonts, and Colors.
Fig 1: Created a map for the reward system along with the UX team to know which activities across the app can be treated as rewards. It includes both positive and negative rewards.
Fig 2: From Fig. 1, we bifurcated the rewards into levels, which include its benefits based on difficulty, to include gamification in the app.
Every level is indicated with a name and a monkey badge. Illustration on the badge is decided based on the Evolution of monkeys
Initiative: Explored Invision tool for its advanced features and suggested product manager and IT team on using it for Design delivery management through kanban board and also for assets transfer for developers.
Reason to choose: Single tool to manage multiple tasks for us as well as client, saved a lot of time and money in using multiple software like Zeplin, Trello etc..
Challenge: Learning a new tool and teaching the team and client to use it.
We researched on the evolution of Monkeys/Apes and came up with the level name and character for the same.
Few among them are:
Gray Langur, Marmoset, Lion Tamarin, Squirrel Monkey, Guenon etc.
We know most of them are not.
Our education system teaches us how to get a job, but not how to make money.
But Monkey is at our help. Introduced e-Learning Module to educate ourselves on finances and Community module to discuss and share our knowledge on finances with the world.
Building an education module was tricky, as it was not a linear way of learning. Every learning kit has multiple domains to cover, so users need to go through multiple domains to learn a single topic. So we had built a matrix (as shown below) to understand and iterate on it to convey the idea and design on it.
Collaborated with Video creation partner: It was my first experience in collaborating with an external video team in bringing education videos that are in sync with the mobile design and interaction.
Brainstormed and defined all the minute elements that go into creating a discussion in the community.
List of features and their usage
Personas who use it
List of roles each persona has
Outcome: This documentation helped us to take approvals before the design and filtration of elements.
Community - Wireframes and Final design
Conducted usability testing with target audience after designing the app.
I created the testing setup using my GoPro camera and Tripod which was connected to laptop which was used to monitor and record.
Final designs
Journey
Ask Expert
Calculator
Planner
Timeline
Dashboard Design
Extended version of Reward system
User testing with app updates
Importance of understanding product in deep before starting with any research/design process
How to save time by testing wireframes with users before designing gives valuable feedback
Being in sync with the team for consistency of work when multiple people are involved in similar activity
Learned the importance of Documentation and Prioritization
Planning tasks and activities beforehand
Partner closely with cross-functional members to define user needs and product requirements.
Deep diving into a new domain
Learning and adapting new research methods