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.
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.
If you are not familiar with design management techniques, design thinking, design research, or anything about user experience this is the book for you. A lot of it does depend on the decider, and oftentimes in the real world this is not possible because of the amount of time required.
This book is much better than expected! It's practical, with plenty worksheets (on the Sprint book website) and contains clear, helpful directions based on Jake's experience working with this.
The sprints are like a mix of scrum and design thinking. Leaning more towards the latter.
Some have remarked the book is full of Google-talk. I didn't feel that way at all. They mention Google a few times, but it's never obnoxious or distracting at any level.
Practical lean startup method that any startup can execute in a week. I recommend buying both the audible and paperback book, because it will become your essential reference guide for getting traction with your ideas.
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.
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.
The concept behind the book is solid. I can see how it could save companies time by investing five days up front. The narration was easy to listen to and kept me interested.
Report Inappropriate Content