Interviews

Elicit detailed requirements and uncover real needs through direct stakeholder conversation.

Definition

Interviews are structured or semi-structured conversations conducted by a Business Analyst to elicit detailed information from individual stakeholders. They provide depth over breadth and are especially effective when individual perspectives, sensitive topics, or specialized domain knowledge are involved. Unlike surveys or workshops, interviews allow the BA to probe, follow up, and adapt in real time.

Inputs

  • Business objectives and problem statements
  • Stakeholder list with identified roles and influence
  • Existing documentation reviewed in advance
  • Prepared question guide organized by theme

Outputs

  • Elicitation notes with identified requirements, assumptions, and constraints
  • Stakeholder concerns and follow-up questions
  • Inputs to process models, user stories, or use cases
  • A basis for validating requirements with the broader group

When to Use

  • Requirements are unclear or ambiguous and individual perspective is needed
  • Stakeholders have unique or specialized knowledge not shared by the group
  • Topics are politically sensitive or involve individual accountability
  • Early discovery phase when building trust and credibility with stakeholders

When Not to Use

  • When alignment across many stakeholders is required — use a workshop
  • When time is extremely limited and broad input is needed — use surveys
  • When stakeholders have already agreed and information is well documented
  • As the only technique on a large initiative — interview findings must be consolidated and cross-validated

See this technique in action with a free RequirementsHub workspace.

Start Free Workspace →