AI Design Sprint

What is an AI Design Sprint?

An AI Design Sprint is a time constrained workshop.

An AI design sprint combines the exercises from a classic Design Sprint and an AI opportunity workshop.
During a design sprint, the team focuses on a specific task or process for a specific user group to enhance with AI and finds the best ideas to validate.
Just like regular Design Sprints, the team sets a measurable outcome to improve – both to serve as a guiding light and to look back at the impact after implementation.
Design Sprints have shown to save up to 7x time and 2x budget spent compared to the normal way of working.

AI Design Sprint day by day

Bringing together a cross-functional team for an intense period of ideation, prototyping and validation of specific AI ideas to a specific challenge The difference between doing the sprint as 3 days instead of 4 days is that there will be less time for ideation and sketching, and you may have some longer and more intense days.

1. Understand

On the first we stay in the problem space, challenging our understanding of the problem.

Expert interviews
User journey mapping with AI ideation

2. Ideate

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

Elaborating on AI ideas
Sketching
Voting
Storyboarding

3. Prototype

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

Usability test preparations
Prototyping using AI prototyping tools

4. Test

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

Usability testing
Retrospective

‍

1. Understand and ideate

On the first we stay in the problem space, challenging our understanding of the problem before ideating and sketching solutions together.

Expert interviews
User journey mapping
with AI ideation
Elaborating on AI ideas
Sketching
Voting
Storyboarding

Abstract illustration with a smartphone and some shapes that float around it

2. Prototype

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

Usability test preparations
Prototyping using AI prototyping tools

Abstract illustration with some bubble talks

3. Test

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

Usability testing
Retrospective

1. Understand

We challenge our understanding of the problem and hone in on how AI opportunities can improve the user journey.

2. Ideate

We gather inspiration to ideate and sketch out the most impactful AI ideas.

3. Prototype

We prepare for the test in parallel with prototyping the solution using AI prototyping tools.

4. Test

We test the prototype with real users to validate or reject ideas and round off the sprint together.

What makes a good North Star?

It expresses value

We can see why it matters to customers

It’s actionable

We can take action to influence it

It’s not a vanity metric

We can be confident that the change is meaningful and valuable

It’s a leading indicator of success

It predicts future results, rather than reflecting past results

It’s understandable

Language that non-technical partners can understand

It represents vision and strategy

Our company’s product and business strategy are reflected in it

It’s measurable

We can instrument our product to track it

Run a AI Design Sprint

An AI Design Sprint is a time constrained workshop.

A successful AI Design Sprint starts well before day one and continues beyond the final test. Clear goals, the right participants, and a structured approach are key to making the most of the process. By preparing thoroughly, collaborating effectively during the sprint, and acting on the results afterward, teams can turn promising AI concepts into real, validated solutions.

Understand, Define, Prototype, Validate

3-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 AI Design Sprint. Before going into an AU Design Sprint, we encourage you to use our AI 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. An AI Sprint Challenge should clearly state which user group you are targeting, which main task or process you are looking to enhance with AI 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 user test participants. 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, but it is usually always a good idea to include actual users/customers.
As for the user test participants, they should be a diverse group focused on the people that will perform the new and/or improved task. The AI 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 the AI Design Sprint, for instance using our Mural template which contains all the recommended exercises in chronological order.

‍

Understand - The first day is mainly spent interviewing experts, ensuring we have framed our Sprint Challenge correctly and mapping out the optimal user journey.

Ideate - 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.

Prototyping and test preparation - 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 using an AI prototyping tool. 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.

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. Retrospective

The last part of the sprint should be used evaluating the usability tests as well as the overall success of the sprint weighed against the sprint challenge.

‍

After

6. Follow up on the sprint 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.

‍

7. Iterate

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 or even run the sketching exercises again. If changes are minor, that might not be needed but sometimes a good idea takes 3 sprints to be ready for implementation.

‍

8. Create tickets for development

Once the prototype is ready, teams can move on to development as they would with other features.

‍

Before

1. Plan the AI Design Sprint. Before going into an AU Design Sprint, we encourage you to use our AI 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. An AI Sprint Challenge should clearly state which user group you are targeting, which main task or process you are looking to enhance with AI 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 user test participants. 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, but it is usually always a good idea to include actual users/customers.
As for the user test participants, they should be a diverse group focused on the people that will perform the new and/or improved task. The AI 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 the AI Design Sprint, for instance using our Mural template which contains all the recommended exercises in chronological order.

‍

Understand - The first day is mainly spent interviewing experts, ensuring we have framed our Sprint Challenge correctly and mapping out the optimal user journey.

Ideate - 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.

Prototyping and test preparation - 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 using an AI prototyping tool. 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.

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. Retrospective

The last part of the sprint should be used evaluating the usability tests as well as the overall success of the sprint weighed against the sprint challenge.

‍

After

6. Follow up on the sprint 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.

‍

7. Iterate

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 or even run the sketching exercises again. If changes are minor, that might not be needed but sometimes a good idea takes 3 sprints to be ready for implementation.

‍

8. Create tickets for development

Once the prototype is ready, teams can move on to development as they would with other features.

‍

Before

1. Plan the AI Design Sprint. Before going into an AU Design Sprint, we encourage you to use our AI 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. An AI Sprint Challenge should clearly state which user group you are targeting, which main task or process you are looking to enhance with AI 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 user test participants. 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, but it is usually always a good idea to include actual users/customers.
As for the user test participants, they should be a diverse group focused on the people that will perform the new and/or improved task. The AI 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 the AI Design Sprint, for instance using our Mural template which contains all the recommended exercises in chronological order.

‍

Understand - The first day is mainly spent interviewing experts, ensuring we have framed our Sprint Challenge correctly and mapping out the optimal user journey.

Ideate - 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.

Prototyping and test preparation - 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 using an AI prototyping tool. 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.

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. Retrospective

The last part of the sprint should be used evaluating the usability tests as well as the overall success of the sprint weighed against the sprint challenge.

‍

After

6. Follow up on the sprint 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.

‍

7. Iterate

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 or even run the sketching exercises again. If changes are minor, that might not be needed but sometimes a good idea takes 3 sprints to be ready for implementation.

‍

8. Create tickets for development

Once the prototype is ready, teams can move on to development as they would with other features.

‍

Before

1. Plan the AI Design Sprint. Before going into an AU Design Sprint, we encourage you to use our AI 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. An AI Sprint Challenge should clearly state which user group you are targeting, which main task or process you are looking to enhance with AI 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 user test participants. 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, but it is usually always a good idea to include actual users/customers.
As for the user test participants, they should be a diverse group focused on the people that will perform the new and/or improved task. The AI 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 the AI Design Sprint, for instance using our Mural template which contains all the recommended exercises in chronological order.

‍

Understand - The first day is mainly spent interviewing experts, ensuring we have framed our Sprint Challenge correctly and mapping out the optimal user journey.

Ideate - 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.

Prototyping and test preparation - 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 using an AI prototyping tool. 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.

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. Retrospective

The last part of the sprint should be used evaluating the usability tests as well as the overall success of the sprint weighed against the sprint challenge.

‍

After

6. Follow up on the sprint 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.

‍

7. Iterate

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 or even run the sketching exercises again. If changes are minor, that might not be needed but sometimes a good idea takes 3 sprints to be ready for implementation.

‍

8. Create tickets for development

Once the prototype is ready, teams can move on to development as they would with other features.

‍

Before

1. Plan the AI Design Sprint. Before going into an AU Design Sprint, we encourage you to use our AI 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. An AI Sprint Challenge should clearly state which user group you are targeting, which main task or process you are looking to enhance with AI 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 user test participants. 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, but it is usually always a good idea to include actual users/customers.
As for the user test participants, they should be a diverse group focused on the people that will perform the new and/or improved task. The AI 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 the AI Design Sprint, for instance using our Mural template which contains all the recommended exercises in chronological order.

‍

Understand - The first day is mainly spent interviewing experts, ensuring we have framed our Sprint Challenge correctly and mapping out the optimal user journey.

Ideate - 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.

Prototyping and test preparation - 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 using an AI prototyping tool. 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.

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. Retrospective

The last part of the sprint should be used evaluating the usability tests as well as the overall success of the sprint weighed against the sprint challenge.

‍

After

6. Follow up on the sprint 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.

‍

7. Iterate

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 or even run the sketching exercises again. If changes are minor, that might not be needed but sometimes a good idea takes 3 sprints to be ready for implementation.

‍

8. Create tickets for development

Once the prototype is ready, teams can move on to development as they would with other features.

‍

Before

1. Plan the AI Design Sprint. Before going into an AU Design Sprint, we encourage you to use our AI 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. An AI Sprint Challenge should clearly state which user group you are targeting, which main task or process you are looking to enhance with AI 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 user test participants. 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, but it is usually always a good idea to include actual users/customers.
As for the user test participants, they should be a diverse group focused on the people that will perform the new and/or improved task. The AI 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 the AI Design Sprint, for instance using our Mural template which contains all the recommended exercises in chronological order.

‍

Understand - The first day is mainly spent interviewing experts, ensuring we have framed our Sprint Challenge correctly and mapping out the optimal user journey.

Ideate - 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.

Prototyping and test preparation - 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 using an AI prototyping tool. 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.

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. Retrospective

The last part of the sprint should be used evaluating the usability tests as well as the overall success of the sprint weighed against the sprint challenge.

‍

After

6. Follow up on the sprint 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.

‍

7. Iterate

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 or even run the sketching exercises again. If changes are minor, that might not be needed but sometimes a good idea takes 3 sprints to be ready for implementation.

‍

8. Create tickets for development

Once the prototype is ready, teams can move on to development as they would with other features.

‍

Resources

To run an AI Design Sprint you need a set of artefact documents, which you can find in the resources below.

AI Design Sprint board

Follow this day-by-day exercise schedule in a full 4-day format for a meaningful and efficient sprint.

‍

AI Design Sprint light board

Follow this day-by-day exercise schedule in a condensed 3-day format for faster, more focused results.

AI Design Sprint Plan (regular)

AI Design Sprint Plan (light)

Usability Test Script

Score card

Usability testing tips and tricks

Design Sprint course

Usability Testing course

Tool recommendations

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.

Google Docs

Create, and collaborate on online documents. Edit together with secure sharing in real-time and from any device.

Google Sheets

Create and edit online spreadsheets. Get insights together with secure sharing in real-time and from any device.

Google Meet

Real-time meetings using your browser, share your video, desktop, and presentations with teammates and customers.

Mural

Mural offers both a shared workspace and training, a practical way to collaborate that anyone can learn and apply.

Google Gemini

Google's AI assistant. Get help with writing, planning, brainstorming, and more.

Visma GPT

A secure, company-approved AI assistant that helps Visma employees work more efficiently by providing answers, ideas, and content without training on user data.

Replit

An online platform for quickly prototyping, building, and running code directly in your browser.

Lovable

A tool for quickly prototyping and building software using AI to generate code, designs, and app logic.

Figma Make

A collaborative tool for rapidly prototyping and designing AI-driven ideas directly in Figma.

Success stories

Knowledge is meant to be shared. Explore the cards below to learn more about how companies around Visma have leveraged their teams to work better with turning data into insights.

North Star

Lessons from Dinero: How to operationalise your product strategy with a North Star

North Star

Lessons from ProActive: How to engage teams with an inspiring North Star

North Star

Lessons from ProActive: How to successfully implement and follow up on a North Star

Design Sprint

Lessons from Silverfin: How to ensure adoption of AI features with Design Sprints

Design Sprint

From Mockup to pNPS UP in Visma Recruit

North Star

Lessons from Ecare: How to help customers thrive with a meaningful North Star

Design Sprint

Lessons from Viskan: How to speed up product development and foster collaboration with Design Sprints

Product Strategy Sprint

Lessons from Flex: How to place your bets with the Product Strategy Sprint

Design Sprint

How to drive innovation and transform a team in 4 days

Design Sprint

How to win a €3.2 million deal without writing a single line of code

Product Vision Sprint

Lessons from Resolve: How to unite teams and create a foundation for the future with Product Vision Sprint

Design Sprint

Cloud accounting software built for small businesses

Validate ideas for AI with

AI Design Sprint

What is an AI Design Sprint?

AI Design Sprint day by day

Design Sprint achievements

400 kEUR ARR

+20 pNPS

+3 customers

What makes a good North Star?

Run a AI Design Sprint

Resources

AI Design Sprint board

AI Design Sprint light board

Tool recommendations

Is your success story next?

Unlocking Rapid Innovation: The Power of Design Sprints

Success stories

Lessons from Dinero: How to operationalise your product strategy with a North Star

Lessons from ProActive: How to engage teams with an inspiring North Star

Lessons from ProActive: How to successfully implement and follow up on a North Star

Lessons from Silverfin: How to ensure adoption of AI features with Design Sprints

From Mockup to pNPS UP in Visma Recruit

Lessons from Ecare: How to help customers thrive with a meaningful North Star

Lessons from Viskan: How to speed up product development and foster collaboration with Design Sprints

Lessons from Flex: How to place your bets with the Product Strategy Sprint

How to drive innovation and transform a team in 4 days

How to win a €3.2 million deal without writing a single line of code

Lessons from Resolve: How to unite teams and create a foundation for the future with Product Vision Sprint

Lessons from Giant Leap: How to go to market with confidence with Design Sprints

Get in touch with our team

Product Discovery

Workshop Facilitation

Product Analytics

Playbook

Success Stories

Resources