Cross-functional scenarios
Tell me about a launch that didn’t go as planned. What happened and what did you learn?
Choose a launch that missed a number you set, and tell it plainly. Give the goal, the gap, and the assumption that turned out wrong, including any that were yours.
Then show what you did in the first weeks to limit the damage and the practice you changed afterward, with proof you kept it. Blaming another team or closing on a lesson about communication loses the panel.
5 min read
Free 10-minute mock
Practice “A launch that went wrong” free
Your first mock interview is free (10 minutes). No card needed.
What a failed-launch story has to prove
Everyone who has run launches has had one miss. Panels know that, so the question is never whether you failed. It is how you diagnosed the failure, and whether you can talk about your own part without flinching or spinning it.
Treat the miss the way you would treat a competitor’s launch. What did you expect, what happened instead, and which assumption broke? Strong strategic thinking on the rubric includes adjusting when results fall short. Strong analytical rigor means being explicit about what the evidence supports. An Exceptional answer goes further and shows you now hunt for the evidence that would disprove your plan before you commit budget to it.
Picking which launch miss to tell
- It missed a number you set or agreed to. A target makes the gap concrete and shows you were accountable for it.
- Part of the cause was yours. A positioning bet, a channel choice, a timing call. If the only cause was a late build, you become a spectator in your own story.
- It was recoverable, and you did something. The response in the first few weeks is where most of the skill shows.
- The lesson changed a habit you can prove. “I now test the core claim before launch” only lands if you can name a launch where you did it.
Avoid the disaster that still stings. A launch that hit its target a month late is also out, since that is a success story in disguise. Pick a miss that hurt.
How to shape a launch post-mortem answer
- The goal, in one sentence. What you launched and the number you were aiming for.
- The gap. What happened, as a number, with no cushioning.
- The broken assumption. The specific belief that turned out wrong and how you found out.
- The response. What you changed in the first weeks to limit the damage.
- The lasting change. One practice you adopted, and a later launch where you used it.
Timing matters more here than on most questions. People spend a minute and a half setting up the launch and then rush the diagnosis, which is the part being scored. Keep the setup under twenty seconds.
A mobile game season pass that missed
“We launched a paid season pass for a mobile puzzle game, and I set the goal of twelve percent of monthly players buying in the first season. We got to four. I had built the whole campaign on exclusive cosmetics, because our loudest players on the forums asked for them. When I looked at who did buy, most of them were players who ran out of lives every day. They wanted more play, not more hats. In week two I paused the paid social creative and ran an in-game survey that got about two thousand answers. It confirmed the pattern. For the next season we led with extra daily lives and longer events, and pushed cosmetics to the bottom of the store page. Conversion reached nine percent. The mistake was treating the forum as the player base. Now I test the core claim in a small in-game placement before any creative budget goes out, and I’ve done that on the four launches since.”
The speaker names the assumption as their own, dates the response, and gives a practice with evidence of repetition. None of that requires a dramatic failure. It requires a clear sense of which belief broke.
How launch-failure answers go wrong in the room
The miss that belonged to someone else
“The launch slipped three weeks because engineering found a performance problem late. Sales had already told customers the date, so there were some awkward conversations. We got through it, and my takeaway was to build more buffer into launch timelines.”
This is honest, and it happens constantly. It loses points because the PMM is a bystander and the lesson fits any project. If the slip is the story you have, find the part you owned inside it, such as how you rebuilt the sales narrative for the new date. Otherwise pick a launch where your own call was wrong.
The lesson with no receipt
“I learned to validate messaging earlier” is a claim. Follow it with the next launch where you did, and what the early test caught.
Follow-ups after a launch that missed
| Likely follow-up | What it is after | Your move |
|---|---|---|
| How early did you know it was going wrong? | Whether you watch leading signals or wait for the final number | Name the first signal you saw and when, even if you ignored it at first |
| What did you tell leadership, and when? | How you handle bad news upward | Say when you raised it, what you said, and what you asked for |
| What would have caught it before launch? | Whether the lesson is specific | Describe the test you would run now and what result would have stopped you |
| Would you launch it again? | Whether you can separate a bad idea from bad execution | Give a clear yes or no and the reason, then what you would change |
More questions in this category
Frequently asked questions
- How bad does the failure need to be?
- Bad enough that it mattered, and recoverable enough that you acted on it. A missed adoption target works well. A disaster that ended in layoffs pulls the answer toward emotion.
- Can I mention causes outside my control?
- Yes, briefly, if they were real. Then spend the answer on what you controlled. Panels listen for how much of the story you are willing to own.
Guides that help with this question
All guidesFree 10-minute mock
Practice “A launch that went wrong” free
A Mokk session asks this question, follows up on your answer, and scores it on five competencies. Your first mock is 10 minutes, scored like a full interview. No card needed.
Your first mock interview is free (10 minutes). No card needed.
Practice “A launch that went wrong” free
10 minutes · no card needed