There's a story going around in engineering circles that keeps landing because everyone recognizes it.
A VP rolled out Microsoft Copilot to 4,000 employees. $30/seat/month. $1.4 million annually. The board loved the phrase "digital transformation."
Three months later, he checked the usage reports.
47 people had opened it. 12 had used it more than once.
This is satire. But it's satire that gets 1,000 upvotes because everyone who manages AI tool rollouts has lived a version of it.
Why It Keeps Happening
The top comment on a recent r/technology thread about Microsoft scaling back Copilot goals hit the actual problem clearly:
"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."
Nobody told people what to do differently. They got access to a tool and were expected to figure out the behavior change themselves. They didn't. Nobody does.
The Anatomy of a Failed Rollout
Most corporate AI tool rollouts follow the same arc:
Week 1: IT sends access credentials. Maybe a 30-minute recorded demo.
Week 2–4: Early adopters experiment. Get mixed results. Most find it faster to just do the thing themselves.
Month 2: Nobody's talking about it. The initial enthusiasm email is buried in Outlook.
Month 6: Finance pulls utilization reports. Someone schedules an uncomfortable meeting.
The tools aren't broken. The rollout is.
What Actually Changes Behavior
Three things. Just three.
1. A specific anchor task. Not "use AI to be more productive." Give each role one concrete starting point: "Use Copilot to draft your post-meeting summaries." One task. High frequency. Immediately useful.
2. A visible win in week one. If someone on the team has a genuine "oh, that saved me 20 minutes" moment and shares it — adoption spreads. If week one produces nothing memorable, momentum dies.
3. Measurement from day one. If you don't measure baseline before rollout, you can't prove anything. You can't show the improvement. You can't justify the renewal.
The Number That Gets Cited
Industry benchmark for teams with structured training:
- Utilization at 30 days: 65–75%
- Reported time savings: 45–90 min/week per person
Without structured training:
- Utilization at 30 days: 20–35%
- And it plateaus there
Same tool. Different outcome. The training is the variable.
If You're the Person Holding That Utilization Report
We built a free calculator that takes your team size, seat cost, and current utilization and shows you what's being left on the table:
👉 askpatrick.co/roi-calculator.html
If the number is painful, we do a $500 AI Readiness Assessment — flat fee, async, results in under a week:
👉 askpatrick.co/assessment.html
The 47-of-4,000 story is funny because it's true. It doesn't have to be yours.
Ask Patrick helps engineering and operations teams actually use the AI tools they've already bought. askpatrick.co
Top comments (0)