Design Sprints: What are they and how do they invite collaboration?

A design sprint is a five day process that draws inspiration from various methodologies and practices that problem solves from different ideas/perspectives.

Usually, a small team with varying job functions identifies a problem, attempts to find solutions in a rapid five day process, and the end goal of a working prototype that they’re able to test on their audience.

The Design Sprint Handbook also offers a great breakdown of team roles, including:

  • Facilitator
  • Product Owner / Project Leader
  • Decider
  • Designer
  • Engineer
  • UX Researcher
  • Marketer
  • Subject Matter Expert
  • Voice of the Customer

Each role matters. Together, they form a team prepared to take on their sprint.

The 5 day sprint process

Monday: Understand & Define

The first step is all about alignment.

  • Decide what roles each team member is taking for the sprint, what materials are needed to do the sprint, and how the team is going to collaborate.
  • Conduct team interviews and ask “How Might We…” questions to spark insight.
  • Organize the ideas and then vote on which ones they should pursue during the sprint.
  • Define long-term goals and identify key questions.
  • Create a customer journey map that visually traces the ideal user’s path.
  • Learn from others with lightning demos – quick looks at inspiring solutions.
  • Wrap up day one with a 4-step sketching process to begin imagining potential solutions.

Tuesday: Diverge & Decide

Time to cast a wide net before narrowing it down.

  • Build on the sketches with heat map voting, speed critiques, and straw poll voting.
  • Explore all ideas in an “art museum” layout.
  • Then, storyboard the selected path—a clear narrative of your solution.

Wednesday: Prototyping

Getting a tangible object.

  • Use the storyboard and sketches to create a high-fidelity prototype. Then the idea becomes a tangible product that looks and feels real.
  • This isn’t a wireframe or rough draft. It’s something real enough to test and learn from.

Thursday: Testing

Testing the prototype with real users from the target audience.

  • Listen, observe, and gather feedback from the audience.
  • What worked? What didn’t? What was surprising about the product testing?

Friday: Reflect + Report

Review your findings with fresh eyes.

  • Deliver a well-crafted Sprint Report that documents insights, outlines next steps, and provides clarity moving forward.

Foundational Principles of a Design Sprint

These sprints aren’t just about speed—they’re about working smarter, more collaboratively, and more creatively:

  • Working together, alone: Everyone contributes ideas individually before sharing with the group. This avoids group conformity, invites diverse ideas, and adds high level collaboration.
  • Tangible over talk: Don’t just keep talking in circles, build it! Prototypes as a tangible object can speak louder than words.
  • Just start: Don’t wait for the thing to be perfect. Forward motion is better than hesitation or paralization.
  • Embracing ambiguity: The path might feel uncertain, and that’s okay. Momentum matters more than certainty.
  • Avoid the pressure of being creative: Creativity blooms when pressure is released. The sprint structure gives you a path to follow, so lean in and embrace following the path.

The art of facilitation

Behind every successful design sprint is a skilled facilitator – someone who guides the team through the sprint and keeps everyone on task.

A good facilitator is:

  • Organized, yet adaptable.
  • A clear communicator and an active listener.
  • Emotionally intelligent, trustworthy, and capable of making rapid-fire decisions.
  • Confident, collaborative, and always open-minded.

Like anything we do, facilitation gets better with practice. The more you lead, the more intuitive it becomes.

Reflections from a reading

Reading the first few chapters of Sprint: how to solve big problems and test new ideas in just five days lit a fire in me. The story of the Savioke (now called Relay Robots) delivery robot design sprint was really inspring. Their team went through the five day process, and had a high-fidelity prototype ready by Friday. Even though the high-fidelity prototype wasn’t perfect (it was an iPad mounted to the robot’s base), the testing was a success.

Final thoughts

Design sprints don’t just streamline product/service development – they inspire action and collaboration. They give teams a shared path to sprint (haha) down together, where perfection is not required but ideas are celebrated.

Whether you’re starting a new project, stuck in a rut, or just need to get that idea out of your head – a design sprint might be the tool you need.

Let the momentum guide you: Build, test, learn, repeat.


Comments

Leave a comment