How Change Actually Happens on Projects

Across the AEC industry, conversations around healthier materials and product transparency have become increasingly common. Teams are asking more questions about ingredient disclosures, manufacturing practices, carbon impact, and the relationship between materials, human health, and the broader environment.

That shift matters.

There is growing recognition that the products specified on projects are not neutral decisions. They shape occupant experience, environmental impact, supply chains, and long-term building performance. More teams now understand why transparency matters and why frameworks like the AIA’s Materials Action Plan (MAP) are becoming part of the conversation.

So why does implementation still feel difficult?

The answer usually has less to do with philosophy than process.

Even when teams agree on the direction, integrating new requirements into established project workflows introduces friction. And in complex project environments, friction is never theoretical.

Why Good Ideas Can Feel Difficult to Implement

When teams resist a new requirement, it’s easy to interpret that response as a lack of buy-in. More often, it’s a reaction to disruption inside an established system.

Project teams rely on repetition for a reason. Schedules are compressed, responsibilities are clearly defined, and risk is managed through familiar workflows teams know how to execute under pressure.

A new requirement changes that rhythm.

It introduces new decisions, new coordination challenges, and unfamiliar forms of uncertainty. From the outside, that can look like hesitation. Inside the project system, it’s often a rational response to risk.

The industry has good reasons to move carefully. A misstep affects budgets, schedules, deliverables, and people’s livelihoods.

If we want different outcomes, the process itself has to change. And meaningful process change rarely feels comfortable at the beginning.

Projects Are Larger Than Any One Person

We also tend to overestimate the role of individual buy-in in determining whether change succeeds.

Individuals absolutely influence pace and direction. They raise legitimate concerns, identify risk, and shape decision-making in important ways. But people do not evaluate change from a neutral position. We all interpret new ideas through the lens of prior experience, existing responsibilities, and the systems we already trust.

When a new approach introduces uncertainty, the instinct to protect what feels proven and familiar is understandable. It is also one of the reasons change can feel slower than the logic behind it might suggest.

When goals are clear and the broader system is aligned, teams find a way forward. Responsibilities become clearer. Coordination improves. What initially felt disruptive becomes integrated into the normal rhythm of project delivery.

The work doesn’t necessarily become simpler. It becomes more familiar.

The Work Changes the Conversation

One of the most consistent patterns we see on projects is that trust rarely arrives before the work begins. It develops through participation.

Teams don’t need complete certainty to move forward. They need enough clarity to take the next step.

Early in the process, people tend to revisit the same concerns as they try to fit unfamiliar requirements into systems they already trust. That isn’t failure. It’s part of adaptation. But then, gradually, the friction begins to change.

That shift is usually subtle. The same concerns that dominated the beginning of the project simply stop surfacing with the same intensity as everyone grows more familiar with the process. Teams move through coordination meetings, submittals, field conditions, and problem-solving together. With time and repetition, the process stops feeling foreign.

Teams don’t become comfortable before they start; they become comfortable because they started.

The Goal Is Forward Movement, Not Certainty

The goal isn’t to resolve every unknown before starting. It’s to create the conditions that allow teams to move forward, adapt, and improve through the work itself. For teams navigating evolving expectations around materials, performance, and transparency, that reframing matters.

That means building processes that support learning instead of resisting it. It means creating room for coordination, iteration, and problem-solving as new requirements move from theory into real project conditions. And it means recognizing that trust in a new process is never achieved through discussion alone. It’s built through participation.

The industry is no longer asking whether healthier materials, ingredient transparency, and responsible manufacturing matter. We know they do.

The challenge now is whether project systems are willing to evolve alongside that understanding.

New ways of working don’t take hold overnight. They emerge as teams continue engaging with the work long enough for a new practice to stop feeling unfamiliar. That’s how industries move forward. And it’s how better buildings get built.