Architect, Translated: What We Mean When We Say “Programming”

Every profession has its own vocabulary. Architects are no exception.

Sometimes we use words that sound highly technical. Other times, we use completely ordinary words in ways that make perfect sense to us…and potentially no sense at all to everyone else.

So, welcome to Architect, Translated, a recurring series where we take some of the words and phrases you might hear during an architecture project and explain what we actually mean when we say them.

First up: programming. (And no, we’re not writing code.)

What Does “Programming” Mean in Architecture?

In architecture, programming is the process of figuring out what a space needs to do before we start deciding exactly what it should look like.

It’s where we ask questions like:

• Who will use the space?

• What activities need to happen there?

• How many people need to fit comfortably?

• Which spaces should be close to one another?

• What equipment, storage, technology, or infrastructure will be required?

• How might those needs change in the future?

In other words, programming helps define the problem before we start designing the solution.

Why Do Architects Use the Term?

Because a building is more than a collection of rooms. A dental office, restaurant, retail space, corporate office, and custom home all have very different requirements—even if they happen to occupy buildings of similar size.

Programming gives the architect a clearer understanding of how the people inside the building will actually use it.

Before drawing walls, we want to understand the relationships between spaces, the flow of people through them, operational needs, priorities, constraints, and opportunities. That information becomes the foundation for the design work that follows.

Why Does Programming Matter to Your Project?

Good programming can prevent expensive problems later.

Imagine designing an office only to discover that the conference rooms are constantly booked, storage was underestimated, or employees have to cross the entire building every time they need access to a shared resource.

Or imagine opening a restaurant and realizing that the path between the kitchen and dining room creates an unnecessary bottleneck during every dinner rush.

Those might look like design problems. But often, they started much earlier as programming problems.

Taking time up front to understand how a space needs to function can lead to a design that works better on day one—and continues working as your needs evolve.

A Quick Example

Let’s say a growing company is planning a new office. The initial request might sound simple:

“We need space for 40 employees.”

Programming digs deeper.

Are all 40 employees in the office every day? Do they work individually or collaboratively? How often do clients visit? How many meetings happen simultaneously? Does the company expect to grow to 60 employees within five years? Are there teams that need to sit near one another? Is privacy important? What about storage, break areas, wellness rooms, technology, or flexible workspaces?

Suddenly, “space for 40 employees” becomes a much clearer picture of what the building actually needs to accomplish.

And that gives us something much more useful to design around.

Translation Complete

So, when you hear an architect talk about programming, think: figuring out what the space needs to do before deciding what it should look like.

It may not be the flashiest part of architecture, but it’s one of the steps that helps turn a good-looking building into a space that genuinely works for the people using it. And if your architect starts talking about programming and you momentarily wonder when someone learned Python, now you know.

Have a project in mind? Get in touch. Bring us your goals, challenges, wish list, and even the things you haven’t quite figured out yet. Helping you turn all of that into a space that works is exactly where the process begins.