situational Easy GeneralProduct ManagerMarketing

Two weeks before launch, an influential stakeholder insists on adding a new feature that is not in the plan. How would you respond?

Scenario questions test judgment under uncertainty. Below is a sample answer for this one, the traps candidates fall into, and the probes interviewers follow up with.

A strong example answer

Two weeks before a launch I managed, a senior stakeholder asked for a new reporting view. The request landed like a demand, but late requests usually carry a real concern underneath, so I started with questions instead of a reaction. What problem does this solve? What happens if it ships later? His answers told me the need was genuine — just not launch-blocking.

With that, I made the trade-off concrete. The team estimated the work honestly: nine days of build time, plus regression risk on a release candidate. I laid three options in front of him and the sponsor — ship on time without the view, slip the launch to include it, or ship on time and deliver it as a fast follow. I gave a recommendation, but the call was theirs. Decisions like this should be made with real numbers on the table, never on vibes or on whoever argues loudest.

We shipped on schedule and delivered the view in the next cycle. Once he saw the adoption data, he admitted the timing had been fine. He later became one of my strongest allies on other launches — partly, I think, because I took his concern seriously without treating the launch date as negotiable by default.

A framework for your own answer

  • Situation: Describe the launch, the stakeholder, and the late request.
  • Task: State your duty: protect the launch while taking the concern seriously.
  • Action: Explain how you scoped the request and presented costed options.
  • Result: Share the decision, the fast-follow outcome, and the relationship result.

Common mistakes to avoid

  • Don't say yes on the spot to please a powerful stakeholder — that is how launch dates blow up.
  • A flat no with no alternatives damages the relationship and practically invites escalation.
  • Candidates often present the trade-off without a real estimate, so the decision gets made on politics instead of facts.
  • What is worse than saying no? Promising a fast-follow date your team never validated, then missing that one too.

Follow-up questions to prepare for

A strong answer invites follow-ups — interviewers probe to check the reasoning holds up. Prepare for questions like:

  • What if the stakeholder escalates to your boss after you propose the fast-follow?
  • How do you distinguish a genuine launch-blocker from stakeholder anxiety?
  • Has a late request ever turned out to be right? What did you do?

Related practice questions

Keep drilling with these, or browse the complete question bank.

Next up

Practice this question on the clock

Reading an answer and delivering one are different skills. Run a timed round and rate yourself.

Start a practice round

Next up

Interview coming up?

Have your post-interview follow-up email ready before you need it.

Follow-up email generator