
Generally speaking, architects are notorious for a bewildering list of shortcomings. One of our favorite complaints involves the exasperating, browser-crashing websites that represent these alleged forerunners of design. But perhaps the more pertinent shortfall of the industry is the inability of many architects to articulate their ideas in writing. This was a topic taken up by Knute Berger, a columnist for Crosscut and a Seattle native who had some pointed remarks about the recent proposals for the redesign of Seattle’s waterfront.
The op-ed—entitled ‘Why don’t architects speak English?’—criticizes the plans, all of which were submitted for the The Howard S. Wright Design Ideas Competition for Public Space. The most notable of the finalists, a project by PRAUD called the Seattle Jelly Bean, proposes a zeppelin-like float that would hover over the waterfront and control the local climate below it. Berger was not amused.
“There’s a whole lot of visioning, revisioning, and re-revisioning going on,” he says. Interestingly, Berger blames the very devices used by architects to woo the public—the farfetched, computer-generated rendering: “Architects are now fond of using computer images that often turn schemes into abstractions that fail to give any feel for what’s going to be on the ground. There are often too many cubes, domes, blocks, trapezoids, and lozenges…And creative shapes often get lost in translation.” Aside from being too abstract, the designs mask their illegibility with “happy images of computer-generated Seattleites, frolicking in new waterfront public spaces…the sky is too blue, the vegetation isn’t right…and what are people doing when it rains, or during the work day?”

And this is when Berger begins to pick apart the text supporting the designs, block-quoting entire paragraphs from the proposals and adding acerbic commentary like a teacher reading a blatantly apathetic final paper, itching to cover it in red ink. The roundabout phrasing, the strings of buzz words (catalyzing, dematerializing, creating dialogues, etc.), are met with Berger’s unending supply of rhetorical questions.
True, architects have a tendency to pepper their sentences with theoretical jargon, but that’s just one aspect of the problem. The written “gobbledygook,” or “academia-infested code,” that architects often use to explain their designs are reflective of a larger issue that Berger touches upon earlier in his article: “the waterfront re-do suffers from goals that are far too general to mean much, and details that are far too small or undetermined to give us lay people specifics.” In other words, many proposals today fail to express an idea that can be scaled up to the big picture and back down to the small details. Instead, the ideas hover safely in the realm of the abstract, unable to truly engage with site and context, which is the real challenge of architecture. How can that be fixed? To start, Berger has a suggestion for a better Seattle Jelly Bean: a giant floating coffee bean.
[All images courtesy the architects]
more