1.8 Design sprints

Design sprints are a powerful tool in Design Strategy and Software, enabling teams to rapidly solve complex problems and test new ideas. This time-constrained process, developed by Google Ventures, brings together cross-functional teams to explore solutions, create prototypes, and validate concepts with users in just a few days.

The sprint process typically follows five key phases: understand, sketch, decide, prototype, and test. By compressing months of work into a focused sprint, teams can quickly assess the viability and desirability of potential solutions before investing significant resources, making it an invaluable approach in today's fast-paced digital landscape.

What are design sprints

• Design sprints are a time-constrained, collaborative process for rapidly solving complex problems and testing new ideas in the field of Design Strategy and Software
• Originated at Google Ventures, design sprints bring together cross-functional teams to explore solutions, create prototypes, and validate concepts with users in just a few days
• The goal is to compress months of work into a focused sprint, enabling teams to quickly assess the viability and desirability of potential solutions before investing significant resources

Origins of design sprints

Top images from around the web for Origins of design sprints

• 

  Appendix 1: A Sprint Toolkit – Working Group Guide View original

  Is this image relevant?

• 

  Had enough of agile sprints? Time for design sprints - UX Mastery View original

  Is this image relevant?

• 

  Nomad8 | Agile Dunedin 2020: Design Sprint Dinner workshop View original

  Is this image relevant?

• 

  Appendix 1: A Sprint Toolkit – Working Group Guide View original

  Is this image relevant?

• 

  Had enough of agile sprints? Time for design sprints - UX Mastery View original

  Is this image relevant?

1 of 3

Top images from around the web for Origins of design sprints

• 

  Appendix 1: A Sprint Toolkit – Working Group Guide View original

  Is this image relevant?

• 

  Had enough of agile sprints? Time for design sprints - UX Mastery View original

  Is this image relevant?

• 

  Nomad8 | Agile Dunedin 2020: Design Sprint Dinner workshop View original

  Is this image relevant?

• 

  Appendix 1: A Sprint Toolkit – Working Group Guide View original

  Is this image relevant?

• 

  Had enough of agile sprints? Time for design sprints - UX Mastery View original

  Is this image relevant?

1 of 3

• Developed by Jake Knapp and the Google Ventures team in 2010 as a way to help startups quickly validate product ideas and make informed decisions
• Drew inspiration from various design thinking methodologies, agile development practices, and behavioral science principles
• Evolved over time through application in hundreds of sprints with companies across industries, refining the process and techniques

Goals of design sprints

• Rapidly explore and evaluate multiple solutions to a complex problem or opportunity in a short timeframe (typically 4-5 days)
• Foster collaboration and alignment among cross-functional team members, including designers, developers, business stakeholders, and domain experts
• Create a shared understanding of the problem space, user needs, and potential solutions through hands-on activities and discussions
• Produce a tangible prototype that can be tested with real users to gather feedback and validate assumptions
• Make informed decisions about which ideas to pursue further based on user insights and business objectives

When to use design sprints

• Tackling high-stakes, complex challenges where the solution is unclear or there are multiple possible approaches
• Exploring innovative solutions for new products, features, or services in Design Strategy and Software
• Aligning teams around a shared vision and direction when there are differing perspectives or competing priorities
• Accelerating the product development process by compressing ideation, prototyping, and testing into a focused sprint
• Reducing the risk of investing significant time and resources into an untested idea by validating it early with users

Key phases of design sprints

• Design sprints typically follow a structured process with five key phases: understand, sketch, decide, prototype, and test
• Each phase is time-boxed and has specific activities and deliverables to keep the team focused and moving forward
• The phases build upon each other, with insights from one informing the next, leading to a tested prototype by the end of the sprint

Understanding the problem

• Start by clearly defining the problem or opportunity to be addressed in the sprint, considering business goals, user needs, and technical constraints
• Gather and review existing data, research, and insights related to the problem space to build a shared understanding among the team
• Conduct interviews with users, stakeholders, and domain experts to gain diverse perspectives and uncover key challenges and opportunities
• Map out the user journey, identifying pain points, moments of delight, and areas for improvement
• Define the target user and their core needs, motivations, and behaviors to guide solution ideation

Sketching potential solutions

• Encourage individual ideation through rapid sketching exercises like Crazy 8s, where each team member generates eight rough ideas in eight minutes
• Provide a structured format for sketches, such as a storyboard or user flow, to ensure key aspects of the solution are considered
• Emphasize quantity over quality, focusing on generating a wide range of ideas rather than perfecting any single concept
• Share and discuss sketches as a team, building upon each other's ideas and identifying common themes and promising directions
• Refine and combine the best ideas into more detailed solution sketches that consider user experience, technical feasibility, and business viability

Deciding on best ideas

• Review and evaluate the solution sketches based on predefined criteria, such as user value, business impact, and technical feasibility
• Use structured decision-making techniques like dot voting or heat mapping to identify the most promising ideas with input from all team members
• Discuss the pros and cons of each top idea, considering potential risks, challenges, and dependencies
• Reach consensus on the solution(s) to move forward with prototyping, ensuring alignment and buy-in from the team
• Define the key features, user flows, and success metrics for the selected solution(s) to guide prototype development

Prototyping the solution

• Create a tangible representation of the selected solution(s) that can be tested with users, focusing on the core functionality and user experience
• Choose the appropriate fidelity level for the prototype based on the stage of development and testing goals (e.g., low-fidelity paper prototypes or high-fidelity digital mockups)
• Assign roles and responsibilities for prototype creation, leveraging the skills and expertise of team members
• Use rapid prototyping techniques and tools to efficiently build and iterate on the prototype, such as sketching, wireframing, or using digital prototyping software
• Test and refine the prototype internally with the team, gathering feedback and making improvements before user testing

Testing with users

• Recruit representative users from the target audience to participate in testing sessions, ensuring diverse perspectives and experiences
• Develop a test plan and script that outlines the key scenarios, tasks, and questions to guide the user testing sessions
• Conduct moderated user testing sessions, observing how users interact with the prototype and gathering qualitative feedback on their experience
• Capture insights, pain points, and opportunities for improvement based on user feedback and behavior
• Synthesize and prioritize the learnings from user testing, identifying areas for iteration and refinement in the prototype and overall solution

Roles in design sprints

• Design sprints involve a cross-functional team with clearly defined roles and responsibilities to ensure effective collaboration and progress
• The core roles typically include a facilitator, designer, developer, product manager, and domain expert, each bringing unique skills and perspectives
• Additional roles may be involved depending on the specific project and organizational context, such as marketing, research, or executive stakeholders

Facilitator responsibilities

• Guide the team through the design sprint process, ensuring adherence to the schedule, activities, and deliverables
• Plan and prepare for the sprint, including defining the challenge, recruiting participants, and gathering necessary materials and resources
• Facilitate discussions, activities, and decision-making sessions, promoting active participation and collaboration among team members
• Manage group dynamics, ensuring all voices are heard and conflicts are resolved constructively
• Keep the team focused on the sprint goals and outcomes, mitigating distractions and scope creep

Team member participation

• Actively engage in all sprint activities, contributing ideas, insights, and skills relevant to their domain expertise
• Collaborate with other team members, building upon each other's ideas and providing constructive feedback
• Take ownership of specific tasks and deliverables, such as sketching solutions, creating prototype components, or preparing user testing materials
• Share knowledge and insights from their respective fields to inform solution development and decision-making
• Maintain a positive and open-minded attitude, embracing experimentation, learning, and iteration throughout the sprint

Stakeholder involvement

• Engage key stakeholders, such as executive sponsors, subject matter experts, or customer representatives, at strategic points throughout the sprint
• Invite stakeholders to participate in problem framing, solution ideation, and prototype feedback sessions to gather diverse perspectives and insights
• Communicate sprint progress, learnings, and outcomes to stakeholders, ensuring alignment with broader organizational goals and priorities
• Seek stakeholder input and approval on key decisions, such as solution selection or prototype refinement, to maintain buy-in and support
• Collaborate with stakeholders to define next steps and plan for post-sprint activities, such as further testing, development, or implementation

Planning for design sprints

• Effective planning is crucial for the success of a design sprint, ensuring the team is well-prepared and aligned on the goals, process, and deliverables
• Key planning activities include defining the challenge, gathering relevant data, identifying key stakeholders, scheduling the sprint, and preparing materials and space
• Careful planning helps to maximize the value of the time-boxed sprint, enabling the team to focus on solving the problem at hand efficiently and effectively

Defining the challenge

• Clearly articulate the problem or opportunity to be addressed in the sprint, considering business objectives, user needs, and technical constraints
• Frame the challenge as a question that inspires exploration and solution-oriented thinking, such as "How might we...?" or "What if...?"
• Ensure the challenge is specific enough to be tackled within the sprint timeframe, yet broad enough to allow for diverse ideas and approaches
• Validate the challenge with key stakeholders to ensure alignment with organizational priorities and feasibility of implementation
• Communicate the challenge to the sprint team, providing necessary context and background information to foster a shared understanding

Gathering relevant data

• Collect and review existing research, data, and insights related to the problem space, such as user interviews, analytics, market trends, or competitive analyses
• Identify gaps in knowledge or understanding that may require additional research or exploration during the sprint
• Summarize key findings and insights in a format that is easily accessible and digestible for the sprint team, such as a research report or synthesis wall
• Share relevant data with the team prior to the sprint, allowing them to familiarize themselves with the context and come prepared with ideas and questions
• Continuously gather and incorporate new data and insights throughout the sprint, adapting the problem framing and solution direction as needed

Identifying key stakeholders

• Map out the stakeholders who have a vested interest in the problem space or solution, including users, customers, business leaders, domain experts, or partners
• Determine which stakeholders need to be directly involved in the sprint, considering their expertise, influence, and availability
• Engage stakeholders early in the planning process to gather their input, expectations, and constraints for the sprint
• Communicate the sprint goals, process, and deliverables to stakeholders, setting clear expectations for their involvement and the expected outcomes
• Plan for stakeholder participation in key moments throughout the sprint, such as problem framing, solution ideation, or prototype feedback sessions

Scheduling the sprint

• Identify a suitable timeframe for the sprint, typically 4-5 consecutive days, ensuring availability of all necessary participants and resources
• Block out the entire duration of the sprint in participants' calendars, minimizing external distractions and commitments
• Allocate time for each phase of the sprint, considering the complexity of the problem and the experience level of the team
• Plan for breaks, energizers, and team-building activities to maintain momentum and engagement throughout the sprint
• Communicate the sprint schedule to all participants and stakeholders, ensuring clarity on the daily agenda and expected deliverables

Preparing materials and space

• Secure a dedicated space for the sprint that allows for focused collaboration, such as a conference room or design studio
• Ensure the space is equipped with necessary materials and supplies, such as whiteboards, sticky notes, markers, and prototyping tools
• Prepare any templates, frameworks, or reference materials that will be used during the sprint, such as user journey maps, storyboard templates, or ideation prompts
• Test and set up any technology or equipment needed for the sprint, such as projectors, video conferencing tools, or design software
• Create a welcoming and inspiring environment that promotes creativity, collaboration, and experimentation, such as by adding posters, plants, or snacks

Facilitating design sprints

• Effective facilitation is essential for guiding the team through the design sprint process, ensuring productive collaboration, and achieving the desired outcomes
• The facilitator plays a key role in setting the agenda, timekeeping, encouraging participation, managing group dynamics, and documenting progress and decisions
• Skilled facilitation creates a safe and inclusive environment where all team members can contribute their ideas and expertise towards solving the challenge at hand

Setting the agenda

• Communicate the overall goals, process, and deliverables of the sprint to the team, ensuring a shared understanding of what success looks like
• Break down the sprint into clear, time-boxed activities for each phase, allocating sufficient time for ideation, discussion, and decision-making
• Provide a visual agenda or timeline that outlines the key activities, milestones, and expected outcomes for each day of the sprint
• Adapt the agenda as needed based on the team's progress, energy levels, or emerging challenges, while still maintaining the overall structure and goals
• Start each day with a brief review of the previous day's outcomes and the current day's objectives, setting the stage for focused and productive work

Timekeeping and pacing

• Keep the team on track by monitoring time and gently reminding them of the remaining duration for each activity or phase
• Use timers, clock visuals, or verbal cues to create a sense of urgency and maintain momentum throughout the sprint
• Balance the need for efficient progress with the importance of allowing sufficient time for exploration, discussion, and iteration
• Adjust the pacing of activities based on the team's energy levels and engagement, providing breaks or energizers as needed to maintain focus and motivation
• Be prepared to adapt the timeline or agenda if the team encounters unexpected challenges or opportunities that require more time or attention

Encouraging collaboration

• Foster an environment of psychological safety where all team members feel comfortable sharing their ideas, opinions, and concerns without fear of judgment or criticism
• Use inclusive language and facilitation techniques that encourage participation from all team members, such as round-robin sharing or nominal group voting
• Provide equal airtime and attention to all team members, ensuring that quieter or less assertive individuals have opportunities to contribute
• Facilitate cross-pollination of ideas by encouraging team members to build upon each other's suggestions and combine different perspectives
• Celebrate and acknowledge the team's progress, successes, and learnings throughout the sprint, reinforcing a sense of shared ownership and accomplishment

Managing group dynamics

• Be attentive to interpersonal dynamics and potential conflicts that may arise during the sprint, such as differing opinions, communication styles, or power imbalances
• Address any tensions or disagreements promptly and constructively, facilitating open and respectful dialogue to find common ground or compromise
• Encourage team members to assume positive intent and focus on the shared goals of the sprint, rather than personal agendas or biases
• Model active listening, empathy, and curiosity, setting the tone for a collaborative and inclusive team culture
• Use humor, storytelling, or other techniques to lighten the mood and create a positive and energizing atmosphere, while still maintaining focus on the work at hand

Documenting progress and decisions

• Capture key insights, ideas, and decisions throughout the sprint using visual and accessible formats, such as sticky notes, sketches, or digital whiteboards
• Summarize the outcomes and learnings from each phase of the sprint, highlighting the most promising ideas, unanswered questions, and areas for further exploration
• Document the rationale behind key decisions, such as solution selection or prototype features, to ensure transparency and alignment among the team and stakeholders
• Create a centralized repository or dashboard where all sprint artifacts and documentation can be easily accessed and reviewed by the team and stakeholders
• Provide regular updates and summaries to stakeholders who are not directly involved in the sprint, keeping them informed of progress and outcomes

Design sprint techniques

• Design sprints employ a variety of techniques and activities to facilitate problem-solving, ideation, decision-making, and prototyping
• These techniques are designed to encourage creative thinking, collaboration, and rapid experimentation within the time-boxed structure of the sprint
• Commonly used techniques include How Might We questions, Crazy 8s sketching, heat mapping, storyboarding, and role-playing, among others

How Might We questions

• Frame the problem or opportunity as an open-ended question that invites creative exploration and solution-oriented thinking
• Start with the phrase "How Might We..." followed by a specific, actionable challenge that the team aims to address
• Break down broad challenges into smaller, more manageable "How Might We" questions that focus on different aspects of the problem or user needs
• Encourage the team to generate multiple "How Might We" questions, capturing diverse perspectives and potential angles for exploration
• Use "How Might We" questions as prompts for ideation sessions, guiding the team to generate ideas that directly address the identified challenges

Crazy 8s sketching

• Rapid sketching exercise where each team member individually generates eight rough ideas in eight minutes
• Provide a template or grid with eight boxes, prompting participants to sketch one idea per box using simple shapes, stick figures, and annotations
• Encourage quantity over quality, emphasizing the importance of exploring a wide range of ideas without getting bogged down in details or feasibility concerns
• Set a timer for eight minutes and have participants work silently and independently, filling out all eight boxes with their ideas
• Share and discuss the sketches as a team, identifying common themes, interesting concepts, and areas for further exploration or combination

Heat mapping and dot voting

• Collaborative prioritization techniques used to identify the most promising ideas or solutions from a larger set of options
• In heat mapping, team members review the generated ideas and use colored dots or markers to indicate their level of interest, excitement, or perceived value for each idea
• Patterns of clustering or concentration of dots reveal the ideas that resonate most strongly with the team, helping to focus attention and discussion
• In dot voting, each team member is given a fixed number of dots (usually 3-5) to allocate across the ideas they believe are most worthy of further exploration or development
• Ideas with the highest number of dots are considered the top priorities or candidates for prototyping and testing
• Facilitate a discussion around the top-voted ideas to understand the rationale behind the votes and build consensus on the direction forward

Storyboarding the user experience

• Visually represent the key steps, interactions, and emotions of the user journey or solution concept using a sequence of simple sketches or scenes
• Divide a large sheet of paper or whiteboard into a grid of 6-8 panels, each representing a key moment or interaction in the user experience
• As a team, brainstorm and discuss the critical steps and outcomes of the user journey, focusing on the user's goals, challenges, and desired outcomes
• Sketch simple visuals and annotations in each panel to convey the essential elements of the user experience, such as the user's actions, thoughts, or emotions
• Use the storyboard as a tool for communicating the solution concept, identifying potential pain points or opportunities, and guiding prototype development

Role playing and bodystorming

• Immersive techniques that involve physically acting out or simulating the user experience to generate insights and test ideas
• In role-playing, team members take on the roles