The way that I have always looked at new product development, is that somebody needs to drive the bus. And with new product development, I believe that somebody, needs to be engineering. Manufacturing Engineering, Service, Marketing, Sales, all play a role in developing new products, but it is not their primary function. However, it is the primary function for Project Management and Engineering.
As a former mechanical engineer, and now a project manager, one thing that I have always believed is that mechanical engineers, and especially the lead mechanical engineer on a project, end up being somewhat of a project manager themselves. If there is going to be any modularity and serviceability in a design, it is typically the mechanical engineer that makes that happen. Project managers can help facilitate making it happen, but it is the mechanical engineers that actually makes it happen through his/her design work. DFMA and collaboration may increase the time it takes to complete the design phase of project, but I believe it is always in the best interest of the company.
How this all plays into the development of assembly documentation isn't crystal clear to me right now. It does appear that there are many different ways of skinning the assembly drawing cat. One thing that I am certain of, is that at the end of the design phase of most design projects, there is no one that knows how a new product is supposed to be assembled and at what level it is supposed to be serviced, better than the mechanical engineer that designed it. The big question always is, how do you transfer that knowledge to the rest of the company, and how do you maintain and preserve the original design intent?