The Helmet Rule Nobody Wants to Enforce
Gordie Howe played the last years of his NHL career without a helmet. The league had mandated them, but a grandfather clause let veterans who had played without one continue to do so. Nobody was stripping that choice from Mr. Hockey. He had earned the right to decide how he protected his own head, and the league respected it.
I grew up in Detroit. That image stayed with me. And I keep coming back to it as organizations wrestle with one of the more honest questions in AI adoption: when do you let people opt out, and when does the organization’s need for a performance floor override individual preference?
The Autonomy Instinct Is Correct, Up to a Point
The reflex to protect worker choice around AI is not just politically convenient. It reflects something real about how adoption actually works. Forcing tools on people who distrust them produces compliance theater, not capability. You get surface-level usage, no genuine integration, and resentment that poisons the well for everything that follows. The organizations that mandate AI use without building trust first are not accelerating adoption. They are building a case study in why it fails.
Autonomy also reflects a legitimate professional concern. When someone has spent twenty years developing judgment in a domain, and a tool arrives that claims to do that job in seconds, skepticism is not ignorance. It is a reasonable response to an unproven claim. The expert who pushes back on AI is not always defending ego. Sometimes they are defending accuracy, and they are right to make the organization prove it before capitulating.
But the grandfather clause only worked for Gordie Howe because Gordie Howe was Gordie Howe. The rest of the league needed the helmet. Individual exception is not organizational strategy.
The Reskilling Problem Is Real, and It Is Early
Here is where the honest answer gets uncomfortable. Most organizations are having the autonomy conversation before they have solved a more foundational problem: they do not yet know what reskilling for an AI-augmented workforce actually looks like. The tools are evolving faster than training curricula. The job categories most affected are not yet fully defined. The skill gap between workers who use AI fluently and workers who do not is measurable today, but the ceiling on that gap is still unknown.
That uncertainty cuts in two directions. It argues against forcing workers into rigid AI workflows that may be obsolete in eighteen months. It also argues against letting individual preference determine capability investment, because the organization cannot afford to find out two years from now that half its workforce opted out of the future.
The reskilling question is not primarily a training question. It is a strategy question. What does this organization need its people to be able to do, and over what timeframe? Most leadership teams have not answered that with enough specificity to build a workforce plan behind it. They are making policy decisions without a map.
Productivity Is Not Optional, But the Floor Is Negotiable
The pressure organizations feel to show AI productivity gains is real. Boards are asking. Competitors are claiming results. The temptation is to set a high floor fast, mandate adoption broadly, and report the numbers. That approach tends to produce exactly the compliance theater described above, plus a layer of workforce anxiety that is genuinely difficult to undo.
A more defensible position is to define the minimum viable capability the organization needs across roles, and build toward that deliberately rather than universally. Not every role needs the same level of AI fluency. Not every workflow benefits equally from augmentation. The organizations that will win this are not the ones that adopted fastest. They are the ones that adopted with enough precision to build real capability rather than surface coverage.
That still requires setting a floor. Autonomy cannot mean indefinite deferral. At some point the organization has to say: this is what working here requires, and we are committed to helping you get there. That is not coercion. That is a functioning employment relationship with a point of view about the future.
The Conversation Most Organizations Are Avoiding
The reason the helmet analogy holds is not the helmet itself. It is the grandfather clause, and what it says about how institutions manage transition. The NHL was not wrong to let Howe make his own choice. But they did not extend that option indefinitely or universally. It was a bounded accommodation during a transition period, not a permanent policy.
That is the frame most organizations need and few have adopted. Not a mandate, not a free-for-all, but a defined transition window with real support, a clear destination, and an honest conversation about what comes after it closes. Workers deserve to know what the organization actually needs from them. Leadership owes them that clarity before it owes them a policy.
The organizations getting this right are not the ones moving fastest. They are the ones who had the harder internal conversation first, defined what they were actually building toward, and then brought their workforce along with enough lead time to make it real. That conversation is harder than deploying a tool. It is also the only one that matters.