From fear to flow: why AI resistance in teams is about more than technology

From fear to flow: why AI resistance in teams is about more than technology

Artificial Intelligence is moving rapidly from experimental tool to everyday infrastructure. Over the past months, AI developments have accelerated across nearly every domain. New generative models are being embedded into mainstream products, AI is increasingly used in software development and cybersecurity, and organizations are starting to reorganize work around AI-driven productivity gains.

Yet inside many organizations, the biggest challenge is not technological capability.

It is the human response to change.

While leaders talk about efficiency, innovation and competitive advantage, many employees experience something very different: uncertainty. What will change in my work? Which skills will still matter? How much decision-making will be delegated to machines? And what does it mean if AI becomes part of daily operations rather than a separate experiment on the side?

Understanding that tension is becoming essential for organizations that want to adopt AI successfully.

AI is becoming infrastructure

Recent developments show how quickly AI is becoming part of everyday digital infrastructure. Large technology companies are integrating AI capabilities directly into widely used tools, making advanced functionality accessible to millions of users almost overnight. Image generation, coding assistance and automated analysis are no longer niche features. They are increasingly built into the platforms people already use every day.

At the same time, organizations are exploring how AI can reshape internal processes. AI systems are already helping developers write and review code, supporting analysts in processing large volumes of information, and assisting decision-making in areas ranging from customer service to cybersecurity.

This matters because it changes the nature of digital work. AI is no longer something that is only used occasionally for experimentation. It is gradually becoming part of the operational backbone of organizations.

But when infrastructure changes, people feel that too.

The real barrier to AI adoption is often cultural

In many organizations, AI adoption does not stall because the technology is not good enough. It stalls because teams struggle to integrate it into their daily way of working.

Resistance to AI rarely shows up as loud opposition. More often, it appears as hesitation. Teams delay experiments. Managers avoid difficult implementation decisions. Employees quietly continue to work in familiar ways, even when new tools are available.

That reaction is understandable.

For many years, technological change mainly meant new systems that helped people do their jobs faster or more efficiently. AI introduces a different kind of shift. It raises more fundamental questions about roles, expertise and decision-making.

That uncertainty is only reinforced by what people see around them. News stories increasingly link AI to restructuring, job redesign and efficiency measures. Even when organizations position AI as support rather than replacement, employees do not interpret it in a vacuum. They bring those broader signals with them.

As a result, resistance is often not really about the tool itself. It is about what the tool seems to represent.

Psychological safety becomes critical

If organizations want teams to explore AI seriously, they need to create an environment in which that exploration feels safe.

Psychological safety is crucial here. People need to feel that they can ask questions, test new tools, make mistakes and openly discuss limitations without fear of blame or negative consequences. Without that sense of safety, experimentation tends to stop before it even begins.

This is one reason Agile teams may be better positioned to work with AI. Agile ways of working already emphasize experimentation, short feedback loops, learning by doing and transparency in collaboration. Those principles create a stronger foundation for adopting new technology in a healthy and sustainable way.

Still, AI adoption does not happen automatically, even in Agile environments. It requires deliberate leadership and active guidance.

From fear to flow

Organizations that successfully integrate AI tend to understand one thing clearly: adoption is not just about introducing a tool. It is about helping people make sense of change.

When AI is introduced as a disruptive force that will redefine everyone’s role overnight, teams often respond with defensiveness or distance. When it is introduced more realistically, as a capability that can support people in their work, the conversation changes.

AI can help teams move faster, automate repetitive tasks, summarize information and surface patterns that might otherwise be missed. But that does not remove the need for human judgment. People still provide context, accountability, interpretation and direction.

That balance matters.

The real value of AI does not come from replacing human contribution. It comes from combining machine speed and scale with human insight and responsibility. Once teams begin to experience that in practice, their attitude often starts to shift. What first felt threatening begins to feel useful. Uncertainty gives way to curiosity. Curiosity leads to experimentation. And experimentation creates momentum.

That is where fear starts to turn into flow.

Leading AI transformation inside teams

For leaders, this means that successful AI adoption is at least as much a change challenge as it is a technology challenge.

Teams need help understanding what AI can realistically do, where it adds value, where the limits are, and how responsibilities remain clear. Without that guidance, organizations risk creating confusion rather than progress.

This is exactly why leadership, coaching and facilitation matter so much in an AI-enabled environment. Teams need people who can create clarity, structure learning and keep the conversation grounded in both practice and responsibility.

That role is especially important in Agile contexts, where adaptation, reflection and team ownership are already central. Scrum Masters, Product Owners, Agile Coaches and transformation leaders can play a key role in helping teams move beyond fear and toward confident experimentation.

Join the conversation

These questions are at the heart of the upcoming Freaky FrAIday session: From fear to flow: overcoming AI resistance in Agile teams.

During this session, Dr. Steve Mayner and Jurney Koning will explore why AI often triggers resistance inside teams and how organizations can create the trust and psychological safety needed for meaningful experimentation.

The session will look at common fears and misconceptions about AI in Agile teams, practical ways to foster openness and curiosity, and the role of leadership in guiding teams through AI-driven change.

For anyone working in Agile, this is becoming an increasingly relevant conversation. AI is moving quickly from experimentation into everyday practice, and the organizations that benefit most will not necessarily be the ones with the most advanced tools. They will be the ones that know how to bring their people with them.