Upskilling Was Never Optional. AI Has Only Made That Obvious.
Preparing people for new tools is not a training-budget line item. It is a duty owed to the worker.
Every wave of workplace automation produces the same two conversations, usually at the same time, in the same organization. One is about the technology's capability, what it can now do faster or cheaper than before. The other, usually smaller and later, is about the people whose jobs sit next to that capability and now have to change how they work. AI has compressed the gap between these two conversations to almost nothing. Tools that reshape how an operations team functions can go from pilot to full deployment in a matter of months, and the workforce is expected to catch up on whatever schedule the technology sets.
This ordering has it backwards, and Catholic Social Teaching has always insisted on saying so plainly.
Work Is for the Person, Not the Person for the Work
The Church's social doctrine holds a principle that sounds almost countercultural inside a modern operations meeting: work exists to serve the dignity of the person who does it, not the other way around. A technology introduced to increase throughput is not neutral simply because it increases throughput. If it is introduced without a genuine, resourced plan to help the people affected by it grow into new competence, it treats those people as a variable to be optimized around rather than the reason the operation exists in the first place.
Upskilling, seen this way, is not a perk extended to employees who happen to be adaptable, nor a cost center to be minimized before the next budget cycle. It is a duty owed to the worker whose role is changing because of a decision made above them. An organization that adopts a new AI system faster than it prepares its people to work alongside it has not modernized responsibly. It has simply exported the disruption downward onto whoever has the least power to resist it.
What Real Upskilling Requires
Genuine preparation is not a single onboarding webinar attached to a software rollout. It requires time carved out from ordinary workload, not squeezed into it, because a person cannot learn a new way of working while still being measured against the old one's targets. It requires training built around what the tool actually changes about a person's judgment and responsibility, not just which buttons to click. And it requires listening to the people doing the work before the system is finalized, since the person closest to a task usually knows before anyone else where a new tool will help and where it will quietly create new risks.
This is where subsidiarity has real teeth. Decisions about how a tool gets used in daily practice belong, as much as possible, with the team closest to that practice, not solely with whoever selected the vendor. A rollout designed entirely from above, however well-intentioned, misses the texture of the actual work and often produces resentment that no amount of technical training can fix afterward.
The Cost of Getting This Backwards
Organizations that treat upskilling as an afterthought do not simply risk lower adoption rates or slower returns on their technology investment, though both are common outcomes. They risk something more serious: communicating to their own people, however unintentionally, that the tool matters more than the person expected to use it. That message, once received, is difficult to undo, and it corrodes exactly the trust an organization needs if it wants its workforce to engage honestly with new technology rather than quietly resist it.
Preparing people well is not the price of adopting AI responsibly. It is what adopting AI responsibly actually means.