![\"Design](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2018\/09\/design-sprint-post-its-720x479.jpg\")
<\/p>\n<\/p>\n
Applied regularly at Google, Airbnb, McKinsey and LEGO, the Design Sprint allows you to solve any design problem. During the sprint, you take a small team, clear their schedules for a week, and rapidly progress from problem to tested solution. In only 5 days, it accelerates and simplifies the design process of a digital product.<\/b><\/p>\n
<\/p>\n
Browse through this page to understand better:<\/span><\/p>\n Most companies are stuck within old-fashioned office behaviors: endless arguing at meetings, decision churn, extroverts dominating brainstorming sessions, bad roadmaps. It all results in wasted months or years.<\/span><\/p>\n The Design Sprint, developed by Jake Knapp, Braden Kowitz and John Zeratsky at Google Ventures, is a five-day process for answering critical business questions through design, <\/span>rapid design prototyping, and testing <\/span>ideas. <\/span><\/p>\n By running a design sprint, you get a concrete and measurable outcome in just 5 days, thanks to user validation built into the process. <\/span><\/p>\n By getting from problem to solution without running errands, and time spent with unuseful development, you\u2019ll be able to convince investors faster, reduce risks, avoid developing unnecessary features, and maximize your ROI. <\/span><\/p>\n On Monday, we map the problem, based on expert inputs from the client. On Tuesday, we sketch possible solutions together. On Wednesday, we decide on the strongest solution. <\/span><\/p>\n On Thursday, we build a realistic prototype. <\/span><\/p>\n The client is actively involved in the first days of the sprint. Day 4 is devoted to Prototyping and can be performed remotely. On Day 5, we test the prototype: we invite users to test our prototype and take advantage of their feedback to assess the potential of your product. We seek to answer all strategic <\/span>questions through design prototyping<\/span>.<\/span><\/p>\n Monday – Define<\/b><\/p>\n Tuesday – Diverge: <\/b><\/p>\n Wednesday – Decide: <\/b><\/p>\n Thursday – Prototype:<\/b><\/p>\n Friday – Validate:<\/b><\/p>\n In short: the more diverse team the better, but not more than 7-8 people. <\/span><\/p>\n At the bare minimum, decision-makers should be present, plus a facilitator that doesn\u2019t participate in the decision-making. The point is that all stakeholders are represented so that they can give input and be part of the decision-making process.<\/span><\/p>\n We should create a balanced mix of expertise in business, human and technical areas. A typical assortment of participants include:<\/span><\/p>\n Some helping questions:<\/b><\/p>\n Why don\u2019t all companies just read the book and run sprints all the time? Because a successful sprint works much better if the person(s) who facilitate(s) it is impartial outside experts. <\/span><\/p>\n Among other things, the sprint facilitator (sprint master): <\/span><\/p>\n We\u2019re often asked if we can get results quicker by running a design sprint. Why spend months on a long product design process when 5 days is enough?<\/span><\/p>\n The GV design sprint is a tool for a very specific situation:<\/b><\/p>\n Typically good design sprint objectives:<\/b><\/p>\n The client:<\/b><\/p>\n We recently ran a design sprint for Meta Inf, an IT company specializing in the Atlassian ecosystem. <\/span><\/p>\n The product:<\/b><\/p>\n They were working on an automatized email-handler solution that synchronizes and sorts incoming support request emails with Jira. Out of all our possible <\/span>design sprint examples<\/span>, this one describes simplest how we do sprints here at UX studio.<\/span><\/p>\n The issue:<\/b><\/p>\n User feedback indicated that the rules page of the mail-handler was hard to use. Users had difficulties programming the rules that set email automatization in motion, which resulted in high support need. The team felt that they needed a quick UX boost to kickstart the redesign process.<\/span><\/p>\n The team:<\/b><\/p>\n\n
What is a Google design sprint?<\/span><\/h2>\n
What is the outcome of a design sprint?<\/span><\/h2>\n
\n
What are the advantages of a product design sprint?<\/span><\/h2>\n
\n
What does a sprint look like? \u2013 The 5-day design sprint process<\/span><\/h2>\n
The process<\/span><\/h2>\n
![\"Design](\"https:\/\/uxstudioteam.com\/ux-blog\/wp-content\/uploads\/2018\/11\/Sprint_01-720x330.png\")
<\/p>\n\n
\n
\n
\n
\n
Who should participate in the design sprint?<\/span><\/h2>\n
\n
\n
Why do you need a design sprint facilitator and what do they do?<\/span><\/h2>\n
\n
When the design sprint is a good answer (typical scenarios):<\/span><\/h2>\n
\n
\n
Let\u2019s look at a concrete example! <\/span><\/h2>\n
Redesigning a JIRA e-mail handler during a Design Sprint (Case Study)<\/span><\/h3>\n