What Should I Tell My Board About Our AI Strategy?
Last updated: May 14, 2026
Boards want to know three things: are we at competitive risk, what's the investment required, and who owns this. Have those answers ready before anything else. What boards don't want is an AI explainer, a technology overview, or a slide about the history of large language models. They want to know whether you have a plan, whether someone is accountable for it, and whether the organization is exposed if competitors move faster.
Why Is This Harder Than It Looks?
Most AI board presentations fail because they're designed for the wrong audience. The executive who prepared the presentation understands the technology landscape and wants to demonstrate that understanding. The board wants to evaluate risk and resource allocation. Those are different conversations.
There's also an awkward middle ground many executives find themselves in: too much AI activity to report nothing, not enough proven results to report success. Presenting that position honestly — here's what we've tried, here's what we've learned, here's what we're betting on next — is harder than presenting either a success story or a blank slate.
The board is also watching how you handle uncertainty. AI moves fast and the honest answer to many questions is "we don't know yet." Executives who overstate certainty about AI outcomes are creating a credibility problem with a group of people whose job is to stress-test claims.
What Actually Works
Lead with the competitive assessment, not the technology. The first question to answer is whether your organization is at competitive risk from AI. This doesn't require predicting the future. It requires an honest current-state read: are your primary competitors investing in AI, and does that investment appear to affect their cost structure, delivery speed, or client experience? Start there. The board can evaluate risk. They can't evaluate a technology overview.
Bring one proof point, not a portfolio. If you've run a pilot, report the results honestly — including what didn't work. One specific workflow, one specific team, one before-and-after metric. A single honest data point does more for your credibility than five optimistic projections. If you haven't run a pilot yet, be direct about that. "We're in the planning stage" is a defensible position when paired with a specific plan.
Answer the ownership question before they ask it. Who is accountable for AI outcomes in your organization? This is the question boards ask and most executives can't answer cleanly. "It's a cross-functional effort" is not an answer. Name a person, name their authority, name how they'll be measured. If you don't have that answer, identify it before the presentation. A board will forgive an early-stage initiative. They will not forgive not knowing who owns it.
Be explicit about the resource request. What do you need, why, and what does success look like if you get it? Boards approve resource requests when they understand the hypothesis being tested and the criteria for whether it worked. "We need budget to invest in AI capabilities" fails both tests. "We need $X to run a structured pilot on workflow Y with team Z, and we'll measure success by outcome W at 90 days" passes both.
The Thing People Miss
The board is usually further behind on AI than the executive team realizes. The instinct is to present to a sophisticated audience. The reality is that board members have varying levels of AI literacy and almost all of them have questions they haven't asked yet.
Opening the floor for questions — genuinely, not as a formality — often surfaces the concerns that actually matter: data security, talent implications, regulatory exposure, competitive positioning. Those conversations are more valuable than any presentation you can give. Design time for them.
And if a board member asks a question you don't know the answer to, say so. "I don't know, but I'll find out and come back to you" is a credible response. An uncertain answer delivered confidently is a credibility problem that will resurface at the next board meeting.
What This Looks Like in Practice
Executives CoCreate works with often come to board presentations with well-structured pilots and poorly structured narratives. The pilot is working. The story doesn't land.
The restructuring is almost always the same: lead with risk, not capability. Lead with what you own, not what you're exploring. Lead with a proof point, not a roadmap. The board doesn't need to understand AI. They need to understand whether you're managing the risk well, whether someone accountable owns the outcome, and whether the investment is sized appropriately for what you're trying to learn.
When the narrative needs tightening before a board readout, CoCreate lists narrative and facilitation support alongside its other services.
Related Questions
If you have a board presentation coming up and want to pressure-test the narrative, let's talk.