- Paperback: 272 pages
- Publisher: O'Reilly Media; 1 edition (October 18, 2015)
- Language: English
- ISBN-10: 1491923172
- ISBN-13: 978-1491923177
- Product Dimensions: 9.2 x 0.8 x 9.2 inches
- Shipping Weight: 1.4 pounds (View shipping rates and policies)
- Average Customer Review: 21 customer reviews
- Amazon Best Sellers Rank: #77,748 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Design Sprint: A Practical Guidebook for Building Great Digital Products 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
Customers who viewed this item also viewed
From the Publisher
This book is for you
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.
If any of these descriptions sound familiar, then this book was intended for you.
About the Author
The CEO and Co-Founder of Boston-Based User Experience Agency Fresh Tilled Soil, Richard wears the strategic hat around the office. He's worked his way up the web marketing food chain, starting with online ad sales at MultiChoice, Africa’s largest TV and Internet media business. Richard was in the thick of it during the heady dot-com years, founding Acceleration, an international e-marketing business headquartered in London. He has never met a whiteboard he didn't like.
In a world of hyper-specialization, C. Todd stands in the intersections and sees the connections that revolve around us. As an Innovation Architect at Constant Contact's InnoLoft, he facilitates product and service design sprints for a wide range of external startups and internal product teams. C. Todd is also a member of the adjunct faculty at Madrid's prestigious IE Business School where he teaches courses on Creativity, Innovation, Design-Thinking and Communication.
After a career in user experience design and research at companies like Microsoft and Nuance, Trace then became a developer at Pivotal Labs, and is now a Managing Director at thoughtbot. He has facilitated numerous product design sprints, and is an author and maintainer of thoughtbot's design sprint methodology repository. He's brought Lean and Agile methodology to many large companies and small startups, helping teams to focus, prioritize, and become happy and productive.
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
It details the design sprint, what it is, how it is done, and what it's advantages are. Within that context, there's lots of helpful processes explained, like mind mapping and green dot voting. There's lots of techniques and tips to help keep a task team focused and engaged, and to keep the thought process moving at a fast pace, while keeping the possibilities of dangerous groupthink down.
Supply lists are included which I found to be very helpful. It's a book that teams can use, even if they don't adopt the entire process. For instance, if the team wants to try a new adoption of the techniques and decides to focus on just a few activities, they can use the book's clear instructions in 1.,2.,3. format along with supply lists, and tips to help prep in advance.
Why I'm deducting a star from a very useful book:
I do think that resistant team members might focus on some of the 'simple wisdom' in the book as an excuse to disregard it. For instance, is it worth two pages in the book to instruct on the proper method for tearing post-it notes off? For a book about design, that's supposed to foster amazing creativity, there's some really ROTE stock 'looking' photographs of 'people meeting' used. I think the graphics and photography in this book looked overall boring but nice, but almost all of it could have contributed so much more to the goals and utility of the book than it did.
The book also gives just a few ideas for finding a user test group. I think that section could have been better developed.
The book contains several chapters that do tout, what a design sprint but these are minimal.
Also the book has a lot of pictures of design sprints in action, the post-it notes, huddling around tables and such. They are all appropriately placed so you get a sense of what is going on in each section. The book is also well designed and the overall design of the book is well considered, with the pictures interspersing the text and graphical representations of the concepts as well.
What I like about this book was, the prose filled in the story and at the end of each chapter was a takeaway for that chapter. Sometimes it is nice to page back and review a concept.
I also like the primer on how to peel post-its so they don’t curl… There are a lot of practical and alternative methods noted within.
It is hard to say how effective this book is until it is put in practice. I know I will be referring to it for some direction as we are trying to use this method of design in our organization. Unfortunately with any new “method”, you get out of it, what you put into it. If you don’t do the checks and balances, you end up with “same old, same old”. But if you do follow the practice you have a real chance of effective change.
Key, to me is the definition of what problem you are trying to solve for the user and then the resultant testing, to see if you have created something that addresses your fundamental design question, or at least provided a feature people want. Without that it is change for change’s sake. This book seems to be leading you to do the right things at the right time, if followed.
****Why care about design sprints
****The objectives of this book
****Who this book is for: The product professional
****We wrote this book using a design sprint
****How this book is organized
THE WHAT, WHY, WHEN AND HOW OF DESIGN SPRINTS
****Chapter 1: What is a design sprint
****Chapter 2: When (and when not to) do a design sprint
****Chapter 3: How to approach design sprints
****Chapter 4: Before the design sprints, make a plan
****Chapter 5: Phase 1: Understand
****Chapter 6: Phase 2: Diverge
****Chapter 7: Phase 3: Converge
****Chapter 8: Phase 4: Prototype
****Chapter 9: Phase 5: Test
****Chapter 10: After the design sprint: Capture, Iterate and Continue
This book gives you the framework for implementing this sprint in your team and company (i.e. managing the process) which is basically 1. analyze the problem 2. implement 3. test 4. analyze the delivered solution
This book isn't going to teach you basic design principles. There are other books for that.