Where AI earns its place

Every board has an AI conversation running, and most have funded something: a pilot, a proof of concept, a partnership announced with some ceremony. The gap between those conversations and the balance sheet has a familiar shape — pilots that impressed, decks that circulated, and a technology strategy that still treats AI as an initiative rather than a capability. The missing artefact is rarely vision. It is rarely use cases either; most organisations are drowning in use-case lists. What is missing is a fundable path: a prioritised view of where AI earns its place in the operating model, what it costs to run properly, and what has to be true — in platform, data, people, and governance — for the value to actually arrive. "Earns its place" is deliberate framing. AI in the enterprise is not entitled to a place; it competes for one against every other use of capital and attention. A use case earns its place when three tests pass. The decision or process it touches has to matter at scale — automating something trivial produces trivial value at meaningful cost. The data underneath it has to be trustworthy enough to act on, not just to demonstrate with. And the organisation has to be able to absorb the change: a model that the business routes around is an expense, not a capability. Applied honestly, the tests make AI strategy a prioritisation decision first. Strategy means saying no — or at least not yet — to most of the list. Rank what remains by value against feasibility, where feasibility includes the unglamorous variables: the condition of the data, the integration reality, the regulatory exposure of the decision being automated. A short, ranked portfolio that the board actually understands beats a long list that flatters everyone's project. The second commitment is engineering. An AI strategy that does not commit to a platform is a wish. Models that matter run in production, which means deployment pipelines, monitoring, retraining, access control, and cost management — the machinery the pilot never needed. This is where the funding conversation has to be honest: the cost of running AI properly is the cost of the platform and the operating discipline, not the cost of the pilot that produced the demo. The third is governance, and for regulated entities this is now concrete rather than abstract. ISO 42001 gives AI governance a management-system shape an auditor can work with. The NIST AI RMF gives risk teams a shared vocabulary for AI-specific failure modes. And prudential expectations reach AI through the standards that already apply — operational resilience, information security, model accountability. The practical insight is about sequence: governance designed alongside the strategy is a design input, cheap and mostly invisible. Governance retrofitted after deployment is the most expensive kind of control there is — designed in, not bolted on, is a budget position as much as a principle. These three are one decision. A strategy that prioritises without committing to engineering is a deck. Engineering without governance is a liability accumulating interest in a regulated environment. Governance wrapped around use cases that never earned their place is theatre. Made together, they produce something a board can actually fund: a portfolio, a platform sized to it, and a governance design mapped to real standards — with a visible path from the first decision to a governed outcome, and the same senior people accountable across it. A practical place to start: take your current AI use-case list and apply the three tests — does it matter at scale, can the data be trusted, can the organisation absorb it. Expect the list to shrink sharply. That is not the exercise failing; that is the exercise working. The survivors are your AI strategy.