UX Design, UX Research
Track what you eat. A calorie tracking app, where you start by entering your height, weight, and age, how much weight you want to lose over a specific amount of time. As I was using the app regularly, I found some issues that are pointed out in this case study with some possible improvement areas being laid out.
What I like about the app
Features that I found quite useful
What I don’t like
Features that felt unintuitive and need improvements
The main focus on the homepage should be on the macro tracking feature. But, it’s filled with a lot of blog posts and some posts from friends. It could be much cleaner if it was separated with tabs above or giving the ability to choose what to see.There should be a link or button to go to my profile with a single tap. The profile is important here to edit my goals. Those are my pain points with the app. I should have the ability to curate my feed.
Adding new features
From the usability testing and other user research, we keep a tracker of the features users are demanding. We can also analyze the app store reviews to find out feature requests, user pain points, and suggestions. We can add the most demanded ones to the feature backlog and plan as a potential feature. New feature ideas can also come from competitive analysis. Or, from a hypothetical point of view of a product designer or any other team members.
The challenge is to give the user more convenient ways to track with nudges and feedback to make them reach their goals faster.
Top KPIs to consider
Defining the key KPIs from the product team’s perspective can be different from the business/sales teams. By monitoring the important KPIs regularly, the team can perfectly ensure smooth and intuitive UX. Top 3 KPIs that I would choose:
After doing some research on app store reviews and competitive analysis, I found these potential features that can be added to the plan:
Now that we got some potential features, it’s time to work with feature prioritization. This should be a cross-functional team task to discuss and apply prioritization methods to choose which features and initiatives to put on the task list by voting and discussions. There are always many features that can be competing for scarce resources.
To decide the top two features from the potential ones I am using value versus Complexity Quadrant method to understand which feature has more business value and takes less effort. Also using a 2x2 Prioritization Matrix to better understand what points may be more important to both the business and the user.
After analyzing these two prioritization methods, we can see that the Health Score Test would be a complex feature to develop than the others. Also, the business value might be lower in this case. Create challenges fall into the 3rd place compared to others. So, the two features that stand out here are:
I tried to create a quick prototype on focusing the workout plans
Wasting an organization’s time and resources developing a feature that fails, can be an unpleasant experience for me as the product designer/manager. To quickly validate the features impact-ability we can do a user survey with the existing users and after getting a positive response we can do in-depth usability testing on an MVP. My validation plan for these new features is illustrated below
Audience: Online population size of 150 for a sample size of around 100
The cohort the survey will be sent to will consist of
A mix of close-ended and open-ended questions:
Survey Data Analysis
If we use any online survey tools like Google Forms or SurveyMonkey, the analysis and visualization will be easier. Assuming that the survey data is captured over Google forms and we have the data visualization ready to analyze from.
Categorizing them in terms of different data types:
In the Questionnaires, we had a couple of ordinal data questions:
We can create two histograms from these data to understand what type of users are participated and how active they are.
Questionnaires with other data types we had in the survey are:
After graphing the data for each of the sets, we can create histograms for each question (except the string data types) with their responses. From that, we will try to analyze if the majority of the users agreed/interested in getting these features.
After getting a satisfactory result from the survey we can then move on to create an MVP in a beta version of the current app. Invite a group of interested participants for usability testing, should be an iterative process until the experience is satisfactory and intuitive. To get the best result from the usability testing, the user screening process should be well planned out. We should prioritize the existing old users. There can be some new users too, as there will always be new users joining the app.
The test plan should concentrate on areas with potential usability issues and should have proper test scenarios to address them. We should start with the easier task first and then move on to critical ones. A short discussion session can also be held after the testing session.
The testing will clear up any usability and navigation issues and will give us a strong base for the next steps of finalizing and shipping the features.
The features will meet the customer goals by providing them with an all-in-one solution to stay fit and in shape. A true fitness friend. A user doesn’t have to shuffle between multiple apps to follow different plans. As an in-app feature, more tailored contents can be suggested from the user insights.
It will also significantly contribute to the KPIs for this product. Workout plans are repetitive tasks and it will engage more users daily with the app. There will be some content under premium plans as well. For exclusive workout plans and diet plans, the user will be more convinced of the conversion to a premium user. The organizational strategies will find more success with an increase in active users and subscriptions.
Originally published on Medium