<?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 Melissa Ames on Medium]]></title>
        <description><![CDATA[Stories by Melissa Ames on Medium]]></description>
        <link>https://medium.com/@melissaames?source=rss-fe754b674dbf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*xo6zSs6PEhik6fy6.jpg</url>
            <title>Stories by Melissa Ames on Medium</title>
            <link>https://medium.com/@melissaames?source=rss-fe754b674dbf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:35:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@melissaames/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[Noteable]]></title>
            <link>https://medium.com/@melissaames/noteable-66e9199e0fa7?source=rss-fe754b674dbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/66e9199e0fa7</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Melissa Ames]]></dc:creator>
            <pubDate>Sun, 06 Mar 2016 20:28:52 GMT</pubDate>
            <atom:updated>2016-03-06T20:28:52.549Z</atom:updated>
            <content:encoded><![CDATA[<h4>Intro:</h4><p>Looking into an area of opportunity for an existing brand, my team and I landed on a stationary subscription box. Starting with a card sort to narrow down our own interests, we saw overlap in a few areas. Sticking to these areas we pitched our strongest four ideas, and decided to build out Noteable. <strong>Noteable is a stationary subscription service that acts as a sister website to the art supply store, Blick.</strong></p><p>*We jumped into this project originally using Paper Presentation as our brand, but with a last minute pivot we shifted our focus for a better fit.*</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*5eMUYuYEVZOFGekV2VLyOA.png" /><figcaption>Our UX process</figcaption></figure><h4>Research:</h4><p>Our team then began to tackle initial research to see what was already out there. We found our top competitors/comparatives and executed user flows, content blocking, and feature comparison.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*8AiQH-64oN3s-BhFY_TDdw.png" /></figure><p>Looking to compare sites already carrying out an idea close to ours we analyzed tasks flows to see how many steps it would take to achieve a specific task. Specifically we looked at how many steps it takes to join or subscribe and how it works/description. We noted for ease of use we needed to have an accessible subscribe button.</p><p>To have an idea where to start when designing our site, we performed the task of comparative content blocking. Content blocking lays out where everything can be found on the website such as navigation, content, logo, images (carousel), etc. This gave us an idea of how it was working for others and where we should differ. We noted where the calls to action were displayed on specific pages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/502/1*rJhsIuFoQ6ezG-zyS4QW2g.png" /></figure><p>Our feature comparison demonstrated elements incorporated into 3 sites. This allowed us to narrow down our ideas further when deciding what amenities to include.</p><p>Having that information we went on to see who our users would be. We developed a screener and a survey, which provided us with a broad understanding. To weed out anyone who wouldn’t be of use, we added a few questions to act as a screener in addition to our survey. To expand on what we found in the survey, we conducted user interviews.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*5vDva4R5zKo2oga1diHqCA.png" /></figure><p>In our user interviews we delved into questions like</p><blockquote><strong>Tell me about your shopping habits.</strong></blockquote><blockquote><strong>Tell me about your buying habits (stationery)?</strong></blockquote><blockquote><strong>Tell me about the stationary brands that you prefer.</strong></blockquote><blockquote><strong>You indicated you use XYZ subscriptions boxes/services. Can you tell me about them?</strong></blockquote><p>From these interviews we found that people shop out of necessity and out of want. It was common that the individuals wanted to do shopping in store in order to try out a product, and because its more expensive to buy single small items online rather than in store. Individuals tended to shop more out of necessity when it came to stationery. Subscription boxes were very common across those who we interviewed with. We found common themes between individuals that enjoyed getting subscription boxes because they were convenient when busy, enjoyable to open (a gift unveiling experience), and introduction to new products.</p><p>From this we pulled out common themes, using affinity mapping, to come up with user identities that we could base our service around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*WMPByOa8qujkApMyMYKhmA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*fOtf4c9FVUU9sSpw7c4T3Q.png" /></figure><p>Using the MoSCoW method, we came up with elements necessary to incorporate in our site, things we should have, things we could have, and things we wont be including for now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*N4-VHN5AiJZhWhe8RcQvTQ.png" /></figure><h4>Design:</h4><p>Looking at our competitors our team decided our best option was to create a responsive website with breakpoints for web, tablet, and mobile. Based on all the research we had compiled, we began the initial sketching process. Sketching out our personal vision of Noteable, we compared ideas as a group and came up with our mid-fi wireframe scheme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j5-cIny7Jr9HJR3I-NM0Lg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F7E8rCJY67u3ItGx2Bn-EA.png" /></figure><p>We had users test out prototype 1 to see areas of improvement. We heard things like:</p><blockquote>“I would like a success page to see that I’ve successfully subscribed”</blockquote><blockquote>“I want a way to buy items from my previous boxes through my orders”</blockquote><blockquote>“the search bar should part of the global navigation”</blockquote><h4>We iterated based on these comments and came up with our final product which you can click through <a href="https://projects.invisionapp.com/share/UR69VQSWS"><strong>here</strong></a><strong>!</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/481/1*ixknRnIz3fi-AoeEglbxBQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*nRmhZyD99UoY2wq4aw3psg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PpElenEHbuprd5kqfU6-Ig.png" /><figcaption>Home page shown across mobile, tablet, and web</figcaption></figure><h4>Next Steps:</h4><p>Going forward with this project need to:</p><ul><li>Think about incorporating a way to easily repurchase boxes or items.</li><li>Think about the option for gifting.</li><li>Think about adding a rewards program to encourage user return as well as new users. Possibly a point system?</li><li>Think about animating features on our site to bring in a unique touch.</li><li>Continue user testing across mobile, tablet and web; and iterating based on feedback. Forever: <em>user test → iterate → user test → iterate</em></li></ul><p>This project started off a little slow due to the unavoidable sickness that went around, but picked up speed in a serious way toward the end. Thanks to a great team (Anna and Noor)! We communicated well and designated tasks in an effective way, making it all come together in a great way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66e9199e0fa7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hotel Tonight]]></title>
            <link>https://medium.com/@melissaames/hotel-tonight-8e3a0c6955b3?source=rss-fe754b674dbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e3a0c6955b3</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Melissa Ames]]></dc:creator>
            <pubDate>Sun, 21 Feb 2016 16:38:31 GMT</pubDate>
            <atom:updated>2016-02-21T16:38:55.449Z</atom:updated>
            <content:encoded><![CDATA[<h4>Intro</h4><p>Tasked to redesign the Hotel Tonight mobile application in hopes of keeping up with competitors, we focused to create a unique experience that held true to the brand. In order to keep up with the competitors, Hotel Tonight being a last minute hotel booking application needs to focus on increasing the return rate of existing users and likewise increase the rate of new users. In a feedback loop, Hotel Tonight wants to increase the number of rooms being sold which will encourage more hotels to offer rooms and increase the room availability to consumers. In order to help achieve this goal our team went through a process that looked a little like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*Sadok0tUo3AIeRKl1gHUyw.jpeg" /></figure><h4>Research:</h4><p>Having received the area of opportunity we dove into researching how to define and tackle the problems. By developing a initial screener and survey, it helped us familiarize ourselves with the users behaviors. We asked a few basic questions that had to do with how/when/why a user books travel accommodations. We aggregated this information and pulled out a few common themes</p><blockquote>Users most often decided upon a hotel accommodation based on price and location</blockquote><blockquote>Users like to be able to do some sort of research prior to bookings</blockquote><blockquote>Users liked talking to the hotel ahead of time to ensure reliability</blockquote><blockquote>Reading reviews is necessary</blockquote><blockquote>Users like to book or at least start planning in advance</blockquote><p>After gathering this information we went onto comparative and competitive analysis to see what was already out there and why it was doing well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*9fhxOq04Ppu_T30kvGbjoQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*ol2n0-_XS4_eo5OdCRuRHA.png" /></figure><p>From these side by side comparison we found elements that were common and began devising a plan of action. Items that were common across the board included: a sorting feature(to sort by price, location, etc.), collect a list of favorites or wish list hotels, and a calendar feature to compare price trends.</p><h4>Personas &amp; scenarios</h4><p>Using our new found knowledge, we came up with traits that embodied our “typical user” and turned them into two different individuals. In order to keep true to the user as we got further into designing, we tailored this experience to a person(s) who would use the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*WbHll8hhwSM6dA-mGPTXHg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*DJ1sj3DQrtyqXGEIaq6fOw.png" /></figure><p>Scenario: Doug</p><blockquote>Doug wants needs to be able to save hotels to a list so he can book immediately. He also would like to be able to look at the price trends so he knows he is getting a good deal and is staying within his budget.</blockquote><p>Scenario: Piper</p><blockquote>Piper needs to be able to create a wishlist of possible travel accommodations to share with her husband. She also needs a way to directly contact the hotel to confirm pet friendliness so she can bring along her puppy.</blockquote><h4>Prototype 1:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*9Pbh1rKrQgK4DKSZ394ngQ.png" /></figure><p>*Que 5 minutes of some serious scope creep* we each threw our visions of a few specific tasks onto paper and narrowed our ideas. Looking at how to integrate</p><blockquote>sort by feature</blockquote><blockquote>price trends calendar</blockquote><blockquote>previous bookings tab</blockquote><blockquote>tracking(later changed to favorites) tab</blockquote><blockquote>call feature</blockquote><p>We put together our first prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/621/1*CbrTNjmeSme23PyYq8KBlQ.png" /></figure><p>Once we put the screens into InVision to make a clickable prototype, we began rounds of user testing. Overall we found that users were having trouble navigating through the tasks because of unfamiliarity of icons, and lack direction on our part (as we didn’t add hotel names which lead to confusion to where they should be clicking). Readability was also an issue.</p><blockquote>“this (icon) doesn’t make any sense”</blockquote><blockquote>“…not sure where to click for adding to a list”</blockquote><blockquote>“…I don’t know what this is showing me”</blockquote><h4>Prototype 2:</h4><p>Back to the drawing board…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*cnRVU8HApZoC66Yzyd3pUA.png" /></figure><p>Coming back in with a different approach we aimed to revise the areas of confusion. It was clear we needed to change the existing logos in the nav bar, reorganize what remained and what should be added to the nav bar, and added text to be able to differentiate between hotels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*3XoW_AtLQI5zI2IhaIxllg.png" /></figure><p>We then went through another round of user testing, which provided more promising feedback. Users more easily could navigate through the interface. Users picked up on the idea of favoriting a hotel and then having saved into the heart or “favorites” tab. There still were a few things to be improved on: the briefcase in the bottom nav was confused as a calendar, the calendar icon didn’t indicate price trends, and icons and text needs to be increased.</p><h4>Final Prototype:</h4><p>Taking the notes we did a final reworking of our prototype and took it up to a hi-fidelity mockup. We ironed out the last few problem areas. We increased size of icons and text to help with readability and usability. Finally, we broke down the price trends and calendar feature into two different tabs to ensure ease of use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*99fMmZBfiQCr0LM8xAfamQ.png" /><figcaption>Evolution of the calendar through iterations</figcaption></figure><h3>You can click through the final product <a href="https://projects.invisionapp.com/share/XP61CPO65#/screens">here </a>!</h3><h4>Next Steps</h4><p>Going forward with this project would include:</p><blockquote>Talking to developers about the price trends feature to ensure feasibility</blockquote><blockquote>Iterate navigation and icons for usability</blockquote><blockquote>Add a loyalty/rewards program to assist with user return rates</blockquote><blockquote>and to continue to user test → iterate → user test → iterate</blockquote><p>We created a spec doc in give insight to the redesign, all the features and annotations.</p><p>This project overall went step to step pretty seamlessly, which I would attribute to a great team and <strong>tons of communication</strong>. We divided and conquered each task, making sure everyone was on the same page and being given an equal weight of the project. We devised a concrete schedule that helped us navigate and keep everything moving at the pace necessary. It was a great experience working with a design minded team, which made diligently working through the research a task we all learned from. Going forward, making sure the presentation is a well oiled machine is important. We fell a little flat, so reorganization and condensing of material presented is something we will keep in mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*w6HHBvfuKkHukpIMIizJkQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e3a0c6955b3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[S.I. Newhouse School of Public Communications]]></title>
            <link>https://medium.com/@melissaames/s-i-newhouse-school-of-public-communications-de464346e1b0?source=rss-fe754b674dbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/de464346e1b0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Melissa Ames]]></dc:creator>
            <pubDate>Sun, 07 Feb 2016 19:45:47 GMT</pubDate>
            <atom:updated>2016-02-07T19:52:07.761Z</atom:updated>
            <content:encoded><![CDATA[<p>— UX Redesign</p><h4>GA project 2: Appointed the S.I. Newhouse School of Public Communications, I was tasked to do a redesign of the website and start ideation for the mobile site. Based on the persona John, a prospective graduate student, I researched and implemented fixes that would make the site easier for him to navigate when attempting specific tasks. The following will give insight into;</h4><blockquote>Problems &amp; goals</blockquote><blockquote>My process</blockquote><blockquote>Research gathered</blockquote><blockquote>Design iterations</blockquote><blockquote>Synthesis</blockquote><blockquote>The deliverables</blockquote><blockquote>And what will come next</blockquote><h3>Problems &amp; Goals</h3><p>When looking through the Newhouse website, it was cluttered to say the least. It looked as though it had been made without the user in mind, instead it looked like it catered solely to the corporation. Task flows (navigating from page to page) was inconsistent and difficult. <strong>Ultimately, it looked as though the site had been made without content integration in mind.</strong></p><p>To correct these problem areas, I focused on making it easier to navigate through tasks. To have the content of highest priority, according to our given persona, more available. And to condense content.</p><h3>My UX process</h3><p>So, to get to an end product I went through the following steps:</p><blockquote>Research</blockquote><blockquote>Design wireframes for web</blockquote><blockquote>Building of clickable prototype in InVision</blockquote><blockquote>User testing</blockquote><blockquote>Iterations and synthesis</blockquote><blockquote>User testing</blockquote><blockquote>Iterations</blockquote><blockquote>Designing wireframes for mobile</blockquote><h3>The designated persona</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*v1TLemtuWhu6GonFeIbnSw.png" /></figure><p>To get a better understanding of how to redesign, I used John as the persona. John can be known as a 28 year old Father, whom is looking into S.I. Newhouse as a prospective graduate student. He cares to look into the possible faculty, financial aid, and then at application requirements and deadlines.</p><h3>Research</h3><p>Starting with a<strong> competitive analysis</strong>, I compared S.I. Newhouse with similar graduate programs to see how they set up their website. Looking explicitly at task flows, to map out how many actions it took to end on the desired detail page. Below shows the flow for financial aid when compared with Boston University, Columbia, and University of Southern California. This put into perspective that there was clearly better designed flows to arrive at content on competitor sites.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsgzHxDMlCCg-VGr2TMG3Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iQXBSpSq5Qq9o0DneFhlTg.jpeg" /></figure><p><strong>Site Mapping</strong> shows the flow from page to page. The flow made for Newhouse showed how deep content is hidden and how much content is available. This reiterated the idea that items need to be narrowed down and grouped into like categories to cut down on all this content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yEqFPfu4D4IxAWe8oGf3rA.png" /></figure><p><strong>Content inventory</strong> is a index of all the content on a given page. Done for each page, shows how often information is duplicated throughout the site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*0ERwtKO0La_W9Rrmwju1-Q.png" /></figure><p><strong>Card sorting</strong>, which involved me writing out all of the navigation titles and having testers sort them into categories, helped reorganize and condense material. I had a number of people put themselves into the shoes of a prospective graduate students shoes look at extensive list of navigation links and order them by priority. Once they had laid out the navigation links I had them sort the hover navigation items into the header that they felt fit. Lastly, I had them flip over any items they felt didn’t need to be in the global navigation and group anything they thought fit under the same title. The users conveyed that there was an unnecessary amount of navigation and items could be cut down through grouping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*iIGmM2E8pHzXtaO4PkI-Zw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MYaMZKBU9as9kBzTZc4lpA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*3onvBbgeT2VsXIjYM8VS9g.jpeg" /></figure><p>Once I had tester feedback, I started on the initial mockup. This basic model displayed content blocks and a condensed global navigation. I added in features making it a more hi-fidelity mockup, made it a clickable prototype in InVision and then went forward with user testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6TYKLumfLyvOt62RI7S-0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JIivpFAYQv6p8qE7NUUIVA.png" /></figure><p><strong>User testing </strong>was valuable in showing how the user interacted with the given interface. I prefaced the user telling them the persona they should emulate when routing through the site. I then gave them the three tasks they would attempt to complete. Going through design 1 users frequently said things like</p><blockquote>“I didn’t immediately see the apply button in the righthand corner”</blockquote><blockquote>“I’m having difficulty finding items in the hover navigation”</blockquote><p>After listening to the feedback given, I went back to designing and came up with iteration number 2 (as seen below). This time I not only added color to the upper right buttons, so they became more effective calls to action, I added an apply link under admissions in the hover navigation. I also added dividers into the hover navigation to show that the links directly corresponded to their title above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YYzKSMxN5WyVbhkgVvk8kA.png" /></figure><p>You can click through my complete redesigned prototype <a href="https://invis.io/YK5X3KFEG"><strong>here</strong></a><strong>. </strong>As a reminder you are navigating through the pages as John, a prospective graduate student, looking into financial aid, faculty, and application details.</p><p>All of this research lead me to some final conclusions:</p><h4>Using card sorting it was clear that there were too many options for navigation, overall it was too cluttered</h4><h4>Content inventory again showed the high level of content</h4><h4>Site mapping displayed both the number of pages that the user would have to go through to get to a destination and the non-intuitive flow from page to page</h4><h4><strong>User testing provided the most valuable results</strong></h4><h4><strong>Users want don’t want to have to dig for information</strong></h4><h4><strong>Keeping it minimal is more effective</strong></h4><h3>Mobile wireframes</h3><p>Based on what I had designed for web, I did a quick design for mobile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*1o0gVg76Y6eR4XPGiNGBlw.png" /></figure><p>This displays the same content but in a more mobile friendly way through features like a hamburger navigation, to keep the landing page clean.</p><h3>Next steps:</h3><blockquote>Keeping adding in content on the web wireframes</blockquote><blockquote>Make mobile prototype clickable in InVision</blockquote><blockquote>Do user testing with the mobile prototype</blockquote><blockquote>And continue iterating the mobile wireframes based on user feedback</blockquote><h3><strong>Final Thoughts:</strong></h3><p>It was exciting getting to do what felt like a real redesign by applying all our new tools we had learned. The idea that it was client facing, took it one step further in feeling like the real thing. I definitely learned that it’s important to hold onto all the pieces of the design process to reference throughout the process. And while I may have thought some things were a good idea, it’s always more important to listen to the feedback users are giving.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de464346e1b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jive ♫]]></title>
            <link>https://medium.com/@melissaames/jive-76251e913f7b?source=rss-fe754b674dbf------2</link>
            <guid isPermaLink="false">https://medium.com/p/76251e913f7b</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Melissa Ames]]></dc:creator>
            <pubDate>Sun, 24 Jan 2016 19:27:44 GMT</pubDate>
            <atom:updated>2016-02-07T16:18:58.526Z</atom:updated>
            <content:encoded><![CDATA[<p>With a exceptionally fast paced few days, we have wrapped up week 1. Covering everything from becoming familiar with what a User Experience designer is and how that translates into work to making paper prototypes. With GA, this week we learned how to actively assess and use our UX design chops. Day 2 we were given our first project, we were prompted to design the concept for an app. Breaking us into three sections, a category was assigned to each of us and I was given media player. This post will walk you through my step by step process on how I got the idea for my app, Jive.</p><h4>Research</h4><p>In order to appeal to the user we conducted interviews asking our peers their app usage. Going in with a list of 6 broad questions, I began to mentally narrow down my questions after seeing trends in the answers. I asked my interviewees about their most frequented music apps, when they were using them, if they shared music with others, and what they wanted out of a music player.</p><p>As someone who is a big music nerd, I came in with expectations. The more people I asked the more I realized each persons views differed from my own. One of the most frequently stated words were</p><blockquote>“I like sharing music but not publicly”</blockquote><p>Seeing a pattern I moved onto my next step of research, affinity mapping. Writing down everything from my interviews down onto sticky notes I categorized my finds into</p><blockquote>context</blockquote><blockquote>behaviors</blockquote><blockquote>pleasures</blockquote><blockquote>pains</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T2HNyEROtjDG5ImaPVHO8g.jpeg" /></figure><p>As the sticky notes formed stacks, this illustrated clear patterns. Themes like people using Spotify and/or Pandora (although not for sharing), people liked sharing music but would rather do so directly with an individual, and having access to precreated playlists or being able to make their own. This process helped me come up with my problem statement:</p><blockquote><strong>I need to be able to listen and share music within one application</strong></blockquote><h4>Sketching</h4><p>Once we had figured out our problem statements we moved onto learning how to create lo-fidelity and high-fidelity mockups. We designed our first “draft” or initial mockup of our app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N4HS8NB1t-_9GXb0ehNdJQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ySe8qzerUyfADRugxwMFig.jpeg" /></figure><p>I came up with the idea to share music within an music app. Selecting the individual you want to receive the given song, and they would be able to hear a quick preview of the song. The user could go to their own playlists or go to the browse page that has pre-created playlists and upon listening to a song that they wanted to share, they would click over to their friends list and send it directly to the person(s) selected. Clearly, there were many iterations to be done. I received great feedback that helped me go into and pick apart what could stay and what needed improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N2Q8lKP2k0j7o0EfqE0eCw.jpeg" /></figure><h4>Prototyping/User Testing</h4><p>Next step was conducting user testing. In order to view how the user would interact with the product, we used a prototyping app called POP. I went into my first user test prematurely, which lead me to go back and develop a spiel and add more interactions. Going in my prepared to my following tests, I got some valuable responses. (Side note: it was interesting to realize that things that I assumed were obvious were not because my users were not involved in the design process). The majority of my users gave me feedback on</p><blockquote>the flow: difficulty navigating back to the home screen</blockquote><blockquote>needing color so they could visualize more clearly what tab they were on</blockquote><blockquote>inbox needed some sort of notification to grab user attention</blockquote><blockquote>wanting a way to save songs into a specific playlists</blockquote><blockquote>adding playlists for the user who sent the song/playlist</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iw8gydAYS2Bm7mJsEjVw2w.jpeg" /></figure><p>I went in and tweaked; how the preview of a song looked when a user was sent something so that they would save it, ways to navigate back to the landing page, color to indicate tab differentiation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*XOA6Hx40kTMGNOV2tkDjlA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/1*AaavBrQOQnOlk3sfoiofdg.png" /></figure><p>Scenario: Max is listening to a song he thinks Jane might like. He wants to send it directly to her to avoid public sharing. He also doesn’t want to deal with the fuss of going through multiple platforms in order to share the song.</p><p>Flow: Julie sees that Max has sent her a song; She goes into Jive, where she is lands in the browse page, and clicks<strong> INBOX &gt;</strong>Which takes her to her list of unopened and opened songs that she has received. She then opens the song sent from Max by clicking on the <strong>ENVELOPE(or his name) &gt; </strong>this will take her to a 30 second preview of the song, which she likes and wants to save so she can listen to it again at some point. She clicks the <strong>PLUS SIGN &gt;</strong> which outlines that the song will be saved to a playlist called “Max”. She can then go into her playlists and listen to the song again and share it with anyone is she wants.</p><blockquote>You can check out my interactive prototype <a href="https://popapp.in/w/projects/%20%2056a1222d6e09381a42f55933/preview">here</a></blockquote><h4>Overview</h4><p>This last week was a whirlwind, but in the best way possible. I feel like I really learned a lot and grasped the information. I’m excited to get to apply my new skills to our following projects!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76251e913f7b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>