{"id":22669,"date":"2026-07-23T00:58:42","date_gmt":"2026-07-23T00:58:42","guid":{"rendered":"https:\/\/scannn.com\/most-ai-rollouts-fail-due-to-change-management-not-technology-heres-what-we-learned-changing-ourselves\/"},"modified":"2026-07-23T00:58:42","modified_gmt":"2026-07-23T00:58:42","slug":"most-ai-rollouts-fail-due-to-change-management-not-technology-heres-what-we-learned-changing-ourselves","status":"publish","type":"post","link":"https:\/\/scannn.com\/lv\/most-ai-rollouts-fail-due-to-change-management-not-technology-heres-what-we-learned-changing-ourselves\/","title":{"rendered":"Most AI rollouts fail due to change management, not technology. Here\u2019s what we learned changing ourselves"},"content":{"rendered":"\n
\n

Ask most enterprise leaders why their AI investment hasn\u2019t paid off, and they\u2019ll point at the technology \u2014 the wrong model, the immature tooling, the integration that never quite landed. In our research at Atlassian\u2019s Teamwork Lab, that\u2019s rarely the real problem. The organizations struggling most with AI aren\u2019t the ones with the worst tools. They\u2019re the ones that treated a profound behavioral shift as a software deployment.<\/p>\n

The numbers bear this out. Per our 2026 State of Teams<\/a> report, 85% of knowledge workers report using AI, but only 29% have embedded it into how they work day to day. Handing someone a license changes what\u2019s on their screen. It doesn\u2019t change how they make decisions, coordinate with a team, or trust an output enough to act on it. Those are questions of behavior and culture, and they don\u2019t resolve on a rollout timeline.<\/p>\n

So the more useful question isn\u2019t \u201cwhich AI should we buy?\u201d It\u2019s \u201chow do we get an organization to work differently?\u201d That\u2019s a change management problem, and no one has fully cracked it yet.<\/p>\n

What we got wrong first<\/h2>\n

Atlassian has spent two years remaking how roughly 12,000 of our own people work with AI, and the early going was messier than any case study admits. Our first instinct was the common one: make the tools available, celebrate the early adopters, and assume usage would spread on its own. It didn\u2019t.<\/p>\n

Individuals got faster while teams stayed exactly as coordinated, or as fragmented, as before. Enthusiasts built clever workflows that never traveled past their own desks. Skeptics quietly opted out. We were measuring logins and calling it progress.<\/p>\n

The turning point was structural, not technical. We moved AI enablement out of IT and put it under the same leader who owns our people function \u2014 a deliberate signal that this was about how humans work, not which software they run. That reframing did more for adoption than any single feature, because it put the change in the hands of people who understand behavior.<\/p>\n

Top-down and bottom-up aren\u2019t a choice<\/h2>\n

The organizations that make real progress drive AI adoption from the top and grow it from the ground at the same time, and the two halves depend on each other.<\/p>\n

Top-down provides what individuals can\u2019t manufacture alone: a clear reason the change matters, permission to spend time learning rather than only executing, and honest guardrails around what\u2019s safe to try. When leadership sets a visible direction, experimentation stops feeling like a risk to someone\u2019s job and starts feeling like the job. When our head of AI did a live demo of our internal tooling, it drove an enduring 90% increase in AI usage.<\/p>\n

Bottom-up provides what strategy decks can\u2019t: the actual use cases. The workflows worth scaling are almost never the ones leadership imagines in advance. They surface when someone close to the work solves a real problem and shows a colleague.<\/p>\n

In two Teamwork Lab<\/a> experiments<\/a>, 75% and 82% of participants learned a new AI use case from their own colleagues rather than a prescribed list. Those ideas spread only because leadership had built the conditions, and the mechanisms, to carry them from one team to the next.<\/p>\n

Top-down mandates alone produce compliance and dashboards full of shallow usage. Bottom-up alone produces islands of brilliance that never reach the org. The work of change management is building the bridge between them.<\/p>\n

Culture is the substrate, not the slogan<\/h2>\n

The same change program lands very differently depending on the culture it\u2019s dropped into. Top teams are 3.2x more likely to say they\u2019re encouraged to experiment and find ways AI works for them, per our 2026 State of Teams report. And per our 2025 AI Collaboration report<\/a>, 37% of workers prefer not to let others know when AI is assisting them, mostly out of fear it will diminish their credit or be seen as cheating.<\/p>\n

The implication most transformation plans skip: before rolling out AI, be honest about the culture you\u2019re rolling it into. If experimentation isn\u2019t safe today, that\u2019s the first thing to fix \u2014 not the technology. The single most effective thing we did was reframe the goal as building a culture of experimentation, normalizing that most experiments won\u2019t work, and that this is the point.<\/p>\n

In practice, that can be as small as a micro-learning ritual. Ask your team to spend 15 minutes in a meeting (cameras and mics off) trying something new with AI, then come back and share what they did. Some will have something cool to show; others will have failed. Either way, the ritual rewards taking a risk together.<\/p>\n

The unsexy work is the real work<\/h2>\n

The companies using AI well are the ones with the right foundations already in place. Knowledge management isn\u2019t a new problem, but AI is finally the carrot getting people to fix it. We once assumed AI would transform everything on its own. In practice, it\u2019s the unglamorous hygiene \u2014 establishing the right knowledge, the right processes, the right communication skills \u2014 that creates transformation.<\/p>\n

The pattern isn\u2019t unique to Atlassian, which is the encouraging part.Amadeus, a giant in travel tech, recently migrated over 20,000 employees to Confluence Cloud Enterprise<\/a>. The move freed up two full-time engineers from infrastructure maintenance, established Confluence as the company-wide source of truth, and paves the way for RovoAI tools to save employees an estimated 10% of their time.<\/p>\n

The questions that matter more than adoption metrics<\/h2>\n

For leaders sizing up their own AI programs, a few questions cut closer to the truth than any usage dashboard:<\/p>\n