Copilot adoption in the enterprise: getting from licences to use
Build Copilot into a routine your team already owns. Read the scoped Microsoft EMEA example from James Rooney’s contractor role and the Learn options.
Copilot adoption rises when it is built into a routine people already have to do, not offered as a general tool. In his three-month contractor role as Program Manager for Microsoft’s EMEA Data Centre Operations, Tenhaw’s founder built Copilot into the country leads’ biweekly programme reporting. Tenhaw’s Learn programmes apply the same approach to your teams’ real work.
30 minutes with James · how this would work in your organisation
The basis for this approach
This is our adoption approach. The Microsoft example was James Rooney’s own contractor role, December 2025 to February 2026, not a Tenhaw Copilot implementation engagement or a Microsoft-wide adoption study.
The demand signal
In James’s Microsoft contractor role, Copilot use among the country leads moved from roughly 10% to all of them within this leadership group, as reported for the engagement. The case describes adoption in those reporting routines, not Microsoft-wide usage or an independently audited adoption study.
Bring the reason this is on your agenda to a 30-minute call with James, and we can explore what it would take in your organisation.
Book a 30-minute callWhy it stalls
2 failure modes we keep meeting
The tool sits beside the work
A licence alone does not change the reporting or review routine. Start with a task people already own and show where the tool helps them prepare something they need.
The adoption number hides who was involved
Keep the cohort and activity beside the figure. In the Microsoft case the measure concerns the EMEA country leads in James’s contractor engagement, not every employee or every use of Copilot.
If one of these sounds familiar, bring it to a 30-minute call with James and we can explore a way past it.
Book a 30-minute callHow we approach it
3 moves, in order
- 01
Choose a recurring task
James’s contractor role used country leads’ existing biweekly reporting: gathering site updates, normalising risks and preparing leadership briefings. Choose an equivalent real task in your team.
- 02
Practise and review in the workflow
Learn’s £24,000 fixed team programme uses two workshop days and four weeks of weekly pairing over six weeks. Participants bring the task, approved tools and examples, then review what the outputs need.
- 03
Leave a method the team can repeat
Document the decisions, checks and working steps, and have the team use them. The leadership day is £8,500 for up to 12 executives to agree three valued workflows; production build work is a separate scope.
Document the decisions, checks and working steps, and have the team use them.
Prefer to talk it through? Ask us on a discovery call →
Sources
Every source below was opened and read before it was attached. Where nothing survived that check, the claim on this page was softened rather than given a plausible-looking link.
James Rooney’s Microsoft EMEA contractor roleProgram Manager, EMEA Data Centre Operations, December 2025 to February 2026. Founder experience, not a standalone Tenhaw Copilot implementation engagement.Tenhaw, LearnThe closest guides to this one
Nearest first, then the rest. Each one carries the same label: written from delivery, or the method we would bring. All 34 are on the hub.
Setting up an AI centre of excellence
Build an AI centre of excellence around a practical method, accountable workflow owners and learning your teams can reuse. See the Learn cohort scope.
Our approachHow to measure AI coding productivity
Measure AI-assisted delivery through outcomes, cycle time and quality evidence. Read the PPL comparison with its scope and limits intact.
DeliveredDocument intelligence to business intelligence
Turn source documents into data your business can check and use.
DeliveredWhat does an AI-native software delivery lifecycle look like?
Connect requirements, AI engineering and human release decisions.
DeliveredTarget operating model for an AI-native organisation
Design what agents do, what people decide and how the work improves.
DeliveredVoice agents and conversation intelligence
Choose recorded-call insight or a live agent, then design the right workflow.
Or bring the problem to a call instead of reading three more of these.
Book a 30-minute callWork out the next step for your team.
A 30-minute call with James Rooney to discuss your workflow, people and budget. Leave with a rough scope and a useful next step.
Learn: team working-method programme · £24,000 fixed · 6 weeks · excluding VAT
No time that suits? Email hello@tenhaw.com. Calendar not loading? Open it on cal.com.
Describe the work
Describe the work in a paragraph. James replies with a rough scope and budget range within two working days.
Questions this guide answers
Why do Copilot licences go unused?
The existing Tenhaw guidance points to the workflow: the tool sits beside the task rather than within a routine people need to complete. Start by examining the actual work, the review step and what useful output people need.
How do we measure adoption?
Define the cohort, routine and reporting period, then measure use in that work. Keep self-reported use distinct from an independently audited measure, and do not extend one cohort’s result to an entire organisation.
Where should we start?
Choose a recurring task with a clear owner, usable examples and a review step. In James’s contractor role inside Microsoft, that was the EMEA country leads’ biweekly programme reporting.
Training or embedding?
Learn combines practical workshops with pairing on real work, so training and use reinforce each other. If the need is broader programme reporting and coordination, Programme & Delivery Management can be scoped separately.
Was the Microsoft work a Tenhaw engagement?
No. It was James Rooney’s own three-month contractor role as Program Manager for Microsoft’s EMEA Data Centre Operations, from December 2025 to February 2026. It is founder experience, not a standalone Tenhaw Copilot implementation contract.