As a general rule of thumb, I find classifying users into five different types one of the most useful elements when looking at requirements and design purposes. If you approach the requirements and design process as a truly collaborative exercise, then you'll understand that it's not just about extracting information from users.
It's important to understand each type of user so that you can tailor your approach, and adapt your questions and your answers, to answer their questions and satisfy their needs.
The key difference between a developer's and a manager's perspective at this stage is the manager's additional responsibility of facilitating the process while also managing everyone's interest, instead of only being concerned with gathering enough information to begin coding. Therefore, managers...