AI Questions Every Board Should Ask
About this resource
Boards are being asked to approve AI spending, absorb AI risk, and answer for AI decisions, usually on the strength of a presentation given by people with an interest in the answer. Most directors are reasonably uncomfortable with this and reluctant to say so, because the discomfort feels like a gap in their own knowledge. It is not. Board oversight has never required technical fluency in the thing being overseen.
This guide gives directors ten questions across strategy and value, risk and governance, workforce and capability, and evidence. Each one includes what a good answer sounds like and what should concern you, so a director can assess the response without assessing the technology. It adds seven answers that should prompt a follow-up, a workable cadence for what to review annually versus quarterly, and one question worth not asking in open session, because a single sentence from a board reaches the whole staff within a week.
Every one is answerable by a management team that has done the work and unanswerable by one that has not. That asymmetry is the entire value of asking.
How to use it
Ask the same small set of questions consistently rather than asking many questions once. Management teams calibrate to what the board asks about: a board that asks for evidence gets an organization that collects it, and a board that asks about progress gets an organization that produces activity. The questions are the governance. Accept an honest "we do not know yet" and require the answer to improve by the next meeting.
Inside the download
What problem, what was declined, and what happens if the technology stops improving.
Whether a written classification exists and whether staff know it without looking it up.
Whether management learned it by asking or is reporting an impression.
What would remain if the three people driving this left.
Common questions
Ten questions across four areas. Strategy: what problem are we solving and how would we know if we had solved it, what did we decide not to do, and what if the technology stops improving. Risk: what information can and cannot go into these tools and who enforces it, where does human review sit, and what is our vendor exposure. Workforce: what do our people actually believe and what would remain if the key people left. Evidence: what did we measure before we started, and show me one thing that is measurably different.
No. Board oversight has never required technical fluency in the thing being overseen. It requires the questions that reveal whether the people running it have thought it through, which is why each question in this guide comes with what a good answer sounds like and what should concern you.
Why are we behind our peers on this. That question reaches the whole staff within a week, stripped of context, and arrives as a threat rather than as governance. The same applies to any question implying headcount. If the concern is real, raise it with the chief executive directly.
Free. No email list, no follow-up sequence.
More from the resource library, chosen because they pair well with this one.
Why most AI return is undefendable, and the seven questions that have to be settled before any money moves.
Ten questions for directors who hold a duty of care and a duty to the mission, including where the freed capacity actually went.
What actually makes something an agent, why it changes the accountability question, and what to ask a vendor selling one.
Tell us a little about yourself and this document is yours. We don't have an email list. We collect this so we know who's finding our resources useful, and that's it.
You're downloading
this document
Your information is kept confidential and never shared with anyone.
