Use stories when the team can talk to each other and refine as they go. Use cases suit complex flows, heavy alternate paths, or documentation that has to stand alone for auditors, a vendor, or a team you cannot easily reach. A use case captures the whole interaction including exception flows; a story is a placeholder for a conversation, and it fails when that conversation cannot happen.
Why interviewers ask this
This checks whether you choose artifacts by context or by habit. Interviewers want the tradeoff named clearly: stories depend on conversation and lightweight refinement, use cases carry detail across distance and time. Strong answers mention regulated environments and vendor contracts, where a story is not sufficient documentation, and avoid treating either format as inherently more modern than the other.
How to structure your answer
- Frame the choice around whether the conversation can happen cheaply.
- Name the cases for use cases: vendors, auditors, complex exception flows.
- Note that stories are a promise to talk, not a specification.
- Say you mix formats within one project where it fits.
Example answer
It depends on whether the conversation can happen. Stories work brilliantly when the team is together and can refine as they go, because the story is really just a promise to talk about it. The moment that conversation gets expensive, the format stops working. So on a project where the build was with a vendor in another timezone and the contract referenced the specification, I wrote use cases, because the document had to answer questions on its own without me in the room. Same on anything with a regulator involved, where you need the alternate and exception flows written down and traceable rather than agreed verbally in a refinement session. I have also mixed them, with use cases for the two genuinely complicated flows, like a payment reconciliation with about nine exception paths, and stories for everything else. Picking one format for the whole project because it is the house style is how you get either bloat or gaps.
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 keep use cases from becoming a document nobody reads?
- What level of detail do you put in a story for an offshore team?
- How do you handle a team that insists everything must be a story?
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