Google Design Sprint School | RUN A DESIGN SPRINT

Google Design Sprint School | RUN A DESIGN SPRINT

Set the Stage

Before the sprint begins, you’ll need to have the right challenge and the right team. You’ll also need time and space to conduct your sprint.

Monday

Monday’s structured discussions create a path for the sprint week. In the morning, you’ll start at the end and agree to a long-term goal. Next, you’ll make a map of the challenge. In the afternoon, you’ll ask the experts at your company to share what they know. Finally, you’ll pick a target: an ambitious but manageable piece of the problem that you can solve in one week.

Tuesday

After a full day of understanding the problem and choosing a target for your sprint, on Tuesday, you get to focus on solutions. The day starts with inspiration: a review of existing ideas to remix and improve. Then, in the afternoon, each person will sketch, following a four-step process that emphasizes critical thinking over artistry. You’ll also begin planning Friday’s customer test by recruiting customers that fit your target profile.

Wednesday

By Wednesday morning, you and your team will have a stack of solutions. That’s great, but it’s also a problem. You can’t prototype and test them all—you need one solid plan. In the morning, you’ll critique each solution, and decide which ones have the best chance of achieving your long-term goal. Then, in the afternoon, you’ll take the winning scenes from your sketches and weave them into a storyboard: a step-by-step plan for your prototype.

Thursday

On Wednesday, you and your team created a storyboard. On Thursday, you’ll adopt a “fake it”philosophy to turn that storyboard into a prototype. A realistic façade is all you need to test with customers, and here’s the best part: by focusing on the customer-facing surface of your product or service, you can finish your prototype in just one day. On Thursday, you’ll also make sure everything is ready for Friday’s test by confirming the schedule, reviewing the prototype, and writing an interview script.

Friday

Your sprint began with a big challenge, an excellent team—and not much else. By Friday, you’ve created promising solutions, chosen the best, and built a realistic prototype. That alone would make for an impressively productive week. But you’ll take it one step further as you interviewcustomers and learn by watching them react to your prototype. This test makes the entire sprint worthwhile: At the end of the day, you’ll know how far you have to go, and you’ll know just what to do next.

Your sprint story

If you run a sprint, let us know! We’re collecting stories from the sprint community at SprintStories.com. Tweet us at @GVDesignTeam, or help spread the word below.

The Sprint book

A practical how-to guide for sprints, featuring behind-the-scenes stories from some of America’s most fascinating startups. Sprint is available now in hardcover, e-book, and audio.

Buy on Amazon   or see more ways to buy

From GV

Timer illustrationGV design partner Jake Knapp began running design sprints at Google in 2010. He worked with teams like Chrome, Google Search and Google X. In 2012, Jake brought sprints to GV, and the rest of the team chipped in their expertise to perfect the process.

Braden Kowitz added story-centered design, an unconventional approach that focuses on the customer journey instead of individual features or technologies. Michael Margolis took customer research—which can typically take weeks to plan and often delivers confusing results—and figured out a way to get crystal clear results in just one day. John Zeratsky helped us start at the end, and focus on measuring results with the key metrics from each business. And Daniel Burkabrought firsthand expertise as an entrepreneur to ensure every step made sense in the real world.