1. Plan the Design Sprint. Before going into a Design Sprint, we encourage you to use our Design Sprint planning template (make a copy) to settle on the Sprint Challenge, Sprint participants, when the Sprint should take place and which experts and users to book.

‍

2. Settle on a Sprint Challenge. A Sprint Challenge should clearly state which user group you are targeting, which main task you are looking to enable them to do or improve for them and what the desired outcome is. The desired outcome should be measurable. Examples include saving the users time, improving the customer effort score and similar.

‍

3. Book experts and users. Once you have settled on the Sprint Challenge and the intended target group, it is time to book experts and users. Experts can be e.g. internal domain experts, experts within regulations or processes, members of the support team or, if you need to understand the customers and end-users better, they can also be customers and/or end-users. It depends on what you need to learn. As for the users, they should be a diverse group focused on the people that will perform the new and/or improved task. The Design Sprint planning template includes a day-by-day schedule where you will find recommended time slots. 

‍

4. Follow the day-by-day schedule for Design Sprint 2.0, for instance using our Mural template which contains all the recommended exercises in chronological order. 

• Day 1: Understand. The first day is mainly spent interviewing experts, ensuring we have framed our Sprint Challenge correctly and mapping out the optimal user journey. 
• Day 2: Sketching. The second day is mainly spent sketching ideas and voting for the best foundation based on the optimal user journey. The sketches are then used to create a storyboard to make sure all steps of the user journey are covered. 
• Day 3: Prototyping and test preparations. The third day is spent in two groups. One group prepares for usability testing by creating a test script (make a copy) and setting up a scorecard (make a copy). The second group creates the prototype based on the most voted sketches from day two. All team members also make sure to go through some tips and tricks for user interviews and usability testing. The two groups have prototype check-ins throughout the day to make sure that details in the test script and prototype match.
• Day 4: Usability testing. The fourth day is spent usability testing the prototype with five users. One team member facilitates each test, while the other team members take notes and answer the sprint and prototype questions in the scorecard. The team finishes the day with a short retrospective, going through their key findings and what they should focus on next week. 

‍

5. Follow up on the outcome. On top of the short retrospective, we encourage teams to meet up and have a more thorough discussion around the sprint outcome and next steps. 

‍

6. Iterate the prototype if needed. One of the first things many teams do after a design sprint is to update the prototype based on the feedback. If changes are big, we encourage teams to run a few more usability tests. If changes are minor, that might not be needed. 

‍

7. Create tasks in Jira. Once the prototype is ready, teams can move on to development as they would with other features. 

‍

• It can be challenging to run a Design Sprint for the first time. Teams are welcome to request help from Product Discovery Hub. It can be a great way to learn and become self-sufficient. 
• It can be challenging to analyse feedback. We encourage teams to try methods like Thematic analysis (link) and Prioritisation canvas (link) to do it. 

1. Plan the Design Sprint. Before going into a Design Sprint, we encourage you to use our Design Sprint planning template (make a copy) to settle on the Sprint Challenge, Sprint participants, when the Sprint should take place and which experts and users to book.

‍

2. Settle on a Sprint Challenge. A Sprint Challenge should clearly state which user group you are targeting, which main task you are looking to enable them to do or improve for them and what the desired outcome is. The desired outcome should be measurable. Examples include saving the users time, improving the customer effort score and similar.

‍

3. Book experts and users. Once you have settled on the Sprint Challenge and the intended target group, it is time to book experts and users. Experts can be e.g. internal domain experts, experts within regulations or processes, members of the support team or, if you need to understand the customers and end-users better, they can also be customers and/or end-users. It depends on what you need to learn. As for the users, they should be a diverse group focused on the people that will perform the new and/or improved task. The Design Sprint planning template includes a day-by-day schedule where you will find recommended time slots. 

‍

4. Follow the day-by-day schedule for Design Sprint 2.0, for instance using our Mural template which contains all the recommended exercises in chronological order. 

• Day 1: Understand. The first day is mainly spent interviewing experts, ensuring we have framed our Sprint Challenge correctly and mapping out the optimal user journey. 
• Day 2: Sketching. The second day is mainly spent sketching ideas and voting for the best foundation based on the optimal user journey. The sketches are then used to create a storyboard to make sure all steps of the user journey are covered. 
• Day 3: Prototyping and test preparations. The third day is spent in two groups. One group prepares for usability testing by creating a test script (make a copy) and setting up a scorecard (make a copy). The second group creates the prototype based on the most voted sketches from day two. All team members also make sure to go through some tips and tricks for user interviews and usability testing. The two groups have prototype check-ins throughout the day to make sure that details in the test script and prototype match.
• Day 4: Usability testing. The fourth day is spent usability testing the prototype with five users. One team member facilitates each test, while the other team members take notes and answer the sprint and prototype questions in the scorecard. The team finishes the day with a short retrospective, going through their key findings and what they should focus on next week. 

‍

5. Follow up on the outcome. On top of the short retrospective, we encourage teams to meet up and have a more thorough discussion around the sprint outcome and next steps. 

‍

6. Iterate the prototype if needed. One of the first things many teams do after a design sprint is to update the prototype based on the feedback. If changes are big, we encourage teams to run a few more usability tests. If changes are minor, that might not be needed. 

‍

7. Create tasks in Jira. Once the prototype is ready, teams can move on to development as they would with other features. 

‍

• It can be challenging to run a Design Sprint for the first time. Teams are welcome to request help from Product Discovery Hub. It can be a great way to learn and become self-sufficient. 
• It can be challenging to analyse feedback. We encourage teams to try methods like Thematic analysis (link) and Prioritisation canvas (link) to do it. 

1. Plan the Design Sprint. Before going into a Design Sprint, we encourage you to use our Design Sprint planning template (make a copy) to settle on the Sprint Challenge, Sprint participants, when the Sprint should take place and which experts and users to book.

‍

2. Settle on a Sprint Challenge. A Sprint Challenge should clearly state which user group you are targeting, which main task you are looking to enable them to do or improve for them and what the desired outcome is. The desired outcome should be measurable. Examples include saving the users time, improving the customer effort score and similar.

‍

3. Book experts and users. Once you have settled on the Sprint Challenge and the intended target group, it is time to book experts and users. Experts can be e.g. internal domain experts, experts within regulations or processes, members of the support team or, if you need to understand the customers and end-users better, they can also be customers and/or end-users. It depends on what you need to learn. As for the users, they should be a diverse group focused on the people that will perform the new and/or improved task. The Design Sprint planning template includes a day-by-day schedule where you will find recommended time slots. 

‍

4. Follow the day-by-day schedule for Design Sprint 2.0, for instance using our Mural template which contains all the recommended exercises in chronological order. 

• Day 1: Understand. The first day is mainly spent interviewing experts, ensuring we have framed our Sprint Challenge correctly and mapping out the optimal user journey. 
• Day 2: Sketching. The second day is mainly spent sketching ideas and voting for the best foundation based on the optimal user journey. The sketches are then used to create a storyboard to make sure all steps of the user journey are covered. 
• Day 3: Prototyping and test preparations. The third day is spent in two groups. One group prepares for usability testing by creating a test script (make a copy) and setting up a scorecard (make a copy). The second group creates the prototype based on the most voted sketches from day two. All team members also make sure to go through some tips and tricks for user interviews and usability testing. The two groups have prototype check-ins throughout the day to make sure that details in the test script and prototype match.
• Day 4: Usability testing. The fourth day is spent usability testing the prototype with five users. One team member facilitates each test, while the other team members take notes and answer the sprint and prototype questions in the scorecard. The team finishes the day with a short retrospective, going through their key findings and what they should focus on next week. 

‍

5. Follow up on the outcome. On top of the short retrospective, we encourage teams to meet up and have a more thorough discussion around the sprint outcome and next steps. 

‍

6. Iterate the prototype if needed. One of the first things many teams do after a design sprint is to update the prototype based on the feedback. If changes are big, we encourage teams to run a few more usability tests. If changes are minor, that might not be needed. 

‍

7. Create tasks in Jira. Once the prototype is ready, teams can move on to development as they would with other features. 

‍

• It can be challenging to run a Design Sprint for the first time. Teams are welcome to request help from Product Discovery Hub. It can be a great way to learn and become self-sufficient. 
• It can be challenging to analyse feedback. We encourage teams to try methods like Thematic analysis (link) and Prioritisation canvas (link) to do it.