A new project platform goes live on Monday. By Tuesday, a project manager has recreated the old tracking spreadsheet, a superintendent is receiving conflicting updates, and a principal is asking why adoption is taking so long. The issue is rarely that people in AEC do not understand the need for improvement. The challenge is how to reduce change friction when teams are already managing deadlines, client expectations, field conditions, and complex coordination.

Change friction is the drag that appears between a decision and sustained new behavior. It can look like skepticism, delayed follow-through, workarounds, silence in meetings, competing priorities, or a quiet return to familiar routines. Leaders can misread these signals as resistance to change itself. More often, they are signals that people lack clarity, capacity, confidence, or a meaningful connection to what is being asked of them.

The most effective response is not to push harder. It is to get more curious about what is making the change difficult to carry.

Why Change Friction Is So Common in AEC

Architecture, engineering, and construction organizations are built around delivery. People are rewarded for solving immediate problems, protecting project commitments, and keeping work moving. That practical urgency is a strength. It can also make organizational change feel like one more demand placed on already-full teams.

A new process may be logical from the executive level yet create extra steps for a project team during a critical submission. A technology rollout may promise better visibility later but require people to learn new habits now. A restructuring may make strategic sense while raising reasonable questions about decision rights, relationships, and career paths.

Friction increases when leaders describe change only in terms of the future state. People also need help with the transition between the old way and the new one. They need to understand what will change in their daily work, what will remain stable, where they can ask questions, and how the organization will respond when the first version is imperfect.

Start With Curiosity, Not a Communication Plan

Communication matters, but more communication is not automatically better communication. A polished announcement cannot resolve concerns that leaders have not taken time to understand.

Before finalizing messages, ask people closest to the work what the proposed change will require from them. Ask where the process could break down, what competing demands they are carrying, and what they would need to see to believe the effort is worthwhile. These are not questions designed to collect approval. They are questions that improve the quality of the change itself.

A project executive might ask, “Where will this new coordination process add effort before it creates value?” A department leader might ask, “What are we assuming about how work actually gets done?” A team leader might ask, “What concerns are people reluctant to raise in a large meeting?”

The answers may be inconvenient. They may reveal that a timeline is unrealistic, that training is too generic, or that different offices need different support. That is useful information, not a failure of leadership. Curiosity helps leaders distinguish between objections that need to be addressed and preferences that can be worked through.

Listen for the practical concern beneath the reaction

When someone says, “We tried this before,” the underlying concern may be that previous leaders did not follow through. When someone says, “This will not work on our projects,” they may be pointing to a legitimate operational constraint. When a team becomes quiet, they may be unsure whether honest feedback is welcome.

Treating every concern as negativity creates defensiveness. Treating every concern as valuable data builds trust. Leaders do not need to agree with every viewpoint, but they do need to show that they understand the experience behind it.

Make the Reason for Change Specific and Local

Broad statements such as “we need to be more innovative” or “this will improve efficiency” are rarely enough. People need a reason that connects to their work, their clients, and the outcomes they care about.

For a design team, the benefit may be fewer late-stage coordination surprises. For a construction operations group, it may be clearer handoffs and faster issue resolution. For a business unit leader, it may be more reliable information for decisions. The overall strategy can be consistent while the relevance changes by role.

Be equally clear about what the change will not solve. A new platform will not repair unclear accountability. A revised organizational chart will not automatically create trust. A leadership program will not substitute for leaders making timely decisions. Honest boundaries make the case for change more credible because they show people are not being sold a cure-all.

Reduce the Effort Required to Begin

Many change initiatives ask for too much behavior change at once. Leaders announce a new operating model, new systems, new meeting rhythms, and new reporting expectations, then wonder why adoption is uneven. Even capable people struggle when the cognitive load is too high.

Break the change into a small number of observable actions. Instead of asking teams to “embrace collaboration,” define the first practices: use one shared location for current project decisions, establish a weekly cross-functional issue review, or clarify who owns the next action before a meeting ends.

This does not mean oversimplifying a complex transformation. It means making the next step clear enough to practice. Progress becomes more visible when people know what good adoption looks like in the first 30 days, not only at the end of the year.

Leaders should also remove obstacles that make the old way easier than the new one. If teams are expected to use a new workflow but templates, approvals, and reporting still reward the old workflow, friction is predictable. Alignment between systems, incentives, expectations, and leader behavior matters more than a persuasive launch message.

Involve the People Who Will Carry the Change

Involvement is not the same as asking everyone to vote on every decision. Some choices need to be made quickly, and leaders are accountable for making them. But people are more likely to commit when they have a real opportunity to shape how change is implemented.

Invite representatives from different roles, offices, disciplines, and project environments to test assumptions early. Give them a specific role: identify risks, test a pilot, improve training materials, or surface communication gaps. Then show what happened with their input.

This is particularly valuable in AEC organizations, where the difference between a corporate process and project reality can be significant. The people doing the work often see constraints that are invisible in a conference room. Their involvement produces better solutions and demonstrates respect for professional judgment.

Equip Managers to Lead the Middle of Change

Senior leaders establish direction, but managers and project leaders often determine how change feels day to day. Their teams look to them for context, answers, and cues about whether a new priority is real.

Do not assume managers can translate a strategic announcement into practical guidance without support. Give them a clear narrative, likely questions, decision boundaries, and a way to escalate issues they cannot resolve. Just as importantly, give them space to process the change themselves. A manager who is confused or unconvinced will struggle to create confidence for others.

Managers do not need perfect answers. They need the confidence to say, “Here is what we know, here is what is still being decided, and here is how we will keep the conversation moving.” That kind of candor is more trustworthy than false certainty.

Build Trust Through Visible Follow-Through

Trust is built when people see a connection between what leaders say and what leaders do. If leaders ask for feedback, they need to acknowledge it. If they promise decisions by a certain date, they need to meet that commitment or explain the delay. If a pilot reveals a flaw, they need to adjust rather than defend the original plan.

Visible follow-through is especially important after the initial launch, when attention naturally shifts back to project demands. People are watching whether leaders continue to reinforce the change, recognize early progress, and address barriers. They are also watching whether exceptions are handled consistently.

Celebrate learning, not just flawless execution. A team that identifies a problem early and improves the approach is helping the organization build adaptability. When every mistake is treated as evidence that change has failed, people become less willing to experiment or speak up.

Measure More Than Compliance

A completed training session or a signed acknowledgment may show exposure to a change, but it does not show adoption. Look for measures that reflect whether the new behavior is becoming part of the work.

The right measures depend on the change. They might include reduced rework, faster decisions, stronger handoffs, better forecast accuracy, improved retention, or more consistent use of a critical process. Pair operational indicators with qualitative check-ins. Ask teams where the change is helping, where it is adding unnecessary burden, and what would make the next stage easier.

Not every concern requires a redesign. Sometimes teams need time and practice. Other times, their feedback reveals a problem that would become more expensive if ignored. The goal is not to eliminate all discomfort. Meaningful change often requires people to learn, let go of familiar routines, and work through uncertainty. The goal is to ensure that the effort leads somewhere worthwhile.

Connective Consulting Group often sees that organizations make more progress when they stop treating friction as a people problem and start treating it as a leadership signal. When leaders create clarity, invite perspective, and follow through with practical support, change becomes less of a disruption to survive and more of a capability the organization can strengthen.

The next time momentum slows, resist the urge to ask, “How do we get people on board?” Ask a more useful question: “What is this experience telling us about the conditions people need to move forward?” That question can turn friction into insight, and insight into progress.