Should We Be Bilingual?
Or, is it time to pass on "Archispeak?"
This week, Grace Kim, AIA, the "doer" in our Doer's Profile, says that for architects, "so much of what we do is listen to the stories of our clients and reinterpret them into physical form." Are we adding extra grief to this complex process when we make "Archispeak "our language of choice?
I'm not talking about "Archibabble," that pseudo-intellectual bs that wanna-be superstars (and, okay, architecture writers sometimes) shovel about. I think we could agree that Archibabble could go away and the world would keep spinning.
But what about "Archispeak," that fun and handy shorthand that architects all understand among themselves? Is fenestration really more than doors and windows? Means of egress really means more than how to get out of the building? Is it really shorthand or is it a secret handshake, designed to keep the cognoscenti in and everyone else out? Just asking.
It drives me bats when my business-oriented and -educated colleagues shorthand about "buckets" and "ops plans" and "the brand." How do clients like "parti" and "schematics" and "sustainability"?
The Small Projects Practitioners Forum is collecting Archispeak terms to prepare a glossary for translation to clients. Send your terms to them, or send us your comment here, we will forward it. And let us know what you think: Is Archispeak a necessary tool, or should it become a dead language?