Remote Design Sprint: This is how we do it
Tags: ux, designsprint, remoteworkshop, cngroup
Published: 2021-07-30 10:40:19

<b>Did you know that you can have your ideas tested by a high-fidelity prototype in only 5 days? You have a vision, we have a magical tool called The Design Sprint. Here we describe how we run it in CN Group. </b>

What you will find in this article:
</br>
<ul>
  <li>what is a Design Sprint?</li>
  <li>how to get to amazing results in 5 days</li>
 <li>what you need to prepare</li>
 <li>the best thing about the Design Sprint</li>
 <li>what comes after the Design Sprint</li>
</ul>

<h2>What is a Design Sprint?</h2>
<p>The Design Sprint is a step by step design process created by Google Ventures to help prototype and validate ideas. Before investing money into developing a minimum viable product we can prototype your idea and see if it makes sense to the users first.</p>

<p>
We go from <em> nothing </em> to a <b>high-fidelity prototype.</b> But to get there, we need to do many short exercises and activities. Don’t worry, most people find them intriguing and a lot of fun! <b>1 team. 1 week. 1 challenge.</b>
</p>

<img src="https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vjt1ohivz8irofasvnni.png" alt="One week of design sprint" />

<p>
There are many ways to run the Design Sprint. It can take 4 or 5 days. Since we have done over 30 of them in CN Group here is our advice how to get the best out of this method. We encourage you to <b>clear your schedule and invest the time for all 5 days of the Design Sprint.</b> Everything takes time. This way, we will have more time for creating a shared understanding of the problem and, most importantly, for prototyping. We can run it face to face or remotely. Due to the current pandemic I would like to describe the process of the remote version in more detail. Let’s dive in.
</p>

<h2>
“Amazing results in 5 days” is not just a good workout teaser
</h2>

<p>
Day by day. From Monday to Friday. Here is a brief summary of what you can expect to get through during the week of the Design Sprint.
</p>

<img src="https://dev-to-uploads.s3.amazonaws.com/uploads/articles/q01m4ai1iyufdvf8smeh.png" alt="What is happening in 5 days design sprint" />

<p>
I know. It seems so easy, it makes you want to rush in and start tomorrow. But wait!
</p>

<h2>
First, you need to prepare
</h2>

<p>
What do I need to prepare, you ask? People, workspace, and the mindset.
</p>

<p><b>You can do it! (Just not alone)</b></p>
<p>Getting from nothing to a testable prototype in one week is not as easy as it sounds (seriously, it is not). Before the Design Sprint you need people to fill in these <b>three roles</b>.
</p>

<p><b>Core team</b></p>
<p>
Usually there are three people from your company and three people from us. It is suggested to diversify your team, so we have people from different departments. A Solution Architect? A Developer? Somebody from customer’s services? The Core team has to be available for the whole week of the Design Sprint. A very important role in the core team is <em>The Decider,</em> somebody from your organisation who makes the important decisions.
</p>

<img src="https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4tcj9y5ip3kd2zblvmqm.png" alt="Face to face design sprint" />

<em>Tip: Decider could be your CEO or the future product owner.</em>

<p><b>Experts</b></p>
<p>
Not everybody who has something to say about the project can be available for the whole week. That’s OK, we only need them for 20 minutes. An Expert is somebody who can give an idea, or a little piece of information, that can take the group outside the box.
</p>

<p>
<em>
Tip: Anybody who knows something about the product or target clients (finances, marketing, …).
</em>
</p>

<p><b> Testers </b></p>
<p>
The whole core team will contribute to the final prototype so obviously we cannot test it by ourselves. We need somebody who has not seen the prototype before. Every tester needs to be available for 45 - 60 minutes on the last day.
</p>

<p>
<em>
Tip: The best tester would be a potential end user of the final product.
</em>
</p>

<h3>Is preparation really the key to success?</h3>
<p>
Nope. But it helps. A lot!
<br><br>
We all know that <b>long meetings can be exhausting and dreadful.</b> That's why preparing in advance is important. It saves time.
</p>

<p>
Before the actual Design Sprint week, we have a short meeting with everybody from the <em>core team to</em>:
<br>

<ul>
<li> <b>introduce</b> ourselves and do a short chit-chat to get to know each other, because for one week we are going to be the closest of co-workers 😊</li>

<li> <b>listen</b> to what you have to say about the challenge
</li>

<li> <b>talk</b> about what you can expect from the Design Sprint
</li>

<li> <b>answer</b> all of your (and their) questions
</li>

<li> <b>show</b> you the tools we are going to use. We use <a href="https://miro.com/">Miro board </a> for a whiteboard, <a href="https://www.microsoft.com/en-ww/microsoft-teams/group-chat-software">Teams</a> for video conference and <a href="https://www.figma.com/">Figma</a> for prototyping
</li>

</ul>
</p>

<h3>Even remotely we run it smoothly</h3>

<img src="https://dev-to-uploads.s3.amazonaws.com/uploads/articles/1b3018pqgljonoheggpm.png" alt="Remote design sprint set up">
<p>
In the picture above you can see <b>literally everything you need for a remote Design Sprint.</b> Usually, during a face to face Design Sprint, you have a room full of whiteboards, flip charts and notes with sketches taped to the walls. Lucky for us (and you) there are already many <b>digital whiteboards that help us to keep all the necessities</b> (pictures, sketches, notes, feedbacks) in one place. Thanks to this wonderful invention we make sure everybody knows what is happening and we can collaborate on exercises just as well as during a face to face meeting. Our option #1:  <em>Miro board</em>. Thanks to <em>Microsoft Teams</em> we have a place for screen sharing (this comes in handy especially during prototyping and testing) & videoconferencing. Not to mention that sharing files and recording user testing is a piece of cake.
</p>

<p><em>Bonus: Using a digital whiteboard prevents you from losing all notes & sketches when your cleaning lady decides the meeting room is a big mess and throws away your notes. (Yes, that happens.)
</em>

<h3>So, what is the key to success?
</h3>

<p>
After the many Design Sprints we have had in CN Group over recent years, we have three most important tips you need to keep in mind:
<ul>
<li>
<b>Focus on the challenge and clear your schedule</b> as much as possible for the actual Design Sprint week, we need your 100% engagement even if it is not a face to face process.
</li>

<li>If something is not crystal clear, ask, comment, communicate, <b> don’t stay muted!</b> 😊
</li>

<li>
<b>Take risks!</b> There will be a time when we all have to decide on what is the most important for the week. Even if you are not an adrenaline junkie, this is the time and place for big risks and adventurous behaviour!
 </li>
</ul>
</p>

<h2>
So… what is the best thing about the Design Sprint?
</h2>

<p>
This is very simple, so here it is: <b>We cannot fail!</b> Whether we manage to deliver on Friday a prototype that is praised by testers, or the users leave confused and sad, we win. If users are happy, you know you are going in a good direction. You will know you have a prototype you can build on, and it’s easy to see that’s a great start for a project! Even if users are not so happy with the prototype and they do not understand everything, you did not spend months implementing it. You spend only five days and you are not starting empty handed, you know what not to do.
</p>

<h2>What comes after the Design Sprint?
</h2>

<p>
Well, that is totally up to you. Some of our customers decide to update the prototype based on the feedback from end users and retest it again. Some of them have solid preparation for starting the project.
</p>

<p>
However usually the next steps are:
<ul>
<li> <b>finetune the prototype </b> based on the feedback from the end users (or finetune the design for views which were not part of the Design Sprint)
</li>

<li> <em>not mandatory but recommended: do interviews with your end users again to review the changes</em>
</li>

<li>
agree with our sales department about conditions for starting a <b>pilot project</b>
</li>

<li>
<b>Project Kickoff!</b> Usually a two day process were we go through the backlog, do the poker planning, discuss Definition of Done and Acceptance Criteria and everything you need to make sure everybody understands the goal of the project
</li>

<li>
Sprint by sprint <b> working on the project with daily communication between the customer and the team.</b>
</li>

</ul>
</p>


<p>
As we already said, this is totally up to you. To sum it up, this is what you have at the end of the Design Sprint:

<ul>

<li>
<b>A high-fidelity prototype</b> that you can share and show to anybody who might be interested
</li>

<li>
<b>video records of usability testing</b> that you can replay and learn from
</li>

<li>
all the <b>ideas, feedback</b> and the whole process <b>captured in a digital whiteboard</b></li>
</ul>
</p>

<h2>
Want to know more?
</h2>

<p>
We recommend reading the book <a href="https://www.thesprintbook.com/">The Design Sprint</a> by Jake Knapp <em>(Transworld Publishers Ltd, ISBN: 9780593076118)</em> from which you can learn everything essential about Design Sprints. You can also <em>contact us,</em> and we can talk about Design Sprint possibilities with our company. We will be waiting and looking forward to the next wonderful Design Sprint experience! See you soon!
</p>