A project manager dismisses a new project-management platform as “one more system.” A department leader nods in a leadership meeting, then tells their team to keep doing things the old way. A respected technical expert challenges every change request, often with facts that are difficult to ignore.

These moments can be frustrating, especially when schedules are tight, margins are under pressure, and leaders need people to move together. Yet learning how to coach resistant managers begins with a different assumption: resistance is rarely the whole story. It is often a signal that someone sees a risk, lacks clarity, feels excluded, or is carrying the weight of previous change efforts that did not deliver on their promise.

The goal is not to win an argument or force agreement. It is to create enough trust and clarity that a manager can move from protecting what they know toward participating in what comes next.

Start by Reframing What Resistance May Mean

Calling someone “resistant” can be useful shorthand, but it can also stop curiosity too early. A manager may be protecting their team from disruption during a critical deadline. They may be concerned that a new process will compromise quality, client commitments, safety, or the autonomy that helps their people perform. They may simply not understand why the change matters.

In AEC organizations, skepticism can be earned. Teams have seen systems introduced without adequate training, organizational charts changed without clear decision rights, and initiatives launched with energy only to fade when project demands increase. A manager who asks hard questions may be expressing caution, not defiance.

This does not mean every concern is valid or that leaders should allow a single manager to veto needed change. It does mean the first coaching move is understanding before persuasion. When leaders treat concerns as data, they can distinguish between a practical obstacle, a misunderstanding, a values conflict, and a pattern of behavior that requires stronger accountability.

How to Coach Resistant Managers Without Creating Defensiveness

The setting and tone of the conversation matter. Coaching a manager in the middle of a crowded meeting or after a visible disagreement usually increases the need to defend their position. Choose a private moment, name the shared purpose, and speak to observable behavior rather than assigning motives.

For example, instead of saying, “You are being negative about the new staffing model,” try: “I noticed that in the last two meetings you raised concerns about the staffing model, and your team has not yet started using the new process. I would like to understand what you are seeing.”

That distinction is small but meaningful. The first statement labels the person. The second invites a conversation about facts, impact, and possibilities.

Ask questions that make room for the real concern

Curiosity is not a soft alternative to leadership. It is how leaders get better information before deciding what support, adjustment, or accountability is needed. Useful questions include:

• What concerns you most about this change for your team, our clients, or the work itself?
• What do you believe we may be overlooking?
• What would make this change more workable in your area?
• What part of the direction is unclear or difficult to support?
• What do you need from me, and what do I need from you?

Listen for what sits beneath the first answer. “We do not have time for this” may mean the manager needs capacity planning. “This will never work” may point to a specific workflow failure. “My team is tired of changes” may reveal that they have not seen a credible connection between the initiative and better project outcomes.

The purpose is not to promise that every concern will change the plan. It is to demonstrate that concerns can be raised, examined, and responded to with respect.

Separate influence from ownership

Managers need to know where they have meaningful input and where a decision has already been made. Ambiguity invites repeated debate. If a new client-delivery standard is nonnegotiable, say so plainly. If the rollout sequence, training approach, or team-level application can be shaped by experience in the field, say that plainly too.

A clear message might sound like this: “The firm is moving to this standard because we need greater consistency across projects. The direction is set. Your insight on how we phase it, where the process will create friction, and what your team needs to adopt it is essential.”

This approach respects expertise without creating the false impression that participation equals veto power. It also helps managers shift from asking whether the change will happen to helping determine how it can succeed.

Connect the Change to the Manager’s Real Work

Senior leaders often communicate change in strategic language: growth, transformation, integration, market position. Those reasons may be sound, but a manager facing active projects needs to understand the operational connection.

Bring the conversation closer to their reality. How will the new approach affect coordination between disciplines? What will it mean for field communication, proposal development, quality reviews, or client responsiveness? What problem will it reduce? What new burden might it introduce before the benefits are realized?

Be honest about the trade-offs. Some changes do add work in the short term. Some processes feel less efficient before people build competence. Credibility grows when leaders acknowledge that truth instead of overselling a future state.

Then connect the effort to a purpose the manager can recognize. A new system may reduce rework. A clearer decision process may prevent teams from waiting on conflicting direction. A leadership expectation may help emerging managers make decisions with more confidence. When people can see the relationship between the change and work they care about, compliance has a better chance of becoming commitment.

Make Expectations Clear and Support Visible

Empathy without clarity leaves teams uncertain. Once you have listened and explored the concern, establish the next expectation in specific terms. Avoid ending a coaching conversation with “Let’s see how it goes.”

Instead, clarify what the manager will do, what support will be available, and when you will revisit progress. For example: “By next Friday, I need you to identify the two workflows most affected, select a point person for each, and bring forward the barriers your team encounters. I will make sure you have access to the implementation lead and will review the findings with you in our next one-on-one.”

This creates movement without demanding that the manager feel enthusiastic immediately. People can act professionally while they are still working through uncertainty. Over time, action, learning, and visible support can change their relationship with the initiative.

Support should match the source of resistance. If the issue is skill, provide training and practice. If it is capacity, reprioritize work or add resources where possible. If it is a lack of authority, clarify decision rights. If it is a repeated pattern of undermining agreed-upon direction, address the behavior directly and explain the impact on the team.

Watch for the Difference Between Healthy Dissent and Disengagement

Not all resistance should be handled the same way. Healthy dissent strengthens decisions. It surfaces risks before they become expensive failures, particularly in complex project environments where overlooked details can carry serious consequences. Leaders should make room for managers who challenge assumptions constructively and remain willing to help solve the problem.

Disengagement looks different. It may show up as withholding information, refusing reasonable next steps, publicly discrediting decisions after the discussion has ended, or encouraging a team to ignore expectations. In those cases, curiosity still matters, but it must be paired with accountability.

Be direct: “I value your perspective, and I expect you to raise concerns. Once we make a decision, I also expect you to help your team move forward. Continuing to dismiss the process without bringing forward workable alternatives is affecting implementation and team trust.”

This is not punitive. It is a necessary leadership boundary. Managers have influence far beyond their own opinions. Their visible behavior teaches their teams whether change is something to engage with thoughtfully or quietly resist until it disappears.

Build a Relationship That Can Carry Future Change

A single coaching conversation may resolve a practical concern, but deeper patterns take time. Follow through on commitments. Return to the concerns that were raised. Share what changed because of the manager’s input and explain what did not change and why. These actions show that speaking honestly has value.

Also notice progress. A manager who once dismissed an initiative but later identifies a workable solution, invites their team into the conversation, or tests a new practice is doing meaningful leadership work. Acknowledge the shift specifically. Recognition reinforces adaptability without pretending the path was easy.

The strongest leaders do not demand that managers welcome every change with immediate enthusiasm. They create conditions where managers can ask better questions, surface legitimate risks, understand the boundaries of a decision, and lead their teams forward with integrity. That is how resistance becomes a more useful conversation – and how organizations build the trust required for progress.