Essays

I spent a long time solving the wrong problem.

For months, I kept returning to the same architectural renderings, convinced they could be better. I adjusted the light. Changed the lens. Reworked the materials. Replaced the vegetation. Sometimes the changes were subtle, sometimes substantial, but the pattern was always the same. The images became more polished, more convincing, more technically accomplished. They also became, in a way that was difficult to explain, less satisfying. At first I assumed I simply hadn't found the right combination of decisions. Better software. Better prompts. Better editing. Better rendering. Eventually it occurred to me that none of those things were actually the problem.

I wasn't trying to make better renderings. I was trying to make the rendering disappear.

That realization has stayed with me because it extends well beyond architecture. The purpose of a rendering isn't to be admired. It's to help someone understand a building that doesn't yet exist. Every decision that reminds the viewer they're looking at a rendering—no matter how impressive that decision may be—creates a small amount of distance between the image and the architecture it is trying to communicate. The irony is that many of the qualities we associate with realism have the opposite effect. Dramatic skies. Perfect reflections. Cinematic lighting. Lush vegetation. They can all produce remarkable images while quietly asking us to notice the image itself. The architecture begins competing with its own representation.

Once I recognized that, my process changed. Instead of asking how to make an image stronger, I started asking what could be removed without diminishing the architecture. Better vegetation wasn't necessarily more vegetation. Better lighting wasn't necessarily more dramatic lighting. More realism wasn't necessarily more truth. The work became less about adding and more about noticing. Noticing where the image had started to speak louder than the building.

I don't think this is unique to renderings. The same thing happens in writing. A beautifully constructed sentence can draw attention away from an ordinary idea. It happens in technology, where thoughtful interaction is often mistaken for visual complexity. It happens in architecture itself, where a clever gesture can become more memorable than the spaces it was intended to serve. The temptation is always the same. To improve the medium rather than clarify the message.

I've come to think that learning to represent something well begins with learning to see it clearly. That sounds obvious, but I don't think it is. Seeing isn't simply observing what's there. It's learning to distinguish between what belongs to the work and what belongs to our own enthusiasm for it. Those are not always the same thing. Every act of representation contains interpretation. A drawing chooses what to include. A photograph chooses a moment. A rendering chooses a season, a point of view, and a quality of light. None of those decisions are neutral, nor should they be. The question is whether they deepen understanding or merely intensify experience.

For a long time I thought realism was the goal. Now I'm not so sure. I'm increasingly convinced that the best representations are not the ones that feel the most real. They're the ones that leave the fewest obstacles between the work and the person trying to understand it. I suspect that's why I've always been drawn to work that feels inevitable. Not because it appears effortless. Usually the opposite is true. The effort has simply been absorbed so completely into the work that all you're left with is the quiet feeling that nothing else would have made more sense.

It's a small distinction.

But I think it's the one I've been trying to see all along.

One of the most valuable things I've learned in design is that the first problem is rarely the real one.

That sounds obvious, but I've found it surprisingly difficult to practice. When something doesn't feel right, our instinct is usually to begin fixing it. We adjust, refine, optimize, and iterate. We assume the work needs a better answer. Often it needs a better question.

I've noticed this pattern often enough that I no longer trust my first diagnosis. A floor plan feels awkward. A rendering feels artificial. An email feels forced. A website feels cluttered. My first instinct is to start making improvements. Occasionally that works. More often, the work resists every improvement I make. The strange thing is that this resistance usually isn't telling me that I'm incapable of solving the problem. It's telling me that I haven't identified it yet. I've started to pay attention to that feeling. Not frustration itself, but the particular kind of frustration that comes from making something objectively better while somehow making it no more satisfying. That's become one of my most useful signals. It usually means I'm solving the wrong problem.

I've learned to stop asking, "How do I improve this?" Instead I ask, "What am I assuming is true?" That question has changed the direction of more projects than any software, book, or technique. Sometimes the answer is embarrassingly simple. A drawing isn't unclear because it lacks information. It lacks hierarchy. A presentation isn't confusing because there are too many ideas. There isn't a single idea holding them together. A building isn't unsuccessful because one room doesn't work. The circulation never established a clear rhythm in the first place. The visible problem is often just the place where the deeper one finally becomes impossible to ignore.

Design has a way of rewarding activity. There's always another option to explore, another material to test, another image to produce. Understanding is quieter work. It often looks like sitting with a problem longer than feels productive. Not because delay is virtuous, but because premature certainty can be expensive. The temptation is to confuse momentum with progress. I've done it many times. A project begins to move, decisions accumulate, and before long the work has acquired a kind of internal logic. At that point it becomes surprisingly difficult to ask whether the original premise was correct. The further we travel down the wrong path, the more convincing that path begins to feel.

I don't think experience eliminates this problem. If anything, experience makes it more dangerous. The more fluent we become, the faster we can produce answers. That makes it even more important to protect the slower habit of questioning the question itself. I've begun to think that judgment is less about having better answers than about becoming suspicious of easy ones. Not cynical. Not indecisive. Simply willing to believe that the first explanation may only be the most visible one.

This has changed the way I think about design, but it has also changed the way I think about people. Clients rarely arrive with architectural problems. They arrive with stories, frustrations, ambitions, and constraints. The architecture emerges from listening carefully enough to discover the question beneath the one that was first asked. The same is true in everyday conversations. People often tell us what they think they need. Listening is the work of discovering what they're really trying to say. I've come to believe that this is where good design actually begins. Not with creativity. Not with expertise. With attention. Attention is what allows us to notice when something feels unresolved before we know why. It's what gives us permission to pause before reaching for another solution. And it's what gradually separates refinement from understanding.

I still solve the wrong problem more often than I'd like. The difference is that I no longer see that moment as failure. I've started to see it as the beginning of the real work.

One of the easiest mistakes to make in design is assuming that more work will produce better work.

Sometimes it does. Often it simply produces more work.

I've spent enough time revisiting projects to recognize a particular moment that seems to appear in almost every creative process. The work has reached a point where every change is technically an improvement. A rendering becomes more detailed. A drawing becomes more complete. A sentence becomes more polished. Yet somehow the work becomes less itself. For a long time I mistook this for fatigue. I assumed I had simply spent too many hours looking at the same thing. Now I think something else is happening.

Every project has a center of gravity. As long as each decision strengthens that center, the work becomes clearer. Eventually, though, the improvements begin competing with one another. Individual decisions may become better while the whole quietly becomes less coherent. I've noticed this in buildings. A carefully considered detail is added because it's beautiful. Another because it's useful. A third because it solves a genuine problem. None of the decisions are wrong. Together they begin asking the building to become something it was never trying to be. The same thing happens in writing. A sentence becomes more elegant. An example becomes more complete. A paragraph becomes more persuasive. Somewhere along the way, clarity quietly gives way to explanation.

I've come to believe that restraint isn't the opposite of ambition. It's one of its highest forms. Restraint asks us to trust that the essential idea is already strong enough to carry the work. That doesn't mean stopping early. It means recognizing the moment when additional effort is no longer serving the original intention.

I've realized that this is one reason I admire work that feels inevitable. It rarely feels incomplete. Just as importantly, it rarely feels over-resolved. Nothing appears missing. Nothing appears anxious to prove itself. The work simply occupies the amount of space it needs.

I don't think experience makes this moment easier to recognize. If anything, experience expands the number of things we're capable of adding. Judgment becomes less about knowing what can be done than about knowing what no longer needs to be done. That has changed the way I finish projects. I still work hard. I still revise. I still look for better solutions. But I'm increasingly suspicious of changes that improve one part of the work while asking the whole to become louder. I've started to think that finishing isn't the moment when there's nothing left to add. It's the moment when there's nothing left that wants to be added. The difference is small. But I think it's where much of design lives.

I've never been particularly interested in convincing people.

Not because persuasion isn't important, but because I've found that the most meaningful progress usually happens before anyone begins arguing for a solution. It begins with listening.

When I was younger, I thought listening meant collecting information. Clients described what they wanted. Consultants explained constraints. Contractors pointed out problems. My job was to absorb as much of it as possible before deciding what to do. I still think information matters. I just don't think that's what listening is. Over time I've come to realize that people rarely arrive with fully formed questions. They arrive with observations, frustrations, ambitions, habits, and assumptions. Sometimes they describe a solution when what they're really expressing is a concern. Sometimes they ask for certainty when what they actually need is confidence. Sometimes they spend half an hour explaining a problem that was revealed in the first five minutes. Listening isn't waiting for someone to finish talking. It's paying attention to what remains consistent beneath the words.

I've found that the same is true of places. A site doesn't tell you what to build. A building doesn't tell you how it should change. Neither speaks in that way. But both contain patterns that become easier to recognize the longer you're willing to observe them. Light falls in certain places. People develop habits. Paths emerge. Rooms acquire purposes they were never designed for. Good design rarely begins by imposing order. More often, it begins by recognizing the order that's already there.

I've noticed that the strongest projects I've worked on weren't driven by the most forceful ideas. They were driven by the clearest understanding. Once the underlying question became visible, many decisions that had seemed difficult began to feel surprisingly straightforward. Materials, proportions, circulation, even details started reinforcing one another instead of competing for attention. The work became quieter. Not because less was happening. Because less needed to be argued for.

I've started to think that this is one reason thoughtful work often feels calm. It isn't calm because it's minimal. It's calm because it no longer spends energy defending itself. The decisions support one another. They belong to the same conversation. I don't think listening guarantees good work. It certainly doesn't eliminate difficult decisions. But it changes the role of the designer. Instead of trying to invent the strongest idea, we're trying to recognize the most truthful one. That distinction has become increasingly important to me. It asks for curiosity before confidence. Attention before expression. Understanding before authorship.

I'm still learning how to do that. Some projects resist it. Some conversations move too quickly. Sometimes I mistake confidence for clarity. But whenever the work begins to feel forced, I've learned to ask myself a simple question. What haven't I listened to yet? More often than not, that's where the project begins again.

The longer I work, the less interested I become in being right.

That may sound like a strange thing to say for someone whose job involves making decisions every day. But I've come to realize that good work rarely depends on certainty. More often, it depends on responsibility. Responsibility for understanding the problem before proposing a solution. Responsibility for noticing what others have overlooked. Responsibility for leaving the work in a better state than I found it.

I've started to think that this is the quiet obligation shared by every designer. Not to produce something remarkable, but to care enough that the final result feels considered. That care isn't measured by the number of hours invested or the complexity of the process behind it. It's measured by whether the work reflects genuine attention.

I've noticed that people often talk about quality as though it's something added at the end of a project. A final round of edits. A better material. A cleaner rendering. A more polished presentation. My experience has been almost the opposite. Quality isn't something that's applied. It's something that's preserved. Every decision either protects the central idea or slowly pulls the work away from it.

That has changed the way I think about effort. I no longer assume that harder work automatically produces better results. Sometimes the most responsible decision is to keep searching. Sometimes it's to remove something you've grown attached to. Sometimes it's simply to leave a good idea alone. The work doesn't ask for the same thing every time. Our responsibility is to recognize what it needs rather than insist on what we want to give it.

I think that's why I've become increasingly skeptical of the idea that good design comes from talent alone. Talent may shape how quickly someone sees an opportunity. It doesn't determine whether they care enough to follow it all the way through. Care is quieter than talent. It's less visible, less celebrated, and often far more consequential.

I'm still learning what responsibility looks like in practice. Every project presents new constraints, new people, and new questions. Every project reminds me how much I still don't know. But I've found that uncertainty becomes much less intimidating once I stop treating it as a weakness. It's simply part of taking the work seriously.

When I look back at the projects that continue to matter to me, I rarely remember the moments when I felt most confident. I remember the moments when I slowed down long enough to understand what the work was asking of me. Those moments almost never made the project easier. They simply made it more honest.

I don't know if thoughtful work can ever be guaranteed.

I do think it can be deserved.

And increasingly, that feels like the standard worth pursuing.