Foundations & core concepts of product launches

Nintendo put two home consoles into the market four and a half years apart. The Wii U, released in November 2012, sold roughly 13.5 million units across its entire life and was discontinued in early 2017. The Switch, released in March 2017, sold about 2.7 million in its first month, passed the Wii U's lifetime total inside its first year, and has since sold more than 140 million. Same company, same engineers, same Mario, same retail partners, same category. A hardware gap does not explain a difference that size. The second console was launched. The first one was only released. That distinction is what this lesson exists to make precise, because every other decision in a launch playbook sits on top of it.

What a product launch actually is

A release is an engineering event. The code ships, the feature flag flips, the boxes reachreachThe number of unique people exposed to your message in a given period. Unlike impressions, reach counts each person once, no matter how often they see it.View full definition → shelves. It is binary, it has a date, and product and engineering own it.

A product launch is a coordinated, time-bound commercial event that moves a defined audience from not knowing the product exists to using and paying for it, and that fixes the product's position in the market while attention is concentrated. It runs across three phases: pre-launch (building awareness, seeding proof, preparing sales and support), the launch moment (activating channels together so the market hears one story inside a short window), and post-launch (converting first use into retention and expansion revenue).

The two events are independent. You can release without launching, which happens every time a feature appears in release notes and nobody outside the build team notices. You can launch before you release: Nintendo revealed the Switch in a three-minute trailer in October 2016 and shipped in March 2017, using the intervening months to settle what the product was in buyers' heads before a single unit sold. And you can launch something you released long ago, which is what repositioning is.

Sub-concept 1: How to tell which one you have

One question separates them. Does this change what a buyer believes, or what a salesperson says? If a customer would need to update their mental model of what you sell, or a rep would need new words in a discovery call, you have a launch. If nothing changes except that something works better than it did on Friday, you have a release, and dressing it up as a launch spends attention you will want later.

This is where most teams get confused, because the two share a calendar date but nothing else. The release date is set by readiness of the code. The launch date is set by readiness of the market and the go-to-marketgo-to-marketThe strategy defining how you'll launch a product: target segments, channels, value proposition and coordinated action plan.View full definition → machine: enablement done, pricing signed off, support briefed, proof points collected. When those two dates are forced to be the same date, the launch loses, every time, because the code is the thing people can see slipping.

Sub-concept 2: Launch tiers

Not every launch deserves the same investment, and pretending otherwise is how teams burn out. A tier is a declaration of how much company attention a launch is allowed to consume.

A Tier 1 launch introduces a new product, a new category position, or a new business model. It justifies company-wide mobilisation: executive airtime, press and analyst briefings, paid media, a dedicated enablement programme, a war room in the first week. The Switch was Tier 1 for Nintendo in the strongest sense, since the company's next several years depended on it.

A Tier 2 launch is a significant capability for an audience that already knows you: a new module, a new plan, a new integration that opens a segment. It needs coordinated marketing, sales enablement and a customer communication plan, but not a keynote.

A Tier 3 launch is an improvement or fix. Release notes, in-product messaging, a line in the customer newsletter. No campaign.

Two things go wrong. Teams tier by internal effort (how hard was this to build) instead of by market consequence (how much does a buyer's view change). And every launch drifts upward, because whoever built the thing wants the keynote. A tier that is not enforced is a wish.

Sub-concept 3: Who owns the outcome

A launch has a single accountable owner, and it is not the product manager. The product manager owns whether the thing works. Product marketing owns whether the market cares: the positioningpositioningThe mental space you want your brand to occupy in your target customer's mind relative to alternatives.View full definition →, the tier, the sequencing, the readiness bar, and the number the launch is supposed to produce. Sales owns pipelinepipelineAll active sales opportunities across the stages of the sales process, together with their combined potential value and probability of closing.View full definition → conversion, support owns the first-week experience, and an executive sponsor owns unblocking. When nobody's name is on the outcome, the launch defaults to whoever shouts loudest in the go-to-market meeting.

Nintendo made a structural version of this call. In 2013 it merged its handheld and home console hardware divisions into one organisation, ending the split that had produced two competing roadmaps, two audiences and two messages. The Switch could be pitched as one machine that works on the television and on a train because one group was accountable for it.

Sub-concept 4: Positioning is the load-bearing decision

Positioning is the choice of which customer, with which problem, comparing you against which current alternative, will find your product obviously better. Get it wrong and no amount of launch activity recovers.

Slack's 2013 launch positioned the product against internal email rather than against chat tools like HipChat or IRC. Comparing itself to chat would have made it a nicer version of something people already had. Comparing itself to email made the pain vivid and the switch worth making. Slack reported roughly 8,000 sign-up requests within 24 hours of opening its preview and about 15,000 within two weeks.

The Wii U shows the reverse. Buyers could not tell whether it was a new console or an accessory for the Wii they already owned, and Nintendo executives later said as much publicly. The tablet controller was genuine engineering. The positioning never made it clear what the thing replaced.

Real-world cases

Case 1: the Wii U as a release without a launch. November 2012, into a market where the Wii had sold over 100 million units. The name reused the predecessor's equity and inherited its confusion. Third-party publishers hesitated, the software drumbeat after the launch window thinned out, and Nintendo never delivered a single sentence that told a parent in a shop what they were buying. Production ended in January 2017 at around 13.5 million units.

Case 2: the Switch as a launch. Reveal in October 2016 with one promise a person could repeat: the same console at home and on the move. Ship date 3 March 2017, tied to The Legend of Zelda: Breath of the Wild, so the launch had one reason to buy now rather than five reasons to consider later. The launch line-up was thin, and Nintendo let it be thin. Post-launch was where the plan showed: Splatoon 2 in July 2017, Super Mario Odyssey in October 2017, carrying momentum into the first holiday instead of letting the March spike decay.

Case 3: the same product, two different launches. Segment released analytics.js publicly in December 2012, aimed squarely at developers who wanted one integration instead of a dozen tracking snippets. Years later the same underlying product was launched again to a different buyer, as an enterprise customer data platformcustomer data platformSoftware that unifies customer data from every source into one persistent profile that marketing, sales and service teams can act on.View full definition →, with a new comparison set and new economics. Nothing about the release cadence changed. The launch changed because the audience and the alternative changed.

CMO action items

• Split the two dates in your planning calendar. Every item gets a release date owned by product and, where it qualifies, a launch date owned by marketing. If the two are locked together by default, you have no launch process, you have a shipping schedule.
• Write your tier definitions down in one page, publish them, and make the tier an explicit decision at planning, not an argument two weeks out. Include what each tier does not get.
• Put one name against every Tier 1 and Tier 2 launch, alongside the number that launch is expected to produce and the date that number will be read. Ownership without a metric is sponsorship, not accountability.

Common mistakes that kill results

Mistake 1: calling a release a launch. The market can only be asked to pay attention a few times a year. Spending that attention on a feature that changes nothing a buyer believes leaves you with no credibility on the day something genuinely new arrives.

Mistake 2: treating launch day as the finish line. The launch moment is the starting gun. Companies that spike on day one and vanish by week four have confused awareness with adoption. The post-launch plan needs the same detail as the pre-launch plan, with named milestones at 30, 60 and 90 days.

Mistake 3: leaving sales and support out of the definition of ready. Marketing can produce ten thousand leads on launch day. If reps cannot state the positioning, handle the obvious objections and demo in the new context, those leads die in the pipeline and the launch reads as a demand problem when it was a readiness problem.