On complex commercial projects, the question isn’t only who owns a decision. It’s who will inherit its consequences.
A project can have experienced people making sound decisions and still begin to drift. A scope reduction affects more than the budget. A program change affects more than the floor plan. A product substitution can solve an availability problem while creating a different installation, maintenance, or design consideration.
None of those decisions are automatically wrong, but none of them are isolated, either.
That’s something I pay close attention to when we’re brought into a commercial project. I’m not only asking whether a decision makes sense on its own. I’m asking: What else does this decision change?
A team can agree on the project and still be solving for different outcomes
Experienced owners and asset managers generally know what they’re spending money on. The more interesting question is what they expect that investment to accomplish.
Take an exterior repaint. If the objective is maintenance, preserving the existing visual direction may be completely appropriate. If the same repaint is part of repositioning the asset, simply replacing what is there may miss an opportunity the investment was intended to address.
Everyone can agree that the property needs to be painted, what the budget is, and when the work needs to happen while still working toward different definitions of success. The disagreement may eventually show up as a debate over color, but color isn’t really the issue. The unresolved question is what job the investment is supposed to do.
The point isn’t that every project needs a larger ambition. In the current market, ownership and asset management teams are making hard decisions about where to spend now and what has to wait. Sometimes maintenance is exactly the right decision. Sometimes the scope needs to get smaller.
Even when everyone agrees on the objective, they’re usually looking at the project through different responsibilities. Maintenance, property management, and ownership will each inherit different consequences from the decisions being made. When third-party management is also facilitating between the onsite team and ownership, keeping those priorities connected can become even more challenging.
The goal isn’t to eliminate those different perspectives. It’s to understand them well enough that solving for one doesn’t unintentionally create a problem for another.
Decision authority and decision consequences don’t always sit in the same place
Experienced project teams generally have clear approval structures. What I pay attention to is what happens after a decision is made.
Who has authority to approve this decision, and who will inherit its consequences?
Those are not always the same person. That doesn’t mean more people need to be involved in every decision. It means recognizing when a decision crosses into someone else’s work or changes the options they will have later.
We saw this on a university project in the Midwest where we were not brought in at the beginning. Decorative chandeliers had been planned in the same ceiling that needed to accommodate an in-ceiling projector and the requirements of the audiovisual system.
Ceilings get crowded quickly. Lighting and AV aren’t the only considerations; fire suppression, alarms, and other building systems all need to be coordinated within the same space.
In this case, the chandeliers ultimately had to be removed because the room couldn’t function as needed with them in place. The chandelier decision made sense on its own. The problem became apparent when its consequences reached another discipline.
Experience across design and implementation helps us recognize which decisions are likely to travel further into a project than they initially appear. I want those connections identified while the team still has room to respond.
Some constraints can’t change, and the design still has to account for them
Commercial projects come with fixed conditions, and experience helps us incorporate them without allowing the finished space to feel unresolved.
We see this frequently on podium projects, where large columns carrying structural or building-system requirements can run directly through the spaces we’re designing. The columns aren’t moving, but they still affect how we plan circulation, furniture, and the room around them.
The design problem isn’t how to eliminate the constraint. It’s how to incorporate it intentionally.
Sometimes that means planning around it. Other times, it means integrating the condition into the design so it becomes less pronounced and the space feels more seamless.
The fixed condition still influences the design. It just doesn’t have to feel like something the design failed to anticipate.
When the project changes, look at what changes with it
Budgets tighten, scopes shift, products become unavailable, and field conditions surface. The adjustment itself isn’t the only consideration. What matters is what that adjustment changes elsewhere in the project.
If the scope is reduced, for example, the remaining work may need to be phased differently, or procurement and installation may change. Decisions made for one coordinated project may no longer make sense when the work is separated.
In the current market, reducing scope or moving part of the work into a later phase may be exactly what the economic reality requires. I want the team making that decision with a clear view of what it means for the rest of the project.
Product availability creates a similar challenge. If a specified product isn’t available within the required timeline, the goal isn’t to casually change the design. We need to understand what the original selection was meant to accomplish and find an appropriate alternative that preserves the larger design intent and project requirements.
Execution is where the design has to hold up
Once a commercial construction-document set is issued, the design direction should be established. Construction isn’t the time to continually reinvent it, but questions don’t stop.
Clarifications come up. Field conditions can reveal something unexpected. A proposed substitution or field decision may affect another part of the space. When that happens, someone needs to understand what the decision does to the project as a whole.
That’s a big reason Color Works Design stays involved through implementation and participates in OAC meetings. Our role doesn’t stop with developing the design. We stay engaged to help represent how the total space is supposed to function and come together when questions arise during execution.
We recently had a situation where a fireplace had been scheduled as part of the design, but a proposed field change would have projected it significantly farther into the room.
The general contractor reached out before proceeding. Looking only at the fireplace, the change might have appeared workable. Looking at the entire room, it created a line-of-sight problem. We went back to the table with the team and worked through a solution that reduced the projection and allowed the fireplace to work within the larger space.
Staying involved through construction doesn’t mean continually redesigning the project. It means being there when an individual decision affects something larger than itself.
Different perspectives should make the project stronger
I don’t expect everyone on a project team to see a decision the same way. In fact, I count on the people around the table to bring different expertise to it. The value is in knowing when those perspectives affect the decision in front of us without losing sight of what the project needs to accomplish.
Good coordination doesn’t mean adding more voices to every decision or making a complicated project simple. It means recognizing when one decision crosses into somebody else’s work and getting the right people around the table before the consequence shows up somewhere else.
Sometimes a perfectly reasonable decision for one part of the project creates a problem for the next. The earlier we see that connection, the more room we have to respond.
