First, check the targets were agreed and measured as set
"The launch underperformed" needs a comparison. Find the launch plan and look for targets written before launch, with a measure, a number and a date for each. If there were none, the launch did not miss a target; it lacked one, and the last cause on this page comes first. If targets existed, check that the results are being read the way they were set: the same measure, the same segment, the same window. A launch meant to drive adoption among existing customers should not be marked down for weak press coverage, and a major launch read after a fortnight may simply not have reached its sales cycle yet.
Then locate the shortfall in the chain from attention to revenue. Were enough of the right people reached? Did they understand and show interest? Did interest become trials, demos or purchases? Did those who started succeed with the product? A launch can miss at any link, and each link points to a different cause. Other programme-level problems are routed from the marketing strategy troubleshooting hub.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Little noticed a significant change, or a minor one drew heavy spend for little return | The tier assigned against the tier criteria and the change it announced | Launch tier mismatched to the change | Re-tier and relaunch at the right scope |
| People saw the launch but describe the product wrongly or cannot say who it is for | Launch messages and pages against the positioning; buyer feedback | Positioning and message hierarchy unclear | Rewrite around one segment, its job and the proof |
| Interest arrived but demos stalled, questions went unanswered, support was surprised | Training dates, asset availability and sales feedback in launch week | Sales and support not ready | Train and equip now; brief support |
| Broken links, missing pages, untracked campaigns or a product gap at launch | Which readiness checks were run and who signed them off | Readiness gates skipped | Complete the missing pieces before more promotion |
| Every team claims success with a different number | When and by whom the measures were chosen | Success measures set after launch | Agree targets now and re-read against them |
Fix, verify and prevent each cause
A launch tier that did not fit the change
A major change announced with a changelog entry slips past the market; a minor improvement given a full campaign spends heavily and teaches the audience that announcements are routine. Either way the result disappoints. The launch planning and tiers guide sets out how tiers match effort to the size of a change.
Fix: re-score the release against the tier criteria; if it was under-tiered, plan a second wave for the audiences and channels it missed, and if it was over-tiered, stop the heavy spend and let it settle as a feature or minor release.
Verify: reach among the intended audience, and the measures set for that tier, move after the second wave.
Prevent: have the tier agreed against written criteria by product, marketing and sales when the release is scheduled, not when the launch is being planned.
Positioning that never made clear who it is for and why
If buyers who saw the launch cannot say what the product does for whom, the positioning or the messages built on it were unclear. The messaging hierarchy and proof points guide turns a positioning decision into a few pillars, each with proof. Two outside tools help the rewrite. The jobs-to-be-done article in Harvard Business Review frames demand around the progress a customer is trying to make, and Strategyzer's Value Proposition Canvas maps customer jobs, pains and gains against what the product offers.
Fix: choose the primary segment, state the job the product does for it and the proof that it does it better, and rewrite the launch pages and messages around that.
Verify: buyers and new customers asked to describe the product say back the intended message, and the conversion rate (CVRShare of visits or clicks that convert.) from launch pages to trial or enquiry improves.
Prevent: test the messaging with a handful of target buyers before the launch assets are produced.
Sales and support not ready on the day
Launches create questions. If representatives have not been trained, have no demo or comparison material, or learn about the launch from customers, interest dies in the first conversation. Support teams surprised by a new feature add to the damage. The sales content and training guide covers matching assets to buying stages and training representatives before they need it, and the tutorial on writing a product demo script adds a branch for a new buyer role, such as a finance buyer, to the existing narrative.
Fix: run a short training session now, give sales the core assets for the stages where deals stalled, and brief support with the questions customers are already asking.
Verify: sales reports fewer stalled conversations about the new product, and the share of launch-sourced opportunities that progress rises.
Prevent: put sales and support readiness in the launch plan with dates that fall before launch day, and confirm completion rather than assuming it.
Readiness gates skipped, so the launch went out incomplete
Pressure to hit a date leads teams to launch with pages missing, campaigns untracked, a key integration not ready or the audience never built. The launch then spends its moment of attention on an experience that cannot convert. The go-to-market guide defines gates with criteria for moving from one phase to the next. The phase-gate reviews framework explains how to write those criteria before each phase begins and who should make the go or hold call.
Fix: list what was missing at launch, complete it, and only then resume promotion; where tracking was absent, note the gap so later results are not compared with an incomplete baseline.
Verify: the checks that were skipped now pass, and the conversion path works end to end on the devices buyers use.
Prevent: treat each gate as a decision with named sign-off, and move the date rather than the gate when criteria are not met.
Success measures set after the launch
When measures are chosen afterwards, every team finds a number that looks good and nobody can say whether the launch worked. The measuring launch success guide shows how to choose measures by tier and set targets before the launch.
Fix: agree now, in one meeting, a small set of measures along the FunnelModel of the customer journey stages. the launch was meant to move, with targets based on comparable past launches where they exist, and re-read the launch against them.
Verify: one shared report shows each KPIA metric tied directly to an objective. against its target, and the teams accept it.
Prevent: make agreed measures and targets a condition of approving the launch plan.
A prevention routine for launches
Every cause on this page is decided before launch day, so prevention means a few fixed checks in the planning process rather than better luck afterwards. When a release is scheduled, agree its tier against written criteria with product, marketing and sales. Before any assets are produced, write the positioning for the launch's primary segment and test the messages with a few target buyers. At the same stage, set the measures and targets, so the plan cannot be approved without them. Before launch, run the readiness gates with named sign-off: pages, tracking, audience, sales training, support briefing and product completeness; if a gate fails, move the date. After launch, read results at the intervals the plan set rather than daily, and hold the post-launch review once the measures have had time to move. The review's output should be a change to the launch template, the tier criteria or the checklist, so that the next launch inherits what this one learned. The product launch playbook holds the forward plan this routine protects. Where the doubt is whether the product has enough demand at all, testing demand before the launch settles it before stock is ordered or the build is committed.
A software firm's reporting add-on
A project-management software firm launched a reporting add-on as a feature release with a target of 600 paid activations in the first quarter. After eight weeks it had 140. The review found three causes. The add-on opened a new segment, finance teams, and so met the criteria for a major launch, but it had gone out as a feature release with one email to existing users. The launch page described dashboards rather than the job finance teams needed done, closing month-end reports faster. And the sales team had been briefed two days after launch, with no demo script for finance buyers. The firm re-tiered the add-on, rewrote the page around month-end reporting, trained sales and ran a second wave aimed at finance teams. Activations reached 520 by the end of the following quarter.
Common mistakes
Judging the launch on numbers nobody agreed in advance. Holding the date and skipping the gate. Briefing sales on launch day. Describing features instead of the job the product does. Answering a weak launch with more media before the cause is known.
