Launch

Origin & evolution

The launch-as-event belongs to the era of boxed goods, where manufacturing, distribution, and a single irreversible release🚢ReleaseProduct SpecificationA shipped version of the productView reference → date forced everything into one moment. Geoffrey Moore's *Crossing the Chasm* (1991) gave the discipline its enduring frame: a launch is a beachhead aimed at a specific early market, sequenced so one segment's adoption pulls in the next. Launch tiers formalised that sequencing, moving from internal and alpha releases through a soft or limited launch to general availability, the point at which the product is fully supported and open to all.

Continuous delivery then pulled the engineering ground out from under the single date. The practice of separating deployment📤DeploymentEngineeringA deployment eventView reference → from release, articulated by Martin Fowler, Jez Humble, and engineering teams at companies such as Facebook, splits one event into two. Deployment puts code on the infrastructure; release exposes it to users, often gated behind feature flags🎌Feature FlagEngineeringA feature toggle for controlled rolloutView reference → so the timing becomes a business decision⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference → rather than a technical one. A feature⭐FeatureProduct SpecificationA product capability or featureView reference → can sit deployed and dark for weeks before anyone launches it.

That decoupling clarified three words teams had run together. Deployment is operational, release is the act of exposure, and launch is the market moment: the announcement, the campaign, the day the world is told. A product can be deployed daily, released gradually to a small cohort👥CohortGrowthA group of users sharing a common characteristicView reference →, and launched once, loudly, when the story is ready. The tension is real: ship continuously and you risk🎲RiskComplianceA risk to the product or businessView reference → a product that never has a moment; orchestrate a big-bang launch and you risk a date engineering cannot safely hit.

How it works in practice

A team has built a collaborative whiteboard feature. The code is deployed to production behind a flag and exercised internally for two weeks (the internal tier). They open it to 5% of accounts as a soft launch, watch error rates and activation, and widen the flag to 50% once the numbers hold.

The public launch is a separate decision, timed to a conference keynote three weeks after the feature first deployed. On launch day, a growth campaign📢Growth CampaignGrowthA growth-focused campaignView reference → carries the announcement across email, the changelog🕰️ChangelogProduct SpecificationA record of changes shipped in a releaseView reference →, and paid social. The release had already happened, quietly and safely; the launch is the moment it becomes a story the market hears.

Launch vs. its neighbours

• Release is the technical act of exposing built functionality to users, possibly to a slice of them and possibly silent. A launch is the public, market-facing moment. One launch may bundle several releases that shipped over preceding weeks.
• GTM strategy🏹GTM StrategyGo-To-MarketA go-to-market strategyView reference → is the standing plan for how a product reaches and wins its market across positioning🎪PositioningGo-To-MarketProduct positioning statementView reference →, channels, and pricing. A launch is a bounded execution within that plan, one orchestrated moment rather than the ongoing motion.
• Marketing channel📻Marketing ChannelMarketingA marketing channelView reference → is a path the launch travels along, such as email, press, or a community. The launch is the coordinated event; the channels are how its message is carried. A launch typically lights up several at once.

In the graph

In the Unified Product Graph, launch🛸LaunchGo-To-MarketA product launch event is a leaf in the Business, GTM and Growth region, hanging off go-to-market. A gtm_strategy🏹GTM StrategyGo-To-MarketA go-to-market strategyView reference → connects to it through gtm_strategy_launches_via_launchGTM Strategylaunches viaLaunchhierarchy, placing the launch as an execution under the standing plan. It ties to the engineering side through launch_ships_with_releaseLaunchships withReleasecross-domain, which keeps the market moment and the technical exposure as separate nodes that can diverge in time, and to demand generation through launch_amplified_by_growth_campaignLaunchamplified byGrowth Campaigncross-domain. Modelling these as distinct, connected entities is what lets a product deploy continuously while still choosing, deliberately, when to have a moment.