By Johannes Sundlo — AI & Future of Work Advisor. I help leaders and HR teams turn AI into adoption that sticks, through keynotes, workshops and change programs.
Most organisations don’t have an AI problem. They have an adoption problem. The tools work, the pilots look promising — and then nothing changes in how people actually do their jobs. This is the practical guide to closing that gap: what real adoption means, why it stalls, and the conditions that make AI stick.
What “AI adoption” actually means
Adoption isn’t licences purchased or pilots launched. It’s a measurable change in how everyday work gets done — people reaching for AI on their own because it genuinely makes the work better. Access is easy to buy. Adoption has to be earned, and it’s the only part that creates value.
Why most AI initiatives stall
- It’s bolted on, not built in. AI lives in a separate tool people forget to open instead of inside the workflow they already use.
- No early, visible win. A 12-month transformation with nothing to show in month one loses the room.
- Fear goes unaddressed. People quietly worry AI replaces them, so they don’t lean in.
- It’s treated as IT’s job. Adoption is a change-leadership challenge wearing a technology costume.
The “Adoption that Sticks” model
Across keynotes and change programs with organisations of every size, the same five conditions show up wherever AI actually takes hold. Miss one and adoption stalls.
- A painful, specific starting point. Begin with one repeated, low-risk task people already dislike — not a strategy.
- Built into the workflow. The AI step lives in the template, checklist, or doc people already use.
- Human in the loop. AI drafts, a person decides — so people trust the output and own the result.
- Visible local proof. “This used to take 40 minutes, now 8.” Concrete wins spread faster than any mandate.
- Leaders who go first. When leaders use AI out loud, everyone else gets permission to.
Where to start — by role
Adoption looks different depending on who you are. Two practical guides go deep on each:
- HR teams: see AI for HR: a practical guide to adoption that sticks.
- Leaders and executives: see AI for Leaders: a practical guide to driving adoption.
- Recruiting and talent: see AI in Recruiting: a practical guide.
How to measure AI adoption
Track three signals, not vanity metrics: breadth (how many teams use AI in real work without being told to), depth (is it touching meaningful tasks, not toys), and momentum (are new use cases appearing on their own?). When all three trend up, you’ve moved from pilots to a culture.
Common questions about AI adoption
Why do most AI pilots fail?
Most AI pilots fail because they run as isolated side-projects, disconnected from the work people do every day. A pilot proves a tool works in a demo; adoption means changing habits — a fundamentally harder job. Three patterns kill them: no early, visible win in the first month; no owner with the time and mandate to carry it; and no behaviour change from leaders. The data backs this up. In a 2025 survey of 461 Swedish HR professionals, 81% had access to generative AI, yet only 25% used AI agents and just 33% had any formal training — the bottleneck was enablement, not technology. Pilots that succeed start with one painful, repeated task, build the AI step into an existing workflow, keep a human in the loop, and make the result visible so it spreads on its own. See the full State of AI in HR data.
How long does AI adoption take?
Expect meaningful change in a quarter, not a week. Lasting AI adoption is a behaviour shift, and behaviour shifts take a few months of deliberate effort — not a single workshop or a big-bang launch. A practical 90-day cadence works best: in the first month, leaders experiment openly and set simple guardrails; in the second, back two or three real pilots with protected time; in the third, build AI into onboarding, templates and how work gets reviewed so it becomes the default. Speed matters on learning, patience matters on scale. The organisations stuck after a year are usually the ones that either rolled out everything at once or analysed endlessly without shipping anything. Momentum compounds: each visible win makes the next team more willing to try. For year-over-year benchmarks on where Swedish HR teams actually are, see the State of AI in HR data.
Who owns AI adoption in an organisation?
AI adoption is shared, but it has to be led. Leaders set the direction, remove friction, and model the behaviour by using AI in their own week; teams own the specific workflows where it lives. It is emphatically not “IT’s project” — the moment AI becomes one department’s side-task, it stays in a corner and never reaches daily work. The data shows how unsettled ownership still is: in 2025 only 3% of HR professionals saw AI primarily as an HR question, down from 6% the year before, while 39% called it an IT question. That’s the gap and the opportunity — the function best placed to drive people-and-change adoption is the least likely to be holding the wheel. The fix is a leader who goes first, a clear owner per workflow, and visible local proof. More in the State of AI in HR data.
Make AI adoption actually happen
Keynotes that make AI click for the room and workshops that turn it into habits your team uses the same week. Let’s find the right format.
Pilot vs. adoption: what’s the difference?
| A pilot | Real adoption | |
|---|---|---|
| Goal | Prove the tool works | Change how work gets done |
| Scope | One team, time-boxed | Spreads on its own |
| After it ends | Often nobody owns it | Built into daily workflows |
| Key signal | “It worked in the demo” | Used without being told |
| Typical outcome | Quietly dies | Becomes the default |
The five conditions at a glance
The data: see State of AI in HR: Sweden 2024–2025 — original survey data on the AI adoption gap.
