Interviews

Interviews

Introduction: Why This Matters

Interviews are one of the most direct and effective ways to gather information from stakeholders, subject matter experts, or team members. They allow the project manager to explore perspectives in detail, ask clarifying questions, and uncover insights that might not surface in group settings.

On the PMP exam, interviews are commonly tied to requirements collection, risk identification, and stakeholder analysis. In real-world projects, they provide nuanced understanding, build stronger relationships, and help ensure decisions are based on accurate and complete information.

Purpose and Objectives

Primary Purpose: To collect detailed, qualitative information by engaging directly with individuals or small groups.

Key Objectives:

  • Gather rich, personalized insights from stakeholders and subject matter experts.
  • Clarify ambiguous requirements or uncover hidden assumptions.
  • Identify risks, constraints, and opportunities from multiple perspectives.
  • Strengthen stakeholder engagement by giving individuals a voice.
  • Translate interview findings into actionable project documents.

Overview

Interviews support multiple PMP scenarios by producing high-quality insights that feed requirements, risk, and stakeholder work.

  • Where you use them: Collect Requirements, Identify Risks, and stakeholder analysis and engagement activities.
  • Why they matter: They uncover nuance, context, and assumptions you often miss in group settings.

Characteristics

  • Direct and personal: One-on-one or small group conversations designed to surface detailed insight.
  • Flexible formats: Structured, semi-structured, or unstructured depending on the need and stakeholder.
  • Clarification-focused: Enables probing questions to reduce ambiguity and confirm meaning.
  • Confidential-friendly: Often encourages more honest input than a large group setting.

Practical Example

Context: A project to develop a new mobile application for airline passengers.

Activities:

  • Interview key groups: One-on-one interviews with frequent flyers, flight attendants, and customer service representatives.
  • Capture and synthesize input: Document needs and translate themes into requirements and integration considerations.

Outcome: Frequent flyers emphasized real-time flight updates, flight attendants stressed passenger support features, and customer service representatives highlighted integration with complaint management systems. The combined insight shaped stronger requirements that addressed critical stakeholder needs from multiple angles.

Common Pitfalls

Bias and weak question design

  • Pitfall: Leading questions that steer the interviewee’s answer.
  • Prevention: Use neutral phrasing and ask open-ended questions first, then confirm specifics.

Low-value execution

  • Pitfall: Poor preparation, unclear goals, or skipping follow-up questions.
  • Prevention: Define the purpose, prepare a guide, and probe for examples and edge cases.

Loss of insight

  • Pitfall: Failing to capture insights (relying on memory).
  • Prevention: Take structured notes or record with permission, then summarize immediately after.

Incomplete coverage

  • Pitfall: Limited sample size or interviewing only the loudest stakeholders.
  • Prevention: Interview a representative mix, then validate patterns with other techniques.

Sensei Tip : Start broad, then sharpen. Use open-ended questions first, then confirm specifics. That is how you uncover assumptions without pushing your own.

Exam Alert : If the question says you need detailed, qualitative insight or you must uncover hidden assumptions, interviews usually beat surveys and group sessions.

Exam Lens

Patterns on the PMP Exam:

  • Choose interviews when the scenario requires one-on-one clarification, depth, or probing follow-up questions.
  • If the scenario emphasizes confidentiality or a stakeholder may not speak freely in a group, interviews are the safer choice.
  • When the scenario needs breadth (many people quickly), questionnaires or surveys may be better than interviews.

Sample Question

Question: A project manager needs to clarify specific requirements and uncover hidden assumptions by engaging stakeholders directly in a one-on-one setting. Which technique should be used?

  1. Brainstorming
  2. Focus groups
  3. Interviews
  4. Questionnaires

Correct Answer: C. Interviews. Explanation: Interviews are best for direct, in-depth discussions with stakeholders to clarify requirements and uncover assumptions. Brainstorming and focus groups are group techniques, while questionnaires are less personal and usually provide less depth.

Quick Recap Table

Concept Description Exam Watch Point
Interviews One-on-one or small group discussions Used for detailed, qualitative insights
Types Structured, semi-structured, unstructured Look for scenarios about clarification or hidden assumptions
Outputs Refined requirements, risks, stakeholder analysis Signals direct stakeholder engagement and follow-up documentation

Key Takeaways

  • Interviews provide deep, personalized insights not easily captured in group settings.
  • Types include structured, semi-structured, and unstructured approaches.
  • Success depends on preparation, active listening, and clear documentation.
  • On the PMP exam, interviews equal detailed stakeholder input, not broad surveys or group consensus.

Next Step

Having mastered interviews, we now move to the next data gathering technique: Checklists & Check Sheets.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (Project Management Body of Knowledge), Seventh Edition. Project Management Institute.

Scroll to Top