Design Sprint

Rojesh Shrestha
Devnetwork
Published in
2 min readApr 14, 2017

We have always been busy in adding new features using new and cool technologies. But in the process, we seem to fail to realize how these features are being perceived or used by the end users. The design sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers.

Normally our approach towards developing new features has been building the idea that seems cool or helpful, launching it and testing it with end users. The problem with this approach is building the prototype and launching it takes time. And after launching it if we realize that the feature was not helpful to the end users then both our time and resources are wasted. This is when the concept of design sprint comes into play.

Stages of Design Sprint

Understand

On the first day of the sprint, we start by finding out the problem that we want to solve. We involve people or experts who can help us better understand the problem.

Define

After having detail understanding of the problem, we start to focus on strategy. In this stage, we decide what we want to achieve for our end users. This is also a part of the first-day exercise.

Diverge

On the second day, each member diverges and starts focusing on their own ideas or solutions separately, following a four-step process that emphasizes critical thinking over artistry.

Decide

On the third day, each member comes up with a stack of solutions. The team then reviews and critique all the ideas and vote for the best options. The team can choose 1–3 ideas to prototype and test.

Prototype

On the fourth day, we start converting the idea that has been chosen for prototyping into the storyboard. Then we adopt a ‘fake it’ philosophy to turn that story into the prototype. Rapid prototyping allows us to test out your ideas without investing a ton of time, money, or resources.

Validate

On the final day of the sprint, the prototype is validated with the set of testers by interviewing them and seeing how they react to the prototype. The very good thing about this approach is we will know how far we have to go, and we will also know just what to do next.

--

--