Boards are asking about AI at almost every meeting now, and the questions are getting sharper. “What’s our AI strategy?” has turned into “What are we spending, what have we got for it, and what could go wrong?” Leaders who answer with enthusiasm instead of specifics tend to lose the room.
This post gives business leaders a set of AI board talking points for those conversations: the questions directors usually ask, how to answer them honestly, and the evidence worth bringing.
AI board talking points: the questions boards usually ask
| Board question | What a strong answer includes | What to avoid |
|---|---|---|
| What’s our AI strategy? | Two or three named business problems, each with an owner and a measure of success | A list of tools or a vision statement |
| How much are we spending, and on what? | Spend split by use case, including people, licences, and usage costs | A single “AI budget” number |
| What have we got for it so far? | Results against the measures you set, including what didn’t work | Pilot counts or adoption numbers alone |
| What are the risks? | The specific risks for each use case and the control for each | “We take responsible AI seriously” |
| Are we falling behind competitors? | What competitors have actually shipped, and where you’re deliberately not following | Fear of missing out as the reason to spend |
| Do we have the skills? | Which roles are trained, which aren’t, and the plan | Hiring one AI leader as the whole answer |
Talking point 1: Most AI projects fail for organizational reasons
This is the single most useful fact to bring to a board, because it reframes the conversation away from technology. A 2024 RAND study, based on interviews with experienced data scientists and engineers, found that by some estimates more than 80% of AI projects fail, and that the most common root causes were organizational, starting with leaders misunderstanding or miscommunicating the problem the AI was meant to solve.
What to say: our approach puts the business problem, ownership, and stage gates first, so we stop weak projects early rather than late.
Talking point 2: Buying often beats building, but not always
In coverage of MIT’s 2025 study of enterprise generative AI, buying tools from specialized vendors and working with partners was reported to succeed about 67% of the time, against roughly a third of that for internal builds. The sample was small, so treat it as a direction rather than a rule.
What to say: we build only where it gives us an advantage or where data can’t leave our environment. Elsewhere we buy, and we’ve trained the people who evaluate and integrate what we buy.
Talking point 3: Risk is managed per use case, not per company
Boards worry about AI risk in general terms. It’s more convincing to show that risk is assessed for each use case. A practical structure is the NIST AI Risk Management Framework, which organizes the work into four functions: govern, map, measure, and manage.
| For each use case, be ready to state | Example |
|---|---|
| What could go wrong | The assistant gives a customer a wrong refund policy |
| How likely and how costly | Low frequency, moderate cost, reputational impact |
| The control in place | Answers come only from approved policy documents; refunds above a threshold need human approval |
| How you’ll know it’s working | Weekly sample review and an evaluation set rerun on every change |
If you operate in Europe or sell into it, also be ready to say how your use cases are classified under the EU AI Act, whose obligations are being phased in over several years.
Talking point 4: Spend should follow stage gates
A board is far more comfortable approving AI spend in stages than in one large commitment.
| Stage | What it must prove before the next | Typical spend |
|---|---|---|
| Proof of concept | The approach can work on real examples | Small, time-boxed |
| Pilot | Users adopt it and the measure moves | Moderate, limited users |
| Production | It holds up at scale, with risk controls and an owner | Larger, ongoing |
What to say: nothing moves to the next stage without meeting the criteria we agreed in advance, and we’ve stopped projects that didn’t.
Talking point 5: Skills are a board-level risk
If leaders can’t judge AI proposals, every other control is weaker. Say which roles have been trained, starting with the people who approve AI spend, and what the plan is for the rest. A short readiness score, such as our AI transformation readiness self-assessment, gives the board a baseline to track over time.
A one-page board update
| Section | Content |
|---|---|
| Portfolio | Each use case, its stage, owner, and measure |
| Results | Movement on each measure since last update |
| Spend | Actual vs plan, by use case |
| Risk | New risks, incidents, and controls changed |
| Decisions needed | What you’re asking the board to approve or stop |
Ending with the decisions you need is what turns a status update into a useful board conversation.
Preparing for these conversations
AgileFever runs a course on this, so take the suggestion with that in mind.
AI Transformation for Business Leaders covers use case prioritization, business cases with stage gates, governance, vendor evaluation, change management, executive reporting, and why AI projects fail, over 16 hours with no coding. The final project is presenting your own AI transformation playbook to a mock executive panel, which is close practice for a real board. The price is $1,000 in the US or ₹65,000 in India.
Additional discounts are available. Contact us to know more.
Sources
RAND, The Root Causes of Failure for Artificial Intelligence Projects (2024); Fortune on MIT NANDA’s 2025 report; NIST AI Risk Management Framework.
