Agency17 June 20263 min read
How to win over developers who are skeptical of AI (a lead's playbook)
Your best senior tried the AI, got code that was almost right and took longer to fix than write, and quietly stopped. That's not resistance, it's judgment. Here's how a lead earns real buy-in instead of fighting it.
The short answer
You win over skeptical developers by taking the skepticism seriously instead of overriding it. Most of it is sound engineering judgment reacting to real experience: copilot-style AI that produces almost-right code which takes longer to fix than to write. Don't mandate, and don't frame it as replacement. Win your hardest senior first by letting them stress-test agents on real work in operator mode, with guardrails and review gates that make the output trustworthy. When the best skeptic is convinced, the team follows.
Short version: the developers pushing back on AI are usually your good ones, and they're usually right. They tried it, got code that was almost right and took longer to fix than to write, and drew a reasonable conclusion. That's not change-resistance, it's the same judgment you hired them for. You don't win them with a mandate or a motivational deck. You win them by changing what the AI actually does, from autocomplete that makes slop to operators that do trustworthy work, and by letting your hardest skeptic prove it on real code.