Handling Changing Requirements
Part of the Business Analyst Roadmap
In short
'Tell me about a time requirements changed mid-project.' They aren't checking whether change happened, because it always does. They're checking whether you stayed calm and handled it with a process.
'Tell me about a time requirements changed mid-project' — testing whether you handle ambiguity and change gracefully rather than treating it as a crisis or an annoyance.
Think of it like this
The baker's last-minute change
The night before the party, the customer calls: make it eggless, and add a second tier. A good baker doesn't panic or refuse. He checks what's possible, explains the new price and time, gets a yes, and adjusts.
Watch it happen
STAR for a change story
1/5Situation: 'Two weeks before launch, the client added a new approval rule from their auditors.'
The big ideas
What you need to know
Show a calm attitude
Say change is normal. Treating it as a crisis or an insult is exactly what interviewers worry about.
Impact analysis first
Before saying yes or no, work out the effect on scope, time, cost and quality.
Offer options
Present trade-offs to the decision-maker. You don't decide alone, and you don't just absorb the change.
Record the decision
Update requirements, the backlog and the change log so everyone works from the same version.
Save yourself the pain
Common mistakes
Oops
Telling a story where you blame the client for changing their mind.
Do this instead
Frame change as normal and focus on how you managed it well.
Oops
Saying you quietly added the change to keep everyone happy.
Do this instead
Show you assessed impact and got an informed decision. Silent scope creep is a red flag.
Your mission
Prepare your change story
Quick check
A stakeholder asks for a big change one week before release. What should you do first?
Go deeper
- 1Prepare a real story where you navigated a requirement change professionally.
- 2Structure it with STAR (Situation, Task, Action, Result) for a tight answer.
- 3Highlight the specific process you used to assess and manage the change, not just that it happened.
More behavioral at this stop
Explain a Past BA Project
Managing a Difficult Stakeholder
Cross-Functional Collaboration Stories
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.
