Ireland has excellent AI awareness resources. That's different from what boards and leadership teams need when making decisions they'll be accountable for. The distinction matters — and it's rooted in experience, not credentials.
Ireland has built a genuinely strong ecosystem of AI awareness over the last few years. Events, workshops, webinars, content programmes — there are real resources for organisations trying to understand what AI is, what it can do, and where to start. That infrastructure has value. It has brought AI literacy into organisations that would otherwise be years behind.
But awareness and advisory are different things. The distinction is not about credentials or status. It is about what happens when the stakes go up.
When awareness is enough
If a leadership team is trying to understand whether AI is relevant to their business, what tools their competitors are using, or how to begin an internal conversation about AI adoption — awareness content and education programmes are exactly what they need. They are accessible, practical and appropriately scoped.
The same is true for individual contributors trying to get more out of the tools already in their stack. A workshop on how to use Copilot effectively, a course on prompt engineering, an event on AI trends in your sector — all genuinely useful.
When something more is required
The picture changes when the decision carries material weight.
A leadership team considering a six-figure AI investment that will change how the organisation operates needs someone who has made those decisions before — and carried the consequences. Not advised on them from the outside. Made them, implemented them, defended them when things went wrong.
A board approving an AI system in a regulated environment needs someone who has sat on the other side of that table — who knows what a non-executive director can realistically absorb in a two-hour session, what questions to ask management, and what accountability looks like when an AI system causes a problem the board didn't anticipate.
An SME leadership team trying to decide between three competing AI platforms, each backed by vendor marketing that all sounds the same, needs someone with the pattern recognition to see through it — built across multiple technology cycles, not just this one.
What two decades of enterprise technology leadership changes
There is a specific kind of knowledge that comes from running enterprise technology at scale over a long period. Not advising on it. Running it.
When you have been the person responsible for technology outcomes across thousands of organisations — as COO for Microsoft Enterprise across Western Europe — you develop a different relationship to risk. You have seen what implementation looks like when it works and when it fails. You know what vendor commitments are worth in practice versus in pitch. You have managed the gap between what a technology was supposed to do and what it actually did, at a scale where that gap has real consequences.
That pattern recognition does not come from attending the same conferences and reading the same reports everyone else reads. It comes from accountability. From being the person whose name is on the outcome.
What board experience specifically adds
Running enterprise technology is one thing. Sitting on the board of an organisation as it navigates governance decisions is another.
As a Non-Executive Director at Dublin Airport Authority and Tailte Éireann, the questions I face are the same ones I am asked to help other organisations answer: how does a board exercise meaningful oversight of something as technical as AI without becoming dependent on management for interpretation? How do you ask the right questions without technical expertise? What does the EU AI Act actually require of directors, as distinct from management?
These are not theoretical questions. They come up in real board meetings with real consequences. That experience shapes what advisory looks like — it makes it specific to how governance actually works in practice, not how it is supposed to work in a framework document.
What building AI companies adds
The third strand is what comes from building AI-native businesses from the ground up. As a startup CEO twice over, the view of AI implementation is grounded in what it actually takes to get AI to work inside an organisation — the integration problems, the adoption challenges, the gap between demo and deployment, the cost of getting it wrong when you have limited runway.
For SME leadership teams in particular, this matters. The challenge for a 50-person professional services firm is not the same as the challenge for a 5,000-person enterprise. The budget is different, the risk tolerance is different, the implementation capacity is different. Advisory that does not account for that reality is not advisory — it is a framework written for someone else's problem.
The practical difference
When a leadership team engages with Acuity AI, the starting point is not a standard framework applied to their situation. It is a diagnostic — built around their actual workflow, their actual risk exposure, and their actual capacity to implement change.
The recommendations that come out of it are grounded in what the evidence shows, not what vendors are promoting. And they come from someone who has operated at the level where those recommendations carry weight — and who therefore applies the same standards to their advice that they would apply to any significant operational decision.
That is what separates advisory from awareness. Not a credential. A different relationship to accountability.