Microsoft: Centralising EMEA programme reporting and Copilot adoption
The role, the work and what changed
In his own contractor role inside Microsoft's EMEA Data Centre Operations, James centralised programme reporting with every EMEA country lead and embedded Copilot into their existing biweekly reporting. Documented processes remained with the internal team after the role ended.
Role period: December 2025 to February 2026. Case summary updated 5 November 2026.
- Primary job
- Programme prioritisation, shared workload/status reporting and operating processes for EMEA leadership.
- Working context
- Every EMEA country lead, with on-site data centre visits to understand the operations behind the reporting.
- Copilot scope
- Prompts and workflows for site updates, risk registers and leadership briefs inside the existing biweekly reporting routine.
- Reported adoption
- Roughly 10% to all EMEA country leads in this engagement. This is a reported group-level outcome, not Microsoft-wide adoption or audited telemetry.
The challenge
EMEA Data Centre Operations needed one view of which programmes mattered. Information sat across countries, lessons did not travel consistently and leadership lacked a clear workload picture. Microsoft 365 Copilot licences were already available, but usage among country leads was roughly 10%. Programme visibility was the primary brief; Copilot adoption formed part of improving that work.
What we did
James worked with every EMEA country lead and visited data centres to understand operations first-hand. He mapped the gaps in prioritisation, information sharing and lessons learnt, then designed programme and status-reporting processes that brought the information together for leadership.
He built Copilot prompts and workflows into the biweekly reporting cycle, helping country leads synthesise site updates, normalise risk registers and prepare leadership briefings. He documented the processes so the internal team could continue after the three-month role.
// run against The Tenhaw Way, published in full and free to adopt without engaging us
The outcome
Programme information was centralised, giving EMEA leadership a shared view of high-level workload and status. 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. Documented ways of working remained with the internal staff after James's role ended.
How this experience applies
The transferable practice is to connect AI adoption to a task people already own: gathering updates, reviewing risks and preparing a decision-ready briefing. This was James's own programme-management contractor role inside Microsoft, with Copilot embedded in delivery practice. It was not a standalone Tenhaw Copilot implementation engagement.
Internal programme names, tooling, individuals and decision timings remain confidential.
Other engagements
Sector first, because that is the next question. All 13 are on the hub.
Standing up the delivery engine behind a £40bn hydrogen business case
£40bn, business case underpinned
Turning erratic global delivery into something the business could plan around
3, regions: UK, USA, Singapore
From traditional ways of working to an agentic operating model
54 vs 1, front-end changes shipped on the same epic, outcome ticket against normal ticket, in a similar cycle time
Want the same thing, in your organisation?
A 30-minute call with James Rooney about the workflow, product or delivery challenge you want to improve. Leave with a rough scope and a practical next step.
most start with a fixed-price AI Readiness Audit · £44,000 · 4 weeks · working prototypes
No time that suits? Email hello@tenhaw.com. Calendar not loading? Open it on cal.com.
Questions about this engagement
Was the Microsoft work a Tenhaw engagement or James's own role?
It was James Rooney's own contractor role inside Microsoft, as Program Manager for EMEA Data Centre Operations from December 2025 to February 2026. This is founder experience, like the HSBC and Discovery roles. It demonstrates programme delivery and Copilot adoption within a live reporting practice, rather than a standalone Tenhaw Copilot contract.
What was James's primary job in Microsoft EMEA Data Centre Operations?
Orchestrating priority programmes and making high-level workloads visible to the EMEA senior leadership team. James worked with every EMEA country lead, centralised programme information and documented the operating processes. Copilot was designed into this reporting work; it was part of the delivery practice.
How was Copilot adoption built into Microsoft country leads' reporting?
In this engagement, it included prioritisation, centralised programme status, documented ways of working and prompts used in the country leads' existing biweekly reporting cycle. The practical job gave people a reason to use the tool and a routine in which to review its output. Reported usage rose from about 10% to all the EMEA country leads involved, not all Microsoft staff.
Who should read the Microsoft EMEA programme-delivery case study?
Technology, operations and transformation leaders coordinating programmes across countries or sites. It is particularly relevant where programme information is fragmented and Microsoft 365 Copilot is already licensed but weakly used. The case shows how reporting, prioritisation and a tool-adoption routine can be designed together.
Which Tenhaw engagement covers work like the Microsoft EMEA role?
Tenhaw's Programme & Delivery Management engagement can rebuild programme reporting, prioritisation and governance across teams and suppliers. Where Copilot is already part of the client's approved stack, adoption can be designed into that live work. The published engagement is £18k–£35k per month, with the actual scope agreed before work begins.