ARTICLE 15

Why “One Small Change” Is Part of the Design Process

There is a phrase architects hear all the time:

“Everything looks great. I just have one small change.”

Sometimes the change really is small.

Sometimes it opens the door to a much bigger conversation.

And that is not necessarily a bad thing.

Changing your mind, questioning an idea, testing another layout, or realizing that something does not feel right is a normal part of designing a building. In fact, one of the reasons architectural projects are divided into different phases is to create opportunities to explore ideas before they become expensive or difficult to change.

Good design is not about getting everything perfect on the first sketch.

It is about developing the project in the right order.

Why Architecture Has Different Design Phases

You may hear architects use terms like Schematic Design (SD), Design Development (DD), and Construction Documents (CD).

To someone outside the profession, those can sound like technical names for different sets of drawings.

They are really stages of decision-making.

Each phase is meant to answer a different set of questions and give the client an opportunity to understand the project more clearly before moving deeper into design, engineering, permitting, pricing, and construction.

Schematic Design: What Are We Actually Trying to Do?

Schematic Design is where the major ideas of the project begin to take shape.

This is where we look at things like:

It is also where we start asking the bigger question:

What are we actually trying to accomplish?

A client may come to me saying they need an addition.

After studying the house, we may find that reorganizing the existing floor plan solves the problem without adding square footage.

Or the opposite may happen. We may discover that trying to force everything into the existing footprint creates too many compromises, and an addition becomes the better long-term solution.

That is why Schematic Design is so valuable.

It gives us room to explore before we commit.

Sometimes the First Step Should Be Exploration

Not every client comes to an architect with a perfectly defined scope.

Actually, many do not.

You may know that your kitchen does not work.

You may know your house feels too small.

You may want to renovate a cabin, finish a basement, add a primary suite, or rework an awkward floor plan.

But you may not yet know exactly what the project needs to become.

That is where an exploratory or Schematic Design phase can be extremely useful.

Rather than immediately jumping into a full set of construction drawings, or committing to a large lump-sum architectural fee before the project is fully understood, we can first study the existing conditions, talk through priorities, explore different options, identify potential problems, and begin defining what the project really is.

For clients, seeing one large architectural fee at the very beginning can sometimes feel overwhelming, especially when there are still a lot of unknowns.

It can be difficult to commit to a significant number when you are still asking basic questions about what you want to build, what it may cost, whether an engineer will be needed, or even whether the project makes sense.

Breaking the process into phases can make that initial commitment more manageable while also giving everyone better information before determining the scope and fee for the next stage.

Instead of saying:

“Here is the fee for the entire project based on what we think might happen.”

We can first spend time understanding what the project actually is.

That can be better for both the client and the design team.

The Client Gets a Decision Point

One of the biggest advantages of an exploratory phase is that the client does not have to know every answer on day one.

The early design process can help determine:

That last point is important.

Sometimes the best result of an early design phase is confidence that the project should move forward.

Other times, the client may discover that the project is larger than expected, that another approach makes more sense, or that now is simply not the right time.

That is still valuable information.

Finding that out early is much better than finding it out after a significant amount of design, engineering, permitting, and documentation has already been completed.

Better Scope Usually Means Better Pricing

One of the hardest things to price accurately at the beginning of a project is something that has not really been defined yet.

If we do not know which walls are moving, how large the addition is, what structural work may be required, what level of finish is expected, or what consultants need to be involved, everyone is estimating based on assumptions.

The architect is estimating design effort.

The engineer is estimating their scope.

The contractor is estimating construction.

The client is trying to establish a budget.

The more clearly the project is defined, the better those conversations can become.

An exploratory or Schematic Design phase helps move the project from:

“We think we want to renovate this part of the house.”

to something more specific:

“We are renovating approximately this area, moving these walls, opening this portion of the structure, adding these spaces, and keeping these existing elements.”

That is information people can actually work with.

It does not guarantee that every number will be exact, but it gives the architect, consultants, contractor, and client a much better foundation for realistic conversations about cost and scope.

It Helps Determine Who Needs to Be Involved

Another advantage of developing the project in phases is that we begin to understand what additional expertise may actually be required.

Does a structural engineer need to evaluate an existing wall?

Will site work require a civil engineer?

Is there an existing septic system that may be affected?

Do we need a survey?

Are there zoning restrictions?

Will the local jurisdiction require specific documentation?

Are there unusual energy-code or building-code issues?

At the beginning, we may not know the answers to all of those questions.

And that is okay.

The early design process helps uncover them.

Instead of bringing multiple consultants into the project based on guesses, we can begin assembling the right team as the scope becomes clearer.

That can save time, reduce unnecessary work, and make consultant proposals more accurate.

Design Development: Turning the Idea Into a Building

Once the major direction is established, the project can move into Design Development.

This is where the design becomes more detailed.

Materials are considered more closely.

Windows and doors are refined.

Cabinetry and built-ins may begin to develop.

Structural systems are coordinated.

Mechanical, electrical, and plumbing requirements become clearer.

Exterior materials and assemblies are studied.

Important dimensions and relationships are resolved.

At this point, we are no longer asking only:

“What could this project be?”

We are beginning to answer:

“How is this actually going to work?”

Changes can absolutely still happen during Design Development.

That is part of design.

But as more pieces become coordinated, changes may begin affecting more parts of the project.

That is why resolving the major decisions during Schematic Design is so valuable.

Why Changes Become More Difficult Later

Changes are a normal and expected part of design.

The important distinction is when they happen.

During Schematic Design, we are intentionally exploring ideas.

We may move walls, test different layouts, change room sizes, reconsider an addition, compare several options, or decide that an idea we originally liked does not actually work.

That is exactly what the phase is for.

As the project progresses, however, those ideas begin to become interconnected.

A wall is no longer just a line on a floor plan.

It may now relate to:

So moving that line later in the project may require changes in several different places.

It may also mean revisiting ideas that were already studied, discussed, and resolved earlier in the process.

That additional work is not always obvious when looking at the final drawing.

A client may see a wall move two feet and understandably think:

“Didn't we just move one line?”

But behind that one line may be several drawings, details, dimensions, systems, and consultant documents that also need to be reviewed and coordinated.

The amount of work required to make a change is not always proportional to how large that change looks on the page.

One Change Can Touch a Lot of Things

Take something as simple as moving a bathroom wall.

Depending on the project, that might affect:

The point is not that the change should not be made.

Sometimes changing it is absolutely the right decision.

The important thing is understanding what the change affects before making it.

Sometimes the answer really is:

“No problem. That is an easy change.”

Other times the answer may be:

“Absolutely. We can look at that, but here are the other things we should consider before we make the decision.”

Both are completely reasonable outcomes.

Why Phase Approvals Matter

This is another reason projects are divided into phases.

At the end of Schematic Design, the goal is to agree on the major direction of the project before spending time developing all of the details.

At the end of Design Development, the goal is to have the major materials, systems, dimensions, and design decisions resolved before producing the final construction documents.

These milestones create natural opportunities for the client and architect to stop, review the project, ask questions, and make sure everyone is comfortable moving forward.

Changes can still happen afterward.

But once a phase has been reviewed and approved, going back and significantly changing previously resolved work may require additional design and coordination.

That is not a penalty for changing your mind.

It simply recognizes that some of the work may need to be done again.

Small Changes Can Add Up

Another challenge is that projects rarely change because of one dramatic revision.

More often, there are many small decisions over time.

Move this wall.

Make this window larger.

Change the kitchen layout.

Add another closet.

Move the bathroom.

Extend the addition another few feet.

Change the ceiling.

Move the door.

Individually, each request may seem relatively minor.

Collectively, however, they can substantially change the original scope of the project.

It can also become difficult to track how much additional work has occurred when revisions happen little by little over a long period of time.

That is another benefit of having clearly defined phases and decision points.

They help everyone understand:

Where did we start?

What has been approved?

What has changed?

What still needs to be resolved?

And most importantly:

What do those changes mean for design effort, consultant coordination, construction cost, and schedule?

That transparency benefits everyone.

Construction Documents: Communicating How It Gets Built

Construction Documents are where the developed design is translated into the drawings and information used for permitting, pricing, and construction.

Plans, elevations, sections, details, dimensions, notes, and consultant information are coordinated into a much more complete package.

By this stage, the project should have a strong foundation.

The client understands what is being built.

The design team understands the scope.

Consultants understand what they are responsible for.

The contractor has much better information for pricing and construction.

That does not mean changes suddenly become forbidden.

Projects evolve.

But the later a significant change occurs, the greater the chance that previously completed work needs to be revisited.

That might mean updating architectural drawings, coordinating with an engineer, revising permit documents, changing something already priced by a contractor, reordering materials, or modifying work that has already begun in the field.

At that point, the consequences can go beyond architectural fees.

They can begin affecting construction cost and schedule as well.

The Goal Is Flexibility Without Surprises

I do not want clients to feel like they cannot change something once we start designing.

Quite the opposite.

If there is a better solution, I want to find it.

If something does not feel right, I want to know.

If seeing the drawings causes you to rethink an idea, that is valuable information.

The goal is not to prevent changes.

The goal is to create a process where those changes can be explored at the right time and with the right information.

That is one of the biggest benefits of spending enough time during Schematic Design to explore the project thoroughly.

It is much easier to test three ideas early, decide that two of them do not work, and move forward confidently with the third than it is to fully develop one solution and discover much later that we should have taken a different direction.

Early exploration gives us flexibility. Later coordination gives us certainty.

Both are important.

A More Comfortable Way to Begin

For some projects, especially renovations, additions, feasibility studies, or projects where the scope is still evolving, beginning with an exploratory Schematic Design phase can be a much more comfortable way to start.

We can look at the existing building, review the available information, discuss what is working and what is not, develop possible directions, identify major constraints, and begin defining the scope.

Then, rather than committing to the entire architectural process before fully understanding the project, the client has an opportunity to evaluate what has been learned and decide how they want to proceed.

By that point, I can usually provide a much clearer understanding of:

That can lead to more accurate fees, more realistic construction expectations, and fewer surprises for everyone involved.

So About That “One Small Change…”

When a client says:

“Everything looks great. I just have one small change.”

The answer should not be frustration.

It should be curiosity.

Absolutely. Let's look at it.

Maybe it takes five minutes.

Maybe it reveals a better solution.

Maybe it changes the direction of the project.

That is what the design process is there for.

The earlier we understand the goals, explore the possibilities, and define the scope, the easier it becomes to make good decisions as the project moves forward.

Because good architecture is not about avoiding change.

It is about understanding the consequences of a decision before that decision becomes expensive.

And sometimes the best thing an architect can do at the beginning of a project is not rush to draw the final answer.

It is to help the client figure out what the right project actually is.



Michael Demetrios Frudakis, AIA, NCARB
 Principal Architect