Milan Bogojevic Blog

Is AI Transformation a Myth?

6 min read updated 10 October 2026

Illustration of an AI transformation announcement peeling back to reveal cost cutting and layoffs, with employee silhouettes below.
Illustration of an AI transformation announcement peeling back to reveal cost cutting and layoffs, with employee silhouettes below.

AI transformation becomes a myth when buying tools is treated as evidence that an organisation has changed. A nonprofit needs different evidence: a workable process, people trained to run it, a named decision owner and a handover that survives someone leaving. Without those, a successful demo can conceal a fragile operation.

Picture a mid-sized company in this hypothetical example. Its CEO announces a major AI transformation, buys several tool licences and arranges one day of training. Six months later, management reduces administrative staffing and describes the decision as AI-driven efficiency. The announcement alone cannot show whether the remaining team can perform the work safely.

The Myth of Technological Transformation

Executives tend to treat AI transformation as a software purchase: buy the licences, announce the initiative, and the transformation is assumed to follow on its own. In practice, the hard part was never the technology. It's the processes, the responsibilities, and the people who have to actually change how they work. The gap between the announcement and what actually happens inside the organisation is wide enough that it deserves its own name: AI theatre. BCG’s 2020 research on digital transformation describes the difficulty of achieving lasting change and the importance of organisational conditions. It concerns digital transformation broadly, not an AI-specific failure rate.

What can a transformation announcement conceal?

My concern is that an AI label can make a cost-cutting decision sound like a capability improvement. That is a risk to examine, not a claim about every employer or vendor. Ask what has changed in the work: which tasks disappeared, which new review tasks appeared, and whether the team has time and skills to perform them.

For a nonprofit, a promised efficiency gain can quietly become extra checking for a programme officer. A pilot budget should account for that work before leadership calls it a saving.

The Nonprofit Version of This Myth

The corporate version of this story has a budget to hide behind. A nonprofit usually doesn't, which makes the same myth look different, but it isn't actually smaller.

Consider a second hypothetical example: a mid-size NGO running three community programmes with a staff of fourteen. A new grant requires "digital transformation," so the executive director greenlights an AI pilot for case note summarisation, chosen in a single afternoon after a vendor demo. The pilot runs well for six weeks, largely because the one programme officer who championed it keeps feeding it clean, well-formatted notes and quietly fixing its mistakes before anyone else sees them. When that programme officer leaves for a new job three months later, the pilot collapses within weeks: nobody else knows which fields the tool needs, nobody owns checking its output, and the organisation quietly goes back to manual notes, now a tool poorer and with less trust in AI projects than before it started.

Nothing about this is a story of AI failing on the merits. The operational problem in this hypothetical case is specific: the organisation never built a second person who understood the tool, never defined who owned the decision to keep using it, and never separated "this works because one person is holding it together" from "this works." That's a handover failure, not a demo failure, and it's exactly the distinction covered in AI Transformation Pilots Fail at the Handover.

My view is that nonprofits are actually more exposed to this version of the myth than most companies, not less, because a fourteen-person team rarely has the slack to build real redundancy around a pilot, and a grant-funded "innovation" line often pressures a team to adopt something fast, before anyone has asked who owns it once the person who chose it moves on. The five-gate test for choosing AI tools is worth running before the pilot starts, specifically because it forces that ownership question early, when it's still cheap to answer.

What changes for the people who stay?

In my view, asking staff to supervise AI output creates a responsibility that deserves training and scheduled time. It should not be absorbed invisibly alongside their existing work. In a small nonprofit, the person checking a draft may also be the person answering beneficiaries, preparing a donor report and covering a colleague’s absence.

Write down the tasks the tool removes and the review tasks it adds. A smaller headcount is not, by itself, proof of a better process.

Why can a quick saving be easier to sell than a lasting change?

A licence purchase and a reduced budget are easy to present to a board. A trained backup, an improved handover and a careful review process take longer to demonstrate. My view is that leaders should report those operating conditions alongside any claimed saving.

For nonprofits, the consequence is practical: an innovation grant should fund the time needed to make the pilot repeatable, including time for a second person to learn it.

What Real AI Transformation Would Require

Three conditions separate a real transformation from AI theatre. First, sustained investment in skills, with pay that actually reflects the new responsibilities people are asked to take on, not just a one-day training session. Second, leadership willing to accept a slower timeline and openly admit when a rollout is failing, instead of quietly redefining success. Third, honesty about whether layoffs are actually driven by business needs or simply by the existence of a new tool. For a smaller nonprofit, these conditions belong in the pilot plan before the tool becomes part of everyday work.

My view

An AI transformation claim should be tested against how the organisation now works. A tool purchase does not establish that change, and staffing reductions do not establish that AI caused it. I would ask for a repeatable workflow, measured review effort and a second person who can operate it.

The question worth asking is whether the team has gained a capability it can sustain.

FAQ

What is AI theatre?

AI theatre is the gap between announcing an AI transformation and changing how an organisation actually works. Buying licences, running a one-day training session, or promoting an AI initiative does not establish the processes, skills, and responsibilities needed for lasting change.

Why can an AI pilot fail after a successful demo?

An AI pilot can fail when its success depends on one person who prepares inputs and corrects errors. If that person leaves without documented workflows, a trained backup, and clear responsibility for checking output, the organisation may be unable to keep the pilot running. A successful demo does not prove that a tool will survive a handover.

What does real AI transformation require?

Real AI transformation requires sustained investment in skills, clear ownership of workflows and output checks, and leadership willing to accept a slower rollout and admit failures. New responsibilities should be reflected in pay, and decisions about staffing should be explained honestly. For nonprofits, training a second person and planning the handover are essential to keeping a pilot operational.

Sources

About the author

Milan Bogojevic works on practical AI adoption in nonprofits, with a focus on workflows, human accountability and organisational capability.

Last updated: 10 October 2026.

Next in AI Transformation