CTO AI Corner: overcoming resistance to change in AI-assisted software development?

One common challenge I see when coaching AI tools in different organizations is unexpected resistance to change-even from developers who usually embrace new technologies. Some of the most innovative engineers hesitate to take the AI tooling leap.

And honestly, I get it.

Letting go of part of your hard-earned expertise - skills you've spent years mastering - can feel unsettling. It may even spark self-doubt: If AI can write most of the code, what's my value?

To feel safer, many developers limit AI use to tasks they already dislike, like unit tests or documentation. They accept AI-generated code in small increments - maybe a line or two at a time - while continuing to write the core code manually. But this cautious adoption limits AI's full potential and slows down real skill development.

How can we make AI-assisted development feel safe, inspiring, and rewarding?

Manage expectations - Give developers explicit permission to be less productive while learning AI tools. Growth requires adjustment.

Facilitate success stories - Peer-to-peer inspiration works better than AI vendor pitches. Encourage teams to share real wins.

Normalise failure - Learning new tools means making mistakes. Failures teach more than successes. Create a culture where experimentation is encouraged.

Be patient - AI adoption is a journey. Encourage, support, but don't pressure. Not everyone adapts at the same pace.

March 21, 2025
Authors
Tomi Leppälahti
Share

Leave a message and let's explore together how and where to use AI.

Thank you for your message! We will be in touch soon.
Whoops! Something went wrong with the form submission.