← Back to list

Architecture beyond buildings (Part I)

Architecture Isn’t Just About Buildings. And Sometimes It Isn’t About Buildings at All.

Y-H T-P · 2026-05-23 17:05 · 0 claps · 4.9 min read
#architecture #urbanism #design-thinking #spatial-thinking #creative-process
Open on Medium ↗
Wiki topics: GEN · Genomics & Sequencing PRD · Product Design 🏛️ · Architecture

Architecture beyond buildings (Part I)

People moving

People moving

Architecture Isn’t Just About Buildings. And Sometimes It Isn’t About Buildings at All.

A client told me something once, before I’d drawn a single line.

We were sitting across a table and they said: “I don’t actually want a building. I want my team to stop leaving.”

Despite being on the building up my experience as a young Architect, I believe I’ve been in this long enough to know that when a client says the quiet part out loud, you stop talking. So I did. And I listened. And everything I thought I was there to do quietly fell apart and reformed into something more useful.

We designed something smaller than what was planned. Much smaller. Less floor area, more thought per square meter. It worked. Not because the architecture was brilliant, but because for the first time in that project, we were solving the actual problem.

I still think about it. Not because it was a great building. Because it taught me something I hadn’t been taught anywhere else.

Schools teach us to think in buildings. Of course they do, it’s the medium, it’s the output, it’s what gets you hired and published and eventually respected. Nobody hangs a framed brief on a gallery wall. So you learn to move fast from question to form, from problem to plan. The training is efficient. It is also, quietly, incomplete.

Because the brief is almost never the problem. The problem is buried. Two, three, four layers down, under the program and the site and the client’s stated preferences and the budget that’s already too tight. You have to dig for it. And a lot of architects, understandably, given the economics of the practice, don’t have the time or the margin or the habit.

That’s where work that changes things separates from work that merely gets done.

A community center is not about community (Yeah right I just said that). It’s about the fact that a neighborhood has been losing its elders for fifteen years and nobody has said so publicly. A corporate office is not about the office, it’s a CEO’s last move to hold together a culture that started fraying after the third round of layoffs. A kitchen renovation is, sometimes, two people in a marriage that stopped working trying to fix something they can actually afford to fix.

Design the kitchen. A lot of architects do. It will be correct. Nobody’s life will change.

Or go looking for the real question. It’s never in the brief. You have to want it badly enough to ask for it.

There is a building in the city where I work that I find genuinely painful to walk past.

It is, by every objective measure, a good building. The proportions are considered. The light is handled well. The materials were chosen with care. The architect knew what they were doing. And it is completely, thoroughly empty of life. People walk past it the way they walk past a car they don’t recognize… without a second glance. Nobody lingers. The benches in front of it have never been used for longer than the time it takes to check a phone.

Eight minutes away on foot, there’s a space that isn’t really a space at all. A gap between two buildings on a narrowing street. No design credit. No plaque. No one’s portfolio piece. But for thirty years, people have been showing up there. Older men in the mornings. Children in the afternoon. A woman who sells grilled plantain on Thursdays. A kid who brings a speaker on weekends.

The city has tried three times to “improve” it. The neighborhood has blocked them every time.

No architect made that. But that is what I understand architecture to be capable of at its best. The ability to create the conditions for that kind of life. The materials come afterward. The life is the point.

I want to be direct about something before this starts sounding like a design school lecture.

I am not that deeply interested in architecture as philosophy. I am mainly interested in it as practice. Meaning site constraints, contractor negotiations, building codes, clients who change their minds on week eleven, budgets that were fiction from the beginning. I have been in all of those rooms and have no illusions about what it takes to get a building built.

But I do think we confuse technical skill with architectural intelligence. They’re related. They’re not the same thing.

Every architect you are competing with has technical skill. It’s the floor, not the ceiling. What separates the projects that matter ( the ones that outlast the conversation, that people feel without being able to name, that a neighborhood quietly depends on) is a quality of attention that happens before the design starts. Before the concept. Before the first sketch.

It’s the moment when you decide what you’re actually trying to do. That decision is the architecture. Everything else is the means.

The profession is under pressure from enough directions that most people I know in it have stopped looking directly at all of them at once.

AI is doing the documentation. Fees have been compressed for so long that fighting it feels futile. The smartest young architects are leaving, some for tech, some for real estate, some for nothing in particular, just out. And underneath all of it is a question that sits in every new construction brief and that almost nobody says in the room: should we be building this at all?

I think that is the most architecturally serious question we have stopped asking.

Not because building is wrong. We need housing desperately. We need schools and clinics and public infrastructure. But somewhere along the way, construction became the default response to problems that often have better answers. A building where a policy change would do more. New square footage where a programmatic rethink of existing space would serve better. Addition where subtraction was called for.

The architects I respect most have, at least once in their career, looked at a brief and told the client: this is not a construction problem. And then shown them what it was instead.

That is not unbuildable idealism. It is the job, done properly.

I’ll be honest… I don’t know how to close this cleanly, because I don’t think it closes.

What I know is that the projects that follow me ( the ones I turn over in my mind years later, the ones I reference when I’m trying to explain something to my fellow architects and friends) are almost never the most technically resolved or the most photographed. They’re the ones where the thinking was honest from the beginning. Where someone decided, early, to go looking for the real problem instead of accepting the one that arrived pre-packaged in the brief.

Those projects usually don’t win awards. Sometimes they don’t even get built.

But they change something. In the client, in the people who use the space, occasionally in the street or the neighborhood or the way a city block feels on a Wednesday morning to someone who couldn’t tell you why.

That’s what this discipline is capable of. Buildings, when they come, are how we make it tangible. But they are the result of the thinking.

The thinking is where it starts. It is also, if you do this long enough, where it never ends.

If this hit something for you ( or if you think I’m wrong about any of it) I want to hear it.


메타데이터
post_id
3ecff22165bd
slug
architecture-beyond-buildings-part-i-3ecff22165bd
url
https://medium.com/@yanntapepineau.archi/architecture-beyond-buildings-part-i-3ecff22165bd
canonical_url
https://medium.com/@yanntapepineau.archi/architecture-beyond-buildings-part-i-3ecff22165bd
author_url
https://medium.com/@yanntapepineau.archi
status
ok
fetched_at
2026-06-09 15:37:30