Understanding Stakeholder Needs and Concerns
You'll learn how to systematically gather stakeholder expectations, priorities, and concerns using proven elicitation techniques.
After you've identified and mapped your stakeholders (the previous step), you need to truly understand what they care about. This isn't about guessing or assuming—it's about actively listening and uncovering both stated and unstated needs.
Core Elicitation Techniques
Interviews are your most powerful tool for depth. Schedule one-on-one conversations with key stakeholders. Use open-ended questions: "What does success look like to you?" or "What keeps you up at night about this project?" Listen more than you talk. Follow-up questions reveal hidden concerns that surveys miss.
Surveys work well when you need breadth across many stakeholders or want quantifiable data. Ask about priorities ("Rank these features 1-5"), satisfaction levels, or specific pain points. Keep surveys short and focused—long surveys get abandoned or answered carelessly.
Observation uncovers the gap between what people say they need and what they actually do. Watch end-users work with current systems. Note their workarounds, frustrations, and efficiency patterns. Sometimes stakeholders can't articulate their real needs until you see their day-to-day reality.
Combining Approaches
Use these techniques together. Start with observation to understand context, follow with interviews for depth, then validate patterns with broader surveys. Different stakeholders respond better to different methods—executives may prefer brief interviews, while distributed teams might engage better through surveys.
What You're Really Looking For
Dig beyond surface requests to discover underlying priorities, risk tolerance, constraints, and success metrics. A stakeholder saying "I need faster reports" might really mean "I need to make decisions before Monday's meeting" or "My team wastes hours formatting data."
Key Takeaway: Effective stakeholder understanding combines interviews (depth), surveys (breadth), and observation (truth) to uncover not just what stakeholders ask for, but what they actually need to succeed.