Interviews
Interviews are structured or semi-structured conversations with stakeholders or subject matter experts to elicit needs, requirements, risks, and context. They enable probing and follow-up questions to obtain deeper, qualitative insights than documents or large group sessions typically provide.
Key Points
- Interviews can be structured, semi-structured, or unstructured depending on the objective and time available.
- They are useful for uncovering tacit knowledge, clarifying ambiguous information, and exploring complex issues in depth.
- Can be conducted one-on-one or in small groups, in person or virtually, with careful attention to confidentiality.
- Preparation is critical: define objectives, select interviewees, and create an interview guide with open-ended questions.
- Active listening, neutral wording, and probing questions improve accuracy and richness of the data.
- Validate key takeaways with interviewees to reduce misunderstandings and bias.
- Combine interview findings with other data-gathering techniques to triangulate and strengthen conclusions.
When to Use
- Early in a project to explore needs, constraints, and success criteria with key stakeholders.
- When stakeholders hold unique or tacit knowledge not captured in documents.
- To clarify conflicting or ambiguous feedback from surveys, workshops, or metrics.
- For sensitive or politically delicate topics that require confidentiality and trust.
- When expert judgment is needed to assess risks, assumptions, or feasibility.
- To elaborate acceptance criteria, user stories, or process details that require context.
How to Use
- Define clear objectives and outcomes; decide on structured vs. semi-structured format.
- Select interviewees based on roles, influence, knowledge, and diversity of perspectives.
- Prepare an interview guide with open-ended and probing questions; plan time and logistics.
- Obtain consent for note-taking or recording; explain purpose, confidentiality, and how data will be used.
- Conduct the interview: build rapport, ask open questions, probe for specifics, and actively listen.
- Summarize key points during the close and confirm understanding with the interviewee.
- Document, synthesize themes, and update project artifacts (requirements, risks, backlog) promptly.
- Follow up to validate interpretations or fill gaps discovered during analysis.
Inputs Needed
- Interview objectives, scope, and success criteria.
- Stakeholder register or contact list to identify and prioritize interviewees.
- Background materials such as the business case, charter, scope statements, process maps, or prototypes.
- Existing data and signals to probe (survey results, metrics, incident logs, previous lessons learned).
- Interview guide, consent/recording plan, and logistics (schedule, platform, venue).
Outputs Produced
- Interview notes, summaries, transcripts, and recordings where permitted.
- Refined or new requirements, user stories, acceptance criteria, and success measures.
- Identified risks, assumptions, issues, and constraints for the relevant registers.
- Updated stakeholder needs, priorities, and expectations.
- Updates to the elicitation log, decision log, backlog, and change requests as needed.
Example
A project manager for a cross-functional improvement initiative interviews field staff, operations leaders, and compliance specialists. Through semi-structured conversations, the PM uncovers a regulatory constraint that affects turnaround time and a hidden handoff problem between teams. The PM summarizes findings with each interviewee for confirmation, then updates the backlog, revises acceptance criteria, and adds new risks to the risk register.
Pitfalls
- Asking leading or closed questions that bias responses.
- Insufficient preparation resulting in unfocused conversations and missed insights.
- Over-reliance on a small set of voices causing sampling bias.
- Poor note-taking or delayed documentation leading to errors and loss of nuance.
- Failing to validate interpretations with interviewees.
- Ignoring cultural and virtual dynamics that affect trust and candor.
Related Items
- Workshops and facilitated sessions.
- Focus groups.
- Surveys and questionnaires.
- Observation and job shadowing.
- Brainstorming and nominal group technique.
- Document analysis.
- Delphi technique for expert consensus.
PMP Example Question
During early elicitation, a project manager needs to uncover tacit knowledge and clarify ambiguous requirements from a small set of subject matter experts. What should the PM do first?
- Send a structured survey to all stakeholders to collect quantitative data.
- Schedule one-on-one semi-structured interviews with selected experts.
- Hold a large brainstorming workshop with the entire project team.
- Rely on existing documentation to avoid disrupting busy experts.
Correct Answer: B — Schedule one-on-one semi-structured interviews with selected experts.
Explanation: Interviews enable probing and clarification of tacit knowledge in a confidential setting. Surveys and large workshops are less effective for deep, contextual insights.
HKSM