<?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[Gatsby Design Labs - Medium]]></title>
        <description><![CDATA[A space for us to imagine, test, and document our ideas about the world in which Gatsby innovates - Medium]]></description>
        <link>https://medium.com/gatsby-design?source=rss----a15a8949da02---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Gatsby Design Labs - Medium</title>
            <link>https://medium.com/gatsby-design?source=rss----a15a8949da02---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:31:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/gatsby-design" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Design Snacks]]></title>
            <link>https://medium.com/gatsby-design/design-snacks-d11d395efce2?source=rss----a15a8949da02---4</link>
            <guid isPermaLink="false">https://medium.com/p/d11d395efce2</guid>
            <dc:creator><![CDATA[Raisa Gates]]></dc:creator>
            <pubDate>Fri, 11 Mar 2022 17:28:06 GMT</pubDate>
            <atom:updated>2022-03-11T19:52:50.455Z</atom:updated>
            <content:encoded><![CDATA[<h3>The quest to create engaging design artifacts</h3><p>I’ve always struggled to consistently share design work with my development team. In the past, I’ve created design docs as a way to communicate the status of long-running projects and document every step of my design decision-making process.</p><p>Initially confused that no one wanted to spend hours reading through my process work, I realized that my design links and walls of text weren’t suited for busy developers.</p><p>Designing <em>how</em> I present my work is arguably just as important as the work itself. When I clearly communicate the user story and the type of feedback I’m looking for, the quality of feedback I receive is better. My dev team is just as much a user to me as the customers I’m designing for.</p><h3>Enter Design Snacks</h3><p>I like to think of Design Snacks as bite-sized takeaways that highlight important design exploration or research quotes that my team may find valuable. It’s an artifact I can share every week to let people know what’s coming around the bend, keeping my team curious but not overwhelmed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jJ6f39B6BWDsDc3xpUt_RA.png" /></figure><h3>What are the ingredients to a tasty snack?</h3><h4><strong>Early explorations without expecting feedback</strong></h4><p>I wanted to showcase small interactions and early work without expecting any feedback from my team. Don’t get me wrong: feedback is always welcome in the design world. But pressuring my team to always have an opinion can ruin the enjoyment of seeing the design process unfold and getting quick insights into my process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UKwY7x0loLZ8w8BlOXefyw.png" /></figure><h4><strong>A quote or two from user interviews</strong></h4><p>Not everyone has time to read through my research takeaways. (Sometimes I can’t even read through my colleagues’ takeaways.) Instead, I highlight quotes and link to the full takeaway for those who want to learn more.</p><p>My research often highlights areas of improvement, but over time, I’ve started to incorporate more positive quotes, too. Positive feedback creates momentum and makes for tastier snacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D8_2v_extOK1iXTn-stu5w.png" /></figure><h4><strong>Adding novelty into the format</strong></h4><p>To emphasize the exploratory nature of what I’m sharing and introduce a little fun, I’ve departed from Gatsby’s main brand and created Design Snacks-specific illustrations and colors.</p><p>Figma helps me create fun surprise interactions and nudges me away from writing walls of text. As a designer, I can present my work in a way that’s unique, engaging, and hopefully fun!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*igcPRH07HSV6rysHHD4ArQ.png" /></figure><h3>How has it helped me and my team?</h3><h4><strong>Personal accountability</strong></h4><p>A weekly cadence of sharing my work has helped keep me accountable to the deadlines I set for myself. I can’t procrastinate as often if I’m due for sharing a snack. Don’t worry, I’m not a saint — I still procrastinate and keep cookies to myself, just not as often.</p><h4><strong>It’s a conversation starter</strong></h4><p>It’s easy for me to avoid sharing early work with my team because, quite frankly, it’s not good — or so the traumatized print designer still in me would think. I found that when I don’t worry about sharing a complete design, I’m able to focus the conversation on smaller details. This allows me to share design iterations much earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tQeAjZoNR63GikYY1KnjGg.png" /></figure><h4><strong>Visibility on what’s next</strong></h4><p>Sharing designs gets my team excited for the work that’s coming up. They may not be actively thinking about the same user problems as I am, but it gives them the ability to connect my future work with the work they’re developing right now.</p><h4><strong>Bringing my team closer to the user</strong></h4><p>Not everyone can join me for user interviews or read through user insights. Showcasing particular interviews and highlights has been a great way to bring the user to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xgVW0SqLErpwDnIkM42Gtw.png" /></figure><h4><strong>An invite to Design Island</strong></h4><p>Design Island is certainly not Love Island — in fact, it’s quite the opposite. As a single designer on a product squad of many developers, it can feel as though I’m on an island of my own, trying to solve problems. While the island provides space to do deep work, there’s always the risk of perishing in loneliness.</p><p>Design Snacks have helped me close the distance between my island and the passing ship that houses the rest of my squad, acting as an inflatable raft to carry me over. All jokes aside, it’s really easy to feel lonely as a single designer on a squad, and I’ve found design snacks to be a point to connect on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c_UNl9V2SJnyULib7KRYXA.png" /></figure><h3>Have I completed my quest for the perfect design artifact?</h3><p>No, I have not. I think process work is iterative, something that will always be adapting and changing based on how I and my teammates work. So far, Design Snacks have had a great response from my team. While it may not always be the answer, it works right now and that’s good enough for me.</p><p>Stay hungry my friends ❤</p><p>If you enjoyed reading my thoughts on Design Snacks, please reach out to me on Twitter <a href="https://twitter.com/raisajg8s">@raisajg8s</a>. You can also check out some additional design-focused content from the Gatsby design team by visiting our <a href="https://www.gatsbyjs.com/blog/gatsby-design-labs-is-now-on-medium/">index of Gatsby design articles.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/165/1*lxBZVIFTYU0p9A35KalNZQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d11d395efce2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gatsby-design/design-snacks-d11d395efce2">Design Snacks</a> was originally published in <a href="https://medium.com/gatsby-design">Gatsby Design Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we built Gatsby’s user research program]]></title>
            <link>https://medium.com/gatsby-design/how-we-built-gatsbys-user-research-program-ec46a6d681e0?source=rss----a15a8949da02---4</link>
            <guid isPermaLink="false">https://medium.com/p/ec46a6d681e0</guid>
            <category><![CDATA[gatsbyjs]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Gatsby Design Team]]></dc:creator>
            <pubDate>Wed, 12 Jan 2022 17:29:38 GMT</pubDate>
            <atom:updated>2022-01-14T14:46:46.767Z</atom:updated>
            <content:encoded><![CDATA[<h4>User research on a small team can be tough, but building a solid foundation is everything.</h4><figure><img alt="An orange, smiling blob with sunglasses sits above a heading that reads “Gatsby Design Labs,” surrounded by subtle, playful arrows and shapes." src="https://cdn-images-1.medium.com/max/1024/1*jcxNui5z5EOZ7kgHw84qLA.png" /></figure><h3>Our quarterly recap</h3><p>Last year, our design team launched <a href="http://gatsbyjs.com/design-labs">Gatsby Design Labs</a>: a space for us to imagine, explore, and test our ideas about the people that use Gatsby, the people that don’t, and the world in which Gatsby innovates. We’re sharing our biggest research efforts from 2021 — and what we’re cooking up for 2022.</p><figure><img alt="A black and white photo of Albert Einstein on a light yellow grid background, surrounded by playful shapes." src="https://cdn-images-1.medium.com/max/798/1*yLoyU0h_m0Z9tKdhY9g-Sw.png" /><figcaption>According to our friend Einstein, play is the highest form of research.</figcaption></figure><h3>Launching our user research program</h3><p>In 2021, we struggled to run consistent user research. Finding participants for user interviews and usability tests consumed a lot of time, and response rates were low.</p><p>In late September, we launched the Design Labs user research program, aiming to recruit a core group of Gatsby users who want to be kept in the loop on research and test out upcoming designs. More than 40 people signed up, and 14 people participated in interviews and usability tests.</p><p>On behalf of every user we interviewed or tested with, we donated $25 to one of four non-profit organizations in addition to offering $25 of account credit.</p><figure><img alt="Two blue blob characters on a lighter blue background each have a speech bubble: one says “Gatsby has helped me accomplish…” and the other says, “My biggest painpoint is…”" src="https://cdn-images-1.medium.com/max/799/1*woa8oIsjLvL6Qpow_gwfbA.png" /></figure><h3>What we tested</h3><p>We usability tested new designs for features on the product roadmap along with emerging ideas — projects that could be on a future roadmap. Our aim with usability tests was not only to see how people felt about new designs but, more importantly, how they used them. We took that feedback to improve our designs before implementing.</p><p>A few things we prototyped and tested with users last quarter:</p><h4>“Add a site” flow</h4><blockquote>How does an updated “Add a site” flow improve user understanding and adoption?</blockquote><figure><img alt="A cropped section of a UI dialogue that says “Get started with Gatsby Cloud,” followed by a large purple button that says “Start my free trial.”" src="https://cdn-images-1.medium.com/max/797/1*5k7e-48rOi_rJIxve9x62g.png" /></figure><h4>Build queues</h4><blockquote>How might users understand which builds are in their queue?</blockquote><figure><img alt="A cropped section of a user interface showing a user’s build queue on Gatsby Cloud." src="https://cdn-images-1.medium.com/max/797/1*-s3qj5GMugY1RS3WJZwhyw.png" /></figure><h4>Navigation updates to the build view</h4><blockquote>What would a cohesive navigation for builds, PRs, and previews look like?</blockquote><figure><img alt="A cropped section of user interface that features four navigation tabs: production, pull requests, previews, and environments, followed by a list of builds." src="https://cdn-images-1.medium.com/max/797/1*ouLN-XAeeCnvWAgTGrL3Xg.png" /></figure><h4>Environments workflow</h4><blockquote>How might people use a space to test different branches and environments?</blockquote><figure><img alt="A cropped image a UI dialogue titled “Configure Environment,” with two selector inputs for content environments and code branches." src="https://cdn-images-1.medium.com/max/797/1*hSOR83l16mMd50VKS347Jg.png" /></figure><h3>What we learned</h3><p>We gathered great insights from our user research sessions, which resulted in design iterations, roadmap pivots, and revisiting assumptions on what our users need.</p><p>But on a higher level, we learned that even with a dedicated pool of participants, running consistent, targeted research is still a challenge. It requires tenacity. It involves reaching out to users at certain times of the week, sending email reminders before research sessions, and always pairing with a teammate (one to facilitate, one to take notes).</p><p>Most of all, we witnessed the effort it takes to build a solid research practice tailored to Gatsby’s needs. Research might look different for our design team of three than at a larger org with more specialized roles — and that’s the fun part! We’re learning how to conduct effective research together and reap the rewards of talking to the people who use Gatsby.</p><figure><img alt="A colorful, abstract workflow graphic with “developer” and “editor” as points in the workflow." src="https://cdn-images-1.medium.com/max/797/1*LDeervDa-0SMpiRyVOsa2w.png" /></figure><h3>What’s next</h3><p>We’ve done the ground work to establish Gatsby Design Labs. In Q1, we’ll continue user research to support the product roadmap along with a few special projects:</p><h4>More user research</h4><p>Among other initiatives, we plan to test new Gatsby starter designs, understand enterprise account management, and improve the product experience for new Gatsby users.</p><h4>Design system</h4><p>Throughout 2022 we’ll be working with the front-end team to ensure consistent styles and components in our design system, which means a better user experience for everyone.</p><h4>Gatsby Design on Medium</h4><p>Hey… that’s what this is! We’ll keep publishing case studies, reflections, design tips, and more to invite you into Gatsby’s design process. Stay tuned!</p><figure><img alt="An outline of a hand reaching for a square shape sits on a bright purple background, complemented by grid lines." src="https://cdn-images-1.medium.com/max/797/1*ekBOvVNIsr0WIwRP6obguA.png" /></figure><h3>Closing thoughts</h3><p>In 2021 we built the foundation of our research process and our design team. In 2022 we’ll use that foundation to keep exploring, testing, and dreaming bigger for everyone who’s a part of the Gatsby community.</p><p>Cheers to a brand new year! ❤,</p><p>The Gatsby Design Team<br>Raisa, Flo, &amp; Molly</p><figure><img alt="A rounded square, light blue, with a smiling face. This lil’ guy is proud of our progress on Design Labs!" src="https://cdn-images-1.medium.com/max/165/1*bczcMhPAoZhlwG-VEnZsuw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec46a6d681e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/gatsby-design/how-we-built-gatsbys-user-research-program-ec46a6d681e0">How we built Gatsby’s user research program</a> was originally published in <a href="https://medium.com/gatsby-design">Gatsby Design Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>