<?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 Rosenbaum on Medium]]></title>
        <description><![CDATA[Stories by Amy Rosenbaum on Medium]]></description>
        <link>https://medium.com/@amy.s.rosenbaum?source=rss-64c41b04d539------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uBxpIl3A56TtK0e8pcYeCQ.jpeg</url>
            <title>Stories by Amy Rosenbaum on Medium</title>
            <link>https://medium.com/@amy.s.rosenbaum?source=rss-64c41b04d539------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:31:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amy.s.rosenbaum/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[UX in real life: how the double diamond helped me deliver a wedding toast]]></title>
            <link>https://uxdesign.cc/ux-in-real-life-how-the-double-diamond-helped-me-deliver-a-wedding-toast-37a06be4666?source=rss-64c41b04d539------2</link>
            <guid isPermaLink="false">https://medium.com/p/37a06be4666</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Amy Rosenbaum]]></dc:creator>
            <pubDate>Wed, 31 Jul 2019 23:44:24 GMT</pubDate>
            <atom:updated>2021-10-26T02:54:43.431Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How the double diamond helped me deliver a wedding toast — a UX case study</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eivBInYRC_7BJsaJO7h1PA.png" /></figure><p>I recently had the honor of giving a toast at the wedding of two dear friends, Serena and Chris. I was touched to be asked to contribute to one of the most meaningful days of their lives as a couple, but I was also slightly terrified. It was my first time ever putting together a toast for a wedding, and though I have no fear of public speaking, the stakes were incredibly high. My friends would have these memories forever, so I wanted to absolutely crush it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*xrp1i6IA1m-B7UQlXzRulw.png" /></figure><p>This toast, like my friends, would be a little nontraditional. I received my brief two weeks before the wedding: “Something Chris and I both deeply love and appreciate are words, memories, and stories from our loved ones, but we know that nobody wants to sit through a million speeches…So, we came up with the idea of collecting lots of people’s stories and having a conglomerate friend’s speech.”</p><p>I thought this idea was awesome, and as I started to problem-solve, it hit me: I had a UX project on my hands. I didn’t need to be nervous because there was a process I could use to get it done — the Double Diamond, commonly known as</p><p><strong>&lt; DISCOVER | DEFINE &gt; &lt; DEVELOP | DELIVER &gt;</strong></p><p>I had two weeks, the length of a design sprint, so I got started immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Q-AIr9ZO5xCJ48TnpJSYg.png" /><figcaption>Sometimes the steps are called different things, but it’s all the same process!</figcaption></figure><h3><strong>DISCOVER</strong></h3><p>UX is all about the users, which meant I needed to focus on them first. Serena and Chris were my “clients” — both users and stakeholders — but I needed to keep two other groups in mind: all of the people I was soliciting toasts from and all of the people at the reception who would be listening to my speech.</p><p>The first group I’d be dealing with was Chris and Serena’s friends and family, the collective in my collective toast. I approached the email to them like a survey, carefully designing it to achieve my goals. Since people tend to procrastinate or opt out when they feel overwhelmed, I wanted to keep things simple by setting three constraints:</p><p><strong>1Deadline</strong>: I gave everyone a week to respond, leaving me a week to synthesize, write, edit, and practice the actual speech.</p><p><strong>2 Word Count</strong>: I asked for 25 words or less per submission, which I hypothesized would<br> a. lower the user effort in replying<br> b. allow for maximum inclusion of user toasts<br> c. keep the final run time of my speech down</p><p><strong>3 Theme</strong>: By providing a unifying prompt for the toasts, I hoped to spark user creativity and save them the effort of developing their own theme. (Plus, it would be easier for me to turn into a cohesive speech!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*tVaLEGboko9dhZG5-t59Fw.png" /></figure><p>The first prompt I thought of was “advice on how to have a happily married life,” which I felt would be meaningful to Serena and Chris. But I realized this theme left out people who weren’t married, so I wanted to provide a second choice: “how you knew Serena and Chris were right for each other.”</p><p>My two prompts settled, I thought about what other information I might need to make the speech work. I decided to ask respondents to describe their relationship to the couple, which would give me context in framing their toasts. Serena then sent out my “survey” in a wedding update email, and with a week to wait, all I could do was hope and trust the process!</p><p>I was elated when answers started rolling in, but I did need to account for user error. Some people forgot to include their relationship to the couple, so I followed up with them. Some people wrote longer than 25 words, so I edited and relaxed my criteria as necessary. When the deadline hit, I knew I had some great content, and I couldn’t wait to start my synthesis.</p><h3><strong>DEFINE</strong></h3><p>I received 15 submissions in total, 10 pieces of advice on having a happy marriage and 5 stories about Chris and Serena’s relationship.</p><p>When I came up with the two prompts, I figured the one that received more responses would become the theme of the entire speech. But just like in an actual UX project, I had to let go of my assumptions and let my research findings determine the design of the product. I truly loved submissions from both prompts, so I made the call to include both in the final toast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/649/1*n7w5b-rjnkUSTMGfiHXg0g.png" /></figure><p>Of the 8 toasts I choose, there was equal representation for the bride and groom, 4 from Chris’ side and 4 from Serena’s side. I achieved near gender-parity and a good sampling of friends from all areas of their lives, including childhood, college, graduate school, and their professional lives. Though I prioritized people who weren’t giving in-person toasts, I did include one sibling, Chris’ brother and best man. (I was also happy to pay homage to Serena’s heritage with 8 toasts, as 8 is one of the most auspicious numbers in Chinese culture.)</p><p>With my submissions chosen, I sent out an email to ward off hurt feelings, assuring the respondents that all of their toasts would be sent to Serena and Chris post-wedding. All that was left to do was to bring everything together.</p><h3><strong>DEVELOP</strong></h3><p>Sometimes when I sit down to write, I get anxious about finding the right way to express what I want the reader to know. However, treating this toast as a UX project took some of the anxiety out of it. I had done my research, which had given me my content, and I knew very deeply how I wanted the users (both the wedding couple and the audience) to feel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*q_2Z8Xwnnh733UifO6dSeA.png" /></figure><p>The first thing I tried to do was give the listeners context, to tell people what and why. The wedding toast was not in a typical format, and I had to prime the audience to receive the rest. To me, this format spoke to my friends’ desire for inclusivity — both as individuals and as a couple — so I framed the collective toast as a way for everyone to feel loved and included.</p><p>My next challenge was to order the submissions, to make a narrative from the collective. I shuffled the prompts within their respective groups to begin, finding the toasts that related or responded to each other before crafting a through line. I made sure to give context to each contributor, outlining their relationship to Chris and Serena for the audience’s benefit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*0bGYsT4nNGLq30GQlulnDA.jpeg" /></figure><p>With my core shaped, I started writing my transitions. Only then did the relationship between my two themes (“how you knew Serena and Chris were right for each other” &amp; “advice on how to have a happily married life”) become clear. I was talking about their past and their future, their beginning and their continuance: “With beautiful memories from your past and wise advice for your future, you will find your own way to a long and happy marriage, with help from each other.”</p><p>As I came to the close, I also wanted to reference the speech’s source and the reason for its existence: the collective audience. “Of course, you will always have this wonderful community of family and friends to lean on, to ask advice from, and to share in the life you’re making together.” Finally, the actual toast! “Congratulations on taking this first step. As their community, let’s raise our glasses to Serena and Chris.”</p><p>The speech had been written, but my work was not over. I made sure to time and further edit it, aiming for my sub-4-minute goal. I practiced out loud and listened to see if my words could be easily understood. (Speaking aloud also made me realize I needed some name pronunciations, which my respondents provided with phonetics, sound-alikes, and even recordings.) Since UX is all about iteration, I practiced over and over, hoping to know the words by heart.</p><h3><strong>DELIVER</strong></h3><p>The wedding day arrived, and I realized that there was one aspect of the Double Diamond method I’d overlooked. In lean and agile UX, you can always start your process over and iteratively work to make your product better. For me though, I only had one shot to deliver this speech.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*zsjTyLFONs-_sHk4rFO9BQ.png" /></figure><p>The morning of the wedding, I woke up to find that I had totally lost my voice. I had been sick earlier that week, but since I felt better going into Friday, I wasn’t worried about protecting my voice. Saturday morning, I could barely squeak out a sound. I immediately put myself on hot tea and vocal rest, relying on a particularly animated game of charades to communicate with my friends for most of the day.</p><p>At the ceremony, some of my worries fell away. The priest, who had gotten to know my friends during their wedding planning, seemed to echo some of the submissions I incorporated into my toast. Getting this independent validation of my research from her, I felt like I had chosen the words and themes that represented Chris and Serena well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*06KAz4t1BK4SU5YFAmxCAQ.jpeg" /></figure><p>I started warming up my voice during cocktail hour. I was a little husky and nowhere near full volume, but I could get it done. (It helped that their signature cocktail had three ingredients that improved my vocal quality: whiskey, honey, &amp; lemon.) When I picked up the mic, I breathed deeply and spoke slowly, relying on the muscle memory that comes from rehearsal.</p><p>Though I was directing my speech to the newly married couple, I was thrilled by the audience reaction — some laughs, awws, and even cheers as they found themselves represented in the toast. But the most important reaction came from the people in front of me: Serena and Chris, who received a chorus of words from their loved ones on a day that celebrated love and community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*ddAtv1tXWz2nNviPn7Yvfg.png" /></figure><p><strong>FINDINGS/NEXT STEPS</strong></p><p>Serena initially asked to me to work on this toast “because of your literary background and your love of words and people and squishy feelings.” For all those reasons and more, I was proud to claim the role of “speech doula.” But I know that my UX skills were the essential ingredient to my success.</p><p>UX is ultimately about problem-solving based on needs and constraints, and it’s taught me how to think through a project strategically. In a perfect world, would I have liked more time or more submissions? Maybe. But my process got me to the solution, and the joy of my friends was worth every second of work. I loved tackling this nontraditional UX project, and I’m looking forward to many more to come — to a long and happy UX career!</p><blockquote>Thanks for reading! I’m currently looking for UX opportunities, so if you’d like to work with me, feel free to check out my portfolio (<a href="https://www.amyrosenbaum.com/">amyrosenbaum.com</a>) and get in touch!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37a06be4666" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-in-real-life-how-the-double-diamond-helped-me-deliver-a-wedding-toast-37a06be4666">UX in real life: how the double diamond helped me deliver a wedding toast</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t ignore your “crazy” ideas: how I made my first UI animation]]></title>
            <link>https://uxdesign.cc/dont-ignore-your-crazy-ideas-how-i-made-my-first-ui-animation-604a97f6eeb7?source=rss-64c41b04d539------2</link>
            <guid isPermaLink="false">https://medium.com/p/604a97f6eeb7</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Amy Rosenbaum]]></dc:creator>
            <pubDate>Wed, 13 Feb 2019 04:13:09 GMT</pubDate>
            <atom:updated>2019-07-29T00:54:58.371Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*5bJuRJh-rr3-5rTyYvpXKw.png" /></figure><p>One of the most daunting parts of starting a career in UX is building your portfolio website. Presenting the projects you’ve worked on — balancing form and function in a way that is both comprehensive and engaging — is an intimidating task with almost limitless possibilities. How do you even begin to create a website that perfectly encapsulates who you are as a designer?</p><p>Needless to say, my classmates and I were feeling the pressure mount as we approached the end of our UXDI course at General Assembly. The issue of our portfolios loomed on the horizon, but as always, our ever-patient instructors had <a href="https://uxdesign.cc/unraveling-a-complex-ux-problem-how-a-greek-myth-helped-me-conquer-information-architecture-743ebd7d0ea">a plan to help us</a>. We revisited an exercise that we learned at the very beginning of the course: <a href="https://www.iamnotmypixels.com/how-to-use-crazy-8s-to-generate-design-ideas/">Crazy 8s</a>.</p><p>The point of Crazy 8s is to sketch 8 ideas in 8 minutes, trusting your instincts and working fast to meet your goal. As someone who tends to work on the slower side, Crazy 8s feels freeing…The ideas don’t have to be perfect; they just have to be down on paper when the timer goes off.</p><p>In our portfolio round of Crazy 8s, our instructors made the goal of imperfection even more explicit: We needed to sketch bad ideas of what should be in our portfolio and present them to a classmate. A lot of laughter and truly terrible ideas followed, but when I finished, one sketch stuck out:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XWsaTG8I-3gJX18fZLWJWg.jpeg" /></figure><p>Something about this marquee concept truly tickled my fancy, and when the course ended, I couldn’t stop thinking about it. Since I wanted to work on my UI skills and experiment with animation, I figured I’d give in to my “crazy” idea and turn it into my next project.</p><p>The first part of the sketch I wanted to finesse was “HIRE ME.” I knew I could come up with a phrase that better represented my job search — a less desperate, more deliberate vibe. I settled on “LET’S DO GOOD WORK TOGETHER” and immediately wanted to see my new motto in lights.</p><p>I decided to undertake the animation in <a href="https://www.flinto.com/">Flinto</a>, which has emerged as my prototyping software of choice. (I’d taught myself how to use Flinto for my fourth GA project, so I felt pretty familiar with its capabilities.) I envisioned a way to make a blinking effect in its Behavior Designer, but I needed a vessel for the lights. The fastest way I could think to accomplish my task was to download a <a href="https://www.urbanfonts.com/fonts/Marquee.htm">marquee font</a> and animate from within the text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*8Rn6hnZMH2otFdC7sdRfKA.gif" /><figcaption>Attempt #1: Not exactly what I had in mind.</figcaption></figure><p>As a budding UX designer, one of the hardest parts of the creative process is getting the image on screen or paper to match the one in my head. For me, this first draft was a total flop. The timing was off, the contrast was poor, and though the animation blinked, it didn’t really read as a marquee. I soon realized that if I wanted to make this project as fun as it was in my mind, I’d have to put in some serious work.</p><p>So I went back to the drawing board and took a look at real-world examples of marquees. It was here that I spotted my main problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*LOu_Sknph89n6kjUtC7O5Q.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*uAv37QmmRtiqs4nEx5MzAA.gif" /></figure><p>To make my design a true marquee, I needed my lights to have a stronger sense of movement — to run in a continuous path of motion and not just blink back and forth.</p><p>My next step was a Google search for pared-down design inspiration, something I could plausibly mock up as a vector in Sketch. For the text, I wanted to recall the style of <a href="https://www.google.com/search?q=light+board+letters&amp;source=lnms&amp;tbm=isch&amp;sa=X&amp;ved=0ahUKEwiRgNP50bfgAhUqnuAKHT59DJIQ_AUIDygC&amp;biw=1279&amp;bih=673">light board</a> letter signs with a bold yet compressed font: Myriad Pro Bold Condensed. Thinking ahead to the animation, I drew an even number of bulbs to illuminate: 50.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/581/1*Lx1sI_b9zbAeQ7lnznujjw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*RILD_4KJuhRnY6c-wj-Sww.png" /><figcaption>My inspiration and the vector that followed</figcaption></figure><p>My vector was complete, but it looked lifeless. If I animated the design as it was, I’d only have a slightly elevated version of my first attempt. My next idea was to make the light bulbs feel round with a radial gradient, contrasting the “on” and “off” bulbs with a yellow tint.</p><p>Though I’d accomplished what I wanted with the 3D bulbs, I had no idea how to achieve a more illuminated effect. <a href="https://www.youtube.com/watch?v=YAXtnFALh_0">YouTube tutorials</a> proved helpful, introducing me to blurs. I played around with adding the blur on top of the yellow bulbs, which now emitted a lovely soft glow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*4MDGrDELkP7IwNkzonU7MA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*FZYlhWDx1VyYQV1_qOoB9Q.png" /><figcaption>Let there be more realistic-looking light (with a blur effect)!</figcaption></figure><p>With the bulbs looking lit, I turned my attention to the letter signs, which were falling a little flat. YouTube once again delivered with tutorials on <a href="https://www.youtube.com/watch?v=IbtFSbUkw7k&amp;t=3s">drop shadows</a>. I added a horizontal drop shadow along the letter rails, to give the appearance that the letters were being held in place, and a darker vertical drop shadow between the words, to pop the letters off from the background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*hyOTxsiaE7Mam-ozVj4FXw.png" /><figcaption>A closer look at the drop shadows, gradients, and blurs. I covered the shadows that bled into other elements with white rectangular “patches.”</figcaption></figure><p>After finalizing the look of my starting frame, I had to create the rest of the Sketch artboards to export to Flinto. I knew I had to cycle the lights around the marquee frame by frame, which involved turning the lights and the blurs on and off as necessary.</p><p>I thought I’d be done after a cycle of 5, but when my initial animation jumped, I realized I actually needed a cycle of 10 to have the lights end smoothly where they began. It took a lot of tedious fiddling to get to the final frames (20 changes each across 10 frames, for 200 individual changes in total), but I cranked up some good music and worked it out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*QuS2qqGyI8siZlpcX8-SaQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*tme55nG63BC2mVxAGGYTpw.png" /><figcaption>The first and second frames, with the light bulbs advancing by one place</figcaption></figure><p>Once I’d linked all 10 frames to transition automatically in Flinto, I experimented with the timing of the animation. 100 milliseconds between frames provided the quickness I was looking for.</p><p>My last challenge was the make the gif loop seamlessly, an exercise in timing, editing, attention, and patience. Flinto has built-in recording capabilities at 50 fps (frames per second), but for some reason, I couldn’t get the gif to line up correctly. A friend suggested that I try <a href="https://getkap.co/">Kap</a> to record my screen, and at 30 fps, the gif finally looped smoothly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*MpZuqMjudb_t-SX0P_870w.gif" /><figcaption>The final gif!</figcaption></figure><p>Though I can still see some imperfections in my final gif (an inexplicable flicker on the lower-mid letter rail and a misplaced white patch at the end of the same line), I’m ultimately thrilled with how this project turned out.</p><p>Since <a href="https://www.amyrosenbaum.com/">my portfolio</a> is still a major work in progress and my job hunt is still ongoing, I understand how this side project could be considered a waste of time. To me though, joy and passion are vital parts of my UX process. Taking the time to develop an idea — one that made me laugh, made me curious, and made me excited to learn more — is what <a href="https://medium.com/nyc-design/curiouser-and-curiouser-my-journey-down-the-ux-rabbit-hole-65ffcf570bc">my UX journey</a> is all about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XWsaTG8I-3gJX18fZLWJWg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*MpZuqMjudb_t-SX0P_870w.gif" /><figcaption>The full evolution of my “crazy” bad idea</figcaption></figure><blockquote>Thanks for reading! I’m currently looking for UX opportunities, so if you’d like to work with me, feel free to check out my portfolio (<a href="https://www.amyrosenbaum.com/">amyrosenbaum.com</a>) and get in touch!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=604a97f6eeb7" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/dont-ignore-your-crazy-ideas-how-i-made-my-first-ui-animation-604a97f6eeb7">Don’t ignore your “crazy” ideas: how I made my first UI animation</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unraveling a complex UX problem: how a Greek myth helped me conquer information architecture]]></title>
            <link>https://uxdesign.cc/unraveling-a-complex-ux-problem-how-a-greek-myth-helped-me-conquer-information-architecture-743ebd7d0ea?source=rss-64c41b04d539------2</link>
            <guid isPermaLink="false">https://medium.com/p/743ebd7d0ea</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[general-assembly]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[uxdi]]></category>
            <dc:creator><![CDATA[Amy Rosenbaum]]></dc:creator>
            <pubDate>Sun, 25 Nov 2018 16:56:46 GMT</pubDate>
            <atom:updated>2019-07-29T00:54:02.018Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*67PEYVjWvzfdvtW-j-htSw.jpeg" /></figure><p>The first time I knew I made the right decision to attend General Assembly was five days before my UXDI course started. I had been riding a rollercoaster of emotions the whole month leading up to this moment, whipping wildly between the high of starting something new and the low of leaving an industry I called home for seven years. In the general anxiety of a major life change, I suppose I was looking for a sign I was doing the right thing. I found it in the welcome email from our instructors:</p><blockquote>“It is our pleasure to welcome you to <strong>UXDI October 2018</strong> (aka <strong>UXDI Gordian</strong>)!”</blockquote><p>Seeing those words, my myth-loving heart thrilled. If my teachers valued the metaphor of the Gordian Knot (and meaningful metaphors in general), they were my kind of people, and I was going to be OK.</p><p>Like many Greek tales, the story of the Gordian Knot starts with a legendary task: unraveling an impossible knot. Many had tried and all had failed, but eventually, news of the Gordian Knot reached Alexander the Great. An oracle prophesied that anyone who could undo the Knot was destined to become the ruler of all Asia, so Alexander decided he needed to succeed.</p><p>When Alexander the Great attempted to untangle the Knot, he failed the same way people before him did. But then he did something different. He stepped back from the problem, drew his sword, and cut clean through the Knot. With a new perspective and a little creativity, the Gordian Knot was solved.</p><p>I’ve leaned on this story throughout the course (despite its problematic justification for conquering Asia), and I certainly needed it for P3.</p><h3><strong>CLIMBING THE MOUNTAIN</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FPjfu59mFtUBgTjrF4QYsg.jpeg" /></figure><p>GA’s third project (P3) is commonly referred to as “the Mountain.” It comes at the midpoint of the course, arriving too quickly after two stressful, strenuous projects. Sleep-deprived and slightly delirious, we kicked off our lessons and started climbing.</p><p>The focus of P3 is Information Architecture (IA), which Wikipedia says is “the art and science of organizing and labeling websites…to support usability and findability.” To test our IA skills, we would be examining the <a href="https://www.stjude.org/">St. Jude Children’s Research Hospital website</a> as a case study and evaluating it using several different methods.</p><p>The deliverables for our previous projects had been assigned in a linear fashion, so each new part of the project built on what we had just completed. But the deliverables for P3—a current sitemap, a revised sitemap, a task flow, a user flow, a competitive/comparative feature analysis, a closed card sort, and an open card sort—were all due together, and as we’d soon find out, they were horribly entangled with each other.</p><h3><strong>EXISTING SITE MAP</strong></h3><p>I made a plan of action to work through the deliverables, starting with the existing site map. It felt like a solid foundation, as the research I’d do for it would inform how to tackle the rest of the evaluations.</p><p>Site maps have a logical structure based on hierarchy. Like family trees, they show the relationship of pages to each other, “parent” to “child.” For me, they also brought back pleasant memories of biology and taxonomy, where Latin names told a story of discovery and relationships between species.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*cFkzDsJ8yUd5h3JadJXYwA.png" /><figcaption>Keep an eye on the two right-most categories: “Get Involved” and “Ways to Give”</figcaption></figure><p>But the St. Jude site was a much different beast than the straightforward e-commerce site we’d mapped in class. The website was complex and sprawling. Two sections were completely entwined together (“Get Involved” and “Ways to Give”) in a way that didn’t make sense to me. It was difficult to get a clear sense of hierarchy from the navigation, which meant I had to map the site by diving into the interior pages and checking out the URLs.</p><p>I felt shaky about my foundation, so it was hard to move forward with the next part of the project. But I knew that, with our one-week deadline, getting stuck for too long on any piece of the project meant failure. I pushed on out of necessity, resolving to double back when I could.</p><h3><strong>COMPETITIVE/COMPARATIVE FEATURE ANALYSIS</strong></h3><p>After the snarl of the site map, it was a relief to work on the competitive/comparative feature analysis. The answers came more easily, as I was somewhat prepared by my previous sales and marketing experience.</p><p>I picked three competitors for St. Jude fairly quickly, selecting non-profit research hospitals with a national reach (two of which specifically treat children): Shriners Hospitals for Children, Mayo Clinic, and Children’s National Health System.</p><p>The comparator was harder to pin down. I couldn’t figure out an indirect competitor to a research hospital, so I looked at the other piece of St. Jude’s business model: their fundraising. Then it hit me with the force of <a href="https://people.com/celebrity/sarah-mclachlan-aspca-commercial-singer-reveals-how-she-really-feels/">a Sarah McLachlan song played over a sad commercial</a>: the ASPCA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sWAos5cD2v-CKJ7x4MbwYQ.png" /><figcaption>It sounds a little far-fetched, but the proof is in the website structure.</figcaption></figure><p>Once I had my competitors nailed down, I picked out ten site features, laid out a comparison chart, and finalized this deliverable with confidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kZDsvnQzeHPqMu_tehYR5Q.png" /><figcaption>Four of the ten features I analyzed.</figcaption></figure><h3><strong>TASK/USER FLOWS</strong></h3><p>Fresh off of my feature analysis, I was excited for my task and user flows.</p><p>Flows appealed to the younger version of me—the kid who made complex legends for her treasure maps and obsessed over flowchart quizzes in teen magazines. I also loved their sequential, detailed logic, which felt like the adult version of <a href="https://www.usertesting.com/blog/5-user-research-lessons-i-learned-from-making-pbj-sandwiches/">the PB&amp;J test that rocked my world in elementary school</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*7v9AAzhI032d3dgbKCqOgA.png" /><figcaption>A task flow is the best path for a user to find the information they’re searching for.</figcaption></figure><p>Having spent plenty of time investigating the St. Jude site (and the rabbit holes I could go down to find information), I picked a task that was relatively straightforward: “Find resources to help you plan a fundraiser at your office for your coworkers”</p><p>Unfortunately, “relatively straightforward” on the St. Jude site meant a roundabout path for resources, heading off the site and into my Gmail account before being directed back to the site. The user flow got even more interesting, as there were several ways to get to <a href="https://www.stjude.org/get-involved/workplace-giving/workplace-fundraisers.html">the form that was essential to obtaining the fundraising information</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*mDTa2PTxjPQA9aCUF6xteA.png" /><figcaption>A user flow shows all of the possible paths a user can take to get to the information they’re looking for. The end of this user flow is picked back up in the task flow above.</figcaption></figure><p>With my flows finished, I was still puzzled by the overlap between the “Get Involved” and “Ways to Give” sections. I hoped card sorting could illuminate whether this jumble was as big a problem for other users as it seemed to me.</p><h3>CLOSED AND OPEN CARD SORTING</h3><p>Card sorting was the deliverable I was most worried about, though it turned out to be the most enlightening and the most fascinating.</p><p>When I began prepping my sort, I was skeptical that five different people, all with their own mental models, could give me usable trends. But this step definitely turned out to be one of those “<a href="https://medium.com/nyc-design/curiouser-and-curiouser-my-journey-down-the-ux-rabbit-hole-65ffcf570bc">trust the process</a>” moments.</p><p>Picking representative cards for such a large website was a little tough, but I stuck to about thirty cards. For the closed sort, users would place the cards the way they’d expect to find them under the six existing primary navigation categories. For the open sort, users would group the cards and name their new categories themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cz6DbikM6eLyDpYhL5L3tg.png" /><figcaption>The top level categories and the representative cards in a closed sort.</figcaption></figure><p>Since I didn’t have ready access to medical professionals for my card sorts, I picked people who had jobs that involve categorization, prioritization, and looking for themes (editors, literary agents, and a product manager). For the open sort, I prioritized people who were decisive and weren’t rushed for time, as I thought that open sorting could be more stressful than closed sorting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b9l1xL_P7kipIGPiDznfug.jpeg" /><figcaption>An open card sort card where the user made a new category called “Fundraising” (and thought about Rihanna).</figcaption></figure><p>Once I completed all six sorts, I synthesized them into a large Excel chart. The bright red areas in both sorts (where all three users placed the cards incorrectly) were ones I wanted to pay attention to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aj_iwrUVsIo2SLXUd5vFyA.png" /><figcaption>The bold red means all 3 users put the cards in the wrong place, which indicated a problem to me.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tc-3CA7EsdsC4OqP0MZecw.png" /><figcaption>Much less bold red! And all three users combined the “Get Involved” and “Ways to Give” in one category.</figcaption></figure><p>As displayed by the color-coding, the closed sort users mostly matched the cards under About Me, Care &amp; Treatment, Research, and Training to their original places on the St. Jude site. Open sort users categorized their cards similarly to the existing site, with two major changes: enmeshing “Get Involved” with “Ways to Give” and eliminating “Research” completely.</p><h3><strong>REVISED SITE MAP</strong></h3><p>Card sorting had given me data for my revised site map, but now I had to decide what to do with that data.</p><p>Based on the closed sort success rate of users matching cards to the original categories, I kept the existing primary navigation largely the same. Still, I knew I had to address the “Get Involved” and “Ways to Give” sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/565/1*vukIrVeq8i7wLyDQaCNJvw.png" /><figcaption>The revised site map, now with five primary navigation categories.</figcaption></figure><p>Since users strongly intertwined “Get Involved” and “Ways to Give” in both the closed and open sort, I combined them in my revised site map. I took the name for the new category (“How to Help”) from one of my users. I also accepted my other open users’ subcategories of “Donations,” “Fundraisers,” and “Other Ways to Get Involved,” as they all made distinctions between ways to give.</p><p>I also chose to move “Affiliate Clinics” from “Care and Treatment” to the “About Us” section, as all six users miscategorized it.</p><p>One change I decided not to make was to the “Research” section, which was not represented in any user-made open sort categories. However, none of my card sort users were in medical or scientific fields, which is the segment of users the Research section serves. I think asking users in the medical field to name categories would have yielded different results, so in the absence of real data, I left the category as is.</p><h3>UNTYING THE KNOT</h3><p>After I turned in all of my deliverables, I was both relieved and elated to have climbed the P3 Mountain. (I had emerged mostly unscathed, aside from a slight St. Jude website Stockholm Syndrome.) I learned so much about the art and science of IA, and I surprised myself with how much I could accomplish using the marriage of both my soft and hard skills.</p><p>While P3 was a tangled mess at times, I kept the Gordian Knot mindset with me: remembering to step back from the immediate problem and look at something seemingly impossible from a different perspective. Though I have so much more to learn (and I wouldn’t trust myself with a sword), I now know that I can use patience, creative thinking, and the right UX tools to unravel even the knottiest problems.</p><blockquote>Thanks for reading! I’m currently looking for UX opportunities, so if you’d like to work with me, feel free to check out my portfolio (<a href="https://www.amyrosenbaum.com/">amyrosenbaum.com</a>) and get in touch!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=743ebd7d0ea" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/unraveling-a-complex-ux-problem-how-a-greek-myth-helped-me-conquer-information-architecture-743ebd7d0ea">Unraveling a complex UX problem: how a Greek myth helped me conquer information architecture</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Group projects, stress, and collaboration in UX: what makes a good group?]]></title>
            <link>https://uxdesign.cc/group-projects-stress-and-collaboration-in-ux-what-makes-a-good-group-591942856bac?source=rss-64c41b04d539------2</link>
            <guid isPermaLink="false">https://medium.com/p/591942856bac</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[general-assembly]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Amy Rosenbaum]]></dc:creator>
            <pubDate>Sun, 04 Nov 2018 22:39:37 GMT</pubDate>
            <atom:updated>2019-07-29T00:57:44.251Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Sv5g31Ri4ZLdQoPey45kw.jpeg" /><figcaption>Yes, this is a group of puppies. It’ll make sense later.</figcaption></figure><p>It’s a phrase that can strike fear into the heart of even the most ardent extrovert: “Group Project.” Those two words conjure up an avalanche of memory and feelings, the remnants of past group projects back to haunt us:</p><blockquote>Who’s in my group? Are they going to be nice? How do we divide the work? Am I going to have to do all the work? What if we disagree on something small? What if we disagree on something BIG? What if they think my ideas are stupid? Oh no, oh no, oh no, I hope this is going to work.</blockquote><p>We all knew this was coming. Collaboration is an essential part of the work UX designers do, and the majority of GA’s UXDI curriculum is designed around group projects. But knowing and doing are two different things, and we still had no idea what we were in for.</p><h3><strong>BRINGING US TOGETHER</strong></h3><p>The first thing all four of us did together was a group stand-up, where we went through a list of questions provided by our instructors. Some of the questions we answered were logistical, and some required us to dig deeper into self-awareness:</p><blockquote>What are your strengths and weaknesses? <br>How do you prefer to resolve conflict and receive feedback? <br>When and how do you want to check in with each other?<br>What can you teach and what do you want to learn?</blockquote><p>I found this exercise incredibly valuable, as it helped us open up to each other and navigate some potential landmines upfront. It also kept us accountable later on, as we could use what was said in the stand-up as a baseline for our group. Moving forward, I know stand-ups will be an essential part of my UX group work toolkit.</p><p>To me, another essential part of creating a group is naming it, and my teammates were kind enough to humor me. We went with “Pegasus,” after we rejected the “<a href="https://library.gv.com/hiring-a-designer-hunting-the-unicorn-ec8f3a2ebd78/#934e">UX Unicorn</a>” label.</p><p>Armed with self-knowledge and our name, we immediately jumped in to scheduling and logistics. We had a lot of deliverables due in a short amount of time, and taking into account our separate commitments over the weekend, we had to start right away.</p><h3><strong>HOW WE BEGAN</strong></h3><p>We were tasked with designing a responsive website, which is a website that renders smoothly on both mobile phones and desktop/laptop computers. Instead of giving us a problem to solve with our site, our instructors assigned us a broad topic (Health) and told us to figure out who needed help in that space. We decided to narrow our focus to mental health and moved to the second piece of the puzzle: finding people to interview.</p><p>Given our tight timeline, we knew that the most accessible and willing users were our fellow GA students. Since they might be uncomfortable discussing “mental health” with us, we shifted our project topic to “stress” and sent out a screener survey to qualify participants. We looked for certain intersecting trends in the responses, which narrowed our pool of thirty respondents to nine. After asking about availability, we ended up with four user interviews.</p><p>I absolutely geek out over the UX research process — finding the right people to interview and asking them the right questions — so I was pleased to conduct our user interviews. In these interviews, the researcher and the user form a group of two, with the researcher actively listening to what the user is telling them. Answers can be given directly and indirectly, verbally and through body language, so it’s the researcher’s job to work out the subtext and get to the user’s truth.</p><p>One of the most interesting things I heard in our interviews was how users talked about their favorite stress-relieving websites: YouTube and Instagram. Though all our users could easily tell me who they watched and what cute animals they followed, they described the content in a largely dismissive way:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*_bxaMUe8dWG2il_wyIa9lQ.jpeg" /><figcaption>Size of words indicate frequency of use across interviews.</figcaption></figure><p>So I asked “why?” about these word choices. User 3, who previously said YouTube was her “best form of therapy,” elaborated:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*UrilQLYd45bbwm55NEozvA.jpeg" /></figure><p>While users said YouTube and Instagram content didn’t treat their underlying stress, all of our users admitted that it was ultimately helpful as a way to reset their mind. I felt this idea was something to explore, so I couldn’t wait to go back to my group to synthesize the rest of the interviews.</p><h3>SEARCHING FOR OUR SOLUTION</h3><p>We regrouped after the weekend to uncover more themes from our user interviews, using an affinity map as our guide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5RrFcaOn3MA4c0aGm5n6g.jpeg" /><figcaption>Part of Triceara with part of our affinity map</figcaption></figure><p>The groups of post-it notes that clustered on our affinity map informed us visually that we were on to something. By the time we had finished, our users’ journey through stress had emerged:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*kxBH9YUIZ4iO3Qf4iOuALg.jpeg" /></figure><p>We spotted commonalities in what made our users stressed (“stressors”), but we also found a pattern in how they knew they needed to de-stress. Since all of our users recognized their personal physical or emotional reactions to stress, they knew when they needed to take a break from their current situation to reset their mind. We called this moment their “trigger point.”</p><p>Our users also expressed a desire to manage their stress in a healthy or mindful way — going to the gym, yoga, running, walking, meditation, or talking with someone they trust — but sometimes, it was hard to find the time or the motivation to do these things. So they turned to something quick and easy: YouTube and Instagram.</p><p>We grouped these insights together when we crafted our persona, Peggy Sasse. Her journey map below replicates our users’ pattern of stressors leading to a trigger point, followed by stress-relief and feeling better. This map was useful in plotting out touchpoint opportunities for our website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*bUEpSyUQWZlhpzm-Kt3k9A.jpeg" /></figure><p>At last, we had found our problem space and a way we could help.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*JTLjsJBbJqCUMuqhre6inA.jpeg" /></figure><h3><strong>OUR GROUP BREAKTHROUGH</strong></h3><p>We started coming up with solutions, using a design studio and a MoSCoW map as a way to brainstorm and prioritize features. In my first round of sketches, I was thinking about how to present users with stress-relieving content while giving them back time and control. I wanted to move away from the endless scrolling and endless suggested content of Instagram and YouTube, so I loved the idea of a website with a timer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0WpQziL77kL71dLlyWOioQ.png" /><figcaption>Ideas to help users reset quickly and stay on task; no to pagination and yes to an overlay tied to a timer system</figcaption></figure><p>Ironically, I was pretty stressed by the timed format of a design studio, which requires strict time limits on generating and presenting ideas. I do my best creative work with time to think — like our users, I have <a href="https://medium.com/nyc-design/curiouser-and-curiouser-my-journey-down-the-ux-rabbit-hole-65ffcf570bc">a thing about time and control</a> — and the rapid pace of our work was getting to me.</p><p>That night, a group member called me out in most compassionate way, and we had an honest, productive conversation about where my stress was coming from. Though it was a little uncomfortable to discuss, I didn’t have to bottle it up and pretend to be fine. In fact, it was better for the group if I didn’t. (The additional irony that we were a stressed-out group of people making a website to help others de-stress isn’t lost on me. UX designer, heal thyself.)</p><p>Looking back, I can see that this was our group’s trigger point. By setting the precedent of airing out issues and talking through them, we got comfortable with each other. Until then, we had been working together, but after that moment, we started to become a team.</p><h3>DESIGNING FOR OUR USERS</h3><p>The next day, we did another design studio, but we relaxed the time limits and set constraints by starting with only home page sketches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SGTsNYa3jEmXoc7M3GCsFQ.png" /><figcaption>Three concepts for our home screen, from the slow round of our design studio</figcaption></figure><p>At the end of each design studio round, we came together to discuss each new feature/page and remix each other’s sketches. We kept combining ideas this way until we ended up with a fully-formed paper prototype, which we translated into our mid-fidelity wireframes. One round of usability testing later, and we were ready to kick our designs up a notch.</p><p>Moving into a higher fidelity, with real images and color choices, was really fun. We decided that our website needed a name, so we settled on MINDR.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*ewzTreTHQ_WKvpZsSK79tw.png" /><figcaption>Names are hard! The word breaks down into “Mind” and “Dr.” We also liked the connotations of “Reminder.”</figcaption></figure><p>Creating a responsive website required us to think about the layout and design of our content on two differently-sized screens. The main consideration for us was the clickability of elements, as users navigate a phone with their fingers and a desktop/laptop with a mouse. Across both platforms, we made sure our timer system would help manage user stress (and not add to it) by giving users the ability to mindfully set their own time or even browse without time limits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Xkywg-FOB3HXw12ohX5xmA.png" /><figcaption>Our mobile timer elements. We didn’t want our overlay to be annoying, so we gave it a “snooze” option.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*j3Q_CxInd8uc9jTB3-soKA.png" /><figcaption>We built out two content feeds: “give my mind a rest” (mindless) and “give my mind a workout” (mindful)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*6C1a7DeIQhSsnBdO12eFuw.png" /><figcaption>Our filtering system, to help users find content. For ease of use, the filter takes up the whole mobile screen.</figcaption></figure><p>We thought that the vital elements of MINDR. were our timer system, stress-relieving content, and easy navigation, so our usability tasks tested if users agreed. With all of the cute animals to check out, the <a href="https://projects.invisionapp.com/share/Z4OVPMF23C7#/screens/328525417">clickable prototype looked pretty adorable</a>, and users really liked the idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*tJ3Q1PXrJtsIoAUr0KYkcA.png" /></figure><p>Based on our usability tests, we also prioritized an idea for our “next steps” — building out a user profile to save favorite content, personalize the home feed, and customize the timer — that would make MINDR. even more user-friendly.</p><p>When it was finally time to present our website to our class, we knew we’d nailed it. Our design choices were rooted in user data and carefully considered by every member of our group. “Pegasus Design Studio” came through for each other and we were flying high.</p><h3>WHAT MAKES A GOOD GROUP?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dZFNlJeTbOUF_Og63wWOZA.png" /><figcaption>(From left) Raquel, Amy, Triceara, and Yoyo. We didn’t realize until later that our names spelled out A.R.T.Y.</figcaption></figure><p>So, what makes a good group? Obviously, the people. (I had <strong><em>great</em></strong> people on my team.) But putting great people in a group isn’t where making a group ends. From this experience, I took away some best practices for group work, in UX and beyond:</p><ol><li>Recognize your group members’ strengths, especially if they conflict with your own work process. Someone who’s fast can finish something necessary quickly, and someone who’s careful can check over their work when they’re done. A logical brain can work together with an artistic brain when they communicate well and meet in the middle. In every case, our four brains together were absolutely better than one, and learning each other’s strengths helped us to work seamlessly.</li><li>Stick to a system for sharing work. (It will save you.) We worked collaboratively in Google Drive, which helped us talk things over and make changes in real time. It was also useful to have a single place to find group work that was done. (Documentation is important!)</li><li>Look ahead when scheduling and assigning work. I was the most enthusiastic about this in the beginning, but everyone soon got on board with backcasting and timeboxing. Keeping all of our schedules in mind helped so much with work/life balance, and knowing about outside obligations upfront made it easier to distribute work fairly.</li><li>Create a group culture. This happens organically, but having those shared reference points makes the work more fun. By the end of the project, we had our own group slang, nicknames, and in-jokes. We were absolutely “the loud group,” because we all liked working while talking everything over. When we were apart, we looked forward to our Google Hangouts.</li><li>Make it a priority to take care of each other, and pay attention to people’s physical and mental needs: water, food, a break, a distraction. (Yes, we all watched a few videos together.) We were living in a pressure cooker, but having other people around who cared about us eased the worst of it.</li><li>Actively listen to each other. (Like in user interviews, your group members are speaking both verbally and nonverbally.) We were all talkers, so we had to work to be careful about interruptions. If a group member is quiet, ask them for their input. If someone thinks something is wrong but they can’t articulate it, listen to their underlying concern. Developing the reflex to ask “why?” instead of saying “no” created an opportunity to understand and come up with solutions.</li><li>Be patient with each other and respect each other. Every group will have tense moments — because every group is made out of human beings with their own perspectives and life experiences — but most people want to work well together within a group. Remember that the kind of energy you bring to a group is often the kind of energy you’ll get back.</li></ol><p>Ultimately, all of the best practices above build trust — trust that everyone wants what’s best for each other, for the group, and for the project. This shared trust positions criticism as growth and kills defensiveness. Trust makes sure people feel heard, valued, and safe, and it gives people room to grow and change. Trust is the foundation that great groups are built upon.</p><h3>SAYING GOODBYE, TOGETHER</h3><p>The last thing our group did together was a wrap-up. We went over the last two weeks, gave each other “grows” to work on and “glows” to be proud of, and formally closed out our group experience.</p><p>Since we were finishing each other’s sentences by the end of the project, we almost knew what each other was going to say for “grows” and “glows.” Still, it was so nice to have a space to tell each other how we felt out loud. We had gone through something together, and we all emerged better for it.</p><p>I’m incredibly grateful to my group members for what we made. Heading into my next solo project — all about information architecture, or how we group information — I’m still carrying the best parts of them with me. They told me trust my instincts more, and I plan to make them proud.</p><blockquote>Thanks for reading! I’m currently looking for UX opportunities, so if you’d like to work with me, feel free to check out my portfolio (<a href="https://www.amyrosenbaum.com/">amyrosenbaum.com</a>) and get in touch!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=591942856bac" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/group-projects-stress-and-collaboration-in-ux-what-makes-a-good-group-591942856bac">Group projects, stress, and collaboration in UX: what makes a good group?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Curiouser and Curiouser”: my journey down the UX rabbit hole]]></title>
            <link>https://uxdesign.cc/curiouser-and-curiouser-my-journey-down-the-ux-rabbit-hole-65ffcf570bc?source=rss-64c41b04d539------2</link>
            <guid isPermaLink="false">https://medium.com/p/65ffcf570bc</guid>
            <category><![CDATA[new-york]]></category>
            <category><![CDATA[general-assembly]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Amy Rosenbaum]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 00:54:15 GMT</pubDate>
            <atom:updated>2019-07-29T00:51:09.842Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*7LzhJXDIubcYIOzWKBRaMA.jpeg" /></figure><p>Two weeks ago, I changed my life and took my first steps toward a new career in user experience design (UX). After seven years in book publishing, beginning this journey was disorienting — a little like flying and a little like falling. So it was entirely fitting that, all of last week, I couldn’t stop thinking about Lewis Carroll’s classic children’s book, <em>Alice in Wonderland</em>.</p><p>I had some idea of what a ten-week User Experience Design Immersive (UXDI) program at General Assembly (GA) might look like, thanks to the “orientation” session. Choice quotes from alumni: “Say goodbye to your friends and family.” and “Don’t sleep here.” At the time, this was funny and mildly terrifying, kind of like someone yelling: “OFF WITH HER HEAD!”</p><p>Then the program started, and it kept going, and I started to understand fully what GA means by “Immersive.” Still, the alums at orientation had also said, “Trust the process.” A few days ago, I finally understood that too. But I’m getting ahead of myself. I should do what the King of Hearts says: “Begin at the beginning…and go on till you come to the end: then stop.”</p><h4><strong>“WHO ARE YOU?”</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*LzuaHqAbZ5iUsHtthQdrJQ.jpeg" /></figure><p>I’m Amy, and I’m a former book publishing person. I worked a number of jobs in publishing, but children’s books were always first in my heart.</p><p>Children’s books are kind, brave, experimental, and funny. They are beautiful design objects and incredibly practical tools. Their end result, I believe, is creating more empathetic human beings.</p><p>The obsession with empathy is not the only place children’s books and UX intersect, but to move forward, it was enough for me. I fell down the rabbit hole and began Week 1 of UXDI.</p><h4><strong>FOLLOW THE WHITE RABBIT</strong></h4><p>I landed with a thump, immediately dropped into a space where everyone was speaking words I didn’t wholly understand and following a rhythm I couldn’t hear. I met my 24 classmates, and with barely a how-do-you-do, we had a full day of lectures. That night, we were given our first assignment:</p><blockquote>“Create a mobile app that supports the GA student social experience”</blockquote><p>I hit the ground running and scheduled my user interviews that night.</p><p>UX (and GA itself) is an extrovert’s paradise, and I especially loved the research phase of this project. I spoke with five UXDI students from cohorts who were further along in their programs, taking the opportunity to learn about them, their habits, their likes/dislikes, and GA itself. Piecing together the details of my fellow students’ lives, and perhaps getting a glimpse of what was ahead for me, was exhilarating. I wanted to know everything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/473/1*DQo9GJry1IrqnhP2eRmekA.jpeg" /></figure><p>I didn’t have a lot of time to revel in this stage of the project, because reality set in: I had to transcribe my interviews. It was a hard lesson in scope to transcribe five 25-minute interviews in less than 48 hours.</p><p>I, like the White Rabbit, am <a href="https://www.youtube.com/watch?v=ZOLpCWlsCjw">a little obsessed with time</a>. (You might say “Type A.”) I also have a stage/project management background, and I really love to schedule. The transcriptions threw my task projections way off, and nothing else could get done until they were. I went off on my own, away from my cohort — working constantly, anxious that I was running so late. I knew exactly how the poor White Rabbit felt: “The hurrier I go, the behinder I get.”</p><h4><strong>THE POOL OF TEARS</strong></h4><p>The deadlines on the first project loomed, and I was drowning. Affinity mapping was sinking me. I’d asked for too much information, and alone in my non-whiteboard-walled apartment, it was hard to synthesize.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*cK8XOnR0JKo_iLpJu27J6w.jpeg" /></figure><p>In my sleep-deprived haze, I tried stay positive by putting together a persona that made me laugh and resolving to do better. I was drowning, but I knew I could pull myself out. To get the most of the experience, I had to pay attention to the lessons the course was teaching me. I had to UX my experience of UXDI.</p><h4>“TAKE SOME MORE TEA”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*nLEXwAddxYWBjtrHh99aiw.jpeg" /></figure><p>Looking before I leaped, I poured over the briefs for upcoming projects. Our instructors wanted us to succeed, and they gave us all the guidance we needed, if we looked and listened for it. There was a method to their madness. I focused more on learning the UX process and practicing the tools than perfecting a final product, adjusting my own metrics for success.</p><p>I did stay very conscious of my time management, as time is the most precious resource at GA, but I also tried to be gentle with myself. I slept and ate. I listened to music that made me happy, counted dogs on my way from the subway, bought glitter unicorn stickers, and brought in loose leaf tea from home. I prioritized finding moments of joy in an incredibly intense experience, and I set myself up for success by taking time to think things through thoroughly.</p><p>The last piece of the puzzle was looking out, past my own experience. To complete this project, our cohort had to interact with people who had been where we were. So, I learned what to do by watching them. They stuck together in groups, generously supported each other, and asked for help when they needed it.</p><p>I started to lean on and learn from my own classmates. We all came to the course with incredibly diverse skills, backgrounds, and personalities, and we had so much to teach each other. (We still do!) My cohort became my best resource, and I gratefully wanted to give back as much as I got from them.</p><h4>“DRINK ME”</h4><p>With a clearer head, more time to think, and more support, I started making work I was proud of. I redid my affinity map, and I cemented the high-level opportunity spaces around the “GA student social experience”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*bN2Th9vfXpqbIAj70qLGKA.jpeg" /></figure><p>Users spoke the most about having a good time off campus, with 4/5 users stating off-campus drinks with their cohort were their favorite events during UXDI. But organizing these cohort drinks were not without their difficulties:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*V_05j84rIWqRi8w_Q0lniA.jpeg" /></figure><p>Through my users’ words, I found the heart of my story:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*7Vl6t0h2oClZCaIQTkwsiQ.jpeg" /></figure><p>With this in mind, I put the finishing touches on my persona, Bizzy Lerner:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*4SN04Pq43uIakwgUDyUUKA.jpeg" /></figure><p>Trying to solve Bizzy’s pain points, I arrived at my mobile app: GA Recs, which curates recommendations of where to go around campus from GA students.</p><p>Many (many, many) iterations of wireframes came next. After spending so much of my professional life on the computer, putting pen to paper made me feel like a kid again. This sense of play carried over to my paper prototype, where I cut out tiny Xs for filtering checkboxes and left a hollow window in a screen to allow my “map” to move.</p><p>When it was time to usability test, I picked a task that would directly address the main frustrations of my users and my persona:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*sWGzPrtIktoB9BquMjMNRQ.jpeg" /></figure><p>Based on my users’ feedback (and some delight), I clarified the design before creating mid-fi wireframes in Sketch and a <a href="https://invis.io/RBOLWKNY82Q#/325735073_Drinks_Screen_Home">working prototype in InVision</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*1th9Gq_TFMZJ4L7vyjtIPA.jpeg" /><figcaption><a href="https://www.freepik.com/free-photos-vectors/travel">Travel vector created by Freepik</a></figcaption></figure><p>By the time I put together my final presentation, everything had clicked. I trusted the process, and it saw me through.</p><h4>“WE’RE ALL MAD HERE”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/1*_QyL2QpLZx3Nu8uMSA03jw.jpeg" /></figure><p>Not all of my stories end so neatly, and I know there will be more twists and turns to this one before “THE END.” (We have eight weeks to go, after all!)</p><p>I do feel much luckier than Alice, who had to travel through Wonderland alone. I have 24 classmates who are journeying alongside me, plus a growing network of mentors and friends. For my cohort, this is just the beginning, and I can’t wait to see where our adventures will take us next.</p><blockquote>Thanks for reading! I’m currently looking for UX opportunities, so if you’d like to work with me, feel free to check out my portfolio (<a href="https://www.amyrosenbaum.com/">amyrosenbaum.com</a>) and get in touch!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65ffcf570bc" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/curiouser-and-curiouser-my-journey-down-the-ux-rabbit-hole-65ffcf570bc">“Curiouser and Curiouser”: my journey down the UX rabbit hole</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>