Is Architecture Stressful?

The timelines. Every developer client I've worked with wants six months of design compressed into three, and then the city permitting process adds four months that nobody accounted for. My project manager Thora keeps a spreadsheet she calls "the lie tracker" where she logs the original schedule next to what actually happened. I looked at it last month. In the past two years, zero projects have hit their original deadline. Not one.

The worst case was a 12-unit condo project for a developer named Mr. Abed. We designed it in about four months, which was already fast. Then the zoning board hearing got pushed back. Three times. Each postponement meant updated drawings because the board wanted to see revisions addressing neighbor concerns from the last session. Each update took our team about 40 hours. So that's 120 hours of rework on a project that was already past deadline, and none of it was because the design was wrong. The design was fine. The process just kept moving the finish line. Mr. Abed called me after the third postponement and said, "Why is this taking so long?" I wanted to say, your building has been ready for months. It's the city. But you can't say that, because the client hired you to get the building built, not to explain why the city is slow. So I absorbed it.

Thora told me once that the actual design portion of a project is about 30% of the total effort. The rest is coordination, documentation, permitting, and managing the gap between what the client expected and what reality delivered. I went to architecture school for the 30%.

When you design an office building and make a mistake, someone's conference room is too small. When you design a school and make a mistake, the consequences are different. I've been doing K-12 work for most of my career, and the weight of it has only increased. Every decision about sightlines, egress paths, and lockdown protocols carries something that doesn't exist in commercial work. My associate Lisbet started with us three years ago after spending a decade on retail projects. She told me her first week on a school project that she went home and sat in her car for ten minutes before going inside her house. She couldn't articulate why. I could.

Last year, Dr. Willard, the superintendent of one of our client districts, brought in a safety consultant to audit three of the schools we'd designed in the previous five years. One finding changed everything about a cafeteria entrance we'd completed two years earlier. The sightline from the front office to the main entrance was partially blocked by a structural column. You could see 80% of the entrance from the office window, but there was a blind spot on the left side. In a normal building, that's nothing. In a school, that blind spot is the kind of detail that ends up in an incident report. We redesigned the entrance at our cost because it was the right thing to do, even though the original design met code. Code is the floor. In school design, the floor isn't enough.

I stayed at the office until 1 AM last Tuesday. Not because there was a deadline. Because the studio lead, Mikael, was still there, and in this firm you don't leave before the studio lead. Nobody says that out loud. There's no policy. But you learn fast. The first month I was here, I left at 7 PM on a Wednesday because I had dinner plans. The next morning Mikael asked me how my evening was, and the way he said "evening" made it clear that leaving at 7 was noted. So now I stay. We all stay.

The thing that finally cracked something in me was a competition entry. The firm entered a design competition for a cultural center in Abu Dhabi. We spent three weeks on it. I personally logged about 200 hours of rendering work during that stretch, which means I was working until midnight most nights and coming in on both weekends. The renderings were beautiful. I'm proud of the images I produced. We didn't win. The firm didn't get shortlisted. Three weeks, 200 hours of my time, unpaid overtime, and the result was a PDF that sits on a server somewhere. My college friend Tamsen works in tech. She makes $40,000 more than me and leaves her office at 5:30. I called her the night we found out we lost and she said, "Wait, you worked 200 hours on something and they didn't even pay extra for that?" I didn't know how to explain that in architecture, the overtime is the job. It's not extra. It's built into the culture as proof that you care enough.

Contractors. That's the answer. I can handle difficult clients. I can handle permit delays. I can handle the financial uncertainty of running my own practice. What I cannot handle gracefully is opening up a wall on a site visit and discovering that the contractor changed my design without telling me. It happened in March. A kitchen remodel for a client named Carissa. I designed a new header to span a wider opening between the kitchen and dining room. Specified the size, the bearing points, the connection details. Clear drawings. I came to the site on a Thursday and the contractor, Chet, had moved the header 8 inches to the left. Eight inches. He didn't call me. Didn't text. Just moved it because, in his words, "it worked better with the plumbing."

The structural engineer had sized that header for the loads at the original location. Moving it 8 inches changed the load path. It probably would have been fine, but "probably fine" is not a phrase I'm comfortable putting my license behind. I had to get the engineer back out, which cost Carissa $800 she wasn't expecting. Chet told Carissa the delay was because "the architect keeps changing things." I found out because Carissa called me, upset, asking why I was making changes mid-construction. I had to explain that I wasn't the one who made changes. Chet was. That conversation took 45 minutes and most of my patience.

This happens constantly. Not always that dramatic, but the pattern is the same. I design it. The contractor adjusts it in the field without consulting me. The client sees a delay or a cost increase and assumes the architect is the problem. In residential work, the contractor is on site every day. The architect shows up once a week. The contractor controls the narrative.

My stamp goes on drawings for buildings where a mistake doesn't mean a leaky roof. It means a potential explosion. That's the stress, and it doesn't fade with experience. If anything, experience makes it worse because you've seen enough near-misses to know how many things can go wrong in a facility with pressurized systems, volatile chemicals, and equipment that runs 24 hours a day. My colleague Renata has been doing this work for 15 years and she still triple-checks every set of drawings before they go out. Not because she's uncertain. Because she's experienced enough to know what's at stake.

Last year we had a situation on a pipe rack design. We use Revit for our modeling, and there was a clash detection issue between a structural member and a process pipe that didn't get flagged during our internal review. The clash was subtle, maybe 2 inches of interference, and it got through to fabrication. The fabricator caught it, but by that point they'd already cut steel. The fix cost $180,000. Nobody was hurt. Nothing exploded. But Jarrett, the plant safety officer, sat me down and walked through what would have happened if that clash had been in a high-pressure line instead of a utility pipe. The answer involved the phrase "blast radius." I went home that night and sat at my kitchen table for a long time.

I chose this specialization because the projects are interesting and the pay is better than residential or commercial. Both of those things are still true. But the liability calculation is different when your error margin is measured in potential casualties rather than change orders.

The gap between what the community needs and what the money allows. That's where the stress lives. I got into this work because I wanted architecture to mean something beyond aesthetics. My colleague Teo and I joined this nonprofit within six months of each other, both out of firms where we'd been designing luxury condos, both wanting to do work that felt connected to actual people. And it is connected. That's the problem. When you know the names of the families who will live in the building, cutting the budget feels personal in a way it never did on a market-rate project.

The one that still bothers me: a 40-unit affordable housing project in South LA. We'd been working with the neighborhood for months. Selma, the housing director, organized community meetings where residents told us what they needed. The number one request was a community room on the ground floor. A place for after-school programs, tenant meetings, a space that belonged to the building's residents. We designed it. It was in the plans through schematic design and into design development. Then the budget got cut 15% after a funding source fell through. Something had to go. The community room was the largest non-residential space in the building. Cutting it saved enough to keep the unit count intact.

Selma and I sat in her office for an hour trying to find another way. There wasn't one. We could cut finishes, reduce the lobby, shrink the bike storage. We did all of that. It still wasn't enough. The community room came out. I went to the next neighborhood meeting and explained why. A woman in the third row said, "So you asked us what we wanted and then took it away." She wasn't wrong. That was two years ago and I still think about it when I drive past the building.