Why a top-down AI mandate backfires, and the channel that already carries weight.
Most of my team has adapted to working with AI. There are a couple of holdouts, and underneath that there’s a real current of fear in part of the population we build for, a sense that AI is here to take their responsibilities away. The question I’ve been sitting with: how do you move adoption across an org without making that fear worse?
A month ago my instinct was to ask our CEO to make it a top-down mandate, reinforced by the other executives. I’ve changed my mind.
Why a mandate backfires
A mandate makes the scary thing scarier. When the message that you need to change how you work arrives as a directive from the top, it compounds the Sunday-night dread. It lands as “this is happening to you” rather than “I’m doing this with you, and how can I help you get there?” For people who are already anxious, top-down is close to the worst possible delivery, because it removes the one thing that makes change tolerable, which is feeling like someone is in it with you.
Use the channel that already works
Our engagement data says the same thing every year. The single highest factor, consistently, is the relationship with the direct manager. We already know, from trending data we trust, that manager interaction is one of our strongest suits. So why would we route the hardest change we’ve asked of people through anything else? The move is to invest in frontline managers, my direct reports, and equip them to have these conversations one on one, with an intimacy a company-wide directive can’t carry. You meet the energy where it already exists. You can’t manufacture it from the top.
The honest hard part is that this is art, not a checklist. I can’t hand a manager the bullet points for “make your report comfortable adopting AI.” What I can give them is the questions, and a way to think about it. That’s harder to scale than a memo, which is exactly why it lands. The thing that doesn’t reduce to a slide is the thing people actually respond to.
The teachable part
Before you escalate a sensitive change to the highest authority you can find, check which relationship in your org actually carries weight. Pushing hard change through a low-trust channel when a high-trust one is sitting right there is a routing error. Making it official and top-down feels like taking it seriously. With anything people are afraid of, seriousness looks like proximity, not altitude.