Why Do Professors "Rip Apart" Projects In The Final Review?

In a recent article in which ArchDaily reached out to our readers for comments about all-nighter culture, one comment that seemed to strike a chord with many people was kopmis' assertion that, thanks to the tendency for professors to "rip apart" projects in a final review, "there is no field of study that offers so much humiliation as architecture." But what causes this tendency? In this article, originally published by Section Cut as "The Final Review: Negaters Gonna Negate," Mark Stanley - an Adjunct Professor at Woodbury University School of Architecture - discusses the challenges facing the reviewers themselves, offering an explanation of why they often lapse into such negative tactics - and how they can avoid them.

Courtesy of Section Cut

The final review is the well-known, cautiously anticipated endgame for the student of architecture; the lonely gazelle steps up in front of the row of (too often male) toothy lions lying lazily back in their shitty folding chairs, still picking their teeth from the last devouring, sipping coffee, trying their best to look disinterested. They have carefully calibrated their postures of indifferent intimidation over years of practice. Most versions of it are sad. This is why, I suspect, architects most often wear black. It’s like a sad funeral parade of too-serious, black-clad mourners moving from station to station in search of all the cracks in the work that can be exploited, putting them quickly to bed. “This is where it falls apart”, “You could have done ____”, “This is not a thesis”. The sleepy students (after an incredibly unhealthy lack of rest) can barely follow the reviewers’ comments, even if their brains weren’t edging on fugue state. They are underfed (on mostly cheap, brown-colored things) and improperly bathed. Quite the series of insurmountable hurdles to a learning moment.

Most review spaces in my experience are, oddly enough, much wider than they are deep… this makes the already too-populous panel of critics seem to stretch infinitely in either direction. And notice next time if you will, the ends of the row of critics seem to pinch in toward the work, as if to trap the prey inside. This format of review seems to beg authority (at least formally): critics are seated, united in authoritative judgment of the student (who stands); the audience sits behind the critics, facing the same direction (the student faces them all)… one could expect to find this spatial organization in a kangaroo court.

Then, the perennial conundrum of the order of the review. The first student is tasked with overcoming the passive distraction of the critics, easing them into the hours-long review from wherever they have been that morning. This is a lot like the first inning of a baseball game: unpopulated, too-hot, and not drunk enough. By the end, it’s like closing time at a sketchy nightclub: delirious comments and questionable decisions. Some students loathe the review; they would sooner skip it altogether. But most, I find, have an expectant (if somewhat worried) idea that their work will be judged “good” or “bad” in this moment – that they’ve done the right thing or they haven’t. Students: this is probably the most uninteresting way of thinking about it. The review is about speculation as much as evaluation. Critics are not enemies, and they don’t know everything. Admitting a level of uncertainty that necessarily occurs within design education completely changes how one imagines the review moment.

Courtesy of Section Cut

In architecture schools the pedagogical model is, at best I’d say, confused. I like confused; I choose it over certainty when given the chance. In architecture, as in most other creative endeavors, students don’t learn by way of cataloguing information and reciting that information back, as they might in, say, mathematics. In algebra there are rules that simply do not waver; they are learned, practiced, catalogued, and regurgitated in response to exam questions. This is one of the more efficient ways to learn algebra. In architecture, the pedagogical model is somewhat different. Here, students make things, beautiful things, then attach those things to a wall, where they then gather their peers around and invite more-experienced (often teacherly) voices to respond to those things. It’s kind of odd. And it is notoriously difficult to measure (which I’m also okay with). This slack makes things unknowable, and the review moment is often fraught and confused because of it. Students shed tears, they experience euphoria, they drink coffee, they find new capabilities in themselves, they renounce beliefs, they drink coffee.

In many ways architecture review culture mirrors the discipline itself – it sits somewhere between the unconstrained, wildly productive studio art review where students say nothing and the work speaks for itself, and the controlled, disciplinary thesis defense where the saying of things is as important as anything. It’s somewhere between being creative and discursive, between intuition and method, between beautiful and substantial. I revel in the potential of this weird moment. It is the most exciting, most valuable, most vibrant moment in design education, and many of the reasons that make it bad are precisely the reasons that make it good. BUT… this depends entirely on one’s approach. There are many things students can do: sleep more, work harder, assume less, fail more… and forget about “right answers.” Instead, see how fast and wild the conversation can go (and, as a bonus, how many fights you can start). But we can probably do better by dissecting the psychology of the other constituent party: the critic.

Critics face a surprising amount of pressure from all sides – from the students, from the fellow critics, from the studio instructor, from the discipline, from oneself. Critics are often on trial themselves – to perform in front of friends (or enemies), students, peers, and potential bosses. They are sometimes under scrutiny by senior faculty or administrators (a double layer of critique!). One has to sound smart, after all, and architects are quite good at this. Critics always hope they are saying valuable things that resonate with The People. This hope is indicative of the struggle with relevance that every architect (and academic) seems to carry around under their arm: “who is listening?, is what I’m saying worth it?, is my work valuable?” The review is a kind of real-time feedback mechanism that tickles this instinct quite well. An affirmative head nod from a fellow critic is often enough to sustain one’s impression of themselves for some time. The anxiety over impressing one’s audience fades over time–the more reviews one sits on, the less nervous one is, of course – but the pleasure it brings seems to live on in perpetuity.

And so, given the background dynamics of this tricky ritual, critics often default to oppositional politics, to lion and gazelle mentality. The critic must have something truly good to say. And nothing pleases the people like torture. Sadly, there are learned behaviors that pass not only from generation to generation but also virus-like amongst peers, often within one afternoon. Students often don’t see the implicit grappling for power and attention that tempts critics in this scenario.

Read the rest of this article at Section Cut for more about the mindset of the reviewer and a list of tropes that they often fall into - and a way they can avoid them to create a positive educational feedback loop.

About this author
Cite: Mark Stanley. "Why Do Professors "Rip Apart" Projects In The Final Review?" 09 May 2015. ArchDaily. Accessed . <https://www.archdaily.com/629314/why-do-professors-rip-apart-projects-in-the-final-review> ISSN 0719-8884

You've started following your first account!

Did you know?

You'll now receive updates based on what you follow! Personalize your stream and start following your favorite authors, offices and users.