Episode 18: Jack Falvey on Why AI Governance Starts With the Problem
Items couldn't be added
The title couldn't be added to your basket.
Couldn't add title to Wish List
‘Remove from Wish List’ failed
Adding to library failed
‘Follow podcast’ failed
‘Unfollow podcast’ failed
-
Narrated by:
-
By:
Employees are using AI at work. The question is whether leadership gives them safe tools, clear boundaries, and a reason to follow the rules.
IT infrastructure manager Jack Falvey joins Andrew DeGood and Liz Short to examine shadow AI, data exposure, coding governance, and the growing pressure on teams responsible for systems they do not fully control. Jack explains why users often arrive with a preferred technology before anyone has defined the problem. His answer is practical: understand the need, standardize what should be repeatable, test changes, and keep access narrower than the requested shortcut.
The conversation moves from GitHub Copilot and PowerShell to custom technology stacks and employee-built applications. The Turn looks five years ahead. When anyone can build software, governance cannot begin after deployment.
Better adoption requires more than buying a license. It requires leadership communication, usable approved tools, technical context, and accountability for what reaches production.