<?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 Nathan Maus on Medium]]></title>
        <description><![CDATA[Stories by Nathan Maus on Medium]]></description>
        <link>https://medium.com/@nathanmaus?source=rss-cd87fc85f8f0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*F7ucLnDA90QGYRizQsjAwA.png</url>
            <title>Stories by Nathan Maus on Medium</title>
            <link>https://medium.com/@nathanmaus?source=rss-cd87fc85f8f0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:29:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nathanmaus/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[Let Your Stuff Work For You]]></title>
            <link>https://medium.com/nathanmaus/let-your-stuff-work-for-you-e0dfb0e11731?source=rss-cd87fc85f8f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0dfb0e11731</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[peer-to-peer]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nathan Maus]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 21:11:07 GMT</pubDate>
            <atom:updated>2019-04-29T21:11:07.592Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QH2jMt37XUZmERfuBxbc-A.png" /></figure><h4>Website UI Design | Case Study</h4><h4>Introduction</h4><p>Yoodlize is a peer-to-peer rental network that allows you to rent anything and everything from the community. Wether that’s from your neighbor or you’re on vacation looking to try something new. I was brought on during the early stages of development to design the UI for the website.</p><h4>The Problem</h4><p>Experiences are expensive… Say you want to kayak down the Salmon river, well a kayak costs a lot of money and it will most likely sit in your garage after 1 or 2 adventures. Imagine wanting to build a custom bed frame for your son, you need a lot of specific tools to do that.</p><p>People have already bought these expensive items and they’re usually just packed away in the garage collecting dust. There needs to be a way to bring these items into the wild where they can THRIVE… and that’s where Yoodlize comes in. We created a platform that allows people to EXPERIENCE more of what life has to offer without shying away because of the expensive gear that comes with it.</p><h4>Team</h4><p>Nathan Maus (me) — Designer</p><p>Jeremy Robertson — CTO &amp; Co-founder</p><p>Jason Fairbourne — CEO &amp; Co-founder</p><p>Natalie Fairbourne — CFO &amp; Co-founder</p><p>I was excited yet nervous to start this project. This was the first freelance gig I was offered since graduating from DevMountain and I was so grateful for the opportunity. Yet, I was out of my comfort zone and taking on a project that I didn’t realize was so large. During my first meeting with Yoodlize we discussed the website and the different pages that needed to be designed. I underestimated the amount of effort these screens would take. This design took me 6 weeks in total but I wish I had more time to test the product and validate my designs with potential customers.</p><h4>Research</h4><p>This project was different than anything I did in school because I wasn’t going through the UX process and was mainly doing UI and Visual Design. As much as I would have liked to conduct my own research and learn more about the users, that wasn’t in the budget and my timeline was short. When I arrived at Yoodlize, they had conducted some market research and held a few focus groups. From this initial research they had came up with the features they wanted to provide, and had rough wireframes laying out what would go on each screen.</p><p>So my work started a little differently then any of my other projects and I got straight to creating more detailed wireframes and diving right into the visual aspect of the project. Since I didn’t have the time to conduct my own research I looked at other companies (AirBnB, VRBO, Lyft, etc.) in the peer-to-peer space for inspiration and validation.</p><p>From a high perspective, the experiences I needed to design were the homepage, item description and rental flow, dashboard, login/signup flow, search and browse functionality, and the flow of listing an item. Some of these experiences were easier than others. I’ll mention the more difficult issues I ran into below. Also, once you’re done reading please feel free to look at the InVision prototype at the bottom to see the other aspects of the design.</p><h4>Pain Point #1: Dashboard</h4><p>The dashboard took me some time to figure out. I needed to cram in a lot of information that the user could easily view and understand. The user needed to see their messages, calendar, listings, rentals, reviews, profile, and account information. This was a lot of information to cover and it started to dawn on me, the true size of this project.</p><blockquote>How was I going to organize all of this information so it was easy to understand and navigate?</blockquote><p>First thing first, the initial screen of the dashboard needed some key information. I decided to include new messages, upcoming rentals, and recent reviews. This allowed the user to quickly see if they had new requests, any upcoming rentals, and make sure they kept their ratings up by staying on top of new reviews.</p><p>For the navigation, I went with a Material Design styled secondary navigation bar. This style navigation is visually easy to digest and understand. It takes up little space and really fit the look we were going for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HrV08JxVENOo5TmgKbM3DA.png" /></figure><p>Although there was a lot of important information in the dashboard, I found it easy to design the layout for most pages. The big issue I ran into was with the calendar. I needed a calendar that could show me all the listings and rentals I had upcoming, along with any information that may be necessary. What if you have 20 items listed… how do you see these items on a calendar?</p><p>I took a step back here. You can’t visually show an infinite amount of items on a single calendar, it’s just not possible. It could show a max of 2 items per day before the text got too small and it wasn’t accessible anymore. So, I decided to create two views for the calendar: an item view and an overview of each week. The first view I was going to design was the single item view.</p><p>For this view I needed an option to switch between different items and types of rentals (Listing or Rental). On top of that I needed a way to block out days for the times the user wanted to use their item and view rental information. I used a card based approach throughout my designs because I believe they do a great job at grouping important information, making it easier to digest.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DkcoarD8RMwFkr-W18ozGw.png" /></figure><p>As you can see, at the top of the screen you can quickly switch between items and types of items and well as quickly jumping to specific months. On the right, the card information for the selected rental period would stay static and always present even if you scroll down through the calendar. This card view gives you access to important information and allows you to quickly jump to your messages with that user. Another important feature is the ability to leave yourself a note for a specific rental period. If a user blocked out a few days, months in advanced, then canceled those plans… this helps them remember why those days were blocked and would help the user bring in more profit by reminding them to rent these items during that period.</p><p>Unfortunately. I wasn’t able to design the second view of the calendar in my time with Yoodlize as we decided it wouldn’t be making it to the MVP. I briefly described my ideas with them and mentioned that it would be a necessary feature to include in a future release.</p><h4>Pain Point #2: Search Feature</h4><p>One large functionality that I was getting stuck on was the search function. Since Yoodlize was a limitless platform, how was I going to portrait all the categories, sort parameters, items, and a map in a visually appealing and easy to use page? I dabbled with a few different options that ended up taking up too much real estate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lNpZKp7M5SwGHL5NJuqMtQ.png" /></figure><p>First option was to have the search, sort, and categories on the left side of the page. The categories and sub-categories were in dropdown boxes, this created a lot of friction due to the fact that we could potentially have a lot of categories. No one wants to scroll through endless options trying to find what they’re looking for. With this option there was two rows of item cards in the middle and on the right side of the screen was a map. To make everything fit the item cards were pretty small, and the map was narrow. This option wasn’t going work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ihqy5Ky7Q3D_hIBFa-TK4g.png" /></figure><p>The second option I came up with was to have the search, sort, categories, and map take up the top half of the screen. On the left was the search, sort, and categories. The categories and sub-categories were similar to the first option and were in dropdown boxes. The map took the top-right quarter of the screen. This option allowed for slightly larger item cards which was nice but the visual emphasis on the screen was the search area and the map. This took away from the importance of the items the user was searching and still took up too much real estate on the screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_NFOhBYywpw8iREyZ-q7FA.png" /></figure><p>The third option, and not the last, was similar to the second option. The search area stayed in the same place but what changed was the map. I moved the map below the search area. This meant the left half of the screen was taken up by the search options and the map. This allowed the item cards to become larger, again bringing more importance to the items. With the items taking up the right side of the screen, it was visually more present to the user and it was easy to navigate between search and browsing your results. But, the search area was still taking up too much space and I needed another option.</p><p>The fourth and final option, was quite a bit different. I placed the map on the right side of the screen and it extended from top to bottom. This gave the user a larger map to easy search items closer to them. The biggest change though was the search, sort, and categories section. Instead of placing this information in a box, I created a second navigation just under the header. In this secondary navigation bar, I placed the categories, sub-categories, filter options, and sort options. Then I placed the search bar and location just above the first items on the left. This method allowed me a larger map, larger item cards, and an easy to use search function. The visual hierarchy changed from the search and map function being the user’s first focal point to the items available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*As1e7_CE1xm3BZBwJNcv3Q.png" /></figure><h4>Homepage</h4><p>Yoodlize is all about helping users Experience more! That’s why we based the entire homepage on experiences. The hero shot will always include someone doing a really fun activity such as: surfing, camping, skiing, riding a dirt bike, etc. This inspires users to go out and try these activities and we provide a platform where they can rent the necessary items. As you scroll through the categories on the homepage, it was designed to spark the users imagination on the limitless possibilities! Inspire them to finish their DIY project, throw an epic birthday party, be unpredictable, or create something new.</p><p>We pull items from different categories and feature them in these 5 categories on the homepage.</p><ol><li>Imagine</li><li>Work</li><li>Play</li><li>Create</li><li>Live</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vt_wCr8lIQ_hUSMoq90G5A.png" /><figcaption>Homepage scroll flow that shows Experiences and Category sample</figcaption></figure><h4>Listing an Item</h4><p>At first, listing an item seems simple enough, you just add your description, upload a couple photos, and you’re making money. However, our users needed a bit more than that. They needed to choose the categories and sub-categories they were going to post this item in, write their title and description, upload photos, choose pickup/delivery options, blackout days, price, insurance options, and rental rules. That’s a lot, and how does the user know how to get the most out of these options?</p><p>To answer this, I decided to walk the user through this step by step with tips on how to get their products recognized. They also have the option to skip the process and go to a single page with all the information needed without the tips. This is good for users that have posted before and don’t need any help to optimize their posting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8iQptmq4xGlPHNfyOjcnJw.png" /><figcaption>Sample of the first few steps of listing a product</figcaption></figure><h4>Animations</h4><p>I created a couple animations in Principle to show the movement for the search bar on the homepage and for hiding the map in the search section. The search bar animation is really cool but after talking with my developer the implementation was going to be difficult and definitely wasn’t making it to the MVP. I wanted the search function to always be available no matter where they were on the screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*w6ljAQ1zm8vrRQgoJkTKaQ.gif" /><figcaption>Initial Animation of the Search function</figcaption></figure><p>The map animation was easier to animate and would be relatively easy to implement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ortOExtGGxrO1AZWZZ7-Q.gif" /></figure><p>Below is a link to my InVision prototype. Please go through and play around. Feel free to let me know if I missed anything or if you have any comments on the project.</p><p><a href="https://invis.io/DSGWBJCNP49">Click here to view the project `Yoodlize`</a></p><h4>Success</h4><p>Success to me will come when this site launches in January 2019. To finally see my designs come to life in the wild will be amazing. I really enjoyed working with the Yoodlize team on this project and I want to thank them for giving me the chance to show off my skills. I am very pleased with the designs I came up with in the short period of time I had working on the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zRN6jngojudrZOiRNi6Lzw.png" /></figure><h4>Lessons Learned</h4><ol><li><strong>Scope Creep.</strong> This was my first real project since I graduated from DevMountain. I was really excited and didn’t know what I had gotten myself into. Mainly because I didn’t know the right questions to ask during my initial meeting. I thought 4–5 key pages and a few extra supporting pages would be relatively simple and quick, but I just didn’t dig deep enough to realize how much each page would require. For future clients, I will have a more in-depth discussion on what is needed and write these out so everyone is clear on expectations. And most importantly, this will help me give an honest timeline that will allow me to deliver a great product while staying within the clients budget.</li><li><strong>Process. </strong>In school we were taught to follow our process to make sure you are designing the right product. Sometimes you can’t go through your process entirely due to budget, timeline, etc. In these times you need to improvise and pick and choose methods to validate your designs. This took me a little bit to realize, and when I did I validated many of my designs by looking at other products that have been built on the peer-to-peer business model. But from my experience, every possible moment to get real data from potential customers would have benefitted us greatly.</li></ol><p>If you’re based in Utah, go check out <a href="http://www.yoodlize.com/">yoodlize.com</a> and start renting gear!</p><p><strong>Thanks for reading! If you like it, clap away! If you want to talk further, connect with me on </strong><a href="https://www.linkedin.com/in/nathan-maus/"><strong>LinkedIn</strong></a><strong> or go visit my portfolio page at </strong><a href="http://nathanmaus.co/"><strong>nathanmaus.co</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0dfb0e11731" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nathanmaus/let-your-stuff-work-for-you-e0dfb0e11731">Let Your Stuff Work For You</a> was originally published in <a href="https://medium.com/nathanmaus">Nathan Maus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Taking an Idea into the Wild]]></title>
            <link>https://medium.com/nathanmaus/taking-an-idea-into-the-wild-4bfb073224ce?source=rss-cd87fc85f8f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bfb073224ce</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[social-impact]]></category>
            <category><![CDATA[food-waste]]></category>
            <dc:creator><![CDATA[Nathan Maus]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 15:30:55 GMT</pubDate>
            <atom:updated>2018-11-13T16:27:37.448Z</atom:updated>
            <content:encoded><![CDATA[<h4>CoCreate Hackathon</h4><p>I recently watched a video that inspired me to find a way to save our planet from the polluted state that it’s in right now. We put greed and our own personal gains over Earth and the future of the human race. We do this because in our lifetime we won’t see, or don’t want to see, the effects our actions have on this planet.</p><blockquote>How can I use design to make an incredible improvement to our planet and our lives?</blockquote><p>I had been contemplating an idea and had done some research to see what was possible. I then learned that <a href="http://www.commoncreatives.com/">Common Creatives</a> was hosting a Hackathon at <a href="http://www.devmountain.com/">DevMountain</a>, the bootcamp where I learned UX Design. This was my opportunity to take the initial research I had done and turn it into a working prototype. This was exciting yet slightly terrifying. Taking your idea, convincing people to help you build it, and then presenting it to a board of judges all within 16 hours is a feat to say the least. The hackathon started at 7PM and ended at 11AM and was fueled by endless coffee, JDawgs, and an assortment of snacks all provided by CoCreate in hourly giveaways.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hQsptZ0La_1GJJrTnWRfrg.png" /><figcaption>www.commoncreatives.com</figcaption></figure><p>Now, let me give you a sneak peek into the idea that helped me take home first place and, best of all, a few amazing introductions and interested parties. I’m not going to give away too much information just yet, but follow me on <a href="https://www.linkedin.com/in/nathan-maus">LinkedIn</a> and I’ll release more updates as this product progresses.</p><h4>The Idea</h4><blockquote>When you think of the main causes of pollution, where does your mind go?</blockquote><p>Chances are your first thought is the burning of fossil fuels, while that may not be far off from true, one of the largest contributors of methane gas in our atmosphere is food waste. In America we waste about 40% of the food we manufacture. Let me repeat that… WE WASTE ABOUT 40% OF THE FOOD WE MANUFACTURE. And for some reason we have people starving in every country in the world. Not to mention the amount of resources that we consume to create that food just compounds the problem. As the human race, we need to change for the good of everyone.</p><p>My idea is to create a platform that helps businesses effortlessly donate excess food and to get that food into hungry mouths. This idea would kill 2 birds with 1 stone: cut down on greenhouse gases and feed the hungry. This is going to be a huge task but it’s doable and if more people start to realize the need for ideas like this, we can really make a difference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y1YtaDuubhVwglY647m_BA.jpeg" /></figure><h4><strong>The Execution</strong></h4><p>The first hour of the event was for team building. I met a developer, Eli Smith, who seemed to know what he was doing. I explained my vision and he knew exactly what to do. We started bouncing ideas around and I knew it was going to be a productive night. Since I had already done some research into the problem I had an idea the direction I wanted to take the project. At 8PM, we started whiteboarding and brainstorming possible features and what each feature we would look like. Due to the nature of a hackathon, I made a lot of assumptions based on my research and what I thought would be useful to my customers.</p><p>Again this was just overnight, we had 16 hours to make something functional. So we took this short timeframe to create one aspect of the platform and that was from the donors perspective. Once we had finished deciding on our features, Eli started creating the API’s that we needed while I broke down the features to determine what components we would need to create.</p><p>It was probably around 10PM when I finally started sketching our solution. After sketching a few ideas I checked in with Eli to make sure my ideas would be doable in our timeframe. After reflecting on my experience, I think this was one of the main factors that allowed us to build a functional, well designed product in just 16 hours.</p><p>Next, I started creating low fidelity wireframes so Eli could start developing the layout. This is when I realized how little time we had. It seemed like every hour only lasted 15–20 minutes. More Coffee…</p><p>Let’s jump forward now because I don’t want to spend another all-nighter, this weekend, writing this article. Around 7AM we had a functional product that allowed us to demonstrate how businesses could make donations and track the donations they have already made. The site was live and was populating real data (for now). Now it was time to tweak the product and get the visual aspects correct.</p><p>At this point we were both hitting a wall, we had been working for 11–12 hours and knew we had another 4 hours to go.. Eli went to take a power nap while I decided to stay up and make notes on all the visual aspects that needed to be updated. Luckily we still had coffee and endless snacks.</p><p>Finally, after a few more hours, we made our last changes and called it a night (or morning). Neither of us had seen what other teams were working on and had no idea how our product compared.</p><h4><strong>How to win a Hackathon</strong></h4><p>Our panel of judges were amongst the best in their respective field. Our first judge was the Design Director of a local agency called <a href="https://underbelly.is/">Underbelly</a>. The second judge was the Technical Director for <a href="http://rallyinteractive.com/">Rally Interactive</a>, another local agency. And our final judge had started multiple companies and was currently the Director of Corporate Strategy and Marketing for <a href="http://www.elearningbrothers.com/">eLearning Brothers</a>. To win this thing, I knew I had to create a product that would touch on all these areas.</p><p>For the Design aspect, I used a card style dashboard to keep it clean and easy to understand. Dashboards are great to use to get a quick overview of your entire account. Since this project is pretty complex, I found this method would help me organize all the content.</p><p>During the hackathon we didn’t use any complicated tech, but in the long run I’ve had some ideas about how I can make this product better. So, I made sure to mention my ideas on how I would integrate new technology into the product.</p><p>Lastly, I went into details on how I was going to make money and my go forward strategy. As well as touching on possible paths I could take once the product has gained some traffic.</p><p>I think the number one thing that helped us win was how well rounded our idea was. First, I had an idea that solved a very complicated problem that everyone can relate to and participate in solving. Then I understood the business side of the solution. How we were going to make money, get people involved, etc. I presented the problem I was trying to solve, the business requirements, and my idea before showing the actual product. I believe this helped show my understanding of the problem and my passion in solving it. So, if you’re deciding to participate in a hackathon, make sure to choose an interesting problem to solve and understand all aspects of the solution.</p><p>Last tip, stay in good communication with your developer. You have such a small window to build a product, you just can’t afford to waste any time. Make sure what you’re designing will be doable and figure out what the plan is before anyone starts designing or writing code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7WQUqyLRC68P5jZVW7ol9w.jpeg" /><figcaption>Our Dashboard Solution</figcaption></figure><p>I almost forgot, so for first place we took home $500… in $1 bills 😆. This was amazing, but the best part of it all was the opportunities this hackathon presented. After it was all finished I had multiple people approach me to learn more about the project and see how they can contribute. I’m so excited to see where this product goes and I’m slightly terrified with how fast it’s happening. But that’s all part of the fun right!</p><p><strong>I had so much fun at this event and I can’t wait until next year! Maybe I can build something with one of you. Thanks for reading! If you like it, clap away! If you want to talk further, connect with me on </strong><a href="https://www.linkedin.com/in/nathan-maus/"><strong>LinkedIn</strong></a><strong> or go visit my portfolio page at </strong><a href="http://nathanmaus.co/"><strong>nathanmaus.co</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bfb073224ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nathanmaus/taking-an-idea-into-the-wild-4bfb073224ce">Taking an Idea into the Wild</a> was originally published in <a href="https://medium.com/nathanmaus">Nathan Maus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Millennial News | UX Case Study]]></title>
            <link>https://medium.com/nathanmaus/millennial-news-ux-case-study-6aad929302f9?source=rss-cd87fc85f8f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/6aad929302f9</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[news]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nathan Maus]]></dc:creator>
            <pubDate>Mon, 16 Jul 2018 21:51:57 GMT</pubDate>
            <atom:updated>2018-07-16T22:03:32.751Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VzzZONMsTofnQnGSZ5EOwg.jpeg" /></figure><h4>Android Native App</h4><p>During my time at DevMountain, a UX Bootcamp, I designed a news app that was targeted towards millennials. My team and I presented news in a way that removed initial bias and gave the reader the ability to choose for themselves.</p><h4>The Problem</h4><p>Millennials are always on the move and because of this, they don’t have a lot of time to sit down and read a newspaper. Most of the news they receive comes from social media and unverified sources, which needs to be taken with a large grain of salt. It was also noted that most millennials avoid watching the news, due to a large amount of negative and depressing news that is reported on a daily basis.</p><h4>Team</h4><p>Nathan Maus (me)</p><p>Tara Shipp</p><p>Micaiah Buttars</p><h4>Research</h4><p>We surveyed 46 millennials between the ages of 18 and 28 to understand the issues they have with the news.</p><p><strong>These are the pain points that stood out to me:</strong></p><ul><li>Millennials don’t like watching the news because most news stations focus on ‘depressing’ news.</li><li>Millennials are on the move, now more than ever, and they don’t have a lot of time to read long articles.</li><li>To check the validity of a story they will check the same news coming from different sources. Making it tedious to learn what the facts are.</li></ul><p>After gathering that data I wanted to validate it by reaching out to a local expert. I got us an interview with the head of digital solutions at KUTV, a local news station in Salt Lake City.</p><p><strong>This is what we learned:</strong></p><ul><li>The average time a millennial spends with their news station is 6–7 minutes</li><li>Millennials are visual learners</li><li>Based on KUTV’s internal research, millennials love live footage; KUTV even has tools to track social media posts so they can present information as it comes through. Making every citizen a live reporter for KUTV.</li></ul><p>The biggest insight that we gained from KUTV was the realization that millennials love live footage. In our initial survey, we weren’t aware of this fact so we didn’t explore it too much. After learning about this from the news station we were able to dig a little bit deeper and improve our focus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BO-f9zt-tzwtRr_5HFiHKg.png" /><figcaption>Primary Persona based on Research Conducted</figcaption></figure><h4>Ideation</h4><p>Now it was time to create a solution. We weren’t here to recreate the news, just present it in a different way. We decided to pull content from the top networks, and weed out any click-bait sources.</p><p>During our process, I kept asking myself, “How do we present news in an unbiased way?” At first, we thought to create our own content that would list our “facts” from both sides of the story. But how do we stay unbiased? Obviously, we will have our own opinions and that will show in our writing even if we try to be neutral.</p><p>Everyone has a bias, no matter who you are or what you do. It’s human nature. It’s how we’re raised, our parents have their ideals and push those onto us. We can’t get rid of bias unfortunately.</p><p>We want a way for users to consume the content, and make their own decision about the information…</p><blockquote><strong>What would you think of the news if you didn’t know which station it was coming from?</strong></blockquote><p>This question helped us create a very unique experience for our user, and could change their biases completely. We removed the source from every article to give our users the freedom to consume the information with an open mind. Once they have finished the article, they could check the source to see which station wrote it.</p><p>Users had a fun time with this. They would guess which station wrote the article before checking the source. We also give them a quick, yes or no, question to see how they feel about the topic. Once answered, it would show them how they compared to everyone else that read the article.</p><p>Now, how can we solve the issues that millennials have with the current way the news is shown to them?</p><h4>Pain Point #1</h4><blockquote>Millennials don’t like watching the news because most news stations focus on ‘depressing’ news.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*agdzQdZrPfBpadwUqmPoJg.png" /><figcaption>Low-fidelity wireframe of My News</figcaption></figure><p>We gave the user a ‘My News’ section. This section would be their homepage, so when the app launched they wouldn’t be overwhelmed with depressing news. Here they could follow topics, specific issues, or stories they’ve researched and they would only see news based on what they follow. This allowed them to only see the news that’s important to them.</p><p>We decided to present news within topics. On our homepage, it would show you topics such as gun control, Facebook privacy, autonomous cars, etc based on current news articles. Once you found a topic you wanted to explore you would tap that topic and be presented with relevant articles and videos.</p><p>This prevented users from seeing ‘depressing’ headlines right off the bat. This also helped users dive deep into a specific topic instead of browsing through tons of articles to find more similar content. Our users didn’t have time for that.</p><h4>Pain Point #2</h4><blockquote>Millennials are on the move and they don’t have a lot of time to read long articles.</blockquote><p>Once you’re within an topic you had the ability to quickly tab between all content, articles, and videos; this gave the user a quick way to choose the format of the news.</p><p>With every article or video we post, there is a time tag near the headline that will tell the user the approximate time it will take to get through the content. Providing this time tag allowed our users to quickly find the news that they could consume at the moment.</p><p>Based on what I learned from KUTV, I knew that our users enjoyed Live news. This is a quick way they can learn what’s happening right now. We added the Live feature to our bottom navigation bar, so they could access this content from any page in our app.</p><p>Last but not least, some users don’t have enough time to read any articles. To solve this, we give the user an overview of the topic with quick facts from all sides of the story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*Cd4CgIn720N_DPtNcE1shg.png" /><figcaption>Low-fidelity wireframe of specific topic</figcaption></figure><h4>Pain Point #3</h4><blockquote>To check validity of a story they will check the same news coming from different sources. Making it tedious to learn what the facts are.</blockquote><p>This was very surprising and sad to me. We live in a culture where this is the norm. A place where we can’t even trust the media; we have to check multiple sources and jump through hoops, just to try and understand what’s going on.</p><p>We have an advantage here. Since we aren’t a single media source, we have the ability to compile information from multiple sources. Once the user explores a topic they will be shown multiple articles about the same topic or story. These articles will be from all the top news stations so our users don’t have to hunt them down. They can quickly flip through each article and understand both sides of the story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/1*c1PS8_NyCj2xaveVS0BZhw.png" /><figcaption>Swiping between articles based on the same topic</figcaption></figure><h4>Implementation</h4><p>Now it was time to start wireframing, and testing our app. Our first iteration of wireframes had a few problems that we discovered during testing. Initially, when you selected a topic a drawer would drop down and give you our quick facts on the topic. If you wanted to explore more, you would click an ‘Explore’ button and it would take you into the articles and videos for that topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*KypyBwQrvzbpSGHSSIgyug.png" /><figcaption>Wireframe showing original drawer</figcaption></figure><p>Our biggest concern during testing was that users were getting confused with this drawer. They didn’t know they were quick facts, a lot of them thought they were headlines and tried clicking them to go to those articles. That gave us the idea to change that drawer to include headlines instead of facts. This helped a little, users understood this but it was still clunky. The more I thought about this feature the more I knew it had to change. Micro-interactions need to withstand time. I knew that after the 100th time opening that drawer before exploring an topic was going to be a problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*iV6JuU5a5wGBTlt1tNNw3A.png" /><figcaption>Overview after removal of drawer</figcaption></figure><p>This led me to think of a different way to present the overview of the topic. We removed the drawer so that once you click a topic, it would take you right to the relevant articles. Then, if you wanted the overview we created a selection at the top of the screen that would show you those quick facts on this topic.</p><p>This resonated really well with my testers. They were happy that they weren’t forced to read those quick facts/headlines or make 2 clicks to get to the articles and videos.</p><p>Based on our research, we know that millennials are visual learners, so I wanted to present most of our content with pictures and videos. Each topic is designed with a photo representing the topic and the title of the topic on a card. This creates a very appealing visual design which is easy to use and navigate.</p><p>I chose to follow Material Designs guidelines for this project because, in my opinion, their navigation options work really well when you have a lot of content to show on a small screen. It helped to keep my design clean and easy to navigate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/343/1*vyNDf_DpzZhn6R7xZbyv8w@2x.png" /><figcaption>Home screen showing the My News Tab</figcaption></figure><h4>Visual Design</h4><p>Now that our wireframes and testing were finished, it was time to add visual aspects to the design. At this point in the project, our instructor split us up so that we could explore our own visual style. I was excited to tackle the visual aspects myself but was glad that I could still get feedback from my team to improve my design.</p><p>Colors were difficult to choose for this project. I knew the tone of this app had to be strong, trustworthy, and young. Two colors came to mind: red and blue. Red represents strength, leadership, courage, and determination. While blue represents: intelligence, communication, trust, and inspiration. These are great attributes for a news station, that is why almost all news stations are an iteration of these colors. But they also represent the Democratic and Republican parties… which we don’t identify with because we are trying to bring all relevant news to our users no matter what party they are affiliated with. I still wanted to keep within these two colors but I didn’t want it to look affiliated to either party.</p><p>I chose the main color of my app to be a shade blue, but I wasn’t sure what shade. So, I mocked a few palettes and asked some of my peers their opinion; I used a navy blue, cobalt blue, and baby blue for this test. The feedback was that the navy blue looked old and very much linked to the democratic party. The baby blue wasn’t serious enough. But the cobalt blue still communicated trust, and it drew in a younger crowd. Cobalt Blue it is! I also ended up using red as an accent color. It compliments the cobalt blue really nicely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/1*-gZ0QtVXuHFykYtLoHs8jw@2x.png" /></figure><p>Again, I followed the guidelines from Material Design for this project because they are very successful at presenting information in a clean and precise manner. They do this with the use of cards and their elevation guidelines help create a recognizable visual hierarchy.</p><p>Below is a link to my InVision prototype. Please go through and play around. Feel free to let me know if I missed anything or if you have any comments on the project.</p><p><a href="https://invis.io/QSMZKC8BKEJ">https://invis.io/QSMZKC8BKEJ</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mg8Rj7DWmRHp5yJey73onQ.png" /><figcaption>Flow of final design</figcaption></figure><h4>Success</h4><p>Once the visual design was finished I tested it one more time to make sure I didn’t miss anything. The people I tested it with, loved the concept and the flow of the app. I presented them with the task of finding and reading the article “They led a national march. Now Parkland Students return to a school they say ‘feels like jail’.” (shown above) During this final testing, users an easy time completing the tasks. They also said that they would use this app as their main source of news if it was ever developed. Overall I was very pleased with the final product.</p><h4>Retrospective</h4><p>There were a few design challenges available that really resonated with me… The Millennial News app was not one of them. I don’t follow the news and politics don’t interest me, so I didn’t even know where to start with this project.</p><p>After starting this project I really started to enjoy it. What I loved most, was using my skills and applying them to a topic I didn’t know much about. I got to explore and learn more about something I wasn’t initially interested in. This may be the most exciting thing about working in design.</p><h4>Lessons Learned</h4><p>Don’t just put a Band-Aid on and expect the issue to be fixed, find the deep reason that is creating the issue. For example, this is what happened in our earlier design with the opening drawer. At first, we had quick facts located in the drawer and expected this was the issue users had and didn’t dig deeper. So we changed quick facts to headlines… That didn’t work either, so we stylized it more. We were stuck on that idea because we didn’t want to let it go. Once we dug a little deeper and really explored the issue, we realized it wasn’t the right fix and we had to scrap that design.</p><p><strong>Thanks for reading! If you like it, clap away! If you want to talk further, connect with me on </strong><a href="https://www.linkedin.com/in/nathan-maus/"><strong>LinkedIn</strong></a><strong> or go visit my portfolio page at </strong><a href="http://nathanmaus.co/"><strong>nathanmaus.co</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6aad929302f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nathanmaus/millennial-news-ux-case-study-6aad929302f9">Millennial News | UX Case Study</a> was originally published in <a href="https://medium.com/nathanmaus">Nathan Maus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Every Teen Seen | Case Study]]></title>
            <link>https://medium.com/nathanmaus/every-teen-seen-case-study-fe055b13bd6d?source=rss-cd87fc85f8f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe055b13bd6d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Nathan Maus]]></dc:creator>
            <pubDate>Thu, 26 Apr 2018 16:01:52 GMT</pubDate>
            <atom:updated>2018-04-26T16:01:52.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ggEqj9QypL17A8E2YGy-eg.png" /></figure><h4>UI/Visual Design iOS App</h4><blockquote>Since 2007 Utah youth suicides have tripled, from 3 per 100k to 8.5 per 100k, a drastic increase not seen anywhere else.</blockquote><p>When I first started researching this epidemic, I was heartbroken to hear the stats here in Utah. Why are teens feeling like they have no other choice? When Every Teen Seen (ETS), a non-profit organization focused on teen suicide prevention, approached us with an app idea I was happy to help.</p><p>ETS’ mission is to eradicate teen suicide in their communities through awareness, fun, education, and empowerment. The goal was to design an events app that helps struggling teens join this new community of supporters.</p><p>They had a developer who started building the app interface, but they needed our help designing something beautiful. I was apart of the design team for this project.</p><p>Our developer needed help with the visual design and with the overall interactions of the product. The app looked and felt very basic. He had the functionality ETS wanted but the layout, visuals, and overall feel of the app needed improvement.</p><p>The logo was edgy and distressed which is the opposite of what a suicidal teen needs. Also, the login paths are confusing. What does Join The Cause mean? What does Lead The Cause mean? I will address these later.</p><p><strong>Below is an example of the original interface.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*ZzvUCYSnUqOhvrrX-aNE2Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*1LNew9yM4i6SwCo_Xfl-5Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*7rBhzV2utqcM68pMgIPDAg.png" /><figcaption>This is what ETS originally had as their login and splash screen</figcaption></figure><h3><strong>Research</strong></h3><p>ETS needed a final design in 3 weeks, so we broke the project up into 3 sprints and we tackled it with a lean UX approach. Normally I would start conducting interviews but our limited timeframe prevented me from doing so.</p><p>I began with online research to wrap my head around the teen suicide epidemic that Utah was facing. I found a few resources in Utah that teens can use to reach out to someone to talk to or to report something anonymously. Some of these would be included in the resources section of our app. My online research led me to the University of Utah Neuropsychiatric Institute where I learned:</p><blockquote>Teens don’t feel comfortable talking about suicide to adults</blockquote><p>This led me to assume hotlines are inefficient. Due to these findings, we know our users need to feel comfortable using our app.</p><h3><strong>Design</strong></h3><p>Our team did a great job collaborating throughout the project, so I had a part in most screens. My main focus for this project was to design the profile page, donate now page, and the flow of how a user becomes an admin.</p><p>The features of this app were determined by ETS and include:</p><ul><li>Events page with the ability to RSVP</li><li>Resources page with useful information for teens to get help anonymously if they need to.</li><li>Profile page which allows users to see the events they’ve RSVP’d. This page also allows admins to see what you’re interested in so they could build events around common interests.</li><li>Admin’s view. Admins can view others profiles as well as create events for users to attend.</li><li>Donate now feature. This would allow parents to donate to Every Teen Seen.</li></ul><h4><strong>Admin access</strong></h4><p>ETS has specific users that are influential in teens lives. These users mainly consist of teens that hold a position at their school, adults, or counselors but if anyone is influential in this community they can contact ETS to become an admin. These users are then given an admin password so they can create events to help bring teens together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/281/1*A5OuLLm906FIjZ3aBMJbNg.png" /><figcaption>Edit profile page with Admin access at the bottom</figcaption></figure><p>The method ETS was using for admin access was cumbersome and confusing. For an admin to login each time, they would need to enter their login details as well as the ETS admin password. However, the majority of their users weren’t going to be admins but they could still see the admin login during their login process. This wasn’t acceptable; my goal is to make this process easier for admins. If admins don’t want to use the app then the app dies, because it is built off the events that they create.</p><p>To achieve this goal I did these 3 things:</p><ul><li>I designed the login page so everyone signed in exactly the same way, using their email address and password.</li><li>Next, I created an activation flow instead of requiring the user to type the admin password each time. This flow started on the users’ profile page.</li><li>Since most users wouldn’t activate an admin account, I kept the link small and near the bottom of the edit profile screen. Once a new admin activated their account, they could start creating events for users to attend. They would only need to do this once, removing the frustration caused by entering that password every time.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bSs7K1oatB5D_Z-Hw58ODQ.png" /></figure><p>When I showed this flow to our developer, he was so relieved because he was getting tired of typing in the admin password every time he wanted to look at his app. Success!</p><h4>Profile</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MbJBMpJgZrkICmo_shHkRw.png" /></figure><p>ETS didn’t want this app to be a social media app. You can’t follow anyone or have friends within this app. It is mainly used by an admin to see what interests you have so they can tailor events to your interests. So the profile page was going to be pretty simple.</p><p>I designed it so the user could see the events they’ve RSVP’d to and to add or change their interests.</p><p>At the moment, admins will have to go to each individual profile to see the users interests. ETS wanted to get the MVP out first and then revisit this limitation. If they were to contract me for the next stage I would create a page where admins could see specific interests from users within a certain radius. This would allow them to quickly get an idea of what kind of event they want to create.</p><h4>Tagline and Onboarding</h4><p>Based on some of our initial assumptions, the app needed to be friendly but also serious in nature. Opposite of the initial interface. Our users needed to feel part of a community. We needed to empathize with our users and convey that help is available. So we came up with a tagline that we all loved. It was inviting and creates a feeling of trust.</p><p><strong>You’re Seen, You’re Heard, You’re Not Alone.</strong></p><p>We also used this tagline as part of the onboarding process. We knew this would have an impact and we wanted it to be the first thing the user saw. We chose to use an automatic carousel that would cycle through different images with this tagline displayed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*utWTuWVELq5nG_Z0s0NJKA.png" /></figure><p>Another assumption was that teens may be reluctant to provide their personal data if they’re scared to talk about their suicidal thoughts. So, we gave the user the option to skip the login/signup page. This allows the user to see what the community was doing, and see how ETS may benefit them. After all, this app is about suicide prevention, so we don’t want to give the user any reason not get the help they need. However, if they want to RSVP to an event, an account would need to be created.</p><h4>Presentation</h4><p>At this point in the project, we had a total of 2 weeks before presenting our design to the developer and the CEO of Every Teen Seen. We used every last minute of that time to create a polished and feasible design. This was the first time I have presented any work to a CEO or developer, and I was nervous, to say the least. I was relieved to see how excited he was about the work we have done. We brought his imagination to a reality. He was excited to get the app developed and in the app store.</p><p>After presenting to the CEO it was time to go through every design aspect with the developer. For the most part, it went smoothly with just a few tweaks on the design and explanation of how things functioned. During our meeting, our developer mentioned the need for a donate page.</p><h4>Donation page</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*Sf9U1B7yNp1OoJtYlNaI-Q.png" /></figure><p>ETS’ goal was to have a page where users could easily donate to the cause. ETS relies on these donations to continue creating events and spreading awareness for suicide prevention.</p><p>They didn’t have PayPal integration at the time so they could only take payments via credit/debit cards.</p><p>As I was creating this page, I realized that users had to input a lot of information and it seemed overwhelming. This could deter users from donating. I decided to ask a few colleagues what they thought. They validated my suspicion that everything on the page blended together and was overwhelming. I decided to divide the page into three sections. One for the donation amount, one for the name &amp; address, and one for the payment. I tested this again and my colleagues were able to consume this data easier. They mentioned that the visual hierarchy was easier to understand now.</p><p>One challenging aspect of this page was creating the error states. It was difficult to anticipate all possible scenarios. This was important because I needed the user to quickly understand the error reason. It’s also important to write copy that doesn’t make the user feel like they made a mistake or that they’re stupid, this could create a poor experience and deter someone from donating.</p><h4>Developer communication</h4><p>We sent these changes to our developer as he was updating the first version of the app. This is when I realized communication is key. There were issues with the visual aspects. our developer used different font sizes in specific areas, changing the visual hierarchy of the information. The spacing was too tight in some places, and some of the components were missing the correct shadows. We set up another meeting with him and explained every detail to make sure he understood the reasoning behind the small details of our design. Once he understood why we designed the app the way we did, he paid closer attention to the details of our design. I think the biggest takeaway from this is that everyone thinks differently. Some details I add to a design may be overlooked if I don’t point it out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*gcbB9eFTm0yJuDa2fip4Eg.png" /><figcaption>Splash Screen and App Icon</figcaption></figure><p>The last thing that the developer needed was a quick splash screen and app icon. The splash screen needs to be a basic design that a user can consume in a second. It’s required to show this screen while the app is launching. I designed a screen that was consistent with our app. It had a gradient that we’ve used across the app as well as the new logo we created. The app icon was very similar. An easily recognizable logo for ETS and a bright gradient background that pops on your home screen.</p><h4>Retrospective</h4><p>It was exciting seeing this app come together from start to finish. This was the first project I was a part of that created an actual product distributed to the public. It was great seeing the transformation of the app from what ETS had, to what we created.</p><p>I was also excited to work on this project because it would make a difference in peoples lives. It still breaks my heart knowing that there are children out there that think suicide is their only option. If my design helps to save one teen’s life — that would my greatest success.</p><p>It was so fun being apart of this process with Every Teen Seen. They are doing something great and I can’t wait to see their progress and how they affect the community around them. You can find this app in the app store go check it out!</p><p><a href="https://itunes.apple.com/us/app/every-teen-seen/id1350070430?mt=8">Link to App Store</a></p><h4><strong>Lessons Learned</strong></h4><p>Make sure you are very thorough when handing a design to a developer. They may miss something that you believe is very important. I found a tool called Zeplin after this project ended. Zeplin allows me to upload my design from Sketch, and a developer can see every detail I made very easily. Checking spacing between elements, font sizing, shadow properties, etc. It’s built specifically to efficiently hand a design off to a developer.</p><p>Communicate often. My developer was very active in our Slack channel. If I had any questions about the company or what he needed he would get back to me very quickly. This helped me design efficiently.</p><p><strong>Thanks for reading! If you like it, clap away! If you want to talk further, connect with me on </strong><a href="https://www.linkedin.com/in/nathan-maus/"><strong>LinkedIn</strong></a><strong> or go visit my portfolio page at </strong><a href="http://nathanmaus.co/"><strong>nathanmaus.co</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe055b13bd6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nathanmaus/every-teen-seen-case-study-fe055b13bd6d">Every Teen Seen | Case Study</a> was originally published in <a href="https://medium.com/nathanmaus">Nathan Maus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gratico Case Study]]></title>
            <link>https://medium.com/nathanmaus/gratico-case-study-bbb6c8345b5?source=rss-cd87fc85f8f0------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbb6c8345b5</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[gratitude]]></category>
            <category><![CDATA[portfolio]]></category>
            <dc:creator><![CDATA[Nathan Maus]]></dc:creator>
            <pubDate>Tue, 27 Mar 2018 22:34:57 GMT</pubDate>
            <atom:updated>2018-04-11T22:39:35.090Z</atom:updated>
            <content:encoded><![CDATA[<h3>Benefits of Gratitude | Case Study</h3><h4>DevMountain Design Challenge</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IzHUq_GAZX9EhOcP5lBl-w.png" /></figure><h4><strong>Introduction</strong></h4><p>During this project my team and I were tasked to research the problem that the majority of people feel unappreciated at work.</p><p><em>How can we build a solution that shows users and businesses the benefits of gratitude in the workplace.</em></p><h4><strong>Business Challenges</strong></h4><p>Initially we had a hard time understanding how me might quantify gratitude. So we did some research to see what solutions were already out there, and what people had to say about their workplace. We noticed a few competitors provide a platform that allows users to transfer money to praise their peers. We made an assumption that most employees want monetary prizes for their hard work. But now it was time to interview a few individuals to test our hypothesis and get some more data.</p><h4><strong>Team</strong></h4><p>Nathan Maus (Me), UX Designer</p><p>April Li, UX Designer</p><p>Ty Maxey, UX Designer</p><h4><strong>Research</strong></h4><p>We wanted to test a few different research methods since this was our first project at DevMountain. Even though some methods were very intimidating.</p><ul><li>I wanted to start out with man-on-the-street interviews. One lady told us that she had quit her previous job because no one ever thanked her for her hard work. This helped us realize that our users needed a way to praise each other.</li><li>Then we created a quick survey that was sent out via LinkedIn and Facebook as well. The biggest thing we noticed from our users, money wasn’t what people wanted most. They wanted a more personal connection with their coworkers, and they wanted to be heard by their bosses and executives.</li></ul><p>This helped us get a grasp on the frustrations that many people run into at work and start building our persona. But I still wanted to here the other side of the story. What were businesses doing to promote and show gratitude in the workplace? Finally, I got 2 interviews scheduled.</p><p>The first interview was with Austin Rynders, an operations manager at a multi-billion dollar research hospital. We learned a lot from the experiences he’s had with his own employees. Two huge factors came out in this interview. One, everyone likes recognition in different ways; this means that no matter what you do it’s going to be hard to please everyone. Next, I asked Austin if there were any initiatives that he tried implementing that completely failed. They had an initiative that involved writing someone’s name on a star and recognizing them for going above and beyond. Then each month a manager would pick a star off the wall and that employee would receive a gift card. This initiative ended because inappropriate comments and jokes were being written instead of appreciation towards other coworkers. This helped us in determining the constraints and methods in which an employee would be able to recognize another coworker. We made it required to tag a coworker so this wouldn’t happen with us. Also because of this, we realized we didn’t want this to become a message board so we restricted the feed to recognition without additional comments.</p><p>The second interview I setup was with the VP of People Operations, Kat Judd, from Lucid Software. The CEO of Lucid Software wrote an article a few months before, about the benefits of gratitude in the workplace. After reading the article I knew I had to talk with someone there. The first thing I noticed when we arrived, was the shelf filled with awards that different employees had received. Kat was a pleasure to speak with and had a lot of insights on how a leading company, like Lucid, treated it’s employees.</p><p>Two things that stood out to me:</p><ul><li>They had an unlimited amount of thank you cards at the front desk that you could use to write someone a quick thank you. Kat mentioned that these were the most memorable gifts she ever received at work. These seemed so genuine to me that we added a way to send a gift card from our store.</li><li>They have a channel on Slack that is dedicated to giving quick shout outs to your fellow coworkers. This stood out to me because at this point we decided that employees would be given a specific amount of points each month to use on other people. But this was a quick way they could recognize someone without dipping into their points.</li></ul><h4><strong>Persona and User Story Map</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sKlPymqX6XwkvdyaM-ZLLw.png" /></figure><p>This is the persona we created from the research conducted by my team</p><p>We compiled our research and created our primary persona, Justin. This helped us understand our users goals and create a design that fit their needs. Justin wanted:</p><ul><li>To open communication between upper management and employees</li><li>To personally recognize coworkers more often</li><li>To connect with his peers on a more personal level</li></ul><p>It was difficult to create a solution that would help our users show genuine appreciation while still remaining organic. Most solutions already out there, seemed more of a novelty. I spoke with someone that said at he used Motivosity, and would trade dollars with his friends instead of appreciating his coworkers.</p><p>We addressed this by staying away from cash rewards because we felt that these weren’t very personal. My team and I brainstormed ideas that could feel personal but were also practical.</p><blockquote>What can someone give you that makes you feel grateful? For Christmas it’s nice to receive an envelope of cash, but you are always more thankful when you get something that you want.</blockquote><p>Because of this brainstorm session and the research we conducted, we created a gifting solution that helps employees give personal gifts to each other for their hard work. These gifts could include company swag, gift cards, and other gear depending on what the business wanted to use for gifts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*44Bi1bhj5glx57n3goP62g.jpeg" /><figcaption>User Story Map</figcaption></figure><p>To keep open communication between upper management and employees we decided to create a Q/A board. Here the user could ask questions of any team, in a public setting, then someone from that team could reply to that question. We had this at Netflix and it was so nice to get an answer about a decision that was made or to just inform another team of an issue. We also created an Awards section, this would allow upper management to showcase employees hard work.</p><p>For Justin to personally connect with and recognize his peers we designed these features:</p><ul><li>Profile page, which is very detailed, allows him to learn more about someone.</li><li>Meetup feature, allows him to tell people that he’s going to grab lunch, coffee, etc and his peers could attend that meetup with him.</li><li>Wishlist, allows him to personalize his gifts and get to know his peers likes and dislikes.</li><li>Points. Justin is given a specific amount of points each month, which he can redeem in the store and send someone a gift.</li><li>High-5 feature, allows him to give someone a quick shoutout in the main feed without using his points.</li><li>Nominations, allows Justin to nominate his coworkers for fun monthly awards.</li></ul><h4><strong>Sketching and Wireframes</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ShpFfY5EFss1qci04oU2mA.png" /></figure><p>Our next step was to start sketching. Our team was great at being open to feedback and making changes to their designs. I chose these designs because they were informative and fun. The different message states look like comment bubbles from users, which creates a fun personal feeling when someone recognizes a peer. I designed the homepage dashboard to have important acts of gratitude front and center, then it shows monthly awards and nominations on the right hand side for everyone to see. I also thought added little icons for different styles of recognition (recognize, high-5, meetup) next to each message on the dashboard so it would be easily identifiable to other users.</p><p>At this point we started creating low fidelity wireframes, but our consistency was lacking across our designs. So, I took the initiative to create a library in Sketch that we could all use to keep our designs consistent. We were now ready for our design review.</p><h4><strong>Design Review and Testing</strong></h4><p>We presented our low-fidelity wireframes to our peers and received great feedback during this design review. Some people were concerned with how users might portray the heart icon as inappropriate. Also they wanted more details on the profile page, such as size or brand of items they’d like.</p><p>With this information we changed it up a little bit. We realized that we had a like button and a love button because that’s what other platforms used. We decided that it wasn’t necessary to have a love (heart) button in this setting because it is a design that will be used strictly at work. As for the profile page, we created an option to setup a wishlist. This way when someone wants to appreciate a coworker they can personalize it with a gift from their wishlist, without having to worry about if they’d like it or what size they needed.</p><p>Once we changed those few considerations we created a task flow to test our users. This helped us gauge if users actually understood how to interact with our design. A few things stood out right away.</p><p>The first task was to ask their marketing team a question. This ended up taking the longest amount of time. Our users had a hard time finding the Q/A board and most ended up at the teams page. The team page only showed the employees in each department and didn’t have a way to ask them a question.</p><ul><li>To address this we changed the label from Q/A to Questions and added an Ask button next to each team name on our Teams page. These two changes made it easy for our users to navigate to the correct page.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ASCpnVksKws2SD25sziyA.png" /><figcaption>Homepage Wireframe with changes annotated</figcaption></figure><p>The last thing they had an issue with was sending anonymous feedback to upper management. We created a feature to allow users to send feedback to HR, they could send it anonymously if they liked. A lot of people thought the feedback option was for the actual web app or they didn’t know who was going to receive their feedback.</p><ul><li>We struggled with how to label this and make it more known to the user. I took a step back and looked at the bigger picture. There wasn’t one instance in our research that someone needed a way to complain about their boss. We realized that we had created an assumption that Justin had an issue talking with his manager, and this feature wasn’t necessary for our users.</li><li>We ended up removing the feedback feature since it didn’t align with our users goals.</li></ul><p>We tested our design after fixing these two issues, we were now ready to dive into the visual design aspect of this project.</p><h4><strong>Visual</strong></h4><p>Our tone for this project was fun and whimsical so our colors and logo had to represent that tone. Our colors kept changing because it just didn’t feel right to me. When we started our color scheme didn’t feel fun and inviting. We wanted people to feel welcomed, happy, and heard. We did some further research to find out what colors may represent these feelings. We finally chose a main color, and 2 accent colors based off this research.</p><ul><li>Blue was chosen for our main color because it represents good communication and trustworthiness.</li><li>Yellow represents cheerful and happy.</li><li>Orange, adventure and creativity.</li></ul><p>After that I applied certain elements of Google’s Material Design. Their approach has been successful with dashboard style designs because it creates a sense of depth to each element. We prototyped the flow of this design with InVision.</p><p><a href="https://invis.io/57GKCLPZH32">https://invis.io/57GKCLPZH32</a></p><p>Once we prototyped the flow we tested users again. Users were happy that the feedback button was removed as it confused them too much. When we added color to the design, users understood the hierarchy and functionality much better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E5mSREoOZf-aO4kSG3N1Aw.png" /><figcaption>Homepage/Dashboard</figcaption></figure><p>Then using Principle, we prototyped the aspect of gifting one of your peers.</p><p><a href="https://youtu.be/Vi8n3ni6P0Q">https://youtu.be/Vi8n3ni6P0Q</a></p><p>Overall, we got great results from our users and I am very happy with our design given the short period of time we had to complete the project.</p><h4><strong>How we Measured Success</strong></h4><p>The way we measured success for this project was by gauging how users interacted and understood our design. Users had an easy understanding of how the design worked and could navigate through the tasks with ease. If this design was implemented, we would measure employee retention over the next year to see if the business’ retained more employees. We would also measure employee engagement to see if people used the product frequently.</p><h4><strong>Lessons Learned</strong></h4><ol><li>One of the biggest lessons I learned from this project is to always make sure you are designing for your users and not yourself. It’s easy to get carried away and convince yourself that your decision is for the user but always test it against your personas.</li><li>Seeing eye to eye can be hard. It’s so important to work together though so you have to look at something from another person’s view. Everyone can add something productive and everyone is working towards the same goal.</li><li>Test, Test, Test! Without testing there is no way to know if your design is going to work. Obviously, I know exactly how the design functions because I built it. But the first time someone sees your design they should be able to use it, and there’s only one way to find out if that’s possible… test it.</li></ol><h4><strong>If I had more time</strong></h4><p>One aspect of the design we didn’t touch on too much was onboarding. Onboarding is a very important aspect, our platform is relatively easy to use but could use some help to understand all functionality. I would take the coach mark approach to our onboarding process. This would allow our users to get right into using the product but would guide them along let them know what specific functions do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/381/1*M2hymI4qgryL8XjkZZ1Dnw.png" /><figcaption>Final Logo Design</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbb6c8345b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nathanmaus/gratico-case-study-bbb6c8345b5">Gratico Case Study</a> was originally published in <a href="https://medium.com/nathanmaus">Nathan Maus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>