<?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 Katherine Evans on Medium]]></title>
        <description><![CDATA[Stories by Katherine Evans on Medium]]></description>
        <link>https://medium.com/@katherineevans?source=rss-2413722f2dd9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*MY9ZzEWsoQgya9wN.</url>
            <title>Stories by Katherine Evans on Medium</title>
            <link>https://medium.com/@katherineevans?source=rss-2413722f2dd9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:04:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@katherineevans/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[Fandango: A UX Design Case Study]]></title>
            <link>https://medium.com/@katherineevans/a-ux-design-case-study-417bf1f9e500?source=rss-2413722f2dd9------2</link>
            <guid isPermaLink="false">https://medium.com/p/417bf1f9e500</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Katherine Evans]]></dc:creator>
            <pubDate>Mon, 26 Jun 2017 11:15:13 GMT</pubDate>
            <atom:updated>2017-07-11T01:30:59.035Z</atom:updated>
            <content:encoded><![CDATA[<p>By Kate Evans</p><p><strong>The following case study reflects the design process my team used to add a hypothetical new feature to the current Fandango mobile app.</strong></p><p><em>For context, this is a concept project completed by 4 design students. Fandango is a corporation that currently sells movie tickets via phone, web, and mobile applications.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*FK8v6XO9jP78F63zibnndQ.jpeg" /><figcaption><em>Disclaimer: This case study was completed by 4 UX Design students, not by Fandango’s Design team.</em></figcaption></figure><h3>The Problem</h3><p>Project Brief:<em> Fandango wants to build a service that notifies you of events happening in your area, allows you to easily purchase tickets, and then use a digital pass to attend the event.</em></p><p><strong>Duration:</strong> 2 weeks</p><p><strong>Role: </strong>UX/UI Mobile iOS Design</p><p><strong>Skills &amp; Tools:</strong> Design Thinking, Competitive Analysis, Feature Analysis, Survey Screening, Contextual Inquiries, User Research, User Interviews, Affinity Diagram, User Flows, Personas, Problem Statements, Problem Solutions, Storyboards, Wireframing, Sketching, Paper Prototyping, Usability Testing, Iterating, High-Fidelity Prototyping, Sketch, InVision</p><h3>Research: Forming Assumptions</h3><p>We began our project by compiling a list of assumptions to help direct our research, which helped us gain a better understanding of the difference between the experience of purchasing a movie ticket vs. an event ticket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/731/1*vqg2BjRC5safYw8mUJvxMQ.png" /></figure><p>We validated these assumptions by cultivating a holistic awareness of Fandango’s Brand Identity. Their 4 main guiding principles [<a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=3&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwjKtPrbq9vUAhXDGj4KHfsuAX8QFgg1MAI&amp;url=http%3A%2F%2Fimages.fandango.com%2Fdoc%2FOnline_brand_usage_guidelines_updated_.pdf&amp;usg=AFQjCNGh9c8eFMQYTIHozPRK4Kid9PJwSQ">available to the public</a>]: SIMPLE, MAGNETIC, DEFINITIVE, PLAYFUL. We narrowed these principles into the themes that would guide our project:</p><ol><li><strong>Keep it Conversational — </strong>Provide empathetic and “playful” communication within the app and become a trustworthy resource. Provide sharing options to keep users satisfied and engaged.</li><li><strong>Be the Expert for the User — </strong>Bring Fandango’s movie expertise into the topic of concerts &amp; events. Provide recommendations and delightful options that enhance the experience.</li><li><strong>Keep it Simple </strong>— Prioritize a simple and effortless experience for the users so they can bypass the pain points of purchasing tickets online, so they can focus on enjoying the event .</li></ol><p>From here, we conducted a competitor analysis of similar event/concert apps (such as Eventbrite, Ticketmaster, Bandsintown, Live Nation, and Stub Hub) and made a feature analysis chart.</p><p>Which features were crucial to the goals of our users and which were not?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*NrnR3dy92RPoXb2vhDld6g.png" /><figcaption><em>(The features shared by each competing app are highlighted in green. The key features include: Account login, Featured/Recommended/Upcoming Events, Direct Search, Event Filtering, Location Services &amp; Map integration)</em></figcaption></figure><h3>Research: User Interviews</h3><p>From here, we developed a list of survey questions to send out in the span of 1 day. The data we received back from our <strong>82</strong> participants helped our group to screen candidates for user interviews. The key takeaways from our 5 interviews are highlighted below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*uAgO-F3VmryMQ-J5kRIYSA.png" /></figure><h3>Research: Feature Mapping</h3><p>To help us prioritize the most necessary features of our MVP, we rated our research findings on a scale of 1–10 from “Nice to Have” to “Essential”.</p><p>We then consulted a Web Developer to determine how realistic and complex each feature would be to build. From here, we mapped our findings in a Feature Quadrant. This concluded our research and allowed us to move on to the Ideation phase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*jq4m2hv5a39oyQMg_gAxQg.png" /><figcaption>To help prioritize the features for our MVP, we consulted a web developer to rate the complexity of each feature.</figcaption></figure><h3>Ideation: Personas</h3><p>Based on our research, we created our primary persona and storyline for the remainder of our project and group presentation.</p><ul><li><strong>Name:</strong> Elle Carter, 26</li><li><strong>Bio:</strong> Concert Enthusiast</li><li><strong>Needs:</strong> Discover and share concerts &amp; events with friends, Simple payment process with Venmo integration</li><li><strong>Goals:</strong> Find specific concerts &amp; go to as many as possible</li><li><strong>Frustrations:</strong> No existing hub where she can follow artists, find and purchase concert tickets</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/824/1*67B83o75VXhVcmtAnjJAFQ.png" /></figure><h4>Problem Statement</h4><p><em>As a frequent concert go-er I need a way to follow my favorite artists and local venues, purchase tickets, and coordinate attending events with my friends all in one place so I can go to more concerts.</em></p><h4>Solution Statement</h4><p><em>Build an event feature that allows users to find, purchase, share, and attend local events so they can spend less time planning and more time enjoying!</em></p><h3>Ideation: Storyboard</h3><p><strong>Scenario:</strong> <strong><em>Elle is riding the train home from work when she gets a text from her friend visiting next weekend. Elle wants to show her friend a good time and find a fun concert they can both attend.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/1*4eNjbChgF4xgKpQOKViySA.png" /></figure><h3>Ideation: Paper Prototype</h3><p>Based on research we sketched out wireframes that would lead to our first prototype, including:</p><ul><li>Spotify Integration</li><li>Venmo Integration</li><li>Map integration</li><li>Digital Pass</li><li>Sharing capabilities</li><li>Artist Info Page &amp; Related Atists</li><li>Venue Amenities</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*CTvdIKAbY8N07nXYssz6Jw.png" /><figcaption>Some of our initial wireframes &amp; sketches</figcaption></figure><h3>Usability Testing: Wireframes and Paper Prototyping</h3><p>We tested our first prototype on 5 participants and discovered what areas needed iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/1*9sab7xaUD4qmJ2oNoA657g.png" /></figure><p><strong>Our key findings:</strong></p><ul><li>Participants wanted instant access to <em>all</em> content, and flow through the purchasing process quickly. They found it frustrating having to choose between the two portals: <em>Movies</em> or <em>Events</em></li><li>Participants found the ticket purchasing process time consuming and cumbersome given the complexity of selecting seats at a concert [we used the same conventions as the current Fandango app].</li></ul><h3>Usability Testing: Iterations</h3><p>Based on the feedback we received from Usability Testing, we made many iterations to our prototype. Here are a few of the changes we made:</p><ul><li>Design a “Linked Accounts” page for Spotify, Facebook, and</li><li>Design a home to quickly access Favorite Artists</li><li>Design a simpler “Seat Selection” feature with the option to filter out available sections based on the number of available seats that were “together”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*K48f_s6AsSxzJDoF4oG0QA.png" /></figure><p>Make sure to also check out some of the screens from our Final Interactive Prototype!:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hOjiLE04jsDONfEqKOZPlw.jpeg" /></figure><h3><a href="https://invis.io/T9CBHMJG5#/240361287_Landing_Page"><em>See the finished Interactive Prototype here</em></a></h3><h3>Next Steps</h3><p>The future iterations of our MVP would include:</p><ul><li>Waitlist for sold out events</li><li>Fandango VIP Rewards Program</li><li>Function where users can order food/drinks to their seats</li><li>Season tickets for recurring events</li><li>Digital “shoebox” as a way to store tickets as souvenirs</li><li>Design a search results page</li><li>Design the “Favorites” section</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=417bf1f9e500" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Abodeon: An eCommerce Case Study]]></title>
            <link>https://medium.com/@katherineevans/just-in-time-an-ecommerce-website-re-design-853f300610d3?source=rss-2413722f2dd9------2</link>
            <guid isPermaLink="false">https://medium.com/p/853f300610d3</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <dc:creator><![CDATA[Katherine Evans]]></dc:creator>
            <pubDate>Mon, 19 Jun 2017 20:27:35 GMT</pubDate>
            <atom:updated>2018-12-14T18:37:54.847Z</atom:updated>
            <content:encoded><![CDATA[<p>A mid-century-themed website redesign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*W6qo6SqA4Z35fIOffxST4g.png" /></figure><p>There’s this little shop in Porter Square, with funky furniture and items so unique, you‘ll have trouble finding them anywhere else. When you walk in, you’ll start to pick up on something you can’t quite figure out yet. You’ll start bopping to Al Kooper playing through the record machine, setting the tone for Mid-Century Modern and Vintage vibes. It‘s an experience that somehow evokes feelings of nostalgia and sentiment, no matter your age— an experience not many other stores can provide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GJh2b08AbVgGvtNXNx3vrQ.jpeg" /></figure><p><em>Abodeon,(</em>pronounced abode-EON<em>) </em>resides<em> </em>in Somerville, MA. With an affinity for acquiring and selling Mid-Century Modern and Vintage Designs, most of the items here are one-of-a-kind. The owner, Dale, (a fascinating man I had the opportunity of interviewing) came up with the shop name by fusing the words “Abode” and “Beyond” together.</p><p>And that’s exactly what the in-store experience does — transcend you beyond the chaotic stock noise of IKEA-land and into a world that believes everything you own should speak to your soul and bring you joy.</p><p>The problem is, <em>Abodeon</em>’s website brings you anything but joy. Frustration, confusion, self-doubt (and maybe a little depression)…but joy? Far from it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bd2Jx9PWTfm3j0UHv3wRnw.png" /></figure><h3><strong>The challenge</strong></h3><p>I needed to find a way to bring <em>Abodeon’s </em>in-store experience of quality, care, and authenticity to it’s otherwise unfriendly website. I followed this outline.</p><h3><strong>Project Outline</strong></h3><ol><li>Discovery &amp; Research</li></ol><p>2. Sketching &amp; Ideation</p><p>3. Narrow the Scope</p><p>4. Prototype, Test, Iterate &amp; Repeat</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iL6Nnd9fmiRl0CxlT3lzpw.jpeg" /></figure><p>I began the Discovery phase by interviewing the owner of Abodeon, Dale (here on the left). I continued to interview numerous participants, including people who work as Interior Designers, Art &amp; Furniture dealers, Textile Designers &amp; Professors, as well as people who are none of those things. Everyone needs furniture, right?</p><blockquote>I asked questions to get to the root of my participants’ online shopping woes, such as “What sites do you enjoy shopping at most? What sites do you enjoy shopping at least? And most importantly, WHY, WHY, WHY?”</blockquote><p>Turns out there were a million reasons. I took to my notes and created an <strong>Affinity Diagram</strong> to narrow my focus down to ten focus points and determine what users would and <em>would not</em> want in an eCommerce experience.</p><p>I then started researching other stores similar to <em>Abodeon </em>. Since there aren’t many, I researched sites such as <em>Rejuvination</em>, <em>Wayfair</em>, and <em>Loveseat. </em>I picked apart the positive and negative elements of their wireframes with a Competitor Analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*zRbQMdE-FYrF4_Lk7jaUug.png" /></figure><p>It all came down to three components:</p><ol><li>Personalize &amp; Delight</li><li>Clear site navigation</li><li>Strong Visual Design</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=853f300610d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I learned from a 3-day Design Sprint]]></title>
            <link>https://medium.com/@katherineevans/skwire-fb16b334bbb1?source=rss-2413722f2dd9------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb16b334bbb1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[mobile-app-design]]></category>
            <dc:creator><![CDATA[Katherine Evans]]></dc:creator>
            <pubDate>Sun, 11 Jun 2017 16:54:01 GMT</pubDate>
            <atom:updated>2017-06-15T15:16:56.786Z</atom:updated>
            <content:encoded><![CDATA[<p>And how to avoid “Feature-itis”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*shohdILMpWEipmbeKcjcTA.png" /></figure><h3>Who are we designing for?</h3><p><em>“I wish there was a better way I could go running outside without my house keys, or to let people in and out of my house when I can’t be there.”</em></p><p>My design partner is an all-around busy person — and that’s putting it lightly.</p><p>As an avid runner with a busy work schedule, on top of family and social commitments, she’s constantly in-and-out of her apartment. Any kink in her schedule could be disastrous. For someone like my partner… who has the time to be five places at once AND be at home to let the cable guy in?</p><p>Because being 5 places at once is <em>physically</em> <em>impossible</em>, my partner asked me to design an app that lets people in-and-out of her house without a <em>physical</em> <em>key</em>.</p><p>After rounds of research, I found out she wasn’t the only one who felt this way.</p><h3>Problem Statement</h3><blockquote><strong><em>As a busy person, I need to be able to lock or unlock my house from anywhere, because I’m not always able to be there to do so with a key.</em></strong></blockquote><h3>Challenge</h3><p>Design an app that can unlock the door with personalized security.</p><p><strong>Time Frame</strong>: 3-day design sprint</p><h3>My Design Process</h3><ol><li>Research the benefits &amp; pain points of using a physical key.</li></ol><p>2. Identify the recurring thought patterns among participants</p><p>3. Design a mobile app with “smart” access</p><p>4. Narrow feature focus</p><p>5. Test &amp; Iterate to a final prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gr8W5cxv9XdyUBiQMjak-A.jpeg" /></figure><h3>Research: Interviews</h3><p>We can all agree that it totally stinks to misplace our keys. But how often do we actually <em>lose</em> them? And how often do we allow people access to our homes when we’re not there? This is what I needed to find out. So I interviewed multiple participants with varying ages and socioeconomic backgrounds about the prospect of a physical and digital key. <strong>Some of my questions included:</strong></p><p><em>“How do you handle getting locked out of your place?”</em></p><p><em>“Say your friend is visiting your house for the week. How would you arrange her getting in/out of your house while you’re at work?”</em></p><p><em>“If you had an app that let you control who can get in/out of your house, </em><strong><em>what kind of functionality would it have?”</em></strong></p><h3><strong>The feedback I received was around what I expected… but it also included insight to the need for specific features I would have <em>never</em> thought of without:</strong></h3><p>“<em> If I didn’t have a key, I would wait for someone with another set, or find a way to break in myself”</em></p><p><em>“I would want extra security”</em></p><p><em>“When I lose my keys </em><strong><em>I feel really annoyed</em></strong><em>, because all of my plans get ruined”</em></p><h3><strong>Research: Affinity Diagram</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1MedqDW_IUoQXoOyEB7p0Q.jpeg" /></figure><p>Given the abundance of intel I received from my participants, I took to my handy post-it notes and sorted the recurring feedback with an Affinity Diagram. The three main take-aways were:</p><ol><li>I want more functionality</li></ol><p>2. I want better security</p><p>3. I want more freedom</p><h3>Design an app with “smart” access:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ff64i5pRiopcpZWXaFzpvg.png" /></figure><p>Now it was time to translate my research into tangible designs. I sketched out functionality options so a friend could have temporary (or permanent) access to the key. I sketched out security features, like a passcode for the key-holder to enter, and the concept of a fingerprint-verification system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ig8_mUwOkc9DsmPUdE9bxw.jpeg" /></figure><p>I sketched out the ability to schedule access for deliveries and task-related entries.</p><p>What I didn’t realize is the critical mistake I had made.</p><p><strong><em>I had sketched out far too many features to include in a 3-day design sprint.</em></strong></p><h3><strong>Narrow my focus: Features</strong></h3><p>With one day left, I needed to revisit [and refocus] on the three points my affinity diagram had determined. How can I establish security, functionality, and accessibility, yet keep the design simple? And how could I possibly complete this in less than one day?</p><p>I went bare-bones and stripped my prototype of any excess features. I kept the fingerprint security but got rid of the access code the user needed to enter each time she opened the app. Instead, I decided to take to FitBit and create an app that programmed to a lock device that attached to the door. This way, the user would simply register the lock on the app, verify her fingerprint, and walk away satisfied. By including the main points of security, accesibility, and functionality…why did it take so long to come to this simple solution?</p><h3>Iterate and test:</h3><p><em>I tested my new prototype until 10pm. I burned the midnight oil to create these high fidelity prototypes. And I believe I’ve found the solution to a mode of keyless entry.</em></p><h3>This is <em>Skwire:</em></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2f14BiPDw0nX83Le_fFhQw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q-RqbwFdiBpajrjXu25pIQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rQzFx80vCntC1nH7jdMteg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*75KtPtDmgwPbI64y2vnMhQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b47_gOd13o1tDQw9M2rkCw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vn2ggrCf6rfMY02RF2LMWg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OqVeMS3yil83L2s62rLAjQ.jpeg" /></figure><p>When I’m able to revisit skwyre, I want to make the following changes:</p><h3><strong>Next Steps</strong></h3><p><strong>Create user flows for:</strong></p><p>-Lending out key code<br>-Access requests<br>-Temporary and permanent key holders</p><p><strong>Refine current High Fidelity prototypes:</strong></p><p>-Add lock to first screen<br>-Create “Edit” function for Account password<br>-Create more storyboard scenarios (app functions)</p><p>For all the struggle this seemingly simple app carried, I’d say I learned the most important lesson to User Experience Design— and I sure am glad I learned it during this first project.</p><p>Always remember to…</p><h3>BEGIN BY KEEPING IT SIMPLE!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb16b334bbb1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>