Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days (English Edition) Kindle-editie

Jake, John, and Braden have synthesized the most important design-thinking concepts of today into a book that is worth its weight in gold. Seriously — I’ve translated the ideas and checklists in this book to tens of thousands of dollars already as a design consultant.

It’s weird... even after 4 years of studying Art & Design in college and 4 years of working at a big tech company, this book was STILL a revelation to me. It helped me understand and practice design in a whole new way. I was lucky to be mentored by top-tier designers. Now you can be mentored by some of the best designers in the Silicon Valley. Listen in on how they work and think...

90% of what you need to know about designing great products is in these 257 glorious pages. The other 10% is just blood, sweat and tears.

What Jake and his co-authors prescribe in the book sounds rather too good to be true and unconventional, but it has made a world of sense to me.

What usually takes months and months of hopeless meetings, emails and expenditure has been narrowed down to just 5 days of intensive work by all the KEY parties. Emphasis has been put on 'key' parties as most often businesses approach to answer their biggest questions with just 2 or 3 people from the top management involved.

I like how they advise startups to focus on most pressing questions. I can see how many founders and deciders can get lost in a web of questions during startup. They recommend an ideal size of the sprint to be seven people or less, I couldn't have agreed more. And this is only one of the many ingenious tips I liked. Another one is the 'no device rule'.

I've always been a fan of whiteboards but these guys have taken the idea to another level. I quote: " the simultaneous visibility of project material helps us identify patterns and encourages creative synthesis to occur more readily than when these resources are hidden away in file folders, notebooks, or PowerPoint decks."

Another key insight I got from the book is the reminder that 'nobody knows everything'. I can imagine many CEOs thinking this way due to hubris. I quote: "..the information is distributed asymmetrically across the team and across the company. In the sprint, you've got to gather it and make sense of it, and asking experts is the best and fastest way to do that."

The 'How might we' method was also a great light-bulb. Rephrasing business obstacles into helpful questions. Another helpful method is the 'lightning demos which involves finding inspirational ideas from both within your company and even outside your industry. I could imagine limiting myself to my competitors only, but stretching as far as other businesses who do nothing remotely similar is a revelation.

Another ingenious solution suggested by the authors is the 'mind reader' - a sketch of complex ideas as a simple drawing of boxes and text. This then forms a basis for a prototype.They emphasize on the quality of the solution as opposed to the artistry of the drawings - they really do give hope to people like us who wouldn't know what do with a brush :) They further elaborate on the usefulness of sketching, I quote, "once your ideas become concrete, they can be critically and fairly evaluated by the rest of the team - without any sales pitch. And perhaps, most important of all, sketching allows every person to develop those concrete ideas while working alone."

Crazy 8s is another brilliant idea introduced by the team. An 8 minute exercise of sketching 8 variations of your strongest ideas. I found it quite unconventional, and hence my belief that it will work. Basically the exercise helps you consider alternatives and also serves as an excellent warm up for the main event.

I found the 'prototype mindset' to be the best idea in the whole book. The authors suggest building a facade and testing it, this initially sounded uncomfortable to me, but I later saw the genius in it. I quote, "To prototype your solution, you'll need a temporary change of philosophy: from perfect to just enough, from long-term quality to temporary simulation." I can see how this idea can save a huge amount of time and money for a company down the line.

In the end the authors emphasize the best part about the sprint, which is the chance to learn whether you are on the right track with your ideas in just 5 days. "You can have efficient failures that are good news, flawed successes that need more work, and many other outcomes." I couldn't agree more.

The choice of examples used in the book was also great, not exactly Malcolm Gladwell level, but still inspiring nonetheless.

I recommend the book to Startup founders, top company management or any one looking for unconventional methods to improve productivity on any sphere of their lives.

"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.

The book content is great and the process methods and practice are well defined for any UX professional to pick up and be effective with out of the box. Four stars because the Kindle version is dreadful, don't buy it terrible image formatting of tiny indistinguishable blobs. The Kindle typography is also borderline. Buy paper you will thank me.

A fantastic cookbook for getting better product outcomes faster.
I'm going to use the Sprint checklists every time I run a workshop from now on.

This book is notable for the things it leaves out of the design process.

An example is brainstorming. At one point in history, every collaborative design activity had to involve brainstorming Jake and team actually discourage spending time brainstorming in Sprint. After some reflection, I'm starting to see the wisdom of leaving it out.
This doesn't mean they discourage creative or divergent thinking, only that classic brainstorming as a group can create unwanted digressions.

Another Design collaboration staple Jake leaves on the cutting room floor is creating exhaustive documentation and analysis of every step in the Design Sprint process. He promotes focusing the documentation work on the product prototypes, and user feedback which is very wise advice.