The Tools Are Ready. The Question Is Whether Your People Are.
Most AI programmes are designed around a technology timeline. Select the tool. Configure the platform. Build the integrations. Train the users. Launch.
The timeline makes sense on paper. Every milestone is actionable, measurable, and within the control of the project team. The problem is that it treats the workforce as a variable that can be addressed in the final stage, just before launch, with a training session and a support guide.
By the time the training arrives, the damage is often already done. Employees have been hearing about the AI rollout for months. They have formed opinions, anxieties, and assumptions that no training session is going to undo. The ones who are sceptical have already started building arguments for why it will not work. The ones who are fearful have already started looking for ways to avoid it.
Research from Prosci's benchmarking studies on change management consistently shows that resistance in the first 90 days of a technology deployment is the strongest predictor of long-term adoption failure. Once resistance takes root, it becomes self-reinforcing. Early adopters feel isolated. Resisters find each other. Middle-ground employees read the room and wait.
The window that matters most for AI adoption is the one most organisations skip: the period before the tools go live.
Why the Pre-Launch Window Exists and Why Most Organisations Waste It
Between the decision to deploy AI and the actual launch, there is typically a period of several weeks to several months. During that window, the technology team is building. The project team is planning. And the workforce is waiting.
That waiting period is psychologically charged. Employees know something is coming, but they do not know exactly what it means for them. In the absence of clear, credible information, they fill the gap with assumptions, and those assumptions tend to be negative. This is not a character flaw. It is a well-documented cognitive pattern. Uncertainty triggers threat responses, and threat responses produce exactly the behaviours that AI programmes struggle with: avoidance, scepticism, and passive non-compliance.
Organisations that use the pre-launch window well do something specific with it. They invest in readiness, not just technical readiness, but emotional and cultural readiness. They address the psychological barriers to adoption before the tools arrive, so that when launch day comes, the workforce is prepared rather than braced.
What an AI Change Readiness Sprint Covers
A Change Readiness Sprint is a structured programme designed to fit into the pre-launch window, typically two to four weeks depending on the size of the organisation and the complexity of the deployment. It runs in parallel with the technical workstream, not after it.
The sprint covers three areas.
Psychological Safety
The first area is psychological safety: creating the conditions where employees feel safe to engage with AI honestly, including expressing uncertainty, asking questions, and admitting when they do not understand something.
Amy Edmondson's research on psychological safety in organisations demonstrates that teams with high psychological safety learn faster, adapt more readily to change, and are more willing to experiment with new tools and processes. Teams with low psychological safety do the opposite: they avoid risk, withhold questions, and default to existing behaviours even when new approaches are clearly better.
In practice, building psychological safety for an AI rollout involves several concrete actions. Leaders need to openly acknowledge that the change is significant and that uncertainty is normal. Managers need to be equipped with language and frameworks for having honest conversations with their teams about what the AI tools will and will not do. Employees need safe spaces to voice concerns without being labelled as resistant.
This work has to happen before the tools launch. Trying to build psychological safety after employees have already had a negative first experience with the technology is orders of magnitude harder.
Communication and Framing
The second area is how the AI programme is communicated to the workforce. The default in most organisations is a combination of all-hands announcements, email updates, and FAQ documents. These are necessary but insufficient.
What matters is framing: the narrative that employees construct about why AI is being introduced and what it means for them personally. If the framing is "efficiency and cost savings," employees will interpret that as a threat. If the framing is "expanding what you can do and removing the work you do not enjoy," employees will interpret that as an opportunity. Both framings can be honest. The one the organisation chooses shapes everything that follows.
The sprint helps leadership develop a framing that is specific, credible, and connected to the actual experience employees will have. Generic messaging about "the future of work" does not move anyone. Specific examples of how the tool will change a particular workflow, combined with clear commitments about how roles will evolve, do.
Practical Readiness
The third area is practical readiness: making sure that when the tools go live, employees have the minimum viable capability to engage with them successfully.
This is different from a full training programme. The goal is not mastery. It is enough confidence to try. Research on technology adoption shows that the first interaction with a new tool disproportionately shapes long-term attitudes toward it. A positive first experience creates momentum. A confusing or frustrating first experience creates resistance that persists long after the initial problem is resolved.
The sprint designs that first experience deliberately. It identifies the one or two use cases where the tool delivers the most immediate, visible value for each team, and focuses practical readiness on those use cases specifically. Everything else can come later. The priority is making sure day one goes well.
What Happens After the Sprint
The sprint is a starting point, not an endpoint. The culture work does not stop when the tools go live. But the sprint establishes three things that make everything after it more effective.
First, it creates a baseline of psychological safety that allows employees to engage honestly with the technology. Problems surface faster. Feedback is more candid. Adoption patterns are more visible.
Second, it gives leaders and managers a shared language for talking about AI adoption. Instead of defaulting to productivity metrics and usage reports, they can have conversations about how the technology is landing emotionally and culturally, and what needs to be adjusted.
Third, it generates early momentum. When employees have a positive first experience with the technology, because the sprint was designed to produce exactly that, the adoption curve steepens. Early wins build confidence. Confidence builds willingness to experiment. And experimentation builds the kind of organic capability development that no training programme can replicate.
Before You Launch, Prepare
The fastest way to undermine an AI programme is to launch it into a workforce that was not ready for it. The fastest way to prepare the workforce is a focused sprint in the weeks before launch.
Our AI Change Readiness Sprint combines psychological safety frameworks with practical AI onboarding and runs in as little as two weeks. If your organisation has a launch date on the calendar and the culture work has not started yet, the time to act is now.
Sources: Edmondson, Amy. "The Fearless Organization." Wiley, 2018. Prosci. "Best Practices in Change Management." https://www.prosci.com/methodology/benchmarking Deloitte. "2025 Global Human Capital Trends." https://www2.deloitte.com/us/en/insights/focus/human-capital-trends.html McKinsey & Company. "The State of AI in 2025." https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai