Before I said anything about AI, I asked a room of 100 salespeople a single question. It was the first session after lunch at a leading Australian media company’s national sales conference in Sydney, an AI working session sitting inside a day built for pipeline and performance rather than workshops. I asked the room what their honest reaction had been when they first saw AI on the agenda that morning.
Nobody answered out loud, but the room did not need to. You could read it: genuine curiosity, mild dread, and a lot of people somewhere in between. It is close to the most accurate summary of where most Australian teams sit with AI right now, whatever industry they work in.
I opened with a different company’s story before turning to theirs. In 2018, Starbucks posted four consecutive quarters of sales decline, and the cause was not a shortage of technology or data. They had both. What they had not built were the human conditions that make access actually count for something. That distance has a name. We call it the Integration Gap: the space between having AI access and actually seeing it work consistently across a team. Most teams never close it, and the reason is rarely the tool sitting in front of them.
Three conditions close that gap, and I have watched each one play out with real clients. The first is permission. A specialist insurance brokerage had staff using AI unevenly, not out of reluctance, but because nobody had told them clearly whether they were allowed to. Once leadership said yes, usage followed almost immediately. The second is skill. Some teams are handed a login and left to work out the rest on their own, and the tool sits idle, not because people resist it, but because access was never the same thing as knowing how to think alongside it. The third is culture. At Gatehouse, shadow AI, people quietly using tools leadership could not see, disappeared once the culture began rewarding experimentation done in the open rather than punishing it.
When permission, skill, and culture are all in place, the technology tends to look after itself. Miss any one of them, and it will not matter how capable the tool is.
None of that lands if a room is still holding real objections, so I addressed the three I hear most often before moving on to anything practical. AI will take my job, when in practice it takes tasks rather than judgement, and hands time back instead. I’m not a tech person, when the truth is that if you can write a brief, you already have what this requires. We tried this before and it didn’t stick, which is usually accurate, because the conditions were not there the first time. Naming an objection out loud tends to do more work than talking around it.
Then came the exercise. Ten teams were given thirty minutes, a sheet of A3 paper, and markers, along with a single brief: pick a task you do every week, and work out where AI could sit inside it.
The shift in the room happened faster than I expected. People stopped talking about AI as an abstract idea and started talking about their actual Tuesday, naming specific tasks and specific frustrations, the parts of the week that quietly eat time that could go somewhere better. The winning team had mapped a task that sits at the start of almost every project, cross-referencing information and pulling out what matters, done the same way every time. They were precise about what AI could take on and exactly where human judgement needed to stay.
After a year doing this work inside organisations, the pattern holds. People do not resist AI because they are afraid of the technology. They resist it because nobody has made it feel relevant to the work they actually do on a Tuesday morning, or because they have not been given permission to experiment yet. Give a room thirty minutes, a real brief, and something genuinely at stake, and most of that resistance disappears on its own.
If your team is sitting somewhere between AI access and actual adoption, the gap tends to close for the same two reasons every time: people can see how it connects to their real work, and they have been given permission to try. If that is the conversation your leadership team needs to have, get in touch.