A director I worked with described the problem better than most research can. She had read her company's AI strategy twice, attended both all-hands where it was presented, and taken notes at the off-site. She could recite the pillars. She understood the technology well enough. What she could not do was name a single thing her team should do differently by the following Monday. She was not confused about the content. She was confused about whether the strategy was ever intended to reach her team at all.
That confusion turns out to be rational. A 2026 survey found that three-quarters of executives privately acknowledge their company's AI strategy is "more for show" than actual operational guidance. The same research found 73% of CEOs reporting anxiety about that strategy and 64% worried about losing their role if the AI transition fails. What these numbers describe is not a technology adoption problem. It is a visibility problem: the document that satisfies the board was never designed to guide the people who have to execute it.
When the Audience Is the Board, the Strategy Is for the Board
There is a particular kind of document that organizations produce when external pressure arrives before internal clarity does. It has pillars and named owners and a two-year horizon. It probably involved a consulting firm. It passed through multiple review cycles and landed in a clean deck that the C-suite presented with confidence. What it does not contain is a clear answer to the question that every director and VP below the C-suite will eventually ask, which is: what am I supposed to do now?
AI strategy documents in 2026 are, in many organizations, exactly this kind of document. The pressure to have an AI strategy arrived from boards, investors, and the general ambient fear of being surpassed. The pressure to have a strategy that could actually guide operations arrived later, if it arrived at all. When the deadline is a board meeting and the audience is shareholders, what gets produced is something calibrated to satisfy that room. This is not cynicism. It is incentive alignment operating exactly as designed.
The problem with this is what happens next. A leader who knows the strategy is primarily a positioning artifact will eventually stand in front of the people who work for them and present it as operational guidance. That gap, between what they know privately and what they communicate publicly, is where organizational trust starts to hollow out.
The People Asked to Execute It Have Already Done the Math
When 29% of employees admit to actively working against their company's AI rollout, the standard interpretation is change resistance or poor communication. The more direct reading is that employees have correctly identified the strategy as incoherent, and working around it is the rational response to a plan that was never meant to reach them.
Workers under 30 report the same skepticism at even higher rates, with 44% acknowledging they are working against the rollout in some way. These are not people failing to understand the strategy. They have understood it quite well. They have watched the same pattern across multiple cycles: the announcement, the steering committee, the pilot that produced a report, the report that produced no second phase. Over time the pattern becomes legible. Organizations that produce strategic artifacts without operational follow-through are teaching their employees a very specific lesson about what announcements mean.
The aggregate cost of that lesson is visible in the data. Ninety-five percent of organizations report zero meaningful ROI on their generative AI investments. Fifty-four percent of C-suite executives say AI adoption is fracturing their organization. These are outcomes produced not by difficult technology or inadequate investment, but by strategies designed for audiences that will not be present during execution.
The Accountability Question Nobody Is Asking
AI strategies that work tend to share a quality that has nothing to do with technical sophistication. They are narrow. They are tied to a specific problem that was already costing something, to which AI happened to be a useful answer. They have a named person whose job is explicitly on the line if the strategy produces nothing. They are not usually described as transformations. They are usually described as solutions.
What most executive AI strategies are missing is not vision or investment. It is the moment when someone says, out loud, what they are personally accountable for and what failure looks like. Before that moment, the strategy is a presentation. After it, there is at least the possibility of execution. The failure to reach that moment is not accidental. A strategy built for a board audience does not benefit from naming failure conditions, because naming failure creates the possibility of accountability, and accountability is uncomfortable to perform in front of investors.
The ethics here are worth naming. When a leader publishes a strategy they know is designed primarily for external signaling, they are making a choice about what they owe the people they lead. The answer most organizations have arrived at, by negligence or by design, is that they owe them the performance of direction without its substance. The cost of that answer shows up gradually: in the 34% of C-suite executives who do not believe their own team is aligned on strategy, in the employees who have concluded the path of least resistance is to wait for the announcement cycle to end, and in the boards who are eventually handed results that match neither the strategy nor the investment.
The pattern has a parallel that predates AI. In "Agile Sucks! (When You Do It Wrong)," Zac Parker and James Wright document how roughly 70% of organizations using Agile frameworks report positive metrics while producing no real business outcomes. Announced transformations that satisfy the review audience without changing operational reality are not a new problem. The mechanics are worth understanding before you design your next one. <a href="https://a.co/d/bdUxZLw" target="_blank">Get the book here.</a>
Read Agile Sucks! (When You Do It Wrong) →