Toolkit Navigator

Google Design Sprints

The Design Sprint is a methodology for quickly solving problems through developing a hypothesis, prototyping an idea, and testing ideas with users. Design Sprints quickly align teams under a shared vision with clearly defined goals and deliverables. The Design Sprint methodology was developed at Google from a vision to grow user experience (UX) culture and the practice of design leadership across an organisation. The length of time for Design Sprints will be based on the goals and the needs of the team. Sprints typically range from 1 to 5 days. This resource includes guidance on the methodology, planning sprints, a method library (including recipes for sets of methods used sequentially for different purposes), and downloadable resources. The web-based resource also features a community of contributors as well as case studies. While the Design Sprint methodology has commonly been used for product design in a private sector context, the methodology can also be valuable in the public sector for exploring a problem spaces and quickly prototyping ideas and testing assumptions.



Discipline or practice

Product Design

Process Facilitation and Co-Design

Link to toolkit

Source files

About this resource


United States

Date Published




Web-based resource

See cases from others doing this in government

Go to case studies

Find experts and advisers who can assist me with this

Go to advice

Other toolkits related to Product Design

One review for "Google Design Sprints"

  1. Jane Kloster says:

    Google Sprint is a short, intense and fast design process, which consists of 6 predefined and well-described phases with associated working methods. The purpose and framework of each phase is clear, which can be an advantage if you haven’t worked with design or sprint before. It is recommended that the sprint is being completed over 5 days, but it can also be completed in less. Because you work intensively for a short period, preparation is incredibly important to ensure a good experience during the sprint as well as a good and usable output. The sprint format is good for jumpstarting an innovation process and getting the participants’ creativity going. It’s especially good at the beginning of a project to define your product or create a shared vision. The format isn’t recommendable if you don’t have user research or a strong understanding of your customer base, then you can consider running a Research Sprint, or conducting a Research study. And maybe most important – if you do not have leadership buy-in. The framework for the process is determined in advance, which can be a good thing for design beginners who aren’t used to working with open processes – however, it’s important that there is a participant who has the mandate to make decisions so that the process remains relevant to the context of the company as well as having a participant who is responsible for adhering to the time and ensuring progress in the process. When using this toolkit, you must anticipate preparation time and be aware of who your end-user is, especially if you work with public sector innovation. The Google Sprint website itself is very informative and has described many aspects of working with Sprints.

Add your review

Have you used this toolkit? If so, what did you use it for and how did it work? What are its strengths and limitations? Share your experience so others can learn from you.

Your email address will not be published. Required fields are marked *