This tests your composure, stakeholder management, and ability to protect the project baseline while still being helpful under hierarchy pressure.
Use the role-play to show active listening, propose a quick impact assessment, and offer at least two realistic options instead of a flat refusal or an automatic yes.
Start by acknowledging the stakeholder's request without committing to it, then pivot immediately to the cost of the change. Say plainly that you need to run a quick impact assessment on two things: the launch date and the quality of the existing scope, since you have no buffer in either. Explain that even a small feature touches the test script, the regression cycle, and possibly documentation, so the real question is not whether it is simple, but what you would have to drop or delay to fit it in. Offer two concrete options, for example, a post-launch release in the next sprint, which keeps the current date intact, or a one-week slip with a compressed test phase, which you would need the sponsor to approve explicitly. Frame it as a decision for the sponsor to make, not a problem you are dumping back on them. In the Philippine context, keep the tone respectful but firm, using the Taglish register only to mirror the stakeholder's style, and never fall back on the reflexive "yes po" that feels safe in the moment but damages your credibility later. Close by asking which option they prefer, so the conversation ends with a clear, documented choice rather than an open-ended promise.
Avoid the trap of saying 'Yes po, gagawan natin ng paraan' right away because you feel pressure from a senior leader. Instead say, 'I hear that this is important. Let me show you the impact on the launch date and budget, and we can choose the least risky path.'
Situation
In my previous role as a project manager for a retail inventory system, the sponsor asked me two weeks before launch to add a small customer note field that she said would take only an hour.
Task
I had to respond to the sponsor in that meeting and protect the launch schedule without dismissing the request outright.
Action
I acknowledged that the field seemed small and asked how it would be used. I then asked a developer to give a quick estimate, which revealed that adding the field would require a database update, a UI change, and two days of regression testing. I presented three options to the sponsor: move the launch by one week, add a temporary workaround, or include the field in a post launch patch.
Result
The sponsor chose the post launch patch, and we launched on the original date with the field delivered ten days later after a proper test cycle.
Even a 'simple change' can hide testing and integration work, so estimate before committing.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.