From software development classes in School to University, we were told the most powerful method of requirements gathering was observation. Yet in my whole professional life I've never had a chance to do it despite putting the idea forward. One of my old colleagues who managed to observe a client was met with hostility and questions from the people he was observing. Other times clients want to dictate and have no dia…
When I was developing internal software at a big company, I went to observe some actual users at the company. (I thought what we were building didn't make sense, so I wanted to see if they actually used it that way.) I got a tongue lashing from management for that one! "You're a developer. You're not supposed to talk to users." The entire project, of course, was eventually cancelled.
Been there, done that. Once spent months working on a project but when I finally got to talk to the users they told me it didn’t do what they wanted and even if it did they wouldn’t change their working practices (union rules maybe?)
At the end of the year the manager who had assigned me this project dinged me on my appraisal for not having delivered it.