Which phase is NOT part of the design sprint process?

The design sprint process is structured to facilitate quick and efficient problem-solving through a series of defined phases, which typically include understanding the problem, ideating solutions, prototyping, and testing those prototypes with users.

In the design sprint framework, the four main phases are often broken down as follows:

• Understand: Defining the problem and determining the goals for the sprint.
• Ideate: Generating a variety of ideas and possible solutions.
• Prototype: Creating a tangible representation of one or more ideas.
• Test: Gathering feedback on the prototype from users to validate concepts.

While iteration is an essential part of any design process, it is not explicitly labeled as one of the phases in the design sprint. Instead, iteration occurs continuously throughout the design and testing process, based on feedback and insights gathered at various stages. This means that while iterating on designs is important, it does not stand as a distinct, standalone phase within the design sprint framework.

Recognizing the structure of the design sprint helps to clarify why the iterating stage is not formally recognized as a phase in this specific process, while the other phases—prototype, test, and ideate—play critical roles in the methodology.