How to respond to “Our team isn’t ready for change”
Customers say “Our team isn’t ready for change” for a reason. Here is what usually sits behind it, how to respond and what to avoid.
What is really behind it
The customer is worried about adoption: people who resist, are overloaded or are fed up with new things. It is a real risk. Behind it there may also be a lack of confidence that the change will help the team rather than burden it.
Typical in: Software and SaaS, Manufacturing and logistics, Professional services, Contact centre and customer service
How to respond
Pick the framework that fits the customer. The wording is an example direction, not a script: say it in your own words.
Clarify before you answer
Ask what sits behind the objection, so you answer the real concern.
“That is a fair concern. What worries you most: that people will not use it, that they have no time to learn it, or that they will resist being asked to?” Each calls for a different answer.
Propose a smaller step
Shrink the decision to something low-risk that moves things forward.
“We could start with one or two people who are open to it, and let the rest see how it goes. A small, successful start often does more than a big announcement.”
Offer proof
Offer an example, a reference or a sample the customer can check. Never an invented figure.
“I can show you how teams usually introduce this and where they run into trouble, so you can judge whether your team could manage it. Would a short walkthrough help?”
The follow-up question
After your response, ask:
Who in your team would be the natural person to try it first?
What not to say
Avoid: Your people will just have to get used to it.
It dismisses the customer’s responsibility for their team. A manager who feels unheard becomes the person who blocks you.
Practise it out loud
Reading is not the same as saying it. Talk to an AI customer who raises this kind of objection and see in the report which sentence helped.
What does “Our team isn’t ready for change” really mean?
The customer is worried about adoption: people who resist, are overloaded or are fed up with new things. It is a real risk. Behind it there may also be a lack of confidence that the change will help the team rather than burden it.
How do you respond to “Our team isn’t ready for change”?
Clarify before you answer: “That is a fair concern. What worries you most: that people will not use it, that they have no time to learn it, or that they will resist being asked to?” Each calls for a different answer. Propose a smaller step: “We could start with one or two people who are open to it, and let the rest see how it goes. A small, successful start often does more than a big announcement.” Offer proof: “I can show you how teams usually introduce this and where they run into trouble, so you can judge whether your team could manage it. Would a short walkthrough help?”
What should you ask after “Our team isn’t ready for change”?
Who in your team would be the natural person to try it first?
What should you not say when a customer says “Our team isn’t ready for change”?
Avoid “Your people will just have to get used to it.” It dismisses the customer’s responsibility for their team. A manager who feels unheard becomes the person who blocks you.
Educational conversation training. It is not legal or financial advice and it promises no results. Always follow your company’s rules, the terms of the product and a customer’s clear no.