Release
In product discovery, a release is the act of deploying a product change to users—typically done after validating assumptions through testing and learning.
How does release serve as a decision point?
A release represents a decision point that follows discovery and delivery. The decision to release should be based on whether assumption testing shows the change will have the desired impact.
When a solution is vetted through assumption testing, releasing the change is the natural next step. But if any assumptions fail or show little impact, teams need to decide whether to iterate, pivot, or abandon the idea.
How does release relate to MVP?
An MVP (Minimum Viable Product) is defined as the smallest or easiest product you can release to learn what you need to learn—not just the minimum feature set.
This means:
- Not: The smallest product you can get out the door
- Instead: The smallest product that will test your critical assumptions and generate the learning you need
The emphasis is on learning rather than shipping for its own sake.
What should teams consider before releasing a feature?
Before releasing a feature or change, teams should consider:
- Impact: Does the tested change show enough impact to justify the ongoing costs?
- Implementation costs: What will it take to build and deploy this?
- Maintenance: What's the long-term cost of maintaining this change?
- Customer learning curve: How much effort will customers need to invest?
- Opportunity costs: What else could we build with these resources?
How should teams view releases in continuous discovery?
In continuous discovery, releases aren't end goals—they're opportunities to continue learning and validating. Teams should frame releases as learning vehicles that help them understand whether their changes create the intended value for users.
Learn more:
- Practice Defining Your MVP
Related terms:
- Assumption Testing
- Research
- Risky Assumption
Last Updated: October 25, 2025