Partner with us

Get your ticket

Call to action
Your text goes here. Insert your content, thoughts, or information in this space.
Button

Back to speakers

Patrick
Mcgarry
Federal Chief Data Officer
ServiceNow
Patrick McGarry is the Federal Chief Data Officer at ServiceNow, a role he assumed following the company's acquisition of data.world, where he previously built the Open Data Community, Partner Ecosystem, and Public Sector practices. With two decades of experience spanning defense, intelligence, and the private sector, he leads data strategy and AI governance for ServiceNow's U.S. federal clients, with particular focus on Department of Defense modernization initiatives. Patrick began his career as an enlisted member of the U.S. Navy before transitioning to technology leadership roles at Red Hat, Alcatel-Lucent, and SourceForge, where he specialized in building open developer ecosystems. His expertise in metadata management, knowledge graphs, and functional data governance has made him a trusted advisor on AI adoption strategies across federal civilian agencies, defense organizations, and the Intelligence Community. Patrick brings a unique socio-technical perspective to organizational design and data strategy; recognizing that successful AI and data initiatives require institutional change, not just technical deployment. In his daily work, he positions data infrastructure as trust infrastructure, helping Federal leaders build durable capabilities that enable faster decision cycles while maintaining security, compliance, and mission readiness in complex operational environments.
Button
20 May 2026 13:15 - 14:00
Panel | The AI data stack decision: Infrastructure, enterprise, and implementation perspectives
Every team building with AI hits the same wall: what do you own, what do you outsource, and how do you know the difference before it costs you 18 months and a rewrite? The answer looks completely different depending on where you sit. Infrastructure teams see it as a capacity and control problem. Enterprise leaders see it as a governance and risk problem. The people implementing it see it as both, plus everything nobody planned for. This panel brings together voices from all three layers to cut through the theory and get into where these decisions actually land, what creates long-term leverage, what becomes a maintenance burden, and what the vendors and integrators who've seen hundreds of these calls wish teams had asked earlier.