EY refers to the global organization, and may refer to one or more, of the member firms of Ernst & Young Global Limited, each of which is a separate legal entity. Ernst & Young Global Limited, a UK company limited by guarantee, does not provide services to clients.
How EY can help
-
We embed leading-edge AI capabilities into everything we do for you, to help ensure the rapid delivery of AI-powered services and solutions. Learn more.
Read more
With AI at an inflection point, clients looking to us for leadership and the competition moving quickly, the EY team knew our investment in this space demanded laser focus.
As one of 14 companies that were selected to participate in the Harvard Frontier Firm AI Initiative charting the course for AI disruption, with a clear AI strategy to execute at scale and a highly skilled and finely trained workforce, we were confident we had the capabilities, the appetite to adopt AI and the readiness to adapt as the first global client in Microsoft’s M365 Copilot Early Access Program.
Knowing what was to come, we put AI adoption to the test. Starting with a small-scale pilot phase in August 2024, we rolled out the tool more broadly that October, with a full-scale deployment five months later. Taking full advantage of our longstanding alliance with Microsoft, we positioned ourselves as “Client Zero,” seeing the opportunity not only to experiment but to lead by example.
Having conducted significant testing, due diligence and a readiness program, we knew Copilot would meet our security, compliance and operational standards prior to launch, and that it wouldn’t compromise data security. Operating within the Microsoft 365 ecosystem, it adhered to our existing identity, access and compliance policies. What we were looking for was solid proof that complex organizations could move quickly without compromising governance or culture.
But we also anticipated that opening up AI across all users would require more than a typical implementation. This transformation demanded a cultural shift in how our people worked collaboratively on a day-to-day basis. It would have a major change to how they learned, how we looked at data, security and privacy. And we needed to know whether steps would need to be taken - in an abundance of caution - to mitigate the potential risk of breaches and unauthorized access.
We started by operationalizing the rollout through mandatory training with attestations required for our all 6,500 licensed users and reminded our people of our Code of Conduct and privacy commitments. We made sure to tell our people that we trusted them to use their best judgment and our guidelines to actively monitor and address potential risks that could emerge and instill comfort throughout the transition. We encouraged them to build in critical time to experiment, from 30 to 60 minutes per week on hands-on trialling, and equipped them with FAQs and escalation paths should incidents arise.
Early and consistent communication tackled the need for oversight. Peer-led forums and feedback loops allowed for continuous process improvement via surveys, champion forums, dashboard analytics and role-specific playbooks with packaged prompts and patterns that teams actually used.
Hundreds of power users and change champions worked behind the scenes, buddying as colleagues and busting myths to dispel concerns and shape the conversation. Some expected hiccups arose - like early skepticism of potentially autonomous action and privacy concerns. There were also some unexpected challenges. Some users were disillusioned when Copilot didn’t match their expectations. We responded by refocusing teams on the tool’s strengths, and reminded them that we’ll adapt and adopt as capabilities expand across all MS applications.
We also reiterated our commitment to clear governance to help enable fast and safe deployment with risk-based, “human in the loop” checks and giving people dedicated time to explore the tool.
Pairing leadership accountability with strategic piloting and meaningful engagement was a recipe for success. We hosted “show me your Copilot” demos in established meetings, capturing day-in-the-life workflows, and packaged prompts and patterns based on team usage. And guess what: adoption stuck.