DDD targets software with complex domains, which is usually the case with enterprise information systems. Traditionally, in the organizations developing this kind of software, there is a "systems analyst" (SA) role which faces the stakeholders, translating their needs into software requirements which drive software development activities.
This way, the SAs disconnect communication between the domain experts and the developers who do the design. Effectively, an SA creates a (maybe implicit) model based on her own perception of usefulness and possibly filters out knowledge useful for design purposes.
The question is whether the role of systems analyst should be eliminated at all in a DDD setting. If the answer is positive, this will make an unexpected change in the organization which may be hard to justify, as we are just going to adopt a "design" method. Are there any guidelines on how to make such a transformation? Or else, we must somehow fit the SA role into the DDD setting.