A widely quoted figure says most AI projects fail. Treat it with care: RAND's 2024 report on the root causes of AI project failure notes that "by some estimates" more than 80 percent fail, but that figure is drawn from other estimates, and every study defines failure differently. What RAND's own interviews with 65 experienced data scientists and engineers found is more useful: the first root cause it lists is that leaders misunderstand or miscommunicate the problem the AI is meant to solve. Many AI programmes stall not because the tool doesn't work but because people don't use it, or use it badly.

"They're scared of losing their jobs" is the usual explanation, and it is only one of several. This course works with five resistor archetypes. Each is a pattern of concern, not a type of person, and one employee can show more than one.

Job security: "Will this replace me?" The answer is specific information about what will change in their role, and what support exists if it changes a lot. Vague reassurance makes it worse. Distrust of outputs: "It makes errors." Often this is correct, and it is a reasonable professional instinct. The answer is evidence: let them test the tool on work they already know the answer to, and show where human review stays. Professional identity: "This devalues what I know." Common among senior experts whose standing rests on skills the AI appears to imitate. The answer is a one-to-one conversation and a role in setting the quality standard the AI must meet. Overload: "I don't have time to learn this." The answer is protected time and taking something else off their plate, not another e-learning module. Quiet non-adoption: people who agree in meetings and never open the tool. The answer is usage data by team, a manager who asks about it, and building the tool into the normal workflow so that not using it takes more effort than using it.

Enthusiasts need attention too. Keen but unsupported staff drift to personal accounts, which is the shadow AI described in Module 1, or give up when the first output disappoints. Shadow AI and non-adoption are mirror images: both mean the sanctioned route isn't working for someone.

Treat resistance as information. It tells you where the tool, the training or the message is weak. The leader's job is to diagnose the real concern, respond to that rather than the caricature, and recruit the most credible people, sceptics included, into a change coalition that models the new way of working.

AI literacy is the ability to understand what AI can and can't do, judge its outputs critically and use it well. Every employee needs some; very few need a lot. The mistake most organisations make is one programme for everyone: too technical for most staff, too shallow for the people who will redesign workflows, and too big for L&D to deliver at once.

This course uses its own four-tier model. Awareness is for everyone: what AI is, where it goes wrong, the organisation's acceptable-use policy, what must never be put into a tool, and how to raise a concern. User is for people whose work will change in the current deployment wave: using the sanctioned tool in their own workflow, prompting it well, checking its output and knowing when to escalate. Practitioner is for user champions and function leads: redesigning workflows, judging output quality across a team, coaching colleagues and feeding problems back to the programme. Builder is for a small group in the programme team, IT and data: configuring and integrating tools, setting up agents and their guardrails, testing and documenting systems for governance.

Assign tiers by role, not seniority. A partner who will review AI-drafted work needs user-tier skills; a junior analyst configuring the tool may need builder skills.

Sequence literacy behind the deployment roadmap. Awareness comes first and goes to everyone. User training arrives just before each function's tool goes live, because skills learned months ahead fade before they are used. Practitioners are trained a wave ahead so they can support their colleagues. Builders start at once.

To avoid swamping L&D, split the work. Vendors' own training covers tool mechanics; internal sessions cover judgment, policy and your own examples. Champions run short peer sessions in their teams.

There is also a regulatory driver. Article 4 of the EU AI Act, applicable since 2 February 2025, requires providers and deployers of AI systems to take measures on the AI literacy of their staff. The Digital Omnibus on AI (Regulation (EU) 2026/1744) recast it as a duty to take measures that support literacy, without guaranteeing any individual's level, but did not remove it; deployers of high-risk systems carry more specific competence requirements. The Act reaches organisations outside the EU when their AI output is used there, so UK firms with EU clients should take note. The four tiers align broadly with Article 4; they are not taken from it.

Measure literacy by behaviour, not attendance: sanctioned tools in regular use, outputs checked before they are relied on, shadow AI falling.

Employees fill silence with rumour. If the first thing staff hear about the AI programme is a vendor's press release or a colleague's guess, the programme starts on the back foot. A communication plan has two parts: a stakeholder map that tells you who needs what, and a cascade that delivers it.

Build the stakeholder map from the deployment roadmap in Module 4. For each group, record its AI impact (high, medium or low: how much its daily work will change), its likely response (champion, neutral or resistor, using the archetypes from Lesson 6.1) and your engagement approach. High-impact resistors need one-to-ones; high-impact champions need a role; low-impact neutrals need clear, brief information and little more.

The communication cascade adapts one core message for each layer: the board, the executive and function heads, managers, then all staff. The core message answers five questions. Why are we doing this, in business terms? What will change, for whom and when? What will not change? What support will people get? How is it governed, and how do I raise a concern? The board version leads on investment, risk and measures. The function-head version is about their team's timing, their role as sponsor and the questions they will be asked. The all-staff version is plain, short and specific.

Say what won't change. "AI will not make decisions about anyone's employment" or "every client deliverable is still reviewed by a person" does more for trust than any amount of enthusiasm, provided it is true.

Managers are the critical layer. Employees ask their line manager, not the programme team, so brief managers before staff hear anything, and give them a short set of likely questions with honest answers, including "we don't know yet" where that is the truth.

The governance charter from Module 5 belongs in the cascade, not just the compliance file. Publishing who oversees AI, what it may and may not decide, and where to escalate a concern turns governance into a trust signal.

Time the cascade to the roadmap. A function whose tool arrives in months 12–18 needs to know it is coming and when, but detailed briefings a year early only create anxiety. Different functions hear different messages at different times.

Finally, make it two-way: an open channel for questions, answers published for everyone, and a visible change when feedback shows something is wrong.

Principles need a timetable. This course uses its own 90-day structure for the first stretch of an AI programme, the period in which adoption either takes hold or quietly stalls. Each 30-day block has a purpose and a measure.

Days 1–30, quick actions and early wins. Announce the programme through the cascade, briefing managers first. Publish the acceptable-use policy, the list of sanctioned tools and the governance charter. Open the awareness tier of the literacy programme. Set baselines for whatever you will measure. Put the first tool live with a team that wants it. A good early win is visible, low-risk, measurable and in a team with a willing leader; it doesn't need to be the biggest prize.

Days 31–60, momentum and resistance. Launch the user champions cohort once the first tools are live, so champions have real experience to share. Hold one-to-ones with the high-impact resistors on the stakeholder map. Fix the practical barriers people report, such as access, log-ins or a missing template. Run user-tier training for the next team. Look at the first adoption data by team.

Days 61–90, embedding and measurement. Tell the first success story, with real numbers and a named team that agreed to it. Build adoption measures into normal team reviews. Check readiness for the next wave against the go/no-go gate from the deployment roadmap. Report to the steering committee.

Measure adoption, not just usage. Log-ins and licences issued show access; adoption means weekly use within the actual workflow, outputs checked before they are relied on, and the outcome the business case promised, such as hours freed, starting to move.

Established change models are useful context. John Kotter's eight steps, set out in Leading Change (1996), stress urgency, a guiding coalition and short-term wins; Prosci's ADKAR model traces individual change through awareness, desire, knowledge, ability and reinforcement. The 90-day plan borrows from both, but it is built around what an AI programme specifically needs: tools that arrive in waves, literacy that tracks them and trust that must be earned with evidence.

Watch change fatigue. Keep to one launch per team at a time, as the deployment roadmap does, and don't let the 90-day plan add a second.

The AI Change Leadership Planner brings the module together: stakeholder map, communication cascade, literacy programme, early wins plan and 90-day milestones in one printable plan for your HR director, function heads and steering committee.

Employees read the same headlines, so distinguish displacement, where roles are eliminated, from augmentation, where roles change because AI takes some tasks. The major studies disagree on scale. McKinsey Global Institute's The Future of Work after COVID-19 (2021) estimated that more than 100 million workers across eight economies might need to switch occupations by 2030. The OECD devoted its Employment Outlook 2023 to AI and the labour market. The WEF Future of Jobs Report 2025, a survey of over 1,000 employers, projected 170 million jobs created and 92 million displaced globally by 2030. Estimates vary with method, sector and definition; none is a forecast for your firm.

Earlier automation produced labour market polarisation: David Autor and colleagues document demand growing for high- and low-skill work while mid-skill routine roles shrank, and Acemoglu and Restrepo (2019) show how automation can displace workers from tasks faster than new tasks reinstate them. Whether generative AI follows suit is debated, because it reaches cognitive work. Brynjolfsson, Chandar and Chen (Stanford, revised November 2025) found employment of 22- to 25-year-olds in the most AI-exposed US occupations fell 16% relative to less exposed peers. For workforce planning, the warning concerns entry-level roles and how people learn the job.

So give three honest messages. AI will change roles; we are not planning to replace our workforce with it, if that is true. We will support people whose work changes. And here is the evidence behind our view. "Don't worry, AI will create new jobs" damages trust because people can tell it is reassurance, not information.

AI for social good is real. AlphaFold, from Google DeepMind, has predicted structures for over 200 million proteins, made freely available, and earned a share of the 2024 Nobel Prize in Chemistry. WHO has recommended computer-aided chest X-ray reading for tuberculosis screening since 2021, which matters where radiologists are scarce. A World Bank trial in Nigeria found that six weeks of teacher-supported AI tutoring raised English scores by about 0.3 standard deviations. Claim social benefit only where your programme delivers it.

Policy is moving fast. The UK's AI Opportunities Action Plan (January 2025) set out 50 recommendations, all accepted, within a principles-based approach unlike the EU's rules. The summit series ran from Bletchley Park (November 2023) to Seoul (May 2024), Paris (February 2025) and New Delhi (February 2026).

Human-AI collaboration beats either alone only when the human knows where AI is weak. In a 2023 Harvard and BCG experiment with 758 consultants, those using GPT-4 did 12.2% more tasks, 25.1% faster, at higher quality, inside AI's "jagged frontier"; on a task outside it they were 19 percentage points less likely to be right. AI amplifies expertise; it doesn't replace it.