The Skeptic's Behavioral Profile

Most organizational skeptics are High-C or High-D by DISC profile — not because skepticism is limited to these dimensions, but because the behavioral presentation of skepticism expresses most visibly through these profiles. High-C individuals have a built-in evidence requirement and a low tolerance for unsubstantiated claims. They are not being difficult — they are operating at their natural analytical standard. High-D individuals are skeptical about anything that threatens their control or competitive positioning. They may agree with you privately and obstruct you publicly if they perceive the initiative as undermining their authority. Same surface behavior — sustained objection — completely different drivers, completely different interventions.

1. High-C Skeptic Profile Driver: evidence gap. The High-C skeptic is not resisting the initiative — they are resisting insufficient justification for the initiative. They need: documented methodology, cited evidence, clear risk analysis, and proof of governance. They will not be persuaded by enthusiasm, by anecdote, or by authority. Give them documentation. Give them data. Give them time to analyze both. Then ask for their assessment.
2. High-D Skeptic Profile Driver: control threat or competitive positioning. The High-D skeptic who is raising substantive objections may be protecting their autonomy or defending their organizational territory. The tell: their objections shift as each one is addressed, and they never fully acknowledge when a concern has been resolved. The intervention is not evidence — it is inclusion. Give them a role with genuine authority in the initiative. The High-D who has ownership of an outcome cannot oppose the outcome without opposing themselves.
3. High-S Skeptic Profile Driver: stability threat. High-S skeptics are not typically the loudest voices, but they are the most consistent. They will raise the same concern repeatedly because the concern is not resolved by information — it is resolved by experience. Show them a stable pilot. Give them a phased implementation with advance notice. Let them see that the old processes are being treated with respect even as new ones are introduced.