Design Sprint 2.0

What is a Design Sprint?

A Design Sprint is a time constrained, five phase process that uses design thinking to reduce the risk when bringing a new product, service or feature to the market.

A Design Sprint 2.0 takes product teams from hypothesis to usability tested prototype in just four days
During a Design Sprint, the team works to improve the experience for a specific user group performing a specific task with the goal of reaching a desired, measurable outcome
Design Sprints have shown to save up to 7x time spent and 2x budget spent compared to the normal way of working
Success stories include companies winning tenders without writing a single line of code, drastically improving their customer satisfaction metrics and increasing their UX and innovation maturity as a result of sprints

Design Sprint process

Bringing together a cross-functional team for an intense week of ideation, prototyping, and validation of potential solutions to a specific challenge.

Illustration that represents a light bulb

1. Understand

On the first we stay in the problem space, challenging our understanding of the problem.This is some text inside of a div block.

Illustration that represents some working tools

2. Ideate

On the second day we gather inspiration, ideate and sketch solutions together.

Illustration that represents a futuristic mobile interface

3. Prototype

On the third day we turn the most voted sketches into a prototype and prepare to meet the users.

Illustration that represents some bubble talks

4. Test

On the fourth and final day we test the prototype with users and round off the sprint together.

How it works

Research shows that Design Sprints enables teams to save 7x the time and 2x the budget compared to their normal way of working. Success stories include companies winning tenders without writing a single line of code, drastically improving their customer satisfaction metrics and increasing their UX and innovation maturity as a result of sprints.

A Design Sprint is a time constrained, five phase process that uses design thinking to reduce the risk when bringing a new product, service or feature to the market.

Understand

Define

Prototype

Validate

4 days

Product Manager and/or Product Owner (Decider), Business Analyst, UX Designer, Developer, Quality assurer, Support, Marketing, Sales, Integration consultant

Before

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.

‍

During

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.

‍

After

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.

‍

Tips

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 and Prioritisation canvas to do it.

Learn more

Mural template
Crash course in Design Sprint (internal training)
Design Sprint 2.0 explained - AJ Smart (video)
Design Sprint day by day - The Sprint book (article and video)
Design Sprint day by day (internal presentation and articles)
A 4 minute facilitator’s guide (video) – Nielsen Norman Group‍
Energizers and icebreakers (video) – Nielsen Norman Group

This is some text inside of a div block.

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

No items found.

Before

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.

‍

During

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.

‍

After

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.

‍

Tips

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 and Prioritisation canvas to do it.

Learn more

Mural template
Crash course in Design Sprint (internal training)
Design Sprint 2.0 explained - AJ Smart (video)
Design Sprint day by day - The Sprint book (article and video)
Design Sprint day by day (internal presentation and articles)
A 4 minute facilitator’s guide (video) – Nielsen Norman Group‍
Energizers and icebreakers (video) – Nielsen Norman Group

Templates

Ultimately, the choice of design tool depends on the specific needs of the designer and the project at hand. Each tool has its strengths and weaknesses, and designers must consider factors such as cost, ease of use, and collaboration features when selecting the best tool for their needs.

Design Sprint 2.0 board

Follow this day-by-day exercise schedule for a meaningful and efficient Design Sprint.

Design Sprint Plan

Usability test script

Score card

Design Sprint 2.0 board

Usability testing tips and tricks

Video intro

Tool recommendations

Below you will find some tool recommendations, but please note that you are free to choose whatever tool you prefer. For some tools we have group wide licenses, in which case access can be requested via licenses@visma.com. Remember that you always need cost approval from your immediate manager.