The Program Runs Its Diagnosis

The program is in its sixth month. Two business units have been flagged as high resistance. The evidence the implementation team has compiled: adoption rates that lag the rest of the portfolio by ten to fifteen points, a persistent pattern of exception requests that the governance process has approved more often than denied, training attendance that meets the formal minimum without exceeding it, and leadership messaging that is technically on-message but carries the particular flatness of a statement prepared under obligation. The change management workstream has responded. Town halls were scheduled and held. Business unit heads delivered targeted communications from scripts the program office provided. A pulse survey went out; the program office reviewed results and planned follow-up. The program sponsor committed to personal visits at both sites.

Three months later, the visits happened. The metrics moved, but not much. Both units remain at the bottom of the adoption leaderboard. The program office is planning a second communications initiative.

The program is not running low on ideas. It is running the same idea repeatedly because the diagnosis that produced the first intervention has not been questioned. The assumption, held implicitly by the change management workstream and reinforced by every governance review, is that these teams are resistant in a way that better communication and stronger leadership reinforcement can address over time. That assumption deserves examination. Not because these teams are secretly enthusiastic about the change, but because what looks like resistance is almost certainly a rational response to structural conditions that no volume of town halls will alter, and that the program’s diagnostic instruments are not designed to detect.

The more useful question is not “how do you manage resistance?” It is: what is resistance actually telling the program about the conditions it has created, and why are those conditions so systematically misread?

What the Behavioral Reading Accurately Observes

Programs do not invent the resistance they report. When a change management workstream flags a team as resistant, it is typically observing real behaviors: participation that meets the formal minimum without exceeding it, questions that accumulate rather than resolve as the program progresses, workarounds that survive alongside new processes rather than being retired by them, and a quality of waiting that is difficult to name precisely but immediately recognizable to anyone who has managed an enterprise rollout across multiple sites. Programs that report resistance are, in most cases, accurately reporting what they observe.

What the conventional diagnosis misattributes is the driver. The behavioral reading locates the cause in the stakeholders themselves: their risk aversion, their attachment to existing methods, their insufficient understanding of the business case, their failure to trust the direction. Programs do not manufacture these attributions either. They reflect a near-universal interpretive tendency in program management cultures, where execution pressure creates strong incentive to treat the plan as sound and variance from the plan as a stakeholder problem. When the program is behind schedule, the question “what is wrong with the plan?” is less politically available than “what is wrong with these teams?”

The structural reading begins one level deeper. Its diagnostic question is: what conditions would have to exist in this organization to make this observed behavior rational, regardless of how any individual feels about the change? That question almost always has a specific answer, and it points somewhere other than the stakeholders’ attitudes.

When the Structure Makes Non-Cooperation the Rational Choice

Incentive misalignment is the structural source of resistance that programs are least equipped to detect. Programs routinely ask teams to adopt new behaviors while the incentive structures governing those teams continue to reward the old ones. A migration to a standardized operating model requires functional leads to absorb transition costs in the quarters when those costs will affect their performance metrics, with the promise of long-term benefits that will not appear on any scorecard they are held accountable to. The adoption of a shared data platform asks business units to expose performance information they have, until now, managed discretely within their own regional scorecards. The rollout of a new workflow system requires teams to invest time in learning during a period when their throughput targets remain unchanged.

In each case, the behavior labeled as resistance is a rational calculation about the cost of compliance. The teams may not oppose the direction. They are responding, without necessarily articulating it, to the fact that the incentive architecture has not been adjusted to make adoption less costly than non-adoption. A town hall that explains the strategic rationale more clearly will not alter that calculation. The calculation runs on incentives, not on information, and until the incentive structure is adjusted, the calculation will continue to produce the same answer: wait.

The particular difficulty with incentive misalignment is that the teams experiencing it rarely name it as such. They report workload pressure, capacity constraints, and implementation complexity, all of which are real secondary effects but not the primary source of the resistance. The operational language teams default to under pressure confirms the behavioral diagnosis. The structural source behind that language remains unnamed, which is exactly what makes it persistent.

A second structural source is harder to detect because it operates through what is not said rather than what is observable. Programs ask for commitment from stakeholders whose real concerns the program has never surfaced. A team lead whose expertise in the legacy system had become obsolete when the new platform went live, with no clear picture of what her professional value would look like on the other side of the transition. A regional manager who had supported the program formally while privately calculating that the centralized model would expose performance gaps his team had managed through institutional workarounds for years. A senior specialist who had endorsed the new process in the steering committee while carrying an unspoken concern about whether his team could maintain client service standards through the transition period.

None of these individuals is behaving dishonestly. Each is navigating a structural gap: the program created conditions for formal endorsement without creating conditions for honest disclosure of what endorsement actually costs them. The concerns that the program never surfaced do not disappear. They persist, shaping behavior in ways that produce the observable signature of resistance without any of the stakeholders experiencing themselves as resistant. They experience themselves as managing real pressures the program has not accounted for. The behavioral diagnosis looks at the output of that experience and calls it a communication problem. The structural diagnosis looks at the conditions that produced it and asks why the program architecture made it rational for these concerns to remain unexpressed.

The Structural Cost of Managing the Symptom

The interventions programs design in response to resistance do not merely fail to address the structural sources. They actively suppress the diagnostic signal those sources are generating, while leaving the conditions that produced it intact.

A communication campaign directed at teams whose resistance is structurally produced tells those teams, implicitly, that the program has heard their behavior and interpreted it as an information problem. The response to an incentive misalignment is a town hall that explains the business case more clearly. The response to an unacknowledged interest concern is a leadership reinforcement message. Both decode the signal as “insufficient understanding” and respond accordingly. This is wrong about the cause. It is also socially costly, because teams struggling with real structural pressures and receiving a communication campaign in response learn something specific: that expressing the struggle through observable behavior produces more messaging rather than structural adjustment. The rational response to that learning is to perform the adoption behaviors more convincingly while continuing to navigate the actual constraints unchanged. Adoption metrics improve. The underlying condition does not.

The more damaging effect is what happens to the signal itself. When programs respond to resistance with engagement initiatives, the visible symptoms often moderate, because teams adjust their visible behavior in response to the increased attention. The adoption curve inches upward. Pulse survey scores improve. The program’s measurement instruments report forward progress. The structural source remains intact, but the intervention has partially suppressed the evidence that would prompt structural investigation. The program moves into its next phase carrying a misalignment that has become harder to detect because the program has managed its most visible symptoms without resolving them.

This mechanism produces a recognizable pattern: a transformation program that appears to be gaining traction in its middle phases, then loses momentum near the end or shortly after formal closure, when the structural pressures that were managed through heightened attention reassert themselves as the program’s oversight infrastructure winds down. Programs attribute the momentum loss to change fatigue or sustainability challenges. Its actual cause is that the resistance the program managed was a symptom, and the program never addressed the structural condition producing that symptom.

Reading the Signal Before Managing the Symptom

The question programs ask when resistance persists is almost always some version of “why aren’t these teams adopting?” That question has a structural flaw: it assumes the behavior being observed is a deviation from a sound baseline rather than a rational response to conditions the baseline has not accounted for. The more useful formulation is: what would a person in this structural position, with these incentives and these unresolved concerns, rationally do? If the answer resembles the behavior being labeled as resistance, the behavior is structural information, not a change management failure.

Several markers distinguish structurally-produced resistance from the kind that communication and engagement can address. The most reliable is consistency across individuals. When the same behavior pattern appears across multiple people in the same role, function, or region, individual explanation becomes less credible. Different people with different personalities and different relationships to the program, responding identically, suggests that what they share, the structural position, is doing the explanatory work. Individual resistance is idiosyncratic. Structural resistance tends to be uniform.

Persistence through communication cycles is equally diagnostic. If resistance survives multiple rounds of messaging, clearer business case presentations, and visible leadership reinforcement, the cause is almost certainly not informational. Structural sources of resistance do not respond to additional information about the rationale for change, because they are not produced by insufficient understanding of the rationale. They are produced by conditions the rationale does not address.

The third marker is harder to observe through formal channels but tends to be definitive when available: the pattern of concerns that surface in one-on-one conversations but not in formal settings. What people say to trusted colleagues informally, away from governance forums and official feedback mechanisms, tends to be structurally accurate. These conversations name the real pressures, the real calculations, and the real conditions that formal program processes have not created safety to surface. They are the diagnostic signal in its least managed form. A program that invests in creating conditions for these conversations, in bilateral settings where honest disclosure carries little social cost, typically learns more about the real sources of resistance in a single afternoon than in a dozen town halls.

What Adjusting the Diagnosis Requires

Once the program has determined that the resistance it is observing is structurally produced, the intervention design changes entirely. Not because communication becomes irrelevant, but because the program now knows it is not treating a communication problem, and designing a response against the actual source requires instruments that most program frameworks are not built to provide.

The first adjustment is an incentive architecture review before execution begins, not after resistance has emerged. Programs routinely assess stakeholder readiness: do people understand the change, do they have the skills to execute it, do they agree with its direction? Programs rarely assess whether the incentive structures governing stakeholder behavior have been adjusted to make adoption less costly than non-adoption. That assessment belongs in the design phase, covering questions like: what performance metrics govern the teams being asked to change, what transition costs will they absorb in the short term, and what long-term benefits will appear on the scorecards they are held accountable to? The questions are not complicated. What is uncommon is treating them as design inputs rather than as background context. A program that identifies an incentive misalignment before execution can redesign around it. A program that discovers the misalignment six months in must manage it, which is more expensive, less effective, and by that point produces exactly the adoption lag described here.

The second adjustment is a shift in the character of pre-execution stakeholder conversations, from confirmation-seeking to interest-surfacing. Programs that engage stakeholders before execution in bilateral, low-stakes settings, asking not “do you support this?” but “what would this mean for your team, and what would need to be true for that to be manageable?” consistently learn more about the structural sources of potential resistance than programs that treat formal alignment checkpoints as their primary diagnostic instrument. The concerns that surface in these conversations are the structural signal before it has been compressed into the behavioral symptoms that programs eventually flag as resistance.

Neither adjustment is technically complex. What makes them rare is the implicit assumption they require the program to abandon: that the plan is sound and variance from it is a stakeholder problem. The structural reading of resistance requires, instead, the assumption that variance is information about conditions the plan has not accounted for. The program’s job is to surface and address those conditions before execution pressure converts them into patterns that look indistinguishable from the behavioral resistance that communication campaigns are designed to manage.

The programs that manage resistance most effectively are not the ones with the most sophisticated engagement campaigns. They are the ones that have diagnosed accurately enough to know whether what they are observing reflects a communication gap or a structural condition, and that have the discipline to design their response against the actual source rather than its most visible symptom. That discipline is not widely practiced, because the instruments programs use to track progress are calibrated for confirming what the plan predicts, not for detecting where the plan’s assumptions about structural conditions are wrong. The resistance that persists through every communication wave is the plan trying to surface one of those wrong assumptions. The programs that hear it learn something. The programs that manage it carry the unresolved condition forward into the next transformation cycle, where it appears again, with a different label.

These patterns are examined structurally in Strategic Negotiation in Organizational Transformation (Omou Publishing, 2026), which develops both the diagnostic and design frameworks in full.