Seriously, there are some necessary attributes that I don’t find prevalent in “younger” (under 50?) architects. One is the desire to know construction products: how to evaluate, select and detail (in text and graphics) products that make the design real (other than GREEN attributes). Another is knowledge of construction contract documents. Communication abilities are secondary to these issues.
I try to inform and even educate the architects I work with. I don’t find much interest, however, only resentment that I’m making problems by wanting technical design directions, like which options to select for the specified product or even to want to know what specific characteristics should apply to an overly-generalized design direction, such as (the latest example) “add a ‘bulletproof’ ticket window.” After all, the expectation is that the spec writer will compensate for what architects don’t know (an ever expanding void).
But I’ll still ask the questions and inform the “designer” about what has been done in the past by the firm and state that I will follow that spec unless otherwise directed. Sometimes I get a response. Usually the issue gets resolved much later, as a response to an RFI from a bidder or contractor or from the owner when an unsatisfactory product gets installed. Of course, the issue then has turned into errors, omissions and uncoordinated descriptions in the specs rather than insufficient design directions.
I guess the fun will come back to spec writing when BIM takes over. The BIM objects will provide all the information a spec writer needs to whip out a clear, correct, complete, concise and expedient spec … or at least until the BIM program becomes robust enough to generate the complete set of specifications without a spec writer.