Notice: Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the nfd_wpnavbar_setting handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home1/chrismr6/public_html/wp-includes/functions.php on line 6078

Warning: Cannot modify header information - headers already sent by (output started at /home1/chrismr6/public_html/wp-includes/functions.php:6078) in /home1/chrismr6/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/chrismr6/public_html/wp-includes/functions.php:6078) in /home1/chrismr6/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/chrismr6/public_html/wp-includes/functions.php:6078) in /home1/chrismr6/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/chrismr6/public_html/wp-includes/functions.php:6078) in /home1/chrismr6/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/chrismr6/public_html/wp-includes/functions.php:6078) in /home1/chrismr6/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/chrismr6/public_html/wp-includes/functions.php:6078) in /home1/chrismr6/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/chrismr6/public_html/wp-includes/functions.php:6078) in /home1/chrismr6/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home1/chrismr6/public_html/wp-includes/functions.php:6078) in /home1/chrismr6/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":731,"date":"2020-10-26T12:56:51","date_gmt":"2020-10-26T12:56:51","guid":{"rendered":"https:\/\/chrismiles.co\/?p=731"},"modified":"2020-10-27T08:51:42","modified_gmt":"2020-10-27T08:51:42","slug":"how-to-facilitate-a-design-sprint-remotely","status":"publish","type":"post","link":"https:\/\/chrismiles.co\/how-to-facilitate-a-design-sprint-remotely\/","title":{"rendered":"5 Steps to Facilitate a Great Remote Design Sprint"},"content":{"rendered":"Reading Time: <\/span> 6<\/span> minutes<\/span><\/span>\n
\"\"\/
Photo by Gautam Lakum<\/a> on Unsplash<\/a><\/figcaption><\/figure>\n\n\n\n

I love anything that allows me and the team I am working with to break away from their normal day to day, ideate, design and refine. I also not-so-secretly love a bit of a process. Anything that is repeatable can be made into a framework to make your life easier, in my humble opinion.<\/p>\n\n\n\n

A design sprint, therefore, ticks lots of nerdy product and organisational boxes for me.<\/p>\n\n\n\n

A couple of months ago I facilitated a remote design sprint.<\/p>\n\n\n\n

I was nervous\u200a\u2014\u200apartly because I believe that if you\u2019re not nervous, you don\u2019t care enough about what you\u2019re doing, but more specifically because I wasn\u2019t sure how such a collaborative session would work remotely.<\/p>\n\n\n\n

A year ago I\u2019d have said you can\u2019t possibly run such an intensive workshop with so many breakout tasks and discussions remotely, but a year is a mighty long time, as 2020 has proved.<\/p>\n\n\n\n

But here we are\u200a\u2014\u200aforced to realise that remote working can work, and a design sprint is no different\u200a\u2014\u200ait just requires a bit more up-front effort.<\/p>\n\n\n\n

I\u2019ve created this post based on what I learnt from preparing, running and then reflecting on the remote sprint. I hope it helps you to run your own!<\/p>\n\n\n\n

Here\u2019s an overview of 5 prep activities to do, as the word prep would suggest, before the session.<\/p>\n\n\n\n

Communicate set up needs<\/h3>\n\n\n\n

Most office workers are now pretty adept at joining a call, knowing how to share content and avoiding the dreaded \u2018not-on-mute while you\u2019re eating a packet of crisps\u2019 issue. In fact, Zoom entered our lexicon almost overnight in the same way as Uber, Deliveroo and older examples like Hoover and Plaster.<\/p>\n\n\n\n

That being said, don\u2019t assume. It\u2019s going to be important that you can all see and hear each other so ask everyone attending several days in advance to make sure they\u2019ve got all the right digital and physical tools and equipment:<\/p>\n\n\n\n