CM-301b · Module 1

The Skeptic as Signal

3 min read

Here is the counterintuitive observation that most change managers resist: high-quality skeptics are assets. They identify failure modes before they materialize. They stress-test the initiative's assumptions. They surface concerns that enthusiastic adopters are too committed to raise. The Evidence Skeptic who demands proof of ROI is doing exactly what the organization's analytical function should do. The Risk Skeptic who catalogs what could go wrong is building your risk register for free. I don't tell people what they want to hear. What I tell them is this: the question is not whether the skeptic's concerns are valid. The question is whether you are disciplined enough to listen.

Do This

  • Distinguish between valid concerns that require substantive response and manufactured objections that require a different intervention entirely
  • Create a formal mechanism for skeptic input — a review session, a structured questionnaire, a documented feedback process
  • Treat skeptic concerns as a quality input to the initiative design, not as resistance to overcome

Avoid This

  • Dismiss skeptic concerns as obstruction without examining their validity
  • Route around skeptics rather than engaging them — the concern will not disappear, it will just surface later in a more damaging form
  • Conflate the skeptic's behavior with the skeptic's intention — most skeptics are not trying to kill the initiative, they are trying to protect something they care about