Business Analyst interview question
How do you facilitate a requirements workshop?
Set a decision-focused objective, invite the necessary roles, share context, use a timed agenda and neutral facilitation, surface dissent, document assumptions and parking items, and finish with owners and deadlines.
Direct answer
What a strong answer covers
How it works
A workshop is worth its cost only if it produces decisions or artefacts that could not be produced by email. It starts with a stated objective in the form of what will be decided or built, the right roles in the room including whoever can say yes, and pre-read material so the time is spent deciding rather than briefing. The agenda is timed, the facilitator stays neutral and draws out the quiet participants and the disagreements, and assumptions, open questions, and off-topic items are captured visibly instead of derailing the session. It ends with the decisions read back, each action having an owner and a date, and notes sent the same day.
Example
A two-hour workshop to define the returns policy for a new marketplace had the objective of agreeing the eligibility rules and the refund timing. Finance, operations, legal, and product attended; a one-page pre-read summarised current disputes. Two disagreements were surfaced and decided by the product lead against the principle of customer trust over margin, and three edge cases were parked with owners. The rules went into the requirements the next morning.
Common mistakes
- Holding a workshop with no decision to make and producing a list of ideas nobody owns.
- Letting the most senior person talk for an hour while others nod.
- Ending without owners and dates so nothing moves afterward.
A useful answer structure
Answer from your own work.
Do not memorise a script: use only examples you can explain honestly in follow-up questions.
Open the desktop workspace and rehearse a clear answer in your own words.