{"id":79633,"date":"2022-09-20T10:01:00","date_gmt":"2022-09-20T14:01:00","guid":{"rendered":"https:\/\/www.shortform.com\/blog\/?p=79633"},"modified":"2022-10-03T11:59:56","modified_gmt":"2022-10-03T15:59:56","slug":"design-sprint-jake-knapp","status":"publish","type":"post","link":"https:\/\/www.shortform.com\/blog\/design-sprint-jake-knapp\/","title":{"rendered":"Jake Knapp’s Design Sprint Book: Overview & Takeaways"},"content":{"rendered":"\n

Looking for an overview of Sprint<\/em>? What is Jake Knapp’s Design Sprint process? What are the book’s key takeaways?<\/p>\n\n\n\n

Jake Knapp developed the Design Sprint while working at Google Ventures, the investment arm of Google\u2019s parent company. His process allows you and your team to build and test a prototype in just a five-day work week. <\/p>\n\n\n\n

Keep reading for an overview of Jake Knapp’s book Sprint<\/em> and the Design Sprint process.<\/p>\n\n\n\n\n\n\n\n

Sprint<\/em> by Jake Knapp: Book Overview<\/h2>\n\n\n\n

Do you have an idea for a product, but you\u2019re not sure how to turn it into a testable prototype? Maybe you\u2019re not even sure it\u2019s worth pursuing at all. Well, using Jake Knapp\u2019s Design Sprint process, you can build and test prototype products within a five-day work week,<\/strong> helping you determine your idea\u2019s viability quickly and cheaply. <\/p>\n\n\n\n

Jake Knapp invented the Design Sprint process while working for Google. After moving to Google Ventures (GV), he facilitated sprints with over a hundred companies, including Slack, Airbnb, and Spotify. Designers John Zeratsky and Braden Kowitz collaborated with Knapp at GV to refine the process, and Zeratsky and Knapp later co-authored a book on time management, Make Time<\/em><\/a>. All three are experts in efficiency, productivity, and team improvement strategies. <\/p>\n\n\n\n

(Shortform note: At its most basic level, a Design Sprint is a set amount of time in which a team works on a set of tasks to create a testable version of a product. Sprints gained their name due to their short duration and the high intensity of the work involved.) <\/p>\n\n\n\n

In this article, we\u2019ll show you what to do on each day of your sprint in a step-by-step format. In our commentary, we\u2019ll teach you about the underlying principles behind the Design Sprint and provide examples of a sprint in practice. <\/p>\n\n\n\n

(Shortform note: The authors organize their information about sprints into a day-by-day guide. This is arguably the most effective structure because each day’s tasks build on the day before, creating a smooth progression from planning your prototype, to building it, to testing it. Within each day, we\u2019ve broken down the authors\u2019 instructions into clearer steps and added new examples to more clearly illustrate the chronology of each day\u2019s activities.) <\/p>\n\n\n\n

The Evolution of the Design Sprint: Its Roots in Design Thinking<\/strong>

One source of inspiration Jake Knapp found for his Design Sprint process was IDEO\u2019s design thinking workshops<\/a>. The Design Sprint follows many of the same principles as design thinking: a process designers use to understand the needs of users, solve design problems, and develop products and services. 

Like the Design Sprint, design thinking is an iterative<\/em> process<\/a>. This involves creating many versions of the same idea and improving your idea using the information you gain from each iteration. Ultimately, design thinking can be broken down into two parts: identifying a problem and developing a solution<\/strong>. 

A design thinking process cycles through four phases, which repeat as many times as is necessary to create the best product. 

– First, there is the observation phase<\/strong>, when designers gather information about the customers who\u2019ll use their product.

– Second is the idea generation phase,<\/strong> when designers come up with as many solutions as they can to the problem they want to solve with their product.

– Third is the prototype phase,<\/strong> when designers create sketches and models of the best ideas generated in the second phase. 

– Fourth is the testing phase,<\/strong> when designers have their target customers test the prototype product and give feedback. 

A sprint goes through one cycle of these phases: A series of multiple sprints, each testing different iterations of the same product, would look more like a typical design thinking process. Another distinction between design sprints and design thinking is that sprints follow a strict schedule, which is not always required for a design thinking cycle.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Day 1: Planning the Sprint and the Customer Experience<\/h3>\n\n\n\n

Now that you\u2019ve prepared for your Design Sprint, on Monday, Knapp, Zeratsky, and Kowitz suggest identifying a goal for your project and the questions you want your sprint to answer. You\u2019ll also plan a customer\u2019s experience with your product, from their first encounter with it through the full process of using it.<\/p>\n\n\n\n

Identify Goals and Questions<\/h4>\n\n\n\n

The authors say to start off Monday by deciding on a goal with your team. It can be as broad and lofty as you want. When choosing your goal, think about the purpose of your project and what you hope it will achieve in the near and distant future. The information you learn from your sprint will help you progress toward this long-term aspiration.<\/strong> <\/p>\n\n\n\n

For example, say there\u2019s a team from a bookstore who are using their sprint to develop a prototype for a personalized book recommendation feature on their website. Their broader, long-term goal is to create a personalized online retail experience for their customers. Creating a successful recommendation tool would be one step toward reaching that goal. <\/p>\n\n\n\n

(Shortform note: Other authors also advise starting the development process with clear goals for your product\u2019s future. Marty Cagan (Inspired<\/em><\/a>)<\/em> calls this your \u201cvision\u201d in his product discovery process<\/a>. To create a strong vision for your product, he suggests defining a clear \u201cwhy\u201d: You need to articulate why<\/em> you think your product will be successful. Additionally, don\u2019t be afraid to dream big. If your vision isn\u2019t ambitious, it probably isn\u2019t worth pursuing. Your vision should excite and inspire every member of your team.)<\/p>\n\n\n\n

After you\u2019ve identified your goal, the authors note, you must consider the challenges that could prevent you from achieving it. Identifying these now will help ensure that you\u2019re not surprised by a new obstacle later on in the design process. On a whiteboard, rework these challenges into a short list of questions you want to be answered by the end of the sprint.<\/p>\n\n\n\n

For example, one challenge of the bookstore\u2019s recommendation tool could be its algorithm not picking up on the subtler qualities of books that make spontaneous, creative recommendations from a bookstore employee so special. The question related to this problem would then be, \u201cCan an automated recommendation service provide the same quality of recommendations as a bookstore employee?\u201d<\/p>\n\n\n\n

Day 2: Creating a Design<\/h3>\n\n\n\n

On Monday, you narrowed down your priorities for the Design Sprint. Now you know where you\u2019ll focus your attention during your sprint. On Tuesday, Knapp, Zeratsky, and Kowitz suggest you gather inspiration for your idea, create a drawing of your best design idea, and begin recruiting customers for Friday\u2019s interviews. <\/p>\n\n\n\n

Gather Inspiration<\/h4>\n\n\n\n

The authors argue that every good idea builds off of what came before, <\/strong>so you\u2019ll start on Tuesday morning by gathering inspiration from other products and services. Every team member should make a list of products, either from your company or from another, that have features you can emulate in your own product. In short presentations, each person will explain the contents of their lists. As people present, record every product mentioned with a little sketch and blurb explaining what inspiration it has to offer. <\/p>\n\n\n\n

(Shortform note: Drawing from other people\u2019s products to create your design may feel strange. It may even feel like stealing. To get better as a designer, however, you have to study the products you admire to understand what makes them so successful.<\/a> If you synthesize the successful elements you identify with your own ideas and experiences, you can create an original product with its own unique value<\/a>. This doesn\u2019t mean copying or even refashioning. It means adding your perspective to an existing conversation.)<\/p>\n\n\n\n

Draw Your Ideas<\/h4>\n\n\n\n

Once you\u2019ve reviewed your outside examples, it\u2019s time to start drawing concrete designs for your product. Knapp, Zeratsky, and Kowitz outline a four-part process that each team member will complete individually<\/em> on Tuesday afternoon. You will refine your ideas more with each part.<\/p>\n\n\n\n

Day 3: Making Decisions<\/h3>\n\n\n\n

After spending Tuesday producing ideas for your Design Sprint, Jake Knapp instructs you to spend Wednesday deciding which one to pursue. Once your team leader selects the one you\u2019ll use to inform your next steps, you\u2019ll create a storyboard to plan for Thursday\u2019s prototype.<\/p>\n\n\n\n

Storyboard the Prototype<\/h4>\n\n\n\n

Once your team leader has selected a design, the authors instruct you to draw a more extensive storyboard of your prototype in use (10 to 15 panels on a whiteboard). Start by drawing the moment and the context in which the customer first engages with the product. For example, the first panel of the bookstore\u2019s storyboard could show a web search for the bookstore\u2019s website.<\/p>\n\n\n\n

Fill in the other panels with steps that a customer will have to go through to use your product from start to finish. As the authors say, you\u2019re telling the story of what you want to happen during Friday\u2019s tests with customers.<\/strong> For example, the middle panels of the bookstore\u2019s storyboard might include a drawing of each question prompt the customer will be asked before they receive their recommendations. They\u2019d depict the layout of each screen, the important text involved, any images included, and so on. The last few panels might depict the various recommendations the customer received, showing what the profile for each recommended book would look like. <\/p>\n\n\n\n

Day 4: Creating the Prototype<\/h3>\n\n\n\n

Wednesday was decision day\u2014now, it\u2019s time to use the storyboard you created to build your prototype.<\/p>\n\n\n\n

Before you begin building, divide responsibilities for the creation of the prototype. Knapp, Zeratsky, and Kowitz recommend filling the following roles.<\/strong><\/p>\n\n\n\n