This is Chapter 1 from “Design Sprint: A Practical Guidebook for Building Great Digital Products,” by Richard Banfield, C Todd Lombardo, and Trace Wax. Design Sprint was just recently named one of the 100 Best Product Design Books of All Time by The Book Authority (#8 for those who are counting!). NOTE: I have included links to additional, related Design Sprint resources within the post that are not part of the book chapter. These resources are denoted by a “- — -” divider.
The big idea with the Design Sprint is to build and test a prototype in just five days. You'll take a small team, clear the schedule for a week, and rapidly progress from problem to tested solution using a proven step-by-step checklist. It's like fast-forwarding into the future so you can see how customers react before you invest all the time and expense of building a real product.
What Google learned from their research is similar to what developed within IDEO over the course of 30 years where trust, purpose, and impact have evolved to become central to IDEO’s culture. There’s a focus on establishing trust and building relationships by designing intentional moments, which we call rituals. For example, IDEO’s weekly tea time ritual was designed as a way to encourage collaboration and “casual collisions”—a time when people step away from what they’re working on and connect with each other. Small, consistent moments like tea time are a prime way to deepen relationships and trust over time.
But probably the most valuable benefit of design sprints is that they introduce stakeholders to the importance of validating ideas with real users. Google has orientated the whole week around building a prototype that users find easy to use. That is a valuable lesson for colleagues who can often be more focused on their own agenda, rather than that of the user.
Once we have an understanding of the foundation we all need to run a successful design sprint, we kick off by working through the sprint’s Monday exercises — setting a proper long term goal based on our sprint challenge, determining our sprint questions, creating a map, interviewing experts, connecting our personas to the map, and selecting a target.
Access to all the course videos, that not only describe the process in a great deal of detail, but also the mindset and very concrete tactics that you can put to work immediately. You also get access to all the bonus materials, including the Design Sprint cheatsheet, the preparation checklist, and facilitators toolkit, and lifetime access to the AJ&Smart Design Sprint community. As a student on the course you'll get lifetime access to all course improvements (we’re a big believer of continuous improvements, and you’ll get to benefit from this!)
“Sprints begin with a big challenge, an excellent team — and not much else. By Friday of your sprint week, you’ve created promising solutions, chosen the best, and built a realistic prototype. That alone would make for an impressively productive week. But Friday, you’ll take it one step further as you interview customers 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.”
For this design sprint training resource we will focus on the 5 day format from the Sprint book since it is the most widely known with tools and resources we can use in design sprint training workshops. If you are looking for a design sprint facilitator or design sprint training, email us at [email protected] and we can recommend one of more than 10 excellent trainers or facilitators in our network across the globe.
We added a new exercise here that makes the storyboarding process at least 27 times easier (give or take). It’s called User Test Flow and it’s a form of Note & Vote exercise. Everyone designs the barebones of their own storyboard and then we vote on the one or two that we end up prototyping. Even though it’s an extra step, it speeds up the storyboarding process by a million miles and eliminates the “designing by committee” aspect of it. Here’s a video that explains it in detail (and there’s a Medium post on it, too). https://res.cloudinary.com/practicaldev/image/fetch/s--Kjt27KoI--/c_fill,f_auto,fl_progressive,h_50,q_auto,w_50/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/92605/70cd7f2f-e0f0-4603-922c-b1048cbd9a7e.jpg
But probably the most valuable benefit of design sprints is that they introduce stakeholders to the importance of validating ideas with real users. Google has orientated the whole week around building a prototype that users find easy to use. That is a valuable lesson for colleagues who can often be more focused on their own agenda, rather than that of the user. https://www.tatvasoft.com/blog/wp-content/uploads/2015/12/joint_application_development_methodology.jpg
Design Sprints started at Google to spark collaborative creativity, solve complex business problems and reduce the risk of failure when launching a new product to the market. Since the Sprint book came out in 2016, Design Sprints have become widely adopted globally by companies as a tool for innovation and problem-solving and one of the most hyped processes around.
You’re the product person in your organization. You may have no one reporting to you. You might have 50 people in your product group. You might be responsible for the entire product. Maybe the design team doesn’t report to you, nor do the developers or marketing and sales teams. Maybe you’re in a startup without all those defined roles, and you wear a lot of hats. Maybe you’re in a large enterprise organization that has each one defined to the nth degree. Maybe you are a product design freelancer. You might work in an agency as a consultant. You probably have read a blog post about this process. Maybe you even tried one yourself. You’re very likely wondering how your unique needs will work with design sprints and are seeking more information than you can find in a few blog posts. https://res.cloudinary.com/practicaldev/image/fetch/s--gk0eqZrY--/c_imagga_scale,f_auto,fl_progressive,h_100,q_auto,w_100/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/64057/722ec19f-029b-479d-a34b-33cf27a5fe79.jpg
Use the Tabata training method of product design. Tabata training is a workout method that focuses on 20 seconds of intense work followed by 10 seconds of rest. This is a great metaphor for sprint prototyping: It’s intense, and that means that rest is just as important as the creative bursts. Make a point of managing team energy by having intentional down days. With Swell, we made sure to keep our energy up by working in cafes, getting breather spaces when we needed to focus, and even hitting up museums or exercise classes to stay healthy and inspired.