We interview the people who do the work, document what the solution must do, and prioritise it so the first version is achievable.
Requirements gathered from one stakeholder tend to describe that person’s part of the process. We deliberately talk to several, including the people who will use the system daily, and write down the disagreements as well as the consensus — unresolved disagreement is what stalls projects later.
We talk to the people who will use and pay for the system.
The current process written down, step by step, including the exceptions.
Requirements ordered by value and dependency, not by who asked loudest.
A written requirements document
A prioritised feature list
An agreed definition of the first release
A short call
Short and focused
Phase by phase
Optional
Tell us what you’re trying to achieve. We’ll help you find the right path forward — no obligation, no jargon.