Why many AI roadmaps are platform launch plans.
The typical AI transformation roadmap reads like a vendor implementation guide. It starts with a technology audit, moves through vendor selection and licensing, proceeds to deployment and training, and closes with a dashboard to track utilization. The sequence assumes the hard part is choosing and configuring the right technology.
That assumption fails in practice. The hard part is changing how people work, and deciding which behaviors the organization will reward.
When a roadmap begins with platform selection, it bakes in the wrong sequence. By the time the licenses are bought and the training is scheduled, the organizational decisions that determine adoption have already been made, or skipped.
You can see the assumption on the roadmap slide itself. The horizontal bars run across four quarters: select vendors, pilot, scale to the business units, realize value. Near the bottom, in a thinner bar, sits change management.
That thin bar is an accurate picture of the budget and the attention behind it, and an organization executes the plan it can see. The AI arrives and the training completes on schedule, and how the work gets done barely changes.
The record here is uncomfortable. MIT Media Lab's Project NANDA found in mid-2025 that about 95% of enterprise generative AI pilots showed no measurable P&L impact, a preliminary, contested figure from a report that is not peer-reviewed and partly self-reported, but a recognizable one. Those organizations had roadmaps, and many of them will have hit their milestones.
One more assumption is buried in a single timeline: that the organization is one thing, with one schedule and one go-live. In practice it is dozens of teams with dozens of different relationships to the work and to the leadership introducing it. Some are already ahead of the roadmap on personal accounts. Some will read the roadmap as a threat assessment aimed at them.
A real AI transformation roadmap sequences the work in the order that produces adoption: people before process before platform. It starts with ground truth about who will use AI and what mistrust already exists. It maps the processes worth redesigning before it picks the software to redesign them with. And it treats platform selection as the final step.
People before process before platform.
People-first means starting with an honest read on readiness and on the skills people still lack. Before any workflow gets mapped or any AI gets piloted, the roadmap must answer: which teams will adopt quickly, which will resist, and why.
That requires a diagnostic. A survey tells you what people say they think; a diagnostic gets at what they believe about their job security and whether the organization will punish them for saying the AI does not work.
The AI Profit Ready Assessment is a fast first read: eight questions, about two minutes, and the result shows straight away your stage (Foundation, Optimization or Innovation), a read on Empowered People, Efficient Process and Profitable Platform, and the first move to make. With ground truth in hand, the roadmap can sequence adoption by readiness.
Process-second means redesigning workflows around how people will use AI day to day, which is not how the vendor demo shows it. Platform-first roadmaps skip this step entirely. They assume that once people are trained, they will figure out how to integrate AI into their daily work. That assumption produces the most common failure mode: everyone is trained but nobody changes behavior, so the licenses sit unused.
A process-first roadmap identifies a handful of high-value workflows where AI can demonstrably reduce friction or increase output. It maps those workflows in detail, including exactly where AI enters the process and what success looks like in concrete terms. Only after that work is done does platform selection begin.
Platform-last means choosing technology based on the workflows you have already committed to redesigning. By the time platform selection starts, the roadmap already defines which capabilities and integrations matter, and which teams will pilot first. The platform decision becomes a procurement exercise.
The three-stage sequence.
A people-first AI transformation roadmap moves through three stages: ground truth, redesign, and adoption. Each stage has a clear output that gates the next one. No stage begins until the prior stage is complete.
Ground truth is the discovery stage. It answers: who will adopt quickly, who will resist, and why. The output is a segmented readiness map that groups the workforce by how likely each group is to adopt.
High-readiness teams become early pilots. Low-readiness teams get targeted change support before they touch AI. The AI Profit Partnership runs this stage for one leader and a team of up to 20 over 90 days: it researches how the team works today, finds where the leader's view and the team's do not match, and ends in a plan for the year ahead.
Redesign is the workflow stage. It answers: which processes will we redesign, in what order, and what will success look like. The output is a prioritized backlog of a handful of workflows, each mapped in detail, with clear success metrics and a named owner.
This stage can run before the AI platform is selected. What it needs is clarity about what work will change and how the organization will measure that change.
Adoption is the platform and launch stage. It answers: which AI will we use, who will pilot it, and how will we scale from pilot to standard practice. The output is a phased launch plan that sequences adoption by readiness.
High-readiness teams pilot first. The organization learns from their experience and refines the workflows, and only then expands to lower-readiness groups.
The team that pilots first is worth choosing deliberately. Look for a team with existing pull toward AI and a manager who frames it as relief. Their workflow should produce results people outside the team will see. Everyone else in the organization hears about that first experience before they hear anything official about the program.
Proof at the end of this stage has to be defined honestly, because deployment and training are both easy to declare and neither one is proof. The stage is complete when the team would argue to keep the AI if it were taken away, and when there is a number attached that a skeptic outside the team would accept. That point cannot be scheduled precisely, which is why the roadmap should hold the next stage behind it.
How to choose the right starting point.
Not every organization should start at stage one. Some have already run a diagnostic and know where resistance sits. Some have already mapped key workflows and are ready to pilot. The right starting point depends on what you already know and what you are still guessing about.
Start at ground truth if you cannot name the specific teams that will resist adoption, or if senior leadership is divided on whether the problem is cultural or technical. Start here too if past change initiatives died in the middle without clear cause, or if the organization has spent on AI and adoption is flat but no one can explain why in concrete terms.
Start at redesign if you already know where readiness and resistance sit and which teams will adopt early, with leadership aligned on the people problem. Start here if the open question is which workflows are worth redesigning first.
Start at adoption if workflows and success metrics are already defined, and the only open question is which platform to use and how to phase the launch. Start here if the organization has done the hard work of naming what will change and is ready to execute.
Many organizations should start at ground truth. The ones that think they should start at redesign or adoption discover, once they run a real diagnostic, that they were guessing about readiness and mistrust. Better to know that before the platform is bought.
One piece of work sits ahead of all three starting points: the executive team's own alignment. If the leadership group cannot give the same answer to what this transformation is for, that conversation is where the roadmap begins. Skipped, the disagreement moves down the organization as mixed messages, and managers read the ambiguity correctly and wait.
What a finished roadmap delivers.
A finished AI transformation roadmap is a sequenced set of decisions, each with a clear owner and a clear output. The roadmap answers what the organization will learn and redesign, and in what order it will launch. It takes the questions in the order that reduces risk and improves the odds of real adoption, leaving some for later.
Treating each milestone as a decision point is what makes that sequencing hold under pressure. On the Gantt chart version, a milestone is the date on which something is declared done. Here, arriving at one forces a choice: continue as designed, adjust, or stop.
What did the first team teach us about the design? Does the next wave need a different product or a different conversation with managers? What do we now know that the original plan could not have known?
A roadmap built this way has somewhere to put what each stage teaches it. One built on fixed dates does not, so it keeps its shape while the reporting stays green and the work stays the same.
The deliverable is a document the CEO and CHRO can take to the board. It names where readiness falls short and the workflows that will change, in launch order. It specifies how the organization will measure success at each stage. And it makes a single, defensible claim: this is the sequence that produces adoption.
The roadmap also defines what the organization will stop doing. Many AI transformation plans are additive: they pile new software and new dashboards on top of existing work. A real roadmap names what gets cut and what the organization will stop measuring. Without subtraction, the roadmap is just more work for the same people.
Common roadmap failure modes.
The most common failure mode is skipping ground truth and moving directly to platform selection. The organization picks a vendor and buys the licenses, then discovers months later that middle management never believed the AI would help. By then the budget is spent and the board is asking why ROI has not materialized.
The second failure mode is designing the roadmap around vendor timelines and ignoring organizational readiness. The vendor has a fixed launch timeline. The organization has a workforce that has watched earlier transformation initiatives fail and does not believe this one will be different. The roadmap that follows the vendor timeline will hit every milestone and still produce no adoption.
The third failure mode is treating an ongoing capability build as a one-time training event. The roadmap schedules a short training session, declares the workforce trained, and moves to launch. Months later nobody is using AI, and the explanation offered is resistance to change. A short session does not build capability, and the roadmap never planned for ongoing support.
The fourth failure mode is delegating the roadmap to IT or HR without executive ownership. The CTO or CHRO builds a credible plan, but the CEO does not make a public commitment to the sequence or the timeline. Middle management reads that silence as permission to ignore the roadmap. The plan dies quietly, and the next board meeting asks why AI adoption is still flat.
Questions people ask.
How long does a full AI transformation roadmap take to execute?
The organization sets the duration. The sequence stays the same: ground truth first, then workflow redesign and pilot planning, then platform selection and phased launch. What stretches it is the number of workflows being redesigned and the distance between what leadership believes and what the workforce can execute. Skipping ground truth moves that work to the end, after adoption has already stalled, and the sequence gets run again from the start.
Can we run ground truth and workflow redesign in parallel?
No. Workflow redesign assumes you already know which teams will adopt or resist, and what mistrust exists. If you are still guessing about those factors, the workflows you design will not match how people work day to day or what they are willing to change. Ground truth must finish before redesign begins. The output of ground truth (a segmented readiness map) is the input to redesign.
What if we have already bought the AI platform?
Start at ground truth anyway. Readiness and workflow clarity, backed by change support, are what determine adoption. If the platform is already selected, the roadmap adjusts to map workflows around the AI's capabilities, but the sequence remains the same: ground truth, then redesign, then launch. Skipping ground truth because the AI is already bought is a common cause of flat adoption.
Do we need an external partner to build an AI transformation roadmap?
Many organizations need an external partner for the ground-truth stage more than for the roadmap itself. Internal teams struggle to get honest answers about fear and mistrust. Employees who suspect the AI initiative is a plan to shrink their team will not say so to their CHRO; an anonymous diagnostic is where that comes out. An external partner runs that diagnostic and hands the organization a clear read on readiness it can act on. From there, internal teams can handle workflow redesign and launch planning.
How do we measure progress on an AI transformation roadmap?
Measure the outputs of each stage. Ground truth measures the percentage of the workforce segmented by readiness and the clarity of the resistance drivers. Redesign measures the number of workflows fully mapped, with success metrics and named owners. Adoption measures behavior change and output improvement in pilot teams before scaling. Many organizations measure training completion and license utilization. Those are lagging indicators. They tell you adoption has already failed without telling you why.