When companies talk about AI tool adoption, they usually mean developers. GitHub Copilot for the engineering team. Claude Code for the backend squad. The metrics, the ROI conversation, the training budgets — all developer-focused.
Meanwhile, the rest of the company got Microsoft 365 Copilot and nobody said a word.
The Forgotten Half of Your AI Rollout
M365 Copilot is deployed across HR, Finance, Marketing, Operations, Legal, and Customer Success at thousands of companies right now. These teams got access the same way the developers did: an IT email, a 30-minute video, and a "good luck."
The difference is nobody's measuring whether they're using it. There's no utilization dashboard that VPs of HR check. There's no quarterly review where Finance justifies their Copilot spend.
So it quietly disappears.
Anecdotally, these teams are at even lower utilization than developer teams — under 15% in most cases — because:
The use cases aren't obvious. Developers at least know "Copilot autocompletes code." What does it do for an account manager? For an HR business partner?
The training materials are developer-biased. Microsoft's own documentation defaults to code examples. Prompting guides talk about functions and APIs.
Nobody's accountable for results. Engineering has sprint velocity. HR and Finance have... a subscription nobody checks.
What Actually Works for Non-Dev Teams
The pattern that moves the needle for non-developer teams is the same as developer teams, just with different anchor tasks.
For HR teams:
- Draft job descriptions from a bullet-point brief
- Summarize candidate feedback across multiple interview notes
- Generate first drafts of policy documents
- Summarize meeting transcripts from hiring panels
For Finance teams:
- Draft budget narrative for board decks from spreadsheet data
- Summarize lengthy vendor contracts to bullet points
- Generate variance analysis commentary from Excel outputs
For Marketing/Comms:
- Turn a one-page brief into a first-draft email campaign
- Repurpose a blog post into 5 social posts
- Summarize competitor announcements into internal briefings
For Customer Success:
- Draft QBR decks from account notes
- Summarize ticket trends into weekly reports
- Generate templated renewal emails personalized by account context
The principle: one anchor task per role. Not "use Copilot more." One concrete task they do weekly, where Copilot saves 30–60 minutes.
The Measurement Problem Is Worse Here
Engineering teams at least have proxy metrics — PR velocity, deployment frequency, time in review.
Non-developer teams have almost none. When you ask "is your team getting value from M365 Copilot," you'll usually get:
- "Some people use it, some don't"
- "I tried it for a meeting summary once"
- "It didn't seem to understand our terminology"
That last one is important. M365 Copilot works significantly better when trained on your company's documents — SharePoint content, internal wikis, existing templates. Most teams don't know this. They use it cold, get generic outputs, give up.
The Training Conversation Your L&D Team Needs to Have
If you're in L&D and you're planning AI adoption training, the developer conversation and the non-developer conversation are different:
| Topic | Developer Teams | Non-Developer Teams |
|---|---|---|
| Anchor task | Code review, test writing | Meeting summaries, document drafting |
| Success metric | PR cycle time, utilization % | Time saved on recurring tasks |
| Common failure mode | Over-relying on output | Under-trying due to bad first results |
| Training format | Hands-on with real code | Live prompting with real documents |
| Time to value | Week 1-2 | Week 2-4 (slower ramp) |
The non-developer ramp is slower, which is why you need structured onboarding — not just access.
Free Resource
If you want to know whether your Copilot deployment is paying off — for dev or non-dev teams — we built a free ROI calculator: askpatrick.co/roi-calculator.html
It takes 2 minutes and tells you exactly how much productivity is sitting unused in your current subscription.
Ask Patrick trains engineering and non-engineering teams on Claude Code and Microsoft Copilot. If your M365 rollout is stalled, the free AI Readiness Assessment is a good place to start.
Top comments (0)