situational Medium GeneralProduct ManagerData / AnalyticsMarketing

Six months after you championed a change, the data shows it is not working. What would you do?

How to handle this hypothetical in an interview: a worked example answer, the missteps that signal poor judgment, and the follow-up questions that test your reasoning.

A strong example answer

Six months of bad data on something with my name on it — the temptation is to defend it, so I treat that impulse as the first thing to manage.

Then two checks before any verdict. Is the measurement trustworthy, and is six months even the right window for this kind of change? Some shifts take longer to surface. Second, and harder: is the idea wrong, or the execution? Those look identical in a dashboard. Adoption numbers plus a handful of conversations with the heaviest users usually separate them — teams that genuinely embraced the change versus teams that complied on paper.

If execution is the gap, the answer is enablement, not abandonment. If the idea itself is wrong, I write the rollback proposal myself: original thesis, evidence against it, what we learned. Recommending the death of your own project hurts once and builds credibility permanently. Either way, the loop closes publicly — a short note on what the data showed and what happens next, so the next person is not afraid to champion something.

A framework for your own answer

  • Situation: Own that your name is attached to the initiative.
  • Task: Verify the data before reacting — then verify your own bias.
  • Action: Distinguish broken idea from broken execution before deciding.
  • Result: Show you can kill or pivot your own project cleanly.

Common mistakes to avoid

  • Your reputation is attached to the change — defend it anyway and credibility goes down with it.
  • Don't kill the initiative at the first bad month without checking whether execution is the real problem.
  • Candidates often let a failing change fade quietly instead of forcing an explicit decision.
  • If the data says the idea itself was wrong, don't pin it on the team's adoption.

Follow-up questions to prepare for

Expect the interviewer to dig past your first answer. Common follow-ups for this question include:

  • How long a window do you give a change before judging it?
  • What if leadership still believes in it after your readout?
  • Tell me about a time you actually killed your own project.

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