Making OKR accessible to help every business to cut the noise and focus on growth.


OKR Quickstart

Design Sprints = discovery done in 5 days 🥳

Well that’s what I used to think.

In the early 2000s I came across Design Thinking and over the next 10 years I went really deep on the concepts. Super useful for industrial product design.

Not so useful for Software Product Design as it tends to push you towards a final solution.

But… the Design Thinking concepts and practices are super useful. Which is where Jake Knapp published the Google Ventrures Design Sprint. It brought in a lot of the concepts and applied it specifically to product teams building software.

I thought this was the ultimate solution. In fact, this is still is my go to when introducing discovery to a team.

The problem is, discovery doesn’t stop until the product is dead.

This is where *Continuous Discovery* comes in.

Rather than a once off activity, the product trio (Tech Lead, Product Manager and Designer) meet with customers weekly to better understand the problem space and test solution ideas.


Here’s where I need your help! I’m creating a video on Continuous Product Discovery

To make sure I cover everything in the video, can you share:
1. What’s the most misunderstood idea in continuous discovery?
2. What are some tips you have?
3. Where does it work best?

3 months ago (edited) | [YT] | 1