<?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 Troy Owens on Medium]]></title>
        <description><![CDATA[Stories by Troy Owens on Medium]]></description>
        <link>https://medium.com/@troy.owens?source=rss-ded3b36472d3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3cu2FttgBQ7pF66mNXA8Ug.jpeg</url>
            <title>Stories by Troy Owens on Medium</title>
            <link>https://medium.com/@troy.owens?source=rss-ded3b36472d3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:14:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@troy.owens/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[The Hungry Jazz Fan]]></title>
            <link>https://medium.com/design-bootcamp/the-hungry-jazz-fan-ed039fd74d30?source=rss-ded3b36472d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed039fd74d30</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[food]]></category>
            <category><![CDATA[utah-jazz]]></category>
            <dc:creator><![CDATA[Troy Owens]]></dc:creator>
            <pubDate>Sat, 01 Jan 2022 03:32:50 GMT</pubDate>
            <atom:updated>2023-08-14T16:46:02.977Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PcRetAjadfgowcb2SHDBeA.png" /></figure><p>As a Utah Jazz fan and season ticket holder, I’ve put in some hours on the team’s official app. I’m the type of fan that orders food every game. And because they’ve required you to use the app to order food the last 2 seasons, I’m very familiar with the pitfalls and annoyances of that experience.</p><p>When I’m at a game I want to limit the time I’m on my phone so I don’t miss any of the action on the court. The process of ordering food isn’t broken, but hungry fans who just want to eat could save some time with a few tweaks.</p><p>Below is an in-depth analysis of all the changes I made.</p><h3>New In-Area Tile</h3><p>When I open the app at a game, there are key things I to access:</p><ol><li>My tickets so I can get into the game</li><li>A map of the area to find my seats</li><li>A link to the Team Store so I can buy jerseys etc.</li><li><strong>MOST</strong> importantly, an easy way to order food</li></ol><p>You’ll notice instead of making these tasks easy to accomplish, the current Jazz app has a tile with 5 customizable button links, 4 of which are duplicated on the home page:</p><ol><li>News (appears <strong>twice</strong>)</li><li>Roster (appears <strong>twice</strong>)</li><li>Arena (appears <strong>twice</strong>)</li><li>Shop</li><li>Schedule (appears <strong>twice</strong>)</li></ol><p>If you’re like me, you tried to add a “Food” as one of the 5 customizable buttons. For whatever reason, that’s not option. Since 4 of the 5 buttons are duplicates, and the button to order food is buried, I decided to redesign this tile to include the 4 in-arena tasks that are needed most (keeping “Shop” as the “Team Store”):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R_anJs77KgHBUGrTU8HB3Q.png" /></figure><h3>Smaller Tile</h3><p>When you finally navigate to the where you can order food (Arena &gt; Order Food &amp; Drinks), you’ll see that the tile for each restaurant is absurdly large and takes up valuable space. You can only see 3 restaurants in the current app compared to 6 restaurants in my redesign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gB-dQZRujb4TuYnJr0kqEA.png" /></figure><p>The logos for each restaurant are just too large. They have also stacked them on top of text, leaving large white space on every tile that should be used to present information and save vertical scrolling space. I have to scroll 16 full page lengths to see every restaurant. I’ve redesigned the tiles so they save 58% of the vertical space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UIgRGd4w1ctIuVsVA19RmA.png" /></figure><h3>Info Hierarchy</h3><p>For some reason, the current app places the concourse (1st level or 2nd level) at the lowest level of hierarchy. If I’m on the Main Concourse, I first want to know if the restaurant I’m looking for is on the Main Concourse, or if I’m going to have to climb a large flight of stairs to get to the Upper Concourse. THEN I want to know which portal to go to get the food.</p><p>This has been redesigned to you can read the restaurant title without the Portal name crowding the title, and so the Concourse is before the Portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_nN7p9gSCr5DSrec0-Cnnw.png" /></figure><h3>Unused Button</h3><p>There’s a “button” (a generous name given its small black text with no button shape whatsoever) in the bottom left of the restaurant tile that I had not even noticed until I was working on this article.</p><p>It is essentially useless, as tapping anywhere on the tile takes you to the order screen for the restaurant. When I asked others who I attend games with if they had noticed the “button”, they hadn’t. I removed it as it isn’t needed or seemingly noticed by users; one less piece of text to scan on every single restaurant tile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Es3vJiCZWarrhrID4IHHCA.png" /></figure><h3>Alphabetical?</h3><p>Lists of text can be sorted in a variety of ways, but the way it was done in the app is fairly lazy. Someone coded the list to be sorted by Restaurant name, and then alphabetically, but only looking by the first letter of the Portal name.</p><p>The result is a list that mixes double letter portals (EE = Upper Concourse) and single letter portals (E = Main Concourse). For example, Bon Bon has 4 locations in the arena. The 4 locations are listed in the app in this order:</p><ul><li>Portals EE (Upper Concourse)</li><li>Portal K (Main Concourse)</li><li>Portal MM (Upper Concourse)</li><li>Portal Q (Main Concourse)</li></ul><p>The Main and Upper Concourse locations are mixed. It would be preferred to group them by concourse for each restaurant, as I have done in the updated designs below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yEoaDTs54F4KxwQr8Vio0A.png" /></figure><h3>Concourse Filtering</h3><p>The current app forces you to view both Main and Upper Concourse restaurants in the same list. As I discussed before, it’s 16 full page scrolls for the whole list. I cut that in half with my design, but the list length could be cut in half again if the user could filter the restaurants by concourse.</p><p>Using the same tab mechanism found on the current home page of the app, I’ve made concourse tabs which serve as filters to only show restaurants on the concourse you choose: All, Main, or Upper. People generally eat on the Concourse their seats are on. It saves time so they don’t miss the game, and who wants to go up and down flights of stairs?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0xr3q3OxnY5znfh0AkNcFA.png" /></figure><p>Additionally, sometimes you only have 2 minutes for a timeout or a quarter change and you need food fast. In those scenarios, I only want to see restaurants that are on my same concourse so I can pick up my food quickly and be back in my seat.</p><h3>Conclusion</h3><p>For hungry Jazz fans going to games, a lot of time could be saved if some small changes were made:</p><ol><li>Surface frequent in-arena tasks like ordering food to the home page</li><li>Reduce oversized images on restaurant tiles to save 58% vertical space</li><li>Sort each restaurant in the list by concourse and then by portal alphabetically</li><li>Add a concourse filter in the restaurant list to only see food on your concourse</li></ol><p>Dear Utah Jazz organization… I will trade UX work for tickets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed039fd74d30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-hungry-jazz-fan-ed039fd74d30">The Hungry Jazz Fan</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[UI is just micro UX]]></title>
            <link>https://medium.com/design-bootcamp/ui-is-just-micro-ux-c9e815ee0c0d?source=rss-ded3b36472d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9e815ee0c0d</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[resources]]></category>
            <dc:creator><![CDATA[Troy Owens]]></dc:creator>
            <pubDate>Wed, 29 Dec 2021 20:44:21 GMT</pubDate>
            <atom:updated>2022-01-02T16:12:26.319Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0F0FAj-sA53JroOltrKNTQ.png" /></figure><p>If you’re in the product design world you might often get asked these questions:</p><ol><li>Are you a UI designer OR a UX designer?</li><li>Do you have UI skills or UX skills?</li><li>Is this ticket for UI work or UX work?</li></ol><p>For those who don’t know, UI stands for User Interface (Design) and UX stands for User Experience (Design).</p><p>We know what someone means when they ask these questions, because we’ve been taught to draw a line between UI and UX. We’re told UI is the skin and UX is the bones. Form (UI) verses function (UX). We’re told that all a product needs is UX design and that UI design comes second, or third, or wherever.</p><p>I accepted this early on in my career but I’ve had trouble with it in recent years. The logic came out of trying to simplify and distinguish these areas as separate design specialties or disciplines, to make it easy to teach and explain to someone. While there are some differences, it’s not UI versus UX.</p><p>It’s all UX design. UI is just micro UX. Every part of the design affects the user’s experience.</p><h3>Example 1: Cars</h3><p>If all we cared about were the bones of a car (UX), then all we need is:</p><ul><li>The frame</li><li>The motor &amp; transmission</li><li>Wheels</li><li>Steering controls</li><li>Acceleration and brake controls</li><li>A seat</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IcBrNoUBDiJeztfSWI144A.jpeg" /><figcaption>Photo from ChrisFix on Youtube</figcaption></figure><p>Would you buy this car? It could take you from A to B. It serves it main function, but it would be wildly uncomfortable, unsafe, and terrible to look at. And with no labels on any of the controls, it may be dangerous or impossible to operate.</p><p>Yes, having an adverse reaction to the way something looks and feels is critical to the UX. The feeling a product gives you when you see, touch, or use it is part of your user experience.</p><p>Let see how the user experience improves when we add some skin (UI):</p><ul><li>Soft cushions on the seats</li><li>Leather seat covers</li><li>Doors</li><li>Windows</li><li>AC to keep cool</li><li>Heat to keep warm</li><li>Labels explaining buttons, levers, and guages</li><li>Your favorite paint color</li><li>Airbags &amp; seatbelts</li><li>Side and rearview mirrors</li><li>Cupholders for your favorite drink</li><li>A great stereo to play your favorite songs</li></ul><p>If you take all the skin off of your favorite car, is it still your favorite car?</p><h3>Example 2: Clothing</h3><p>You hate the cold, so you go shopping for some warm clothes. You buy the first items you see: some green snow pants, a large yellow turtleneck, knit polka dot pink mittens, and white rain boots.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fLzcsgJC42t9QJ9fFDaYyg.png" /></figure><ul><li>Are you warm?</li><li>Are the clothes comfortable?</li><li>Do you like how you feel when you wear them?</li><li>Do you like how you look in them?</li></ul><p>Yes, the clothes accomplished the function of keeping you warm, but what about the other goals you had for the clothes? Do they match your style, do they make you feel happy when you wear them? Would you prefer the turtleneck be made from a different material that doesn’t itch your neck?</p><p>In addition to keeping us warm or cool, we typically want clothes that we like the look of, are comfortable, and make us feel good when we wear them.</p><h3>Example 3: Red Button Colors</h3><p>Most people look at the color red as a destructive color. We often see it on a mobile app asking is if we want to delete something. Of the 2 options below, which is less confusing?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*ChHo__VpGcqpzmlAoqPdjw.png" /></figure><p>Option 1 encourages the eyes to look at the red button, misleading the user to press “Cancel” when they may really want to press “Delete”. We see this all the time, especially from products that want to prevent us from deleting an account with them.</p><p>Option 2 is the ideal way this should be displayed, so users know that red = destructive, stop, remove.</p><h3>Example 4: Font &amp; Color Choices</h3><p>Something as small as font and color choice affect the experience of the user, and also the the perception of their brand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K6lMBWOFgNpHgONHNmr1EQ.png" /></figure><p>Same company name, copy, layout, offer, experience, and consultants (just different headshots). One relies on bright gradient colors and the infamous Comic Sans and Papyrus font families. If you’re like me, I would much rather entrust my money with the company on the right.</p><p>The way you present the product (all of the visual design) matters. People want to invest their money with serious people, who take their jobs and clients seriously.</p><p>Option 1, while not <em>outright</em> a terrible design, would be better suited for social media platforms for teenagers and young adults.</p><h3>Conclusion</h3><p>UI is just micro UX. Everything you see in the design is part of the user experience. The best “UX” work can be ruined by terrible UI, resulting in a broken experience. UX and UI are just the same. One is high-level, and one is granular. Learn to value both as a complete UX experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9e815ee0c0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ui-is-just-micro-ux-c9e815ee0c0d">UI is just micro UX</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[Don’t Be Clever]]></title>
            <link>https://medium.com/@troy.owens/new-to-ux-dont-be-clever-a4b1b07faa00?source=rss-ded3b36472d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4b1b07faa00</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Troy Owens]]></dc:creator>
            <pubDate>Wed, 29 Dec 2021 17:48:48 GMT</pubDate>
            <atom:updated>2021-12-30T02:12:08.626Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oue0bbqX0Ej6yYN1hYkuqQ.png" /></figure><p>It’s tempting to want to design a creative or clever user experience, especially as a Jr. UX designer at the start of your career. You have a new boss to impress, and you don’t want anyone to think hiring you was the wrong decision.</p><p>Don’t be clever.</p><p>Your UX goals should center around designing an experience that feels familiar; something users know how to use with as little instruction as possible. This isn’t to say that there is no creativity in UX design. You often have to discover new solutions to usability problems. The trick is discovering solutions that either are familiar, or at least feel familiar to users.</p><p>Whether UX is new or old to you, you’re probably familiar with quantitative data (data and statistics from product usage) and qualitative data (user tests and interviews). These 2 things help inform your solution, but they’re not solutions. When looking for how to solve a UX issue, or introduce a new UX feature, I look to the familiar.</p><p>Ask questions like:</p><ul><li>Who are our product’s users? (User Personas)</li><li>What apps and experiences do they use daily?</li><li>What UX mechanisms are featured in those apps and experiences?</li></ul><h3>Example 1</h3><p>Great products feel familiar, even if they are entirely new.</p><p>I remember when I bought my first pair of Apple AirPods. I had never synced bluetooth headphones, or used any apple brand headphones before. It was unbelievably easy. It was so easy I almost felt guilty, as if I had cheated. These were the steps:</p><ol><li>Bring my AirPods near my iPhone</li><li>Open the AirPods case</li><li>A floating tile asked if I wanted to connect the AirPods</li><li>I agreed</li><li>AirPods synced</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sfs64HVgpq07RbQZk0Ddzw.jpeg" /><figcaption><a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJIhEgcypQQg&amp;psig=AOvVaw2DczSBq2sV-UnZ09QWXlmg&amp;ust=1640897242559000&amp;source=images&amp;cd=vfe&amp;ved=0CAkQjhxqFwoTCIic1eDwifUCFQAAAAAdAAAAABAD">How to connect AirPods — Apple Support</a></figcaption></figure><p>Not once did I have to go into settings. I opened the AirPods and tapped the iPhone screen one time, and it was done. The experience was so easy, it mimic’d familiarity. As if it was a skill I had practiced so many times it was second nature. That’s how well the experience was designed.</p><p>The lesson here? Design the product so simple and easy to use that the user thinks they’ve been using it their whole life. Let the experience convince them it’s familiar.</p><h3>Example 2</h3><p>Look at what already works, avoid what doesn’t.</p><p>Let’s look at something annoying, but clearly effective. In August of 2016 Instagram launched Stories. You could upload pictures and videos overlayed with effects, and they would expire in 24 hours.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-iTmqBCGnNGPLPca5VgYQ.png" /></figure><p>If you didn’t already know, every social media platform’s goal is to keep you using the app as long as possible, despite what they may say.</p><p>Someone at Instagram decided to use a Snapchat-like function and apply it as a new feature on instagram. Instead of sending disappearing direct messages, you could post disappearing messages for all your followers. If someone wanted to catchup on everyone’s latest posts, they had to check the app daily as stories would disappear in 24 hours.</p><p>I don’t have Instagram’s data, but I’m guessing engagement went way up. Now it seems all social media companies have a “story” feature:</p><ul><li><strong>Whatsapp </strong>Status, Feb 2017</li><li><strong>Skype</strong> Stories, Aug 2017 — Sept 2018 (RIP)</li><li><strong>Facebook </strong>Stories, March 2018</li><li><strong>Youtube </strong>Stories, Nov 2018</li><li><strong>LinkedIn</strong> Stories, Feb 2020 — Sept 2021 (RIP)</li><li><strong>Pinterest </strong>Story Pins, Sept 2020</li><li><strong>Twitter </strong>Fleets, Nov 2020 — Aug 2021 (RIP)</li><li><strong>Spotify </strong>Clips, Feb 2021</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fJUqOqNWvg_FhBjB6MxAQ.png" /></figure><p>When Facebook and Youtube added stories to their app, they didn’t have to worry about their users not knowing how to use the feature. It was familiar.</p><p>You’ll notice that Skype, LinkedIn, and Twitter all tried Stories but didn’t get the engagement they wanted. So they axed the feature; their core users didn’t like or want Stories. It’s important to be aware of your users’ needs and what is currently drawing them to your app.</p><p>The lesson here? Steal what has already been proven to work for YOUR users, and adapt those features as needed.</p><h3>Conclusion</h3><p>It’s tempting to push yourself to design a clever experience to impress your peers and bosses, but don’t be clever. Steal from the best, and use your creativity to design experiences that feel familiar, even if they are entirely new. Creating overly clever or creative experiences will often cause your users to rethink using your product, as it means they’ll have to relearn to do something they already know how to do.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4b1b07faa00" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>