<?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 Jia Gao on Medium]]></title>
        <description><![CDATA[Stories by Jia Gao on Medium]]></description>
        <link>https://medium.com/@jiagaoclub?source=rss-7271119353f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ucKMFO7g8CYANIZLOCLq9Q.png</url>
            <title>Stories by Jia Gao on Medium</title>
            <link>https://medium.com/@jiagaoclub?source=rss-7271119353f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:48:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jiagaoclub/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[Tips for Running a Remote Design Sprint]]></title>
            <link>https://medium.com/@jiagaoclub/tips-for-running-a-remote-design-sprint-5060a8d8dfae?source=rss-7271119353f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5060a8d8dfae</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-sprint]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Jia Gao]]></dc:creator>
            <pubDate>Mon, 15 Aug 2022 17:43:32 GMT</pubDate>
            <atom:updated>2022-08-15T17:43:32.829Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design collaboration at large</h3><p>The landscape of design collaboration has changed through WFH — less physical sticky notes on a white board, and more “hey, you’re on mute!” discourse.</p><p>It’s been quite an adjustment for all of us product designers out there, because our role relies heavily on working closing with stakeholders and users.</p><p>For some background, I work at <a href="https://www.autodesk.com/">Autodesk</a>, a company with a large spread of software products, complex systems, and varied customer segments. It’s been a continuous adjustment collaborating in such a big (and remote) organization, since my previous roles have been at startups with far less process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KIAhfzH8d0qNZVyYSJlNvw.jpeg" /></figure><h3>Creating opportunity for design thinking</h3><p>Earlier this year, I led a <em>remote</em> design sprint as a way to bring my team together, build trust, and ultimately, have a shared alignment on strategy moving forward.</p><p>For those of you who are less familiar with what a design sprint is, it’s typically a week long process that uses design thinking, prototyping, and user testing to answer critical open questions within the product and business. It’s way shorter than a standard development cycle, and it’s far less risky and expensive.</p><p>Learn more here:</p><p><a href="https://www.gv.com/sprint/">The Design Sprint - GV</a></p><p>It definitely took me additional research, time, and coordination to pitch, plan, and run a digital design sprint at a large organization, compared to my past IRL experiences at smaller companies.</p><p>I thought I’d share my experience to help guide you on how to make your own remote design sprint as successful as possible, especially now that we’re working together through a screen more than ever before.</p><p>Let’s break this down into 3 main steps.</p><h3>1) Pitching</h3><p>Before getting pumped about all of the details in a design sprint, there may be some persuasion to do. Whether that’s a pulse check on interest from your direct team (who will likely participate), or leadership buy-in, it’s important to identify who your audience is and why they might consider a design sprint.</p><h4>Tip 1: Identify who you need to convince, and figure out what it is that they care about</h4><p>By knowing how a design sprint may take part in solving someone’s top-of-mind problems at work, or significantly impact a team’s future roadmap, you can leverage your pitch in a way that will persuade your audience.</p><p>Hell, maybe you work for a place that knows near to nothing about the value of design thinking. Setting that context on the “why” with successful case study examples or sharing links to resources will help ease concerns that come up.</p><p>Knowing your audience will also inform the best way to sell the idea. If you’re comfortable with your immediate team members and already have their trust, a casual meeting topic could be enough. If there’s more process and bureaucracy involved with top down approval, a deck might be a better medium.</p><h4>Tip 2: Know the answers to the following questions:</h4><ul><li>What is a design sprint?</li><li>Why should we use this methodology?</li><li>Why should we do this <em>now?</em></li><li>How will this benefit me (or my team)?</li><li>What tradeoffs (identify the opportunity cost) would we be making by accommodating this sprint?</li></ul><p>These questions will come up directly or not so directly. You will be the point person to answer them. Doing this pre-work beforehand isn’t glamorous, but it saves time and emotional energy in the long run.</p><h3>2) Planning</h3><p>Let’s say majority vote is a yes to the design sprint (yay). The next step is planning an agenda to make sure things not only go smoothly, but more importantly, that you get the most bang for your buck from the time together.</p><h4>Tip 3: Consider your constraints and plan accordingly</h4><p>People have doctors appointments, kids to tend to, or their excitement simply burns off in 48 hours. By taking the time to consider human things like this, your agenda will be more realistic, and your end goal will be more feasible.</p><p>Here are things that I determined before jumping into logistical day-to-day details:</p><ul><li>Who is involved (we need commitment)</li><li>The ultimate goal we want to achieve (refine the problem upfront so there’s less talking and more doing)</li><li>What digital tools to use (make sure everyone has the proper set up)</li><li>What homework to do (ensure everyone has the knowledge of the problem space to succeed)</li></ul><h4>Tip 4: Get cross-functional members involved early to gain trust and build hype</h4><p>There’s a direct team that you want participating in a design sprint, usually a couple of designers, a product person, an engineer, a researcher, and someone customer facing. A group that’s small and nimble (no more than 7).</p><p>However, that does not mean you shouldn’t involve more cross-collaborative folks leading up to the week of the sprint.</p><p>Being at a large corporation, it’s easy to blow a vision too far out into the future (will the world even exist by then?), or try to fix every user need. To help prioritize and focus on a more defined problem area, a UX researcher and I put together an exercise where each participant got a certain amount of money (fake, unfortunately) to bid on product opportunities based off of market segments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nBzjTtVp6omU2FR6mNqGPA.png" /><figcaption>Unfilled, zoomed-in example</figcaption></figure><p>We sent these FigJam boards out like surveys — to people in sales, customer support, deployment specialists, peers in other groups, and leadership. People who have different pulses on what the demands are, what the competitive landscape is like, and where we as a company stand out.</p><p>We then added up the total sums across all of the opportunities to create a stack ranked list.</p><p>The best part about doing something like this is that you gain visibility and traction for the sprint, collect diversity of thought, and spread the power of design (corny, I know) in a relatively passive way.</p><h3>3) Facilitating</h3><p>Phew! Now for the actual sprint. I cannot stress the importance of over communicating. People have a lot more energy and enthusiasm to extend when they have a clear direction on what they need to do, and agree on what success looks like.</p><h4>Tip 5: Communicate purpose and ownership everyday</h4><p>I recommend setting up a temporary Slack channel just for the design sprint, so that all related conversations are centralized and not lost in the daily shuffle. Prior to the start of each day, I communicated through our dedicated channel how the agenda was structured, who was assigned what role, and what the goal of the day was.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tEMF0YF9i6c1eanITajycw.png" /><figcaption>Slack screenshot, announcing the day’s schedule</figcaption></figure><p>As you can see, I inserted time for breaks and lunch, and we did half days for the entire week. Screen and Zoom fatigue is real, and this allowed the team to have some recovery time in the afternoon. Also, by switching out roles everyday, each person had the chance to yield their decision maker powers, or become the fastest typing note taker there ever was, or politely yell “1 minute left!” at the end of an ideation session.</p><h4>Tip 6: Consolidate insights</h4><p>The end of a design sprint feels like a fever dream. So many quick decisions made, scrappy drawings, and notes to sift through. It’s important to gather all of this documentation, organize it, and synthesize it. For our team, there was impact both from a cultural standpoint and from a business perspective.</p><p>From a people lens, it brought us closer together. We had an open sharing session halfway through the week to express any concerns or feelings that had come up. A manager said it was the first design sprint they’ve participated in since the startup they joined was acquired by Autodesk. Others got over the fear of sharing their sketches. Overall, it invited non-designers to participate in design thinking and storytelling without any judgment.</p><p>From a business point of view, we were able to solicit a ton of feedback in a very short amount of time. At the end of the week, we had a clickable prototype that we used to test multiple concepts with 5 participants. After synthesizing those interviews, we had a good sense of how to prioritize initiatives for our next half from the broader themes.</p><h4>Tip 7: Share it broadly</h4><p>The design sprint gave us a chance to step back, and look at our product more holistically. I consolidated all of the insights into a PowerPoint and presented it to multiple groups within the company. This then cascaded and brought forth more conversations across teams and functions.</p><p>The overarching learning from this whole experience for me was that, if you think there’s an opportunity for change or impact within your team, go for it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5060a8d8dfae" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>