Military structure + architect is not often like milk and honey.
How so? Think about it... Any soldier would tell you the first thing to fail in battle is the plan. As such, they've gone to great lengths to create a uniform system that allows the plan to change, while still maintaining a consistent form of communication among the ranks. I think the analogy is ideal.
Not arguing, but just wanted to offer that perspective.
When I was in Arch school, I worked as a draftsman and estimator for a company that did a lot of government / military contracts. The agencies all had iron-clad drafting standards that were really interesting... They were fully scalable from a dog house to a laser testing facility. They were well thought out... like some guy sat in a cave in Tibet for a decade and had it all worked out to the last detail. It worked well, and it taught me a lot about setting up drafting / CAD standards.
This has nothing to do with the creative process - design is a separate discipline from production, in my eyes. As another poster noted in another topic (rather bluntly), if the principals aren't fully up to speed on the production software, they shouldn't get involved in the production, other than checking the output of the production crew to insure it is communicationg their design intent (which usually rapidly erodes as the construction process begins!).
Really, the most important thing, in my opinion, is to use identification systems that work from generals to specifics. That was the main kernel of wisdom I gleaned from years of doing work for giant agencies who would have drawings being interpreted by people who might never meet and in vastly differing settings.
Just an observation.