The Six Skeptic Types

Not every skeptic is skeptical for the same reason. A CFO who says "your numbers seem weak" and a VP of Operations who says "we cannot execute this" are both blocking the decision, but they need different responses. Misreading the skeptic type produces the wrong response — which hardens the skepticism rather than resolving it. Diagnose the type before you respond.

1. The Data Skeptic — "your numbers are wrong" This executive does not trust the data, the methodology, or the source. Response: provide the methodology, the sample size, and the source immediately. Offer to share the raw data. Reference the peer examples that used the same methodology. Do not defend the numbers abstractly — provide the documentation that allows the executive to verify them independently.
2. The Risk Skeptic — "you are underestimating the downside" This executive has been burned before — by a similar project, a similar vendor, or a similar technology. Their risk sensitivity is experiential, not analytical. Response: name the specific risk they are raising before they finish the sentence. Describe the mitigation in detail. Provide a reference from a peer organization that faced the same risk and managed it. The risk skeptic relaxes when they believe the risk has been genuinely seen and addressed, not dismissed.
3. The Capability Skeptic — "we cannot execute this" This executive does not trust the organization's ability to implement, not the recommendation itself. Response: acknowledge the organizational history that produced this concern. Describe the specific implementation support that addresses it — phased rollout, dedicated resources, vendor support. Provide a reference call with a peer who had the same concern and executed successfully.
4. The Priority Skeptic — "this is not the right problem" This executive believes the organization should be focused on a different initiative. Response: acknowledge the competing priority directly. Explain the connection between this initiative and the competing priority — how this investment enables or accelerates the other. If there is no connection, acknowledge the tradeoff and make the case for why this initiative is the higher-value use of resources right now.
5. The Timing Skeptic — "not now" This executive agrees with the recommendation but not with the timing. Response: make the cost of delay visible. Each quarter of inaction has a quantifiable cost — in efficiency, competitive position, or implementation timeline. "Not now" that is left unchallenged becomes "never." Make the executive own the cost of the delay explicitly.
6. The Vendor Skeptic — "I don't trust the solution" This executive has concerns about the specific technology or provider, not the problem or approach. Response: separate the recommendation from the specific vendor if possible. Offer vendor options. Provide customer references from organizations the executive trusts. Acknowledge the vendor's limitations honestly — an honest limitation acknowledged is less damaging than one discovered later.