Ep 170: Architecture School versus the Real World
There is a moment of realization that occurs when you get your first real job in an architectural office that maybe architecture school and what is now going to be expected from you are a little out of phase with one another. Are you prepared, do the differences matter, and what happens when you come to the conclusion that your job and almost everything you have experienced so far based on your time in college, seem so different. Have you made a terrible mistake, or are things about to get amazing? Welcome to Episode 170: Studio versus Real Life.
[Note: If you are reading this via email, click here to access the on-site audio player]
Today we are going to be talking about the differences between the studio experience of architecture students versus the realities of an actual job. There are a handful of emails that I routinely receive and in almost all cases, I would write a blog post with my normal response so that rather than rewriting my answer to the same question over and over again, I could simply point them towards the blog post on the matter.
01 The Pace is Different jump to 3:49
I’ve noticed that once you transition from school to professional practice, the pace of architectural work changes drastically. In school, you might have an entire semester to refine every last detail, but in a firm, every hour is assigned a dollar value (that might be an overly dramatic way of saying it but not entirely inaccurate). As your experience (and billing rate) grows, so do expectations for quicker, more efficient problem-solving. It can be just as cost-effective to pay a higher-rate veteran for one hour as it is to hire a newcomer for five. That dynamic pushes me to rely on my familiarity with codes, circulation, and design principles without having to look everything up or explore countless dead-ends.
At professional architectural offices, this emphasis on speed is front and center. We frequently prepare proof-of-concept studies before contracts are even signed, compressing weeks of design into just a day or two. Recently, another colleague and I modeled a 160+ key hotel with retail, a parking garage, and amenities—complete with a commercial kitchen—in roughly a day and a half. Though not entirely final, it was accurate enough to move forward with confidence. This accelerated process can be stressful, but it also highlights how crucial experience is in making fast, informed decisions
Speed and stress are definitely considerations that mark the difference between studio and post studio work.
02 Project Typology jump to 9:24
I’ve been thinking about project typology—the kinds of buildings we design in school versus the kinds we actually end up designing in the real world. In my own college experience, I worked on three or four museum projects, but I’ve never once designed a museum in my professional career. Instead, everyday architecture often involves far less glamorous work, yet someone has to design them, and that’s where many of us find ourselves in practice. It doesn’t mean there’s no pride in such work; in fact, the hotel project I’m involved with now is shaping up beautifully, with plenty of room for creativity and thoughtful design moves. I can't remember who said it, but "There are no bad projects, just bad architects" comes to mind.
Still, there’s an undeniable difference between the conceptual exercises we tackle in school and the real-world projects we take on later. My theory is that academic assignments are intentionally fantastical (i.e. ridiculous) because professors want to teach you how to think rather than lean on preconceived notions. In school, you might end up designing an environment that is specific for traveling poets and butterfly researchers—something so unusual that you can’t rely on a pre-baked solution you might be bringing to the table. During our discussion, Andrew makes a fair point by suggesting that projects like museums and interpretive centers also h...
Polska