The Pope, IKEA, and the Billion-Dollar Question Nobody's Asking About AI

Last month, Pope Leo XIV released an encyclical on artificial intelligence. Not a pastoral letter about souls or salvation—a warning about reflexes. He called it Magnifica Humanitas, and the sharpest observation about AI I've read all year came from the Vatican, not Silicon Valley.

Here's what caught me: Leo didn't argue theology. He identified a pattern I've watched play out across four technology disruption cycles. When something new and powerful arrives, organizations immediately ask "what does this mean for me?" before they ask "what is this, actually?"

That reflex looks like prudence. It's usually fear—and I've watched it cost companies billions.

The IKEA Case Nobody Talks About

In 2021, IKEA deployed an AI customer-service agent named Billie. The headlines wrote themselves: 8,500 customer service jobs eliminated. Automation eating the working class. The math was simple subtraction.

Except IKEA didn't fire those 8,500 people.

They retrained them as interior design consultants. Billie handled the routine questions—"Where's my order?" and "What are your hours?"—while the humans moved upmarket to the work that actually required human judgment. That reskilling generated approximately €1.3 billion in new revenue.

Billie didn't eliminate 8,500 jobs. It revealed them.

The defensive posture could only ever subtract. The curious question—"what could these people become once the routine work is handled?"—is the one that found the billion.

I'm advising clients right now who are meeting AI with a spreadsheet and a headcount target. They're asking the reflex question, the defensive question, the one that feels like risk management. And they're missing the IKEA pattern entirely.

Railroads and Customer Service Reps

I've seen this movie before. Multiple times.

When electronic trading arrived at the New York Stock Exchange in the late 1990s, the floor traders panicked. Their entire identity was reading the crowd, catching the hand signals, feeling the energy of the pit. The technology looked like an extinction event.

The traders who survived didn't defend their old work—they asked what the technology was actually good at, and what it wasn't. Electronic systems could match orders faster than any human. They couldn't read market sentiment, structure complex derivatives, or advise institutional clients on timing. The floor traders who moved upmarket became strategists and relationship managers. The ones who defended the pit became casualties.

The parallel isn't perfect, but the pattern is. Nobody gets fired the day the railroad arrives. The town just slowly empties out—unless someone asks what the railroad is actually good for and rebuilds around that answer.

The Question Your Competitor Is Already Asking

Here's what I'm seeing in the field right now: two companies, same industry, same AI capability lands in their lap.

Company A asks: "How many FTEs can we eliminate?"

Company B asks: "What work have we been tolerating instead of solving?"

Company A runs a cost-savings analysis. Identifies 15% workforce reduction. Implements layoffs. Saves $2.3M annually. Declares victory. Twelve months later, they're wondering why their competitor is eating their lunch.

Company B inventories the soul-crushing work nobody wants to do. The data entry. The routine compliance checks. The FAQ responses. The manual reconciliations. They automate that work and move their people to the strategic projects that have been languishing in the backlog for three years. The projects that required judgment, relationship capital, and creative problem-solving. The ones that actually generate revenue.

Defensiveness optimizes for the org chart you have. Curiosity optimizes for the org chart you need.

I'm not saying layoffs never make sense. I'm saying the companies who lead with that question are answering before they understand what they're looking at.

What the Math Misses

The spreadsheet makes AI look like a substitution problem. Replace expensive human with cheaper algorithm. Run the ROI. Make the cut.

That math assumes the work stays constant and you're just changing who does it.

But that's not how technology disruption actually works. The work doesn't stay constant. The technology reveals work you didn't know you needed—or couldn't afford to prioritize when humans were buried in routine tasks.

IKEA didn't know they were sitting on €1.3 billion in interior design consulting revenue. They couldn't know—because their humans were answering "Where's my order?" 847 times a day. Billie didn't replace the work. It revealed the opportunity cost of the work.

When I walk clients through this, the pushback is always the same: "But Jay, we're not IKEA. We don't have some secret billion-dollar revenue stream hiding in our customer service team."

Maybe. Or maybe you do and you can't see it because everyone's too busy doing the work that AI is about to handle in 0.3 seconds.

The Uncomfortable Question

So here's where I usually lose people: I don't know what that hidden work is for your organization. Neither do you. The only way to find it is to remove the routine work and see what your people reach for when they have bandwidth.

That's uncomfortable. It requires actually trusting that your people have been sitting on insights and ideas and strategic thinking that they haven't had time to pursue. It requires believing the bottleneck isn't their capability—it's their capacity.

And if you run the AI deployment as a headcount reduction, you'll never find out if you were right.

The Pope called this our "technocratic reflex"—we see a tool and immediately calculate what it replaces rather than what it enables. I call it expensive. Because the companies that win the next decade aren't the ones who cut fastest. They're the ones who ask "what is this, actually?" before they ask "how does this threaten me?"

What to Do Monday Morning

Here's the specific action: before you run the cost-savings analysis on your next AI implementation, run the opportunity-cost analysis first.

Ask your team: "If we automate this work, what work have you been wanting to do but haven't had time for?" Not a hypothetical. Actual projects. Actual client conversations. Actual strategic initiatives that have been stuck in the queue because everyone's buried in routine execution.

Make a list. Put dollar figures next to the items if you can. Compare that list to your cost-savings spreadsheet.

Then decide which question you're optimizing for.

Defensiveness feels safe. It just quietly forecloses the upside. And I've watched enough disruption cycles to know: the companies that survive aren't the ones who defended what they had. They're the ones who asked what they could become.

What has your reflex already cost you?

I work with professional services firms navigating AI, blockchain, and emerging technology disruption. If you're trying to figure out what your team could become on the other side of automation, let's talk.