is not a strategy.
It's a budget.
AI initiatives ≠ AI strategy.
Since 2023, most organisations have launched AI initiatives: pilots, proofs of concept, tool subscriptions. Some appointed a Chief AI Officer. Others produced an AI roadmap. Almost none built a real AI strategy.
The difference is fundamental. A list of initiatives answers: "What are we doing with AI?" A strategy answers: "Why, how, and in service of what competitive position?"
Why it fails : systematically.
Confusing AI adoption with competitive advantage. Deploying AI is not an advantage : everyone is doing it. The advantage comes from how you decide, which dependencies you avoid, and which capabilities you actually build.
Three questions an AI strategy must answer.
Not in general. For your organisation, your business model, your specific constraints. A strategy that doesn't answer this for your specific case is not a strategy.
Not all dependencies are equivalent. Some are reversible at reasonable cost. Others lock you in for 5 to 10 years. An AI strategy makes explicit which dependencies you choose to accept.
Control over critical decisions, data, and the ability to exit vendor relationships. An organisation that cannot answer these questions does not control its AI strategy : it is subject to it.
The right time to build the strategy is before.
Most organisations start thinking about AI strategy after accumulating dependencies. They end up managing constraints rather than building a position. Decisions made in the first 12 to 24 months of AI deployment structure the organisation for 5 to 10 years.