{"author":{"@type":"Person","name":"Alexander Bock","url":"https://abxk.ai/en/autor/alexander-bock/"},"categories":["AI Work"],"content":{"markdown":"Picture a company that buys AI licenses for every employee. Three months later, a third of the staff use the assistant every week, mostly for small tasks, and the business case is far out of reach. The tool works. The adoption does not. Buying a tool changes nothing by itself: people have to change how they work.\n\nThis is part 4 of Level 4 in our AI Work learning path. Part 2 showed that the benefit of AI depends on how much freed time turns into value ([measure the ROI of AI at work](/en/ai-work/learn/measure-roi-of-ai-at-work/)). This part covers the human side: why AI tools fail without adoption, how new tools spread through a team, champions, training formats, communication, fears, adoption metrics and incentives.\n\n## Buying a tool is not adoption\n\n**Adoption** means that people use a new tool regularly, for the tasks where it helps, in a way that changes results. Access is not adoption, and neither is one enthusiastic try. A representative US survey shows the gap. As of late 2024, nearly 40 percent of adults aged 18 to 64 used generative AI, but only 9 percent of employed people used it every workday (Source: Bick, Blandin and Deming, \"The Rapid Adoption of Generative AI\", NBER Working Paper 32966, 2024, revised 2025, nber.org).\n\nThe funnel shows five stages from license to impact. At each stage, people drop out for typical reasons:\n\n![Funnel with five stages: licensed, tried, habit, core tasks, impact; on the right the typical breaking points between the stages](/images/learn/en/ai-adoption-and-change-management-funnel.webp \"From license to impact: every stage loses people, so measure all five.\")\n\n- **Unclear rules and no time.** People do not know what they may enter into the tool, and nobody gave them time to learn it.\n- **A disappointing first try.** AI does well on some tasks and fails on others that look similar. Whoever starts with the wrong task gives up early. Level 0 explains this uneven border in [what AI changes at work](/en/ai-work/learn/what-ai-changes-at-work/).\n- **Only small tasks.** People rewrite an email now and then, but the tool never reaches the tasks that matter.\n- **An unchanged process.** The team uses AI on top of the old workflow. Steps, roles and targets stay the same, so the saved minutes disappear.\n- **A mandate without guidance.** \"Use AI for everything\" pushes people toward quick, low-effort output. Researchers at BetterUp Labs and the Stanford Social Media Lab link such top-down mandates to **workslop**: AI output that looks finished but has to be fixed by someone else (Source: reported by Fortune, September 2025). Say where AI helps and where it does not, and make clear that people stay responsible for what they pass on.\n\n## How new tools spread through a team\n\nNew tools do not spread evenly. The sociologist Everett Rogers described five groups of adopters in his book *Diffusion of Innovations*, first published in 1962: innovators, early adopters, early majority, late majority and laggards. Their shares follow a bell curve, and the share of people who use the innovation grows along an S-curve.\n\nGeoffrey Moore added an important point in his book *Crossing the Chasm* (1991). Between the early adopters and the early majority lies a gap, the **chasm**. Early adopters try new things because they are new. The early majority wants proof that the tool works for people like them, ready-made examples and help when they get stuck.\n\n![Bell curve of Rogers' five adopter groups with their shares, an S-curve of the share of people who use the tool, and a dashed line marking the chasm between early adopters and early majority](/images/learn/en/ai-adoption-and-change-management-curve.webp \"How new tools spread: the model of Everett Rogers, with the chasm described by Geoffrey Moore.\")\n\nFor AI at work, this means that the enthusiasm of the first users does not carry the rollout. You win the majority with results from colleagues in the same role, with examples from their own tasks and with time to learn. The model is a description, not a law, and the groups in your team may be larger or smaller. But the lesson holds: the majority follows proof, not novelty.\n\n## Build a network of champions\n\n**Champions** are employees in each team who use AI early, find good use cases, share examples and help their colleagues. They are not part of the central AI team. They work in sales, service or finance and know the work there. A champion network connects two directions: the AI team supplies rules, templates and updates, and the champions send back examples, problems and requests.\n\n![A central AI team connected to five champions in sales, service, marketing, finance and operations; each champion supports five colleagues, three of whom already use the tool](/images/learn/en/ai-adoption-and-change-management-champions.webp \"A network of champions: support flows out from the AI team, examples and problems flow back.\")\n\nChampions need four things:\n\n- **Time:** a few hours a week, agreed with their manager and written into their goals.\n- **Early access** to new tools and features, and a direct line to the AI team.\n- **A stage:** short demos in team meetings, a channel for questions and a shared library of good examples.\n- **Recognition:** visible thanks from management and credit in performance reviews.\n\nChoose champions for respect, not only for enthusiasm. A respected colleague who says \"this saved me an hour on the monthly report\" convinces the early majority more than any vendor demo.\n\n## Train in formats that fit the work\n\nNo single format builds a habit. Combine several, and match each to its purpose:\n\n| Format | Good for | Limits |\n|---|---|---|\n| Short online course | Basics for everyone: what AI can do, rules, data, checking outputs | Builds knowledge, not habits |\n| Hands-on workshop | Practice on the team's own tasks, led by a champion | Needs preparation and real examples |\n| Office hours | Questions from daily work, fast help when someone is stuck | Only helps people who come |\n| Peer demos in team meetings | Proof from colleagues, new ideas | Tend to show only highlights |\n| Library of examples and prompts | Reusing what works, a faster start | Gets outdated without an owner |\n| Deep dive by role | Owners, reviewers and power users | Small groups only |\n\nTwo principles make training work. First, train on real tasks from the team's own work, not on generic examples. Second, show where the tool fails, not only where it shines. People who know the weak spots trust the tool for the right things. In the EU, the AI Act also asks companies to support the AI literacy of staff who use AI systems (Article 4). Part 3 of this level places this duty in [AI governance for business teams](/en/ai-work/learn/ai-governance-for-business-teams/).\n\nSoftware can deliver the basics and show the adoption metrics described below. According to the vendors, Evolve creates training courses, adapts them to each learner and measures the results, and Databox combines dashboards, automated reports and goals:\n\n{{\u003c tools \"evolve databox\" \u003e}}\n\n## Communicate honestly and answer fears\n\nGood communication answers five questions before people ask them: Why are we doing this? What changes for me? What stays the same? What are the rules? Where do I get help? Managers matter more than any announcement. When a manager uses the tool openly and shares a real example, the team follows.\n\nChange happens person by person. The **ADKAR model** by the change management firm Prosci describes five steps that each person goes through: awareness, desire, knowledge, ability and reinforcement. Communication covers the first two steps, training and practice the next two, and recognition and results the last one.\n\n![Five rising steps of the ADKAR model with an AI example for each: awareness, desire, knowledge, ability, reinforcement](/images/learn/en/ai-adoption-and-change-management-adkar.webp \"The ADKAR model applied to an AI rollout: each step needs its own action.\")\n\nFears need direct answers. Avoid promises you cannot keep, such as \"no job will change\". Say what you know:\n\n| Fear | What is behind it | What helps |\n|---|---|---|\n| \"AI will take my job.\" | Uncertainty about the future of the role | Be honest about plans, show which tasks change, say how freed time will be used |\n| \"I will look incompetent.\" | New skills, visible mistakes | Safe practice time, no evaluation of individuals by usage data |\n| \"I might break a rule.\" | Unclear limits for data and use | Clear rules with examples of allowed and forbidden inputs |\n| \"I am liable for AI errors.\" | Unclear responsibility | Review rules, clear accountability, a way to escalate |\n| \"This is a way to monitor us.\" | Usage data can show who did what | Measure at team level, agree on rules with the works council |\n\nResearch supports honesty on the first point. The ILO found that generative AI is more likely to change parts of jobs than to replace whole jobs (Source: ILO, Generative AI and Jobs, Working Paper 96, 2023, ilo.org). That does not mean that nothing changes. It means you can tell people which tasks change and how.\n\n## Measure adoption without monitoring people\n\nResearchers at Google proposed the **HEART framework** to measure how people use software: Happiness, Engagement, Adoption, Retention and Task success (Source: Rodden, Hutchinson and Fu, \"Measuring the User Experience on a Large Scale\", CHI 2010, research.google). It works well for AI tools at work:\n\n| Dimension | Example metric for an AI tool | Watch out |\n|---|---|---|\n| Happiness | Share of users who would keep the tool, from a short survey | Early enthusiasm fades, so ask again after two months |\n| Engagement | Tasks done with AI per active user and week | More use is not always better |\n| Adoption | Share of licensed users who used it in the last 30 days | Counts tries, not habits |\n| Retention | Share of users still active after eight weeks | The best early warning |\n| Task success | Share of AI results used after light edits | Needs regular sample checks |\n\nReport these metrics per team, not per person. Ranking individuals by AI use invites fake activity and damages trust. In Germany, the works council also has a say in systems that can monitor performance. And watch out for **Goodhart's law**: when a measure becomes a target, it stops being a good measure. A target such as \"50 prompts a week\" produces 50 prompts, not better work.\n\nIncentives help when they reward results and learning, not clicks:\n\n- **Time:** protected time to learn, especially in the first weeks.\n- **Recognition:** good examples shown in team meetings, with the names of the people behind them.\n- **Career:** AI skills in role profiles and development goals.\n- **Shared gains:** an open decision on how freed time is used — less overtime, more time with customers, new tasks — so that employees benefit too.\n\nAvoid usage quotas and leaderboards. They measure activity, not value.\n\n## Plan the rollout in four phases\n\nEach phase has its own goal and a clear signal for moving on. The pilot phase follows the same logic as Level 3's guide to [running an AI pilot project](/en/ai-work/learn/run-an-ai-pilot-project/):\n\n| Phase | Goal | Actions | Move on when |\n|---|---|---|---|\n| Prepare (weeks 1–4) | Ready to start | Rules, two or three use cases per team, champions named, baseline measured | Champions trained, use cases tested |\n| Pilot with champions (weeks 5–10) | Proof in daily work | Champions use AI on real tasks, collect examples, fix problems | Clear results on at least one use case |\n| Roll out team by team (months 3–6) | Habits in the majority | Workshops on team tasks, office hours, example library, demos by managers | Retention is stable, task success is known |\n| Embed (months 6–12) | The new normal | AI in process descriptions, onboarding and role profiles, old steps removed | The use case metric has moved, reviews run regularly |\n\n{{\u003c callout type=\"try\" title=\"Check one tool you already pay for\" \u003e}}\nFill in the funnel for one AI tool your company has licensed: how many people have access, how many tried it, how many use it every week, how many use it for core tasks — and did the team's metric move? Then talk to three people who stopped using it. Their reasons show you which phase to repeat.\n{{\u003c /callout \u003e}}","text":"Picture a company that buys AI licenses for every employee. Three months later, a third of the staff use the assistant every week, mostly for small tasks, and the business case is far out of reach. The tool works. The adoption does not. Buying a tool changes nothing by itself: people have to change how they work.\nThis is part 4 of Level 4 in our AI Work learning path. Part 2 showed that the benefit of AI depends on how much freed time turns into value (measure the ROI of AI at work). This part covers the human side: why AI tools fail without adoption, how new tools spread through a team, champions, training formats, communication, fears, adoption metrics and incentives.\nBuying a tool is not adoption Adoption means that people use a new tool regularly, for the tasks where it helps, in a way that changes results. Access is not adoption, and neither is one enthusiastic try. A representative US survey shows the gap. As of late 2024, nearly 40 percent of adults aged 18 to 64 used generative AI, but only 9 percent of employed people used it every workday (Source: Bick, Blandin and Deming, \u0026ldquo;The Rapid Adoption of Generative AI\u0026rdquo;, NBER Working Paper 32966, 2024, revised 2025, nber.org).\nThe funnel shows five stages from license to impact. At each stage, people drop out for typical reasons:\nFrom license to impact: every stage loses people, so measure all five. Unclear rules and no time. People do not know what they may enter into the tool, and nobody gave them time to learn it. A disappointing first try. AI does well on some tasks and fails on others that look similar. Whoever starts with the wrong task gives up early. Level 0 explains this uneven border in what AI changes at work. Only small tasks. People rewrite an email now and then, but the tool never reaches the tasks that matter. An unchanged process. The team uses AI on top of the old workflow. Steps, roles and targets stay the same, so the saved minutes disappear. A mandate without guidance. \u0026ldquo;Use AI for everything\u0026rdquo; pushes people toward quick, low-effort output. Researchers at BetterUp Labs and the Stanford Social Media Lab link such top-down mandates to workslop: AI output that looks finished but has to be fixed by someone else (Source: reported by Fortune, September 2025). Say where AI helps and where it does not, and make clear that people stay responsible for what they pass on. How new tools spread through a team New tools do not spread evenly. The sociologist Everett Rogers described five groups of adopters in his book Diffusion of Innovations, first published in 1962: innovators, early adopters, early majority, late majority and laggards. Their shares follow a bell curve, and the share of people who use the innovation grows along an S-curve.\nGeoffrey Moore added an important point in his book Crossing the Chasm (1991). Between the early adopters and the early majority lies a gap, the chasm. Early adopters try new things because they are new. The early majority wants proof that the tool works for people like them, ready-made examples and help when they get stuck.\nHow new tools spread: the model of Everett Rogers, with the chasm described by Geoffrey Moore. For AI at work, this means that the enthusiasm of the first users does not carry the rollout. You win the majority with results from colleagues in the same role, with examples from their own tasks and with time to learn. The model is a description, not a law, and the groups in your team may be larger or smaller. But the lesson holds: the majority follows proof, not novelty.\nBuild a network of champions Champions are employees in each team who use AI early, find good use cases, share examples and help their colleagues. They are not part of the central AI team. They work in sales, service or finance and know the work there. A champion network connects two directions: the AI team supplies rules, templates and updates, and the champions send back examples, problems and requests.\nA network of champions: support flows out from the AI team, examples and problems flow back. Champions need four things:\nTime: a few hours a week, agreed with their manager and written into their goals. Early access to new tools and features, and a direct line to the AI team. A stage: short demos in team meetings, a channel for questions and a shared library of good examples. Recognition: visible thanks from management and credit in performance reviews. Choose champions for respect, not only for enthusiasm. A respected colleague who says \u0026ldquo;this saved me an hour on the monthly report\u0026rdquo; convinces the early majority more than any vendor demo.\nTrain in formats that fit the work No single format builds a habit. Combine several, and match each to its purpose:\nAI Adoption and Change Management Format Good for Limits Short online course Basics for everyone: what AI can do, rules, data, checking outputs Builds knowledge, not habits Hands-on workshop Practice on the team\u0026rsquo;s own tasks, led by a champion Needs preparation and real examples Office hours Questions from daily work, fast help when someone is stuck Only helps people who come Peer demos in team meetings Proof from colleagues, new ideas Tend to show only highlights Library of examples and prompts Reusing what works, a faster start Gets outdated without an owner Deep dive by role Owners, reviewers and power users Small groups only Two principles make training work. First, train on real tasks from the team\u0026rsquo;s own work, not on generic examples. Second, show where the tool fails, not only where it shines. People who know the weak spots trust the tool for the right things. In the EU, the AI Act also asks companies to support the AI literacy of staff who use AI systems (Article 4). Part 3 of this level places this duty in AI governance for business teams.\nSoftware can deliver the basics and show the adoption metrics described below. According to the vendors, Evolve creates training courses, adapts them to each learner and measures the results, and Databox combines dashboards, automated reports and goals:\nEvolveAnalytics \u0026amp; Operations · AI at the coreTraining and enablement platform that creates courses, adapts to each learner and measures results. DataboxAnalytics \u0026amp; Operations · Software with AI featuresAnalytics platform with dashboards, automated reports, goals and AI analysis. Short descriptions from our tool comparison, based on the vendors' information — not tested by ABXK.\nCommunicate honestly and answer fears Good communication answers five questions before people ask them: Why are we doing this? What changes for me? What stays the same? What are the rules? Where do I get help? Managers matter more than any announcement. When a manager uses the tool openly and shares a real example, the team follows.\nChange happens person by person. The ADKAR model by the change management firm Prosci describes five steps that each person goes through: awareness, desire, knowledge, ability and reinforcement. Communication covers the first two steps, training and practice the next two, and recognition and results the last one.\nThe ADKAR model applied to an AI rollout: each step needs its own action. Fears need direct answers. Avoid promises you cannot keep, such as \u0026ldquo;no job will change\u0026rdquo;. Say what you know:\nAI Adoption and Change Management (2) Fear What is behind it What helps \u0026ldquo;AI will take my job.\u0026rdquo; Uncertainty about the future of the role Be honest about plans, show which tasks change, say how freed time will be used \u0026ldquo;I will look incompetent.\u0026rdquo; New skills, visible mistakes Safe practice time, no evaluation of individuals by usage data \u0026ldquo;I might break a rule.\u0026rdquo; Unclear limits for data and use Clear rules with examples of allowed and forbidden inputs \u0026ldquo;I am liable for AI errors.\u0026rdquo; Unclear responsibility Review rules, clear accountability, a way to escalate \u0026ldquo;This is a way to monitor us.\u0026rdquo; Usage data can show who did what Measure at team level, agree on rules with the works council Research supports honesty on the first point. The ILO found that generative AI is more likely to change parts of jobs than to replace whole jobs (Source: ILO, Generative AI and Jobs, Working Paper 96, 2023, ilo.org). That does not mean that nothing changes. It means you can tell people which tasks change and how.\nMeasure adoption without monitoring people Researchers at Google proposed the HEART framework to measure how people use software: Happiness, Engagement, Adoption, Retention and Task success (Source: Rodden, Hutchinson and Fu, \u0026ldquo;Measuring the User Experience on a Large Scale\u0026rdquo;, CHI 2010, research.google). It works well for AI tools at work:\nAI Adoption and Change Management (3) Dimension Example metric for an AI tool Watch out Happiness Share of users who would keep the tool, from a short survey Early enthusiasm fades, so ask again after two months Engagement Tasks done with AI per active user and week More use is not always better Adoption Share of licensed users who used it in the last 30 days Counts tries, not habits Retention Share of users still active after eight weeks The best early warning Task success Share of AI results used after light edits Needs regular sample checks Report these metrics per team, not per person. Ranking individuals by AI use invites fake activity and damages trust. In Germany, the works council also has a say in systems that can monitor performance. And watch out for Goodhart\u0026rsquo;s law: when a measure becomes a target, it stops being a good measure. A target such as \u0026ldquo;50 prompts a week\u0026rdquo; produces 50 prompts, not better work.\nIncentives help when they reward results and learning, not clicks:\nTime: protected time to learn, especially in the first weeks. Recognition: good examples shown in team meetings, with the names of the people behind them. Career: AI skills in role profiles and development goals. Shared gains: an open decision on how freed time is used — less overtime, more time with customers, new tasks — so that employees benefit too. Avoid usage quotas and leaderboards. They measure activity, not value.\nPlan the rollout in four phases Each phase has its own goal and a clear signal for moving on. The pilot phase follows the same logic as Level 3\u0026rsquo;s guide to running an AI pilot project:\nAI Adoption and Change Management (4) Phase Goal Actions Move on when Prepare (weeks 1–4) Ready to start Rules, two or three use cases per team, champions named, baseline measured Champions trained, use cases tested Pilot with champions (weeks 5–10) Proof in daily work Champions use AI on real tasks, collect examples, fix problems Clear results on at least one use case Roll out team by team (months 3–6) Habits in the majority Workshops on team tasks, office hours, example library, demos by managers Retention is stable, task success is known Embed (months 6–12) The new normal AI in process descriptions, onboarding and role profiles, old steps removed The use case metric has moved, reviews run regularly ▸Check one tool you already pay for\nFill in the funnel for one AI tool your company has licensed: how many people have access, how many tried it, how many use it every week, how many use it for core tasks — and did the team\u0026rsquo;s metric move? Then talk to three people who stopped using it. Their reasons show you which phase to repeat.\n","words":1914},"date":"2026-10-14","description":"Why AI tools fail without adoption, and what helps: champions, training on real tasks, honest answers to fears, adoption metrics and incentives that reward results.","image":"https://abxk.ai/images/cover/ai-adoption-and-change-management.webp","json":"https://abxk.ai/en/ai-work/learn/ai-adoption-and-change-management/index.json","kind":"page","language":"en","learning_path":{"category":"ai-work","level":4,"level_name":"Expert"},"modified":"2026-10-14","related_tools":["Evolve","Databox","ElevateForward.ai"],"section":"ai-work","tags":["ai-adoption","change-management","training","expert"],"title":"AI Adoption and Change Management","translations":[{"json":"https://abxk.ai/de/ai-work/learn/ai-adoption-and-change-management/index.json","language":"de","url":"https://abxk.ai/de/ai-work/learn/ai-adoption-and-change-management/"}],"url":"https://abxk.ai/en/ai-work/learn/ai-adoption-and-change-management/"}