Case Study Week 3: YUKA
Third week and new challenge… Adding a new functionality to a successful app!
Among all our possible options we chose YUKA because we consider that it is an application that despite being based on a very interesting idea, its execution and presentation to the users it is not attractive enough to retain them.
ROLE
In this case, the team consisted of three members: Elena Martin Pereira, Adrian Barrado and myself. The decisions were made quickly and directly, and everything really flowed very well into our final proposal.
All the work was done between August 31st and September 4th, 5 days of work.
RESEARCH
This time we wanted to focus not only on users who use YUKA (or have downloaded it at some point) but also on all those people who, being digital users, are concerned about their nutrition.
From the interviews and surveys conducted, we learned that as a rule, when they wanted to buy a product, they compared the different brand labels and ended up choosing the product according to these labels. This process, although it was simple for those who had some food and nutrition education, was tedious because it required a lot of time to make the comparison.
The application so far solved very well everything that had to do with informing and educating users, but did not contemplate that users could be interested in products that were outside the recommendations of the app.
With the problem already in mind and all the information we obtained, we developed our User Persona, the User Journey and the User Scenario, which helped us a lot to put ourselves in our user’s shoes and to launch ourselves into the search for a solution.
SOLUCIÓN
We decided that the app needed a feature that would allow its users to easily compare the products they are interested in at a glance.
The next steps after all the UX work were aimed at better understanding what we wanted the brand to represent and how we were going to approach the new functionality while maintaining the essence of YUKA.
We started with a Low Fi that brought together the best ideas that we as a group had shown in our respective Crazy Eights and which came in line with the initial Brainstorming. From there we made a Moodboard, discovered the main Brand Attributes and created the Style Tile.
PROTOTYPE
The prototype shown below began as a Low-Fi that we tested on various users until we reached the final High Fidelity version that we presented.
In the prototype we can see how the user scans a product and from the card itself accesses to compare it (they could also do this from “Compare” on the tab bar).
He tries to compare another product but the EAN is “broken” so he accesses to another new functionality: product recognition by photo. Next you will see the comparison, which filters and orders according to the user main interest, the calories.
On the last screen we see how the user accesses his history to check a comparison that he had already made.
NEXT STEPS
Much remains to be developed and tested in terms of comparisons, so the first thing that should be done is to spend time improving this functionality. We need to know how would more than 3 comparisons appear, how do we manage to show the data that the user is interested in, and also if we have enough information to implement product detection without scanning the barcode.
In addition, other possible functions to be developed emerged from our interviews and surveys, such as the possibility of detecting and warning the user that the scanned product is not suitable for him/her in the event of having some type of intolerance (gluten, lactose, fructose, sorbitol…), so another interesting line of development is presented here.
LEARNING
A new week and a new learning experience. Leaving the for me “always present” learning from the teams diversity, this week has served me to realize two things:
First, you can’t fall in love with an idea and follow it until it crashes, you have to fall in love with the problem and work from there.
The second… generally the option that seems the simplest is the one that best solves the problem of your users. Sometimes it is not necessary to invent the wheel, but it is enough to listen and empathize to reach the optimum solution.
Thanks for reading! If you prefer to read this article in Spanish click here. Let’s work together! Drop me a line at its.carfish@gmail.com
