This screens for whether you can spot scope creep before it becomes a runaway project, and whether you can enforce process without alienating stakeholders.
Use a short STAR story that shows you noticed a pattern, quantified the impact, and introduced a lightweight control rather than ignoring the additions or blaming anyone.
Start by walking them through the moment you noticed the pattern, not the single request. Say plainly that you saw a few small asks come in through chat or email, each one minor on its own, but when you added up the hours and the dependencies, the timeline had quietly slipped by a week. Explain that you did not call anyone out or make it a blame exercise. Instead, you quantified the impact in terms they cared about, like delivery dates and workload, and then you scheduled a short meeting with the stakeholders involved. In that meeting, be honest about what you found and propose a lightweight fix, such as a simple change log or a weekly five minute check where anyone can raise an addition and you confirm the cost to the schedule together. Emphasize that you framed it as protecting their priorities, not blocking their requests, and that you still accepted the good ideas, just through a visible process. If the conversation happens in Taglish, keep your tone professional but warm, and make sure the stakeholder leaves knowing you are on their side, not policing them. Close by saying the project landed on time and the team now checks scope as a habit, not a formality.
Avoid responding to an out of scope request with 'Sige, ihabol na lang natin' because it teaches stakeholders that the change control process is optional. Instead say, 'I can add that, but let me log it and confirm the schedule impact with you first.'
Situation
During a volunteer website migration for a nonprofit, three department heads kept requesting small content tweaks by email without going through the change log.
Task
I needed to stop the silent expansion and get the team back to the approved requirements without damaging relationships with the stakeholders.
Action
I pulled the original signed requirements and listed every informal request received in the last two weeks. I called a short meeting with the department heads to show that the combined additions would add at least 40 hours of work. I introduced a simple one page change request form and agreed that any future addition would be batched and reviewed weekly.
Result
The informal requests dropped, and one genuinely urgent content update was approved formally with an adjusted deadline. The site launched two days early.
Small unrecorded additions add up, so make scope changes visible to everyone.
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.