No True Scotsman Fallacy

Modifying definitions to exclude counterexamples and protect a generalization

What is the No True Scotsman Fallacy?

The No True Scotsman fallacy occurs when someone makes a generalization, then faces a counterexample that disproves their claim, and instead of revising their argument, they modify their definition to exclude the counterexample. The name comes from an illustrative example: "No Scotsman puts sugar on his porridge." When faced with evidence of a Scotsman who does put sugar on his porridge, the response becomes, "Well, no TRUE Scotsman puts sugar on his porridge."

In sales contexts, this fallacy often appears when sales professionals or prospects attempt to dismiss evidence that contradicts their claims by retroactively modifying definitions or criteria.

Examples in Sales Contexts

Example 1: Customer Success Claims

Scenario: A sales representative discussing implementation success.

Sales Rep: "All of our customers achieve ROI within six months."

Prospect: "I spoke with Company X who uses your solution, and they mentioned they haven't seen ROI after a year."

Sales Rep: "Well, any customer who properly implements our solution and follows our best practices will see ROI within six months. Company X clearly didn't follow our recommended implementation process."

The sales rep is modifying the original claim by adding new conditions that weren't initially stated to exclude the counterexample.

Example 2: Prospect Objection

Scenario: A prospect dismissing evidence of a solution's effectiveness.

Sales Rep: "Our solution has helped several companies in your industry improve efficiency."

Prospect: "No company in our industry has successfully implemented automation tools like yours."

Sales Rep: "Actually, Companies A, B, and C in your industry have implemented our solution with significant results."

Prospect: "Well, those aren't really comparable companies because they have different business models/are larger/have more resources/etc."

The prospect is modifying their definition of "companies in our industry" to exclude counterexamples that don't fit their narrative.

How to Avoid Using the No True Scotsman Fallacy

  1. Be precise from the start: Make claims with appropriate qualifiers and conditions upfront. Instead of "All customers see results in 30 days," say "Most customers who follow our implementation plan see initial results within 30-45 days."
  2. Acknowledge exceptions: When faced with counterexamples, acknowledge them and refine your position rather than dismissing them. "You're right that Company X had a different experience. Their situation was unique because of X, Y, and Z factors."
  3. Use data ranges: Present outcomes as ranges rather than absolutes. "Our customers typically see ROI in 4-8 months, depending on several factors including implementation scope and internal adoption."
  4. Be transparent about conditions: Clearly state the conditions under which your claims apply from the beginning. "For companies with at least 100 employees and a dedicated IT team, our solution typically reduces costs by 30%."

How to Counter the No True Scotsman Fallacy

When you encounter this fallacy from prospects or competitors:

Why Sales Professionals Should Care

Understanding the No True Scotsman fallacy is important for sales professionals because:

Conclusion

The No True Scotsman fallacy undermines honest communication by allowing people to protect generalizations from counterexamples through ad hoc redefinitions. In sales contexts, this fallacy can lead to unrealistic expectations, damaged credibility, and poor decision-making. By making precise claims with appropriate qualifiers from the start and being willing to acknowledge exceptions and refine positions when faced with counterexamples, sales professionals can build more trusting relationships with prospects and guide them toward solutions that genuinely meet their needs.

Key Takeaway

Make precise claims with appropriate qualifiers from the start, and when faced with counterexamples, be willing to acknowledge them and refine your position rather than moving the goalposts through redefinition.