Someone posted this on Reddit a few months ago. It has over 1,100 upvotes because everyone recognized it immediately:
"Last quarter I rolled out Microsoft Copilot to 4,000 employees.
$30 per seat per month. $1.4 million annually.
I called it 'digital transformation.' The board loved that phrase.
Three months later I checked the usage reports.
47 people had opened it. 12 had used it more than once."
It's satire. But barely.
The Microsoft quarterly report from late 2024 backed it up: Copilot seat count was actually scaled back because adoption wasn't materializing. The head of Microsoft's AI division said essentially the same thing in plain English: almost nobody is using it.
Why This Happens
A top comment on that same r/technology thread (5,500 upvotes) said it plainly:
"I don't think they convinced anyone what the use cases are for Copilot. Most people don't ask many questions when using their computer, they just click icons, read, and scroll."
That's it. That's the whole problem.
The way people actually work is: they have established habits. They know what they do when they need to draft an email or analyze a spreadsheet. Copilot sitting in the corner of their screen doesn't interrupt that habit. It doesn't insert itself into the workflow. It waits to be asked.
And nobody trained them what to ask.
The "Just Announce It" Failure Mode
Here's the typical enterprise AI rollout:
- Procurement buys seats (often because a vendor offered a bundle deal, or because a competitor announced they were using AI)
- IT provisions access
- Someone records a 30-minute intro video nobody watches
- An email goes out: "Copilot is now available. Use it to be more productive."
- Three months later: 47 of 4,000.
The failure isn't the tool. It's the assumption that access equals adoption.
This doesn't happen with any other tool. Nobody rolls out Salesforce with a single email and expects 4,000 users to figure it out. Salesforce gets an implementation partner, a training plan, and a phased rollout.
AI tools — despite being far more open-ended and requiring far more behavior change — get an announcement email.
What Actually Moves the Number
Based on deployments where we've seen teams go from sub-20% to 65%+ utilization in 30 days, the pattern is consistent:
1. Anchor task per role
Not "use Copilot." Specific: "Use Copilot to draft your weekly status update every Friday." Or: "Before every PR submission, run a Copilot review pass." One task, high repetition, visible time savings.
2. Live session, not a video
The single most impactful thing you can do is a 90-minute live session with real tasks from the actual team. Side-by-side comparisons of lazy prompts vs. structured ones. Engineers ask questions. They see results in real time. That's what creates believers.
3. Social proof loop
A #ai-wins Slack channel where people post time saves. When an engineer sees a peer posting "just generated a 3-page API doc in 8 minutes," they try it. Visible wins compound.
4. Measurement
You need to know if it's working. Weekly active users per seat. Self-reported time savings by task. Teams that measure adoption improve it; teams that don't measure plateau at 20-35%.
The Math on Fixing This
The good news: if your utilization is at 47/4,000 (1.2%), there's enormous upside. Even getting to 40% would be a 33x improvement.
Industry benchmark for well-trained teams: 65-75% utilization at 30 days post-training.
For a 100-person team at 30% utilization vs. 65% utilization:
- Difference: 35 more active daily users
- If each saves 30 minutes/day: 17.5 hours/day recovered
- At $80/hr loaded cost: $1,400/day, $28,000/month
Against a $3,000–$6,500 training investment: payback in under a week.
If You're Sitting on Unused Seats
You have two moves:
Option A: Wait. Hope people figure it out. Defend the line item to Finance in Q3.
Option B: Treat the deployment like any other system rollout. Role-specific training. Anchor workflows. Measurement plan.
If you want to know exactly where your team stands before committing to Option B, we have a free ROI calculator: askpatrick.co/roi-calculator.html
Or if you're ready to talk about a structured training session: askpatrick.co/assessment.html
Ask Patrick runs co-work training for engineering and operations teams deploying Microsoft Copilot and Claude Code. Flat-fee sessions, not per-seat licensing. askpatrick.co
Top comments (0)