Understanding Stakeholder Goals and Constraints
You'll learn: How to uncover what stakeholders truly need by looking beyond their initial requests and exploring the real problems they're trying to solve.
The Gap Between Requests and Needs
Stakeholders often come with a solution in mind ("We need a deep learning model!") rather than articulating their underlying problem. Your job is to dig deeper and understand the why behind their request. What they ask for isn't always what will solve their actual problem.
Think of it like a doctor's visit: a patient might request antibiotics, but a good doctor asks about symptoms, history, and context to diagnose the real issue—which might not require antibiotics at all.
Elicitation Techniques
Ask "Why" repeatedly: Use the "Five Whys" technique. If someone says "We need churn prediction," ask why. They might say "to reduce customer losses." Ask why that matters now. You may discover the real constraint is a new competitor entering the market next quarter.
Explore constraints explicitly: Ask about:
- Time: When do they need decisions? Daily? Monthly? One-time?
- Budget: What resources are available? Can they collect new data?
- Technical: What systems must the solution integrate with?
- Interpretability: Do they need to explain decisions to regulators or customers?
Probe edge cases: "What happens if the model is wrong?" reveals risk tolerance and whether you need high precision or high recall.
Distinguish stakeholder types: The person requesting may not be the end user. A VP might want efficiency gains, but the team using your tool needs simplicity. Map these different goals early (as you learned in Identifying and Mapping Stakeholders).
Documentation is Critical
After elicitation, document goals, constraints, and assumptions explicitly (tying back to your earlier lesson on Documenting Assumptions and Open Questions).
Key Takeaway: Effective stakeholder elicitation transforms vague requests into clear, actionable requirements by systematically uncovering underlying goals, real-world constraints, and success criteria through targeted questioning and active listening.