Skip to main content
Test Double company logo
Services
Services Overview
Holistic software investment consulting
Software Delivery
Accelerate quality software development
Product Management
Launch modern product orgs
Legacy Modernization
Renovate legacy software systems
DevOps
Scale infrastructure smoothly
Upgrade Rails
Update Rails versions seamlessly
Technical Recruitment
Build tech & product teams
Technical Assessments
Uncover root causes & improvements
Case Studies
Solutions
Accelerate Quality Software
Software Delivery, DevOps, & Product Delivery
Maximize Software Investments
Product Performance, Product Scaling, & Technical Assessments
Future-Proof Innovative Software
Legacy Modernization, Product Transformation, Upgrade Rails, Technical Recruitment
About
About
What's a test double?
Approach
Meeting you where you are
Founder's Story
The origin of our mission
Culture
Culture & Careers
Double Agents decoded
Great Causes
Great code for great causes
EDI
Equity, diversity & inclusion
Insights
All Insights
Hot takes and tips for all things software
Leadership
Bold opinions and insights for tech leaders
Developer
Essential coding tutorials and tools
Product Manager
Practical advice for real-world challenges
Say Hello
Test Double logo
Menu
Services
BackGrid of dots icon
Services Overview
Holistic software investment consulting
Software Delivery
Accelerate quality software development
Product Management
Launch modern product orgs
Legacy Modernization
Renovate legacy software systems
Cycle icon
DevOps
Scale infrastructure smoothly
Upgrade Rails
Update Rails versions seamlessly
Technical Recruitment
Build tech & product teams
Technical Assessments
Uncover root causes & improvements
Case Studies
Solutions
Solutions
Accelerate Quality Software
Software Delivery, DevOps, & Product Delivery
Maximize Software Investments
Product Performance, Product Scaling, & Technical Assessments
Future-Proof Innovative Software
Legacy Modernization, Product Transformation, Upgrade Rails, Technical Recruitment
About
About
About
What's a test double?
Approach
Meeting you where you are
Founder's Story
The origin of our mission
Culture
Culture
Culture & Careers
Double Agents decoded
Great Causes
Great code for great causes
EDI
Equity, diversity & inclusion
Insights
Insights
All Insights
Hot takes and tips for all things software
Leadership
Bold opinions and insights for tech leaders
Developer
Essential coding tutorials and tools
Product Manager
Practical advice for real-world challenges
Say hello
Leadership
Leadership
Leadership
Product management

Don't play it safe: Improve your continuous discovery process to reduce risk

We often front-load discovery to feel confident before building—but that’s not real agility. This post explores how continuous learning reduces risk better than perfect plans ever could.
Doc Norton
|
June 16, 2025
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Big changes are big risk. But often the more we try to eliminate risk, the more risk we create.

Most teams agree that learning is key to reducing risk. But not all learning happens during implementation. And not all approaches to product discovery are as iterative as we like to think.

In many orgs that have some form of product discovery in place, there’s a tendency to treat product discovery, inception, and design work as a way to front-load certainty and perceived safety. Research gets packaged into polished prototypes. User flows are vetted, click-through demos reviewed, copy finalized. Boxes have been checked, sign offs are obtained, success feels inevitable. By the time development begins, there’s a sense that the hard part—the learning—is done.

From there, teams move into delivery mode. They build incrementally, they iterate on implementation, they follow agile rhythms. But the product thinking has already solidified. What gets built may be sliced small, but the underlying decisions are no longer being questioned.

It creates the comfort of “knowing” while giving the appearance of agility.

But it’s not agility. It’s choreography.

And when things shift—as they inevitably do—it becomes clear how little room we left ourselves to adapt.

Certainty feels safe—learning is safer

When we invest heavily in up-front discovery, it can feel like we’ve reduced risk. We’ve anticipated edge cases, validated with users, aligned on a vision. But that confidence is only real if we keep validating as we go.

No matter how thorough your discovery process is, the most reliable learning still happens where software meets customer. Early. Often. In context.

The further discovery is from that point of contact, the more assumptions sneak in. The tighter the prototype, the harder it is to change course. And the longer we go without user feedback on the live experience, the more fragile our work becomes—no matter how good it looked in design reviews.

Treat discovery like delivery

The healthiest product teams don’t just iterate on implementation. They iterate on understanding.

They approach product discovery the same way they approach development: in small, testable steps. They release early prototypes not just to stakeholders, but to real users. They fold learning from production back into their product thinking. They augment initial discovery learnings with live product analytics, customer feedback, and satisfaction surveys (to name a few) as input to adjust and improve on what they've delivered. And they keep discovery going through delivery—not just before it.

This is what continuous discovery looks like. Not a separate phase, but an ongoing practice.

Instead of trying to eliminate risk through “getting it right,” they reduce risk by learning faster and adjusting sooner.

Make the learning loop short

The teams that adapt best are the ones with the shortest feedback loops. They don’t pretend to be certain—they design their work so they don’t have to be.

They test assumptions quickly. They validate throughout the development and delivery cycle, not just after launch. They expect their early thinking to evolve. And because they’ve built that expectation into how they work, change doesn’t feel like failure—it feels like progress.

What’s next

If your product process feels stuck—if discovery happens all at once and delivery happens in isolation—it’s worth asking: when was the last time we changed our minds?

Not because we were wrong. But because we learned something new.

Interested in building a more adaptive product practice?

At Test Double, we help teams shorten their learning loops—not just their delivery timelines. Whether you're looking to ship sooner, validate more often, or untangle ambiguity in your product process, we can help. Let’s talk.

‍

Doc Norton is Vice President of Delivery at Test Double and has extensive experience in building great software and great teams, including focuses within his career in software development, software architecture, product management, technology leadership, agile coaching, organizational agility, and systems thinking.

‍

This blog post was originally published on docondev.com.

Related Insights

🔗
Audentes Fortuna Iuvat: being bold amidst uncertainty
🔗
Good teams ship great products. Great teams kill bad ones.
🔗
The art of product restraint: Why less delivers more
🔗
You’re holding it wrong! The double loop model for agentic coding

Explore our insights

See all insights
Developers
Developers
Developers
C# and .NET tools and libraries for the modern developer

C# has a reputation for being used in legacy projects and is not often talked about related to startups or other new business ventures. This article aims to break a few of the myths about .NET and C# and discuss how it has evolved to be a great fit for almost any kind of software.

by
Patrick Coakley
Leadership
Leadership
Leadership
Turning observability into a team strength without a big overhaul

By addressing observability pain points one at a time, we built systems and practices that support rapid troubleshooting and collaboration.

by
Gabriel Côté-Carrier
Developers
Developers
Developers
Why I actually enjoy PR reviews (and you should, too)

PR reviews don't have to be painful. Discover practical, evidence-based approaches that turn code reviews into team-building opportunities while maintaining quality and reducing development friction.

by
Robert Komaromi
Letter art spelling out NEAT

Join the conversation

Technology is a means to an end: answers to very human questions. That’s why we created a community for developers and product managers.

Explore the community
Test Double Executive Leadership Team

Learn about our team

Like what we have to say about building great software and great teams?

Get to know us
Test Double company logo
Improving the way the world builds software.
What we do
Services OverviewSoftware DeliveryProduct ManagementLegacy ModernizationDevOpsUpgrade RailsTechnical RecruitmentTechnical Assessments
Who WE ARE
About UsCulture & CareersGreat CausesEDIOur TeamContact UsNews & AwardsN.E.A.T.
Resources
Case StudiesAll InsightsLeadership InsightsDeveloper InsightsProduct InsightsPairing & Office Hours
NEWSLETTER
Sign up hear about our latest innovations.
Your email has been added!
Oops! Something went wrong while submitting the form.
Standard Ruby badge
614.349.4279hello@testdouble.com
Privacy Policy
© 2020 Test Double. All Rights Reserved.