Design Sprint explained in simple 5 W’s & 1H

• What is Design Sprint?
• Why Design Sprint?
• When we need a Design Sprint?
• Who can be the participants?
• Where to conduct?
• How to conduct Design Sprint?

What is Design Sprint?

Design sprint is a 1–5 days process to validate any new business concept with customers through rapid design, prototyping & test.

Why Design Sprint?

• It is a quick and inexpensive way to validate new ideas without investing in code
• Limits the risk level of failure to early stage
• Get an immediate result & responses
• Maximize your return on investment
• Wow your key stakeholders and get their buy-in

When we need a Design Sprint?

• Big, new ideas are best to test in design sprint
• When challenges are complex and requires lot of efforts
• When fresh & cross thinking needed
• Requires success or failure market validation

Who can be the Participants?

• A Facilitator (most likely designer)
• A Decider (CEO/PM/DH)
• Designers
• An Engineer
• A Product Manager
• A Marketer
• And anybody else who has shared knowledge

Where to conduct?

Book a room with;

• Less destruction, wifi enabled etc
• Whiteboards or large post-it pads
• Set of colored whiteboard markers
• Sharpie per person (Keep stock )
• Pad of sticky post it's per person
• Sheets of paper
• Roll of tapes
• Pair of scissors

How to Conduct?

Understand & Map out the Problem

• Identify the problem to be solved
• Map the user journey
• Define your long-term goal
• Define how might we questions (HMW)
• Leverage existing knowledge

Sketch Creation & Ideation

• Customer journey mapping
• Build inspiration from existing solutions through lightning demos
• Generate solutions to the identified problem by brainstorming in design thinking pattern
• Create crazy 8 individual solution pitches

Concept Development & Decide

• Critique individual solution pitches
• Select which solutions, features and functionalities are best to move forward
• Make storyboard prototype flow

Prototype Development

• Create a working prototype for user testing
• Avoid dummy content, use always realistic content
• Prepare user interview script

Test & Validation

• Test the prototype with users and debrief to the team
• Observe or record users interactions with the prototype
• Ask 5W’s & 1H questions to users
• Validate hypotheses and assumptions

Take Away

• The sprint gives teams a shortcut to learning without build in code and launch
• Saving months of design, engineering and development costs
• Massive team collaboration

You can connect with me on Behance & LinkedIn

Walkthrough of building Design System: https://medium.com/nyc-design/building-the-talabat-design-system-e94283dda6c3

What is Micro-interaction: https://medium.com/nyc-design/what-is-micro-interaction-3d7237a14427