The Shrug

The story you've been sold about adoption is wrong. Here's the one I keep seeing on the ground.

Share

Your people are underwhelmed by AI. That's worse.

Somewhere in your building right now, one of your people just opened an AI tool on something that actually mattered to them. They didn't know what to type, so they pasted in a prompt somebody sent them on Slack. They read what came back. And they shrugged.

Then they closed the tab and went back to the work they'd been doing before.

That shrug is the actual problem at your company. Not resistance. Not fear. Not change management. A quiet, mild, “I guess that's kind of neat,” followed by a complete return to business as usual. Your rollout plan doesn't account for it. Your training program doesn't prepare your people for it. Your dashboard absolutely doesn't show it. The seats are active, the prompts are flowing, the ROI slide is green.

And underneath all of it, your workforce is using the most powerful tool of their lifetime like a slightly better autocomplete.

Surfacing: The Fingerprint Paradox

Here's the part the vendor slides leave out. All of it is a human problem wearing a technology costume, and the reason most companies can't solve it is that they're trying to solve it the way they've solved every technology rollout for the last forty years, by engineering the human variation out of the process.

That approach isn't a mistake. It's a century-old discipline. Manufacturing built the modern world on the insight that if you could standardize a process tightly enough, you could produce consistent output regardless of which operator ran the machine. Standard work. Six Sigma. Lean. All of it built on the same foundational bet: human variation is a defect to be eliminated, and the best process is the one that runs the same whether your operator is your best person or someone who started last Tuesday. For physical work with knowable tolerances, that bet paid off spectacularly.

And here's the part most knowledge workers have never stopped to notice: we imported the entire playbook.

Look around your office. The standard operating procedure that tells the underwriter how to make a decision. The interview script the recruiter reads from. The quarterly report that looks identical to last quarter's because the template mandated it. The five-box process diagram on the conference room wall that someone printed out and laminated. None of these are accidents. Every one of them is standard work imported from the shop floor and dressed up in Microsoft Word. The goal is the same goal your grandfather's plant manager had in 1962: consistent output, regardless of who does the work.

The modern knowledge economy has been running on a manufacturing playbook for thirty years, and most of the people executing it have no idea where it came from.

That playbook is the reason your company is currently failing to adopt AI.

When AI arrived, the instinct of every leader trained in that paradigm was to do the thing that had always worked before. Standardize the prompts. Lock down the approved workflows. Write an SOP that tells every person on the team exactly how to use the tool. Build a dashboard that measures whether they're using it the approved way. It's the same playbook used for the SOP and the template and the laminated diagram, and it feels like the responsible move, because for forty years it has been the responsible move.

Six months later, the entire workforce is treating AI like a slightly better cycle-start button. Press the green button, collect the output, move on. Producing work that is technically correct and spiritually hollow. The shrug. Everywhere. Across the whole org.

This is the Fingerprint Paradox, and it's the most important thing nobody's naming about AI adoption right now. Manufacturing spent a century perfecting the art of removing the fingerprint of the individual operator, the personal judgment, the accumulated craftsmanship. AI work absolutely requires you to put it back in.

AI doesn't need your obedience. It needs your craftsmanship. The specific way you think about the problem, the questions only you would ask, the verification instincts only you would apply, the taste only you have developed over years of doing the work. That's not the obstacle to AI adoption. That's the entire point of it.

This is what the manifesto meant when it said: we don't say the machine is broken. We say the operators have different practice.

And the fractal property makes it inescapable. A company training its people to be cycle-start button pushers is failing at scale exactly the way a single person is failing at their desk, by treating the human as the variable to minimize instead of the variable that decides everything.

The shrug isn't a bug in your adoption program. The shrug is the program working as designed.

Every SOP you write for AI, every dashboard you build to enforce approved usage, every training program that reduces the tool to a sequence of safe prompts. All of it is making the shrug more entrenched, not less. You're not failing at AI adoption. You're succeeding at the wrong goal.

What's Next

If you're a leader watching your rollout produce the shrug across hundreds of people, this series is for you. If you're a single person who's felt the shrug yourself and wants to climb out before your peers do, this series is for you too. Same fingerprint paradox. Same operating system. Two scales of the same problem.

Next Tuesday: the people who escape the shrug all have one thing in common, and it isn't intelligence, effort, or experience. It's something quieter and more deliberate, and it's almost entirely missing from the way your company is teaching people to work with AI right now.

See you then.

Q

Know someone who'd recognize the shrug? Forward this. They can find the rest at belowthesurface.anchor11.com