I had a team once — smart people, experienced, top performers — who absolutely did not want to use AI.

Not hostile. Just... unmoved. They'd been through enough technology hype cycles to know that most new tools create more work before they create less. They'd sat through the demos, attended the training, and gone right back to doing things the old way.

I didn't fight them. I didn't mandate usage. I didn't track adoption metrics.

I challenged them.

The 30-Day AI Challenge

Here's what I proposed: for 30 days, pick ONE task from your weekly workflow. Just one. Use an AI tool to attempt it. If it's faster, better, or even just interesting — keep going. If it's not, drop it. No judgment.

The rules were simple:

• Week 1: Pick your task. Something repetitive and time-consuming. Not critical — we're experimenting, not betting the farm.
• Week 2: Refine your approach. Most people get mediocre results on first try because they write mediocre prompts. This week is about learning what the tool needs to produce what you need.
• Week 3: Measure. How long does the task take now vs. before? What's the quality difference? Where does the AI output need human editing vs. where is it good enough?
• Week 4: Decide. Keep, modify, or abandon. Your choice. No pressure.

What Happened

By the end of week 2, something shifted. The skeptics weren't skeptical anymore — they were curious. Because they'd found something specific that worked for THEIR work. Not a demo scenario. Their actual Tuesday afternoon headache.

By week 4, every single person on the team had adopted at least one AI workflow. Not because I told them to. Because they proved it to themselves.

The conversions that stick aren't the ones leaders mandate. They're the ones people discover.

Why This Works

Three psychological principles at play:

1. Autonomy. They chose their task. They controlled the experiment. Nobody forced anything.
2. Competence. By week 2, they were getting better at prompting. That skill development is intrinsically motivating.
3. Evidence. By week 3, they had their own data. Not someone else's case study. Their data. Their workflow. Their results.

You can't argue with your own experience.

Try This Monday

Propose the 30-day challenge to your team. Frame it exactly as I described: one task, four weeks, their choice, no pressure. Then step back and let them discover what you already know.

I detailed the full 30-day onboarding plan — including the specific prompts, templates, and measurement frameworks — in The AI-First Leader. It's the system that turns reluctant teams into self-motivated adopters.

Don't push adoption. Design discovery.

— Vance Sterling