Enterprise Digital Uplift and Systematic Technology Education

Self-Paced Business Systems Analysis: Bridging the Gap between Business and Technology
About Lesson

Interviewing Techniques

In this lesson, we will explore interviewing techniques as a powerful method for eliciting requirements from stakeholders.

Introduction to Interviewing
Interviewing is a key technique used in requirements elicitation to gather information directly from stakeholders. It involves conducting structured conversations to understand their needs, expectations, and perspectives regarding the system or project.

Preparing for Interviews
Before conducting interviews, analysts need to prepare adequately:

Identify Stakeholders: Determine the relevant stakeholders who possess valuable insights and knowledge about the system.
Define Interview Objectives: Clearly define the goals and objectives of the interview to ensure focused discussions.
Develop Interview Questions: Prepare a set of open-ended and specific questions that will elicit the desired information.
Create an Interview Plan: Establish a schedule, allocate sufficient time for each interview, and decide on the preferred interview format (e.g., face-to-face, phone, or video).

Conducting Effective Interviews
To conduct effective interviews, analysts should consider the following techniques:

Establish Rapport: Create a comfortable and open environment to encourage stakeholders to share their thoughts and opinions.
Active Listening: Pay close attention to stakeholders’ responses, clarify any uncertainties, and actively engage in the conversation.
Probing: Ask follow-up questions to dig deeper and gain a comprehensive understanding of stakeholders’ requirements.
Neutral Position: Maintain a neutral and unbiased stance to encourage honest and unbiased responses from stakeholders.
Documenting: Take detailed notes during the interview to capture essential information accurately.

Types of Interview Questions
Interview questions can be categorized into several types, including:

Open-Ended Questions: Allow stakeholders to provide detailed and unrestricted responses, encouraging them to share their perspectives.
Closed-Ended Questions: Seek specific information and can be answered with a simple “yes” or “no” or with specific details.
Probing Questions: Help gather additional information or clarify stakeholders’ responses, encouraging them to elaborate further.
Hypothetical Questions: Pose hypothetical scenarios to explore stakeholders’ preferences or responses in different situations.
Prioritization Questions: Ask stakeholders to prioritize requirements or features to understand their relative importance.

Challenges and Considerations
Interviewing stakeholders may present some challenges that analysts need to address:

Limited Availability: Stakeholders may have limited time and availability, requiring careful scheduling and efficient use of interview time.
Bias and Influence: Stakeholders’ biases or influence from others may impact their responses, so it is important to probe for genuine requirements.
Language and Communication: Language barriers or technical jargon may hinder effective communication, necessitating clear explanations and active listening.

Interview Follow-Up
After conducting interviews, analysts should review their notes, clarify any uncertainties, and validate the information with stakeholders if needed. The gathered requirements should be analyzed, consolidated, and documented appropriately.


Interviewing is a valuable technique for requirements elicitation, allowing analysts to gather firsthand information from stakeholders. In this lesson, we explored the preparation and techniques involved in conducting effective interviews. We discussed the importance of establishing rapport, active listening, probing, and neutral positioning during interviews. Additionally, we highlighted different types of interview questions and the challenges that may arise during the process. By mastering interviewing techniques, analysts can effectively gather requirements, ensure stakeholder satisfaction, and contribute to the successful delivery of the system or project.

CHAT