Why Interview Skills Matter
Stakeholder interviews are the primary requirements elicitation technique for Business Analysts. The ability to extract meaningful requirements through conversation separates excellent BAs from average ones. Poor interviews produce vague requirements, miss critical needs, and waste everyone's time. Effective interviews uncover unstated assumptions, resolve ambiguity, and build stakeholder relationships.
Interviews aren't casual conversations—they're structured information gathering with specific objectives. Preparation determines quality. Random questions produce random answers. Strategic questioning, active listening, and systematic documentation transform interviews from meetings into valuable requirements discovery.
The Interview Process
Prepare
Research stakeholder background, review documentation, define objectives, prepare questions. Send agenda beforehand. Preparation shows respect and improves results.
Open
Set context, explain purpose, establish rapport. Share what you know, clarify what you need. Build trust before diving into questions.
Elicit
Ask open-ended questions, listen actively, probe for depth. Let stakeholder talk. Use silence effectively. Capture verbatim responses.
Clarify
Confirm understanding by paraphrasing. Ask for examples. Challenge assumptions respectfully. Surface conflicts and constraints.
Close
Summarize key points, confirm next steps, thank stakeholder. Leave door open for follow-up questions.
Document
Write notes immediately while fresh. Organize findings, identify gaps, prepare follow-up questions. Share summary for validation.
Essential Question Categories
Current State Questions
"Walk me through your current process." "What pain points do you experience?" "What workarounds have you created?" "How much time does this take?"
Future State Questions
"What would ideal look like?" "If you could change anything, what would it be?" "What outcomes do you want?" "How would success be measured?"
Why Questions
"Why is this important?" "Why do you do it this way?" "Why does this problem exist?" "Why now?" Uncover root causes and motivations.
Constraint Questions
"What can't change?" "What are the non-negotiables?" "What budget/timeline constraints exist?" "What dependencies must we consider?"
Impact Questions
"Who else is affected?" "What happens if we don't solve this?" "How many people/transactions?" "What's the business impact?"
Validation Questions
"Did I understand correctly that...?" "Can you give me an example?" "What did I miss?" "Is there anything else I should know?"
Interview Techniques
Active Listening
Focus completely on stakeholder. Don't interrupt. Take notes but maintain eye contact. Listen for what's not said. Pause before responding.
The Five Whys
Ask "why?" repeatedly to reach root causes. Don't accept first answer. Dig deeper until fundamental need emerges. Stop at insight, not irritation.
Mirroring
Repeat last few words as question to encourage elaboration. "You said the process is broken?" Prompts stakeholder to explain further.
Silence
Don't fill every pause. Silence makes people uncomfortable—they fill it with information. Count to five before asking next question.
Hypothetical Scenarios
"What if we couldn't do X, what would happen?" Forces stakeholder to reveal priorities and think through implications.
Show, Don't Tell
Ask stakeholder to demonstrate current process. Observation reveals details they'd never mention. "Can you show me how you do this?"
Interview Mistakes to Avoid
❌ Asking leading questions
✅ "Don't you think we should..." is leading. Ask open-ended: "What approach would work best?" Let stakeholder drive, don't bias responses.
❌ Interviewing without preparation
✅ Research beforehand. Review existing documentation. Prepare questions. Winging it wastes stakeholder time and damages credibility.
❌ Talking more than listening
✅ 80/20 rule: stakeholder talks 80%, you talk 20%. Your job is extracting information, not demonstrating expertise.
❌ Not documenting during interview
✅ Take detailed notes in real-time. Memory fails quickly. Capture exact phrases and examples. Share summary after for validation.
❌ Accepting solutions as requirements
✅ Stakeholders describe solutions ("I need a button"). Probe for underlying need ("Why do you need that button?"). Document needs, not solutions.
❌ No follow-up after initial interview
✅ First interview rarely captures everything. Plan follow-ups, validate understanding, fill gaps. Relationships enable ongoing requirements discovery.
🚀 This Is Your Jump Start
You now understand stakeholder interview fundamentals: structured process, question frameworks, elicitation techniques, and documentation methods.
The fundamentals are here. The next steps are yours.
Practice interview skills in any context. Prepare questions systematically. Listen more than you talk. Ask "why?" repeatedly. Document immediately. Interview mastery comes through deliberate practice.
