Three Distinct Talent Needs
AI talent strategy requires clarity on three different populations, each with different development needs:
AI Fluent Workforce (Everyone)
The ability to use AI tools effectively in daily work: knowing which tasks AI helps with, how to prompt well, how to evaluate outputs, and when not to use AI. This is no longer a specialist skill — it's becoming a baseline professional competency, like using email or spreadsheets. Development approach: structured learning programmes, peer learning networks, embedded into onboarding and role development.
AI-Augmented Specialists (Functional Experts)
Domain experts in each function (finance, marketing, operations, HR, legal) who can identify the highest-leverage AI applications in their domain, evaluate domain-specific tools, and lead their function's AI adoption. These people combine deep domain expertise with high AI fluency. Development approach: domain-specific AI training, access to technical expertise, cross-functional AI communities of practice.
AI Technical Capability (Builders)
People who can build AI systems: machine learning engineers, data engineers, AI product managers, and the applied AI researchers who push the edge of what's possible. Development approach: hiring externally and/or upskilling existing data and software teams; requires a longer and more expensive development timeline than the other two populations.
The Build/Buy/Partner Decision
For technical AI capability specifically, organisations face a build/buy/partner decision with real trade-offs:
Build: Develop internal AI/ML teams. Highest long-term value and IP retention; requires 18-36 months to build meaningful capability from scratch; expensive and competes with tech companies for talent.
Buy: Acquire companies with existing AI capability. Fastest route to technical depth; cultural integration is the primary risk; expensive.
Partner: Work with AI vendors, consultancies, and specialist firms. Fastest time to capability; creates dependency; limits differentiation over time.
Most organisations need some combination. The strategic question is: which AI capabilities are core to your competitive differentiation (build these) and which are commodity infrastructure (buy or partner for these)?
Organisational Design for AI
Three organisational design questions matter for AI capability:
Centralised vs. federated AI teams: A central AI team provides consistency and efficiency but creates distance from business problems. Federated AI capability embedded in business units provides relevance but risks duplication and inconsistency. The hybrid — a small central team that sets standards and provides technical depth, with embedded AI practitioners in each major business unit — is increasingly the model that balances both.
Where does the AI product function sit? Who owns the AI product roadmap — technology or business? The answer shapes incentives and priorities significantly. Technology ownership produces technically excellent systems with variable business adoption. Business ownership produces strong adoption with variable technical quality. Joint ownership with clear accountability is hard to design but usually necessary.
How is AI fluency measured and rewarded? If AI competency is invisible in performance management, development, and promotion criteria, it will develop unevenly and slowly. Organisations that explicitly define and reward AI fluency — at appropriate levels for each role — develop it faster.