Why we don’t do “AI strategy”
Strategy decks don’t ship. Outcomes do. A short manifesto.
A short manifesto
We do not write AI strategy decks. We do not run AI maturity assessments. We do not produce AI roadmaps. We have nothing against any of these on principle — we just find that the act of writing them rarely correlates with the act of shipping AI.
What we do instead
We start with the use-case that has the highest ratio of measurable value to effort, and we ship it in production within 90 days. Once it is live and producing the metric, we earn the right to do the next one. The pipeline of “next use-cases” emerges from the act of shipping, not from a deck.
Why this works
AI in 2026 is operationally hard, not architecturally hard. The bottleneck is the discipline to operate models in production, not the design choices upstream. Strategy decks describe the design choices; they do not describe the discipline.
When strategy decks make sense
When you are seeking board approval for a multi-year programme that requires capital. They are useful artefacts for that conversation. They are not useful artefacts for shipping use-cases.
Related articles.
Three patterns that make AI agents production-safe
4 minThree patterns that make AI agents production-safe
Read articleDesigning for the 3am page
6 minDesigning for the 3am page
Read articleWhy mainframe modernisation finally pays back
6 minWhy mainframe modernisation finally pays back
Read articleWant to discuss this?
A senior partner will respond within one business day.