Add Prime to get Fast, Free delivery

Kindle
$16.99

Available instantly

Audiobook
$0.99
with membership

Hardcover
$16.99

Paperback
$25.35

$16.99 with 48 percent savings

List Price: $32.50

Get Fast, Free Shipping with Amazon Prime FREE Returns

FREE delivery Monday, January 13 on orders shipped by Amazon over $35

Or Prime members get FREE delivery Tomorrow, January 9. Order within 21 hrs 37 mins.

In Stock

$$16.99 () Includes selected options. Includes initial monthly payment and selected options. Details

Ships from

Amazon.com

Sold by

Amazon.com

Returns

30-day refund/replacement

Payment

Secure transaction

Add a gift receipt for easy returns

$8.26

Get Fast, Free Shipping with Amazon Prime FREE Returns

Used book in good and clean conditions. Pages and cover are intact. Limited notes marks and highlighting may be present. May show signs of normal shelf wear and bends on edges. Item may be missing CDs or access codes. May include library marks. Ships directly from Amazon. Used book in good and clean conditions. Pages and cover are intact. Limited notes marks and highlighting may be present. May show signs of normal shelf wear and bends on edges. Item may be missing CDs or access codes. May include library marks. Ships directly from Amazon. See less

FREE delivery Monday, January 13 on orders shipped by Amazon over $35

Or fastest delivery Sunday, January 12. Order within 21 hrs 37 mins

Only 1 left in stock - order soon.

$$16.99 () Includes selected options. Includes initial monthly payment and selected options. Details

Access codes and supplements are not guaranteed with used items.

Enhancements you chose aren't available for this seller. Details

${cardName} not available for the seller you chose

${cardName} unavailable for quantities greater than ${maxQuantity}.

Sold by ZBK Wholesale and Fulfilled by Amazon.

Other sellers on Amazon

New & Used (160) from $2.24

Image Unavailable

Image not available for
Color:

To view this video download Flash Player

Follow the authors

Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days Hardcover – Illustrated, March 8, 2016

by Jake Knapp (Author), John Zeratsky (Author), Braden Kowitz (Author)

4.6 4,578 ratings

See all formats and editions

{"desktop_buybox_group_1":[{"displayPrice":"$16.99","priceAmount":16.99,"currencySymbol":"$","integerValue":"16","decimalSeparator":".","fractionalValue":"99","symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"HP%2BBiPvHqPP8AAv40ND1xxQai5ZO7gRrcn7AndutuDOwWuI3QJOQ7gSRTd2OWdWfJXSeosZ13DNk8eItCZO6olpFJyG5OW99QSo%2B8NuHN8M4Bo4letLal6RkgJ6jX2GSdZpYPS6iv135N1QvUIqn6g%3D%3D","locale":"en-US","buyingOptionType":"NEW","aapiBuyingOptionIndex":0}, {"displayPrice":"$8.26","priceAmount":8.26,"currencySymbol":"$","integerValue":"8","decimalSeparator":".","fractionalValue":"26","symbolPosition":"left","hasSpace":false,"showFractionalPartIfEmpty":true,"offerListingId":"HP%2BBiPvHqPP8AAv40ND1xxQai5ZO7gRrR%2BeRz9mwCqaymjKzZFLdKS7fTG2tkKiucthwCWpStqxI32YolzokryjXL17kX1tE5LlA4rupSMBAsArxYFx6U2AqtGE923KqCKKXixJPf4pcYgTPio1Bt0dv4yya9d%2FHo19ILDsnaCJZlW%2B%2FMvZzLX8gH0tWfb4h","locale":"en-US","buyingOptionType":"USED","aapiBuyingOptionIndex":1}]}

Purchase options and add-ons

From inside Google Ventures, a unique five-day process for solving tough problems, proven at thousands of companies in mobile, e-commerce, healthcare, finance, and more.

Entrepreneurs and leaders face big questions every day: What’s the most important place to focus your effort, and how do you start? What will your idea look like in real life? How many meetings and discussions does it take before you can be sure you have the right solution?

Now there’s a surefire way to answer these important questions: the Design Sprint, created at Google by Jake Knapp. This method is like fast-forwarding into the future, so you can see how customers react before you invest all the time and expense of creating your new product, service, or campaign.

In a Design Sprint, you take a small team, clear your schedules for a week, and rapidly progress from problem, to prototype, to tested solution using the step-by-step five-day process in this book.

A practical guide to answering critical business questions, Sprint is a book for teams of any size, from small startups to Fortune 100s, from teachers to nonprofits. It can replace the old office defaults with a smarter, more respectful, and more effective way of solving problems that brings out the best contributions of everyone on the team—and helps you spend your time on work that really matters.

Editorial Reviews

Review

“Every business leader I know worries about the same thing: Are we moving fast enough? The genius of Jake Knapp’s Sprint is its step-by-step breakdown of what it takes to solve big problems and do work that matters with speed and urgency. A sprint is a cure for what ails companies in an ever faster world.”
—Beth Comstock, vice chair of GE

"The key to success, often, is building the right habits. But which habits work best? Sprint offers powerful methods for hatching ideas, solving problems, testing solutions—and finding those small, correct habits that make all the right behaviors fall in place."
– Charles Duhigg, author of The Power of Habit

"To quote one of my colleagues, “don’t get ready, get started”. Through hard won experience Jake Knapp and the team at Google Ventures have refined an efficient, hands-on approach to solving your product, service and experience design challenges. Try the book and try a Sprint."
– Tim Brown, CEO of IDEO and author of Change By Design

"Read this book and do what it says if you want to build better products faster."
– Ev Williams, founder of Medium, Blogger, and Twitter

"Sprint teaches you a novel process for solving really thorny problems in just 5 days. It's full of helpful, entertaining stories that will make it easier for you to succeed. What more, exactly, would you demand from a book? I wish all business books were this useful."
– Dan Heath, co-author of Made to Stick, Switch, and Decisive

About the Author

Jake Knapp is cofounder and general partner at Character Capital and a New York Times bestselling author. Previously, he helped build Gmail and Microsoft Encarta, cofounded Google Meet, and was a partner at Google Ventures. He lives on Orcas Island in Washington state.

John Zeratsky is cofounder and general partner at Character Capital and a New York Times bestselling author. Previously, JZ was a design leader for YouTube, Google Ads, and FeedBurner, a startup which was acquired by Google in 2007, and was a partner at Google Ventures. He lives in Milwaukee, Wisconsin.

Braden Kowitz founded the Google Ventures design team in 2009 and pioneered the role of “design partner” at a venture capital firm. He has advised close to two hundred startups on product design, hiring, and team culture. Before joining Google Ventures, Braden led design for several Google products, including Gmail, Google Apps for Business, Google Spreadsheets, and Google Trends.

Excerpt. © Reprinted by permission. All rights reserved.

Sprint 1 Challenge
In 2002, a clarinet player named James Freeman quit his job as a professional musician and founded . . . a coffee cart.

James was obsessed with freshly roasted coffee. In those days in the San Francisco area, it was nearly impossible to find coffee beans with a roast date printed on the bag. So James decided to do it himself. He carefully roasted beans in a potting shed at home, then drove to farmers’ markets in Berkeley and Oakland, California, where he brewed and sold coffee by the cup. His manner was polite and accommodating, and the coffee was delicious.

Soon James and his cart, called Blue Bottle Coffee, developed a following. In 2005, he established a permanent Blue Bottle location in a friend’s San Francisco garage. Over the next few years, as the business grew, he slowly opened more cafés. By 2012, Blue Bottle had locations in San Francisco, Oakland, Manhattan, and Brooklyn. It was a business that many would have considered perfect. The coffee was ranked among the best nationwide. The baristas were friendly and knowledgeable. Even the interior design of the cafés was perfect: wooden shelves, tasteful ceramic tiles, and an understated logo in the perfect shade of sky blue.

But James didn’t consider the business perfect, or complete. He was still just as passionate about coffee and hospitality, and he wanted to bring the Blue Bottle experience to even more coffee lovers. He wanted to open more cafés. He wanted to deliver freshly roasted coffee to people’s homes, even if they didn’t live anywhere near a Blue Bottle location. If that coffee cart had been Sputnik, the next phase would be more like a moon shot.

So in October 2012, Blue Bottle Coffee raised $20 million from a group of Silicon Valley investors, including GV. James had many plans for that money, but one of the most obvious was building a better online store for selling fresh coffee beans. But Blue Bottle wasn’t a tech company and James was no expert at online retail. How could he translate the magic of his cafés to smartphones and laptops?

Several weeks later, on a bright December afternoon, Braden Kowitz and John Zeratsky met up with James. They sat around a counter, drank coffee, and discussed the challenge. The online store was important to the company. It would take time and money to get it right, and it was difficult to know where to start. In other words, it sounded like a perfect candidate for a sprint. James agreed.

They talked about who should be in the sprint. An obvious choice was the programmer who would be responsible for building Blue Bottle’s online store. But James also included Blue Bottle’s chief operating officer, chief finance officer, and communications manager. He included the customer service lead who handled questions and complaints. He even included the company’s executive chairman: Bryan Meehan, a retail expert who started a chain of organic grocery stores in the UK. And, of course, James himself would be in the room.

The online store was essentially a software project—something our team at GV was very familiar with. But this group looked almost nothing like a traditional software team. These were busy people, who would be missing a full week of important work. Would the sprint be worth their time?

• • •

On Monday morning of our sprint week, the Blue Bottle team gathered in a conference room at GV’s office in San Francisco. We made a diagram on the whiteboard showing how coffee buyers might move through the online store. The Blue Bottle team targeted a new customer purchasing coffee beans. James wanted to focus the sprint on this scenario because it was so difficult. If they could establish credibility and create a great experience for someone who had never heard of Blue Bottle, let alone visited their cafés or tasted their coffee, then every other situation should be easy by comparison.

We ran into a big question: How should we organize the coffee? The shopper in this scenario would be choosing between a dozen or so varieties of bean, each in a nearly identical bag. And—unlike in Blue Bottle’s cafés—there would be no barista there to help choose.

At first, the answer seemed obvious. From boutique coffee roasters to mainstream giants like Starbucks, retailers tend to organize coffee by the geographic region where it was grown. Africa, Latin America, the Pacific. Honduran coffee vs. Ethiopian coffee. It would be logical for Blue Bottle to categorize their beans the same way.

“I have to admit something,” Braden announced. Everyone turned. “I’m into coffee, okay? I have a scale at home and everything.” Electronic scales are the hallmark of a true coffee freak. Owning a scale meant Braden weighed the water and coffee beans so that he could experiment and adjust ratios as he brewed. We’re talking science here. Coffee scales are accurate to a fraction of a gram.

Braden smiled and held his hands palm up. “I don’t know what the regions mean.” There was silence. We avoided looking at James. After all, Braden’s brave admission might be seen as heresy.

“That’s okay,” said James. The floodgate opened. John and Jake didn’t know the difference between coffee regions, and neither did Daniel Burka. We drank coffee together constantly, but none of us had ever admitted to our lack of sophistication.

Then Serah Giarusso, Blue Bottle’s customer service lead, snapped her fingers. “What do we do in the cafés?” she asked. After all, she went on, The Braden Situation must happen to baristas all the time: a customer comes in for coffee beans, but isn’t sure which kind to buy.

James is a slow and thoughtful speaker. He paused for a moment before he answered. “The brew method is very important,” he said. “So we train the baristas to ask the customer a simple question: ‘How do you make coffee at home?’?” James explained that, depending on whether the customer used a Chemex, or a French press, or a Mr. Coffee, or whatever, the baristas could recommend a bean to match.

“?‘How do you make coffee at home . . . ?’?” Braden repeated. Everyone jotted notes. James had started the sprint by explaining his vision: that the online store should match the hospitality of the cafés. It felt as if we were onto something.

The team spent the following day sketching ideas for the store. On Wednesday morning we had fifteen different solutions. That’s too many to test with customers, so the team voted on their favorites as a way to narrow it down. Then James, the decision-maker, made the final pick of three sketches to test.

The first sketch showed a literal approach to making the website match the cafés: It looked like the inside of a Blue Bottle café, complete with wooden shelves. The second sketch included lots of text, to mirror the conversations baristas often have with customers. Finally, James chose a third sketch that organized coffee by brew method, bringing the “How do you make coffee at home?” question right onto the computer screen.

James had chosen three competing ideas. So which one should we prototype and test? The idea of a website that looked like the café was the most appealing. Blue Bottle’s aesthetic is celebrated, and a matching website would look different from anything else in the market. We had to try that idea, and it wasn’t compatible with the other solutions. But those other solutions were also really intriguing. We couldn’t quite decide.

So we decided to prototype all three. After all, we didn’t need a functioning website. To appear real in our test, each fake online store only required a few key screens. Working together with the Blue Bottle team, we used Keynote presentation software to make a series of slides that looked like three real websites. With a little ingenuity, and without any computer programming at all, we stitched those screens into a prototype that our test customers could use.

On Friday, the team watched the customer interviews. One at a time, coffee drinkers shopped on several websites, with Blue Bottle’s three prototypes slipped in among the competitors. (To avoid tipping off the customers, we gave each prototype a fake name.)

Patterns emerged. The store with wooden shelves, which everyone had such high hopes for? We thought the prototype was beautiful, but customers said it was “cheesy” and “not trustworthy.” But the other two prototypes fared far better. The “How do you make coffee at home?” design worked seamlessly. And the “lots of text” design shocked us: People actually read all those words, and the extra information brought Blue Bottle’s voice and expertise to life. As one customer said, “These guys know coffee.”

James and the Blue Bottle team built confidence with their sprint. They were much closer to defining how their online store would work. What’s more, they’d done it in a way that felt true to their principles of hospitality. They believed the online store could be an authentic Blue Bottle experience.

A few months later, Blue Bottle launched their new website, and their online sales growth doubled. The next year, they acquired a coffee subscription company. With a bigger team and new technology, they expanded the web store and began experimenting with new offerings. They knew it would take years to get the online store right—but in the sprint, they started on their path.
The bigger the challenge, the better the sprint
If you’re starting a project that will take months or years—like Blue Bottle and their new online store—a sprint makes an excellent kickoff. But sprints aren’t only for long-term projects. Here are three challenging situations where sprints can help:

High Stakes

Like Blue Bottle Coffee, you’re facing a big problem and the solution will require a lot of time and money. It’s as if you’re the captain of a ship. A sprint is your chance to check the navigation charts and steer in the right direction before going full steam ahead.

Not Enough Time

You’re up against a deadline, like Savioke rushing to get their robot ready for the hotel pilot. You need good solutions, fast. As the name suggests, a sprint is built for speed.

Just Plain Stuck

Some important projects are hard to start. Others lose momentum along the way. In these situations, a sprint can be a booster rocket: a fresh approach to problem solving that helps you escape gravity’s clutches.

When we talk to startups about sprints, we encourage them to go after their most important problem. Running a sprint requires a lot of energy and focus. Don’t go for the small win, or the nice-to-have project, because people won’t bring their best efforts. They probably won’t even clear their schedules in the first place.

So how big is too big? Sure, sprints work great for websites and other software challenges. But what about really large, complicated problems?

Not long ago, Jake visited his friend David Lowe, a vice president of a company called Graco that manufactures pumps and sprayers. Graco is not a small startup. They’re a multinational company who have been in business for more than ninety years.

The company was developing a new kind of industrial pump—a machine used in assembly lines. David, the VP, wondered if a sprint might help lower the risk of the project. After all, it would take eighteen months and millions of dollars to design and manufacture the new pump. How could he be sure they were on the right track?

Jake doesn’t know anything about industrial assembly lines, but out of curiosity, he joined a meeting with the engineering team. “I’ll be honest,” Jake said. “An industrial pump sounds too complicated to prototype and test in a week.”

But the team wouldn’t give up so easily. If limited to just five days, they could prototype a brochure for the pump’s new features and try it in sales visits. That kind of test could answer questions about marketability.

But what about the pump itself? The engineers had ideas for that, too. To test ease-of-use, they could 3D print new nozzles and attach them to existing pumps. To test installation, they could bring cables and hoses to nearby manufacturing plants and get reactions from assembly line workers. These tests wouldn’t be perfect. But they would answer big questions, before the pump even existed.

Jake was wrong. The industrial pump wasn’t too complicated for a sprint. The team of engineers accepted the five-day constraint and used their domain expertise to think creatively. They sliced the challenge into important questions, and shortcuts started to appear.

The lesson? No problem is too large for a sprint. Yes, this statement sounds absurd, but there are two big reasons why it’s true. First, the sprint forces your team to focus on the most pressing questions. Second, the sprint allows you to learn from just the surface of a finished product. Blue Bottle could use a slide show to prototype the surface of a website—before they built the software and inventory processes to make it really work. Graco could use a brochure to prototype the surface of a sales conversation—before they engineered and built the product they were selling.
Solve the surface first
The surface is important. It’s where your product or service meets customers. Human beings are complex and fickle, so it’s impossible to predict how they’ll react to a brand-new solution. When our new ideas fail, it’s usually because we were overconfident about how well customers would understand and how much they would care.

Get that surface right, and you can work backward to figure out the underlying systems or technology. Focusing on the surface allows you to move fast and answer big questions before you commit to execution, which is why any challenge, no matter how large, can benefit from a sprint.

Product details

Publisher ‏ : ‎ Simon & Schuster; Illustrated edition (March 8, 2016)
Language ‏ : ‎ English
Hardcover ‏ : ‎ 288 pages
ISBN-10 ‏ : ‎ 150112174X
ISBN-13 ‏ : ‎ 978-1501121746
Item Weight ‏ : ‎ 1.3 pounds
Dimensions ‏ : ‎ 5.5 x 1 x 8.38 inches

Best Sellers Rank: #17,644 in Books (See Top 100 in Books)
- #42 in Business Decision Making
- #63 in Decision-Making & Problem Solving
- #142 in Entrepreneurship (Books)

Customer Reviews:
4.6 4,578 ratings

Brief content visible, double tap to read full content.

Full content visible, double tap to read brief content.

Videos

Help others learn more about this product by uploading a video!

Upload your video

About the authors

Follow authors to get new release updates, plus improved recommendations.

John Zeratsky
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
John Zeratsky is the bestselling author of Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days and Make Time: How to Focus on What Matters Every Day.
John’s writing has been published by The Wall Street Journal, TIME, Harvard Business Review, Wired, Fast Company, and many other publications. He has appeared on stage nearly 200 times, including at Netflix, IDEO, McKinsey, the Code Conference, and The London School of Economics.
For nearly 15 years, John was a designer for technology companies. At Google Ventures (GV), he helped develop the design sprint process and worked with close to 200 startups, including Uber, Slack, 23andMe, Flatiron Health, Blue Bottle Coffee, and Nest. He was also GV’s in-house copywriter, editor, and content strategist; he created and edited the GV Library, which has reached millions of readers since 2012. Previously, John was a designer at YouTube and Google, and an early employee at FeedBurner, which Google acquired in 2007.
John studied journalism at the University of Wisconsin and graduated with a Bachelor of Science degree from the UW School of Human Ecology, where he’s now an advisor to the Dean and faculty.
Originally from small-town Wisconsin, John and his wife Michelle have lived in Chicago and San Francisco. They spent 18 months traveling in Central America aboard their sailboat Pineapple before moving to Milwaukee in 2019.
See more on the author's page
Jake Knapp
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
Jake Knapp is the author of "Make Time" and the New York Times bestseller "Sprint".
Jake spent ten years at Google and Google Ventures, where he created the design sprint. He has coached over 150 companies on the process, including teams at Slack, Uber, the New York Times, and LEGO. He lives in San Francisco with his wife and sons.
See more on the author's page
Braden Kowitz
Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.
Braden Kowitz founded the Google Ventures design team in 2009 and pioneered the role of “design partner” at a venture capital firm. He has advised close to two hundred startups on product design, hiring, and team culture. Before joining Google Ventures, Braden led design for several Google products, including Gmail, Google Enterprise, Google Spreadsheets, and Google Trends.
See more on the author's page

Customer reviews

4,578 global ratings

How customer reviews and ratings work

Review this product

Write a customer review

Customers say

Customers find the book practical and easy to follow. They describe it as a nice, quick read that demystifies design thinking. Readers appreciate the fast-paced writing style. However, opinions differ on its effectiveness - some find it effective and clear, while others feel the overall process doesn't work well or only applies to simple problems.

AI-generated from the text of customer reviews

Select to learn more

Ease of use Readability Design thinking Pacing Effectiveness

179 customers mention "Ease of use"170 positive9 negative

Customers find the book practical and insightful. They say it's a great reference for sprint planning and Agile management. The book provides detailed instructions for conducting a design sprint, with excellent case studies to illustrate concepts. While some consider it a basic book about sprints, others appreciate the focus on facilitation and interaction design.

"...For me this reduces the risk of implementing a solution which despite of being desirable by users, is non-implementable due technical feasibility or..." Read more

"...The psychology behind the methods is real, the creativity of the design will engage all who participate, and you will build better products...." Read more

"...Basically the exercise helps you consider alternatives and also serves as an excellent warm up for the main event...." Read more

"...The book presents a readily understandable and very engaging description of the process that follows three or four companies through the process...." Read more

150 customers mention "Readability"150 positive0 negative

Customers find the book easy to read and understand. They appreciate its practical, step-by-step approach for getting better product outcomes faster. Readers mention that it's inspirational, well-written, and an enjoyable, quick read.

"...While it is simple read, the underlying concepts have roots in Human Centered Design, Anthropology, Prototyping, UX, Innovation, App Design,..." Read more

"...This is a sprint." This was a great sentence to finish the book, and it's a great sentence to begin working in a better way...." Read more

"...I found the 'prototype mindset' to be the best idea in the whole book...." Read more

"...Respect for the reader, a real issue in many design books that view the uninitiated as somewhat inferior, not this book. Challenges..." Read more

38 customers mention "Design thinking"38 positive0 negative

Customers find the book a useful guide on design thinking. They appreciate the clear explanations and illustrations, as well as the practical approach to creative problem-solving. The book covers topics like prototyping, UX, innovation, app design, software development, and agile. It offers a good balance of abstract and hands-on ideas in an engaging presentation.

"...in Human Centered Design, Anthropology, Prototyping, UX, Innovation, App Design, Software Development, Agile Management, ….. The book stitches these..." Read more

"...of my background and real-world experience, I recognize how effective the sprint design is, and feel confident in using the process with any client..." Read more

"...I found it quite unconventional, and hence my belief that it will work...." Read more

"...Simple and understandable illustrations and actions..." Read more

19 customers mention "Pacing"16 positive3 negative

Customers find the book fast-paced and easy to read. They say it's a great guide for running sprints.

"This was an enjoyable, quick read and I tested it out on my team...." Read more

"This DIY guide is inspiring, focused and really fast-paced...." Read more

"Such a good book! A fast and easy read. I can't wait to experiment with a weeklong sprint at work. It would really help us test out some ideas." Read more

"Quick to read. Excellent guide for the ones running sprints. Give every day detail. Good examples for beginners. Plug and play." Read more

9 customers mention "Effectiveness"6 positive3 negative

Customers have mixed opinions about the book's effectiveness. Some find it effective and clear, with a successful process that works well. Others say it has useful parts but the overall process doesn't work as a whole, takes longer than a week, and only applies to simple problems.

"We actually had our first Sprint last week and it went very well...." Read more

"...which despite of being desirable by users, is non-implementable due technical feasibility or business sustainability...." Read more

"...my own life/projects and am encouraging others to do the same — this sh*t works!" Read more

"...I read it and used it throughout the process and was able to successfully run one...." Read more

Reviews with images

See all photos

Top reviews from the United States

There was a problem filtering reviews right now. Please try again later.

Sameh Z
Design Thinking Time-boxed
Reviewed in the United States on December 9, 2017
Verified Purchase
Sprint book review

The Sprint book is easy read and could be dealt with as a story. The format of Sprint moving through the working week creates atmosphere that I was hearing Jake(the main author) telling me a story. Watching some videos on YouTube for Jake helped me better understand the book. As they say, our writing is kind of reflection of who we are beyond the subject of the book.

While it is simple read, the underlying concepts have roots in Human Centered Design, Anthropology, Prototyping, UX, Innovation, App Design, Software Development, Agile Management, ….. The book stitches these concepts in a simple 5 days intuitive road-map for any organization that wants to solve big challenge in 5 days. No bluff, no extended plans, not procrastination, no top-down solutions, and no naysayers. By solving a challenge, I mean ‘learning’ what to do about it.

Design Sprint is about learning what we need to do about the challenge. The bigger the challenge the higher the applicability of Design Sprint and the bigger the reward can be.

I am familiar with Human Centered Design from IDEO. For me Design Sprint cuts to the chase if we want to apply the whole Design Thinking process in a week. There could be follow-up after the Sprint to iterate on the feedback from users on Friday, but that followup will be shorter. In days , it is like 5+3+2; 5 days for the first Sprint. And every segment has definitive outcomes that provides concrete learning to the organization.

Having key stakeholders in the Design Sprint team, would help having timely feedback and decisions on the progress of the Sprint. Meaning, those stakeholders will bring us to the reality about the aspects of the business applicability of the solution. For me this reduces the risk of implementing a solution which despite of being desirable by users, is non-implementable due technical feasibility or business sustainability.

The book includes examples of companies from diverse industries including healthcare, software development, hotels, coffee-shops, and fitness. I am more comfortable applying Sprint process to design services that primarily utilize digital solutions. However, the author mentioned he implemented the same process for designing non-digital solutions. Again, this is a Design Thinking mentality where we start from complete uncertainty about what we need to do and go through a discovery process for learning about the context and what probably can work. What probably works is based on user testing of a facade solution (prototype).

Sprint book is complete and can be the main source for anyone who wants to facilitate Design Sprint, like me:) Like any other process, learning can happen only through practicing using the right process. and mindset. Based on the lessons learned from tens of Sprints the author facilitated, I believe this book can be valuable for team facilitators.

It is about time for organizations to be transparent about their challenges and empower their employees to help ‘learning’ about what to do regarding them. Historically, organizations provide top-down solutions without engaging the right people who understand the complexity of the existing situation. Meaningful learning can be done in 5 days using the Sprint process detailed in this book and with the right skill-mix of team members. Design Sprint can be incorporated as habitual process for ‘learning’ about challenges and designing solutions/services using Design Thinking mentality. It is all in one week!

Similar to Design Thinking and Learn Startup which focus on learning, Design Sprint aims to reduce the risk of having wrong a product/ solution. Although customer usage of solutions is the final judge, Design Sprint can reduce the risk of developing the wrong feature in the first place. In Agile language, before adding a feature into the product backlog, we need to ensure first that it was tested earlier with the target audience using tangible prototype rather than words. Design Sprint can enable that!

Read more

7 people found this helpful

Helpful

Report
Ben McMann
A Better Way of Working
Reviewed in the United States on March 15, 2016
Verified Purchase
"It's what work should be about – working together to build something that matters to people. This is the best use of your time. This is a sprint." This was a great sentence to finish the book, and it's a great sentence to begin working in a better way.

In the preface, the author states he had his first child. When he returned to the office, he wanted his time on the job to be as meaningful as his time with his family. He took a hard look at his habits and saw that, "I wasn’t spending my effort on the most important work". He discussed how improving team processes became an obsession for him. Through his experience of working with teams to create new products at Google, and experimenting on improving the way teams work, he found that focusing on individual work, having time to prototype, and an inescapable deadline produced far better results.

Running the 5 day sprint described in the book enables a team to easily find out if they are on the right track before they commit to the risky business of building and launching their products. The sprint process however is just as applicable to teams launching internal products/solutions/services. This way of work is applicable to any company, not just startups.

The author shares how other Google Ventures team members added to the sprint process to make it better through the years. Braden Kowitz added story-centered design – which focuses on the whole customer experience instead of individual components or technologies. John Zeratsky helped to ensure that each sprint starts at the end, so the business's would be able to identify and answer their most important questions. Michael Margolis encouraged them to finish each sprint with a real world test. By putting your prototype in front of real customers/prospects, you didn't have to guess whether your solutions were good, at the end of the sprint you got answers.

Over the last 10 years, I have facilitated interactive workshops to help teams get a shared understanding of the business problem they are trying to solve, which is a precursor to a shared commitment to solve the problem. Having a solid understanding of the research behind collaborative approaches to work, and understanding the approach to use based on the problem domain you are in is critical to a successful outcome. Because of my background and real-world experience, I recognize how effective the sprint design is, and feel confident in using the process with any client I work with. The psychology behind the methods is real, the creativity of the design will engage all who participate, and you will build better products.

If you are passionate about helping teams work more effectively, if you care about making work a more engaging experience, if you have a burning desire to improve customers' lives, read this book and then USE this book to run sprints.

Read more

10 people found this helpful

Helpful

Report

Top reviews from other countries

Translate all reviews to English

Cliente Amazon
Pratico e versatile
Reviewed in Italy on October 19, 2024
Verified Purchase
Metodo concreto e facilmente applicabile e versatile per diverse sfide e opportunità aziendali

Read more
Report
Translate review to English
Kushal Arya
A must read book for engineers.
Reviewed in India on July 16, 2024
Verified Purchase
Someone stole my book, so i got hardcover version to keep in my collection. A must read book for engineers. Amazing print quality. Book was delivered in proper packaging.

Read more
Report
Gavin Deadman
Practical guide on everything you need to know to get going with using the Design Sprint process
Reviewed in the United Kingdom on April 10, 2023
Verified Purchase
Since the book publication in 2016, the Design Sprint process has become a familiar approach to efficiently solving big business problems/validating hypothesis that involve high amounts of complexity/uncertainty/risk, and Jake gives the background as to how Design Sprints originated along with an in-depth account of how they went through the process to test some ideas at Google Ventures.

Covering a variety of different experiments which they ran/problems they addressed made it a good read, including Slack (finding the best way to explain Slack to non-tech customers), Savioke Hotels (how hotel guests would react to a robot with personality, by experimenting through a robot delivering a toothbrush to a guests room), Flatiron Health (dealing with the complexities of getting cancer patients into clinical trials), and Blue Bottle Coffee (getting their value proposition clear on a new digital experience).

The book is practical, so if you’re new to Design Sprints, you’ll find it easy to create a plan which you can apply across your product as well as understand the key ingredients needed, so whilst tools have evolved to make it easier more than ever to validate a hypothesis in a remote world for digital products using the likes of Figma, Miro, UserTesting… the fundamentals haven’t changed in that you need to:

1. Collaborate with people throughout the sprint
2. Have a decision maker (normally Product Manager)
3. Identify a high priority problem to solve
4. Ideate and create prototype/s
5. Get feedback from potential customers

“When you get into a regular rhythm of listening to customers, it can remind you why you’re working so hard in the first place.”

Read more

Gavin Deadman

Practical guide on everything you need to know to get going with using the Design Sprint process
Reviewed in the United Kingdom on April 10, 2023
Since the book publication in 2016, the Design Sprint process has become a familiar approach to efficiently solving big business problems/validating hypothesis that involve high amounts of complexity/uncertainty/risk, and Jake gives the background as to how Design Sprints originated along with an in-depth account of how they went through the process to test some ideas at Google Ventures.

Covering a variety of different experiments which they ran/problems they addressed made it a good read, including Slack (finding the best way to explain Slack to non-tech customers), Savioke Hotels (how hotel guests would react to a robot with personality, by experimenting through a robot delivering a toothbrush to a guests room), Flatiron Health (dealing with the complexities of getting cancer patients into clinical trials), and Blue Bottle Coffee (getting their value proposition clear on a new digital experience).

The book is practical, so if you’re new to Design Sprints, you’ll find it easy to create a plan which you can apply across your product as well as understand the key ingredients needed, so whilst tools have evolved to make it easier more than ever to validate a hypothesis in a remote world for digital products using the likes of Figma, Miro, UserTesting… the fundamentals haven’t changed in that you need to:

1. Collaborate with people throughout the sprint
2. Have a decision maker (normally Product Manager)
3. Identify a high priority problem to solve
4. Ideate and create prototype/s
5. Get feedback from potential customers

“When you get into a regular rhythm of listening to customers, it can remind you why you’re working so hard in the first place.”

Images in this review

Report
Erik Lindholm
Bra bok
Reviewed in Sweden on June 17, 2022
Verified Purchase
Bra, praktisk metodik som vi kommer att implementera på mitt företag.

Read more
Report
Translate review to English
Osmar Ramirez
Increíble metodología
Reviewed in Mexico on May 18, 2019
Verified Purchase
Este libro es ideal si tienes cualquier negocio que necesite probar cierta funcionalidad en su flujo operativo. La lectura es muy amena

Read more
Report
Translate review to English

See more reviews

Amazon Prime Free Trial

Return this item for free

Return this item for free

Image Unavailable

Follow the authors