SPRINT

Jake Knapp a Google venture partner, alongside John Zeratsky and Braden Kowitz birth the idea of Sprint which majors on how to solve problems and test new ideas in just five days. This book is a practical guide to choose among many best ideas and make most out of the experience.  The concept of sprint came up when Jack had to come up with an essential feature for Gmail which would automatically sort messages. He had to innovate fast. To do that, he came up with three key aspects to manage the project process:

DEADLINES: Tight deadlines eliminate procrastination. The shorter the time, the faster the result because every allotted time is filled with an activity

GET PEOPLE WITH DIFFERENT SKILL SETS: Get people with a different skill set into one room. The more diverse a team is, the better.  A better sprint team usually consists of seven categories of people and less irrespective of their hierarchy level.

THE RESULT: The result must be a concrete prototype. What gets you real feedback is when you present a functional idea. Brainstorming vague ideas is easy but not worth it.

These three-fundamental concepts work well when each sprint get together one on one and work together to produce something of actual value.

Jack furthermore explains sprint as a method that helps define a problem, compare ideas, prototype one of them and get feedback from customers all in five days. Though it might seem like an intensive process, it has a great potential for a big payout.

Before the sprint process, a recommended number of seven people with a different skill sets must be included:

• The Decider (someone who have enough information on the problem or the leader of the company

• The Marketing Expert

• The Finance Expert

• The Customer Expert (someone who has a unique customer view preferably from the customer care unit)

• An Engineer or Logic Expert

• The Troublemaker (Someone who always have contrary opinion)

• The Facilitator (someone who is unbiased about a decision and keeps things on time). Usually a project manager).

The idea is to make sure everyone on the team understands the problem that needs to be solved and create a purposeful start on Monday.

Jack did a great job by defining the purpose of each day and what needs to be accomplished.

Monday’s goal is to create a discussion around the set goal, map out the challenge and define the problem that will be tackled on the sprint

Tuesday’s goal is to find a solution to the problem identified on Monday. Each person on the team writes down their proposed solution on a piece of paper and is given at least three minutes to present the solution to the whole team out of which the best there will be selected.

Wednesday’s goal is to make a decision. The best way is to critique all ideas and choose the one that will be explored in the sprint. This can be done by discussing sketches and then participants can get to vote via color stickers for their favorite idea. It is advisable to keep all ideas anonymous to avoid skewing of people’s opinion. Once the idea is picked, the team can then storyboard the prototype

Thursday’s goal is to make a prototype of the concept selected on Wednesday. Not a perfect prototype but a reality. The team can make use of keynotes or interactive prototypes other than professional tools. Professional tools take longer time and make you focus on too many details.

Friday’s goal is to see the customer’s reactions by interviewing them. You do not need thousands of customers to carry out the interview; five to six people is enough to expose 85% of the problem and get qualitative feedback. Record your conversations so the team can see the result. Jack gave some hints on how the interview process should go like interacting with the customer, putting the customer at ease, etc.

Once the interview is concluded, the team should go ahead and analyze the result to know if the prototype us promising and deserves further development or if the prototype fails.

Either way, design sprint is a way of finding answers to big questions, bring attention to work that matter, reduce risk and get better solutions.

THE BIG THREE – KEY POINTS

Key point #1:  Design Sprint reduces risk, proffers the answer to significant problems and brings about a better solution.

Key point #2: Sprint is not a one-man business; it can best be carried out by a team made up of different skill sets.

Key point #3: The core concept of Sprint is to decrease the waste of resources (time, energy and money) on the wrong ideas.

One Last Thing

“By asking people for their input early in the process, you help them feel invested in the outcome.”

― Jake Knapp, Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days