While organizations stall on technical implementation, their teams are forming habits that will be very hard to break later.
We hear a version of the same story from organizations across Europe. The AI tools have been purchased. The technical project is underway. And until the infrastructure is ready, the plan is to wait. Train the people later, once there is something concrete to train them on. Address the human side once the technology side is settled.
We understand the logic. We disagree with the conclusion. In the time organizations spend waiting for technical implementation to stabilize, something is already happening to their people, and it rarely works in their favor.
What Happens to Teams While They Wait
When organizations delay the human side of AI preparation, they do not get a clean slate to work with later. They get a workforce that has already adapted, just not in the way leadership intended.
People facing uncertainty without direction do not stay still. They find their own answers. Some start using AI tools on their own, outside any shared governance or practice. Others disengage, deciding that AI is not relevant to their work until someone tells them otherwise. A smaller group develops real anxiety about what the transition means for their role and their future. By the time the technical implementation is ready, the team has already formed its relationship with AI. The question is whether that relationship was shaped by the organization or left to chance.
The habits formed during this waiting period are the ones that will be hardest to change. Unguided AI use produces inconsistent outputs, erodes trust in the technology, and creates exactly the kind of fragmented, ungoverned adoption that technical implementation was supposed to prevent.
The Preparation That Does Not Require the Technology to Be Finished
There is a significant amount of human preparation that can happen before a single workflow is automated. None of it requires the technical infrastructure to be complete.
Leaders can clarify what AI will and will not change about how their teams work, before the anxiety fills that gap with speculation. Managers can begin building the habits of structured AI use: how to evaluate outputs critically, how to maintain quality standards, how to collaborate around AI-generated work rather than defaulting to individual workarounds. Teams can start developing a shared language for what good AI-assisted work looks like in their context.
This preparation does not depend on knowing every detail of the final implementation. It depends on taking the human dimension seriously enough to start now. The organizations that do this consistently report a smoother transition when the technology is ready, because their people are already oriented, already practicing, and already aligned on what the new way of working looks like.
The Real Cost of Waiting
The argument for waiting is usually framed as caution. Train people on something real, not something hypothetical. Avoid creating confusion before the tools are in place. This framing treats preparation as a downstream activity, something that follows implementation rather than enables it.
What it misses is the cost that accumulates during the wait. Cognitive fatigue builds in teams that are navigating uncertainty without support. Trust erodes when employees sense that the organization has not thought through what this transition means for them. And the longer poor habits go unaddressed, the more effort it takes to replace them with better ones.
We have worked with organizations that arrived at their technical go-live with disengaged teams, fragmented informal practices, and leaders who had no shared framework for what they were trying to achieve together. The technology was ready. The people were not. Getting them ready after the fact cost far more than preparing them before would have.
Starting Before You Think You Are Ready
Preparation does not require a finished product. It requires a decision that the human side of this transition is worth investing in now, before the pressure of a go-live forces the conversation.
The organizations that navigate AI transitions well tend to have one thing in common: they treated readiness as something to build, not something that would arrive automatically once the technology was deployed. They started conversations with their teams early. They addressed the anxiety directly rather than waiting for it to surface as resistance. They gave managers the tools to lead through uncertainty rather than leaving them to improvise.
If your technical implementation is still months away, that time is preparation time, and it is available right now.