Launch · Product Adoption · Product Management · PTOS

Launch is Not a Release: How to Guide a Feature to Actual User Adoption

Understanding the Launch phase in product development—it's not just deploying code, but a comprehensive operation to ensure actual use and change in user behavior.

Launch is Not a Release: How to Guide a Feature to Actual Use

In product teams, two concepts are often confused: 'release' and 'launch.' A release is a technical event: the code is deployed to production. A Launch is a comprehensive operation whose goal is to deliver new value to the user and achieve its actual use.

If you just 'released' a feature and moved on to the next task, you most likely wasted your time.

The Main Question of a Launch

Did we just build a feature, or did the right people really start doing the right action?

The Fundamental Principle

A Launch is complete not at the moment of deployment, but when there is adoption in the user's behavior, not just 'we announced it in the blog.'

Why 'Released' ≠ 'Used'?

There is a chasm between a feature appearing in the product and the user getting value from it. Along this path, the user can 'fall off' for many reasons:

1. Didn't notice: They simply didn't see the new feature.
2. Didn't understand why they need it: The value was not communicated in their context.
3. Doesn't trust or fears the risk: 'What if I break everything?'.
4. Can't complete the path to the first victory: The interface is too complex or confusing.
5. Got value once, but didn't form a habit: There was no incentive for repeated use.

Launch is the bridge across this chasm. It's about working on each of these points so the user doesn't 'drop off' halfway.

What is a Launch in PTOS?

In the PTOS methodology, a Launch is an operation to drive behavior, which consists of five key components:

1. Segments: Who do we show the feature to first, and who should absolutely not see it (e.g., VIP clients for whom stability is crucial). Launching 'to everyone' is almost always a bad idea because you lose the opportunity for diagnosis.
2. Adoption Definition: What do we consider 'successful use'? It's not a click or a view. It's a value-event—a specific, measurable action that means the user has received value. For example, 'successfully created and sent a report'.
3. Rollout plan: How will we roll out the change? Usually, it's a phased process (10% → 50% → 100%) that allows you to test your hypotheses and manage risks at each stage. At 10%, we check if users can complete the path at all. At 50%, we check if our support and infrastructure can handle the load. And only then, 100%.
4. Enablement: How will we help the user get to the 'moment of value'? This could be an in-app tooltip in the right place, an email-campaign, or personal assistance from Customer Success.
5. Internal readiness: Are our teams (support, sales, marketing) ready for the questions that will inevitably arise? Do they have answers? Is the documentation updated?

Conclusion

Stop thinking of a launch as the final point. A Launch is the beginning of the most important stage: turning code into real value for the user.

• A release is an event in the life of the team.
• Adoption is a change of habit in the life of the user.

A product 'exists' only where behavior has changed. And the task of a Launch is to ensure this change.