Before you green-light AI, answer these three questions
The boardroom AI decision looks simple. These three questions make it harder, on purpose.
Three questions every business leader should ask before going all-in on AI
There’s a pattern I keep seeing in boardrooms right now. Someone presents a slide deck showing what a competitor is doing with AI. The room gets uncomfortable. A decision gets made. Six months later, the organisation has a shiny new tool that nobody quite knows how to measure, a change management problem nobody anticipated, and a vendor invoice that felt more reasonable before the results came in.
AI adoption pressure is real. I’m not dismissing it. But pressure is a terrible basis for a capital decision, and right now a lot of organisations are confusing movement with progress.
Before you green-light a rollout, three questions are worth sitting with properly. Not as a checkbox exercise, but as genuine tests of whether the deployment makes sense.
What specific metric are we actually trying to move, and is AI the right tool to move it?
This sounds basic. It isn’t. Most AI business cases I’ve seen are built around capability (”we could automate X”) rather than outcome (”we need to reduce X cost by Y amount, and here’s why AI does that better than the alternatives”).
The arms-race dynamic makes this harder to see clearly. Every competitor announcement, every conference keynote, every LinkedIn post about someone’s 10x productivity gain creates a pull toward doing something rather than asking whether this particular something makes sense for your particular organisation.
So ask it plainly: what KPI are we moving, by how much, and by when? Then ask whether AI is genuinely the most efficient way to move it. Sometimes a better process does the job. Sometimes a cleaner spreadsheet gets you further than a six-figure contract. Sometimes the answer really is AI, but it’s a different tool than the one currently on the table.
If you can’t pass that test before signing, you’re spending money on the trend, not the outcome. And that tends to show up in the post-implementation review in ways that are hard to explain to a board.
Who in this organisation owns the hallucination problem?
This is the question I see skipped most often, and it’s the one that creates the most expensive problems down the line.
When a human employee makes a mistake, there’s a chain of accountability you can follow: a manager, a sign-off process. When an AI system produces a confident, detailed, completely wrong answer that ends up in a client report or a regulatory submission, that chain gets murky fast. And these systems do produce wrong answers. Not occasionally. Regularly. With no obvious tell that anything is amiss.
Two things need to be decided before deployment, not after an incident forces the conversation.
First: which department head carries the liability if the AI misleads a client, produces a biased output, or feeds incorrect data into a decision? “The vendor is responsible” is not an answer your regulator or your client will accept.
Second: does your team have the internal expertise to spot when the system is drifting or producing biased results, or have you effectively handed your critical thinking to a black box? This isn’t a theoretical concern. Models degrade over time. Data inputs shift. Outputs that were accurate in month one may not be accurate in month six, and if nobody is checking, nobody knows.
I’ve seen both questions left unanswered until something goes wrong. That’s a very bad time to start working them out.
What do your people actually do with the time AI gives back?
This is the question that separates organisations that get lasting value from AI from the ones that get a short-term efficiency spike and a morale problem they can’t quite explain.
If AI takes over 70% of a job that was previously repetitive, the freed-up time doesn’t automatically get redirected somewhere useful. It needs a plan. What does that person focus on now? Higher-judgment work? Client relationships? Problems that actually need human attention and experience? Or do they sit in a slightly reduced role, doing less of the thing that gave their work meaning, with no clear sense of what the organisation expects from them instead?
The engagement dip that follows poorly planned AI rollouts is real, and it’s predictable. People aren’t opposed to AI taking over repetitive tasks. Most of them would be relieved. What creates disengagement is the feeling that the human element of their work has been quietly removed with nothing put in its place.
The organisations that handle this well treat AI deployment as a reallocation decision from day one. They map out where freed-up human capacity will go before the tool goes live, not after. They’re explicit with staff about what changes, what doesn’t, and what the new shape of the role looks like. It’s not a complicated process. It just requires doing it on purpose rather than assuming it’ll sort itself out.
There’s a case for what some researchers call “slow AI” thinking here: the idea that the goal isn’t to replace human output as fast as possible, but to protect human judgment and redirect it toward the work that machines genuinely can’t do. Faster rollout doesn’t mean better outcome. The organisations that move carefully tend to show the most durable returns.
AI adoption in the right context makes strong commercial sense, and the performance gap between organisations that use it well and those that fumble the rollout is already measurable in some sectors. These three questions aren’t intended to slow things down. They’re the minimum due diligence that separates a deployment with a real return from one that looks good in a Q3 update and quietly gets deprioritised by Q1.
Ask them before you commit. It’s much easier than explaining the answers afterward.