- Start with the business objective, not the tool. "We should use AI for this" is not an objective. "Cut invoice processing time from four days to one" is.
- Prioritise use cases by value, feasibility, and risk together. The most exciting use case is rarely the right one to build first.
- Data readiness is the most common blocker, and the one organisations check last instead of first.
- A pilot has a defined scope, a success threshold agreed in advance, and a rollback plan. Without all three, it is not a pilot, it is a soft launch.
- Test AI outputs against edge cases and adversarial inputs before wider rollout, not just the cases that made the demo look good.
- Human oversight has to be designed into the new process from the start. Bolting it on after deployment produces oversight in name only.
- Measure the business outcome the project was built to change. Adoption and usage numbers are not evidence of value on their own.
AI adoption and AI implementation are not the same problem
Most AI guidance available today, including our own AI Governance guide, addresses AI adoption: staff already using ChatGPT, Copilot, or Gemini, with the organisation needing an inventory, a policy, and a set of controls to catch up with a reality that has already arrived. Adoption governance matters and does not go away once you implement AI deliberately. But it answers a different question to the one this guide covers.
AI implementation is what happens when an organisation deliberately builds AI into a specific business process, system, or product, rather than staff picking up general-purpose tools on their own initiative. Examples: automating first-line support triage, adding AI-assisted document review to a legal process, building AI into a product feature customers pay for. Implementation carries every governance requirement adoption does, plus a set of steps adoption does not need: a business case, use case selection, a data readiness assessment, a pilot, testing against failure modes, and a way to measure whether the thing worked.
Treat implementation as a sequence, not a single decision. Skipping straight from "we picked a use case" to "it is live in production" is where most AI projects that fail actually fail, and the failure usually traces back to a step in the middle of this guide, not the AI model itself.
This guide covers one use case end to end, from business case to a measured result in production. It does not replace ongoing AI governance: the policy, tool register, and vendor oversight in our AI Governance guide keep applying once this system is live, and that guide is where the next use case's vendor due diligence, risk classification, and oversight design should start.
The twelve steps
Implementing AI comes down to twelve steps. We cover them in three companion guides.
Choosing AI use cases and checking data readiness covers steps 1 to 3: setting a measurable business objective, finding and ranking use cases, and checking whether your data can support them.
AI vendor selection, risk assessment and pilots covers steps 4 to 7: choosing the technology, architecture and vendor, assessing the risks, confirming the legal and regulatory requirements and running a controlled pilot.
Testing, rolling out and monitoring AI systems covers steps 8 to 12: testing the system properly, preparing your people, building it into business processes, setting up human oversight and measuring business results.
Your first 90 days
A first AI implementation feels large as a single project and manageable once sequenced. The aim by day 90 is a single use case either live in production with a measured result, or stopped with a clear, documented reason why. The 90-day timeline is illustrative, not a deadline: regulated or safety-critical projects will often need longer for testing, legal review and approvals.