Product Management

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:

• Collaborate with people throughout the sprint
• Have a decision maker (normally Product Manager)
• Identify a high priority problem to solve
• Ideate and create prototype/s
• 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.”