situational Hard Product ManagerMarketingGeneral

A key stakeholder keeps changing requirements mid-project. What do you do?

This is a hypothetical scenario question — the interviewer wants your decision framework, not a war story. Here is a model answer, the mistakes to avoid, and the follow-ups to expect.

A strong example answer

Constant changes are a symptom before they are a character flaw — market feedback, executive pressure, or requirements that were never fully thought through. Understanding why the changes keep arriving comes before trying to stop them.

Then make the cost of change visible, kindly and concretely. Each new request gets a quick impact note: what it adds, what it displaces, what it does to the timeline. Most stakeholders never see the cumulative weight of several "small tweaks," and a simple change log — date, request, impact — often reduces churn on its own. Not by blocking changes, but by making trade-offs explicit. Structure helps too: a short weekly review where changes are batched and decided together, plus a clear line around which decisions are locked for the current phase. Batching converts a stream of interruptions into a manageable decision process, and it gives the stakeholder a regular, expected place to bring new thinking.

When the root cause is genuine uncertainty, shipping a smaller first version gives them something real to react to instead of something imagined. The goal was never to prevent change — some changes are right. It is to make every change a conscious trade-off with a visible price tag, decided deliberately rather than absorbed silently.

A framework for your own answer

  • Situation: Show empathy: changes usually reflect real business pressure.
  • Task: Clarify your responsibility for delivering despite churn.
  • Action: Institutionalize change: impact assessment, change log, decision points.
  • Result: Show the project outcome and the improved relationship.

Common mistakes to avoid

  • Complaining about the stakeholder builds nothing — build a process around change instead.
  • Accepting every change silently works right up until the deadline explodes.
  • Don't refuse all changes rigidly; inflexibility is as damaging as chaos.
  • Have you tried solving it directly first? Escalating to management prematurely skips the real skill.

Follow-up questions to prepare for

Interviewers use follow-ups to verify your story is real. If you get this question in a real interview, expect probes like:

  • What if the stakeholder is an executive you cannot push back on?
  • How do you distinguish necessary changes from noise?
  • Tell me about a project where requirement churn hurt delivery.

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