Note: My following article presupposes that you know the Design Sprint process. If you don’t, please look them up first.
The GV’s design sprint recipe is a standard framework that can be used for answering critical business decisions, may be a MVP for a product or to re- brand an organisation . The 3-day or the 5-day recipe is very specific for a face-face group session but often times your design sprint team will be spread across the globe. The straight forward solution would be to assemble the sprint team in one place but that isn’t very practical when organisations looking using design sprint to achieve fast forward design solution. So, there is always a need to run the design sprint with remote teams. Although, initially it was challenging for me the more sprints I run the better I started getting at it and I think it is now is the perfect time for me to share my process and tips for running a successful remote design sprint.
The step by step sprint planning works perfectly for a remote sprint too but I had to do slight adjustment and add extra steps as below.
Step 1: Write a Sprint Brief
Step 2: Collect or Conduct User Research
Step 3: Recruit and schedule users for usability testing (this is for day 3 usability testing phase)
Step 4: Assemble your Sprint team
Step 5: Plan the Lightning Talks
Step 6: Create a Deck
Step 7: Find the Right Space
Step 7: Identify a virtual collaborating tool (Mural, Realtime board etc), meeting tool(zoom)and online timer.
Step 8: Get the Supplies
Step 8: Prepare and give the sprint team access to the virtual board.
Step 9: Choose a Good Ice Breaker
Step 10: Set the Stage at the beginning of the Sprint
Here is the checklist that you can share with your participants before actual sprint starts
With remote participants the biggest challenge is the time difference, when the sprint team is distributed across different time zone it will be a challenge to identify a reasonable time that suits all the team members. In my case we had few sprint team members in office and most of them located remotely. So, it’s not purely a remote sprint but a mix of both. After many trial and error am currently sticking to a 3hour sprint per day. The image below shows the schedule I follow for each day. Since we utilise only 3 hours out of the entire day recommended by GV there will a bit of homework for the team members to do offline before we assemble the next day. They also need to get access to the virtual boards few days ahead of the first day of sprint so each member is aware of what to expect.
Preparing the white board is very important because it helps us effectively utilise the 3hr spent during the sprint. Use a virtual collaboration tool to prepare these whiteboards( I recommend using real-time board). To start with I suggest you use real-time board’s design sprint guide .For topics that fall into lightening talks the team members are expected to add all the information to the board prior to the actual sprint, this helps us keep information in one place and easier for other team members to refer back and add their comments. For example, the image below shows the competitor analysis that was presented during one of our sprints. It had feature comparison across products and before the sprint began, people added some links to articles and product snapshots that they wanted to discuss during the sprint.
When it comes to writing down the how might we’s, we need to guide the team where exactly to place the stickies on the board. The image below shows bounding boxes for the team to place the sticky. During this phase its also common to expect questions and comments from the team like “What is how might we?”, “ I don’t see a value in writing this..” etc. hence it’s a good idea to mention a sample how might we and add few articles that explains “what is how might we” etc , this gives people an opportunity to gain some understanding before they attend the sprint.
How do people vote virtually? Realtime board do have a voting feature within stick notes but when trying to do voting on sketches we had do it slightly different. For my sprints I created different stickers and left them in a corner for people to drag and vote, we can also include colours to indicate priority and if we would like to know who voted for what we can also try stickers with initials. The image below shows the brand sprint that we conducted with voting in it.
This is the most challenging part of running a remote sprint, keeping the team focused is’nt easy and it really helps if you can make the whole process more interesting. It has to be done throughout the process. One of the things I tried was using some avatar stickers people can use to represent themselves virtually. It turned out to be fun for people to be able to pick their avatar and use them in the boards.
Unlike the standard process from the design sprint kit , the validate phase from day 3 was’t feasable on the same day because our users are spread across different regions with different time zones, hence we had to allocate a week for open test sessions and do the testing remotely with users.
Going forward am looking forward conduct more remote design sprints that is more engaging for the team members also optimise my process to get a maximum benefit out of it. Let me know your thought and am very curious to hear you experience conducting a remote design sprints.