Name: Why Your Engineers Won't Use AI, and What To Do About It In-Person Workshop
Start: 2026-08-26T23:00:00.000Z

You keep telling your engineers to use AI but it's not working

Your engineers won't use AI, and you don't know why. You're doing everything you can, giving them the time, freedom, and AI tools to experiment. But every time you encourage them, it comes back with "it's just AI slop," "I can do it better," "it's not working" - and they kind of give up. There's a resistance you can feel but can't explain.

Meanwhile you and the exec team have identified AI as an opportunity, but you need your engineers on board to explore the questions that matter: how much faster can we ship features? Can we solve customer and business problems and reduce costs? It's an exciting time, but right now you're dragging your engineers along. It's slow and it's hard.

Why can't they just get on board?

Because you're not solving the underlying problem. The resistance isn't about AI. It's about their identity. They've built their whole careers writing code to solve problems, creating their own processes and ways of working, and AI challenges all of it. Logic doesn't work here when there are this many feelings involved.

Solution:

An activity to help your engineers surface and name how they really feel about AI
Guiding them through the identity shift underneath the resistance, using a 4-step model
So they leave embracing AI as part of their role, not a nice-to-have, and choosing to experiment with it themselves

Outcomes

There's less excuses, and your engineers are actively using AI instead of resisting it
Engineers start talking about their AI wins, rather than you pushing AI onto them

Details

Date: Thurs 27 August 2026
Time: 9am to 12pm AEST
Where: In-person, Melbourne (Location TBC)
Investment: $650 AUD
Facilitated by Andrew Murphy

Format

Deep dive into the framework
Solo and group activities
Q&A with Andrew