Showing 3 Result(s)

MapleBank

Empathize

Define

Ideate

Prototype

Test

These are the steps of Design Thinking: a set of cognitive, strategic and practical procedures used by UX designers. The steps that are grayed out will not be covered in this case study.

Description

Creating a smooth onboarding flow for a Canadian neobank.

Overview

MapleBank is a Canadian neobank that wants to break into a new market in Canada. We were tasked with creating a new product that answered a critical financial need of the new market based on five provided personas. We were to focus specifically on users that aren’t already customers.

The ultimate goal of the project is to attract new users to MapleBank with a new product and a great onboarding flow.

maplebank cover

Problem statement

Our problem statement is users have savings goals that they find it difficult to manage and reach with confidence.

How might we help users reach their goals in a realistic timeframe so that they feel empowered?

How might we help users who are eager to reach financial goals track the progress in a simple manner so that they feel confident?

Additional details

Our primary persona was Monique, a woman in her 30s with multiple income streams and many saving goals.

Our team was 3 people, fully remote. We communicated through Discord, Zoom and had all our shared files on Miro. We also had our teacher as an advisor. We all helped with all parts of the project. My main contributions were:

  • Project management: ensuring we reached our goals in time
  • Main Figma person: in charge of setting up our components and styles to ensure consistency in the layout
  • Script writer: in charge of writing our usability test script

This project was done in a very short timeline of 2.5 weeks. This was possible because MapleBank provided us with the research already done. Since we started at the Ideate stage, we were able to get this project done within the time frame.

Overview of steps taken

  • Analyze data provided
  • Initial assumptions
  • Competitive research
  • Persona
  • Journey map
  • Storyboard
  • User Flow
  • Paper wireframes
  • Creating medium fidelity wireframes
  • Usability test (3 users)
  • Design critique (3 users)
  • Usability test (3 users, bias)
  • Prototype building
  • Final usability test (3 users)
  • Final prototype

Full case study

We started by analyzing the data provided to use by MapleBank. We were provided with five personas, as well as statistics about the current population using MapleBank.

Following this, we wrote down some of our initial assumptions surrounding Canadian neobanks and what we’d need to do to stand out.

  • “Clear and easy registration forms” meant having clear instructions and a clear call to action.

  • To stand out in the neobank space, we need to offer customization options throughout the app.

  • To get users excited about savings we would need to find a way that users can easily visualize progress to make it more tangible.

  • Individuals already have savings set aside and would be using our app as a means to visualize their savings plan.

  • Neobanks are not very popular in Canada

  • Individuals that use Neobanks want the user experience to be different than if they were to sign up with commercial banks (i.e less tedious forms, easier approval) 

 

Once we had finished that, we also did a competitive analysis on similar companies, like Koho and Wealth Simple. We wanted to see what other banks and neobanks were doing to see how we could stand out in the banking space. What we realized by doing the competitive analysis is that most banks provide very little information about their products before creating an account. This can be frustrating for users who aren’t already aware of what those products are.

We then started defining the problem. To do so, we chose a primary persona based on the provided personas. We opted to focus on Monique, a woman in her 30s with multiple income streams and many saving goals. We mapped a journey map to learn more about how she would interact with our app. We also created a storyboard to see her frustrations, and how our app could solve the problem. 

Insights gained:

Reviewing Moniques persona, we were able to see that one of her main points was that she was saving for numerous goals. Standard banking apps usually have a savings account, but don’t offer the ability to project savings goals.

Insights gained:

Plotting our journey map is a great way to see the steps taken for users to discover our app, all the way until they decide to use it. This journey map allowed us to see that an important factor would be including customizations. It also showed that we’d need to be able to showcase the benefit of MapleBank right away.

We reviewed our initial assumptions after this, and were able to validate three of them:

 

  • “Clear and easy registration forms” meant having clear instructions and a clear call to action

  • Users will be drawn to our app because we offer a lot of customization options throughout the app

  • To get users excited about savings we would need to find a way that users can easily visualize the process to make it more tangible

At this point, we established what our key criteria would be for creating a successful app. We considered users reaching their dashboard for the first time (setting up a goal and creating an account on the way) was the “aha” moment. Our goal was for users to reach this stage in under 2 minutes.

Following this we started ideating: we worked on a user flow to start to see what the user onboarding would look like. We highlighted in gray our happy user flow, but we made sure to provide the necessary screens incase we had an unhappy user. 

Following this, each of us created low-fidelity paper wireframes. We then discussed and opted for the frames that best fit what we wanted to create for our primary persona.

We turned the chosen frames into medium fidelity wireframes and started our user testing.

We started by doing a usability did on 3 users. We had a script and asked questions that gave us both qualitative and quantitative data.

After reviewing the feedback, we created higher fidelity wireframes.

We did a design critique with 3 fellow designers to get an idea of how users felt about our color and font choice.

From this point, we finalized our UI kit. Most of the feedback on our design was very positive, but we did hear that we were using too much green. It was based on this design feedback that we opted to change our CTA color to orange: orange is very visible so it helps users know where to click, and it also evokes feelings of enthusiasm and energy.

Our other color choices were based on color psychology:

  • We opted for green as our pimary color as green is known to be easiest on the eyes and it has a relaxing effect. That’s a mood we’d love our users to get into when checking their savings goals!
  • We chose blue for our headlines: it’s known to have a calming and tranquil effect and darker blues like this one stimulate the mind into thinking more clearly.

We ran a second usability test in class with 3 new users, which we recognize is bias as we were asking fellow UX designers to review our app. In this case, we had prototyped our wireframes and asked users to complete specific tasks.

This round of feedback gave us a big insight: when we asked users to add funds to a specific goal, they naturally went to the goal page (despite the fact that “add funds” was a navigation option). Based on this, we gave users the option to add funds directly from the individual goal pages.

We applied additional changes based on this test and prepared our prototype for our final test. Our final test was a usability test of 3 new users with a script that we changed to include additional prompts and questions based on the new features and elements that had been added.

In all of our usability tests, users were able to get to the “aha” moment in under two minutes. We were hugely proud that we were able to get users to the “aha” moment this quickly.

The big idea

We added gamification to our app by including badges. User was encouraged to take steps to receive new badges: anything from adding additional funds to their goal, to setting up their profile, to completing their goal. This feature was very popular in our user tests as they felt that they accomplished something regularly by using our app.

Cool thing

We didn’t want users to drop off immediately if they weren’t convinced they needed to save, so we added a button on the welcome screen titled “Inspire me!”. Clicking on this would take users to a screen that showcased why saving is such a good habit to get into, and showcased the features MapleBank has to offer.

Freshly Chopped

Empathize

Define

Ideate

Prototype

Test

These are the steps of Design Thinking: a set of cognitive, strategic and practical procedures used by UX designers. The steps that are grayed out will not be covered in this case study.

Description

Adding in a delivery feature to a recipe kit bookmarking app.

Overview

Freshly Chopped is a recipe kit bookmarking app. They are having issues with returning users so they asked us to incorporate delivery of the recipe kits into the app.

The purpose of this project was to add delivery to a pre-existing app (you can find the Figma file for the original app here). The ask was for users to be able to continue bookmarking recipes as they had done previously, but also give them the option to order the meal kits as well. Part of the ask was for users to be able to generate a grocery list in the app as well if they wanted to buy the ingredients for a recipe kit themselves.

freshly chopped cover

Problem statement

Freshly Chopped wanted to find a way to include delivery in their app to increase return users, without losing the users who wanted to keep using it as a bookmarking app.

How might we design a simple and engaging user experience to encourage busy users to make our app their top choice for meal kits, recipes and grocery delivery?

Additional details

We were provided with 2 primary personas, and after analyzing them, we opted to keep the “busy mom” persona who we named Georgia. We also slightly changed the primary persona: our research showed that the users who would be using this app are busy and would be using the app more for convenience and time-saving reasons.

We were a team of four for this project, fully remote. We stayed in contact via Facebook, used Miro for brainstorming and shared files, and have a shared Figma file for creating our wireframes. We all participated in each step of the process, but I would say I excelled in the following areas:

  • Project management: ensure the team had a clear idea of what needed to be done by when. 
  • Figma person: helped the team refine the Figma file while retaining the style of the existing app.
  • Presentation creator: developed the core of the presentation to ensure we presented our ideas in a clear and concise way.

This project had a short timeframe of 4 weeks. Our research wasn’t as in-depth as we would have liked for that reason, but nonetheless we were able to develop the Freshly Chopped app in a very cool way.

Overview of steps taken

  • Reviewed data from client
  • Initial assumptions
  • Competitive analysis
  • User interviews
  • Refined persona
  • Empathy map
  • Journey map
  • Storyboard
  • User flow
  • Crazy 8s
  • Low fidelity wireframes
  • User testing (4 users, in class, bias)
  • Medium fidelity wireframes
  • User tests (4 users, script)
  • Final medium fidelity prototype

Full case study

For this project, we started by reviewing the data and personas supplied to us by Freshly Chopped. We wrote down some of our initial assumptions, including:

  • To order groceries on a recipe app, there would need to be some sort of motivation to do so (loyalty points, discounts, etc).
  • Ordering groceries online, users must be able to customize quality (example for meat, ability to get organic or local).
  • Users ordering groceries are likely to be health conscious (going to the gym/counting macros etc).
  • Busy users buy groceries online.
  • Users lack trust of other people picking their produce due to being wary of the quality.
  • Users like to cook and share recipes with others.

 

We started some competitive analysis to see what our biggest competitors were doing. We did competitive analysis on 8 competitors (each person working on this project did 2 companies). In each case, we wrote down their strengths, weaknesses, great design features, and opportunities for us. We color coded our analysis to be sure we could keep track of what comments applied to which competitor.

 

 

Competitive analysis insights gained:

While doing our competitive analysis, we found it was frustrating to not be able to see much information about what these apps were offering without first creating an account. We also found the quotes and testimonials from users were popular for users who didn’t already know the brand.

Following this, we re-reviewed the data provided to us by Freshly Chopped. From here, we developed a script to interview users to find out more about how we could solve the problem. We ran 4 user interviews of busy people in the 30s. We all took notes of the feedback we received, and compiled the information together into a master empathy map.

The user interviews gave us a lot of information about how people feel about recipe kits, bookmarking apps, and groceries. We used the information to refine our primary persona, as well as to build a journey map, a storyboard (which allows us to consider and communicate a sequence of states), and a user flow (how a user would move through our app). 

Persona insights gained:

Following our user interviews, we found that our persona needed some refining. Our research showed that the users who would be using this app are busy and would be using the app more for convenience and time-saving reasons.

Journey map insights gained:

A journey map helps to see the steps Georgia would take to learn about and download our app. Our journey map showed us that we needed to showcase from the start how much our app has to offer. We also realized that users wanted to be inspired.

 

The user flow was particularly helpful to see how we could integrate the delivery feature into the app as seamlessly as possible. We highlighted the new screens in gray so that we knew the scope of work we had to design for.

At this point, we were able to review our initial assumptions to see what had been validated (or invalidated). The assumptions that were validated were:

  • Ordering groceries online, users must be able to customize quality (example for meat, ability to get organic or local).
  • Busy users buy groceries online.
  • Users lack trust of other people picking their produce due to being wary of the quality.
  • Users like to cook and share recipes with others.

 

Now that we understand more about our users, we started ideating. We began with crazy 8s, a brainstorming tool where you come up with 8 ideas in 8 minutes. After brainstorming, we individually created low fidelity paper wireframes. We compared our designs as a team to find that we had very similar ideas. We turned our low fidelity wireframes into medium fidelity wireframes: because Freshly Chopped already had a brand style, it was straightforward to add additional parts to the app.

We ran a total of  3 user tests.

For the first test, we interviewed 4 participants. We walked them through the app and asked for feedback on what they liked/disliked so that we could improve.

Our second user test was in-class with 4 participants which we recognize is bias since the testing was done on fellow UX designers.

For our third user test, we asked 4 participants survey questions and asked them to do actions to measure success rates. For example, we asked users to add a meal kit to their cart. For this test, we took scores and watched users attempt the prompts.

1 %

success rate when asking user to add a meal kit to their cart​

1 %

of ecommerce traffic are mobile users

1 %

trust rate for consistent branding 

Usability test script

  • How much more likely are you to purchase from an app that has both meal kits and grocery shopping option?
    • Scale of 1-10 (1 = no way, 10 = very likely)
  • How much more likely are you to order meal kits through an app than a website?
    • Scale of 1-10 (1 = no way, 10 = very likely)
  • Previously through the app we weren’t able to order meal kits nor grocery. On a Scale of 1-10 (1 = no way, 10 = very likely), how much more likely will you buy through the app then if it was only available on a website?
  • If the app didn’t have a meal kit and grocery option would you have visited the website to verify this option?
    • Scale of 1-10 (1 = no way, 10 = very likely)
  • Would you trust a company that’s inconsistent between the app and website?
    • Scale of 1-10 (1 = no way, 10 = very likely)
  • Now that the app is consistent with the website would you trust them more?
    • Scale of 1-10 (1 = no way, 10 = very likely)
  • Looking at this app, what do you think of the designing process?
  • On a Scale of 1-10 (1 = terrible, 10 = amazing), how would you rate it?
  • Please show me what you’d do to edit your grocery list.
  • Please show me what you’d do to order a meal kit/add a meal kit to cart
  • Rate this ordering experience on a scale of Scale of 1-10 (1 = terrible, 10 = amazing)

The big idea

The ask for this project was to add the ability for users to have recipe kits delivered. Our user interviews showed us that people don’t feel great about meal kits. Of those we talked to, they would much rather be able to choose their groceries themselves. 

Our secondary research confirmed this: we found that only 3% of the population is committed to using a meal kit service. 69% of Canadians have never even tried one. Since the beginning of the pandemic, ordering groceries online has boomed: 49% of Canadians are ordering their groceries online.

Based on these insights, we decided to design a delivery feature but also to add a grocery shop to the app.

Cool thing

We added a “What’s in your fridge” feature that allowed users to enter some key ingredients that they had on hand to see recipe kits that included those ingredients. This allowed users to user items that were already in their fridge, thus avoiding waste – one of the key pain points for why users didn’t like recipe kits.

Pizzeria Diavolo

Empathize

Define

Ideate

Prototype

Test

These are the steps of Design Thinking: a set of cognitive, strategic and practical procedures used by UX designers. The steps that are grayed out will not be covered in this case study.

Description

Allowing users to order a custom pizza in under 3 minutes.

Overview

Pizzeria Diavolo allows users to customize their pizza in any which way. They asked us to create an app that would help users create a customized pizza in under 3 minutes.

The purpose of this project was to create low fidelity paper wireframes of an app that would allow users to order a custom pizza in under 3 minutes.

pizzeria diavolo cover image

Problem statement

Busy users need a way to order customized pizza in under 3 minutes.

How might we help busy users customize a pizza in a timely manner?

Additional details

While I didn’t develop a persona for this project, I did interview a participant named Felix who fits the description of who we’re designing for: a full-time employee in his mid-30s who often has to work long hours.

I worked on this project by myself, so I handled all facets of the empathizing, defining, and ideating stages. This included writing an interview script, creating low fidelity paper wireframes, and plotting journey and empathy maps. 

This project had a short timeline of 2 weeks. This was possible because we were only creating low-fidelity wireframes to submit.

Overview of steps taken

  • Initial assumptions
  • Competitive analysis
  • User interview
  • Journey map
  • Empathy eap
  • User flow
  • Ideating
  • Paper wireframes
  • Test
  • Final paper wireframes

Full case study

To start of this project, I wrote down some initial assumptions I had. It’s important to capture these to see which of our assumptions were validated or invalidated based on our research. My initial assumptions were:

    • Something that slowed down users was being overwhelmed by options
        • Too many options meant users didn’t know what to choose

    • Users didn’t like to have to log in/create an account before browsing for options

I also did competitive analysis on other pizza restaurants to see what was working for their apps. I also wanted to identify any pain points that we wanted to avoid in creating our app. Something I realized doing this was that it was popular for pizza restaurants to have a featured deals page with combos.

Based on these assumptions and what I found competitors were doing, I wrote down interview questions to get more information from a participant that matched the user we were designing for: a full-time employee in his mid-30s who often has to work long hours.

I ran a 30-minute interview with a user to get an idea of the pain points and habits they may have when it comes to ordering a pizza online. This interview allowed me to plot a journey map and an empathy map. 

Journey map insights gained:

Journey maps help to see the steps Felix would take to learn about and then download our app.

What we realized when creating the journey map was that Felix wanted to be able to build off existing pizzas. Add bacon to Margherita. Add mushrooms to Meat Lovers. We also realized he wanted to know what other people recommended. He wanted suggestions based on what other users were ordering.

Empathy map insights gained:

Empathy maps allow us to gain deeper insights about our users.

While plotting the empathy map, we noticed that some of his pain points were:

  • Not being able to see his total before going to checkout
  • Not being able to save customized products
  • Sometimes there were too many options and he was left feeling overwhelmed

Reviewing our initial assumptions, one was validated and one was not. The assumption that was validated is that “Something that slowed down users was being overwhelmed by options”. This was validated due to our empathy map. 

Next I worked on ideating. I created a user flow to see how users would interact with our app.

Now that I knew the screens that were needed, I started with doing some crazy 8s just to get some ideas down on paper. Crazy 8s is a quick brainstorm tool where you come up with 8 concepts in 8 minutes. It helps us think outside the box, and just get down whatever idea comes up. After reviewing these, the best options that allowed users to achieve the goal of ordering in under 3 minutes were refined, still keeping them on paper since it’s the very beginning stages of the project.

We received in-class feedback on our paper wireframes. At this stage, I turned them into medium-fidelity wireframes to be able to better present the idea. This wasn’t technically a project requirement, but it did not take long to create the medium fidelity and I wanted to be able to showcase a digital version.

The big idea

The feedback we received from our interview was that they wanted to be able to see what others were eating as that would help them choose what to get themselves. For that reason, we split the ingredients options into tabs. The left tab option showcased the standard ingredients (cheese, meat, vegetables) and right-hand tab showed that ingredients were by chosen by other users.

Cool thing

A portion of the app that we developed is the Pizza Roulette. This feature allows users to “spin the pizza” to receive a randomly customized pizza. They are listed the ingredients and are then able to edit the pizza or add it to their cart as is. This feature is fun, unique, and who knows what kind of pizza you’ll end up with!