Quiz Entry - updated: 2026.07.14
What common stakeholder problems does Requirements Engineering need to address?
Stakeholders often can't articulate, disagree, or over-assume — so the Requirements Engineer matches a different technique to each problem.
| Stakeholder Problem | RE Response |
|---|---|
| Term discrepancies (different understanding of words) | Clarification, build glossary |
| Can describe but won't (too busy, low priority) | Workshops, document analysis |
| Know what they want but can't describe it | Prototyping, observation, scenarios |
| Don't know what they want | Creativity techniques, future workshops |
| Fixed on a specific solution (not open-minded) | Risk analysis, show alternatives |
| Conflicting requirements between stakeholders | Negotiation, prioritization workshops |
Tip: "Can't describe it" is the most common problem — that's why interviews alone are never sufficient. Use prototypes, diagrams, and observation to uncover implicit requirements.