Effective requirements-gathering is part interview, part facilitation, part judgement.
Techniques:
- Stakeholder interviews — 1:1 conversations with each role. Understand their day, pain points, wishes.
- Workshops — group sessions where multiple stakeholders work through a process or scenario. Faster than serial interviews; catches inter-team dependencies.
- Process mapping — draw the current workflow on a whiteboard or BPMN tool. Visual = easier to challenge and adjust.
- Day-in-the-life shadowing — sit with a user as they work. Reveals pain that interviews don't.
- Survey / questionnaires — for breadth across many users with similar roles.
- Existing systems audit — what does the current tool do? What works? What doesn't?
Skills that matter:
- Active listening — don't interrupt; let people fully describe their world.
- Open-ended questions — "Walk me through how you handle a renewal" beats "Do you handle renewals?"
- Probing for "why" — surface true needs vs surface requests.
- Documentation discipline — capture verbatim where possible; summaries can drift.
- Confirmation loops — repeat back what you heard; let them correct.
Common pitfalls:
- Trusting the loud voice over the quiet one. Junior users often have the most honest insights about pain.
- Anchoring on the first answer. First requirement is rarely the right one; keep probing.
- Assuming current process is correct. Sometimes the right move is "stop doing X" rather than "automate X".
- Ignoring non-users. Managers describe what they think happens; users know what really happens.
A senior consultant captures both stated requirements (what they ask for) and observed needs (what the data shows they actually need).