The Skeptic Who Is Right

The most important outcome when a skeptic raises a valid concern is to fix the problem, not win the argument. This is harder than it sounds, because by the time a skeptic has been raising a concern for several weeks, the change management team has often become focused on overcoming the resistance rather than evaluating the underlying concern. Let me be clear: the initiative that changed based on skeptic feedback is more resilient than the one that steamrolled it. The change that was improved by valid criticism is harder to attack than the change that dismissed it.

1. Create the Valid Concern Process Establish a formal mechanism for evaluating skeptic concerns: document the concern, assess it against the initiative's risk framework, determine whether it requires a design change, and communicate the outcome to the skeptic. This is not a bureaucratic exercise — it is evidence that skeptic concerns are being taken seriously rather than managed away.
2. Act on Valid Concerns Visibly When a skeptic concern produces an initiative change, make the change visible and credit the skeptic: "Based on the governance concerns Sarah raised, we have added an audit trail requirement to the data handling framework." This accomplishes two things: it demonstrates that skepticism produces improvement, not just friction; and it signals to other potential skeptics that their concerns will be addressed rather than ignored.
3. Build a Culture of Productive Skepticism The organization that has learned to productively engage skeptics builds better initiatives. Formalize this: post-initiative retrospectives that specifically credit valid skeptic contributions, change management training that distinguishes between valid concerns and manufactured resistance, and explicit recognition for stakeholders who improve the initiative through critical engagement.