← Objection Library

Implementation Will Be Too Difficult

Do not minimize disruption. Compare the temporary inconvenience of change with the permanent cost of dysfunction.

This objection comes from someone imagining their own team's calendar. They are not doubting the product, they are counting the hours it will take out of people who are already short.

What they say

  • “This would be a nightmare to roll out”
  • “My team doesn't have the bandwidth”
  • “Switching is too disruptive”

What's actually underneath it

A real operational constraint deserving respect

One prior bad implementation shaping the whole view

Nobody wants to own the project internally

The ten questions that open it up

Ask one. Then stop talking. The answer is worth more than anything you were about to say.

  1. 1.“Which part of implementation concerns you most?”
  2. 2.“Who on your team would carry the greatest burden?”
  3. 3.“What previous implementation experience is shaping that concern?”
  4. 4.“How much disruption is the current problem already causing?”
  5. 5.“What would make the transition manageable for your team?”
  6. 6.“Would a phased rollout reduce the risk?”
  7. 7.“What support would your people need from us?”
  8. 8.“How long do you believe the difficult portion would actually last?”
  9. 9.“If implementation were easier than expected, would anything else stop the decision?”
  10. 10.“Is avoiding short-term inconvenience worth preserving the long-term problem?”
Advertisement

The trap

Minimizing the disruption. They have lived through one and you have not.

Never minimize the disruption. Weigh it honestly against the disruption the current problem is already producing, and let them do the comparison.

Related objections

Try it live

Paste the objection you actually got this week and get the question to ask back.

Reverse your objection
Advertisement