Find out what changed in the business before assessing the change itself, because that tells you whether more is coming. Then do the impact analysis: what is built, what is designed, what is tested, and what has to be redone. Present costed options and let the sponsor decide, and update traceability so the change does not leave orphaned tests and stale documents behind.
Why interviewers ask this
Interviewers want to see change handled analytically rather than emotionally. The standout move is asking why the requirement changed, since a shift in the market or a regulation usually means further changes are coming and the plan should account for that. They also want a real impact analysis across build, test, and documentation, and the housekeeping that stops stale artifacts lingering.
How to structure your answer
- Ask what changed in the business and whether more is coming.
- Assess impact across design, build, test, and documentation.
- Present costed options rather than a yes or no.
- Let the sponsor decide, then re-baseline.
- Update traceability so nothing is left orphaned.
Example answer
My first question is not about the change, it is about why it changed, because that tells me whether this is a one off or the first of several. If a regulation moved or they lost a major client, more is coming and I should plan for that rather than treat it as an isolated request. Then I do the impact analysis properly: what is already built, what is designed but not started, what test cases die, what documentation goes stale, and what has to be reworked. That number is usually bigger than people expect, and the testing part is the bit nobody counts. I take it back as options with costs, so the sponsor can choose to absorb it, defer it, or drop something else, and then we re-baseline. The last step is the boring one: I go through the traceability and clean up, because otherwise you end up testing against a requirement that no longer exists.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- How do you tell a legitimate change from someone changing their mind?
- What do you do if the change makes work already completed worthless?
- How do you keep the team's morale up through significant rework?
Related business analyst questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions