Tell me about a launch that didn’t go as planned. What happened and what did you learn?

Everyone who has run launches has had one go wrong. Interviewers ask so they can see how you diagnose a failure and whether you take ownership. A candid answer with a specific lesson tells them more than a polished success story.

It scores mainly on strategic thinking and analytical rigor. On the rubric, a Strong answer on analytical rigor distinguishes correlation from causation without being asked.

1. Say what you planned. The goal and the metric, in one or two sentences.
2. Say what happened. The gap between plan and result, stated without excuses.
3. Name the cause. The specific decision or assumption that turned out to be wrong, including any that were yours.
4. Describe the response. What you did in the moment to limit the damage.
5. Give the lesson. One change you now make in every launch, and evidence that you made it.

Every name and number here is invented. Your version should use your own.

“We launched a scheduling feature aiming for thirty percent adoption in the first quarter. We reached nine percent. I had assumed customers found the old workflow painful, and I built the whole message on that. When I looked at usage, most customers had never tried the old workflow, so we were solving a problem they didn’t know they had. In the first month I paused paid promotion and interviewed fifteen customers. We changed the message from saving time to preventing double bookings, and adoption reached twenty-two percent by the end of the next quarter. I now test the core claim with ten customers before I commit budget, and I have done that on every launch since.”

“We had a launch where the timeline slipped because engineering was late. It wasn’t ideal, but we got through it and everyone learned the importance of communication. I would make sure to plan more carefully next time.”

The weak answer blames another team, offers no number, and ends with a lesson that fits any project. Choose a miss you own, quantify the gap, and name one concrete change you made afterward.

• How early did you know it was going wrong?
• What did you tell leadership, and when?
• What would you have needed to see before launch to catch it?
• Would you launch it again?

Prepare a sentence or two for each. The follow-up questions guide explains how to answer briefly and keep your structure.

• Influencing without authority
• Presenting to skeptical executives
• Deciding with incomplete data
• Aligning sales and product
• All cross-functional scenarios questions