Overcoming Resistance to Demo Automation

Why Demo Automation Adoption Fails Before It Starts

Most demo automation initiatives don't stall because of the tool. They stall because of resistance to change. Teams misjudge what demo automation does, assume it threatens their role, or simply prefer the comfort of established ways of working. The result: tools that would create real value never get bought, or get bought and never adopted.

Economists have a name for the kind of change being blocked here: a Pareto improvement, a change that makes someone better off without making anyone worse off. Demo automation is exactly that kind of change. Yet bias, misaligned information, and plain hesitancy still stand in its way, in organizations of every size, every day.

I've successfully embedded demo automation in a large organization and learned this lesson the hard way. Over the next few weeks, I'll publish three articles sharing my key learnings on how to succeed with demo automation, whether or not you hold formal authority in your organization (it helps, but isn't required). Together, these articles form a practical framework. By the end, you'll have the full picture and a concrete starting point for your own organization.

Ready to get started?

The Problem: Why Demo Automation Faces So Much Resistance

Demo automation is particularly susceptible to what we might call the Mulan problem. This field suffers from widespread misunderstanding  and even outright lack of understanding  combined with natural resistance to changing established ways of working.

Consider how different teams misread demo automation's purpose:

• Sales leaders often assume it replaces Presales reps. It doesn't.
• Presales leaders may see it as a substitute for their team's work. In reality, it's complementary; it boosts their team's efficiency.
• Sellers frequently believe it replaces live customer engagement and relationship-building. It doesn't. ("I want a relationship, not an automated demo" is a common objection.)
• Adjacent revenue teams  Field Marketing, Sales Strategy, Sales Programs, and Sales Enablement  often don't even know demo automation exists, let alone how it could help them hit their own goals.

Having experienced and solved these challenges myself, and having learned from others who came before me, I know firsthand how difficult this is. Compounding the issue: Finance and Procurement teams often don't understand the value proposition either, and  because no one else champions it  no investment gets made.

Two Core Challenges Behind Resistance to Change

Driving adoption of something people don't understand runs into at least two obstacles:

1. The bias and misinformation challenge: the same dynamic illustrated in the Mulan story.
2. Natural resistance to change: People generally prefer the status quo because it's easy and comfortable, while change is inconvenient and mentally taxing, especially for busy teams.

Other obstacles exist too, but they're secondary to this core truth: people resist changing their beliefs and behaviors. If you can convince someone that a change serves their interest  and make it easy for them to act on that belief across teams, departments, roles, and functions  the rest follows naturally.

The Solution: Applying Change Management Principles

So how do we solve these challenges? There's an entire discipline dedicated to exactly this: change management, the art of changing beliefs and behaviors.

Just as the right incentive can lead a horse to water, the right incentives can guide people toward desired actions. Designing that incentive is more nuanced with people than with animals, but the underlying principle holds: everyone responds to incentives, whether that means satisfying a core need, reducing cognitive burden, or seeing a number grow in a bank account.

Why Kotter's 8-Step Change Model Works

Change management is part art, part science. Among the many available frameworks, Kotter's 8-Step Process for Leading Change stands out, for three reasons:

• It's field-tested. It was developed and refined using real people solving real challenges in real companies  not created in a research lab.
• It's practical and accessible. The principles are easy to understand and apply, without requiring time spent parsing academic journals.
• It's sequential and actionable. Its step-by-step structure makes it easy to assign tasks, track actions, and measure progress along the way.

In short, the Kotter framework helps practitioners:

• Prepare for change (Steps 1–3)
• Execute the change (Steps 4–6)
• Consolidate the change (Steps 7–8)

Case Study: Netflix vs. Blockbuster

One of the clearest examples of change management in action is the fall of Blockbuster and the rise of Netflix.

Netflix started as a DVD rental company, much like Blockbuster, just as the internet was becoming mainstream. Blockbuster, as the market leader, grew comfortable in its position and failed to recognize streaming as a threat to its business model.

Netflix, under CEO Reed Hastings, took the opposite approach. The company capitalized on the shift and drove a sweeping business model change from DVD rentals to digital streaming. The rest is history: Netflix thrived through deliberate change management, while Blockbuster's inability to adapt led to its downfall.

What's Next

The change management principles that helped Netflix outmaneuver Blockbuster apply just as directly to demo automation adoption  whether you're a business leader, a Disney princess, or someone driving change in your own organization.

In the next article, I'll walk through the preparation steps of the Kotter framework in detail, with practical examples and tips you can apply immediately  so you can start driving change like a true Change Agent.

Want to see demo automation in action?

Explore the Interactive Demo Playbook