<?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 Chien-yu Shen on Medium]]></title>
        <description><![CDATA[Stories by Chien-yu Shen on Medium]]></description>
        <link>https://medium.com/@chienyushen?source=rss-87999f9d3491------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*1DE5f-spZloaHDeR.</url>
            <title>Stories by Chien-yu Shen on Medium</title>
            <link>https://medium.com/@chienyushen?source=rss-87999f9d3491------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 15 Nov 2026 05:15:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chienyushen/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[Case Study: Fresh City Farms]]></title>
            <link>https://medium.com/@chienyushen/case-study-fresh-city-farms-26acc078eb8e?source=rss-87999f9d3491------2</link>
            <guid isPermaLink="false">https://medium.com/p/26acc078eb8e</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Chien-yu Shen]]></dc:creator>
            <pubDate>Mon, 20 Jul 2020 18:23:00 GMT</pubDate>
            <atom:updated>2020-08-31T22:01:51.427Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Hero image for Fresh City Farms Case Study" src="https://cdn-images-1.medium.com/max/1024/1*GZAmqZfHKa3ByRTlAC5KeQ.png" /></figure><h4>Class project: mobile web redesign (July 2020)</h4><h4>Can online grocery gateways provide more than groceries?</h4><p>Fresh City Farms provides quality organic produce straight from local Ontario farms not readily found in most regular grocers.</p><p><em>How can we connect more farms-to-tables?</em></p><figure><img alt="screen shots of high fidelity prototype" src="https://cdn-images-1.medium.com/max/800/1*XTJrFTo7lYlI1pIvb2heuA.png" /><figcaption><a href="https://chienyu588933.invisionapp.com/public/share/AZ1AGO4K5K"><strong>Click here for interactive prototype</strong></a></figcaption></figure><h4><strong>What’s the problem?</strong></h4><p>With few preconceived notions of how the Fresh City Farms (FCF) experience could be improved I conducted user research to identify potential needs:</p><ul><li>qualitative interviews with 5 households</li><li>each with different levels of familiar with online grocery gateways</li></ul><p>By synthesizing the interview data I converge on 3 recurring sentiments:</p><ol><li><em>users want to </em><strong><em>avoid getting the wrong items</em></strong></li><li><em>the </em><strong><em>transparency of pricing</em></strong><em> is paramount</em></li><li><em>the experience of </em><strong><em>inspiring culinary experimentation</em></strong><em> is absent.</em></li></ol><blockquote>“I never know what to make for dinner. I wanna try [cooking] new things.”</blockquote><blockquote>— User Interview 5</blockquote><p>Sentiment #3 in particular was a non-obvious finding and no existing grocery gateway addressed this issue. It presented an opportunity to explore a new feature which will:</p><ul><li><strong><em>inspire shoppers </em></strong><em>to try new ingredients</em></li><li><strong><em>maintain shoppers’ control</em></strong><em> over purchasing decisions</em></li><li><strong><em>incur no extra cost </em></strong><em>and inconvenience for shopper and provider</em></li></ul><figure><img alt="research report cover page" src="https://cdn-images-1.medium.com/max/1024/1*YcrZQhFzGOwpC4FT6813cQ.png" /><figcaption>You can find the <a href="https://www.dropbox.com/s/n2l7uk3i3t97rdd/Chien-yu_Shen_ResearchReport_UX2020.pdf?dl=0">full research report here</a></figcaption></figure><h4>Exploring solutions</h4><p>Base on these research insights<strong> I decided to focus on creating a ‘suggested recipe’ section.</strong> I generated ideas by sketching out how the new feature might be presented right below the ingredient product page.</p><figure><img alt="pen and paper prototype screen shots" src="https://cdn-images-1.medium.com/max/671/1*3e0h0kbGlR-Wge6bx5jprA@2x.jpeg" /><figcaption>Early sketches for ‘suggested recipe’ flow</figcaption></figure><p>The pen sketches ended up being too rough even for a lo-fi prototype. I built a mid-fidelity prototype with Sketch + InVision instead for usability testing testing.</p><p><strong>The users were tasked with getting all necessary ingredients to make a “Steak Frites” dinner. </strong>The recipe section would allow the users to add all necessarily ingredients to make the dish.</p><figure><img alt="mid-fidelity prototype screen shots" src="https://cdn-images-1.medium.com/max/813/1*6kJFZ9cTqTiWVe-0R5DvUg.png" /></figure><p>Feedback from multiple rounds of testing revealed on several major <strong>pain points</strong>:</p><ul><li><em>suggested </em><strong><em>recipes were being confused for products</em></strong></li><li><strong><em>unclear copy writing</em></strong><em> (“What’s for Dinner?”) hindered navigation</em></li><li><strong><em>dense text blocks </em></strong><em>overwhelmed users</em></li></ul><h4>The new look</h4><p>Continuous testing and design iterations further refined the look and feel of the <a href="https://chienyu588933.invisionapp.com/public/share/A41AGO4L9X#/screens/479420739">high-fidelity prototype</a>:</p><figure><img alt="High fidelity prototype screenshots" src="https://cdn-images-1.medium.com/max/1000/1*afTFD4aKtzwvrctN6sadPQ.png" /><figcaption><a href="https://chienyu588933.invisionapp.com/public/share/AZ1AGO4K5K"><strong>Click here for interactive prototype</strong></a></figcaption></figure><p>Major changes from early builds include:</p><ul><li><strong>collapsible product descriptions</strong> provided more screen real estate</li><li><strong>edited copy writing</strong> for clarity</li><li><strong>improved informational hierarchy</strong> through colour and font choice</li></ul><h4>Before &amp; after</h4><p>Here are some comparisons between the original and the revised mobile site:</p><figure><img alt="before and after screen comparison #1" src="https://cdn-images-1.medium.com/max/874/1*uODTQMk73kUxnr3AmKuHCQ.png" /><figcaption>A less cluttered layout was chosen</figcaption></figure><figure><img alt="before and after screen comparison #2" src="https://cdn-images-1.medium.com/max/874/1*vhlZCz86CZXnrpRAJBbo1g.png" /></figure><h4>Style Guide</h4><figure><img alt="colour and font style guide" src="https://cdn-images-1.medium.com/max/1024/1*vp69eZ-aA8mNsMY9onDBpg.png" /><figcaption>I opted for a limited and clean palette</figcaption></figure><h4>Post-game debrief</h4><p>This project being my introduction to UX design impressed upon me the logic of the design process. Several insights gained throughout the experience will surely become my guiding light for the rest of my career.</p><ul><li>effective <strong>research will challenge assumptions</strong> and reveal subjective blindspots</li><li>properly conducted ethnographic<strong> research will generate hidden opportunities</strong></li><li><strong>copy writing can critically lead/mislead users</strong></li><li>when the experience works it’s taken for granted; <strong>the UX designer should be invisible to the user using the product</strong></li></ul><h4>My role</h4><ul><li>UX research</li><li>UX design</li><li>UI design</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26acc078eb8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>