Scope grows when small additions are absorbed quietly until a deadline is missed. A strong answer shows you surfaced each addition as a trade-off, protected the committed milestone, and renegotiated with the people who own the priority rather than deciding unilaterally.
Before you start
You should have an example of scope pressure on a project. This article gives a structure for it.
Step by step
Step 1: Make the trade-off explicit
Every addition has a cost. State what would be dropped or delayed to include it, in terms the requester understands. A visible trade-off turns scope creep into a decision instead of an accumulation.
Step 2: Protect the committed milestone
Define the smallest valuable increment and hold the line on it, offering new requests as follow-ups. That keeps a shippable result while still capturing the ideas, rather than sliding the date.
Step 3: Renegotiate with the owner
When a change is important enough, take it to the person who owns the priority and let them trade it against the current scope. The decision belongs to them; your job is to make the consequences visible.
Worked scenario
A concise STAR answer documents the trade-off.
Situation: A project kept gaining "small" requirements before launch.
Task: Ship the promised increment on time.
Action: Logged each request, showed the cost, offered a fast core plus a follow-up
list, and had the product owner rank the additions.
Result: Shipped the core on time; the ranked additions landed in the next cycle.Walk through the example
The answer makes cost visible, preserves a shippable core and routes the ranking decision to the owner. It shows control without rigidity: requests are captured, not refused, but they are traded rather than absorbed.
Common mistake
Silently absorbing additions and then missing the date, which surprises everyone. The opposite is rigidly refusing all changes, which ignores that some requests are genuinely important. Another is deciding the priority yourself instead of the owner.
Verify the behavior
Check that your story shows a logged trade-off and a preserved increment. Confirm you involved the priority owner. Be ready for a follow-up where a late request was truly critical and how you handled it.
Interview exercise
A critical request arrives the day before launch. What do you do?
Answer and reasoning
Assess the real cost and risk, then present the options: delay the launch, ship without it and follow up, or drop something else. Give the priority owner the decision with the consequences attached. If it truly cannot wait, negotiate the specific trade rather than absorbing it and hoping the date still holds.
Continue learning
Compare prioritization in Prioritization and deadlines in Deadline negotiation. Read the Harvard Business Review on scope and try the Behavioral interview questions.