Doing Discovery Well: How to Measure and Guide Your Team

Teresa Torres argues that discovery teams should be judged by whether their discovery work actually moves a desired product outcome, tracked as absolute progress quarter over quarter rather than percent of a goal. Since outcomes are lagging indicators, she proposes leading indicators that track the behaviors of a strong continuous discovery team. These include cycle time between customer contact, prototyping and assumption tests, rather than raw counts that always rise. She also suggests measuring how often ideas are thrown out, since that signals real learning and a compare-and-contrast mindset. Finally, she recommends using team retrospectives with two questions to catch discovery blind spots and shift learning earlier. The approach matters because it gives teams a practical way to evaluate and improve discovery without relying on vanity metrics.

01Key takeaways

• Measure discovery success by absolute progress on a desired outcome, tracked quarter over quarter over several quarters.
• Avoid counting activities, since counts always rise; measure the maximum days between customer interviews and assumption tests instead.
• Aim for a steady customer conversation cadence, such as at least weekly, and shrink the gaps over time.
• Track days since your last discarded idea to reward learning what not to build and to encourage weighing more options.
• Ask in retrospectives what surprised you and how you could have learned it sooner, to catch discovery blind spots.
• Expect noisy outcome charts; focus on whether the trend rises over the long run rather than on individual quarters.

02Key sections

Discovery is judged by outcomes

A high-performing discovery team should hit its product outcomes at a higher rate over time. Progress should be charted as absolute change, not as a percentage of an ambitious goal.

Avoid vanity metrics

Counts of interviews or experiments always go up and reveal little about quality. Measuring cycle time between activities better reflects cadence and continuous discovery.

Measure idea rejection

Tracking the number of days since an idea was thrown out rewards learning that a solution should not be built. It also encourages considering more options before deciding.

Retrospectives drive improvement

Two retrospective questions help teams spot what surprised them and how they could have learned it sooner. This shifts learning from delivery into discovery.

A simple evaluation framework

Combine cycle time for interviews, prototypes and assumption tests, idea rejection tracking, and retrospectives, while watching outcome trends over several quarters.

03From the post

“How do you know that you are doing discovery well? If you want to improve your discovery process, what outcomes help you track your progress? I get asked these questions often. I like that teams are trying to take an outcome-focused mindset to their discovery practice. The good news”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.