COVID struck again, the second time, and I spent the entire week at home. I didn\u2019t feel great but somehow pulled through.<\/p>\n\n\n\n
At the end of the week, I felt like I feel after every design sprint: \u2018Wow, how come we aren\u2019t this fast in a regular week?\u2019 While taking notes in one of the testing sessions on Friday, I sketched a sticker saying, \u2018Just do it\u2019 in German. Over the weekend, I finished and sent it to the printer.<\/p>\n\n\n\n
Everyone else working on a product or service is earning their mission patches. In the meantime, without contributions to these, I have to create my own.<\/p>\n\n\n\n
The design sprint wasn\u2019t supposed to be remote. All of us were meant to be in the office. But then, no one was. And still, somehow, we managed to do it. Even last November, when running a design sprint within our Service Standard and Manual team<\/a>, we all made it to the office.<\/p>\n\n\n\n So on Monday morning, we moved things to Miro, with the slide deck to navigate us through the sprint unchanged. I am still building on a distilled \u2018how-to design sprint\u2019 deck that my former colleague Ben created a few years ago.<\/p>\n\n\n\n A design sprint is always excellent for building and testing a realistic prototype within a week. It\u2019s a rapid way to test assumptions and big ideas, an opportunity for a team to learn about and be involved in the design process, and to unite the team\u2019s understanding of the problem.<\/p>\n\n\n\n Design sprints are helpful in some contexts but less so in others, as I said in a tweet some time ago.<\/p>\n\n\n\n