Launch is the beginning of an adoption story

Release completion alone does not tell us whether the intended problem is being solved.

I bring product, sales and customer success into a shared review of adoption signals. That helps distinguish a product issue from a proposition or implementation issue, and gives the team a more useful basis for deciding what comes next.

Organisations treat launch as the finish line because that is how most product work is planned and funded. Project budgets end at release, teams move on to the next initiative and the celebration marks delivery rather than value. Customers, meanwhile, are only beginning to discover whether the product fits their work. The early period after launch, when habits are formed and first impressions settle, often receives the least attention from the people who understand the product best and could respond most quickly to what customers find.

My practice is to define, before launch, the small set of adoption signals that would tell us the product is solving the intended problem. These usually include whether customers complete the first meaningful task, whether they return, and whether usage spreads beyond the first enthusiastic users. We agree a review rhythm with sales and customer success for the period after launch and keep part of the product team's capacity reserved for what that review reveals. Without reserved capacity, the review produces findings nobody has time to act upon.

Consider a new feature that is used enthusiastically in some customer accounts and barely at all in others. The product team might assume a design problem and begin reworking the interface. A shared review could show something different: where the feature is popular, customer success ran a short onboarding session; where it is neglected, customers were never told it existed. The issue is implementation rather than product. Adjusting the onboarding approach would cost far less than redesign, and it would leave the team free to address genuine product gaps.

A common failure mode is to read adoption data in isolation and draw confident conclusions too early. Low usage in the first weeks may reflect a customer's internal approval process or a seasonal pattern rather than a weak product. I ask the team to pair quantitative signals with conversations, and to state what we expect to see at each stage before judging whether the product is on track. That guards against abandoning a sound product too soon, or persisting with a weak one because early enthusiasm looked promising.

This asks the leadership team to fund products beyond their release and to treat adoption as a shared responsibility across product, sales and customer success. It asks sales to report honestly when customers are not using what they bought, and product to listen without defensiveness. The board benefits from asking how recent launches are performing against the adoption signals agreed in advance. That question, asked consistently, changes how the organisation thinks about what it means to finish a piece of product work.

Treating launch as the beginning also changes how teams are rewarded. Recognition follows adoption and value rather than delivery dates alone. That shift encourages teams to stay with a product long enough to understand how customers actually use it, which is where the most valuable improvements are found.