Answer · AI Transformation
AI Implementation Roadmap: How to Build One That Survives a Quarter
Aiden Wayne · Updated August 17, 2026
Short answer
Sequence by dependency, not by enthusiasm
Most AI roadmaps are ranked by how interesting each item is. The order that actually works is the order forced by dependency: the data fix before the model, the workflow redesign before the automation, the definition agreement before the dashboard. Ranking by value alone puts item three first and then discovers it needed items one and two.
What each roadmap item must carry
- The workflow it changes, named the way the team names it.
- The current cost — time, error rate, cycle time, or revenue leaked.
- The change itself: redesign, automation, augmentation, or removal.
- One owner with the authority to change the process, not just the tool.
- The measurement and where it will be read from, agreed before build starts.
- The dependency it unblocks or is blocked by.
A 30/60/90 that holds
The purpose of the first 30 days is not value. It is establishing that a change can reach production at all. Companies that skip this spend two quarters in pilots because nobody ever tested the last mile.
| Window | What belongs in it |
|---|---|
| First 30 days | One workflow shipped end to end, however small. Proof the path from idea to production exists. |
| Days 31–60 | The dependency work the first release exposed, plus the second workflow. |
| Days 61–90 | Measurement in place, the third workflow, and a decision on what to stop doing. |
Set the measurement before you build
Agree the number, the source, and the reading cadence before the first line of work. Retrofitted measurement is always contested, and contested measurement is how good work gets cancelled. If a change cannot be measured in a system you already trust, either instrument that first or pick a different change.
Signs the roadmap will not survive
- Every item is a tool name.
- No item names an owner who can change a process.
- Nothing is scheduled to stop.
- Everything is scheduled in parallel.
- The measurement column is empty or says "efficiency".
Frequently asked
- How long should an AI implementation roadmap cover?
- Ninety days in detail, and a directional view of the next two quarters. Anything more detailed than a quarter out is usually rewritten before it is reached.
- Should the roadmap be organised by tool or by workflow?
- By workflow. Tools change during implementation; the workflow being improved and the number being moved do not.
- How many items should be in flight at once?
- One to two per team. Parallelism is the most common reason AI roadmaps deliver nothing in a quarter that would otherwise have delivered one thing well.