Design's First Responsibility: The People Who Live With It

The owner approves a building once. Staff unlock its doors every morning. Maintenance crews keep its systems running. Tenants work under its lights, and neighbors pass it on the street. Those people deal with the result every day, often for decades.

That long view runs through our conversation with Bart Shaw, FAIA, principal and co-founder of Ibañez Shaw in Fort Worth. Shaw makes a direct financial case for good design: buildings cost money long after construction ends, and decisions made early determine much of what owners and occupants will pay later.

Money is only part of the argument. The same decisions affect how comfortably a building works, how difficult it is to maintain and how well it serves people who were never in the room when it was designed. For Shaw, that responsibility starts with the budget and reaches well beyond it.

Design starts with needs, not shapes

Shaw begins with what the client needs the building to do and what the project can afford. Form follows from those conversations.

The Northside Boys & Girls Club is a useful example. Its entrance had to provide security, give staff clear visibility and withstand constant use. It also had to welcome children and families.

Those requirements shaped the architecture. Concrete provided durability and security. Sightlines helped staff see the entrance. Daylight made the interior easier and more comfortable to use. Each choice solves a practical problem, and together they determine how the building feels.

Ibañez Shaw's Chroma project follows the same logic. The 5,600-square-foot Fort Worth workplace uses tilt-wall concrete, a glass enclosure that carries daylight into the building and custom fixtures and desks designed as part of the whole project. The AIA case study reports an estimated 100-year service life. Material, daylight, furniture, daily work and long-term durability were considered together. That coordination is part of the design.

The people who live with the building

The drawing set has an end date. The building does not.

Staff, tenants, maintenance crews and neighbors inherit decisions made during design and construction. A difficult detail becomes someone's recurring repair. Poor daylight shapes every working day. An inflexible room limits how the building can change. Materials selected only for first cost can become maintenance and replacement costs later.

Building performance is the daily experience of the architecture. It is also why coordination matters. The shell, interiors, fixtures, building systems and maintenance plan may be separate contracts, but they still have to work as one place. If they are designed independently, someone eventually has to resolve the conflicts. Too often, that work falls to the owner or the people operating the building.

Good design is a financial decision

Construction is the largest and most visible expense, but it is not the last one.

A building continues to produce costs through energy use, maintenance, repair, replacement and adaptation. Some inexpensive decisions remain inexpensive. Others move the expense into a later year and leave the owner with fewer options.

A poorly designed building may waste energy, age badly or resist changes in use. It can also make ordinary work harder for the people inside it. Those costs appear at different times and on different balance sheets, which is why a construction budget can miss them.

The first-cost spreadsheet is still important. Projects have financing limits, schedules and immediate business requirements. A developer planning to sell in five years faces a different calculation from an institution expecting to occupy a building for fifty.

That tradeoff is real. The answer is not to pretend every project can spend without limit. It is to discuss operating cost, maintenance and useful life early enough for them to affect the design.

Nick picked up that point during the conversation:

By the time systems, materials and scope are fixed, many of the most consequential decisions are already behind the team.

Discipline is how the money gets spent well

Shaw does not treat budget and schedule as reasons to stop designing. He uses them to narrow the field. “All of those constraints I love,” he says. “Now, instead of ten million materials, I'm looking at only the materials I can get in two weeks.”

That narrowing can produce practical ideas. If a project already needs a framed wall, changing the stud depth at one point can create a niche or shape the adjoining room without adding a separate decorative assembly.

In another project, a small clothing boutique could not afford a conventional custom screen. Wire hangers were inexpensive, available and connected directly to the business. Repeated across a frame, they became both the screen and part of the store's identity.

Neither example argues that less money automatically produces better architecture. A reduced budget removes options. A short schedule creates risk. Materials that cannot be purchased cannot be specified. Once the actual limits are known, however, the team can spend its effort on decisions that will still change the result.

That work benefits from keeping judgment close to the project. In a small practice, a principal can sit with the client, follow a detail into construction and see what happens when a decision meets the budget, the builder and the site.

Small firms do not have a monopoly on attention, and large firms are not inherently remote. The practical advantage is a shorter distance between the person making a decision and the people living with its consequences.

Coordination is part of the design

Ibañez Shaw carries its work from the building envelope into the interiors. Shaw described the firm's boundary in practical terms: if something is fixed to the building, they want to understand and design it.

That does not mean every project needs one firm to select every finish or draw every piece of furniture. It means the divisions between architecture, interiors, structure, systems and construction do not remove the need for coordination. They create more places where coordination has to occur.

A ceiling plane still has to meet the lighting. Millwork still has to accommodate outlets, equipment and clearances. Materials selected for appearance still have to be installed, cleaned and replaced. The client experiences one room, regardless of how many contracts produced it.

Separate specialists can produce excellent work. They also bring separate schedules, assumptions and priorities. Someone has to reconcile those decisions before they reach the field.

When that work happens early, it may look uneventful. When it does not, it reappears during construction as redesign, delay or compromise. Coordination is one of the ways design becomes buildable.

The same answer for every client is a warning

Architecture firms develop repeatable details and processes for good reasons. Repetition can control cost, reduce errors and make construction more predictable. It can also make the familiar answer easier to deliver than the right one.

Shaw asks why clients with different sites, needs and communities so often receive the same building. Architects know many ways to put a structure together, but a practice built around repeatable delivery naturally rewards familiar details, standard packages and forms that move efficiently through the office.

Efficiency is valuable. It becomes a problem when the solution is selected before the client, climate, site or city has been understood. A site-specific response does not require novelty for its own sake. It requires enough contact with the client and place for those conditions to change the answer.

That principle is central to how we think about Arcfluence's work as well. A project is not a product line. The plan should respond to the actual property, users, budget and market moment. If the proposed answer looks exactly like the last three projects, it is worth asking why.

The work has to become a place

A drawing is useful only if the team can turn it into a building that works. Paul described that standard near the end of the conversation:

The client brings knowledge no one else has: how the organization works, what the building needs to accomplish, where the budget is firm and which compromises would change the project too much. The architect turns that knowledge into coordinated decisions about space, materials, code, systems and construction. The builder brings another kind of expertise about sequence, cost and what will happen in the field.

Good work gives those perspectives room to change the design. The process is collaborative because no one at the table knows the whole project alone.

Much of that work is difficult to see in photographs. A code issue resolved during design leaves no scar on the finished building. Neither do the calls that prevented a material conflict, the drawing that clarified an assembly or the early decision that avoided a change order months later.

The finished building carries the result. The clearest measure of the design is whether the place serves the people who asked for it and the people who use it afterward.

That is also why these conversations matter. They let architects, builders, owners and operators talk about the decisions behind a building while keeping the real goal in view: a place that gets built and works well once people move in.

About Bart Shaw

Bart Shaw, FAIA, is a principal and co-founder of Ibañez Shaw in Fort Worth, Texas, and an adjunct faculty member at the University of Texas at Arlington. His work was recognized with elevation to the AIA College of Fellows in 2019.

Listen and explore

• The Arcfluence Podcast — more conversations with the people shaping the built environment.
• Ibañez Shaw — About
• AIA Small Project Award — Chroma
• More from Arcfluence