Product in Practice: Adopting the Discovery Habits is An Iterative Process

Teresa Torres profiles Kelsey Terry, former Director of Product at Going, who led a pilot product trio tasked with testing the ideas in Continuous Discovery Habits and spreading them across the company. The story shows that adoption was messy: a tight deadline produced a quick win, an open-ended timeline bred perfectionism and slow progress, and an over-engineered process failed to win executive buy-in. Kelsey eventually fixed the problem by treating the rollout itself as a discovery problem, interviewing stakeholders and building a regular weekly cadence with visible artifacts. The piece matters because it reframes discovery adoption as iterative organizational change, not a one-time framework rollout.

01Key takeaways

• Introduce discovery concepts by describing what they help you do, rather than leading with a branded framework label.
• Use short timeboxes and deadlines as circuit breakers to counter perfectionism and keep discovery moving.
• Treat your rollout of a discovery practice as its own discovery problem by interviewing the people it affects.
• Create a regular weekly cadence and business-friendly artifacts so executives can follow progress without learning visual tools.
• Adapt the principles of a framework to your organization rather than following every step in a fixed order.
• Remember that not shipping value to customers is a real business risk, not just a process cost.

02Key sections

Tight deadline as a first attempt

A 20-business-day deadline to reduce churn on an Elite subscription forced the trio to focus, using assumption mapping, lo-fi mockups, and design spot checks. They shipped on time and established a baseline.

Perfectionism in the second attempt

With no time limit, the team re-read the book meticulously and debated endlessly, aiming to get everything right as the pilot. Customer interviews and prototype testing eventually surfaced a risk, but the process took about two and a half months.

Timeboxing and an over-ambitious onboarding cut

After a retro, the team timeboxed work into 20-day cycles and tried to reduce onboarding to three steps. Executives judged the bold solution too risky, which frustrated the team and exposed a misalignment.

Applying discovery to the rollout itself

Kelsey interviewed executives and colleagues, finding that the process felt slow, exclusive, and unclear. She responded with a weekly meeting cadence and insight-oriented artifacts that made the work accessible to stakeholders.

Lessons for other teams

Kelsey advises introducing concepts rather than branding them, giving teams grace, adapting the framework to the business, and recognizing that failing to ship is itself a risk.

03From the post

“Continuous discovery is not a linear journey—as much as we might want it to be. Like a lot of learning, it often feels messy and chaotic. But if you stick with it, you may eventually find you can look back and see how much you’ve progressed. That’s”

04Frameworks mentioned

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