Remote Design Sprint - Writing Sprint Goal & Questions (2021)

[@irennetjokrodinata1194]

You’re amazing Alvin

[@supercoachpauvillanueva2787]

Thank you for your great channel and with a very simple and informative content! Kudos to you, Sir!

[@lakshaygaur2258]

Highly highly useful and insightful content you create. Do make a small documentary kinda video on how you administered the design process for a project. Keep it a brief interesting video. would love to watch it! Thanks for sharing your knowledge!! :D

[@callebe]

Great video! Does the decider participate in these exercises? Does he/she write long term goals too?

[@relabstudios]

Yes they do Callebe 😊

[@AkhileshKumar-hv2gm]

I have a confusion related to Sprint question: 1. I want to know how this is differ from HMW. 2. How this will impact while creating prototype. 3. What purpose we are trying to solve with Sprint question.

[@relabstudios]

Hello Akhilesh! Those are big questions! We’ll try our best to explain. Hope this helps :) 1. Sprint Questions happens during the Goal & Questions session in a Design Sprint, where the participants are only the sprint core team. The purpose of asking these “Can we...” questions is to balance the optimism of the Long Term Goal. Through asking these Questions, sprint teams can uncover potential “blockers” that may prevent the long term goal from happening. Put it this way, the Questions can also keep you grounded, while being all optimistic about your Goal 😉... The HMW on the other hand, is a note taking technique (commonly used in workshops, sprints or even consulting practices). In a Design Sprint setting, the HMW technique is used during the Experts Interview session. This technique allows sprint teams to record interview notes and convert them into a solvable statement. As an example, rather than noting down “I don’t think this colour works”, teams write “How might we find a colour that works?”... simply by doing this, the concern/feedback becomes solvable... 2. The Goal and Questions are critical for sprint teams as they are one of the key artefacts in your weeklong sprint. You can think of them as an anchor to remind you of what your end Goal is and also what the potential risks/blockers may be. By reading the Questions out loud together as a team before getting into other subsequent Design Sprint activities, you are constantly reminded of the Goal and the Risks/Blockers. So to answer your question as to how this will impact your prototype, it will ensure your prototype is consistently relevant to your sprint challenge... your Goal... and also will ensure that you keep the potential blockers in mind, while producing the prototype. If you don’t do this, your prototype can end up being irrelevant or inconsistent with your Goal & Questions... 3. This should have now been answered while explaining points 1 & 2 above 😀

[@AkhileshKumar-hv2gm]

@@relabstudios Many thanks for your superb explanation 👌. It's very helpful with the examples. You are really doing great job🙌☺.

[@patrickcazer]

@@relabstudios Question how does this work if one is attempting a solo design sprint? is the goal the same as what it would be with a team? or would the goal be geared towards a design thinking perspective since its a 1 person project?

[@gorboman]

I've experienced lag whenever I use Miro. Do you also notice this? If yes, is there a workaround that you can suggest?

[@relabstudios]

Yes! Although we have been using Mural most of the time. I think it depends on the type or number of widgets you use at once. Also a few other factors like number of participants and content volume in a board... For Miro, there’s a good article on how you might be able to improve the collaborative board performance here help.miro.com/hc/en-us/articles/360013588560-Tips-to-Improve-Board-Performance Hope this helps Aria!

[@gorboman]

@@relabstudios thanks. I'll give it a read.