Your engineers hate your AI rollout. Another demo won’t fix it.I hear versions of this everywhere: in live Q&A, in leadership conversations, and from people working inside large organizations. Some employees are excited enough to rebuild their entire way of working. Some want nothing to do with AI. On teams larger than roughly 50 people, I expect to find people at every point in between.Leaders often treat that range as an adoption problem. Buy the tool, run the training, collect the use cases, find the enthusiasts, and push the usage number up.That sequence skips the question people are actually asking: if AI keeps getting better, what happens to me?They are asking whether the company wants more output or fewer people. They are asking which parts of their judgment will still matter, how a junior engineer will learn, whether the work they know will be respected, and what their job becomes when an agent can produce the first draft of code, analysis, or writing. If leaders cannot answer, people will supply their own answer from every layoff headline they have read.The fear isn’t abstract. It’s the ability to put food on the table. A national employment statistic doesn’t calm someone whose own company is talking loudly about efficiency and refusing to say what that means for headcount.This is what I tell leadership.Three things. First, make a public commitment to the people you have and be exact about what you can promise. Second, test one narrow use case tied to the bottom line and judge the finished work, not the usage. Third, show people the work on the other side of the transition: the roles, boundaries, systems, and human decisions you are actually building toward.That doesn’t guarantee agreement. A company can make a legitimate decision that AI fluency is now part of the job. An employee can decide that is not the career they want. But both sides deserve a real decision. “Use AI because AI is the future” isn’t one.This briefing covers:The employment commitment. What to say out loud about jobs, hiring, and careers, and the one-page version you can write this week.The role on the other side. How to name the work engineers move toward, instead of promising them “higher-value work.”The narrow pilot. One use case, the baseline that makes it real, and the three decisions to define before results arrive.What the evidence actually says. Why the Google and METR trials disagree, and what the sabotage statistic is really measuring.The Rollout Commitment prompt kit. Four prompts that interview you and write the commitment page, including the lines you aren’t ready to sign.