The second I have been working on as part of the UX/ UI Design Bootcamp was an for a Wellness Institute.

This time we were working individually and we had to follow a 2 weeks sprint to come up with a solution. My first task here was to understand all the key deliverables and create a roadmap in order to meet all the deadlines. For this task, I follow the kanban methodology.

So let’s get down into business!

Business and Competitive Analysis

In order to understand better the industry I made an online research to see who are the current players out there and how are they tackling the problem of quitting.

User Research

After gathering some insights and some numbers about the problem itself and the current solutions available I wanted to understand better who was my user, to see how they cope with trying to , which methods are they using and which are the reasons that lead them to . As I couldn’t find any SME (Subject Matter Expert) to interview and get some valuable insights from an expert I sent out an Online Survey to help me define my target group. I found out that “people between 27 and 45 who are willing to quit, have tried at list one app but only 3% succeed”. Once I narrowed my target group I conducted several user interviews to get some qualitative data and gather more insights about why they didn’t succeed and what was their experience with smoking apps.

Once I gathered all the information, I created an Empathy Map where I clustered all the data and found behaviors and patterns that were being repeated.

User Persona

Once I had all my empathy map properly cluster I came up with Charlotte my user persona.

Smoking App User Persona

Charlotte recently started a new job as a UX designer in Berlin. She’s excited to bring a user-focused perspective to the design department but nervous because it’s a new challenge for her. She always commits to her goals but there is one which she has not been able to commit: quitting smoking.

She wants to quit but…

  1. Hard to find the motivation
  2. Feels alone in her battle
  3. Can’t keep her mind busy when feeling the craving

Her experience with Smoking Apps

  1. Too many charts
  2. Little engagement
  3. Not challenging

User Journey

Once I had my User Persona defined I “recreated” a day in my User Persona. I drew what is known as User Journey to identify Charlotte’s pain points and find the opportunities to build a solution to her problem. At the end of the day, Charlotte’s pain points represent her future interaction with our product/solution.

Ok, so let’s do a little recap, while the EMPATHIZE & DISCOVERY phases were all about diverging to understand what the nature of the problem is, the DEFINE stage is all about converging your findings to give the project direction. Now is time to define the problem.

Problem Statement

According to the NWI, the smoking rate has decreased 10% in the last year. However, 35% of people who still smoke have tried to quit but ended up failing due to a lack of motivation and stress factors.

They find it hard to quit because they feel alone in their battle as most of their close circle smoke and they have an associate routine to smoking.

There is an opportunity to help the people that are willing to quit smoking. Our goal is to keep them motivated and make them smoke fewer cigarettes,

Hypothesis Statement:

We believe, providing them with ways to measure their success in their fight against tobacco and keep them busy when they feel the craving will help them to control the addiction. We know we are right if we manage to increase the number of days without smoking and fewer cigarettes per day.

Now that we have defined the problem and we have a clear idea of who our users are (their frustrations, goals, and motivations), we will use a series of tools and exercises that will help us generate ideas on how to design a product that will help users accomplish their goals. Let start with the Ideation part! Something that helped me a lot during this phase was the crazy 8 ideation exercise. At this point, I was feeling blocked and not able to think about anything! Thanks to this exercise I was able to start imagining how the app would look like following Charlotte’s needs. But before jumping to the low fi prototype lets define our MVP.

User Stories, Prioritization, and MVP

After finding the opportunities through Charlotte’s User Journey I started writing the User Stories that will define my MVP. In order to build my MVP, I used MOSCOW (Must Have/Should Have/Could Have/ Won’t Have) prioritization model to define which user stories/features will have my MVP. As we had a very tight schedule

User Stories Prioritization

What I wanted to transmit in the app was something completely different from what the competitors are doing out there. After talking with a small sample size I found out they were not very happy with the normal way of use of the quitting apps. The feedback I got was:

  • Not very challenging
  • Not Engaging
  • Very boring, a lot of text!

I used this feedback to define my key features.


  • Onboarding & profile set up
  • Progress
  • Milestones & Shares
  • Penalties
  • Keep me busy ( Keep me entertained while feeling the craving)

Information Architecture

So I survived the first step of the project! Now let’s start the second step. We have defined our MVP, so we now know which are the features that our app will need to have in order to satisfy our user needs but also the business needs. We started creating the Sitemap. A Sitemap (also known as Organization Structure) is used to show the relationship between pages in a site. Sitemaps are also used to document the organization, navigation, and labeling found in a site. A Sitemap depicts where the pages “live” in the platform, but not necessarily the order users will see them in.

After the Sitemap, we are ready to define our user flows. User Flows show how the user will interact with your product and which pages they will see in order to complete a specific goal.

At this stage, we are ready to start working on our low-fi prototype. Once we have it ready we will be able to test it. Testing so early in the process gives us the possibility to find out problems and obstacles that our users encountered while using the app and will allow us to apply these changes in the design. Here you can see the first low-fi prototype.

I did it! The first week of design sprint was accomplished! Now I am ready to review the plan for the second design sprint. I want to point out that normally you don’t go through all this process alone and that you have a team that is supporting you. But I have to admit it has been a great challenge to go through the whole process during these 2 intense weeks. But now let’s stop talking and let’s go back to the project!


Mid Fidelity Wireframes

I validated my low-fi prototype and now is time to start working in the mi-fi wireframes. I will consider all the feedback gathered from the first round of testing. Here you can see the layout. Remember that the Design Thinking Process is ITERATIVE. You will find yourself going back and forth between the different stages as you work through the problem and design the solution.

Smoking App: Mid-fi Wireframes

Visual Design

It’s Monday again and that means that we just started our second design sprint week! This week we will need to cover the following: moodboard, brand attributes, style tile, design system, high-fi app.

What I wanted to transmit in the app was something completely different from what the competitors are doing out there. After talking with a small sample size I found out they were not very happy with the normal way of use of the quitting apps. The feedback I got was:

  • Not very challenging
  • Not Engaging
  • Very boring, a lot of text!

That’s why I decided to go for this brand identity. I wanted to focus not on the smoking itself and why is bad to smoke but more on the benefits of quitting. Kind of making them forget about their cravings and challenging them. Remember my target group was willing to smoke and very goal oriented.

Once I kind of found my attributes and orientation I start working on the high-fi prototypes.

UX Case Study: Quitting Smoking

Project Summary

Now will be the time to go out there and test the final prototype and keep improving the design and the functionalities. We should constantly test and refine our product as time passes by. The process is not over!

Hope you like it! Thanks for reading 🙂

Source link


Please enter your comment!
Please enter your name here