[Behavioral] Tell me about a time you had to reset expectations on a project.

Example Answer

I was on a cross-functional rollout where the outward messaging had gotten more confident than the project really deserved. The workstreams were moving, so the updates still sounded positive, but underneath that, a few dependencies and approval points were weaker than the timeline suggested. You could feel the gap getting wider between the status story and the actual delivery picture.

I pulled the project view back together around what was truly committed, what was still assumption-based, and where the schedule was becoming fragile. Then I walked the stakeholders through two things very clearly: what we could still deliver with confidence and what would need to move if they wanted us to protect quality. It wasn't a comfortable conversation, but it gave everyone a real decision instead of a slowly collapsing plan.

We ended up resetting the sequence and narrowing the first release. The project lost some cosmetic confidence in the short term, but it gained credibility because the team stopped pretending. That was a good reminder that expectation resets are easiest when you do them before trust is damaged, not after.

Common Poor Answer to Avoid

"We realized the timeline was too aggressive, so I let everyone know and we pushed the date."

Why it's weak

That answer is too flat. It skips the judgment, the communication challenge, and the way the PM actually reset the project around something more credible.

Why this works

It sounds like a real story a PM could tell out loud. There is context, action, tradeoff, and a clear lesson without turning into a rambling case study.