A good elicitation strategy depends on the project context, stakeholder availability, complexity, and delivery approach. In an interview, show that you can plan discovery, choose the right techniques, and validate requirements before delivery begins.
My requirement elicitation strategy starts with understanding the business problem, project goals, stakeholders, scope, constraints, and existing documentation. I would review available materials such as process flows, policies, system documentation, user feedback, reports, and current pain points.
Next, I would identify the right elicitation techniques based on the audience and objective. For example, I might use stakeholder interviews for detailed perspectives, workshops for alignment, observation for current-state process understanding, surveys for broad input, and document analysis for existing rules or gaps.
After each session, I would organize the findings into clear requirements, assumptions, dependencies, risks, and open questions. I would validate the requirements with stakeholders through walkthroughs, prototypes, examples, or acceptance criteria to make sure everyone shares the same understanding.
"My goal is to move from unclear business needs to validated, prioritized, and traceable requirements that the delivery team can confidently build from."