Elicitation and Collaboration
What to know
Elicitation is not the same as asking stakeholders what they want. It is the planned discovery of requirements and information through preparation, conduct, confirmation, and communication. Know the major techniques-interviews, workshops, focus groups, observation, document analysis, surveys, prototyping, and brainstorming-and when each fits. Preparation includes selecting stakeholders, choosing techniques, scheduling, and preparing questions or models. Confirmation checks that what you heard is complete and correct; communication ensures the right people receive it. Collaboration runs throughout: stakeholders co-create requirements rather than passively approve them.
Traps
The biggest trap is the requirements-gathering mindset-assuming needs are already formed and simply need collecting. Elicitation often uncovers unstated or conflicting needs. Another trap is relying on a single technique: document analysis may reveal rules that interviews miss, while observation reveals workarounds. Also watch for skipping confirmation-notes that are never reviewed become expensive rework. In workshops, do not let the loudest stakeholder dominate; use facilitation, parking lots, and follow-up.
Worked example
Two departments disagree on approval rules. Rather than separate interviews, run a facilitated workshop with a current-process model. Capture both views on a flip chart, mark the conflict as an open item, and assign an owner and due date. Confirm the agreed rule in writing with both departments.
Rule of thumb
Triangulate: use at least two techniques for high-risk requirements, and confirm every elicitation result with the source before basing design on it.