Design sprint

Structured process for solving problems and testing/validating ideas in a short time.

Sessions
17
Steps
45
Last edited
Jan 7, 2025
Created by
Nova

About this process

Structured, intensive process for solving problems and testing ideas in a short time. The approach, developed at Google Ventures, aims to help teams quickly prototype and validate concepts, cutting down on the time and uncertainty that typically come with developing new products or features.

The process in detail

17 sessions · 45 steps
01

Introductions

Read the full text
New Board
  • What is a design sprint?
  • A design sprint is a 5-day process for answering key business and organizational questions through design and brainstorming, prototyping, and testing. This process is inspired by the book "SPRINT" developed by Jake Knapp and John Seratsky.
  • We love this book
  • Daily goal
  • Every day you need to reach a big goal and each goal can have multiple work sessions, tasks, and whiteboards. RULES:
  • Follow the process! This process is fun and very effective. Follow the timeline Remove distractions (email, Instagram,etc) You will have breaks (drink water, eat healthy and relax) Ask the facilitator questions Use a video call app. You can use Zoom but we recommend spatial.chat.
  • Questions
  • Add your questions here!
  • One sticky note per question!
02

1.1 - Long term goal

3 steps
  1. 1

    Visualization.

  2. 2

    Without a solution.

  3. 3

    Long term goal.

Read the full text
1. Visualization.

What would happen in 3 months if everything goes perfectly? What would happen in 1 year if everything goes perfectly? What would happen in 5 years if everything goes perfectly?

Write a note
2. Without a solution.

What would happen if you can't find a solution?

Write a note
3. Long term goal.

Write the long term goal. Tip: Highligh the best one or add the answer to the conclusion section.

Write a note
03

1.2 - Questions + Ask experts

2 steps
  1. 1

    🤯 How might we...

  2. 2

    Suitable solution.

Read the full text
1. 🤯 How might we...

Read the "goals and instructions" section before you start and answer the question (or questions) "how might we.." 👇and add one idea per sticky note.

🤯 Think about the minimum criteria, the processes that need to be in place, who needs to be involved, and the strategy that will help ensure its success.

Add sticky notes
2. Suitable solution.

How difficult and suitable will it be to find a solution and implement it successfully?

1 = very easy🤩 🤝and 5 = very difficult. 🤕

Choose one
  • 1 🤩
  • 2
  • 3 🤝
  • 4
  • 5 🤕
04

1.3 - User experience

3 steps
  1. 1

    Tell your story.

  2. 2

    User experience.

  3. 3

    The optimized user experience.

Read the full text
1. Tell your story.

Share your screen and explain your user experience. If you were working with a group - do it as a group. During each group or individual presentation, add a dot sticker on the steps you think are important (you can also use the like functionality) While you are listening to another group, you can also take notes and share your thoughts inside the "highlight" section. Use a sticky note per idea, suggestion, etc.

2. User experience.

You probably have some sticky notes that weren't voted. Select the ones with votes and, as a team, moves them (the voted) to a new area on the board. Merge all the stories by putting all the most voted sticky notes together.

3. The optimized user experience.

So you remember the different "how might we..." answers you collected from different experts? Add them to the user experience and brainstorm about a good way to optimize this experience.

New Board
  • DISCOVER
  • EVALUATE
  • START USING
05

2.1 - Secondary Research

10 steps
  1. 1

    Hypothesis/Challenge

  2. 2

    Gather information

  3. 3

    Understanding findings

  4. 4

    Memo (Optional)

  5. 5

    Meeting conclusion (Optional)

  6. 6

    Editing information to provide a clear overview of the challenge

  7. 7

    Organize the sticky board

  8. 8

    Analyze the board

  9. 9

    Exploring, improvements and staying relevant

  10. 10

    First ideas to overcome the challenge (Optional)

Read the full text
1. Hypothesis/Challenge

What's the hypothesis or challenge? What are you trying to uncover or understand in-depth? Where should I add my hypothesis? Include your hypothesis inside the "Session goals and instructions".

2. Gather information

Learn about the market environment and find information about the topic. Everyone on the team needs to find the most recent news related to the product, problem, or challenge. You and your team can use magazines, journals, newspapers, TV news, etc. Write down sources you will explore to the step note here. You can use the sticky board to add your findings and easily create clusters and group the information that is relevant to your situation, idea or project.

Work on the whiteboardOpen Secondary Research
3. Understanding findings

In this step, the team should discuss those findings and explore further if they consider it is necessary. Possible actions the team can take in this step: 1)Discuss all the findings and add a valuable comment or short memo (move to the next step) or - 2)Add more information to help the team get a better understanding of the situation, or - 3)Reorganize the sticky notes ( Internal, Microenvironment, and Macroenvironment)

Work on the whiteboardOpen Secondary Research
4. Memo (Optional)

Share your findings and thoughts. You can add your memo inside the resources section.

Write a note
5. Meeting conclusion (Optional)

Schedule a call or a meeting to talk about the findings until you get to a conclusion. Send an invitation to that meeting to all the members/participants. When the meeting is completed, the session leader will add a summary and conclusion here.

6. Editing information to provide a clear overview of the challenge

The team leader will determine if the team found enough information. If so, the team leader can move forward to step 7 to better visualize and understand all the findings, or step 11 to finalize the research. What should the team do next?

7. Organize the sticky board

The team leader can start organizing that information and create clusters with sticky notes. Continue the session if you need more information.

Work on the whiteboardOpen Secondary Research
8. Analyze the board

In this step, the team will need to analyze the board and add their thoughts and comments below. If someone in the team thinks it’s important to add new information, this will be the last chance to do that.

Work on the whiteboardOpen Secondary Research
9. Exploring, improvements and staying relevant

Invite everyone to explore interesting findings and alternative solutions to the challenge. For example, they will discuss why certain solutions were created, why some solutions worked or didn’t work, and highlight unique businesses. How did they improve and stay relevant in their marketplace? The team can post to the sticky board.

Work on the whiteboardOpen Secondary Research
10. First ideas to overcome the challenge (Optional)

Check the Yellow Section. Start brainstorming. Follow the "Yes, Maybe, No" canvas to select the ideas/information worth exploring further. Keep exploring those ideas. Notes: In this step, the team can add their final comments and, if possible, their considerations and ideas, responding to the question: How would you create the ideal solution for this market or a segment of this market? What are the first solutions you can think of? This is a quick brainstorming session, so it should normally be a quick step. The goal is to get a quick idea of what the team has in mind. Suggestion: In this step, you can get your team collaborating at the same time for 5-15 minutes and ask each to add 1 to 10 ideas. It usually helps to move things along quickly.

Work on the whiteboardOpen Secondary Research
Open Secondary Research
  • 01 | Secondary Research
  • HIGH TO LOW
  • Organize the sticky notes (findings) based on High Risk/Importance and Low Risk
  • This is a sticky note!
  • This is a sticky note!
  • This is a sticky note!
  • Add findings (summary)
  • Organize your sticky-notes (findings) based on internal environment, micro environment or macro
  • MICRO The immediate small-scale environment of an organism or a part of an organism, especially as a distinct part of a larger environment
  • INTERNAL If we are talking about a company we will talk about the culture, the hiring process, the brand, the values, etc
  • MACRO Macro environment refers to the broader condition of an economy as opposed to specific markets. Called DESTEP OR SWOT (the six forces) Political forces Ecological Forces Technological Forces Socio-Cultural Forces Economic and Demographic forces
  • 02 | Transforming insights into ideas
  • IDEATION
  • Add your ideas on sticky notes
  • Yes (Best Ideas)
  • NO
  • Maybe
  • KEEP EXPLORING THOSE IDEAS
  • How would you create the ideal solution for this market or a segment of this market? What are the first solutions you can think of?
06

2.2 - Lightning demos

2 steps
  1. 1

    Lightning demos.

  2. 2

    Top 3.

Read the full text
1. Lightning demos.

Search products or solutions that you find inspiring and add them to the board. Everyone should choose their favorite one (you can also create groups)

Your goal is to add screenshots inside this whiteboard/section and show everyone inspiring products, services, or experiences.

Tips:

•You can look at other industries.
•Show photos, photos, videos... and tell why you like them.
Upload files or add links
2. Top 3.

Explain why you thing this product, website, service or experience is beautiful, or effective (5 min max per person or group) Once presentations are done, and you have a beautiful inspiring board in front of you, vote your favourite one.

Add notes
07

2.3 - Sketch

3 steps
  1. 1

    Individual sketching - 1:15 min.

  2. 2

    The observant view - 15 min.

  3. 3

    Discussion - 30 min.

Read the full text
1. Individual sketching - 1:15 min.

15 min break. 15 min individual brainstorming: Use a pen and paper. Turn on the music or that song that makes you feel good. Write down those "How might we..." ideas that you thought were surprising, interesting, or inspiring. Start sketching your first ideas. Your sketches don't need to be perfect or beautiful. You don't need to show this to anyone. Try at least sketching 4 different ideas. 45 min developing the solution sketch: Spend the last 30 minutes sketching your proposal. This is the sketch your will be sharing with your team. Once you are already, take a picture and add your sketch to the whiteboard. Add a title and notes. Try to sell your idea. Think of a headline and highlight key features. Make sure your sketch is self-explanatory and will be able to catch people's attention without your intervention. Don't add your name and lock all the elements once you are done. TOTAL: 1:15h ⏰ Mark this step as "complete for me" once you are done. 👌

Work on the whiteboardThe Sketch
2. The observant view - 15 min.

You have 15 minutes to go ever all the solutions (in silence) As if you had laser eyes, you will add dots to those areas you think are interesting. You can use as many dots as you want.

Work on the whiteboardThe Sketch
3. Discussion - 30 min.

Discussion: The facilitator or someone will take the lead and go over each sketch ask questions like: This is interesting: "Who has added this dot here? What made this interesting to you?" I can see a lot of dots here, and I am curious... Can some of you share your thoughts? Vote - 3 dots per person (5 min): Use the yellow dot to vote for a solution. You have 3 yellow dots,** and you can vote 3 solutions or vote one single solution with those dots.

Work on the whiteboardThe Sketch
The Sketch
  • This idea got two votes
  • Title
  • Black bird bike (example)
  • Stakeholders found 3 things interesting.
  • Add notes
  • Add notes
  • VOTES Use the yellow dot to vote this solution.
  • VOTES Use the yellow dot to vote this solution.
  • THINGS CATCHING MY ATTENTION Use the blue dots to mark the areas you find interesting.
  • THINGS CATCHING MY ATTENTION Use the blue dots to mark the areas you find interesting.
  • Title
  • VOTES Use the yellow dot to vote this solution.
  • THINGS CATCHING MY ATTENTION Use the blue dots to mark the areas you find interesting.
  • Title
  • VOTES Use the yellow dot to vote this solution.
  • THINGS CATCHING MY ATTENTION Use the blue dots to mark the areas you find interesting.
  • Title
  • VOTES Use the yellow dot to vote this solution.
  • THINGS CATCHING MY ATTENTION Use the blue dots to mark the areas you find interesting.
  • Title
  • VOTES Use the yellow dot to vote this solution.
  • THINGS CATCHING MY ATTENTION Use the blue dots to mark the areas you find interesting.
08

4.2 - Prototyping Tools

Read the full text
Board
  • Prototyping tools
  • Here are a few tools we love.
  • LOW FIDELITY
  • HIGH FIDELITY
  • SKETCH & DISCUSS A FEW IDEAS
  • STATIC DISPLAY OF WHAT THE FINAL PRODUCT WOULD LOOK LIKE
  • USABLE DESIGN TO EXPLORE THE USER INTERFACE AND TEST THE DESIGN. (INTERACTIVE)
  • https://novatools.org
  • https://www.axure.com/
  • https://www.invisionapp.com/
  • https://balsamiq.com/
  • https://www.figma.com/
  • https://www.hotgloo.com/
  • OTHERS: Photoshop Illustrator Sketch XD
  • https://www.figma.com/
  • https://marvelapp.com/pop
  • https://marvelapp.com/pop
  • EVALUATION - DISCUSS THE DESIGN AND ADD FEEDBACK
  • Use our elements and UX and UI card decks during your discussions.
  • https://novatools.org
09

4.3 - Share prototype and get feedback

4 steps
  1. 1

    Screen A.

  2. 2

    Screen B.

  3. 3

    Screen C.

  4. 4

    Screen D.

Read the full text
1. Screen A.

Add your design here. Describe the functionality by saying: As an [X - customer], I want to do [Y - activity] so that I can [Z - value proposition].** Provide a list of resources inside the section or the resources area.**

2. Screen B.

Add your design here. Describe the functionality by saying: As an [X], I want to do [Y] so that I can [Z].** Provide a list of resources inside the section or the resources area.**

3. Screen C.

Add your design here. Describe the functionality by saying: As an [X], I want to do [Y] so that I can [Z].** Provide a list of resources inside the section or the resources area.**

4. Screen D.

Add your design here. Describe the functionality by saying: As an [X], I want to do [Y] so that I can [Z].** Provide a list of resources inside the section or the resources area.**

Board
  • NAME
  • As an [X], I want to do [Y] so that I can [Z].
  • Add notes
  • Add notes
  • Add notes
  • NAME
  • As an [X], I want to do [Y] so that I can [Z].
  • Add notes
  • NAME
  • As an [X], I want to do [Y] so that I can [Z].
  • Add notes
  • NAME
  • As an [X], I want to do [Y] so that I can [Z].
  • Add notes
10

5.1 - Customer interviews

2 steps
  1. 1

    Collect insights.

  2. 2

    Analyze results and add insights to the highlights and conclusion section.

Read the full text
1. Collect insights.

During the interview or phone call, keep this board open or take notes. Add one insight per sticky notes. Evaluate how people feel and their emotions. Do they sound excited? Are they confused?

2. Analyze results and add insights to the highlights and conclusion section.
Work on the whiteboardInterview Dialogue Whiteboard
Interview Dialogue Whiteboard
  • Neutral
  • Bad experience
  • Positive
  • Extraordinary experience (excitement)
  • Not working/ Problem
  • Name
  • Name
  • Name
  • Name
  • Name
  • Name
  • Question
  • Answer
  • Summary and key findings
  • What are you expecting?
  • Question
  • Question
  • Question
  • Question
  • Question
  • Question
11

5.2 - Feedback & Action

2 steps
  1. 1

    Individual proposal.

  2. 2

    Action plan.

Read the full text
1. Individual proposal.

Keeping in mind the interview results submit a short proposal answering the following questions. What is currently not working, and how would you fix it? What would you change to improve your customer experience? What features or product characteristics were the ones the customer enjoyed the most during the interview or demo?

Write a note
2. Action plan.

Propose an action plan. (keep it short)

Add tasks
12

Wrap up

6 steps
  1. 1

    Can we reach our long-term-goal with our current solution?

  2. 2

    What would need to be true to reach our long-term goal?

  3. 3

    What should we do next?

  4. 4

    Takeaway.

  5. 5

    Explorer.

  6. 6

    How would you rate your experience during this sprint?

Read the full text
1. Can we reach our long-term-goal with our current solution?
Choose one
  • Yes
  • Maybe (if we improve the solution)
  • No
2. What would need to be true to reach our long-term goal?
Write a note
3. What should we do next?
Write a note
4. Takeaway.

What key fact or idea would you highlight?

Write a note
5. Explorer.

What do you think we should keep exploring?

Write a note
6. How would you rate your experience during this sprint?

1= Totally dissatisfied and 5= Totally satisfied.

Choose one
  • 1
  • 2
  • 3 🌟
  • 4 🌟 🌟
  • 5 ❤️ 🌟 🌟
13

3.2 - What should we... (individually)

2 steps
  1. 1

    What are we assuming must be true and will happen when validating this idea?

  2. 2

    What should we test/validate with our customers/users? or through our experiement?

Read the full text
1. What are we assuming must be true and will happen when validating this idea?

Add here some of the assumptions we are making and questions we have that heavily affect the success of this initiative, strategy, or project. Add one per sticky note and keep them organized by the following:

High Risk: Use this emoji 🔥 if any of these assumptions, if made incorrectly, are highly risky because the solution or strategy will not work or could even negatively affect our organization.

Somehow Risky: Use this emoji 👀 if there are some risks associated with this if your assumptions were wrong.

Do not use any emoji for low or no-risk ones.

Then evaluate them based on your level of confidence related to how much you know about them. Assumptions can be made in multiple ways: maybe you heard about it, seen some indicators or symptoms, or it could just be common sense, making it very likely to be true. Organize all your assumptions by this:

Use this emoji 🟣 if you are not sure at all and your level of confidence is low, meaning you and everyone else seem to be guessing or treating it as a rumor.

Use this emoji 🟡 if you somewhat know, whether it is because it seems like common sense or because you have heard from key people with experience or have seen indicators of it.

Do not use any emojis if you are almost sure, meaning you are highly confident that your assumption is right and true.

With this structure, you will be able to easily see what is low risk and you have high confidence in. Those can probably be ignored during the research phase since they are highly likely to be true and carry no or low risk.

The key focus should be on those marked with 🔥 and 🟣. These indicate assumptions that are critical for our success and that we do not feel confident about. These need to be turned into key questions during your research and validation phase.

Add sticky notes
2. What should we test/validate with our customers/users? or through our experiement?

Imagine testing a prototype with your potential users. You will need to create a prototype but will need to choose key areas you will show them. What would you text first? Facebook ad or a radio ad? What would you text next? Example: I would test our prototype with [YOUNG MOMS] First, I will show [THIS] because [X], and I want to be able to understand and evaluate [Y] Secondly, I will show [THIS] because [X], and I want to be able to understand and evaluate [Y] etc.

Write a note
14

3.3 - Storyboard for prototyping

Create a storyboard that you can use to develop a prototype. Keep in mind what you thought should be tested with your customer (or user), and start working as a team to develop a storyboard. Learn more about storyboard here: https://uxstudioteam.com/ux-blog/ux-storyboard/

15

4.1 - Prototyping brainstorming (meeting)

16

5.3 - Meeting with whiteboard

17

1.1AProblem Analysis

6 steps
  1. 1

    Define the Problem

  2. 2

    Analyze the Problem

  3. 3

    🎢♨ Identify the Root Cause

  4. 4

    Examine Symptoms

  5. 5

    Consider Challenges, Blockers, and Limitations

  6. 6

    Refine the Problem Statement...👣🦵

Read the full text
1. Define the Problem

In business, taking the time to fully understand a problem is one of the most critical steps. Skipping this step often leads to addressing the wrong issue or investing time and resources in ineffective solutions. Here's a framework to guide you through the process of defining, analyzing, and addressing a problem step-by-step.

🧑‍🎤Start by defining the problem in any way that comes to mind. This is your initial draft, and it doesn’t need to be perfect. Write it down in a central place (e.g., a red square or dedicated space).

🔥🔥Think deeper: How would the user, buyer, or people affected by this problem define it? Consider:

•Is their definition different from yours?
•Why do they see it that way?
•What’s important or unimportant to them?

Define the problem from the perspective of the business, organization, or internal team:

•What specific areas are affected?
•When does the problem occur?
•How does it differ for various use cases?
2. Analyze the Problem

Assess Needs and Pain Points:

•What type of pain does this problem cause?
•Which user or business needs are affected?
•Is the problem urgent or important? For whom? When? Why?

Let us share some additional context with you:

👇Usability Problems

•Users lack an intuitive way to invite and connect with relevant individuals.
•Current workflows may be cumbersome or non-existent for adding connections efficiently.
•Engagement Problems
•Limited ability to grow a meaningful network reduces the platform's perceived value.
•Users might not find enough connections or community to stay active on the platform.
•Scalability Problems
•Without this feature, the platform struggles to leverage organic growth from user networks.
•Difficulty in creating viral loops or achieving network effects.
•Development Bottlenecks
•Delays in launching the feature due to slow team progress and lack of leadership (e.g., absence of a product manager).
•Data-Driven Insights Gaps

According to Henry Murray's theory of human needs, basic needs are psychological and physiological elements that motivate behavior. Murray categorized these needs into primary (biological) and secondary (psychogenic) needs.

Basic (Primary) Needs

These are rooted in physiological survival and directly related to maintaining life:

•Food – The need for sustenance to maintain physical energy.
•Water – The need for hydration.
•Air – The need to breathe and sustain life.
•Shelter – The need for protection from environmental harm.
•Sex – The need for reproduction and continuation of the species.
•Avoidance of Pain – The need to avoid harm or injury.
•Rest – The need for sleep or recovery to maintain physical and mental health.

💜💬Psychogenic (Secondary) Needs

These arise from social and psychological aspects and are central to Murray’s theory. While not "basic," they guide complex human behavior:

•Achievement – The need to accomplish tasks and excel.
•Affiliation – The need to form and maintain social bonds.
•Dominance – The need to influence or control others.
•Autonomy – The need for independence and freedom.
•Order – The need for organization and stability.
•Understanding – The need for knowledge and comprehension.

💥💫Next, Determine the Desired Approach:

•Do you want to solve the root cause of the problem?
•Do you want to create a "painkiller" (address symptoms without tackling the root cause)?
•Or, would you address only part of the problem (not the full scope)?
3. 🎢♨ Identify the Root Cause

Use the “5 Whys” method (at least three iterations of "Why?"):

1.Ask: Why is this a problem?
2.Then ask again: Why? What’s the purpose of addressing it?
3.Repeat until you uncover where the problem originates.

Once you identify the root cause, revisit and refine your problem statement.

4. Examine Symptoms

Define the symptoms or consequences of the problem:

•Think of symptoms as the visible or experienced outcomes (e.g., fever is a symptom of sickness).
•List all symptoms on sticky notes or in a visual format.
5. Consider Challenges, Blockers, and Limitations

Identify challenges or limitations that may shape your approach:

•Organizational strengths or weaknesses.
•Budget or time constraints.
•Reasons for focusing on one part of the problem or tackling symptoms first.

🤫🤔Now, assumptions are normal but need to be managed:

Write each assumption on a sticky note and organize them in a matrix:

•High Confidence (you’re confident the assumption is true).
•High Risk (could significantly affect the outcome if wrong).

For high-risk assumptions, do research or talk to stakeholders. Create a list of questions for stakeholders to validate or invalidate these assumptions.

6. Refine the Problem Statement...👣🦵
1.Review all the steps so far and redefine your problem statement.
2.Transform the problem into a “How Might We” question (e.g., “How might we improve customer satisfaction while reducing costs?”).

Move forward...👣🦵

With a well-defined problem, a clear understanding of its root cause, and a plan to manage assumptions, you’re ready to start working on solutions. This process ensures you’re solving the right problem effectively and efficiently.

New Board
  • Problem analysis The process
  • Current environmental limitations and things outside our control.
  • Root cause is defined as a factor that caused a nonconformance and should be permanently eliminated through process improvement.
  • A sign of the existence of something, especially of an undesirable situation. Different users/people will experience different symptoms.
  • How would you define the problem?
  • How would the user/buyer define the problem?
  • How would the business/Organization/Team define the problem?
  • What type of problem is this?
  • How would you like to approach it?
  • Solve the root cause of the problem
  • "Painkiller" (address symptoms without tackling the root cause)
  • Address part of the problem/some of the causes (not the full scope)
  • List of Assumptions
  • High Confidence
  • Low
  • High Risk
Capabilities
Fully editableAdapts as work changesAdd more sessions anytimeAI can be assigned
N
Created byNova·Official process
Last edited Jan 7, 2025·17 sessions · 45 steps