What Architecture School Didn’t Teach Me

Architecture school taught me how to think about design. Architecture in practice taught me how buildings actually come together.

That distinction took me longer to understand than I’d like to admit.

At university, we’re trained to design meaningful, credible spaces—spaces with intent, narrative, and impact. We learn how to draw, model, present, and argue for ideas. But my first real experience on site revealed something uncomfortable: I knew far less about how architecture becomes reality than I thought.

The Gap Between Design and Construction

One of my earliest lessons was realising how little I understood about practical construction workflows. A drawing can be beautiful, precise, and theoretically sound—but that doesn’t guarantee it can be built easily, efficiently, or correctly.

Turning an idea into a building requires far more than design intent. It demands planning, detailing, sequencing, coordination, and constant communication between architects, builders, engineers, and suppliers.

These are things you don’t fully grasp until you see how a site operates—how decisions ripple through time, cost, and effort.

It’s on-site that architecture becomes real.

The Mistake That Taught Me the Most

One of the biggest mistakes I made early in my career was not asking enough questions.

I thought I needed to have the answers. I assumed that competence meant certainty. In reality, that mindset cost me time, money, and unnecessary mistakes. Builders, engineers, and experienced professionals often already know the challenges you’re facing—they’ve solved them many times before.

Humility would have taken me much further, much faster.

I learned that asking questions isn’t a weakness. It’s a skill. And in architecture, it’s one of the most important ones.

What Architecture School Actually Teaches

Over time, I came to a realisation that shifted how I view architectural education:

Architecture school doesn’t teach you everything. It teaches you how to think.

It gives you the tools to question, analyse, imagine, and explore. But the responsibility to keep learning—to ask better questions, understand context, and adapt solutions—never ends. Architecture isn’t about applying a fixed formula.

Every project is different. Every site has its own logic.

Good design comes from understanding that logic and responding to it intelligently.

The Power of Simplicity

A simple acronym sums up one of the most valuable principles I’ve adopted:

KISS — Keep It Simple Stupid.

The best solution is often the simplest one. Not the laziest—but the clearest. Simplicity reduces errors, improves buildability, and often results in more elegant architecture. Complexity should be intentional, not accidental.

This principle applies to design, detailing, communication, and even decision-making on site.

Rethinking Cost and Quality

Another misconception I had to unlearn was the idea that affordability and sound design are opposites.

Good design does not need to be ugly to be affordable. It can be practical and thoughtful while still respecting the budget.

In fact, clear thinking and simple solutions often save money. When a design understands its constraints — budget included — it becomes more focused, not less creative.

Architecture as a Mindset

Architecture isn’t a destination you arrive at once you qualify.

It’s a mindset.

A way of observing, questioning, and learning continuously. It’s built on curiosity, self-study, and the willingness to accept that you don’t know everything—and never will.

That’s not a limitation.

It’s the foundation of growth.