Go-to-market strategy
What’s your approach to post-launch analysis? What do you evaluate and how does it inform future launches?
Updated · 3 min read
Why interviewers ask it
Most teams hold a retro and then forget it. The question checks whether you turn evidence into changes in how the next launch runs.
Expect this answer to be judged on strategic thinking. In the rubric, a Strong strategic thinking answer builds plans grounded in market and business context.
How to structure your answer
- Compare results to the goal. The primary metric, the baseline and the target.
- Find the drivers. Which channels, segments and messages did the work and which didn’t.
- Gather team and customer input. A blameless retro plus calls with a few customers and reps.
- Write down decisions. Two or three changes to the launch process, each with an owner.
- Feed them forward. Put the changes into the next launch brief template and check them there.
What a strong answer sounds like
The details below are made up. Swap in your own story and figures.
“I’d schedule the review at ninety days, because thirty is too early to see retention. I start with the goal. If we aimed for four hundred new accounts and reached three hundred, I ask where the gap came from. Perhaps enterprise trials converted well but the mid-market webinar brought people who never activated. I’d also talk to six or seven customers and a few reps about what they heard and what confused them. Then I hold a retro with every team, one hour, no blame, focused on what surprised us. We leave with two or three specific changes. After one launch it was bringing customer success into planning at the start and not in week six, and running a dry run of the demo. I put each change into the next launch brief template so it shows up on its own, and I check on it when that launch begins.”
What a weak answer sounds like
“After the launch I would look at the metrics, hold a retrospective with the team, and write up what went well and what could be improved. I would share the learnings with the wider company.”
The weak answer produces a report and no decisions. Say what you would change and how you’d make sure the change shows up in the next launch.
Follow-ups to expect
- What would you do if the team resisted a retro?
- How do you handle a launch that missed but was well executed?
- How long do you wait before judging results?
- Who should see the write-up?
Draft a short answer to each and read them aloud. The follow-up questions guide has a method for keeping them tight.
More questions in this category
Frequently asked questions
- Is it worth doing this for a small launch?
- Yes, in a shorter form. A fifteen-minute review of the goal and one lesson takes little time and still improves the next launch.
- Should I include customers in the retro?
- Interview them separately. Their view is useful, and they’ll speak more freely away from your team.
Guides that help with this question
All guidesPractice it
Answer it out loud.
A Mokk session asks this question and follows up on your answer. A question costs 1 credit and your first credit is free.