Crippled: How to Document

The workflow crippled by How To Document.

'Sat in on a meeting where a full hour was spent on trying to figure out how to give a Part Number to a product component. I had no idea what they were talking about, since I was there as a fill-in for something else that was supposed to be covered by the meeting ('never was) but here is the apparent problem as Noted:

There needs to be a WIP in Department A but an FG in Dept B . Before that can happen, a PO must be generated - which can't happen until there is an approved ECO for the BOO, BOM, PS, MS, ES, PLS, DPS and Rat-a-tat-tats: no one quite knew which was needed for what and what went where. The product component was completed, verified, validated and qualified - no arguments there, no disagreements, no Quality "Yes, but..." - but everyone seemed to be bewitched, bothered and bewildered on how to document it to get it properly "into the system."

Also: Dept A thinks Dept B should be WIPped, too, to which B said "FG you!" and refused to talk about it. QA said "Let's take this offline" and calmed them down.

Oh, and they didn't come up with a solution, either.

The component missed its scheduled release. It was sold, but could not be delivered.

There is a meeting scheduled Monday with Sales & Marketing to discuss how to get the product component released.