Copilot for enterprise knowledge management: Kerry Group’s real-world playbook
Kerry Group’s Shane McGibney is using Microsoft 365 Copilot to turn decades of siloed expertise into a competitive edge—positioning Copilot for enterprise knowledge management as a daily, decision-support partner that fuses proprietary insight with external market signals [1][2].
Lead: Kerry Group and the knowledge challenge
Kerry, a global supplier of ingredients for food, beverage, and pharmaceuticals, has accumulated over 50 years of institutional know-how. That expertise has historically lived across regional systems and files—making it hard to find, reuse, and scale across geographies like China, the US, and Europe [1][2]. McGibney, Business President for Transformation and CEO of Kerry’s Biotechnology Solutions business, needed a way to connect business strategy with highly technical scientific domains [1][2].
Why Copilot is framed as a “knowledge partner,” not just a tool
McGibney characterizes Copilot as a true knowledge partner. It surfaces and summarizes Kerry’s internal content, then pairs it with up-to-date external market data and trends—helping him challenge assumptions, assess risks, and make faster calls on investments, fermentation processes, and broader biotechnology strategy across enzymes and probiotics [1][2]. That fusion of internal know-how and external intelligence creates what he views as a meaningful competitive advantage [1][2].
Why Copilot for enterprise knowledge management matters now
By centralizing and contextualizing fragmented knowledge, Copilot helps Kerry operationalize its collective expertise. For McGibney, the result is spending less time hunting for information and more time on high-value work—effectively eliminating “offline” gaps in his day-to-day decision-making rhythm [1][2]. He cites Copilot’s ability to rapidly synthesize unfamiliar technical and market information so he can engage scientists in informed dialogue and steer strategy with confidence [1][2].
How Copilot connects internal R&D with external market data
At Kerry, Copilot aggregates internal documents and insights from decades of problem-solving, then layers in current market intelligence. The value is twofold:
- It unlocks institutional memory for reuse across regions and teams.
- It grounds strategy in both proprietary R&D and real-time external trends [1][2].
This model reflects Microsoft 365 Copilot’s role in business workflows, where summarization, synthesis, and context-building give leaders faster paths to clarity without replacing domain experts [1][2]. For official product context, see Microsoft’s overview of Copilot capabilities in Microsoft 365 (external).
Real-world example: 86-page acquisition document distilled to actionable insight
A telling moment came just before a holiday period: McGibney received an 86-page acquisition proposal and needed to get briefed fast. Using Copilot alongside Microsoft’s Researcher, he generated executive summaries for each section, then used those outputs to guide targeted follow-up questions. The outcome: he became well-briefed in about 90 minutes—without reading the full document end-to-end. It’s a clear case of enterprise document summarization Copilot applied to a high-stakes decision [1][2].
Measured benefits and early adoption feedback at Kerry
Early user surveys at Kerry showed practical momentum: most users reported saving at least 20 minutes per Copilot use case, and 97% said they wanted to continue using it daily [1][2]. These signals underscore both time-to-value and sustained user intent—key markers for any Kerry Group Copilot case study focused on Microsoft 365 Copilot business use [1][2].
Practical workflow recommendations for enterprise leaders
Organizations exploring a similar path can adapt McGibney’s approach:
- Centralize access: Ensure core repositories and knowledge stores are included so Copilot can surface and connect relevant internal content.
- Pair internal with external: Prompt Copilot to integrate current market data and trends alongside proprietary materials.
- Summarize, then probe: Start with executive summaries of long documents; use those outputs to drive sharper follow-up questions.
- Keep humans in the loop: Use Copilot outputs to inform conversations with subject-matter experts and validate assumptions.
This workflow mirrors how to reduce executive document review time with Copilot to 90 minutes in cases where structured summaries accelerate targeted due diligence [1][2].
Governance, accuracy, and risk considerations
McGibney’s usage shows how leaders can use Copilot to challenge scientists and assess biotech risks while preserving expert judgment. Treat AI as a partner that accelerates synthesis—not as a replacement for technical validation. Encourage teams to verify outputs, document decisions, and iterate prompts to improve clarity and consistency over time [1][2].
Finally, leaders building a Copilot knowledge partner model should align people, process, and platforms: establish access permissions, define review checkpoints, and track adoption metrics that matter to the business. For broader market context on AI developments from Microsoft, see the ongoing updates on the Microsoft AI Blog [3]. For practical, role-based playbooks to support implementation, explore ToolScopeAI’s guides: Explore AI tools and playbooks.
Sources
[1] Kerry Group’s Shane McGibney on how Copilot is his knowledge …
https://news.microsoft.com/source/2026/03/10/kerry-groups-shane-mcgibney-on-how-copilot-is-his-knowledge-partner/
[2] Kerry Group’s Shane McGibney on Copilot as a Knowledge Partner
https://news.microsoft.com/source/emea/features/kerry-group-copilot-knowledge-partner/
[3] Microsoft AI Blogs | Artificial Intelligence News and Updates
https://www.microsoft.com/en-us/ai/blog/
[4] Knowledge Management Strategies in the era of Copilot – YouTube
https://www.youtube.com/watch?v=iVyNvpoWZos
