<?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 Magera Moon on Medium]]></title>
        <description><![CDATA[Stories by Magera Moon on Medium]]></description>
        <link>https://medium.com/@mageramoon?source=rss-9df3beed708c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yrbv1XEXNISIth2A0hOSYA.jpeg</url>
            <title>Stories by Magera Moon on Medium</title>
            <link>https://medium.com/@mageramoon?source=rss-9df3beed708c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:04:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mageramoon/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[In-Product Intercepts for User Research Recruitment]]></title>
            <link>https://medium.com/related-works-inc/in-product-intercepts-for-user-research-recruitment-51efa7fa3d99?source=rss-9df3beed708c------2</link>
            <guid isPermaLink="false">https://medium.com/p/51efa7fa3d99</guid>
            <category><![CDATA[user-interviews]]></category>
            <category><![CDATA[user-recruitment]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Magera Moon]]></dc:creator>
            <pubDate>Tue, 22 Sep 2020 21:48:16 GMT</pubDate>
            <atom:updated>2020-09-22T21:48:16.142Z</atom:updated>
            <content:encoded><![CDATA[<h4>A story about recruitment methods that worked 3x better for us.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o72LpgCReiZ3HIRfvoot2Q.jpeg" /></figure><p>Recruiting interview subjects for a research study can be hard. You spend countless hours crafting recruitment campaigns and eligibility surveys, send 100s if not 1,000s of emails, and yet still have trouble finding candidates. This is a story about a recent project, and some recruitment methods and tricks we tried that worked 3x better for us.</p><h3>First, a little bit of context</h3><p>As <a href="https://www.relatedworks.io/">Related Works</a>, we help a wide spectrum of companies more deeply understand their customers and build better products. A central part of our work is conducting quantitative and qualitative research, which often includes a series of research studies with specific customer cohorts.</p><p>Earlier this year, we had the opportunity to participate in VX2020, an initiative by <a href="https://highergroundlabs.com/">Higher Ground Labs</a> to provide quick, two-week research sprints to companies that build critical tools used by progressive organizations and campaigns. As part of that initiative, we got to work closely with <a href="https://join.mobilize.us/">Mobilize</a>, a white-label events platform that organizations and campaigns use to publish and manage their events.</p><p>We did a number of sprints with them, allowing us to try a variety of different recruitment methods with drastically different results. Our hope is that by sharing our experience, we can help similar product teams more effectively recruit high-quality research participants as well.</p><h3>Sprint 1: Email recruitment</h3><p>Working with Mobilize, we decided that our guiding research question was: “<em>How can we improve the first-time volunteer experience?”</em>. We knew anecdotally that Mobilize is just a single touchpoint in a long volunteer journey, so we wanted to shed some light on this critical part of the experience by speaking to 5–7 first-time volunteers in 1:1 interviews.</p><p>Once we knew roughly who we wanted to talk to, we then needed to define these three key inputs:</p><ol><li><em>What is our specific candidate criteria?</em></li><li><em>Are we going to offer an incentive for their time?</em></li><li><em>What recruitment method should we use?</em></li></ol><p>When thinking about our candidate criteria, we needed to identify what key behavioral and demographic attributes were important. Considering this was going to be the first round of research done with first-time volunteers, we wanted to make sure we were talking to a diverse and representative group of Mobilize’s user base. We ended up with this set of requirements:</p><h4><strong>Mobilize Experience:</strong></h4><ol><li>Recently completed their first volunteer event using Mobilize, ideally within the past week</li><li>Diverse range of organizations or campaigns</li><li>Diverse mix of event types, such as canvassing, debate watch parties, phone banking, etc.</li><li>Diverse mix of device usage, slightly weighted towards iPhones</li></ol><h4><strong>General Demographics:</strong></h4><ol><li>Geographically diverse, and from a mix of urban and suburban areas</li><li>Diverse mix of ages, slightly weighted towards older participants</li><li>Diverse mix of genders, slightly weighted towards females</li><li>Diverse mix of ethnicities</li></ol><p>If you’re new to defining a set of candidate criteria, <a href="https://www.userinterviews.com/ux-research-field-guide-chapter/find-good-research-participants">this article</a> does a great job explaining what to consider and look out for.</p><p>Next on the list was figuring out our research incentive. Typically, it’s a good idea to compensate research participants in some way for their time, but how much and in what form can vary depending on your budget and the level of time and effort you’re asking of them. We decided to offer $50 Amazon Gift cards for about an hour long conversation over video, which is what we typically do for similar research studies.</p><p>We then needed to figure out what recruitment method was going to be best based on our candidate criteria, sprint timeline, and any existing lists of potential research candidates we could pull from. We sat down with the Mobilize team and reviewed some commonly used recruitment methods to see which one made the most sense for us:</p><ol><li>Doing some more <strong>guerilla-style and in-person recruitment</strong> by going to some of these upcoming volunteer events that were hosted on Mobilize, by reaching out to potential candidates from our own network, or even through Craigslist or relevant Facebook groups.</li><li>Adding an <strong>in-product intercept</strong> to Mobilize after someone has registered or attended an event.</li><li><strong>Directly emailing</strong> individuals that signed up for an event for the first time on Mobilize.</li><li><strong>Recruiting from an existing research database</strong> such as <a href="https://www.userinterviews.com/">userinterviews.com</a>, <a href="https://ethn.io/pool">ethn.io</a>, or <a href="https://www.usertesting.com/platform/panel">usertesting.com</a>.</li></ol><p>Considering we were on a very short timeline — we needed to have interviews scheduled and conducted within 4–5 days — doing an in-product intercept and more of a guerilla-style approach was not going to be feasible. We went with the quick-and-easy route: Mobilize helped us compile a list of individuals that had recently attended events, and we emailed them. Since we had limited demographic data, we asked users to fill out a screener survey in order to confirm we were going to be talking to a diverse group of individuals who met our criteria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cc3l3ihIcTTCNsEFyBKL3g.png" /></figure><p>Based on our experience doing similar research in the past, we expected around a 5–7% response rate, but only around 2% of users responded in this case. One hurdle we hadn’t anticipated is that since Mobilize is a white-label product, end users generally aren’t aware of Mobilize. We learned from the users we eventually spoke to that some were even suspicious that our emails might be malicious. <strong>We suspect this lack of brand-awareness played a big role in our low response-rates, and imagine that this same hurdle may apply across a wide spectrum of white-label products.</strong></p><figure><img alt="A couple different organization event pages that all are using Mobilize." src="https://cdn-images-1.medium.com/max/1024/0*gQqEUJJ9ZQ1oTRkm" /><figcaption><em>A couple different organization event pages that all are using Mobilize.</em></figcaption></figure><p>We were eventually able to recruit enough candidates, but ended up having to email many more users than we had anticipated.</p><h3>Sprint 2: Experimenting with in-product intercepts</h3><p>Thankfully, we were able to conduct a second research sprint a month or so later, this time with a little more time to prepare. We still wanted to talk to first-time volunteers, and we knew that directly emailing individuals was sub-optimal given the hurdles around brand awareness we experienced the first time. So we decided to try something different this time.</p><p>We reviewed our list of possible recruitment methods again, and in-product intercepts seemed like it could be a more promising option this time around. After someone has attended an event, Mobilize will send a quick follow-up text asking how the event went. We wanted to see if we could leverage this interaction and add an additional follow-up text for those that responded and had attended their first event, asking if they’d be interested in participating in a round of research:</p><figure><img alt="An example of the text intercept we ended up sending to recruit research participants." src="https://cdn-images-1.medium.com/max/1024/1*RHhdKgsXeZMahZ1v3SoNPw.png" /></figure><p>The Mobilize team was amazing and was able to quickly add this intercept for eligible candidates. Within a couple of days of turning it on, we got roughly a 7% response rate, over <strong>triple the response rate</strong> compared to our first sprint. In addition, since we were able to catch people within a day of attending their event, <strong>the quality of the interviews improved, as people were more likely to remember important details since it was still fresh in their minds</strong>.</p><h3>Conclusion</h3><p>Figuring out which recruitment method to use given your research goals and constraints can be challenging, especially when you’re trying to reach individuals with limited brand-awareness. In our experience, in-product intercepts are an effective method because you’re catching the user while they are already engaged and active within your product.</p><p>If implementing your own custom intercept is not possible, there are a variety of intercept services you can easily implement, such as <a href="https://ethn.io/intercepts">Ethnio’s Intercept Tool</a>. The Nielsen Norman Group wrote an amazing <a href="https://www.nngroup.com/articles/live-intercept-remote-test/">step-by-step overview</a> of how they used it to conduct research on their site. We’ve found intercepts to be an essential recruitment tool in our research, and we hope you find them useful as well.</p><p><em>Many thanks to everyone at VX2020, </em><a href="https://highergroundlabs.com/"><em>Higher Ground Labs</em></a><em>, and the </em><a href="https://join.mobilize.us/blog"><em>Mobilize Team</em></a><em> for the opportunity to work together, and to </em><a href="https://medium.com/@giokincade"><em>Giovanni Fernandez-Kincade</em></a><em> (my partner in work, life, etc), </em><a href="https://twitter.com/mollieruskin"><em>Mollie Ruskin</em></a><em>, and Peter Martinazzi for taking the time to read this post and give thoughtful feedback to make it better. 💖</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51efa7fa3d99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/related-works-inc/in-product-intercepts-for-user-research-recruitment-51efa7fa3d99">In-Product Intercepts for User Research Recruitment</a> was originally published in <a href="https://medium.com/related-works-inc">Related Works</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The People Part of Design Systems]]></title>
            <link>https://medium.com/related-works-inc/the-people-part-of-design-systems-a5b54eea24f4?source=rss-9df3beed708c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5b54eea24f4</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Magera Moon]]></dc:creator>
            <pubDate>Wed, 28 Feb 2018 17:17:55 GMT</pubDate>
            <atom:updated>2018-05-08T16:50:40.088Z</atom:updated>
            <content:encoded><![CDATA[<h4>Experiments and learnings from managing Design Systems at Etsy.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ED_Xqtg7YE6piLQWztHmUw.jpeg" /></figure><p><em>A little over nine months ago, I left Etsy to co-found Related Works. During my last year and a half there, I managed Etsy’s first dedicated Design Systems team. Below are my thoughts about what it meant to make the team and the work successful.</em></p><p>As tech companies grow, the creation of their design system can become a powerful and necessary tool. Typically consisting of a defined set of reusable components and guidelines, design systems make it easy for anyone to create a brand-aligned and cohesive customer experience consistently. At their best, they have the power to align everyone on a shared vision of what your brand’s voice and visual style is, and how it behaves. If you’re new to the world of design systems, I’d recommend reading <a href="https://www.designbetter.co/design-systems-handbook">InVision’s Design Systems Handbook</a>.</p><p>Over the years, Etsy’s design system went through many incarnations. The way we organized to do the work also changed, and in 2016 we created our first dedicated Design Systems team. Up until then, it had been built and maintained by a group of designers and engineers who did it on top of their regular product work. Improvements were being made, but slowly. As demand increased, it became clear we needed a full-time team to keep pace.</p><p>We had a grand vision that by enabling a team of designers, engineers, and product managers to focus on the continued maintenance, improvement, and adoption of our system, the rest of the product org could go back to concentrating on building customer experiences. Anyone could still contribute to the work, but the heavy lifting was now the responsibility of the Design Systems team.</p><p>The reality turned out to be more complicated than that.</p><p>Although we now had a dedicated team, we were still relatively small with a ton of surface area to cover; Etsy had customer experiences spanning web, iOS, Android, email, and off-Etsy and offline, which needed to meet the needs of both buyers and sellers who had very different needs. We were also working on the creation of <a href="https://www.etsystudio.com/">a new marketplace</a> with its own brand and customer needs. We were stretched thin and weren’t able to support all the requests for new or modified components. Product teams would fill in the gaps themselves by creating the additions or modifications they needed, but often without the due diligence required to make sure they would work across all our use cases and relevant platforms. The Design Systems team fell into a pattern of playing catch-up. We were heading down a road where we were a bottleneck, and the benefit of our systems being the source of truth was slowly deteriorating.</p><h3>Fostering collective ownership</h3><p>We realized that ultimately for our systems to succeed long-term, they needed to be thought of as everyone’s responsibility. It became clear our role as a team wasn’t just doing the heavy lifting of ongoing maintenance and improvements. We were a team of system advocates and facilitators, helping everyone contribute to our evolving system with the big picture in mind.</p><p>We learned it was important to create the space, time, and variety of ways people could be involved. We needed to define clear goals for how to contribute, and what a successful contribution was. Lastly, there had to be opportunities for cross exposure to both the demands and constraints of individual product teams and the Design Systems team.</p><p>Over the course of that first year, we experimented with and tried a lot of different things. Some were spun up, but most evolved from existing programs. We ended up with an ecosystem of opportunities, processes, and mechanisms that were valuable in different ways.</p><h4>Design Bug Rotation</h4><p>Etsy had accumulated a decent amount of design debt over the years. As you navigated across Etsy, you could encounter a variety of similar but slightly different components, interactions, or behaviors. It created a fragmented and confusing customer experience, eroding customer trust.</p><p>Inspired by the engineering organization, the Design team created the Design Bug Rotation to help pay down our design debt. Every two weeks or so, a group of designers would get together for a couple of hours to fix what we called “design bugs.” These were things that didn’t hinder functionality and wouldn’t have been filed as an engineering bug, but were places where we were using an old component, an existing one incorrectly, or a one-off alteration. As anyone in the company encountered one of these bugs, they’d file a ticket under a shared Jira board. During a rotation, designers would go through the list and chip away at them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hFhgXbn75wRPmCxFgJETTA.jpeg" /><figcaption>The evolution of Etsy’s visual language over the years.</figcaption></figure><p>Over the years, the rotation gained more structure, with each rotation focused on a specific theme, component, or product area thanks to the hard work of <a href="https://www.linkedin.com/in/cambriakline/">Cambria Kline</a>. We leveraged the rotations as a power boost to the Design Systems team, helping us get through any work that included cleaning up some related design debt.</p><p>Beyond speeding up our work, rotations often freed up the Systems team to innovate and think at a higher level. For example, we were working on a huge push to update our color usage everywhere to be more brand-aligned. It was during one of these rotations that <a href="http://sylormiller.com/">Katie Sylor-Miller</a>, an engineer on the Systems team, realized we needed a more efficient and future-proof way to make these types of sweeping, global changes. As a result, she was able to advocate for the creation of <a href="https://medium.com/salesforce-ux/living-design-system-3ab1f2280ef7">design tokens</a>. If we decided we needed to update our colors again in the future, we would merely update them in one place and see the changes reflected everywhere.</p><p>Lastly, these rotations created an easy way contribute without a considerable time commitment. There were plenty of designers and engineers that wanted to help but didn’t have a specific thing in mind. The Design Bug Rotation gave them an opportunity to do just that. They also got to experience first-hand the costs of not investing in using our design system.</p><h4>New Hire Boot Camp</h4><p>As the design team grew, it became invaluable to onboard new designers to help them hit the ground running. Over the years the process became more robust, with a suite of resources and one-on-one sessions showing them how to use our web toolkit and push changes to production. One of those additions was having every new hire do a 2–3 week boot camp with a team before joining their product team full-time.</p><p>Once we created the Design Systems team, we’d try to have as many new hires as possible do their boot camp with us. We’d give them an achievable project they could finish within two weeks that provided an opportunity for them to get some hands-on experience using our toolkits, documentation and other resources.</p><p>These boot camps made system thinking a foundational part of their entry into Etsy. By working on our system early on, they became invested in its success. Every new hire that did their boot camp with Design Systems became a strong advocate for the work and its adoption.</p><p>In turn, it also created an opportunity for a fresh perspective and new ideas. Things we had grown accustomed to were questioned, creating more thoughtful discussions and long-term solutions.</p><h4>Design Systems Yearly Rotation</h4><p>For every year at Etsy, any brand designer, product designer or engineer could spend two consecutive weeks embedded in the Design Systems team. They would go to all of the regularly scheduled meetings and design crits and worked on a project they were responsible for completing during that time. We’d designate someone on the team as their buddy, who was there to help answer any questions or to bounce ideas off of if they needed to. Rotators could assist with ongoing projects, but often they had specific self-directed plans they wanted to pursue.</p><p>These rotations gave folks, who might not otherwise have the time to do systems work, the opportunity to help in a focused and meaningful way. It gave those individuals who loved systems work but still preferred to focus on product work full-time, a little bit of both worlds.</p><p>One of the most impactful outcomes was when brand designers did a rotation. Our brand team worked on marketing campaigns on and off Etsy, physical items, and special events for our sellers and buyers around the world. They used different processes and tools than the product design team. Many expressed a desire to learn more about the product development process and how to use our web toolkit, but it was hard to squeeze into their busy schedules. As part of a rotation with Design Systems, we’d have them go through our new hire onboarding process, learning how to use our web toolkit and push changes on their own. We’d then pair them with someone on the team to work together to find an existing project they were working on that had an element they could code themselves or something that could become a reusable layout or component with guidelines.</p><p>Rotations with our brand partners provided insight into how to make our systems a stronger expression of our brand, while also making their work more systems-minded in its execution and operations. For example, one rotation focused on creating a set of reusable and responsive hero components that we used for marketing campaigns, event microsites, or critical pages like our homepage. Beyond adding a useful UI component to our system, the brand design team now had a tool that helped them plan and immediately test if the assets they were creating for the hero space would work. While at a photo shoot, they could insert the image into the hero component, confirm that it looked good for all breakpoints, and iterate on the spot if they needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RxunAmQEsHeAuK7rC3S8Aw.png" /><figcaption><a href="https://www.linkedin.com/in/susi-vetter-7235907a/">Susi Vetter</a> testing out image options for <a href="https://www.etsy.com/resolution">Etsy Resolution</a> landing page hero while at the photoshoot.</figcaption></figure><h4>Design Systems Council</h4><p>Teams were working at a rapid pace, and when our current components or modules didn’t fit a specific need, the Systems team wasn’t able to always be there to help and give feedback. To help remedy these issues, we set up what we called the Design Systems Council. It was a shift in our team model to more of a <a href="https://medium.com/eightshapes-llc/team-models-for-scaling-a-design-system-2cf9d03be6a0">federated model</a>, with a select group of representatives that were product-area, subject-matter, or platform experts.</p><p>Their responsibilities were to be a more formalized augmentation of the Design Systems team, who would meet every two weeks to give updates on anything happening within their product area that could impact the everyone and to evaluate, advise, and make decisions on proposed changes to the system. They were also responsible for sharing those decisions and updates with their respective teams. Representatives would rotate roughly every six months to give more individuals an opportunity to participate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytBZazOJqMlHcV-lGLnOIA.jpeg" /><figcaption>The makeup of the Council mirrored the surface area our systems supported.</figcaption></figure><p>It increased visibility and discussion across the product org about what work and decisions were made about our design system, and what needs and issues were coming up that needed to be addressed. It shortened feedback loops between product teams needs and the Design Systems team, making it easier for discussion to happen as soon as possible when our systems weren’t serving them.</p><p>The Council spread accountability, ownership, and decision making to a set of individuals who were uniquely positioned as experts across the company. By being part of the conversations about the impacts those changes might have on our entire system, it incentivized everyone to think systematically.</p><h3>Amplified effects</h3><p>Beyond increasing investment and participation in our systems across the company, there were additional outcomes that had a positive impact on our work and Etsy at large:</p><ol><li><strong>It clarified our goals.</strong> To make these programs useful, we had to improve our contribution process, how we evaluated and measured success for those contributions, and how we prioritized the work to have the greatest impact. Each person who participated in these programs brought an opportunity to question and uncover areas where we could not only make the components better and documentation clearer, but also the process of using and contributing to our system easier.</li><li><strong>Created more considered and thoughtful additions to our systems.</strong> It provided exposure to the challenges and needs of individual product teams with that of maintaining and scaling a global system, thus creating a more resilient one.</li><li><strong>Increased communication and trust across teams</strong>. People got to collaborate with others they wouldn’t otherwise get to as part of their regular work. The relationships created during these different programs created more open channels of communication. People were more inclined to reach out to Design Systems if they had a question and the speed at which information was shared increased.</li></ol><h3>The work is never done</h3><p>Through our experiments, we learned design systems are more than components and guidelines. They’re living organisms made up of the relationships and mechanisms you use to foster collective ownership. Making design systems successful is just as much about creating a people system as it is about creating a technical or operational one. You have to make it easy for everyone to feel responsible for the system with structures that form sustained channels of education and communication between teams. After all, they only work, adapt, and remain resilient because of the people involved.</p><p>Many thanks to <a href="https://twitter.com/00ara00">Ara Kim</a>, <a href="http://giovanni/">Giovanni Fernandez-Kincade</a>, <a href="https://medium.com/@sethdaggett">Seth Daggett</a>, <a href="https://medium.com/@MarcoSuarez">Marco Suarez</a>, and <a href="https://medium.com/@ksylor">Katie Sylor-Miller</a> for taking the time to read this post and give thoughtful feedback. ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5b54eea24f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/related-works-inc/the-people-part-of-design-systems-a5b54eea24f4">The People Part of Design Systems</a> was originally published in <a href="https://medium.com/related-works-inc">Related Works</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Etsy’s Design Principles]]></title>
            <link>https://medium.com/etsy-design/creating-etsys-design-principles-4faf31914be3?source=rss-9df3beed708c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4faf31914be3</guid>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[etsy]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Magera Moon]]></dc:creator>
            <pubDate>Tue, 23 May 2017 18:07:26 GMT</pubDate>
            <atom:updated>2017-05-23T19:00:36.922Z</atom:updated>
            <content:encoded><![CDATA[<h4>Aligning on a shared definition of design excellence</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yBPpNPHEMFNIhvil_-vwcA.jpeg" /><figcaption><strong>Illustration by </strong><a href="https://www.etsy.com/shop/printshopLU"><strong>Lucy Sherston</strong></a></figcaption></figure><p>During my time at Etsy, I had the pleasure of watching the design team grow and evolve. When I joined over six years ago, there was just a handful of designers working collectively to support business and customer needs. Today, it is a multi-disciplinary group of Product Designers, Brand Designers, Art Directors, CX Strategists, Information Architects, Copywriters, and Researchers.</p><p>With so much growth, it became critical for us to have a shared vision to guide the execution and output of our work. Last year Randy Hunt, VP of Design, introduced the Design team’s vision of Etsy being synonymous with design excellence. We had our North Star, but what did design excellence mean in practice for Etsy? What did that look like as a customer experience? How would we know if we’d achieved it or not?</p><p>To help answer these questions, I created a working group with the goal of creating a set of design principles. We believed that everyone in the company participates in creating the best possible customer experience for our community, and this belief was reflected in the makeup of the team, which represented multiple functions; Research, Brand, Engineering, Product, Design, Security, Members and Community, and Values Aligned Business.</p><p>After six months of workshops, Google Docs, surveys, spreadsheets, stakeholder interviews, and group discussions, we had our principles of design excellence:</p><ul><li><strong>Be effective</strong></li><li><strong>Create unity</strong></li><li><strong>Always be thorough</strong></li><li><strong>Express Etsy</strong></li></ul><p>I’ll get into details on them later, but first let’s go through how we got there.</p><h3><strong>A bottoms-up approach</strong></h3><p>When researching other companies’ principles and how they went about creating them, there wasn’t a lot of material that discussed process, especially for large companies. Although the end goal was the creation of these principles, we took a lot of care in making sure the process was thoughtful and inclusive of the individuals that we hoped would use them to inform their work on a daily basis. We believed that these principles were already inherent in the decisions and processes that guide everyone in their work, and that these principles should clearly be “Etsy” in their voice, tone, and values.</p><p>To help us determine how best to involve individuals in our process, we defined three concentric circles, clarifying the types of roles and level of involvement we’d ask people to contribute to the creation of the principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fUWwejsc_9fDG94mJeSCQ.png" /></figure><h4><strong>Principles Working Group</strong></h4><p>The core group responsible for the creation and implementation of the principles. Also responsible for involving key influencers and admin throughout the process.</p><h4><strong>Influencers</strong></h4><p>Key leaders who are responsible for providing feedback throughout the process, and are seen as advocates for the use of the principles.</p><h4><strong>Admin</strong></h4><p>The largest group of contributors from across the company who are responsible for providing feedback on what design excellence looked like in practice and in our work.</p><h3><strong>Aligning on our goals</strong></h3><p>The first thing we needed to do was discuss and align on some core questions about the goals and intended scope of the principles. Michael Yap, a User Experience Strategist at Etsy, quickly identified what he called <em>The 5W’s</em>:</p><ol><li><em>What motivates this work?</em></li><li><em>What are the goals of these principles?</em></li><li><em>What is our definition of design?</em></li><li><em>What characteristics should these principles exhibit?</em></li><li><em>Who should benefit from these principles?</em></li></ol><p>Michael facilitated a series of workshops, giving the group space to unpack our desires for these principles, and align on a definition for the questions above. We then created our “one-sheeter”, capturing these questions on a single sheet of paper that could be printed, shared, and referenced going forward. At the beginning of every meeting, we’d review the 5W’s, asking ourselves if they still felt accurate, and update the sheet when needed. The document evolved over time, and expanded to include more questions that helped guide the creation of the principles:</p><p><em>6. What informs these principles?</em></p><p><em>7. When and where would these principles be used?</em></p><p><em>8. What format should these principles take?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ETU0YLAbf48Rt7XOgopy7w.jpeg" /><figcaption>One of the final iterations of our “one-sheeter” that we reviewed at the beginning of every meeting.</figcaption></figure><h3><strong>Uncovering the “raw material”</strong></h3><p>In order to involve a wide array of individuals across the company, we created a short survey to better understand our definition of excellence in our work. We sent the survey to individuals across Product and Brand Design, Product Management, Marketing, Engineering, Research, and Values Aligned Business.</p><p>We then identified recurring themes from the responses, consolidating them down to 21 distinct statements. Using these core statements, we workshopped our first version of the principles.</p><h3><strong>Gut-checking with key influencers</strong></h3><p>Once we had our first rough draft of the principles, we wanted a gut-check from individuals we had identified as influencers. We did this through 1-on-1 stakeholder interviews, and used this time to ask questions about what value principles would bring to their work, how these principles would apply or impact their work, what would make these principles successful, and what was resonating (or not) with the first draft of principles. Earning buy-in and engagement from those that would later advocate for the use of these principles in existing processes would be a key to their success.</p><h3><strong>First we took an axe to them. Then a scalpel.</strong></h3><p>Armed with the insight and feedback from the stakeholder interviews, we stripped the principles down to five core concepts. We began a process of iterating on these core concepts, each iteration focusing on tweaking, removing, and adding to them with a specific focus in mind. As we tweaked and reviewed, the principles slowly came into focus. We learned that they needed to be bold, feel actionable, and that their value was in adding clarity to what the output and execution of design excellence meant for us. After two months, multiple discussions with key influencers, and nine iterations, we had created a set of four principles that we believed achieved our goals set forth in our 5W’s:</p><h4>Be effective</h4><p>Excellent design means satisfying customer’s needs. It’s asking, ‘are we solving the right problems, in the best way, for the right people?’ Learn from feedback. Listen to your peers, team members, and customers. Open your mind, and have an empathetic heart.</p><h4>Create unity</h4><p>Excellent design means unity. It’s asking, ‘does everything we do feel essential, and work together to create a holistic experience?’ Be consistent. Champion our systems. Align our brand. Make sure nothing is arbitrary.</p><h4>Always be thorough</h4><p>Excellent design means thoughtful design. It’s asking, ‘have we been deliberate and intentional down to the last detail?’ Apply all your passion and skill to crafting experiences that make people feel emotionally connected and respected.</p><h4>Express Etsy</h4><p>Excellent design means boldly being ourselves. It’s asking, ‘are we bravely expressing who we are in what we make?’ Be masters of our convictions and values. Bring their meaning and purpose to our work, and make it uniquely Etsy.</p><h3><strong>Putting our principles into practice</strong></h3><p>When thinking about the best way to unveil the principles, we kept on thinking about what we continually heard from influencers and our peers; in order for them to be successful, they should be central to the way we talk about and evaluate our work and processes used to make it. We had a hunch that what we needed to answer the question of <em>how can we form habits around using these principles in everyone’s daily work?</em></p><p>After sharing the principles at our design all hands, we held a workshop with the entire design team to help facilitate a conversation and way of thinking about how these principles apply to our work. Central to the workshop was having everyone explore various Etsy environments for examples of each principle “in the wild”. Everyone explored our space and found examples of our principles everywhere around them. The result was an exercise in making the process come full circle: These principles were not novel concepts, but rather a shared lens for us to discuss, inform, and help us make better design decisions, together.</p><h3><strong>Learnings and advice</strong></h3><p>When I started this working group, I had no idea how we should create these principles, and how long it was going to end up taking us. Once we had finally shared and celebrated the creation of these principles, we took time to reflect and identify what we liked, learned, and longed for from the past six months. These were the key learnings that we identified as a group about our process:</p><h4><strong>Set a hard deadline, and hold yourself to it.</strong></h4><p>We were a large group working on these principles in addition to our daily responsibilities. It was easy for check-ins or milestones to slip, but when we had a hard deadline that was impossible to move, it helped to keep us on track.</p><h4><strong>Invest in aligning on your goals as a team at the very beginning.</strong></h4><p>Setting time aside early on to make sure everyone was aligned on the specific goals for the work was critical. Also creating a ritual around reviewing our 5Ws at the beginning of every meeting helped make sure we were on the same page when discussing specific next steps or decisions.</p><h4><strong>Be clear about what’s expected of everyone and what role they play.</strong></h4><p>Having a large and diverse working group was incredibly helpful in making sure our principles would truly be relevant and actionable to anyone within the company, but there were moments where it was unclear how best to contribute. Identifying what specific decisions or tasks each person could uniquely be responsible for would have been more impactful, sped up the process, and made everyone engaged throughout the six months.</p><h4>Thank you</h4><p>None of this would have been possible without the dedication and support from these fine folks who helped to lovingly craft these principles as a team: <a href="https://medium.com/@michaelryap">Michael Yap</a>, <a href="https://medium.com/@MarcoSuarez">Marco Suarez</a>, <a href="https://medium.com/@harllee">Jessica Harllee</a>, Sam Sherman, <a href="https://medium.com/@maddyberd">Maddy Berd</a>, Netty Devonshire, <a href="https://medium.com/@kpotochney">Katie Potochney</a>, <a href="https://medium.com/@amitsnyderman">Amit Snyderman</a>, Daniel Espeset, <a href="https://medium.com/@Dymaxion">Eleanor Saitta</a>, Julia van Grieken, Nikki Summer, Madeleine Di Gangi, <a href="https://medium.com/@randyjhunt">Randy Hunt</a>, <a href="https://medium.com/@awright249">Alex Wright</a>, <a href="https://medium.com/@jsnhff">Jason Huff</a>, <a href="https://medium.com/@floriz">Floris Dekker</a>, <a href="https://medium.com/@itschesley">Chesley Andrews</a>, <a href="https://medium.com/@kristinapyton">Kristina Pyton</a>, <a href="https://medium.com/@paperkary">Karyn Campbell</a>, Jim Thomas, <a href="https://medium.com/@kyleturman">Kyle Turman</a>, Jung Park, Anda Corrie, Kate Carmody, Russ Poslusny, Amy Dyer, <a href="https://medium.com/@jaymbergesen">Jay Bergesen</a>, Andre Rickerby, <a href="https://medium.com/@nickeyskarstad">Nickey Skarstad</a>, <a href="https://medium.com/@podduturi">Arpan Podduturi</a>, Aaron Pass, Lynnea Midland, <a href="https://medium.com/@jedediahbaker">Jedediah Baker</a>, and the entire design team at Etsy. Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4faf31914be3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/etsy-design/creating-etsys-design-principles-4faf31914be3">Creating Etsy’s Design Principles</a> was originally published in <a href="https://medium.com/etsy-design">Etsy Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>