Addressing Legitimate Concerns

When resistance is based on a real problem, the intervention is to fix the problem. This sounds obvious. It is rarely done properly — because the instinct of a change program under deadline pressure is to explain why the concern is less serious than it appears, rather than to actually address it.

The stakeholder with a Legitimate Concern is not confused about the problem. They have identified a real gap. Explaining why the gap is smaller than they think does not fill the gap. Filling the gap fills the gap.

The conversion mechanism for Legitimate Concern resistance is co-design: engage the resistant stakeholder as a subject matter expert in solving their own concern. Let them help design the governance framework that addresses the governance gap. Let them audit the security architecture and document the residual risks they are willing to accept. Let them define the training requirements that would satisfy their readiness threshold.

This produces two outcomes simultaneously. First, the concern is actually addressed — by the person who understood it most precisely, which produces a better solution than the change team would design without them. Second, the stakeholder transitions from critic to contributor. They have expertise and authority in solving the problem they identified. The identity shifts from "the person who blocked this" to "the person who made it safe to deploy."