Most AI enablement starts in the worst possible place.
It asks skilled people to use AI on the thing they are already proud of doing well.
Writers get told to use it to write.
Designers get told to design.
Strategists get told to strategize.
Which is a hell of an opener if your goal is to make someone quietly close the tab.
Because for most skilled people, the core craft is not just a task.
It is identity.
It is taste.
It is judgment.
It is usually the part of the job they actually like.
So when AI shows up and says, “Great news, I can do that part too,” it does not feel empowering.
It feels like someone wandering into your garage workshop, pointing at the thing you built by hand, and saying:
“Cute system. Want me to hold the saw?”
That is why so much AI teaching lands wrong.
It starts with the flight.
It should start with the cape.
Lead with the snag
The first win should not be:
“Look, it can do your thing.”
The first win should be:
“Look, it can remove the nonsense wrapped around your thing.”
The admin pile.
The follow-ups.
The formatting.
The scheduling back-and-forth.
The inbox archaeology.
The three-line update that somehow takes 47 minutes because your brain treats it like assembling IKEA furniture in a wind tunnel.
That is where AI should start.
Not as a replacement for your superpower.
As protection for it.
Because when AI takes a swing at the thing you are best at, the bar is brutal.
A writer sees every flat sentence.
A designer sees every dead composition.
A strategist sees every shallow pattern dressed up like insight.
And honestly, they should.
That is taste doing its job.
But when AI helps with the thing you are tired of, slow at, or avoiding because it is technically important and spiritually cursed, the test changes.
You are not comparing AI to your best self.
You are comparing it to friction.
And in that comparison, “pretty good” can feel incredible.
Awe captures, Relief compounds
AI feels least impressive when your standards are highest.
It feels most powerful when the burden is real and the identity stakes are low.
If AI drafts a paragraph for a writer, the writer asks:
“Is this me?”
If AI cleans up a messy pile of notes, the writer asks:
“Can I use this?”
Very different test.
One invites comparison.
The other creates relief.
And relief is wildly underrated in AI adoption.
A lot of people do not need AI to blow their minds first.
They need it to lower the temperature of their week.
They need one small moment of:
“Oh. My brain is not on fire anymore.”
That moment matters.
Because if the first experience feels like competition, every flaw becomes evidence.
See? It does not get it.
See? It is generic.
See? It is not ready.
But if the first experience feels like support, the whole frame changes.
Same tool.
Same person.
Different entry point.
Different outcome.
Stuckness before strength
If you want someone to adopt AI, do not begin with the thing they love most.
Begin with the thing making that work harder to reach.
Ask:
What part of your week drains you?
What do you avoid even though it matters?
What creates drag around your real work?
What support tasks keep your best skill from showing up consistently?
Teach AI there first.
Because once someone sees AI clearing bottlenecks and getting them back to the part they actually care about, the relationship changes.
Now AI is not trying to replace them.
It is making them more themselves.
That is the move.
Not: “AI can imitate your gift.”
But: “AI can free the cape.”
Do not teach people to use AI where their pride is highest.
Teach them to use it where friction is highest.
That is where adoption starts.