From three design partners at Google Ventures, a unique five-day process for going from problem to prototype.
The companies that Google Ventures invest in face big questions every day: Where's the most important place to focus your effort, and how do you start? What will your ideas look like in real life? How many meetings and discussions does it take before you can be sure you have the right solution to a problem? Business owners and investors want their companies and the people who lead them to be equipped to answer these questions - and quickly. And now there's a surefire way to solve their problems and test solutions: the sprint.
While working at Google, designer Jake Knapp created a unique problem-solving method that he coined a "design sprint" - a five-day process to help companies answer crucial questions. His "sprints" were used in the development of everything from Gmail to Google X to Chrome. When he moved to Google Ventures, he joined Braden Kowitz and John Zeratsky, both designers and partners there who have worked on numerous products, including the YouTube redesign. Together Knapp, Zeratsky, and Kowitz have run over 100 sprints with their portfolio companies, inside Google, and in others companies or environments that have sought their help. They've seen firsthand how sprints can overcome challenges in all kinds of companies: health care, fitness, finance, retailers, and more.
A practical guide to answering business questions, Sprint is a book for groups of any size, from small start-ups to Fortune 100s, from teachers and PTAs to nonprofits and public institutions. It's for anyone with a big opportunity, problem, or idea who needs to get answers today.
©2016 Jake Knapp (P)2016 Simon & Schuster, Inc.
As superlative as the title sounds, this book does show you how to solve big problems and test new ideas in five days. It explains who needs to be on the team and provides details on what to do on each of the five days. Through the author's own testing and observations, he found the ideal method to be this 5-day sprint. The Sprint Book website even lists software applications, supplies, and tools that are useful a sprint. It is apparent that the author carefully thought through the optimal structure and timeline for a sprint.
This book like many doesn't have all that much to say but is required to say enough to fill all the chapters. Good work guys. You filled them with examples and reiterated your methodologies over and over. Thanks.
Kidding aside, I personally didn't benefit from this book and maybe disagree with the process philosophically. It is written well and the information might be helpful to people unfamiliar with their users or who just want to follow a five step process to business success.
I've worked with teams before that have probably followed this by the book and it all felt and like a schoolbook team that liked to play dress up. I'm sure you will be successful using this and or pieces of this process, it just feels less personal and more academic.
If your not already familiar with old concepts like, The Lean Startup, Agile Product, Development and User Testing, then this is going to be a great book for you.
But for many of us this book will provide No new information. It's a standard week long sprint ending in some user testing of your prototype, the same stuff that's been preached from the mountain tops for the last 5 years. The authors provide a lot of detail around how to run the sprints, which is nice, but for the most part I was anxious to wrap this book up and move on to something new.
To be clear, if you are Not super familiar with the concepts I mentioned above, then I would Highly recommend this book. The content is absolutely true and this book is a good, albeit basic, summary of the principles needed for rapid, low-cost product development.
They tend to repeat themselves alot, which lost my attention, but there was a lot of good information.
This was a great reading of the Sprint book and well worth your time if you are involved in building software or running your own startup.
There are example stories which are interesting and relevant. There is repetition for the important points. There are step by step instructions on how to do this yourself. What more could you want? Quick, informative, useful. Take bits and pieces of the whole thing. Great.
Henrik de Gyor
If you have an open mind and you are willing to change the ways you solve big problems, I would highly recommend reading this then trying it out in the real world with other willing parties for the various roles you will need. No committees involved.
Good narration, but some visuals where still required to get the full context of the Sprint process. No fault of Dan though.
No extreme reactions, but the book encouraged me to try out Sprints with 4 different startups at the same time. And it worked very well.
Read it, then Sprint through a big problem/challenge.
Wished have read this before started my company, would safes a lot of time and energy
It is always great listening to something that is practical effective and based on solid repeat experience
I look forward to experimenting with this myself
Report Inappropriate Content
If you find this review inappropriate and think it should be removed from our site, let us know. This report will be reviewed by Audible and we will take appropriate action.