From Ideation to Proof in 5 days

Design Sprint

Today most companies use design sprint to cut down unneccessary risks while launching any new products, services or while introducing new features in the market. This process is time-constrained and may be divided into five phases which has been conceptualized by Jake Knapp, John Zeratsky and Braden Kowitz and now widely used across different industries. The main purpose of this approach is to assist the team in setting their goals clearly, validating key assumptions and also planning a product roadmap, before working on the code. Design sprint is similar to the Agile approach, where the key focus is on learning early and having shorter development cycles with lesser durations that typically lasts for a week.

Let’s look further to understand more about design sprint and learn about its history along with the key activities involved in this process.

What is a Design Sprint?

A design sprint is a framework comprising of five phases which is meant to answer some of the most challenging business questions through rapid prototyping along with user testing. The main purpose of sprints is to assist your team to achieve some of their pre-defined goals and deliverables in a quick manner. The key idea behind Design Sprint is building and testing a given prototype in just five days. Design sprint encourages user centric thinking, promotes collaboration, leads to innovation and helps to align the team to work towards a shared vision thereby, enabling companies to launch their products swiftly into the market.

History of the Design Sprint Framework-How did it evolve?

In 2010, the Google Design Sprint framework was conceptualized by Jake Knapp while he was working at Google Ventures or GV and their origins can be traced back to the IDEO and the Institute of Design at Stanford. He also took inspiration from different places such as Google’s product development centre and also used his own experience building products such as Gmail and Hangouts. In 2012, he was successful in getting Design Sprints to Google Ventures, where the additional members of the team got a chance to provide their expertise for refining the process. Braden Kowitz used the approach of story centered design which laid emphasis on the user rather than the technologies or features of the product. Michael Margolis focused on customer research to get crisp and clear results within just one day, which would otherwise take months of planning and still not yield the best results.

John Zeratsky chose core metrics from every business to get measured results while Daniel Burka brought in his expertise as an entreprenuer to ensure that every step would be able to deliver the right results for startups.

In 2012-13, the Google Ventures team published a book that featured how-to series on Design Sprints and that is how this process came to known among the communities. In 2016, the Sprint book was launched which led to many businesses embracing and experimenting with sprints in big companies along with startups.