<?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 Ian Kelley on Medium]]></title>
        <description><![CDATA[Stories by Ian Kelley on Medium]]></description>
        <link>https://medium.com/@ikelley?source=rss-2d93c2b26e46------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6yW9n1nBI97ELq0_WESM7w.jpeg</url>
            <title>Stories by Ian Kelley on Medium</title>
            <link>https://medium.com/@ikelley?source=rss-2d93c2b26e46------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:35:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ikelley/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: Users have no limits]]></title>
            <link>https://medium.com/design-bootcamp/users-have-no-limits-a-playstation-5-ux-case-study-95a201fd4a0c?source=rss-2d93c2b26e46------2</link>
            <guid isPermaLink="false">https://medium.com/p/95a201fd4a0c</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[playstation]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ian Kelley]]></dc:creator>
            <pubDate>Tue, 26 Jan 2021 03:37:00 GMT</pubDate>
            <atom:updated>2021-01-27T03:11:39.385Z</atom:updated>
            <content:encoded><![CDATA[<p>This article outlines my graduating capstone project from my UX Design program at MICA. It showcases a detailed overview of my research goals, methodologies, findings, and ultimately a proposed PlayStation 5 user interface. I hope this article is informative to all, but specifically for those that are new to UX.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FGBYIXQsRr-B3ZfY08_KjQ.jpeg" /></figure><p><a href="https://unsplash.com/photos/k4Akpt5-Sfk">Photo by Alexey Savchenko on Unsplash</a></p><p><strong>High-level project goal</strong></p><p>My intent for this project is to design a hypothetical interface for the PlayStation 5 that improves upon the PS4 interface. Based upon qualitative and quantitative research, these improvements aim to increase the overall usability and satisfaction for the player.</p><p><strong>Project goals</strong></p><ol><li>Research the usability of the PS4 dashboard.</li><li>Research the user, their needs, and pain points.</li><li>Design a new user interface that improves upon the current PS4 user experience.</li></ol><p><strong>Problem statement</strong></p><p>PlayStation 4 players who use the console for gaming, find navigating the user interface for features supporting gameplay awkward, cumbersome, and time-consuming. These features include, but may not be limited to the general navigation of the home screen or main dashboard, recently played games, game library, PlayStation Store, and connecting with friends.</p><p><strong>The challenge</strong></p><p>Research the PlayStation 4 and its user to design a new console user interface. The success of this project, from a business standpoint, could be evaluated based upon PlayStation’s market growth increase.</p><p><strong>Proposal</strong></p><ol><li>Perform robust UX research to identify system inefficiencies, user pain points, and pitfalls that hinder or reduce a player’s overall satisfaction.</li><li>Test a proof of concept, based upon qualitative and quantitative research, to validate if the user interface is solving problems appropriately.</li></ol><p><strong>Methodology</strong></p><p>A combination of UX strategies that aim to understand, explore, and materialize the digital product. More specifically, a discovery session was conducted through user interviews and user surveys.</p><figure><img alt="Colored circles with labels fill a linear graph to compose a project timeline." src="https://cdn-images-1.medium.com/max/1024/1*RnpruozLtVmAeWdCyae4kA.png" /></figure><h3>Week 1 (week 7) — User research</h3><p>User research aims to understand the user, their behavior, motivations, frustrations, and how they interact with the system and product. The information gained provides insights into the problems they face, how they feel, and how they overcome any obstacles.</p><h4>Work to be done</h4><ol><li>Targeted audience identified</li><li>Interview screening questions designed</li><li>User survey questions crafted</li><li>Users surveyed</li><li>User interview questions crafted</li><li>Users interviewed</li><li>Research analyzed</li></ol><h3>Week 2 - Craft user personas</h3><p>User personas provide a high-level snapshot of the primary and secondary users. Crafting personas help designers develop empathy with specific users in order to design targeted and meaningful solutions.</p><h4>Work to be done</h4><ol><li>Craft a user personas</li><li>Craft a user empathy map</li><li>Craft the user’s mental model</li></ol><h3>Week 3— Competitive analysis</h3><p>Thorough competitive analysis and research expose how other products are solving similar problems. This strategy aims to identify both the strengths and weaknesses of other systems so we can better craft our solutions.</p><h4>Proposed competitors to study</h4><ol><li>Xbox One</li><li>Epic Games Launcher</li><li>Steam</li><li>Stadia</li><li>Twitch Launcher</li><li>Netflix (non-direct)</li><li>HBO MAX (non-direct)</li><li>Hulu (non-direct)</li></ol><h3>Week 4— User epics &amp; stories</h3><p>User epics and stories provide specific user needs to solve for. Epics are considered large, high-level goals and the stories within are smaller steps to achieve the high-end goal. In addition, user flows document the steps a user will take in order to complete a goal.</p><h4>Proposed work to be done</h4><ol><li>Design user epics &amp; stories</li><li>Sketch user storyboards</li><li>Sketch and map new flows for key scenarios</li></ol><h3>Week 5— Wireframes and wireflows</h3><p>Similar to user flows, these artifacts visually represent each screen a user will interact with and how all the screens will connect together.</p><h4>Proposed work to be done</h4><ol><li>Sketch wireframes for key interactions</li><li>Sketch wireflows for key interactions</li></ol><h3>Week 6— Lo-Fi prototypes</h3><p>Low fidelity prototypes is a low stake method to design and test our visual solutions. If incremental tests are performed throughout the design process we can more confidently propose appropriate solutions.</p><h4>Proposed work to be done</h4><ol><li>Design low fidelity prototypes for key flows</li><li>Test low fidelity prototypes to validate usability</li></ol><h3>Week 7 — Hi-Fi prototypes</h3><p>Higher-level prototypes begin to add the brand’s visual style and aesthetic to the project. It’s at this stage that we begin to see how the finished product might look, feel, and work.</p><h4>Proposed work to be done</h4><ol><li>Increase prototype fidelity</li><li>Test prototypes</li><li>Edit and refine visual solutions</li></ol><h3>Week 8— “Final” adjustments</h3><p>At this point, a near-complete prototype should be designed and we can begin final testing and evaluation of the system. Final testing should include key scenarios that examine the end-to-end flow.</p><h4>Proposed work to be done</h4><ol><li>Develop and design user scenarios</li><li>Test scenarios with users</li><li>Make final adjustments</li><li>Design stakeholder presentation</li></ol><h3>Now back to the actual work</h3><p>If you’re still with me by this long-winded point, thank you. For those of you that may not know, here is a screenshot of the PlayStation 4 dashboard.</p><p><strong>PlayStation 4 dashboard</strong></p><figure><img alt="PlayStation 4 dashbaord." src="https://cdn-images-1.medium.com/max/1024/1*QXXVdWX2uVPUdrFxY6tpww.jpeg" /></figure><h4><strong>Proposed PlayStation 5 dashboard</strong></h4><figure><img alt="A mockup of my proposed PS5 dashboard." src="https://cdn-images-1.medium.com/max/1024/1*Y7NrFwrhX48zQ2LeBMcu0Q.jpeg" /><figcaption>If you like the landscape art on the wall by the TV, that was illustrated by me.</figcaption></figure><h4>Process</h4><p>The UX design process is an empathetic one. Empathy is key to understanding the human experience. Just like the behavioral, neurological, and therapeutic wizards, I’m trying to understand what the user is experiencing. Although the tools may vary from project to project, the core process remains relatively the same:</p><ol><li>Understand the business, its goals, and needs</li><li>Understand the user and their goals</li><li>Brainstorm and model what the new system may be and test it to validate if these solutions are worth continuing</li><li>Design a prototype of the product and an interface</li><li>Test and validate the system</li><li>Document your results and iterate upon your design decisions</li></ol><h4>User interviews</h4><p>After evaluating my assumptions on how the user may feel and what the user may want in a new design, I set out to find participants to interview. In general, my assumptions were mainly concerned whether this project was worthy of investigation. For all I knew, users are completely happy and satisfied with the PlayStation 4 experience. The results of my discovery interviews are below.</p><ol><li>27 users surveyed</li><li>8 users interviewed</li><li>All users were between the ages of 28 and 37</li><li>All users had 22 to 33 years of gaming experience</li><li>All users were male</li><li>All users averaged between 1 to 2 hours of gameplay a day</li><li>All users play casually and are not professional gamers</li></ol><figure><img alt="Statistics showing the key results of the survey." src="https://cdn-images-1.medium.com/max/1024/1*VwOqt-0919e8fCw6pa6Mbg.png" /></figure><h4>Interview trends</h4><p>The list below gave me actionable experiences to design meaningful solutions.</p><ol><li>Players use the PS4 to play video games, stream movies, listen to music and connect with friends</li><li>Players expressed a tendency to use the PS4 as a form of therapy and emotional release</li><li>Players complained about too many clicks or scrolls to navigate the interface. Users want to customize their dashboard.</li><li>Users expressed wanting meaningful awards and trophies for their in-game achievements (unrelated to the native dashboard)</li><li>Users want to more easily connect and share with friends</li><li>Users are frustrated with the content organization.</li></ol><h4>Research organization</h4><p>All of my research lived within Adobe XD. I organized and curated my content in one central hub for more efficient access.</p><figure><img alt="My Adobe XD file containing all my research in one, easily accessible space." src="https://cdn-images-1.medium.com/max/1024/1*Hcb9sop9r0gLkmjvCMbVFw.png" /></figure><h4>Crafting empathy</h4><p>In order to synthesize the material and better understand the user and their needs, a few artifacts were crafted to help solidify the primary user and guide design decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OmDtSdGvZ3mz5KvhalFSOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NSKdOuxRxNMGwC9tQJlziA.png" /></figure><h4>Wireframing &amp; wireflows</h4><p>With a better understanding of the primary user and their needs, I began sketching wireframes and wireflows.</p><figure><img alt="A layout of a few wireframe sketches." src="https://cdn-images-1.medium.com/max/1024/1*LOMJP0agjobwyQAxNHvIcg.jpeg" /></figure><p>If we skip ahead, after all the numerous piles of sketches, I began to increase the fidelity and work toward a prototype.</p><p><strong>Proposed new dashboard</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lqz257PJALIIjlpCZYY9Vw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYz5sduv_6kQp5w-c7KGYw.jpeg" /></figure><p><strong>PS4 PS Store</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QyztRpJxpSNzGel7gGYttA.jpeg" /></figure><p><strong>Proposed PS5 PS Store</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QL2JWOQoPKM_6VMOnBbaFQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I86h2Fqg4xL1VpFz8wd9_g.png" /></figure><p><strong>PS4 friend list</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lr8qNkagJ9NZGQVnogaZxw.jpeg" /></figure><p><strong>Proposed PS5 friend list</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dqp98w5M4K1ni3h95ZB3eQ.png" /></figure><p><strong>PS4 settings</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PhzOaJpsjtc30oH9SGCcOQ.jpeg" /></figure><p><strong>Proposed PS5 settings</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GA81qypI8EyEqSYEkqLbQA.jpeg" /></figure><p><strong>PS4 profile</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V2zusmyWIurpQnVC0z63tA.jpeg" /></figure><p><strong>Proposed PS5 profile</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dZdyWeNpjzNLo_FvQkv8yg.jpeg" /></figure><h3>Project success</h3><p>A hypothetical business success metric was created. If the PlayStation could increase its monthly subscriptions and by 3% then the potential revenue generated could be over $136 million dollars.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1UKgTzYqHYGRN4URpbFFxA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6oVVLHVKps_XfulAD8_7UQ.png" /></figure><h3>Project challenges</h3><p>The above information is but a small sample of a much larger project presentation. To date, this has been the largest project I’ve tackled by myself. Most of my graduate projects of this caliber were group projects where we all divided and conquered to produce a profound project.</p><p><strong>Challenges</strong></p><ol><li>1. Crafting &amp; articulating user interview questions</li><li>Synthesizing user interview results</li><li>Maintaining proper project scope without much creep</li><li>Structuring user flows and paths</li><li>Trusting the process and my design workflow</li><li>Designing a new system</li><li>Designing a new functionality for a mouse or typical gaming controller</li><li>Designing for scale on a large screen TV</li><li>Information Architecture — how many screens and submenus are necessary?</li></ol><p><strong>Next Steps</strong></p><p>Our work as UX Designers is never done. There is always more to research, design, and refine.</p><ol><li>Mapping Key interactions between screens</li><li>Designing all end-to-end screens</li><li>Defining key paths</li><li>User testing</li><li>Research based design iteration</li></ol><p><strong>Let’s connect</strong></p><p>If you like what you read you can connect with me on LinkedIn — <a href="https://www.linkedin.com/in/ian-kelley-4a82a1119/">https://www.linkedin.com/in/ian-kelley-4a82a1119/</a></p><p>Thank you for reading and wishing you all the best,</p><p>Ian</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=95a201fd4a0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/users-have-no-limits-a-playstation-5-ux-case-study-95a201fd4a0c">Case study: Users have no limits</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Proudly serving Black Rifle Coffee — a UX case study]]></title>
            <link>https://uxdesign.cc/proudly-serving-ux-design-designing-for-black-rifle-coffee-520d33205aa3?source=rss-2d93c2b26e46------2</link>
            <guid isPermaLink="false">https://medium.com/p/520d33205aa3</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[coffee]]></category>
            <dc:creator><![CDATA[Ian Kelley]]></dc:creator>
            <pubDate>Wed, 26 Aug 2020 19:27:18 GMT</pubDate>
            <atom:updated>2020-09-03T10:56:20.887Z</atom:updated>
            <content:encoded><![CDATA[<h3>Proudly serving Black Rifle Coffee — a UX case study</h3><h4>Researching possible solutions to solve issues within Black Rifle Coffee’s user purchasing experience. This case study outlines my process, findings, and design concept.</h4><figure><img alt="An animated gif displaying the new product search landing page." src="https://cdn-images-1.medium.com/max/900/1*LE7_PMOVIXLx0xXUv2XYlg.gif" /></figure><p>I’ve been a fan of BRCC for many years (long before my adventure into UX Design). However, every time I used the website to purchase coffee something felt off, but I couldn’t put my finger on it. It wasn’t until I began studying UX Design at Maryland Institute College of Art that I had the confidence and skillset to explore this problem. So I pulled on my cowboy boots, nested my pomeranian into her bed, and set out to explore these two guiding ideas:</p><ol><li>Research the usability of Black Rifle Coffee Company’s e-commerce website.</li><li>Specifically, research how might the user’s purchasing experience, or journey, be improved?</li></ol><p>My initial assumption was the visual experience is just too much. The visual hierarchy confused me and I assumed it may overwhelm other users too. It is my belief that the current design state can be improved by implementing UX Design strategies that reduce the user’s cognitive load that may lead to an increase in revenue.</p><h3><strong>My Design Process</strong></h3><ol><li>General Research</li><li>User Interviews &amp; Analysis</li><li>BRCC Heuristic Evaluation</li><li>User Flow map (current state) analysis</li><li>User Persona Development</li><li>Competitive Analysis</li><li>User Testing (current state)</li><li>Drafting User Epics &amp; Stories</li><li>Wireframing</li><li>Prototyping</li><li>User Testing (prototype)</li><li>Evaluate &amp; Iterate</li></ol><h3>General Research</h3><p>It’s important to start with high-level research of the company and the brand. My research aimed to collect information in order to better understand BRCC: who they are, where they came from, their ideals, and their customers. As a longtime fan, I’ve been slowly researching them by purchasing their product and consuming their digital content.</p><figure><img alt="16oz pint glass with delicious, swirling coffee." src="https://cdn-images-1.medium.com/max/1024/0*M0BiCdaoAFygTxns" /><figcaption>Photo by <a href="https://unsplash.com/@demidearest?utm_source=medium&amp;utm_medium=referral">Demi DeHerrera</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>User Interviews &amp; Analysis</h3><p>In summation, 8 users were interviewed and they provided a wealth of information regarding their wants and expectations while shopping for and purchasing coffee. I quickly discovered common patterns amongst the users.</p><h4>Patterns</h4><ol><li>Users expressed how important the sensory experience is when buying coffee.<br><strong>A</strong>. Users expressed a want for clear product descriptions articulating how the coffee will taste and smell.<br><strong>B</strong>. Users shared stories that they often buy coffee in-store versus online because they can smell the coffee and gauge how it might taste.</li><li>Users want to know how coffee product A is different than coffee products B, C, and D.</li><li>Users expressed a want for sample bags of coffee with their online purchases. Most of the users stated they are unlikely to buy a new or unfamiliar coffee online unless it been recommended by someone they trust.</li><li>Users expressed a need for a user interface that is simple and efficient.</li></ol><h4>Insightful interview takeaways</h4><ol><li><strong>Added value<br></strong>User’s want more from their order. Based entirely on the interviews, two ways to address this opportunity were brought up. First, users want sample bags of coffee added to their order. Interviewees expressed they were unlikely to buy coffee that had not been recommended by a friend or they hadn’t experienced prior. Second, one user stated that in order to gain his membership to a monthly coffee club, he wanted more than his bag of coffee. He suggested if a brand provided sample bags of coffee, reading material, or other incentives that would encourage him to sign up.</li><li><strong>Product comparisons</strong> <br>This insight moves beyond the user’s desire to have clear and easily understandable product descriptions. Users expressed they want to know how product A is different than product B.</li><li><strong>Sensory input<br></strong>Users expressed that smelling the coffee is a key moment when purchasing coffee at a store. Perhaps, in addition to clear product descriptions, add a description of what the coffee smells or like or how the coffee may make them feel. One user described how coffee was a bonding experience with his military unit and when he woke up and smelled the coffee, it helped calm him.</li><li><strong>Purchasing proficiency<br></strong>Less click is best. Users described that the longer they’re on a website the less likely they will complete their purchase. How can return users be directed better to more quickly and efficiently complete a transaction?</li></ol><h3>Heuristic Evaluation</h3><p>My goal for the heuristic evaluation was to identify any problems and pain points associated with BRCC’s user interface. During my own personal use, as an “expert-user”, I was confused and irritated by my experience. It simply didn’t feel right. This feeling provoked my interest to study why.</p><h4>Heuristic Insights</h4><ol><li><strong>Features &amp; Functions<br></strong>The website scored middle ground which I thought was relatively low. I gave each evaluation within a score of 3 out of 5. Refining the visual design and organization of the information would easily increase the rating.</li><li><strong>Homepage<br></strong>The homepage scored low as well. Again, each evaluation within scored a 3 out of 5. <em>*To note, the homepage has been redesigned since my initial evaluation and it appears more usable.</em></li><li><strong>Navigation<br></strong>Another low earning: 3 out of 5. I would like to see the overall hierarchy and information architecture improved. Almost all pages have competing content and information that distracts the user from completing the main goal(s) of the website — to complete a purchase.</li></ol><h3>Competitive Analysis</h3><p>My competitive analysis involved assessing how the competition has designed their websites to solve for similar experiences. I researched 8 other coffee companies (Cafemam, Invader Coffee, Heart Coffee Roasters, Onyx Coffee, Starbucks, Warfighter, Peet’s, and George Howell Coffee) focusing on their purchasing flow and the visual hierarchy of the user interface.</p><h3>Usability Testing (current state)</h3><p>My goal with testing the current state was simply to watch and observe users interacting with BRCC’s user interface. This step validates my assumptions, but it also brings awareness to new user pain points and opportunities to design rewarding experiences.</p><h4><strong>Usability Test Breakdown</strong></h4><ol><li>5 users tested</li><li>Each user was asked to complete 3 scenarios while talking aloud to help provide insight into their experience and internal interpretation of the process</li></ol><p><strong>Scenario 1<br></strong>Next week is your friend’s birthday and they’ve shared that they want to try BRCC’s coffee. How would you purchase your friend one bag of ground coffee?</p><p><strong>Scenario 2<br></strong>You remembered that your friend recently purchased a coffee grinder and told you how they really enjoy fresh medium roast coffee. Change your order to one bag of medium roast whole-bean coffee.</p><p><strong>Scenario 3<br></strong>After adding the bags of coffee to your cart, you realize BRCC has a coffee subscription service. You decide to gift your friend a coffee subscription instead. Purchase your friend a medium roast coffee subscription that renews every 30 days.</p><h3>Wireframing &amp; Prototyping</h3><p>During the usability testing, I asked users to talk aloud and voice what they were thinking while completing each scenario. Their collective voices illuminated the issues below. After synthesizing the results of the usability test and reflecting on the original user interviews, I began to sketch potential solutions to alleviate user pain points.</p><ol><li>On the product page, there’s a lot of visual information to digest and interpret.</li><li>On the product search page, the hero image contains 3 actionable items that slow the user down</li><li>On the product search page, there are inconsistencies underneath product name and description.</li><li>Users encountered slow load times on all pages.</li><li>On the homepage, the main CTA is below the fold.</li></ol><h3>A freshly re-designed UI</h3><figure><img alt="A new user interface for the product search landing page." src="https://cdn-images-1.medium.com/max/1024/1*-lhvN4klofJURr6-GGT_4w.png" /></figure><figure><img alt="A newly designed user interface for the product landing page." src="https://cdn-images-1.medium.com/max/1024/1*r2hoysOHE2GQI4_PhSMFWw.png" /></figure><figure><img alt="A desktop mockup of how the coffee product landing page will appear." src="https://cdn-images-1.medium.com/max/1024/1*iguuBjg-xwTJFFsjrBKhfQ.jpeg" /></figure><p>In short, the new user interface is improved with the below updates:</p><p><strong>Coffee product search landing page</strong></p><ol><li>Group coffee by roast type with headers displaying what section the user is viewing.</li><li>Redesigned product description area.</li><li>Removed the hero image with the three CTAs.</li><li>Added a quick hover state button “add to cart” to go along with the robust product information “shop” button.</li></ol><p><strong>Product landing page</strong></p><ol><li>Redesigned the visual hierarchy to help direct customers more efficiently and quickly to “Add to cart”.</li><li>Reorganized the structure of the page to emphasize primary, secondary, and tertiary user and business goals.</li></ol><figure><img alt="An animated gif displaying the newly designed product landing page." src="https://cdn-images-1.medium.com/max/900/1*Y6doElnOWA7uoHF0l9ooGA.gif" /></figure><p>If you’ve made it this far in my abridged case study, <strong>thank you</strong>. As it goes with any UX project, there is always more work to be done. If we’re truly champions and advocates for the user, we are continuously researching how we may improve their experience.</p><p><em>A big shout out to everyone on Linked In that commented and interacted with my original BRCC case study. Your interactions and tagged comments allowed me to present my research to the top-brass at Black Rifle Coffee.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=520d33205aa3" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/proudly-serving-ux-design-designing-for-black-rifle-coffee-520d33205aa3">Proudly serving Black Rifle Coffee — a UX case study</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>