<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Y-Dan Bui on Medium]]></title>
        <description><![CDATA[Stories by Y-Dan Bui on Medium]]></description>
        <link>https://medium.com/@ydanbui?source=rss-44fe5b6834e4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KEALx215wvOIoRnVd3DDFQ.jpeg</url>
            <title>Stories by Y-Dan Bui on Medium</title>
            <link>https://medium.com/@ydanbui?source=rss-44fe5b6834e4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:43:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ydanbui/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Designing a Better Cook: A Look at Yummly]]></title>
            <link>https://uxdesign.cc/designing-a-better-cook-a-look-at-yummly-4d7fb1dac340?source=rss-44fe5b6834e4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d7fb1dac340</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Y-Dan Bui]]></dc:creator>
            <pubDate>Fri, 30 Mar 2018 02:27:53 GMT</pubDate>
            <atom:updated>2018-04-02T08:01:18.057Z</atom:updated>
            <content:encoded><![CDATA[<h3>Designing a better cook: a look at Yummly</h3><h4>Exploring the usability of an award-winning app</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mhHpKTZ7ymqlq3nUEviLew.jpeg" /></figure><p>As a fairly recent college grad trying to break free from a lifestyle of ramen, Chik-fil-A, and taco Tuesdays, I’ve come to realize that being a good cook is pretty damn hard. Sure, there have been moments of cooking brilliance, but the process of searching for recipes, hunting down ingredients, and scrambling between laptop–pantry–mixing bowl like a headless chicken beats me down <em>every single time</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*qVWR_NqMKYojy3vWVy2MTg.jpeg" /><figcaption>One of the top image search results for “college diet”</figcaption></figure><p>Yeah, it’s been a struggle. Suffice to say, help was needed.</p><h3>Enter Yummly</h3><p>As an aspiring designer of both amazing products and amazing food, I decided to take a close look at the Yummly iOS app to help me learn to cook and to explore the usability of the app.</p><p><em>Note: I am not affiliated with Yummly in any way (just in case my cooking skills didn’t make that apparent enough).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ywfu5sPgdnUv_CPsR1dReQ.png" /><figcaption>Yummly for your tummly!</figcaption></figure><p>Yummly is a “<a href="https://itunes.apple.com/us/app/yummly-recipes-recipe-box/id589625334?mt=8">smart cooking sidekick</a>” that personalizes the cooking experience. Accessible from the web or via mobile app, Yummly provides features such as personalized recipe recommendations, recipe search and save, shopping list, and quick grocery delivery.</p><h3>Overview</h3><p>Over a period of two weeks, I conducted guerrilla usability testing of the Yummly iOS app and identified that users were having<strong> problems with the saving, sorting, searching, and filtering functions</strong> in the app.</p><p>With user and business goals in mind, I designed solutions to address these pain points and validated the prototype with additional users. The result was a much more streamlined experience in which<strong> using those functions was faster and easier.</strong></p><p>Here’s a quick example: My test results showed that users were confused about the Yum (save recipe) button. I made it significantly easier to use by changing the shape and color of the button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WjJAI45Mb1hr3c0_aRLSpg.png" /><figcaption>Simplifying the saving function</figcaption></figure><p>Let’s dive into my process!</p><h3>Guerrilla Usability Testing: Finding the Pain Points</h3><p>Whether you cook once a day or once in a blue moon, making food is at least somewhat relevant to a good chunk of the population. I assumed that the strangers I would test with would at some point have needed to search for a recipe. I decided that guerrilla usability testing was the best method to use to be able to quickly gather insights while minimizing time and cost.</p><p>Due to this universal language of cooking and the nature of guerrilla testing, I decided to focus on what jobs users might ask Yummly to solve (<a href="https://jtbd.info/2-what-is-jobs-to-be-done-jtbd-796b82081cca">the Jobs to be Done model</a>) and envisioned three different scenarios and job stories in which Yummly could meet a need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*erKbBXAe8hX1hPzUvtYH-Q.png" /></figure><p><strong>With this in mind, I set out to evaluate users’ abilities to complete the following tasks:</strong></p><ol><li>Find a recipe</li><li>Find 3 highly rated recipes of their favorite dish and save them</li><li>View only vegan, soy-free recipes</li><li>Find recipes that only use certain ingredients in their fridge</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*6oBLC8I5iNkpirzj23kgJw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*-4rtBC4y3CXFpHZ7O8zuCA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/1*WZtXf6Zqx6iG9MlVfNklIg.png" /><figcaption>Guerrilla usability testing out in the wilderness</figcaption></figure><p>I tested with eight wonderful people (<a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">why you only need five, minimum</a>) for about 15 minutes each in the Yerba Buena area of San Francisco, ranging from frequent cooks who regularly use recipes to novice cooks who have only cooked a few times.</p><p>As it turns out, <strong>none of the users were familiar with Yummly</strong>, so I was able to uncover many insights into the discoverability of different features and the ease of navigation throughout the app.</p><h3>Analysis: Prioritizing the Pain Points</h3><p>After all the pain points were gathered, I noted the insights on sticky notes and grouped them by user. Then, I used affinity mapping to organize related pain points into categories so I could identify common themes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B-S9YZ2maKOnzU6SEmBygw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-NsM0tSFODa-AJKcdJHbnA.jpeg" /><figcaption>Pain points arranged and affinity mapped</figcaption></figure><p>As themes among the pain points began to emerge, I used a 2x2 prioritization matrix to understand how they ranked in terms of importance to the business and importance to the user. This required making some assumptions about Yummly and its users.</p><p><strong>Assumptions about the business:</strong> Yummly has an advertising-based business model, so success depends on daily active users.</p><p><strong>Assumptions about the users:</strong> Based on my scenarios and job stories, I assumed that being able to find recipes that suit their particular needs and situations would be most important.</p><p>As a designer conscious of both business and user needs, this helped me decide which pain points were important for me to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwDPEhIXUrDGouXN2BndHg.png" /><figcaption>2x2 prioritization matrix showing the most important pain points I uncovered</figcaption></figure><p>My highest priority were the pain points that fell in the upper right quadrant, ones the were important to both business and user.</p><h3>Solution: Eliminating Pain Points</h3><p>I drew task flows as a way pinpoint the exact place where users were running into trouble in carrying out each task. Right next to these, I drew ideal task flows of how users would complete the same tasks pain-free. For the sake of space, I’ve only included one set of task flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJrVtBFpeRHzs8iY9Wbh3w.png" /><figcaption>Task flow illustrating the search function not being easily apparent or reachable (Pain Point 1)</figcaption></figure><p>Now I had a visual indication of exactly where users were running into trouble and a goal for what I would have to change. With this in mind<strong> I generated design solutions based on these ideal task flows, created a prototype in InVision, and validated my solutions with five additional users</strong>.</p><p>Below is a summary of how I addressed each pain point.</p><h4><strong>Pain Point 1: Search is not easily apparent or reachable</strong></h4><blockquote>On first sight, I don’t know where to find a search bar.</blockquote><p>When trying to find a recipe, the first thing users did was tap on <em>Explore</em>, realize there was no way to search from the explore screen, and then have to navigate back and look for a way to search.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A7eqkmWP70gisUXyzyC28Q.png" /><figcaption>Trying to search from the home screen</figcaption></figure><p><strong>My solution</strong>: I renamed the <em>Explore</em> tab to <em>Search </em>so users know immediately where they can go to search recipes. I also added a search bar and search options so users can manually search, in addition to exploring categories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2hcoBZ6VmUCYq8YFByBm1w.png" /></figure><h4>Pain Point 2: Confusion about saving recipes</h4><blockquote>How do I save it?</blockquote><p>All 8 users were confused about the Yum feature, Yummly’s way to favorite and save recipes. Some of those users didn’t realize that Yum was a button that they could click, while others didn’t know what Yum actually meant.</p><p>Once they figured it out, 3/8 users weren’t initially sure where they could find their saved recipes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WjJAI45Mb1hr3c0_aRLSpg.png" /></figure><p><strong>My solution: </strong>I changed the Yum button from circular to heart-shaped, as hearts are a familiar favorite button signifier, and changed the unsaved button state to white instead of orange, as white makes more sense than orange to indicate an unclicked button state.</p><p>I also changed the number of Yums to be displayed on a ribbon rather than a circle. The ribbon is similar to the bookmark icon, acting as a secondary signifier.</p><p>I appropriately changed the person icon in the tab bar to a heart to make it obvious where saved recipes were stored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6iG2ODe_VRj7lmMP9gHFyA.png" /></figure><h4>Pain Point 3: Unable to sort results</h4><blockquote>I thought there was a way for you to view by most popular.</blockquote><p>On the search results screen, users lacked quick access to information that would help them decide whether a recipe is worth saving. Two users specifically pointed out that seeing the recipe’s average rating required them to click on the recipe and wished it was visible at a higher level.</p><p>4/8 users wished there was some way to sort recipes by certain qualities, such as best rated or most Yummed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jy7WIITaJmdSOz_h3IPIvg.png" /></figure><p><strong>My solution: </strong>Add a Sort button on the search results screen that would enable users to view recipes in order of rating, cooking time, or number of Yums. I also added a rating display so users could have a sense of the recipe’s quality without having to navigate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xdi4wu0kbFu737bDS08mLw.png" /></figure><h4>Pain Point 4: Lack of filter visibility and feedback</h4><p><strong>Lack of Visibility: </strong>When presented with finding vegan, soy-free options, only 1/8 users used Yummly’s built in filters. Everyone else manually searched some variant of “vegan no soy” instead. I observed that this was due to two main factors, the filter button not being present on the main search screen, and the filter button being difficult to see even when present.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*blL0hEAo17qllQPvRCbBaw.png" /></figure><p><strong>My Solution (for lack of visibility): </strong>Make the filter button more visible, and have a state change be indicated when filters are applied. I also put a filter button on the main search page so users have filter access right from the get-go.</p><p><strong>Lack of Feedback: </strong>Particularly of note was my test with a person who was actually allergic to soy. She was able successfully find and apply the appropriate filters, but wanted to confirm that they were working and didn’t have the feedback to do so.</p><blockquote>Okay at this point I don’t trust the app and wouldn’t use it anymore.</blockquote><p>She manually looked at the ingredients to see if she could eat them, and actually found that one of the supposed soy-free recipes actually contained a soy product. This made her lose trust in the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VlPcHdogKmXaGQJx6Cnl3w.png" /></figure><p><strong>My solution (for lack of feedback): </strong>Provide tags on the recipe overview to show that recipes were vegan and soy-free.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GE4JQ0xu4SKb4fGU3-uw1A.png" /></figure><h3>Going Forward</h3><h4><strong>Cooking-wise:</strong></h4><p>Become a masterchef with the help of Yummly!👨‍🍳</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*rPbM-GvrCjCx4MPf2KjcGw.jpeg" /><figcaption>What I will no longer be</figcaption></figure><h4><strong>Design-wise:</strong></h4><p>Outside of everything I learned by doing and working through challenges, some of my specific takeaways from this project are:</p><p><strong>Affordances are especially important for new users. </strong>Since everyone I tested with were first time-users of Yummly, alot of the pain points I found (saving, filtering, searching) were a matter of the users being unfamiliar with the product and not knowing the full extent of what they could do. Having to address these pain points reinforced the importance of having affordances and <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">making systems usable without help (or at least making the help easily retrievable</a>).</p><p><strong>There may be tradeoffs between branding and usability. </strong>The Yum button, with it’s orange color and logo mark, was a unique take on the favorite button. Unfortunately, it confused users and decreased usability. Using a more traditional favorite button would make the function clearer, but then Yummly would lose some of its branding and character. My redesigned button was a hybrid of the existing button and a generic button, as I tried to balance the tradeoffs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ryz8wk5DAR8-PpN2OcUdjw.png" /><figcaption>Different options for the Yum button design, each with potential trade-offs</figcaption></figure><p><strong>Edge cases need to be considered. </strong>To my surprise, one user interacted with the app completely differently than everyone else: the user who was allergic to soy. She had to take extra precautions and dig deeper into the recipes than other users. Referring back to <a href="https://jtbd.info/2-what-is-jobs-to-be-done-jtbd-796b82081cca">Jobs to be Done</a>, she had a larger job than the other users. Cases like these need to be considered in the design process, otherwise users with these larger job reqs will look elsewhere.</p><p>Special thanks to <a href="https://medium.com/u/42b058a719ed">Zac Halbert</a>, <a href="https://medium.com/u/9815cb97f4a7">Jake Fleming</a>, <a href="https://medium.com/u/cd409f64eef0">Amy Weibel</a>, and <a href="https://medium.com/u/532011467ec8">Jeff Nissen</a>. Finger tap icons made by <a href="http://xn--https-nw3b//www.flaticon.com/authors/yannick">Yannick</a> from <a href="https://www.flaticon.com/">www.flaticon.com</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d7fb1dac340" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/designing-a-better-cook-a-look-at-yummly-4d7fb1dac340">Designing a Better Cook: A Look at Yummly</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>