Business Analyst
After a solution goes live, how do you check that it actually delivered the benefit everyone expected?
What the interviewer is looking for
- This question tests solution evaluation. Builds business cases with costs, benefits and risks, and checks after go-live whether benefits were actually delivered.
- Strong answers: Compares against baseline measures set earlier, gathers user feedback, identifies gaps, and recommends follow-up improvements.
- Likely follow-up: What if the benefit did not show up?
Another way it may be asked: A new system launched three months ago to save the team time. How would you find out whether it did?
A structure to follow: Answer, explain, example, limits
- Step 1
Answer
Give your direct answer in the first sentence so the interviewer knows where you are going.
- Step 2
Explain
Say how it works or why you would do it that way, in plain words before jargon.
- Step 3
Example
Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.
- Step 4
Limits
Say when your approach would not be the right one. It shows judgement.
This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.
Common slips
- Reciting a definition without showing you have applied it.
- Using terms you cannot explain if asked a level deeper.
- Claiming experience beyond what you can discuss in detail.
How to practise it
Say the answer in 90 seconds, then answer the follow-up as if it were a new question.
Related questions
- How would you build a business case for replacing an old core system, including costs, benefits and risks?
- If a manager says their team's reporting process is too slow, what questions would you ask first?
- How would you write a requirement so that a developer and a tester both read it the same way?
- Tell me about a time you had to understand a process or business area you knew nothing about. How did you learn it?
- Walk me through how you would map how a process works today and how it should work in future, and which tools you would use.