<?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 Amy Lima on Medium]]></title>
        <description><![CDATA[Stories by Amy Lima on Medium]]></description>
        <link>https://medium.com/@amylima?source=rss-93c57afac1d2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KYJ3mY5Xc5P4ic8-yaAAtA.jpeg</url>
            <title>Stories by Amy Lima on Medium</title>
            <link>https://medium.com/@amylima?source=rss-93c57afac1d2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:49:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amylima/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[Pinterest’s Product Design Apprenticeship: A Q&A]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/pinterest-studio/pinterests-product-design-apprenticeship-a-q-a-50fe372b9c51?source=rss-93c57afac1d2------2"><img src="https://cdn-images-1.medium.com/max/2500/1*NPCzZ1bnjDxdYhkA29-DMw.jpeg" width="2500"></a></p><p class="medium-feed-snippet">Amy Lima, Pinterest&#x2019;s first Apprentice Product Designer, and her mentor, Alan Walker, chat about apprenticeships at Pinterest.</p><p class="medium-feed-link"><a href="https://medium.com/pinterest-studio/pinterests-product-design-apprenticeship-a-q-a-50fe372b9c51?source=rss-93c57afac1d2------2">Continue reading on Pinterest Design »</a></p></div>]]></description>
            <link>https://medium.com/pinterest-studio/pinterests-product-design-apprenticeship-a-q-a-50fe372b9c51?source=rss-93c57afac1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/50fe372b9c51</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[apprenticeship]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Amy Lima]]></dc:creator>
            <pubDate>Mon, 11 Apr 2022 19:02:39 GMT</pubDate>
            <atom:updated>2023-05-16T18:12:39.844Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I wanted to challenge myself as a young designer, so I redesigned Silicon Valley’s buzziest app.]]></title>
            <link>https://blog.prototypr.io/i-wanted-to-challenge-myself-as-a-young-designer-so-i-redesigned-silicon-valleys-buzziest-app-452c82c85ef6?source=rss-93c57afac1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/452c82c85ef6</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Amy Lima]]></dc:creator>
            <pubDate>Mon, 01 Feb 2021 18:44:40 GMT</pubDate>
            <atom:updated>2021-02-09T00:53:45.538Z</atom:updated>
            <content:encoded><![CDATA[<h3>I wanted to challenge myself as a young designer, so I redesigned Silicon Valley’s buzziest app, Clubhouse.</h3><p>Reimagining Social Media’s next star: A Case Study.</p><p><em>Disclaimer</em><strong><em>:</em></strong><em> I do not work for Clubhouse, and the views in this case study are strictly my own. As a budding designer, I acknowledge that my vision for this project may be overly ambitious and at times reliant on assumptions of business goals and user data. In a perfect world, I’d be working alongside the Clubhouse team with direct access to these resources to guide my work. Until then, this case study is meant to be an exploratory learning experience on a product I deeply admire.</em></p><p><em>PS: This full case study can also be found on my </em><a href="https://www.amylima.design/clubhouse"><em>portfolio</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H2rqorQIVLZEocjSmtjpmg.jpeg" /><figcaption>Final mockup screens</figcaption></figure><h3>TL;DR:</h3><p>I wanted to test my limits as a young designer by improving the user experience of Clubhouse, the hottest new audio conversation app on the social media scene. After speaking with both power users and novices on the app, I uncovered some specific pain points with wayfinding and discoverability in the app, which became the primary design challenge that guided my work throughout this project.</p><p><a href="https://www.figma.com/proto/zZ7KUnIt9Hrw27IKiXJfEo/CH-wireframes?node-id=263%3A257&amp;scaling=scale-down">Play with the prototype</a> to see how a user would move through key interactions in the app, and continue below for a comprehensive look at the process that led to this final result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W2nV2eOB5Js1PHPlqC0q2w.jpeg" /><figcaption>Onboarding Mockups</figcaption></figure><h3>The Brief:</h3><p>It’s difficult to understate the excitement around <strong>Clubhouse, the audio chat app where members can move around virtual rooms discussing topics ranging from culture to politics.</strong> Raising its first <a href="https://www.forbes.com/sites/alexkonrad/2020/05/15/andreessen-horowitz-wins-vc-sweepstakes-to-back-clubhouse-voice-app/?sh=57e5f3bd6f2a">$100 million</a> with only 1,500 users a month after its beta release, at the time of this writing, Silicon Valley’s buzziest app has just been valued at <a href="https://fortune.com/2021/01/25/clubhouse-reaches-a-1-billion-after-taking-off-some-nine-months-ago/">$1 billion</a> dollars, a mere 9 months after taking off and before even launching to the public.</p><p>Beyond its success with investors, Clubhouse has amassed a fiercely loyal user base, whose creativity has spanned from a 24-hour continuous room dedicated to new user onboarding to a live production of <a href="https://www.complex.com/pop-culture/2020/12/clubhouse-users-organize-live-production-the-lion-king">The Lion King.</a></p><p>As an early beta user on the invite-only platform, I had the unique perspective of following the product’s updates (and exponential success) in real-time, and sought to challenge myself with my most ambitious project yet: redesigning Silicon Valley’s most exciting app in recent memory. <em>No pressure.</em></p><p>The high-level goals of this project were:</p><ul><li><strong>Improving discoverability within Clubhouse</strong>, allowing users to more easily find new rooms, people, and clubs to engage with</li><li><strong>Creating a more seamless Hallway experience,</strong> where users can filter find the most relevant rooms to them</li></ul><h3>UX Challenges: Simplifying a complex information hierarchy</h3><p>One of the main considerations I had to take into account was the hierarchy of the main components users can interact within the app:</p><ul><li><strong>People</strong> (other users of the app)</li><li><strong>Rooms</strong> (a virtual meeting place for audio conversations), and</li><li><strong>Clubs</strong> (interest-based groups rooms can be hosted under).</li></ul><p><strong>Beyond this, I had to consider how each of these components were connected, both interpersonally and through time:</strong> currently, a Clubhouse user’s Hallway (home screen) shows <em>live</em> rooms connected to the people and clubs they follow (which I’ll refer to throughout this case study as “in-network”). This makes it difficult for users to easily keep track of upcoming rooms in their network, as well as join new, out-of-network rooms.</p><p><strong>This became a major dichotomy throughout my work: </strong>I needed to find a balance between making each of these individual parts of Clubhouse easily discoverable while maintaining — and simplifying- the web that weaves them together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DLix9yFUuehG31pIyf_N-g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sF5G1aLg1zhETdQ_cBFEaA.jpeg" /><figcaption>Discovery task flow and mind map of the relationship between Clubhouse components</figcaption></figure><h3>Research + Planning: A UX Researcher’s Dream</h3><p><strong>Another unique aspect of this project was the direct access beta users have to the Clubhouse founders,</strong> Paul Davison and Rohan Seth — every Sunday, the pair host Clubhouse Townhall, an open forum where they share the week’s latest product updates, their upcoming roadmap, business goals, and top priorities, as well as holding space from user-submitted Q&amp;As.</p><p>And thanks to Clubhouse’s enthusiastic user base, the official Townhalls are regularly followed by Townhall recap rooms (shoutout to Community Club), where power users would deep dive into the week’s updates and what features they’re most excited for.</p><p>Between Clubhouse Townhalls, recap rooms, and both official and community-run new member onboarding rooms (including FAQs, Q&amp;As, and discussions), <strong>I spent on average 5 hours a week for 6 weeks gaining as many business insights and goals as I possibly could</strong> from my limited vantage point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ed_2EZCteJg2-HglE0ETgA.jpeg" /><figcaption>A compilation of some of the rooms that became a regular part of my UX Research</figcaption></figure><p>From these discussions, the overarching goals of the Clubhouse team are:</p><p>• <strong>Making Clubhouse accessible for everyone:</strong> Paul always made it clear that the team’s top priority was to scale Clubhouse as quickly as possible while not sacrificing quality</p><p>• <strong>Putting creators first:</strong> another point Paul never understated was the team’s prioritization of the platform’s creators, building tools that would allow for creator monetization</p><p>• <strong>Improving discoverability and suggested content:</strong> at the time of this project, Clubhouse was actively building out their topics directory and algorithms that would make finding relevant rooms progressively easier</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rNYWr45Vs-3ehGQwHnGaHw.jpeg" /><figcaption>Early sketches of how different screens might behave</figcaption></figure><h3>User Interviews, from power users to newbies</h3><p>I spoke with Clubhouse users — both power users and more casual community members — to uncover friction points they currently had with the app’s discovery experience. These interviews showed:</p><ul><li><strong>Keep it lightweight:</strong> most users preferred room discovery to be a spontaneous experience, not necessarily wanting to schedule upcoming rooms in their personal calendars</li><li><strong>Cluttered Hallway:</strong> most users were confused by how the hallway was currently curated, and who of the people they followed were in any given room present</li><li><strong>Hallway as a source of discovery:</strong> despite the cluttered hallway experience, most users still relied on the hallway to find new rooms, despite there being an existing (but not yet robust) “Explore” tab</li><li><strong>Friends first:</strong> when deciding which rooms to join in the hallway, users unanimously wanted to see which of their friends were in any given room</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c2qGTOazOpYjYsKyy_lW0A.jpeg" /><figcaption>Affinity map of my user interviews (made using Evolve)</figcaption></figure><blockquote>How might we make the Hallway a clear and concise place for spontaneous interaction, while facilitating lightweight out-of-network discovery?</blockquote><h3>UX Solution: Streamlining the Discovery-to-Hallway pipeline</h3><p>I developed a simple yet powerful UI that makes wayfinding within your hallway and rooms easier, and bringing rooms found through the discover page into your hallway a breeze.</p><p>In order for this solution to feel cohesive and not siloed, <strong>I needed to implement a near-full redesign Clubhouse, broken up into 5 main experiences.</strong></p><p><em>Play with the final prototype </em><a href="https://www.figma.com/proto/zZ7KUnIt9Hrw27IKiXJfEo/CH-wireframes?node-id=263%3A257&amp;scaling=scale-down"><em>here</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PVOD3TFUzv2GL4-rO3WrXw.jpeg" /><figcaption>Early Wireframes</figcaption></figure><h3>Experience 1: The Hallway</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dMBTSx-OHOHPVqN480Lbzg.jpeg" /><figcaption>The Clubhouse Hallway currently (left), and reoptimized for more functionalities and access to controls (right)</figcaption></figure><p>Users wanted their hallway experience to feel more intentional and within their control. To achieve this, I established a top-level hierarchy of:</p><ul><li><strong>ongoing vs. upcoming</strong>, to allow users to not only see active rooms but get a quick overview of scheduled rooms within their network</li><li><strong>filters by topics of interest,</strong> selected by the user during onboarding, and a</li><li><strong>sort rooms in your hallway </strong>by people vs clubs you follow</li></ul><p>An additional UI decision was to only present people you follow within the rooms in your hallway. This would alleviate the current issue of ambiguity surrounding the names users currently see in the room cards in their hallways.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*j_XwoutFyduLOOFGD0hq7g.gif" /><figcaption>Navigating the reimagined Hallway</figcaption></figure><h3>Experience 2: Room preview</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*6yrxwCarc4B4UfYrFnc3Ig.gif" /><figcaption>Room preview in action, where users can see a full list of which friends are inside any given room</figcaption></figure><p>Currently in Clubhouse, clicking on a room in a hallway immediately drops you into that room’s conversation.</p><p>Since identifying friends in any given room was a high decision factor for users joining a room, I wanted to design a way for users to see who they know inside before committing to join.</p><h3>Experience 3: Discovery</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHYznLw5YnzwO6Ch-WkhSA.jpeg" /><figcaption>Clubhouse’s Explore tab currently (left), and redesigned as an immersive discovery experience (right)</figcaption></figure><p><strong>Currently, discovery in Clubhouse is siphoned:</strong> users go to the Explore tab to discover people and clubs by categories and keywords, and to the calendar tab to discover both active and upcoming rooms across all of Clubhouse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UWepqUKdX3RvoRbIjopUAg.jpeg" /><figcaption>Bringing a room to your hallway via Clubhouse’s Calendar tab currently (left), and reimagined as a simple bottom sheet function (right)</figcaption></figure><p><strong>Most participants actually didn’t use these tabs to achieve their primary goal of discovery,</strong> instead adopting workarounds such as discovering clubs through user profiles, discovering people through rooms, and discovering rooms primarily through their hallway, limiting the scope of content they were being exposed to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*h5qCEOIwa7GWlmTUoRcaVw.gif" /><figcaption>An immersive discovery experience with rich filter and sort options</figcaption></figure><p>While I designed UI solutions to make these workarounds more seamless, I wanted the discover page to be the go-to destination to accommodate for all these use cases, allowing users to search for people, clubs, and rooms by Clubhouse’s growing topics directory, in addition to keywords.</p><p>I also integrated an additional sort functionality to further facilitate discovery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*27XuweBDCZ2f_EEZcnExMA.gif" /><figcaption>Sending an out-of-network room to your Hallway</figcaption></figure><p>Users also wanted an easy, lightweight solution to discover and access out-of-network rooms.</p><p>The ability to send a room from the discover feed to your hallway without committing to following that room’s moderators, corresponding club, or scheduling in your personal calendar was the biggest challenge of this project, involving many iterations in order to feel intuitive.</p><h3>Experience 4: Active Users</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iNL60npLBiSd6YEdRhm1qw.jpeg" /><figcaption>Clubhouse “Available to Chat” flyout currently (left), and reimagined as an “Online Now” tab (right)</figcaption></figure><p>A close cousin to the hallway, your active users screen is where all your Clubhouse people and clubs that are currently online live. <strong>83% of users interviewed mentioned scanning this screen to quickly identify what rooms their friends are in.</strong></p><p>I added a much-requested search bar to further facilitate friend-finding, as well as a sort drop-down menu to reach an even more important distinction: who’s actively participating in a room vs. just listening in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*1TNaZOSK_mWV5wl4GGgyfQ.gif" /><figcaption>Discovering active users by different sort options</figcaption></figure><h3>Experience 5: User and Club Profiles</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rhi_nwhs7P9TudsxJT3Isw.jpeg" /><figcaption>Clubhouse User Profiles currently (left), and after consolidating clubs as one metric (right)</figcaption></figure><p><strong>87% of users discover suitable clubs to follow via user profiles directly. </strong>There exists a further hierarchy within clubs: followers (who receive notifications and see club-branded rooms in their hallway), and members (who, in addition to the above, can also start club-branded rooms themselves).</p><p><strong>In Clubhouse’s current design, the clubs a user follows vs. clubs a user is a member of are in disparate locations: </strong>in the user’s following list and at the bottom of their user profile, respectively. This was confusing to users wanting scan all the clubs associated with a particular person.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*y6fTdFDDGUnY2NIeNqPtWw.gif" /><figcaption>Navigating both User and Club Profiles</figcaption></figure><p>By making clubs associated with a user a consolidated metric, users visiting that profile <strong>can more easily see what clubs that person belongs to, </strong>and immediately follow without visiting a new screen.</p><p><strong>On the club level, being able to access metadata </strong>such as previously held rooms, upcoming rooms, and club admins can help a user get a more effective overview of the club.</p><h3>UI &amp; Branding: A Case for Dark UI</h3><p>In bringing all the pieces of this experience together, it became clear that adding too many visual elements would disrupt the visual hierarchy needed to move through the app with ease.</p><p>Additionally, the typical user experience on Clubhouse is already so immersive and emotive, often spanning all hours of the night — I wanted to take advantage of this use case and implement an elegant UI that emphasized Clubhouse’s few content types harmoniously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w5jHQJ2fEkraBehKAxj94w.jpeg" /><figcaption>A snippet of the Style Guide that guided my work</figcaption></figure><h3>Usability Testing: <strong>How effectively is findability and discoverability throughout the app?</strong></h3><p>After conducting my usability tests, I created an affinity map with insights, behaviors, and findings during the tests. Most users moved through the app with little to no missteps, but for many participants, there was one main point of friction that disrupted a key pillar of this redesign:</p><ul><li><strong>It was still unclear how to access a room you saved from the Discovery page to your Hallway.</strong></li></ul><h3>Usability Testing Insights &amp; Priority Changes</h3><p>Initially, I designed for upcoming out-of-network rooms found in the discover tab to appear in the hallway by the user starring the room, which would then appear in your hallway algorithmically, further discoverable via the “sort by” drop-down menu. There were a few problems with this:</p><ul><li><strong>The original design essentially treated these rooms as saved items, </strong>which inadvertently (and incorrectly) prioritized these rooms over other rooms found in your hallway</li><li><strong>This treatment could have greater implications of disincentivizing spontaneous room creation,</strong> or unfairly prioritizing out-of-network rooms in general</li><li>Beyond this, <strong>embedding a saved item in a sort drop-down wasn’t intuitive</strong> or an expected place to find this type of content</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/255/1*ZRNd59-vmpEzgrYk9IN2vQ.gif" /><figcaption>Setting notifications on the room, club, and user level</figcaption></figure><p>The solution I came up with was to leave room appearance in the hallway to Clubhouse’s algorithm and put the power of further prioritization into the user’s hands via custom notifications.</p><p><strong>My final iteration included design solutions for setting notifications</strong> on the people, club, and room level, so users never miss a conversation they want to be a part of.</p><h3>Conclusion: Lessons learned &amp; where we go from here</h3><p>Going into this project, I knew this would be an ambitious challenge for a young designer. What I didn’t know was just how intricate and all-encompassing that challenge would be.</p><p><strong>I learned that working on a highly publicized and highly beloved product comes with a lot of external pressure and internal emotions to do right by (seemingly) everyone:</strong> power users with fierce attachment to existing structures, new users who can’t fully experience the nuance of an audio app as a static prototype, and the small but mighty Clubhouse team, who are actively iterating their product on a weekly basis, potentially launching imaginative solutions themselves for the same challenges I’m working on, or others I haven’t even imagined yet. Against a constant stream of public conversation over an exciting product that felt almost ethereal, I’ll humbly admit that there were times where this pressure got the best of me and I felt like a total imposture who bit off way more than she could ever chew.</p><p>The biggest lessons this project taught me were the delicate balance between perseverance when faced with complex challenges, grace in the wake of perceived failure, and when to be okay with “good enough” (for this iteration, of course).</p><p>In the end, I’m extremely proud of what I was able to accomplish with this project at this stage in my design journey, and often reminded myself of my favorite mantra that led me to product design in the first place:</p><blockquote>“All I wanted was a job like a book so good I’d be finishing it for the rest of my life.”</blockquote><p>Product design is that job for me, and I’m proud to say that while this project (and all my others) will never be fully finished, I breathed as much life into it as much as I could — I hope you enjoyed it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=452c82c85ef6" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/i-wanted-to-challenge-myself-as-a-young-designer-so-i-redesigned-silicon-valleys-buzziest-app-452c82c85ef6">I wanted to challenge myself as a young designer, so I redesigned Silicon Valley’s buzziest app.</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What every designer needs to know before their first hackathon]]></title>
            <link>https://uxplanet.org/what-every-designer-needs-to-know-before-their-first-hackathon-e880def70dfb?source=rss-93c57afac1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e880def70dfb</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Amy Lima]]></dc:creator>
            <pubDate>Thu, 12 Nov 2020 03:22:11 GMT</pubDate>
            <atom:updated>2020-11-18T13:59:48.098Z</atom:updated>
            <content:encoded><![CDATA[<h4>My Experience and Lessons Learned Attending (and Winning) My First Hackathon</h4><figure><img alt="Man wearing a halloween mask and eyeglasses on his office computer" src="https://cdn-images-1.medium.com/max/1024/1*qorUudPtQ3Ouky2CYtsDjw.jpeg" /><figcaption>Spoiler alert: you’re not actually “hacking” anything</figcaption></figure><p>One of the reasons I love the world of design so much is that its constant evolution requires you to maintain a growth mindset, always eager to upskill or explore a new craft; as someone who finds great fulfilment in a meaningful challenge, this lends especially well to me. And so put it to the test, I humbly signed up for my first hackathon, only moderately aware of what such an event entails, and even less certain of what valuable contributions I could bring to the table as a (very) Junior UX Designer. Challenge accepted.</p><p>The first hurdle was finding a hackathon to participate in in the first place. I was overwhelmed by the amount of choices out there, and found that a majority of hackathons were for students-only, leaving university graduates and current bootcamp students like myself in a gray area. Nonetheless, I set my sights on the more inclusive and social-cause driven events I could find, and reached out to the organizers to confirm my eligibility after applying. A few exchanges later, I was accepted into DubHacks, the largest 24-hour hackathon in the Pacific Northwest. After putting my imposter syndrome aside, forming a team, and an exhaustive 24 hours, my team’s project went on to win the Best Use for Social Good category. Here are some things I learned from the experience.</p><h3><strong>Why Every Hackathon Team Needs a Designer</strong></h3><p>I’m pleased to report that what you’ve heard many times over in design school proves to be true: not everyone thinks like a designer. My team consisted of brilliant developers who were able to quickly deduce how to use their knowledge to build a software tool, but were less versed on how to build a viable <em>product</em>. A good designer knows that a product is not merely the sum of its parts, but a coherent and cohesive experience — this is exactly the unique perspective a designer brings to the table at a hackathon.</p><blockquote>A good designer knows that a product is not merely the sum of its parts, but a coherent and cohesive experience.</blockquote><p>As a designer on the team, it’s your job to look beyond what we were building on a mechanical level, and constantly direct the team towards the greater, more human level of what you’re creating. Yes, the framework and the tech stack are vital, but what good is the greatest technology if it’s unusable (or unclear) to the people who need it most? Whenever our product’s positioning started to feel too broad or unfocused, I’d do my best to reign it in, reminding the team who we’re building this for, what our primary use cases are, and what problem we’re trying to solve.</p><p>If you’re a designer preparing or interested in participating in a hackathon and (like I was) aren’t sure what deliverables or actionable steps a designer takes throughout the hackathon process, here’s a short list of what my involvement looked like:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FlsAVei7DRrPIt3C5KC%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fbuidl-ethdenver-bufficorn-lsAVei7DRrPIt3C5KC&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2FlsAVei7DRrPIt3C5KC%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="297" frameborder="0" scrolling="no"><a href="https://medium.com/media/3740efa177871e81f6998ba16dbf4e62/href">https://medium.com/media/3740efa177871e81f6998ba16dbf4e62/href</a></iframe><h4><strong>Landscape Analysis</strong></h4><p>This is a crucial aspect of your hackathon project that shouldn’t be overlooked. Your project will not only be judged by its execution, but also its viability — what problem is it solving? Which users does it help? How do you know this? This is a great chance to tap into your Design Thinking process and get to the root of the problem you’re building a solution for.</p><p>For me, this involved doing extensive research into the issues surrounding our chosen problem area, as well as the existing tools in the market that aim to solve similar (or different) issues. I also snuck in some user research by reaching out to relevant acquaintances for short, informal user interviews to gain a better idea of their experience and pain points in this area. This was an invaluable step in our process, as when it came time to present our project, we not only had a minimum viable product to showcase, but the research to validate the need for our product in the first place.</p><figure><img alt="Presentation slide with notes on how people with limited vision and broadband access the web" src="https://cdn-images-1.medium.com/max/1024/1*2U5amvXS6_CMu44F08WkhA.jpeg" /><figcaption>I took a deep dive into the world of web inequity for those with vision impairments and limited broadband</figcaption></figure><h4><strong>Task Flows and Sketches</strong></h4><p>Due to the rushed and scrappy nature of hackathons, your finished project will not be fully fleshed out, so it’s important to at least include the most essential features. Creating your product’s primary task flow(s) helps the developers jump right into working on the most important functions first, which is especially helpful if your team ends up not being able to complete the development of your other task flows by the submission deadline. Rough sketches of what the interface will look like help developers contextualize what they’re building from the start and provide important constraints, however loose.</p><p>These were the first deliverables I sent to my team when the hackathon began. I explained to them the main task(s) we should aim to develop, and walked through my sketches of the interface, making note of the most important components on each screen (mainly our CTAs).</p><figure><img alt="A task flowchart of the main functionalities of our product (smart alt-text and a low-res video conversion)" src="https://cdn-images-1.medium.com/max/1024/1*Ph2kTyMgaFtJyYXdfdC5AA.png" /><figcaption>The basic task flows that our product would need to include</figcaption></figure><h4><strong>Wireframes and MockUps</strong></h4><p>Wireframes take your rough sketches one step further and give your developers even more important constraints to work with. Using tools like Figma or Zepplin to share your designs with your developers makes the best use of your time, as they can inspect and use the corresponding code. Adding high fidelity mockups in your presentation helps showcase your work and make it feel more real/functional than your MVP, which will most likely look like your low-fidelity wireframes.</p><p>My team didn’t officially start coding the front-end of our product until I sent them low-fidelity wireframes. After I shared the designs for the main interfaces, I spent a lot of time designing multiple screens and high-fidelity wireframes that never would have had time to be developed. Instead, I’d recommend focusing on the main interface(s) your devs will be building, and then flesh out a high-fidelity version for purposes of your mockup and presentation. To showcase the design in our presentation, I placed an PNG mockup of our product’s landing page in a device (using a Figma Community file template), as well as an additional short promo video I made using Rotato.</p><figure><img alt="Low-fidelity wireframes for our desktop site" src="https://cdn-images-1.medium.com/max/1024/1*rhtOu2O4uHiJOsk6zSuQ3Q.png" /><figcaption>My low-fi wireframes, most of which did not see the light of day outside my Figma file</figcaption></figure><h4><strong>Project Management and Presentation</strong></h4><p>As a designer, you have a holistic perspective on what your team is trying to build beyond the code. Coupled with the landscape research you conducted, this lends perfectly to taking the lead on building your team’s final presentation. Your presentation is the “big sell” of your project — without it, your product has no context, and can’t be judged by the panel. Your presentation doesn’t need to be immaculately designed in and of itself, but should include a few key points, such as:</p><ul><li>An introduction to your hack and team members</li><li>The problem you’re trying to solve</li><li>Your user base and business use cases, and how your product solves for these problems</li><li>Tech stack and product features</li><li>Further, long term impact of your product</li><li>Difficulties and complications you encountered, and what you learned along the way</li></ul><p>I built our presentation in Canva, which allows for easy collaboration and embedded media.</p><p>Designers have the unique advantage of not being pigeon-holed into one sole workflow during hackathons, which allows you to move your team along if/when they’re getting lost in code. This establishes important time limits and constraints, and helps make sure you distribute your time and tasks efficiently. Throughout the 24-hour event, I reminded my team of our upcoming deadlines: what time we should have our MVP finalized, when we would start practicing our presentation, and our submission deadline, providing sufficient buffer room for each in case anything went wrong or got delayed (which, in the world of hackathons, is a near guarantee).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FQGZBpodY7Kdtw99y04%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fkobe-bryant-jobs-finished-QGZBpodY7Kdtw99y04&amp;image=https%3A%2F%2Fmedia0.giphy.com%2Fmedia%2FQGZBpodY7Kdtw99y04%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="396" frameborder="0" scrolling="no"><a href="https://medium.com/media/bab57b5f6b12c83fbac7845d2a03c0c8/href">https://medium.com/media/bab57b5f6b12c83fbac7845d2a03c0c8/href</a></iframe><h3><strong>Where Empathy Meets Strategy</strong></h3><p>Our project idea was born out of my passion for making the web more accessible for people with disabilities and limited access to the internet. I strongly believe design (and tech) is a tool in which we can dismantle exclusionary systems in favor for more inclusive ones, and that commitment to serving underrepresented groups fueled our work throughout the event. I was lucky to be on a team with a member who already had some hackathon experience which allowed us to streamline our process, but looking back, there were other clear steps we took which contributed to our win in the Best Use for Social Good category.</p><p>Here’s my short list of tips to keep in mind to conquer your first (or any) hackathon experience as a designer:</p><h4>1. Start Early</h4><p>I of course don’t mean begin any actual hacking earlier than the event start time, but I do suggest getting to know your team, synthesizing some project ideas, and coming up with an action plan for once the event begins, before it actually begins. Our team hopped on a Google Doc one week before the hackathon to list out each of our core skills and propose 2 project ideas for us to later vote on. Before the hackathon even started, we already had a good idea of who each other were, what we were good at, and what we’d be building in the 24 hour timeframe.</p><h4>2. Do your research</h4><p>The importance of research in your process cannot be overstated. This not only helps you reach your problem statement and validate the world need for your project, but also serves as a reminder during the more daunting hours of the event what impact you’re hoping to make. In moments of insecurity, I’d look back at the research I’d done in this problem space, remind myself of the quantifiable need for a solution, and use that as fuel to keep pushing.</p><h4>3. Be Agile</h4><p>I learned pretty quickly that, perhaps unsurprisingly, building a minimum viable product from scratch in a short amount of time gets messy. Not everything you set out to build in the beginning of the hackathon will make it into the final design, and that’s okay. This is a great environment to be scrappy, fail fast, iterate, and streamline your workflow as much as possible.</p><h4>4. Communicate clearly and frequently</h4><p>Our team communicated mainly via Facebook Messenger, where the developers could quickly troubleshoot and bounce ideas off each other. I used that communication channel to keep the team updated on what I was working on, make some UI notes, ask if anyone needed me for anything, and remind the team of what I needed from them, be it some tech copy to put into our presentation or a reminder of the hour deadline we agreed to start reviewing our project by.</p><h4>5. Be passionate</h4><p>The cliche is not lost on me, either, but it’s true. Even your dream design job may come with some projects you’re not super excited about. Hackathons, on the other hand, provide the unique opportunity to build something you exclusively excited about, under no obligation other than your own will. Be it a social cause or a creative technology, finding a project you’re deeply passionate about will help guide, sustain, and validate your work from beginning to end.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F26xBxZdlxksm4oCje%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fcbc-funny-comedy-26xBxZdlxksm4oCje&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2F26xBxZdlxksm4oCje%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="307" frameborder="0" scrolling="no"><a href="https://medium.com/media/222e577bf0eedfdda2972c000553b3f6/href">https://medium.com/media/222e577bf0eedfdda2972c000553b3f6/href</a></iframe><h3>TL;DR: Get out there and be great</h3><p>I hope this guide serves not only as a framework for the seasoned designer to help structure your workflow during a hackathon, but also inspiration for the young designer to participate in the crazy, chaotic, thrilling, and rewarding world of hackathons head-on.</p><p>Had I let my fear and intimidation get the best of me, I would have missed out on a tremendous learning opportunity; beyond design deliverables, my first hackathon experience allowed me to practice my communication skills, work closely with developers and find a common language between us to help progress our work, and become comfortable working under tight timelines and constraints, all skills that are invaluable to a designer on any level, but especially insightful for a junior in the field who may not yet have ample opportunities to learn by doing.</p><p>So I encourage any and every designer reading this to be brave and be great — I’ll be cheering you on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e880def70dfb" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/what-every-designer-needs-to-know-before-their-first-hackathon-e880def70dfb">What every designer needs to know before their first hackathon</a> was originally published in <a href="https://uxplanet.org/">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interconnecting our world in 1̶4̶0̶ 280 characters or less]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uxdesign.cc/interconnecting-our-world-in-1%CC%B64%CC%B60%CC%B6-280-characters-or-less-e7c9dc391fca?source=rss-93c57afac1d2------2"><img src="https://cdn-images-1.medium.com/max/600/1*EvLmfjxnEgYNvI9Epoy2mw.png" width="600"></a></p><p class="medium-feed-snippet">Dissecting the Usability, Accessibility, and Ethics of Twitter</p><p class="medium-feed-link"><a href="https://uxdesign.cc/interconnecting-our-world-in-1%CC%B64%CC%B60%CC%B6-280-characters-or-less-e7c9dc391fca?source=rss-93c57afac1d2------2">Continue reading on UX Collective »</a></p></div>]]></description>
            <link>https://uxdesign.cc/interconnecting-our-world-in-1%CC%B64%CC%B60%CC%B6-280-characters-or-less-e7c9dc391fca?source=rss-93c57afac1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7c9dc391fca</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[social-media]]></category>
            <dc:creator><![CDATA[Amy Lima]]></dc:creator>
            <pubDate>Tue, 22 Sep 2020 13:46:55 GMT</pubDate>
            <atom:updated>2020-09-22T17:17:41.885Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[When Assumptions Lead to Failures]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/when-assumptions-lead-to-failures-cb8c82f09726?source=rss-93c57afac1d2------2"><img src="https://cdn-images-1.medium.com/max/1100/1*TPZ-7Mrg8xw1fswJEREFfA.jpeg" width="1100"></a></p><p class="medium-feed-snippet">The Rise and Fall of Rhapsody, the Revolutionary Streaming Service You Probably Never Heard About</p><p class="medium-feed-link"><a href="https://medium.com/swlh/when-assumptions-lead-to-failures-cb8c82f09726?source=rss-93c57afac1d2------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/when-assumptions-lead-to-failures-cb8c82f09726?source=rss-93c57afac1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb8c82f09726</guid>
            <category><![CDATA[failure-stories]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[streaming]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Amy Lima]]></dc:creator>
            <pubDate>Fri, 04 Sep 2020 17:52:46 GMT</pubDate>
            <atom:updated>2020-09-11T06:49:08.003Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What Makes a Product Great?]]></title>
            <link>https://medium.com/design-warp/what-makes-a-product-great-fa799ba6bd94?source=rss-93c57afac1d2------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa799ba6bd94</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Amy Lima]]></dc:creator>
            <pubDate>Sun, 30 Aug 2020 22:53:06 GMT</pubDate>
            <atom:updated>2020-09-24T03:58:57.081Z</atom:updated>
            <content:encoded><![CDATA[<p>Differentiating Between Good and Great Product Design</p><figure><img alt="Photo of someone holding an iPhone against a neon background, taken by Daniel Korpai on Unsplash." src="https://cdn-images-1.medium.com/max/802/1*x_Rm4RZ7eMkddV1cgTgHqg.jpeg" /><figcaption>Image by <a href="https://unsplash.com/@danielkorpai">Daniel Korpai</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>Products are objects, systems, goods, and services that consumers use. Products are all around us: our versatile coffee machine that delivers us our daily caffeine fix before a long day, the mug we use as a vessel for that ritualistic morning brew, our car navigation system that gets us from Point A to Point B, the messaging apps we use to keep in touch with friends and family, the social networks we flock to either for distraction or inspiration, and the dating apps that most typically bring us disappointment (although seldom to the fault of the actual product itself).</p><p>So, if products are an inevitable and integral component of our daily lives, why is it that we hardly even think of them, much less recognize them as such? It is precisely this invisibility that differentiates a good product from a great one.</p><p><strong>Products as an Extension of Ourselves</strong></p><p>Whether we realize it or not, great products are not merely supplements to our lives, providing added value to them by solving specific problems, but are solidifying themselves more each day as extensions of our very being, with the user often not being able to separate themselves from the products they use incessantly.</p><p>Put quite simply, when a product is designed exceptionally, we cannot imagine living without it. This goes beyond simply providing a solution to a problem the user faces; When MapQuest, the first consumer-focused interactive mapping site on the internet launched in 1996, it brought tremendous value to the consumer, empowering them to travel to distant, unknown locations with ease and independence. But MapQuest, although a pioneer in navigation technology at the time, had its limitations: it was a web-based service that relied on either a photographic memory or a printing device to make a significant impact in one’s life.</p><p>With the onset of mobile mapping applications, such as Apple Maps, Google Maps, and Waze in the early 2000s, these barriers were eradicated, and a new phenomenon emerged: a consumer base who simply cannot imagine themselves going through the motions of daily life without such applications, turning to them subconsciously, and relying on them to navigate even to locations they know well — “just in case.”</p><figure><img alt="Google Maps image. An everyday interaction with technology." src="https://cdn-images-1.medium.com/max/1024/1*1uzQOuirqHsbj8B4ORP8UQ.jpeg" /><figcaption>Image by <a href="https://unsplash.com/@hjkp">Henry Perks</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p><strong>Products I Can’t Live Without (Even Though I Wish I Could)</strong></p><p>Like most of us, I am (somewhat) addicted to at least one social media network. Between the top two culprits, Instagram is my preferred drug of choice, taking up an undoubtedly shameless amount of time of my day, if only I had the humility to actually look up my logged screen time on the app.</p><p>The app’s design feels seamless, with every action icon positioned intuitively, and gestures such as double tapping to like or swiping left or right to toggle between screens feeling like second nature. Its features rapidly evolve with the nature of the product itself and its users’ behaviors — the “remove follower” option as a softer alternative to blocking a profile and “mute account” as a sort of incognito quasi-unfriending, for example, are two psycho-behavioral nuances in social media that were sorely needed, not openly vocalized, and an attention to detail that makes me impartial to this product in particular.</p><p>My daily journey with Instagram starts exactly how it began when I first downloaded it: I’m a little bored, a little curious, and am hoping to just look at something pretty or interesting for a while. But then, thanks to its highly intelligent algorithm, my mission on the app toggles to functional: I find new workout tutorials to incorporate into my routine, creative cooking recipes to challenge myself with, and snippets of micro-poetry, art, and design to keep me inspired, all of which I can save into distinct folders, that have become a sort of digital representation of the compartmentalizations in my brain: “Cute Dogs,” “SNAX4LIFE,” “#Fitness,” “UX Inspo,” “Art + Tattoos + Quotes.” Yep, that about sums it up.</p><p><strong>What Attracts Me to Product Design</strong></p><p>I’m ceaselessly fascinated with the innovation and value added new technologies in products tend to bring. Through user observation, research, testing, and experimentation, (great) Product Designers can identify and solve problems the user isn’t even aware they have yet, or, within a larger problem they’ve already solved, pinpoint a smaller, more nuanced problem, and solve that. I’ve seen great product design keep my immigrant family in touch across continents, facilitate the lives of my aging parents with the ease of a button, and bring welcomed joy and distraction to my peers and I when we’ve needed it most.</p><p>That magical “Aha!” moment of suddenly introducing more efficiency, ease, or simple delight into your life you either never knew you needed or never imagined you’d be able to attain is what keeps me hooked on great product design, and inspired to be a valuable contributor in the field myself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa799ba6bd94" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-warp/what-makes-a-product-great-fa799ba6bd94">What Makes a Product Great?</a> was originally published in <a href="https://medium.com/design-warp">Design Warp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>