ARTICLE 27

Knowing When to Walk Away From a Design

Architects are taught to keep pushing.

Keep sketching. Keep revising. Keep looking for another solution. Move the wall. Change the roof. Rotate the plan. Try another material. Draw it again.

That persistence matters.

A lot of good design only happens because someone refuses to settle for the first answer.

But there is another side to that process that does not get talked about as much.

Sometimes you have to know when to walk away.

I had already picked out a real site for a conceptual residential exercise. A wooded, sloped property in Montana with a creek running through it and mountain views beyond.

I wanted to see what the site itself could generate rather than starting with a house and trying to make it fit afterward.

That led to a fairly simple idea:

ANCHOR / CUT / OBSERVE

The lower portion would feel heavy and almost geological.

Stone and concrete would anchor the house into the hillside.

The arrival would cut into the terrain, creating a protected and compressed entrance.

Then the upper portion would become lighter.

Timber, glass, and a dark angular roof would project outward toward the creek and mountains. Almost like the building was watching the landscape.

That became The Prow.

And I still think there is something good in it.

That is usually how these things start.

You are excited. The idea feels fresh. You can see where it might go before you have even figured out how to get there. You start sketching, testing things, building the concept out, and for a while it is fun.

Then somewhere along the way the relationship changes.

The thing you were excited to work on starts fighting you.

You move one piece and another stops working. You solve one problem and create two more. You start opening the drawing less like you are excited to design and more like you are preparing for another round with your mortal enemy.

I am exaggerating a little, but not that much.

That shift is usually telling you something.

The problem started when I kept going.

There is a point in almost every design where you stop discovering something and start trying to force it.

You tell yourself you just need one more iteration.

One more floor plan.

One more rendering.

One more detail.

One more adjustment to make everything line up with the original concept.

Sometimes that works.

Sometimes it does not.

At a certain point with The Prow, I could feel myself spending more time trying to make every part of the project justify the original idea than actually improving the architecture.

That distinction matters.

Persistence and progress are not the same thing.

You can spend another ten hours on a design and technically make it more resolved while somehow making the original idea less clear.

There is also a point where you can simply overwork a design.

You redraw it.

Rework it.

Pull it apart.

Put it back together.

Convince yourself the next iteration is going to unlock whatever you have been missing.

Then eventually you look at where you ended up and realize you are almost right back where you began.

That hurts.

I have been down this road more times than I can count.

Part of the problem is that you do not want to give up.

You know some of the best solutions only show up because you kept pushing when it would have been easier to stop. So you convince yourself this is just another one of those moments.

Keep working.

Keep turning it over.

There has to be something on the other side.

And sometimes there is.

But sometimes there is not.

That is what makes this difficult.

There is no alarm that goes off telling you that a design has reached the point of diminishing returns.

You have to develop the judgment to recognize when persistence is still producing something and when you are simply refusing to let go.

I have gotten that wrong before.

I will probably get it wrong again.

Sometimes you take the wrong path.

Sometimes you push a good idea too far.

Sometimes you spend days trying to solve something only to realize the first sketch understood the problem better than the tenth.

You open an older drawing and realize there was something immediate about it that the developed version has lost.

Maybe the plan became too complicated.

Maybe the roof is working too hard.

Maybe every decision now requires another explanation.

One move creates two new problems, and those two solutions create four more.

Eventually you are not designing anymore.

You are negotiating with the thing.

And sometimes walking away does not mean quitting.

Sometimes you just need to step away.

Work on something else.

Come back tomorrow.

Come back next week.

Give yourself enough distance to look at the problem again with fresh eyes.

When you are buried in a design for too long, it becomes difficult to see it clearly. You know every decision, every problem, every version that came before it. Sometimes you are simply too close.

Then you come back later and something changes.

Maybe the answer suddenly seems obvious.

Maybe you realize the original idea was right.

Maybe you see that one move needs to disappear.

Maybe the entire thing needs to change.

Or maybe you come back and realize you do not need to go back at all.

Distance can be part of the design process too.

The difficult part is knowing whether you need a break or whether the design has already given you everything it has to give.

Because once you have put enough time into something, stopping can feel like admitting defeat.

There is always that voice saying:

I have already spent this long on it. I might as well finish it.

But architecture has its own version of sunk cost.

Time invested does not automatically make an idea worth pursuing.

There is a difference between giving up and recognizing that a design has stopped teaching you anything.

Sometimes the best decision is to put the pencil down.

That does not mean the design was a failure.

In fact, I think that is one of the most useful parts of conceptual work.

Not every design exercise needs to become a finished building.

Sometimes the exercise itself is the product.

You test a relationship between materials.

You explore a difficult site condition.

You try a structural idea.

You work through how someone enters a building.

You discover a roof geometry you had never considered before.

You learn what works.

You learn what does not.

And then all of it goes into the bag of tricks.

That bag gets bigger over the course of a career.

You may never build the project that originally produced the idea, but five years later you can be standing on a completely different site and suddenly remember something from it.

Maybe it is the way a concrete wall turned into a hillside.

Maybe it is the way a room projected toward a view.

Maybe it is a deep timber soffit.

Maybe it is a relationship between stone and glass.

Maybe it is just a small detail you drew once and forgot about.

Then suddenly it is exactly what another project needs.

That is one of the things I love about architecture.

Ideas do not really disappear.

They get recycled, modified, combined, rejected, rediscovered, and eventually become part of how you think.

A design that never gets built can still influence a building years later.

The Prow may never become a house.

That is fine.

The carved entry may show up somewhere else.

The relationship between the heavy base and lighter upper volume may come back on another hillside project.

The projecting roof might eventually become more restrained and find a better home.

Even the parts that did not work taught me something.

That is enough.

Professional architecture obviously requires resolution.

Buildings have to stand up.

Water has to stay outside.

Doors have to work.

Codes have to be met.

Drawings eventually have to become instructions that someone can actually build from.

But conceptual design has a different job.

Its job is to ask questions.

What if the building did this?

What if we approached the site from here?

What if the heavy part of the house belonged to the earth and the light part reached outward?

What if the view determined the geometry?

You do not always need to answer every question.

Sometimes you only need to ask the right one.

And I think this is becoming more important as our design tools become capable of producing endless variations.

We can make another image.

Then another.

Then another.

We can change the roof again.

Move the wall again.

Try another material.

Generate another option.

There is almost no natural stopping point anymore.

That does not necessarily make the design better.

More output does not mean more design.

Sometimes you can keep polishing an idea long after the useful thinking has stopped.

I have to remind myself of that too.

Design Is a Muscle

I think design works a lot like a muscle.

You have to use it.

You have to sketch, think, test ideas, make things, question things, and keep putting yourself through the process.

Just like going to the gym, not every workout is going to be great.

Some days you feel strong.

Some days everything clicks.

Other days the work is terrible.

You cannot solve the plan.

The proportions feel wrong.

The idea that looked great in your head does not survive once you put it on paper.

That is fine.

The point is not to produce a masterpiece every time you sit down to design.

The point is consistency.

You keep showing up.

You keep exercising that part of your brain.

You keep training your eye.

Your judgment.

Your understanding of proportion, space, structure, material, light, and the thousand relationships that make architecture work.

You also train your ability to recognize when something simply is not working.

The gym is the same way.

You do not judge your entire physical progress by one bad workout.

The mind should be no different.

One bad design does not make you a bad designer.

One failed study does not erase everything you learned doing it.

Some days are just bad workouts.

But if you keep showing up, eventually you get stronger.

Your instincts get better.

Your eye gets sharper.

Your bag of tricks gets bigger.

And maybe that is another reason it is okay to walk away from a design.

You got the workout.

You learned something.

Come back tomorrow and design again.

Maybe that is one of the differences between drawing and designing.

A drawing can always be changed.

A design requires judgment.

And sometimes judgment means admitting that the original idea was stronger than where the process eventually took it.

That does not erase the work.

It just changes what the work becomes.

Research.

A reference.

A lesson.

Another tool.

Another move to pull out of the bag somewhere down the road.

That has value too.

Sometimes the most productive thing you can do with a design is keep pushing.

Sometimes you need to step away and come back with fresh eyes.

And sometimes the most productive thing you can do is walk away.

Michael Demetrios Frudakis, AIA, NCARB
Principal Architect