Product Launches

What to do if your product launch failed

First make sure it actually failed, and where. Then decide what to change before you spend another dollar.

By Shannon Kearns, published 2026-10-04, 12 min read.

Key takeaways

The work after a failed launch goes in order: diagnosis, then a decision about what to change, then (maybe) a relaunch.

When a product launch fails, the most expensive mistake is fixing the wrong thing. The numbers come in soft, leadership wants a plan by Friday, and the team reaches for whatever is easiest to change: new ads, a new headline, a bigger push.

Those fixes might feel like action, but they're usually aimed at the last step in the chain. Usually where a launch goes wrong is further up, in a decision about who the product was for, what it had to prove, or whether it was ready for more people.

How to tell if your product launch actually failed

A launch failed when it missed the success definition your team agreed to before launch. If you didn't agree on one, you can't yet tell a failed launch from a slow start, and that's the first thing to fix.

This sounds picky, but it matters. I've watched teams declare a launch dead at day 21 when the sales cycle was 60 days, and I've watched others call a launch fine for a full quarter because signups looked great while almost nobody came back and used the product twice.

If you don't have a success definition, write one now, honestly, with what you know today. Set it by funnel stage so you can see where the drop happens, not just that it happened.

Funnel stageWhat to look atA problem here usually points to
AwarenessTraffic from target accounts, ad/social impressions and engagements, press metrics, email opensChannel or audience choice
ConsiderationDemo requests, trial starts, time on key pagesMessaging or positioning
ConversionTrial-to-paid rate, win rate, sales cycle lengthOffer, pricing, or ICP fit
ActivationShare of new users who reach the first moment of valueOnboarding or product readiness
RetentionRepeat usage, early churn, expansionFit with this segment

Read the table from the top down and stop at the first stage that's clearly below where it should be. That's where you start digging. Everything below it is downstream of the real problem.

(If your problem is at activation or retention and your team is debating ad creative, that's a strong sign you're about to fix the wrong thing.)

Three checks before you call it:

If a stage is well below target and still flat after a full cycle, the launch failed there. (Not the news anyone wanted. But at least now you know where to look.)

How to limit the damage from a failed product launch

Pause anything that sends more people into the broken stage, keep everything that doesn't depend on it, and set a date for the diagnosis. Do this in the first week, before you know the full cause.

Most teams either floor it or pull the plug on everything. I get both instincts. But flooring it pays for more people to hit the same broken step, and pulling everything throws away weeks of prep and makes the whole team (and your customers) panic.

What I do when I see signs the launch isn't going to plan:

  1. Pause the accelerants. Paid acquisition, outbound sequences, partner pushes, anything that drives volume into the broken stage.
  2. Keep the product-agnostic work running. Category content, thought leadership, sales and CS preparation. None of that needs the funnel to be healthy today.
  3. Stop promoting anything customers can't reliably use. If a feature is part of the problem, take it out of the spotlight.
  4. Tell the customers it affected. If the launch broke something for an existing segment, roll it back for them if you can and tell them what happened before they find out on their own.
  5. Give sales and CS an honest talk track. What's working, what's paused, and what to say when a customer asks.
  6. Open one shared channel with everyone who touches a customer. Support, CS, sales, product, whoever owns analytics. Anything about the launch goes there.
  7. Put a date on the diagnosis. Tell leadership you'll bring back a root cause and a recommendation in two weeks, and then do it.

How to find out why your product launch failed

You find out why by pairing the funnel data with conversations: the customers who didn't buy or didn't stick, and the people inside your company who heard about problems first. The data shows you where people dropped off. You need the people to explain it.

The customers. Talk to four to six people in each group:

Ask about what happened, not about your product. "Walk me through what you were trying to do when you signed up" gets you a story. "What did you think of onboarding?" gets you a polite shrug. Record every call.

The internal team. Talk to sales, CS, support and product one at a time. Ask each person:

  1. What did you expect this launch to do?
  2. What did you hear or see after launch that surprised you?
  3. Before we launched, what did you think might go wrong, and did you say it?

If people give wildly different answers to the first one, write that down. It's a finding all by itself, and a common one. Only about 19% of people inside a company give the same answer about what the product's value even is.

Then match what you're seeing to where it usually traces back:

What you're seeingWhere it usually traces back
Traffic came, nobody convertedMessaging or positioning. Buyers didn't see their problem in what you said.
Sales went back to the old pitch within weeksMessaging written from the inside out, or no real alignment with sales before launch
Strong signups, almost nobody came backProduct readiness, or weak fit with this segment
Wins from one segment, losses everywhere elseAn ICP that's too broad
Nobody agrees whether it workedSuccess metrics weren't set before the plan
Prospects keep saying "so it's like [competitor]"Positioning that isn't differentiated

Treat each match as a hunch to check. Product marketer Irina Nica put it well in a Sharebird answer on launch post-mortems: "conversion dropped" is just an observation. Name the likely reason, then assign someone to go confirm it. (I went through each of these areas, with warning signs, in Why Product Launches Underperform.) If you're early-stage, I broke down why product launches fail before launch day, and the cheap tests that catch it.

How to run a product launch post-mortem

A product launch post-mortem is one meeting where the team looks at what it expected, what actually happened, and why there's a gap, then decides what to keep and what to change. I like the U.S. Army's After Action Review for this. Wharton describes it as four questions:

  1. What did we intend to accomplish?
  2. What did we actually do, and what happened?
  3. Why did it happen that way?
  4. What will we keep, and what will we change? (This is where the post-mortem turns into the plan for next time. I cover that side in how to prevent a failed product launch.)

How I run it:

Then share the notes with the whole team, even the parts that aren't about their function.

When to relaunch, narrow, or stop after a failed product launch

Relaunch only when the thing that caused the failure has actually changed. Once you know the root cause, you've got five realistic options:

What the post-mortem foundWhat to do
The product works, the message missedRewrite the messaging in customer language, test it with a small audience, then relaunch
It works for one segment and not the othersNarrow to the segment that's working and drop the rest for now
Buyers couldn't see why you're differentReposition before you touch messaging or channels
The product wasn't ready for the people you sent to itFix the product first, then reopen the funnel in phases
No real demand from anyoneStop, and go back to validation before spending more

Narrowing feels like shrinking, so it's usually the hardest sell inside the company. But a small group that buys and sticks around gives you proof, real customer language, and referrals. That's a lot to relaunch from. (I made the case for widening in stages in The Crescendo Product Launch.)

Stopping is the hardest call of all. Decision strategist Annie Duke, author of the book Quit, has a gut-check question in her conversation with Lenny Rachitsky: knowing what you know now, would you start this today? If the answer is no, you're probably already late. Product leader Marc Abraham made that call on Settled Plus, a home-buying product at the UK startup Settled. He retired it within months once it was clear the people it depended on (including the legal professionals in the process) weren't ready to change how they worked.

Whatever you pick, write down your kill criteria before the next attempt starts: which number, at which stage, by which date tells you to widen, hold, or stop. (Do it now, while nobody's emotionally attached to the relaunch yet.)

How to explain a failed product launch to leadership

Bring leadership the root cause, the evidence, and a recommendation. Most leaders can live with a launch that missed. It's much harder when the team can't say why, or shows up with a shiny new campaign instead of an answer.

What to include:

  1. What we expected, in the numbers we agreed on
  2. What happened, by funnel stage and segment
  3. The root cause, and the decision it traces back to
  4. What we've already paused, and what's still running
  5. The recommendation: relaunch, narrow, reposition, fix the product, or stop
  6. The kill criteria for whatever comes next

If you ran the launch, own your part: say which assumption you didn't test.

How to keep the next product launch from failing the same way

Ask your post-mortem questions before the next launch, not after. Most of what a post-mortem turns up was knowable earlier. You just have to go looking for it before the budget goes out.

I wrote that side as its own piece: how to prevent a failed product launch. It covers the pre-mortem, the decisions to lock before you build a plan, and the go/no-go criteria that catch a problem before it turns into a failure.

Questions I get on this topic

How do you know if a product launch failed?

A product launch failed when it missed the success definition set before launch at one or more funnel stages, and that stage isn't improving after a full buying cycle. Check the numbers by segment first, because a launch that looks flat overall is often working for one group and failing for another.

How long should you wait before deciding a product launch failed?

Wait at least one full buying cycle. For a self-serve product, that's usually around 30 days of activation and repeat-use data. For a sales-led product, it's one average sales cycle. Leading indicators at each funnel stage will show you sooner which stage is off.

What is the difference between a failed launch and a slow launch?

A slow launch is moving in the right direction at every funnel stage, just more slowly than planned. A failed launch has at least one stage sitting well below target and not improving. In retention, a slow launch levels off at some point, while a failed one keeps sliding toward zero.

What questions should you ask in a product launch post-mortem?

Use the four After Action Review questions: what did we intend to accomplish, what actually happened, why did it happen that way, and what will we keep or change. Before the meeting, ask each stakeholder separately what they thought might go wrong before launch and whether they said it.

Who should be in a product launch post-mortem?

Include everyone who ran the launch or touches customers: product, marketing, sales, customer success, support, whoever owns the analytics, and a leader who can make decisions. Keep the room to about eight people and gather everyone else's input one-on-one beforehand.

Should you relaunch a product that failed?

Relaunch only if the root cause has changed. If the message missed, rewrite and test it first. If it worked for one segment, narrow to that segment. If the product wasn't ready, fix it and reopen in phases. If nobody showed real demand, stop and go back to validation.

Can you save a failed product launch?

Often, yes. Most failed launches are working for somebody, and narrowing to that segment gives you proof and customer language to relaunch from. Launches are hardest to save when there's no real demand from any segment, or when the team relaunches before finding the root cause.

Keep reading

Read more articles, explore services and pricing, or take the free Go-to-Market Readiness Assessment.