I'm Not an Architect, So I Asked One

When I met my wife for the first time, one of the first questions was the usual one: what do you do for a living? She told me she was an architect. I remember thinking, oh, that's interesting.

A few years later we're together, and we've met a lot of new people since. The reaction never changes. She says she's an architect, or I mention that my wife is an architect, and the person lights up. "Wow, that's so cool. What a great job."

It's even better when people ask us both at once. They turn to me, I say finance, and I get a polite "meh." They turn to her, she says architecture, and they're delighted. I've made my peace with it.

Architecture is one of those rare jobs everyone finds palatable. People know what it is. They see it as creative and technical at the same time, and they assume architects are very smart. When I was younger I used to watch How I Met Your Mother. The main character, Ted, is an architect, and the show leans on exactly this: the job is shorthand for thoughtful, creative, a good catch.

We've been together a few years now, and there are traits I can clearly see in her that seem to come with the profession.

She has an attention to detail that borders on extreme. She has a sense of space I simply don't have, and she visualises things in 2D and 3D with an ease I find slightly unfair. She's naturally comfortable with numbers. And she has taste, plus a vision for how to transform a room that I could never produce on my own.

You see all of this when we talk about buying a place. We come at it completely differently.

I think about value for money; she asks the estate agent questions so technical that most of them simply don't have the answer, which produces a lot of awkward silences. Doing a viewing with an architect is its own experience. She projects what a space could become far better than I can, and I don't think I'm bad at it myself. She's much, much better. She also knows what things actually cost, which is useful for putting a ceiling on my grandeur.

The profession itself surprised me too. Architecture is far less creative than I had assumed. I had pictured people at a drawing board, sketching buildings all day. That happens, but it's one small step in a much longer process. The creative drawing eventually has to become a technical drawing, and that is where the real work of architecture lives. She is excellent at that part.

Most architects barely even draw by hand anymore. She can sketch, and sketch well, but most of her creative time is spent in front of a screen, inside specialist 3D software. The pencil-and-drawing-board picture I had was, again, mostly wrong.

I also never realised how much of a team effort it is. I had imagined a lead architect, maybe one or two people assisting, and that was it. On large projects it's nothing like that. You have big teams, a structural engineer, a landscape designer, an interior designer, and others, with the lead architect sitting above them all to coordinate. It's actually close to what I know from structured finance: you're surrounded by specialists, all pointed at a single goal.

So when I wanted to write about architecture, I didn't try to fake it. I'm not an architect. I asked one: I asked her.

A dozen jobs called by one name

So I asked her the simplest question I had. If someone tells you they want to be an architect, where do they even begin?

Her first answer was that there is no single beginning. "Architecture is different for everybody," she told me, "and everybody's route to being an architect is very different." That's part of what makes it such a good thing to do: you can take it in almost any direction and still, at the end of it, be an architect.

Then she started listing the directions. You could be drawn to the history of architecture and to conservation, working on listed buildings and preserving what already exists. You could be pulled the other way, toward technology and innovation, toward the more technical projects, infrastructure and energy. You could be traditional, and spend your career on the everyday buildings everyone actually uses, offices, houses, large-scale housing. You could be very creative, and work mostly on installations or temporary architecture, the things built for events. Or you could want some mix of all of it, large scale and small, across different sectors.

"There are so many different ways to get into it," she said, "depending on your natural interests and natural strengths."

The proof is in her own friends. They studied at the same universities she did, started at the same line, and have scattered in every direction since. Some work on small-scale projects and care most about conservation. Some are very creative, build installations, and still teach, tutoring students on the side. She has ended up at the large-scale end, commercial work and infrastructure. Same training, same starting point. "Everyone's gone off in their own direction," she said, and you can shape the whole thing to your own strengths.

This is why I knew I could not write about architecture in general, or use AI to fill the (wide) gaps in my knowledge: there is no such thing as architecture in general. There is only the particular path a particular person took. So the rest of this is her story, her experience, her passion. But I could have written a whole different story if I had asked another architect.

She started from feeling

Her own route began at the creative end. The university where she did her Part 1, the undergraduate degree, wanted students to be creative, to read widely, to chase ideas before they chased buildings. So she read. She read some Plato. She read Anthony Vidler's The Architectural Uncanny, a book about the unsettling feeling of things being subtly out of place. "Things that were just out of place," she said, "and how people reacted to those things."

The point of all that reading wasn't decoration. It was a way into people. "For me it was all about understanding how people react to the environment around them," she told me, "and how it can make them feel." Architecture, at that stage, was closer to applied psychology: how a material feels under your hand, what a space smells like, how light hits a surface differently depending on the hour. And in that regard, this is much closer to how I thought architects were working.

One of her tutors once told her she designed buildings in an unusual way. Most people, he said, start with the massing, the outer shape of the building, and then fill that shape with rooms. She did the opposite. She started inside, with the person, with the moments they would have in a space and how those moments would connect, and only then worked outward to the form. She designed from the inside out, and she didn't think it was unusual until someone pointed it out.

You can see that imagination in what she actually produced. Her final Part 1 project, City Zoomorphism, is on public record: a self-sustaining, closed ecosystem set on Orford Ness, the shingle spit off the Suffolk coast. At its centre sits a subterranean desalination factory, bladder-like water tanks, steamy chambers, reservoirs, treating enough water for the settlement's six hundred inhabitants and their crops. In the project's logic, the people who live and work inside the factory have, under its extreme conditions, slowly become human-lizard hybrids. It is strange, let's be honest, and it is meant to be. It is a student asking, in the most literal way available to her, what an environment does to the bodies and the minds of the people inside it.

When she discusses her work at home today, she still starts talking about how people will actually use the space, and how it will make them feel: that question, what a place does to the people in it, never left her.

The whole point is the human in the room

It would be easy to file all of that under student idealism, the kind of thing you believe as a student and quietly drop once you have deadlines and building codes to worry about. She didn't drop it. If anything, working made her more certain of it.

Her claim is simple, and slightly unsettling. A building is never neutral. It acts on the people inside it, whether or not anyone meant it to. "It could make people feel very frightened," she said, "really happy, or really calm. It could make people feel really depressed." If you are not convinced by that, just try to think about it when you go to a public building: just stop for five minutes and take the time to think about the way you feel.

To give a trivial example, I used to work in an old-fashioned office building, which despite having been refurbished many times over the years was quite dark and felt rather depressing. My employer eventually moved us all to a modern newbuild in another part of the city, full of light, with plants all around, large windows: a game changer for daily motivation. Yet, my job has not changed. A room does something to a group of people; the only question is whether the architect was paying attention when it did, or whether they managed to transcribe the idea into reality.

This, for her, is the whole point of the job. It is also the thing she thinks the profession is most at risk of forgetting.

"Sometimes people get really hung up on technical things, or on tradition," she said, "and forget about the human experience, which is the whole point of architecture."

Hold on to that sentence. It comes back later, because the deeper she went into the technical side of the job, the more it turned into a warning she had to keep giving herself.

She had seen the same idea from another angle when she spent time at a landscape architecture firm. There, the sensory experience wasn't a metaphor, it was the actual material. It has a name, biophilic design, building with the senses, and it works on you as you move. You walk through one part of a landscape and it smells like one thing; a few steps further on, it smells like another. "Different smells as you move around different areas," as she put it. Different medium, same conviction: design is something a person feels in the body, not just something they look at.

And yes, there is such a job as a landscape architect: I always assumed it was a kind of gardening, or down to the urban planning department of the city, and sort of dismissed it. But when you actually take the time to think about it, it makes sense that these spaces have been designed with as much care as any building, maybe with lesser technical constraints. Even though I recall that, during Covid, when we shared a desk at home, she spent multiple days modelling a single ramp. As it turns out, you've got many different types of ramps, each with their own pros and cons. Generally speaking, standard urban infrastructure such as public gardens, plazas, or even a simple sidewalk, are the result of a complex design process, with their own constraints and regulations.

She turned technical, without leaving feeling behind

The turn toward the technical started the way it does for everyone training in the UK: a year out. Between the undergraduate degree and the master's, you stop designing imaginary worlds and go and work on real ones. For the first time her projects weren't speculative. They were being built, in London or elsewhere, with budgets and planning constraints and building regulations, and she carried real responsibility while she was still young. It was difficult and high-pressure, which was exactly the point. "You just absorb everything," she said. That single year shaped the rest of her career.

None of this was foreign territory for her. "I've always been quite technical," she told me. "I enjoyed maths and physics at school, and art as well." The creative and the technical have always been intertwined within her. Somehow, a very similar profile to mine, yet I ended up in a non-creative field, and her in one of the most creative ones there is.

So when she reached her master's, she didn't drop the creative side. She merged it with the technical one. "My master's was a fusion of the two," she said. She leaned harder into infrastructure and technology than she had as an undergraduate, but the imagination from Part 1 came with her.

You can see both halves at full strength in her thesis. The project was called Offsetting Las Vegas, and it was shortlisted for the AJ Student Prize for sustainability in 2020. It is her own version of carbon capture, yet at the scale of an entire city.

To start with the technical half. She wrote the thesis like a scientific paper. "I tried to gather as much information as possible," she said. She built a case study on Las Vegas and the power stations that feed it, pulled the energy companies' own published figures on how much they generate and from what, calculated the total carbon emissions, arrived at a footprint for the whole city, and then worked out how much offsetting technology it would take to cancel that number out.

Then came the creative half. The proposal, inspired by Guy Debord's The Society of the Spectacle, answers that carbon figure with a landscape as excessive as the city it offsets: some 900 square kilometres of new forest and seven hundred carbon pumps and treatment plants, wrapped around a small desert town south of Las Vegas. To water all of it, the design floats a canopy five kilometres above the ground, where thirty centimetres of snow settle each month and melt down to irrigate the forest below. It is, on purpose, a piece of spectacle answering a city built on spectacle. Bear in mind this is conceptual and not backed by actual physics for that part.

Underneath both halves was the same question that drove her Part 1: not just the carbon, but the place. The thesis was also about what makes Las Vegas Las Vegas, the society and the appetite that produced it. "Different settings for different projects," as she put it. The engineering and the feeling were never in competition. The whole project was the argument that you need both.

Learning the machine

After the master's she went to work for real, and the technical education that had begun on her year out went into its deep end. In the UK, qualifying as an architect ends with what is called Part 3. You do it while you are employed, on live projects, and it is less about design than about everything that surrounds design: building regulations, contracts, law, how an architecture practice is actually run as a business.

The mechanics are unglamorous and revealing. From the moment you start working after Part 1, you log your experience in quarterly records, formally the Professional Experience and Development Record, or PEDR, writing up what you did each quarter and the problems you ran into, and someone senior who has overseen your work reviews each entry and signs it off. By the time you sit Part 3, you are meant to have touched every stage of a project (the Royal Institute of British Architects, the RIBA, sets out a project across eight distinct stages in its Plan of Work, numbered 0 to 7). Pass the Part 3 exam and you can register with the Architects Registration Board, the ARB, and legally call yourself an architect. In the UK, "architect" is a protected title; you are not allowed to use it until you are on that register. "It's so applied," she said, "it really stays with you."

I still remember her year of studying for Part 3: it was an intense period, going back to evening classes after a full day at work, years after she last sat in a classroom and after already long studies.

From the outside, she made it look easy, but I knew how much work it was. To make it harder, she did her Part 3 while working on a large infrastructure project in the UK. Part 3 quietly assumes you are documenting a building, but she was not working on what you could call a conventional building. That infrastructure project was what you could call a special project: it is being built under a completely bespoke legal and regulatory regime.

In particular, the planning regime was different, the stages were different, the whole shape of the thing was different from the textbook. So she ended up writing, in effect, two case studies at once. "I felt like I was writing two case studies at the same time," she said: one about the project she was actually on, and a second, shadow account of how an ordinary building would have been delivered instead.

That turned out to be a strange kind of luck. Because nothing about her project could be assumed to be normal, "I had to question everything, and question if it was normal," she said, "and it actually gave me a deeper understanding of how things are normally done." She learned the standard model more thoroughly by being denied it.

One thing in particular clicked for me here, because it was the part I thought I already recognised. Read the procurement route and the contract on a large project, she explained, and you can read the entire human structure of it.

The procurement route is simply how the job is organised and who carries which risk: whether it runs as a traditional contract, where the design is largely finished before a contractor is appointed, or design-and-build, where a single contractor takes on both. Sitting underneath it is a standard form of contract, usually a JCT or an NEC in the UK, that spells out the obligations between everyone involved: the client, the contractor, the architect, the external consultants, who answers to whom, who speaks to whom directly and who only through someone else. "You understand the hierarchy and the connections between all of these different people," she said. From the outside, I had compared her world to a structured finance deal, a room full of specialists pointed at a single goal. From the inside, she was describing the same animal. The contractual review, in fact, is very similar to what we do in project finance. I could finally picture one part of her job clearly. And, the other way around, she could picture mine, even if we don't look at it from the same angle.

Back to architecture. When she hit a technical term she didn't know, there was a particular place she went, and still goes: Designing Buildings Wiki, a sort of Wikipedia for architects, the plain-language reference for what a "principal designer" is or how a given contract type works. She used it constantly through Part 3. She still uses it now.

What the machine is for

By the end of Part 3 she had the machine. She moved into commercial work, offices, hospitality, larger developments, and the technical fluency began to pay the way fluency always does. You stop wasting time. You understand the regulations and the procurement and the relationships well enough to get things right the first time instead of fixing them later. "You get things right when you first do it," she said, "instead of making lots of mistakes." It makes the job easier, and it makes you good at it.

And here is where that sentence from earlier comes back.

Because the danger of getting good at the machine is that the machine is absorbing. The regulations, the contracts, the daily problems will happily take all of your attention, and not one of them is the point.

"You can get very bogged down in the technical side," she said, "and sometimes you have to really remember how it is for the person who's going to be in the building. That's one of the most important things."

The better she got at the technical half, the more deliberately she had to protect the other one. The warning she'd made about the profession was, by now, a warning she had to keep making to herself.

So the arc doesn't end with the technical replacing the creative. That was never the shape of it. The philosophy she read at the beginning and the contracts she mastered at the end are not two phases of a career; they are two things she uses on the same day, on the same project. "All of it together is really important," she said. "I use all of it every day."

Which is, in the end, why she likes the work. No two projects are the same, so the problem in front of her is never quite the one she solved last time. If you enjoy that, she said, there is no better field to be in, "like you're constantly doing a puzzle." And the puzzle is only solved when two different things are true at once: when the thing stands up, and when it is "a design that you find beautiful, that you think people will enjoy experiencing."

The engineering and the feeling, the whole way down.

Her advice, and why I asked her

I asked her, at the end, what she would tell someone standing where she stood at the beginning.

Her answer wasn't about technique but rather about direction. There are so many avenues, she said, and you get to decide, while you are still studying, which one actually means something to you.

"Decide what is meaningful to you and what resonates with you," and then take your career that way, "so you can enjoy studying, enjoy working, and enjoy contributing to the world in whichever way you feel is most meaningful for you."

It is the same thing her own path had been quietly demonstrating the whole way through. She didn't choose architecture and then find out who she was. She followed what she was drawn to, the philosophy, then the technology, then the scale, and the career arranged itself around her. The advice and the life are the same shape.

And that is the closest thing I have to a reason for doing any of this. I cannot teach you architecture. I am not an architect, and a few weeks of reading, or a (too) confident AI filling my gaps, would only have produced something that sounds right and helps no one who actually does this for a living. What I can do is go to the person who knows, and bring back what she said. This was even more important to me to ask my wife, as it let me dive deeper into her work and understand it better.

That is the whole of what I want Dantes to be. This is the first article involving someone other than me, and it is just a beginning. For now I have only asked people in my own circles to take part, but I would welcome the input of anyone willing to share their story and their resources, on whichever topic they feel strongly about.

Resources

Below are the resources my wife pointed me to, plus a wider reading list of my own for anyone who wants to go further. You'll find the full, curated set on our architecture shelf.

What she pointed me to

Designing Buildings Wiki — a Wikipedia for architects; the plain-language reference she used all through Part 3 and still uses.
Anthony Vidler, The Architectural Uncanny — the book on things being unsettlingly out of place that shaped her Part 1.
Stephen Shore — the photographer she kept returning to during Part 2 (start with Uncommon Places).
Guy Debord, The Society of the Spectacle — the text behind Offsetting Las Vegas.
The RIBA's Part 3 study books — the set she leaned on: Handbook of Practice Management, the RIBA Job Book, the Part 3 Handbook, The Architect in Practice, and Law in Practice.