Every AI initiative eventually has to make it through a board presentation. And most board presentations on AI fail in one of three ways.

They lead with technology. They hide uncertainty. Or they promise a timeline that no one in the room actually believes.

All three mistakes do the same damage: they reduce your credibility as the person responsible for the initiative, which makes it harder to get the next approval you'll need.

What a good AI board brief looks like

The board doesn't need to understand the technology. They need to understand three things: the business problem you're solving, what it will cost to solve it (in time, money, and organizational attention), and how you'll know if it's working.

That's the whole agenda. Everything else is supporting material.

Lead with the problem, not the technology

The brief that earns respect starts with a clear problem statement: "We have $3.2M in annual revenue that's at risk because our proposal cycle is 22 days and our closest competitor's is 11." That's a business conversation. The board is equipped to engage with it.

"We're implementing an AI-powered workflow automation solution" is a technology conversation. Most boards are not equipped to assess whether that's a good idea, which means they'll either approve it on faith or reject it on instinct. Neither outcome serves the initiative.

Surface uncertainty explicitly

The best board presenters I've seen include a slide called "What We Don't Know." It names the three biggest uncertainties in the initiative — data quality, change management risk, or timeline — and describes how the team is managing each one.

This is counterintuitive. It feels like surfacing weakness. It's actually the opposite: it signals that you've thought rigorously about the risks, which is exactly what a board wants to see from an executive bringing a major initiative for approval.

Hiding uncertainty doesn't make it go away. It just makes you less credible when it surfaces in Q3.

Commit to a specific decision point

Ask the board to approve a 90-day evaluation — not a multi-year roadmap. At day 90, you'll return with results and a scaling recommendation. This framing does three things: it reduces the perceived risk of the approval, it holds the initiative accountable to a specific timeline, and it brings the board back into the conversation at the moment when you'll need their continued support.

Boards approve small bets with clear decision points far more readily than they approve large bets with vague outcomes. Use that.