Handle Manager Resistance to New Technology Adoption
Understand the manager’s operating concern before asking them to champion a rollout.
The buyer moment
Frontline managers resist a new tool because they fear more reporting, disruption, or loss of control.
A frontline manager may resist a new tool because reporting, staffing, or a busy season already absorbs the team. Ask what would become harder in a normal week and who would need to change behavior first. A pilot that includes one skeptical manager can expose practical friction early. Use their feedback to set a small adoption measure, such as completing one approval workflow. The manager gains a voice in rollout design, and the sponsor gains a realistic picture of the effort required. Ask the manager which meeting or report will show whether the first cohort is actually using the new path. Review that evidence with the manager before expanding the rollout.
A useful way to open
“What would make this change harder for your team during a normal week?”
Move the decision forward
Manager resistance often protects capacity or quality. Use it to inform rollout design.
Coach teams to ask about workload, incentives, training, and the manager’s own success measure.
Practice before the next call
Practice with a manager who says, “My team has no time for another tool.” The rep must uncover the specific pressure point.
Next step
Invite the manager into a small workflow design or pilot review before broad rollout.
Practice these next
Protect a customer relationship when a commercial discussion overlaps with an unresolved support issue.
Avoid measuring activity when the customer bought for a different operating reason.
Help buyers separate a real capacity constraint from a vague reason to defer.
Treat low adoption as a joint operating problem before it becomes a price fight.
Build an EBR around decisions, evidence, and unresolved operating questions.
Use trial activity to learn what the buyer is trying to prove.