<?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 Nicole Young on Medium]]></title>
        <description><![CDATA[Stories by Nicole Young on Medium]]></description>
        <link>https://medium.com/@nicoleyoung?source=rss-2a127319b33c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Hi3bWMZZtmSwrAuc.jpg</url>
            <title>Stories by Nicole Young on Medium</title>
            <link>https://medium.com/@nicoleyoung?source=rss-2a127319b33c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:52:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nicoleyoung/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[Green Hopping]]></title>
            <link>https://medium.com/@nicoleyoung/green-hopping-f1763e1bc88e?source=rss-2a127319b33c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1763e1bc88e</guid>
            <dc:creator><![CDATA[Nicole Young]]></dc:creator>
            <pubDate>Fri, 30 Oct 2015 04:00:46 GMT</pubDate>
            <atom:updated>2015-11-02T20:29:30.768Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p-ga3HknqqIb-01z4Q85UQ.png" /></figure><h4><strong>Building up a product into its larger and more impactful mission; make lives healthier!</strong></h4><h4>Opportunity</h4><p>Green Hopping strives to motivate consumers to think twice about what they eat and to encourage them to reject packaged or processed food. Their mission is to <strong>inspire lifestyle changes by facilitating access to healthy food </strong>and by <strong>educating consumers about the beneficial effects of eating a plant-­based diet</strong>. Their goal is to create <strong>change via technology</strong>, by introducing a more ‘natural’ lifestyle in a way that’s accessible and applicable to today’s consumer habits via a mobile food locator and delivery platform.</p><h4>Challenge</h4><p>After building on top of the pre-existing research and conducting our own, we knew our challenge was to <strong>re-design the current app, optimize its search functionality, implement a purchase and delivery flow, as well as introduce a social component</strong> to the app to encourage users to create a community surrounding their shared lifestyle.</p><h4>Process</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5vgpUVbJmmGKeP-vDkTsig.png" /></figure><p>Our CEO had already determined market fit and target demographic by conducting her own extensive research, so my first challenge was learning how to enter the research process <strong><em>in media res </em></strong>for the first time. How do I shape my own research process when some of it has already been done? <strong>Where do I jump in? </strong>Very quickly, I learned the value of flexibility and the importance of keeping your big questions in mind at every stage of the UX process.</p><h3>Discover</h3><p>Her research had asked, “<strong>How do we inspire people to live healthier lives?</strong>” and found that this was most effectively done by <strong>making healthy food choices more accessible</strong>. She then answered the who and the what (health-conscious females and a Google-Maps-for-healthy-food app, respectively). It was up to us to answer this question:</p><blockquote>How can we help them make the best decisions, <strong>once</strong> they’ve already accessed this app?</blockquote><p>To confidently defend those designs down the road, I still had to conduct my own research <strong>to become an expert myself</strong>. Now, full disclaimer. <em>I am a healthy human being who loves to work out, but I am also what you may call, a glutton</em>. I grew up in a family of professional chefs. I was taught at a young age to eat first. Then, and only then, could I ask which unmentionable organ from what exotic animal I had just (in)voluntarily taken into my unassuming body. It was time to leave the dark side and get my veggie on.</p><h4><strong>C</strong>ontextual Inquiries</h4><p>To get a feel for the average customer who identifies with this plant-based lifestyle, I started juice bar-hopping. I saw people hobbling in after what must’ve been a heavy night before, women of all ages walking in with yoga mats, and some very athletic couples who probably consider it romantic to run marathons together.</p><p>I kept up this healthy habit over the duration of this project, juicing at least once a day. Being able to interview customers on the spot was incredibly helpful to <strong>put their answers in real-life context of this larger phenomenon</strong>.</p><h4>Usability and Heuristics</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NGSLH0bXDL8mwzdWnTgNow.png" /><figcaption>The full capacity of Green Hopping’s current app functionality before we UX’d the crap out of it.</figcaption></figure><p><strong>Taking a look at the current app through a lens of usability and heuristics highlighted some notable issues.</strong></p><ul><li><strong>There wasn’t any search functionality.</strong> To view all the options in my area, I’d have to click through into my state, borough, then neighborhood.</li><li><strong>Map view was just 1/2 of my screen</strong> with no option to expand making it hard for me to understand or navigate just exactly where I was looking.</li><li>There was an icon legend, but a lot of <strong>these icons appeared to be redundant</strong> and would pop up <strong>covering the content</strong> I was looking at. Additionally, as a plant-based n00b, I knew I would have trouble remembering what each icon meant.</li><li>Map view on the restaurant page, for when I wanted to navigate to a place I had finally picked, appeared to be <strong>about 100–150px </strong>(eyeballed) high, making it <strong>difficult to navigate.</strong></li><li>Tapping on the heart icon <strong>didn’t appear to do anything</strong> except fill in the heart. I would later be <strong>unable to find the place</strong> that I had assumedly saved.</li><li>I <strong>couldn’t scroll</strong> down on any of the pages. Everything that happened on the app took place within the 667px.</li></ul><h4>Iconography</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*2eWtAuDTud0Jdn6EBGktPQ.png" /><figcaption>Iconography usability tests with all vegan users.</figcaption></figure><p>Knowing that most of the app’s information about healthy food eateries was going to be sourced from either UGC or a third party API like Yelp, I first tackled the one piece of original Green Hopping content: the iconography.</p><p><strong>Three quick usability tests validated the need to redesign the icon legend.</strong> I sought out users who ascribed to this lifestyle, as they‘d be authorities on understanding any iconography pertaining to this healthy universe.</p><h4>Competition</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/273/1*1DOdgpnQxeB5FdNaTLVp6g.png" /></figure><p>Competitors were identified based on the different spaces Green Hopping operates in: food, local search, lifestyle, and delivery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7iOhLhn8iTw_b31uzR5scA.png" /></figure><p>By focusing on <strong>feature analysis, comparative flows, and design style inspiration</strong>, it was clear that Green Hopping had a lot of potential to uncap. But to make sure that we weren’t designing just for the thrill of seeing how far we could take the app, it was time to <strong>get back to the user</strong>.</p><h4>Surveys &amp; Interviews</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qjSKLhhkobeXFBnwIGMyyw.png" /></figure><p>Setting up a screener survey not only helped in identifying which power users to interview later, but it also provided us with a good understanding of a users’s <strong>motivation</strong> to eat healthy. Usually it was because of <strong>general understanding and knowledge that being healthy was inherently a good way to live life</strong>, but some users expressed being motivated by <strong>taste</strong>, <strong>athletic demands</strong>, or <strong>aesthetic reasons such as wanting to be bikini ready</strong> for their upcoming vacations.</p><p>Moving beyond a user’s motivations, interviews shed a light on specific habits and behaviors.</p><blockquote>Having previously answered the <em>why</em>, knowing the <em>how</em> and the <em>what </em>helped inform our designs.</blockquote><p>Users told us <strong>what context</strong> they wanted to pursue healthy food options, <strong>what tools and information they used</strong> to inform their purchase decisions, and <strong>what deterred them</strong> from following through with their goal. One thing to note, was that <strong>we also interviewed users who less regularly opted for a healthy option</strong>. As a business goal, Green Hopping wanted to help more people choose a healthier lifestyle, <strong>not just provide this lifestyle for those who already subscribed to it</strong>. For all users, it was important to define what these habits were and include them in our designs to elevate Green Hopping into a more useful and impactful app.</p><h3>Define</h3><h4>Personas</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*C0DtpIBJH_l4Q0awu2JJrQ.png" /></figure><h4>Features</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*kbyTcA0mSkIwBPtl5nyawA.png" /></figure><p>After conducting our own user and competitor research, we found that there was a need to go beyond search results and <strong>make that information more useful and dynamic</strong>. Users also approached the app with an <strong>end goal of a purchase</strong>. We knew we wanted to <strong>help our users make smarter next-step decisions</strong> with their results, and wanted <strong>convenience in their ultimate end goal</strong>. Lastly, our users expressed a <strong>desire to learn more and stay connected</strong> with new recipes, meals, and restaurants. As we were working with a niche market and <strong>lifestyle app</strong>, we wanted to serve this need by bolstering Green Hopping’s <strong>community aspect</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*mlyOvwHEEc9rpSVkyGTKuw.png" /></figure><h3>Develop</h3><h4>Search</h4><p>As a result, we optimized the current search experience to include a <strong>flow that allowed a user to filter</strong> based on their dietary needs, as well as rating, and price range. We optimized those search results by <strong>increasing the map window</strong> size from half-screen to full-screen (and also introduced a <strong>list view</strong>). Moving beyond the search results, we displayed a <strong>restaurant’s rating and reviews</strong> prominently on the restaurant page, as our users told us this was what they trusted when making purchase decisions.</p><h4>Delivery</h4><p>To address how users usually arrived on the app because they eventually wanted to purchase a juice or a meal, we coordinated with the app’s developers to implement the Yelp API which would source restaurant information <strong>as well as the menu</strong>. Then, using the Stripe API, users would be able to <strong>purchase items</strong> from the menu page and <strong>have it delivered</strong> to them via the Postmates API. Our interface design decisions always <strong>deferred to content, and the goal of the user</strong>.</p><h3>Deliver</h3><h4>iOS v Android</h4><p>The final designs included separate wireframes for both iOS and Android. Why? Turns out, app download numbers were almost split evenly between iOS downloads and Android downloads. The app had also recently launched across multiple cities nationally. Based on these two facts, it was important to not alienate either demographic and design natively for both operating systems.</p><h4>Scenario</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*BDQOK95lggAiFW4tNEP3OA.png" /></figure><h4>Our Solution</h4><p>Had we continued onward in our design process using just the stakeholder research, we would’ve built an app that looks good, but doesn’t have much going on behind it. It would have only displayed search results for the user, and perhaps a way for them to save places. Instead, we capitalized on the research that had already been done and built on top of that, allowing us to delve much deeper into a user’s needs while still designing for Green Hopping’s broader brand mission.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1763e1bc88e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Heroes to Superheroes]]></title>
            <link>https://medium.com/@nicoleyoung/from-heroes-to-superheroes-d82e160b39d0?source=rss-2a127319b33c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d82e160b39d0</guid>
            <dc:creator><![CDATA[Nicole Young]]></dc:creator>
            <pubDate>Fri, 16 Oct 2015 15:39:11 GMT</pubDate>
            <atom:updated>2015-10-21T03:21:40.987Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1CBAvkK4_s7Wo5NezjEeCA.png" /></figure><h4>Designing for disabilities by marrying GoPro with Google Cardboard.</h4><h3>The Problem</h3><h4><strong>One billion people </strong>in the world have a <strong>disability </strong>that <strong>limits </strong>their<strong> movement </strong>and<strong> capabilities</strong>. Because of these limitations, many disabled people are <strong>unable to experience</strong> the <strong>thrills</strong> and <strong>joys</strong> of <strong>outdoor adventures or extreme sports</strong>.</h4><h3>The Opportunity</h3><h4>GoPro and Virtual Reality</h4><p>GoPro’s motto is “Be a Hero”, with intentions to inspire others into action. They believe in passionately <strong>pursuing what’s possible in this world by capturing, sharing, and celebrating memorable moments together</strong>. As CEO Nick Woodman says, “The sharing of our collective experiences makes our lives more fun.” GoPro has recently partnered with Google Cardboard to be the main manufacturer of JUMP, a 16-piece 360 Virtual Reality camera that will help propel virtual reality into users’ everyday lives. Between GoPro’s brand personality and virtual reality partnerships, GoPro is perfectly positioned to create alternative experiences for users with disabilities in innovative ways.</p><h4>Google Cardboard</h4><p>Google Cardboard is a $5 headset made out of foldable cardboard, allowing people to <strong>experiment with VR in an easy and inexpensive way</strong>. In the context of people with disabilities, having an accessible, cheap, and enhanced way of seeing the world allows these disabled users to break the barriers of their limitations.</p><h3>The Process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YchwWhZEu0vGwDqVMgG2Aw.png" /></figure><h3>Discovery &amp; Research</h3><ul><li>Screening Surveys</li><li>Contextual Inquiries</li><li>User Interviews</li><li>Comparative &amp; Technical Research</li></ul><h4>Screening Surveys</h4><p><strong>To effectively design for disabilities, we had to spend time with those disabilities and target our research to those who were living with a mental or physical condition. </strong>Our first step was to research how to talk about disability in a way that wasn’t insensitive or offensive. We crafted a screener survey to find users who had a disability that affected them daily, and had some interest in outdoor physical activities. We reached out to our own personal networks, as well as contacted many organizations and pushed our survey out there. We screened 63 participants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8YGjxtoON7BpZYS-ylwe8w.png" /><figcaption>Based on the questions we asked in our survey, it was clear that many of our users were limited in their everyday movements, but expressed desire to move beyond that.</figcaption></figure><h4>Contextual Inquiries</h4><p>For a broad understanding of the day-to-day challenges and adjustments disabled people need to make, we conducted multiple contextual inquiries. We repeatedly visited the <a href="http://www.cidny.org/">Center for Independence of the Disabled</a>, and also went to Central Park where we watched an <a href="https://www.youtube.com/watch?v=la52e690q48">adaptive baseball tournament</a> for the partially blind. In both instances, we spoke with disabled participants as well as leaders of each respective organization, and were put in contact with more leads. It was also helpful to see how someone with a disability has to make adjustments that I wouldn’t have thought about, had I not seen it firsthand. As a group, my peers and I were beginning to get more comfortable with the complex landscape our users were coming from.</p><h4>User Interviews</h4><p>Our screener and contextual inquiries led us to 9 user interviews, both in person and conference call. We wanted to be authentic to their needs and avoid making assumptions down the road, so we asked questions about the <strong>specifics of their disability, and the context surrounding it</strong>. What was it? What did it mean for them on a daily basis? How and when did it begin? What tools do they use? What adjustments have they made? What was their support system like? We aimed to <strong>understand their history, current state, and hopes for the future</strong>. Their disabilities ranged from hearing loss, partial blindness, late stage muscular dystrophy, paralysis, and celiac disease.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p8AevMqwYGNfG_TG1AhQOQ.jpeg" /><figcaption>Speaking to a user in Holland about his muscular dystrophy and how it affected him.</figcaption></figure><p>Our main finding was that<strong> every person and every disability is a unique story</strong>. Two people who may have the same condition will have entirely opposite experiences. We also were surprised to hear every interview touch on the <strong>subject of normalcy</strong>. Some people had accepted their conditions embedded into their lives as a <strong>“new normal”</strong>. Some sought to return to their <strong>“old normal”</strong>. There was even a lot of gray area in between. <strong>Attitudes about their futures typically depended on the significance of the disability and the context of their support system or adaptive technology.</strong></p><h4>Comparative &amp; Technical Research</h4><p>We then looked at <strong>three categories</strong> of competitors based on the different industries our project was immersed in: <strong>Virtual Reality, Media Channels, and Disabled Services.</strong></p><p>As we compared other companies experimenting with and/or selling VR as an everyman’s experience, we knew our <strong>challenge</strong> was twofold. First, we’d have to get creative about <strong>how to assemble a VR video prototype</strong>. Second, we’d have to learn about <strong>designing within an augmented interface</strong> without having fully defined industry guidelines. We compared large photojournalism and media companies to see how they pushed visual content through various digital channels, and our biggest takeaway was to <strong>always defer UI to content</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m93XTwkHxo_4dOVq5daYrQ.png" /><figcaption>User flow indicating how assistive technology took twice as long to accomplish tasks.</figcaption></figure><p>We had to pay close attention to what our users needed and how they already used their devices. <strong>User flows</strong> were helpful because they showed that <strong>when a user enables assistive technology on their phone or their computer, it takes them twice as long to accomplish a task</strong> due to the extra assistive steps.</p><h3>Synthesis &amp; Ideation</h3><ul><li>Affinity Mapping</li><li>Persona Creation</li><li>Feature Ideation &amp; Prioritization</li></ul><h4>Affinity Mapping</h4><p>As always, to find trends and shared user sentiments from our research, we put everything up on a wall. <strong>It didn’t work. </strong>Huh? This was the first time affinity mapping, tried and true as a the crux of all helpful UX practices, failed me. Our users were <em>so</em> complex, <em>so</em> nuanced, <em>so</em> unique… it was terrifying to think that we had come this far and couldn’t find our next step. Especially after a few emotional interviews. It was time for a long lunch break.</p><p>Upon my group’s return, I realized that <strong>our failure was partly because we were making assumptions</strong> and looking for specific trends. I tried to <strong>map out each user’s story</strong> on the wall, <strong>chronologically</strong>. What was their life like before? What was their history with outdoor sports? With sickness and disability? Where was their disability first introduced into their lives? What happened next? Then after? What about after that?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*xBtw3NFaLln5Svvgwbc98A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7R0FCa6uA2FHv8jBFRikYw.jpeg" /><figcaption>Each user presented in their own columns.</figcaption></figure><p>Voila. <strong>Now we could see trends by grouping users together who had a similar historical context (before their disability), similar recovery/treatment methods, as well as similarities in their disability’s intrusiveness. </strong>They all spoke on different ideas about what “normal” meant to them.</p><h4>Persona Creation</h4><p>As our affinity map now shined a light on this <strong>concept of normalcy</strong>, it was important to see our users through this light. We created a persona for each attitude towards normalcy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kGWUB_ldDyGkVUjJVIv6GQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RsZr1SKiE25z878L_NejXw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8BdJFexLn2eQA2Lx8BLzFg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qsadnCICICCNOwJE_-no1Q.png" /></figure><h4>Feature Ideation &amp; Prioritization</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*rzTcmGEqQIDm5ka-MLMxGA.png" /></figure><blockquote>Our users relied heavily on a support system to assist or beat their limitations.</blockquote><p>We needed to incorporate a <strong>social aspect</strong>, and avoid the possibility of our users being entirely isolated within the VR experience. Strong support systems motivate those with disabilities to integrate into communities and beat their physical or psychological walls.</p><blockquote>Our users weren’t looking for a solution.</blockquote><p>We weren’t here to cure their ailments. Our experience should be <strong>delightful</strong> and <strong>defer to its content</strong>. We were going to keep things really simple and avoid any flashiness, unnecessary features that would slow a user down, and focus on our information hierarchy.</p><blockquote>Accessibility settings exist in a device’s hardware.</blockquote><p>We would build a settings panel when a user was in VR mode, as well as design the rest of the app based on current accessibility standards. This way, our user could avoid having to go into the settings and re-adjust.</p><h3>Prototyping &amp; Testing</h3><h4>Low Fidelity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*gR4zBMAtglgW2desdbVYKg.png" /><figcaption>Results from our design studio sessions.</figcaption></figure><p><strong>Prototype:</strong> To arrange the layout of our features synthesized from our research and prioritized via the MoSCoW method, we did a series of <strong>design studios</strong> (5 minute sketching) on pen and paper, and <strong>dot voted</strong> to find the best layout of all our options. A single module layout affirmed our decision to defer to content, which would be our VR videos.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djRhTXe9RbLyGuU72Orf6Q.png" /><figcaption>Our paper prototype.</figcaption></figure><p><strong>Testing: </strong>A quick validation of our sketches showed that we should keep our single module layout. We learned from our three usability tests, that we needed to get rid of on-boarding. It was an unnecessary feature and our users should only be given information or asked to do something when it was necessary. Again, defer to content!</p><h4>Medium Fidelity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*x0L_pZWSnLzQppvQRyIs2g.png" /><figcaption>Each designer’s interpretation of the home screen.</figcaption></figure><p><strong>Prototype:</strong> We translated our paper sketches into a Sketch wireframe. Having decided on our main layout as a group, we individually went home and finished designing the rest of our interstitial pages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/317/1*0YlT5tlZNmWkwsxOYhiWKQ.png" /></figure><p><strong>Testing: </strong>No surprise, each designer was partial to their own designs so we conducted more usability tests with impartial users. We initially decided on a top navigation bar, thinking our users would accidentally tap on a different page much less. Upon further research into Google’s Material Design documents and Apple’s Human Interface Guidelines, we were wrong! We built a friendly reminder of design guidelines to refer to.</p><h4>High Fidelity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CR4rqB3lic4eiktH41o6AQ.png" /><figcaption>The evolution of our home screen as it shed away the unnecessary design aspects.</figcaption></figure><p><strong>Prototype: </strong>We incorporated our new bottom navigation, side entry sign-in trigger, and built a VR video (including dynamic setting activation based on the direction the user was facing) for the full prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eT-48c_bIR8cyM_k9Q-nRg.png" /></figure><p><strong>Testing: </strong>After usability testing with 6 more subjects, we were ready to present our final prototype! All users were able to search for a specific video, save it to their Favorites, find the video again, play it successfully in VR mode, navigate within the VR settings, and enjoy their experience!</p><h3>Wrapping Up</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/811/1*mo9mm5gpmJATzrKs8cI0yg.png" /></figure><h4>Our Solution</h4><p>We wanted to incorporate a <strong>social feature</strong> to this app. In our final design, <strong>users can see how many people are currently viewing each video</strong>, allowing users to select videos that are popular. We wanted to track only live views, to make our users feel as if they were experiencing the VR experience together with other people.</p><p>In regards to our focus on <strong>accessibility settings and designing for disabilities</strong>, our current app is very simple and intuitive because we made a point to <strong>defer to content</strong> with every design decision we made. <a href="https://www.youtube.com/watch?v=Zp55CawMNLk&amp;feature=youtu.be">When a user is in VR mode</a>, they are able to look down at their feet to activate the settings panel, and then face the direction that they want to ‘click’. Users can click by using the click button on the Cardboard headset.</p><p>We also wanted our app to be <strong>delightful as opposed to offering a solution</strong>. In order to avoid offending anybody by offering a ‘fix’, we also <strong>tested our app with able-bodied users</strong> who didn’t have any disabilities. They also expressed joy, delight and in innate curiosity and interest in VR, indicating that we had accomplished our goals.</p><h4>Scenario</h4><p>Mitch is attracted to nature and loves learning about the wilderness. His condition has slowly worsened each year, which limits his ability to go outdoors safely. As a result, he loves spending time online to experience what he can’t experience offline.</p><h4>Next Steps</h4><p>We would have liked to test and <strong>build more of the app’s social functionality</strong>. Was there a use case for this product in rehabilitation programs? As a group activity? It would have been interesting to bring this product to some of the organizations we had been speaking to, to see their reaction.</p><p>Given that our prototype was a contained example of what settings would look like within VR functionality, <strong>we were unable to test and see if the head nod/tilt was enough to activate those settings</strong>. On this note, it would have been helpful to even<strong> speak with other app developers and designers who had experience with designing VR</strong>. It’ll be exciting to see what industry standard guidelines are in the next 5 years.</p><h4>Last Words</h4><p>I had fun with this process. There were a lot of questions, a lot of learned lessons, and only a <em>little bit of foul language</em>. Despite the tug-of-war of our struggles and accomplishments, one idea remained permanently inked in our brains: these were <strong>real</strong> <strong>people</strong> with <strong>real disabilities</strong> that affected them. I was proud to walk away from this project, knowing that I was capable of contributing.</p><blockquote><a href="http://invis.io/YB3NUOTG6">See our prototype here!</a></blockquote><blockquote><a href="https://drive.google.com/file/d/0B_BN_CLMGraTUEVQcEF1MDYxWmc/view?usp=sharing">And our deck.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d82e160b39d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Dinosaur Named Abe]]></title>
            <link>https://medium.com/@nicoleyoung/the-opportunity-c79bcf41bc2c?source=rss-2a127319b33c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c79bcf41bc2c</guid>
            <dc:creator><![CDATA[Nicole Young]]></dc:creator>
            <pubDate>Mon, 13 Jul 2015 03:58:38 GMT</pubDate>
            <atom:updated>2015-10-21T03:20:45.440Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VUkxVjJdwkUEnlYMBzr-sw.png" /></figure><h4>A 2-week project adding a new group-story feature to Timehop.</h4><h2>The Opportunity</h2><h4>Timehop <strong>wants to </strong>broaden its customer base through a new <strong>group storytelling feature</strong>. This feature expands access to friends who share a memorable experience, and allows them to collaborate together.</h4><h2>The Process</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*yT-Ye9vZp95_PP5lYzB8Gg.png" /></figure><h2>Discovery &amp; Research</h2><ul><li>Comparative and Competitive Research</li><li>Screening Surveys</li><li>User Interviews</li></ul><h4>Comparative and Competitive Research</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/608/1*dVkEmrMZBhF8ydK9Hw3ZKA.png" /></figure><p>Our first step was to understand the business space Timehop occupied. Because Timehop is very much a novelty and niche app, we had to broaden our definition of who its competitors would be. We defined what metrics we’d use to identify our competitors, given the common themes Timehop had in the app industry. We then defined the metrics we’d use to compare them to each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*WLM6HL77Wv3LTR906WeVBQ.png" /></figure><p>After applying a set of Abby IA’s <a href="https://docs.google.com/spreadsheets/d/1zxF6QFSYF3KY-EW4-w644GGBVDGLWVwsxxntgoUxmLg/edit?usp=sharing">heuristic analysis to these competitors</a> and drawing out <strong>user flows for all ten competitors</strong>, we found some main findings that we wanted to keep in mind while building our product.</p><p>— <strong>Users put more effort into creating their content when the content has a longer lifespan</strong>. For example, compare Instagram to Snapchat.</p><p>— <strong>Apps organize content based by tags</strong> (profile tags, geotags and hashtags).</p><h4>Screening Surveys</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*8u9mnVqtItS8BJ1fda8APw.png" /></figure><p>Once we had an understanding of how Timehop fit within the mobile, social, and content-creation sphere, we moved on from business goals to user goals. Our competitor research focused on companies that were inherently social and sharing in nature, so we used that as our first stepping block to build screener surveys. <strong>We </strong><a href="https://docs.google.com/forms/d/16u2kXVwjX3fjfKPby7bGK3VtboPxyd8V6Je59L7BfeE/viewform?usp=send_form"><strong>asked questions</strong></a><strong> about user’s social media habits, how they engage, and how they documented or shared memories on social platforms.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*ihCpCMhuf5kqWdCfL7QATQ.png" /></figure><p>Our <strong>findings</strong> are as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SE6j5WXNdpiCRLRq." /><figcaption>My group members looking over the first survey in action!</figcaption></figure><p>— <strong>The majority of participants all used Facebook, Instagram, and Snapchat most</strong>, usually on a daily basis.</p><p>— Users <strong>check their social accounts daily, but post sparingly</strong>.</p><p>We asked survey participants to leave their information if they so chose, so we could interview them further and find out more about their motivations.</p><h4>User Interviews</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*KZRyNUoRkcOR1DuD-lGmCw.png" /></figure><p>We started with a topic map. Since we had started understanding user’s behavior and habits, we focused on asking questions that would give us an <strong>understanding of their motivations when engaging with social media, as well as the themes of the content they would engage with. </strong>We performed eight interviews and took turns conducting them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*60Ibrk-4m8JXxoO1lSyNlQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*--MQ9VWzeKSAsgW27yibbw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*l167ceD-jg3Nu5zhQ_UxDg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*DC1EVT2JybW2rmiGjvZ5IQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*7xfcusIDYGYuIYJzLyudYQ.png" /><figcaption>Photos from some of our interviews as they were being conducted.</figcaption></figure><p>Our main takeaways from our interviews are as follows:</p><p>— <strong>Stories originate from valuable memories</strong> like birthdays, weddings, trips, and other special occasions</p><p>— <strong>Users post selective individual pics</strong> around a larger theme, like one photo per city they visited</p><p>— <strong>Users care about privacy and how content reflects</strong> on themselves, and will delete or untag photos they don’t like</p><h2>Synthesis &amp; Ideation</h2><ul><li>Affinity Charting</li><li>Personas</li><li>Features</li></ul><h4>Affinity Charting</h4><p>We had done our research, now we needed to know what to do with it. We put the asks from our <strong>client brief on the wall in blue</strong> post-its to make sure we were staying on target. The findings from <strong>comparative research went up in orange</strong>, and the <strong>user research findings went up in pink</strong>. We organized the post-its based on similar ideas and when we took a step back, noticed three main categories emerge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*G9rGJVPmvoSUYk3-HCZqsw.png" /><figcaption>Was there ever a more perfect segue into personas?</figcaption></figure><h4>Personas</h4><p>Accidentally-on-purpose, we had introduced ourselves to our personas. The <strong>creator</strong>, the <strong>organizer</strong>, and the <strong>curator</strong>. We each took a persona and fleshed them out. Why would this persona want to use Timehop? Why would they want to add a group story? What would they want during this process? Why? Why? Why? Why? Why some more? Asking these questions helped us bring these personas to life. Meet Anna, Olivia, and Frank!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*gg-sdnJmnrxCMY-7g6nD2g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Leh_EaGI_S7-003uctw25g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*ZDeo6hgmyVfaGvA43qPzQw.png" /></figure><h4>Features</h4><p>We synthesized our research and brainstormed how to execute them into deliverable features. One way of doing this was by a <strong>group brainstorm</strong> of features derived from our affinity map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*EXJuXTylMFFa2i4xJGZkFg.png" /></figure><p>We also did a series of <strong>user stories</strong> for each persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/632/1*QlTBsTrhiOyu8JjCn2Q-MQ.png" /><figcaption>My persona was Frank, the follower, the curator, the casual scanner of all things social.</figcaption></figure><p>Lastly, we wrote out a master <strong>user scenario and flow for all three personas, </strong>in an effort to put these possible features in context.</p><blockquote>Anna just got back from a trip to Iceland with her two friends. Upon her return, she immediately uploaded her photos onto Facebook while her friends uploaded individual pics to Instagram. As a creator, she wants a way for them to compile all their media together so they can each enjoy the walk down memory lane come the 1-year anniversary of their trip. She opens Timehop and begins creating a new story via the button on the navigation bar. She adds her friends as contributors to the story, and they are now able to collaborate. Because Timehop doesn’t have the technical capabilities (as it’s not a social network or content creator, but a social aggregator), she pulls her friend’s info from her contact list. Timehop sends them a notification text or email. She then selects all the photos that Timehop finds from the Iceland dates she just input into the app.</blockquote><blockquote>Olivia, one of the story contributors, is an organizer. When she gets the notification that she’s been invited to this story, she opens her Timehop app and begins adding her Instagram photos. She sees that she can add or delete photos, or even add more contributors to the story. She adds Frank to the story, a friend she made while on her trip.</blockquote><blockquote>Frank isn’t a Timehop user so when he opens the notification he receives, he’s prompted to see the story and sign up for Timehop.</blockquote><p>Seeing some key consistencies across all methods of feature ideation, the main ones stuck out.</p><h4>Feature ONE</h4><p><strong>Research</strong>: Users put more effort into post creation depending on the lifespan of content. Think Instagram versus Snapchat.</p><p><strong>Finding</strong>: Easy content creation process using Abe as step-by-step guide.</p><h4>Feature TWO</h4><p><strong>Research</strong>: Users tag and organize their content by hashtags, profile tags, and geo tags.</p><p><strong>Finding</strong>: Archived group story tab to help users find their group content.</p><p>***Red flag for technical restraint. Timehop is a social aggregator, not a network or content-creation platform. Since we wouldn’t be able to index each profile’s content, we’d have to find a workaround.</p><h4>Feature THREE</h4><p><strong>Research</strong>: Users are motivated to post by social validation and reputation, so will delete or untag unflattering and inappropriate photos.</p><p><strong>Finding</strong>: All contributors must be able to edit and add to their group story. Group stories must have a setting to address privacy and sharing concerns.</p><p>Off to production we go.</p><h2>Prototyping &amp; Testing</h2><ul><li>Design Studios</li><li>Pop Prototype</li><li>Sketch Prototypes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/647/1*WnOYF8BBdMupyALeByiJnw.jpeg" /><figcaption>In this session of dot voting, we chose to keep Abe as our guide for the on-boarding of group story creation.</figcaption></figure><h4>Design Studio</h4><p>Our purpose for design studios was to <strong>quickly create features</strong> based on our personas needs. We did cycles of <strong>2 minutes to sketch screens</strong>, and <strong>5 minutes to sketch task flows</strong>. When aggregating all our drawings, we used the <strong>dot-voting</strong> method which allowed us to visually see which layouts we preferred to keep in our product, and what our standard icons and buttons would look like.</p><h4>POP Prototyping</h4><p>We then used the designs we voted on and fleshed them out into a POP prototype, in efforts to <strong>quickly validate our ideas</strong> before moving on to higher fidelity frames which would take more effort. We <strong>tested with four users</strong> who mainly expressed a desire to <strong>clarify our navigation buttons</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*OPc_3gtAZNE0LXWdbi4Tcw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*5sqXX0twrp_LAamEn_SJlw.png" /><figcaption>Image 1 is our POP prototype in the making, Image 2 are the lo-fi screens we used.</figcaption></figure><h4>Sketch Prototypes</h4><p>We moved on to higher fidelity wireframes in Sketch to further validate the flow of our story creation task, while mimicking the actual user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2EhhAAy3QVxuLsA6OIETTw.png" /><figcaption>We came up with 1o versions of wireframes in one day! This was a very early iteration.</figcaption></figure><p>We <strong>tested with 6 users</strong>, and even had an impromptu and last minute <strong>session with our “client”</strong>. Our biggest pieces of feedback was that an <strong>archived group story didn’t stay within Timehop’s business model</strong> of ephemeral and daily content. We also gleaned from our tests that our story creation on-boarding process could be <strong>more concise</strong>. To incorporate both these pieces of feedback, we made the current photo post our <strong>trigger to create a group story</strong>, as opposed to an isolated icon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/803/1*Nj4Z4HCKgxAjQCzaiBn_Jw.jpeg" /><figcaption>Our app map helped us see which extra screens we needed to flesh out to complete our user flow based on our three personas.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lwsfYNQC3fz6f5BIWKNAnQ.png" /><figcaption>Our last wireframe, which you’ll have seen screens of in our prototype, showing a point of entry into story creation via the daily post trigger as well as a more concise on-boarding process.</figcaption></figure><h2>Wrapping Up</h2><ul><li>Next Steps</li><li>Our Solution</li><li>Group Dynamics</li><li>Can the real Timehop please stand up?</li></ul><h4>Next Steps</h4><p>Our team would’ve liked to <strong>test our final prototype</strong>. Our impromptu client meeting happened on Friday afternoon, our last day of class-time. We were able to spend just enough time implementing previous rounds of feedback into our final prototype, but were unable to validate it. We also would’ve loved to spend more time <strong>A/B testing different group story layouts</strong>, as well as spend more time thinking about m<strong>ultiple types of media</strong> that are available on Timehop, and how they would group together.</p><p>Additionally, we spent a lot of time throughout our project balancing the line of creating a new Timehop feature which would make it more dynamic, while still sticking to its<strong> business model</strong>. If this feature were deployed in Timehop, I would’ve loved to see the data of <strong>how many new users who signed up for Timehop when they received invitations to join a group story</strong>. This would tell us if we actually addressed our brief’s business goal of expanding Timehop’s customer base. We also had many discussions about how to work with <strong>Timehops’ technical restraints</strong>. Had we been working with stakeholders and developers, we would’ve appreciated an opportunity to speak with them and see what the <strong>long-term business goals </strong>for Timehop were.</p><h4>Our Solution</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*tqBVliXxOhvOwbYFUXTHCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*DaLa56QTJb0gYWUDzex1kQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*STYGn-2KL4RxLtqJUUbWqg.png" /></figure><p>The three images above indicate how we addressed our three features listed earlier. We were able to create an <strong>easy content creation process</strong>, and were still able to utilize <strong>Abe</strong> despite taking away many screens and using the <strong>daily content as our trigger</strong>. To be completely honest, we were just happy we got to include another image of our insufferably cute mascot.</p><p>We created the <strong>archived group story tab</strong> to help users find their group stories, but upon our last conversation found that <strong>this wasn’t appropriate for Timehop’s brand</strong>, and ended up <strong>scrapping this feature</strong>.</p><p>Lastly, we addressed <strong>privacy and sharing</strong> concerns by creating a <strong>permissions pop-up</strong>, before a story is created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*TlGaLhkYIJaX9OHrAsILKw.jpeg" /></figure><h4>Group Dynamics</h4><p>Working in a group for the first time had its struggles. But those were few and far between. To settle these disputes, we always went back to the brief, research, and user. We were an incredibly talented group, with each member bringing a different strength and weakness to the table. We also had great energy and pace. When our client told us on the last day that we should have gone in a different direction, and not to worry that we didn’t have time to execute it, it wasn’t even a question between us three that we should go ahead and continue to show off how efficient we were. The key to our success was being able to think about our project on a macro level while maintaining our persistent perfectionism when it came to every pixel. The most important factor tying these two opposing methods together was keeping our focus so we always knew how to move forward and what we were moving towards. Go, team!</p><h4>Can the real Timehop please stand up?</h4><p>Weeks later, the real Timehop sought users to test some of their own new features, one being a group shared story feature! I was also able to share my project with them. It was humbling, to compare results and see what I could have done to more efficiently design the new feature, as well as empowering to see the similarities as a very beginner designer.</p><blockquote>Check out our <a href="http://invis.io/X93JE2XDY"><strong>final prototype</strong></a>.</blockquote><blockquote><a href="https://drive.google.com/file/d/0B_BN_CLMGraTMzgzTTFVVVdHRXM/view?usp=sharing">And our full presentation <strong>here</strong>.</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c79bcf41bc2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clowns, E-Commerce, and Information Architecture.]]></title>
            <link>https://medium.com/@nicoleyoung/clowns-e-commerce-and-information-architecture-cd6e127e178a?source=rss-2a127319b33c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd6e127e178a</guid>
            <dc:creator><![CDATA[Nicole Young]]></dc:creator>
            <pubDate>Mon, 29 Jun 2015 03:59:42 GMT</pubDate>
            <atom:updated>2015-10-30T16:49:25.551Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>This was my second project at General Assembly, centered around information architecture and content strategy for an e-commerce website, <a href="http://www.newyorkcostumes.com/">NYC Costumes</a> (now renamed Halloween Adventure). My design meets user, business and brand goals and follows IA heuristic best practices. The project happened over 2 weeks, producing a responsive website, 100 items of inventory, and some badass research.</blockquote><h2>The Client’s Problem</h2><h4>Small retailers need to step up their game thanks to the likes of e-commerce retail giants such as Amazon.com.</h4><h2>The Opportunity</h2><h4>How can we redesign NYC Costumes so it serves as a beginning to end, one-stop shop, for all user’s party and costume needs- thus boosting sales and brand recognition for the business, as well as user satisfaction for the buyer?</h4><h2>Research Methods</h2><ul><li>Comparative Analysis</li><li>User Card Sorts</li><li>User Flows</li><li>Persona Analysis</li></ul><h3>Comparative Analysis</h3><h4>Contextual Inquiry-</h4><p>To get a feel for the brand and the business, I did a walk through of the NYC Costumes brick &amp; mortar store. Guess who happens to be morbidly terrified of life-sized figurines, clowns, and masked dolls?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*7Gvvo7q7nGB5oHyFuyfTcw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/435/1*d_d4dbtVshXF2RdrtZK14w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*yA2ucPo_Smy6Kvs9L7WAiA.png" /><figcaption>From left to right, the fear-inducing storefront, the themed organization of the store, a terrified UX designer and observer.</figcaption></figure><p>I learned that shoppers who make their purchases in-store expect their buying experience to also include a walk through of all aisles, and interaction with items and toys they had not initially set out to purchase. Because visiting a costume store is much more of a novelty experience than say, getting groceries or clothes shopping, shoppers expect more of a total experience than a direct path to purchase.</p><h4>Competitor Research-</h4><p>I looked at five other competitors in the costume &amp; party supplies industry; Abracadabra, Balloon Saloon, Party City, Gothic Renaissance, and Village Party Store. I looked at their navigation hierarchy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*e0a7bBGVqVjMGlsxVOkc5A.png" /><figcaption>Balloon Saloon interestingly put their inventory navigation at the bottom of their website. Some competitors focused on corporate pages in their main navigation, others focused on promotions, and most focused on their inventory.</figcaption></figure><p>Then I compared each competitor’s Google ratings and reviews which gave me a wider array and direct insight of customer feedback, their pain points, and their happy points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*7B2Fz7PFMNc-shf4pyeVMA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*E3PgNOyuQd8U2z-u-PDzNA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*HsBBjKuNfLKipWDgeMRBZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*C3Esr6MqxthZ9GXiRaBugA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/461/1*K9xe4phKOJyCkMAJ8cluIw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*WJDzLdfD_BIDspty7WgCuw.png" /></figure><p>I looked at each competitor’s homepage layout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*44f-4wJy1rcjNZNI3WfBVg.png" /></figure><p>And their market positioning, business model, and value propositions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*yyMyLscseqtK_rML1mARLw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*-SV7EWZxVutEBP8e1fmP3A.png" /><figcaption>My biggest finding was that many of these stores list their inventory as a catalog, without a built-out opportunity allowing users to make an online purchase.</figcaption></figure><p>And lastly, compared how each competitor categorized their products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*awe31yEhMg-BTqg1iCb3uA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*o9FTx7lSm-kKB4F_5i5EZw.png" /><figcaption>Gothic Renaissance had no inventory categorization on their website since they had no path to purchase.</figcaption></figure><p>I summarized my competitor research in this map based on whether a company specialized in a product (balloons, party supplies but no costumes, costumes but no party supplies, etc), and whether its website led to a purchase or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*6b68lS5RiGEx_3cl4pIAuw.png" /></figure><h3>User Card Sorts</h3><h4>Open-</h4><p>My comparative research helped me understand the general categories that competitors in the industry use to organize their products. I wanted to see if users would intuitively organize in a similar fashion, so I did a card sort. I gave each user the 100 sample products and asked them to organize the products in any category they saw fit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*uJrCwQ2LoK2Ath9rEV1WGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*BWnOBH6D1sTwlGXGm3XyjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*_NNzAhruND5uKdbfBlZJrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*ut3sl_LtNIrtrOy8jm3xvw.png" /><figcaption>My user’s self-selected categories aligned closely with the categories listed in my competitive research. I noticed that the user’s categories were broader, allowing room for more specific subcategories.</figcaption></figure><h4>Closed-</h4><p>I began to see clear similarities between the categories listed in my competitor research and in the open card sort. It was time to test this hypothesized structure of product information in a closed card test, where a user is given the categories before they begin card sorting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/1*A2N-L7B-l2Bpc2YJn5BqfQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/254/1*_IK9KthIXy5euUa8lANRhQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*ikKgifQiR1-H3pqTHX11Pg.png" /></figure><p>My organized structure of categories wasn’t yet foolproof (as a 2-week-old UX designer, I wasn’t overwhelmingly surprised). Here was some <strong>feedback</strong>.</p><blockquote>“I wish there were <strong>more subcategories</strong>, including a <strong>category for jewelry</strong> under accessories.”</blockquote><blockquote>“<strong>Differentiate</strong> between <strong>wearable</strong> decorations/props/accessories and <strong>non-wearable </strong>items.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*WMKtA2lxtK2wDJhhk-JPNw.png" /></figure><h4>Site Map-</h4><p>By creating a navigation site-map based on the competitor research and card sorts, then seeking feedback during our morning pin-up sessions and one-on-ones, I iterated my categories until I landed at version 2.2 where my users were happy and successfully able to understand where a sub-category could be found. This will appear in our prototype, linked below.</p><h3>User Flows</h3><h4>Add item to shopping cart, then view cart-</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*QxBkW94Q5p7rqjX0KyxQVw.png" /></figure><h4>Heuristic Analysis-</h4><p>Shoppers on <strong>Village Party Store</strong> were unable to finish their task, without a path to purchase.</p><p>Shoppers on <strong>Balloon Saloon</strong> could accomplish the task via a short path with an unclear navigation system.</p><p>Shoppers on <strong>Party City</strong> accomplished their task with multiple points of entry into a product and into the cart.</p><h3>Persona Analysis</h3><p>I looked at the three personas given to me and found some common wishes and pain points. Users wanted to…</p><blockquote>“Establish trust and a relationship with the brand and product”</blockquote><p>To me, this indicated the need for an <strong>emotional</strong> feature which could include <strong>product ratings, social reviews, a profile account.</strong></p><blockquote>“Have quick access to many options, product descriptions, suggestions of past and future purchases.”</blockquote><p>My features should help users make more <strong>educated</strong> purchases, which could include modules for <strong>related products, expandable details tabs, and purchase history.</strong></p><blockquote>“See fair pricing, not be overwhelmed and easily check out.”</blockquote><p>This indicates the need for an <strong>efficiency</strong><em> </em>feature, which might be an <strong>option to rent costumes instead of buy, a minimal layout, and QuickView checkout.</strong></p><h2>The Features</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*IbsZzIngsfLsEJyqJX4h2g.png" /><figcaption>Affinity map for feature prioritization, based on findings from research as well as the constraints from our brief.</figcaption></figure><p>After prioritizing the many different features I could include, I focused on specific features drawn from the different methods of research conducted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*RPg6HsKsryYXruiduea2ZQ.png" /></figure><h2>Sketching &amp; Prototyping</h2><h4>Sketch #1 — Paper</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/1*HU7CBaOql1g_3hgRcJPCNg.png" /><figcaption>Paper sketches for mobile and web, focusing on modular designs.</figcaption></figure><h4>Sketch #2 — Sketch Wireframe</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*YAwQERDe7E0XazFpVDhI3A.png" /></figure><p><strong>Feedback: </strong>Category menu placement isn’t too intuitive for a small mobile screen. Category buttons are <em>waaay</em> too tiny. Why is the shopping cart icon a hanger when across the retail industry it’s usually a cart or basket?</p><h4>Sketch #3 — Sketch Wireframe &amp; InVision Prototype</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*gop1II6-Bcmw0h4tpKCmbg.png" /><figcaption>From left to right: home page, category page, category page and QuickView, shopping cart, settings navigation.</figcaption></figure><p><strong>Feedback: </strong>During my tests, I asked users to find the different menus for settings and categories, save an item for later, add an item to the shopping cart via QuickView and the Product Page, and find related products.</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwZWE1jpnG9Y%26feature%3Dyoutu.be&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FwZWE1jpnG9Y%3Ffeature%3Doembed&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6c8ba49f2918ec9d369b3a8876edf714/href">https://medium.com/media/6c8ba49f2918ec9d369b3a8876edf714/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8y94QTBJ3ak%26feature%3Dyoutu.be&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8y94QTBJ3ak%3Ffeature%3Doembed&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6d48bc8a916c0c182d8a1163de8f3249/href">https://medium.com/media/6d48bc8a916c0c182d8a1163de8f3249/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D5-Vv_80YTiI%26feature%3Dyoutu.be&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F5-Vv_80YTiI%3Ffeature%3Doembed&amp;type=text%2Fhtml&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ba0140500992a3a24ab7cd187e12f533/href">https://medium.com/media/ba0140500992a3a24ab7cd187e12f533/href</a></iframe><p>All my testers ran into the same problem. It was not clear how to find the different categories. The category title didn’t appear to be a drop-down menu, because the button didn’t have enough contrast to stick out. I changed the button to a darker, and filled in arrow, which you can take a look at in the prototype listed below.</p><h4>Sketch #4 — Sketch Wireframe for Web</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/917/1*FnrYUh_iaR8p4RLocAEGkg.png" /><figcaption>This web wireframe takes you through the home page, to the category page, through QuickView checkout, the shopping cart, and the alternate path to purchase via the product page.</figcaption></figure><p>Because I had started with the mobile wireframe, it was much easier to translate these into a web template. With more space to work with I was able to increase the number of columns as well as hero image size, but still easily maintain template consistency by keeping the same format. Web is more conducive to hover states, so what you would previously tap on in mobile you can hover through on web, streamlining the checkout process.</p><h2>The Solution (so far)</h2><h3>The Final Prototype</h3><h4>Sketch #4 — Sketch Wireframe &amp; InVision Prototype</h4><p>My most important task for the next iteration was to more clearly differentiate between the settings and categories menu. By filling it in and making it bolder, I hoped to draw more attention to it.</p><h4>The Walk-Through Story</h4><blockquote>John is a single parent of a 12 year old girl. One day she comes home from school, upset because her classmates made fun of her wanting to be the blue Power Ranger. “Only girls can be the pink or yellow power ranger!” they said. As a single parent and art teacher, John wants to instill values of independence, self-expression, and creative freedom in his daughter. He decides to empower his daughter by surprising her with a blue Power Ranger costume over the weekend and having their own adventure! He likes using NYC Costumes because it shows him related products, where he’s able to find a blue Power Ranger in his adult size. It also offers him a rental option, and as an art teacher, he’s grateful for the cheaper option. After their significant day, and after he sees his daughter empowered, he decides to go back to NYC Costumes. He signs in, looks through his recent purchases, and finds that he can easily find the return label to print. While he’s online, he decides to leave a positive review abut the ease of his transaction, the product, and the emotional connection he had just built with the brand.</blockquote><blockquote>Check out the final mobile prototype <a href="http://invis.io/CU3E6YUS2">here</a>.</blockquote><h3>Summary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*Ev-H4xbtOA6UgK2266DC4g.png" /><figcaption>The user flow for my redesigned NYC Costumes responsive website.</figcaption></figure><p>My solution incorporates all the features I had decided were important based on comparative research, card sorting, user flows, and persona analysis. Drawing out the user flow for my design allowed me to clearly see how a user had multiple paths of entry to the product page, as well as to the shopping cart, which is something I found important after comparing competitive user flows. My categories, based on the card sorting and comparative research, had been tested and verified to be logical as a means of finding products. Lastly, by taking a closer look at our personas, I was able to find out what features would best tie in the user and the information I had just organized!</p><h3>Personal thoughts</h3><p>What I found most surprising was how much research I ended up doing. Looking back, I’d say it was about 85% of the whole project. I began to struggle with what to do with all the research I had done towards the end of the research process. What did I do with all the information now? How do I consolidate and find out what the important takeaways are? The best way for me to get around to this was just to <strong>do </strong>it, test, iterate, test, so on and so forth. Having said that, it was still my favourite part. I felt more confident in my plans when I knew they derived from logical observations about competitors and users, and it also made me feel like I had a bigger hand in the overall business. Overall, I found this project to be important to me because it clarified why research was the most important step. Before creating a solution, I really needed to know the problem.</p><h3>Next steps</h3><p>If I had more time, I would’ve liked to create a clear annotated form of all my wireframes. By the time I got to the prototyping part of the design, I found myself very stuck in the ‘big picture’. After spending the majority of my time taking all the research I had done, converging those ideas, and then broadening them out again when testing and iterating, I found myself mentally stuck in a loop where I never thought I was going to get to a final product worthy of definitive explanations. “That will come later,” my mind told me. Part of this course has taught me that even though you will never feel like you have a perfectly finished and polished product, you’ll still have to package it and send it off. Be ready to be <em>done</em>!</p><p>Other improvements? As always, more tests, more feedback, more iterations. Is there ever such thing as a perfect final product with no more improvements to be made?!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd6e127e178a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>