Design Sprints: A Step-by-Step Guide for Product Managers

4 min readJan 7, 2024

Have you ever felt the pressure of bringing a product to life, only to be bogged down by endless discussions and revisions? What if there was a way to streamline this process, to turn chaos into clarity? This is where the magic of a design sprint comes into play.

As a product manager, you are the maestro of product development, orchestrating various elements to create a symphony of innovation. But even the best maestros need a score to follow. This is where a design sprint becomes your sheet music.

What is a Design Sprint?

A design sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at Google Ventures, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more — packaged into a battle-tested process that any team can use.

Step-by-Step Guide to Running a Design Sprint

Day 1: Understand

Objective: Map out the problem and pick an important area to focus.

Start with the End in Mind: Define your long-term goal. Ask yourself, what does success look like?
Map it Out: Draw a user journey map. Identify key actors, actions, and emotions.
Expert Interviews: Talk to experts in your team to gather insights. This could be anyone from a customer service rep to a CEO.
How Might We (HMW): Turn problems and questions into opportunities. Write down HMW questions to explore solutions.

Example: A fintech company might focus on the user experience of their mobile app, mapping out each step a user takes to make an online transaction.

Day 2: Diverge

Objective: Explore a wide variety of solutions.

Lightning Demos: Showcase existing solutions or features from other products that inspire you.
Sketch: Each team member sketches solutions independently. This includes a series of four steps — notes, ideas, crazy 8s (eight ideas in eight minutes), and a solution sketch.

Example: Team members might sketch different login processes, exploring biometrics, two-factor authentication, or even novel ideas like mood-based access.

Day 3: Decide

Objective: Choose the best solutions.

Art Museum: Display all sketches. Let the team walk around and put dot stickers on features they like.
Heat Map: Create a heat map of the most popular ideas.
Speed Critique: Discuss the pros and cons of each solution.
Straw Poll: Each member votes for their favorite idea.
Supervote: The Decider makes the final call on which ideas to prototype.

Example: The team might gravitate towards a biometric login feature due to its balance of security and user convenience.

Day 4: Prototype

Objective: Build a realistic prototype.

Choose the Right Tools: Depending on the solution, tools might range from paper and markers to digital prototyping tools like Sketch or Figma.
Divide and Conquer: Assign roles — maker, stitcher, writer, asset collector, and interviewer.
Build: Create a prototype that’s “just real enough” to test with real users.

Example: A clickable prototype of the app with the new login feature is created using Figma.

Day 5: Test

Objective: Learn from customer feedback.

Interviews: Conduct one-on-one user tests. Observe how real users interact with your prototype.
Feedback Loop: Collect and document feedback.
Iterate: Identify patterns and insights to refine your product.

Example: Users test the new login feature. The team notes that older users struggle with the biometric setup, indicating a need for clearer instructions.

After the Sprint

Post-sprint, the real work begins. Analyze the results, decide on the next steps, and integrate the learnings into your product development cycle. Remember, a design sprint is not just about the ideas generated, but about learning and moving forward efficiently.

Here is a quick mind map for the above article :

For product managers, design sprints offer a structured yet flexible framework to innovate rapidly. It’s about making the most of your team’s time and creativity, turning ideas into actionable solutions. So, are you ready to lead your team through their next design sprint?

Thanks for reading! If you’ve got ideas to contribute to this conversation please comment. If you like what you read and want to see more, clap me some love! Follow me here, or connect with me on LinkedIn or Twitter.

Do check out my latest Product Management resources 👇