What happened
The Learning Guild published a July 20, 2026 article by Cassie Nii arguing that enterprise AI rollouts should be managed across three linked workstreams: governance, people, and tools. Nii says a common pattern is licensing Microsoft Copilot or another enterprise AI tool, sending a launch email, adding recorded training to the LMS, then seeing adoption stall while shadow AI persists.
Why it matters
For L&D and instructional design teams, the practical point is that tool access and one-off training are not treated as enough in Nii’s framework. She identifies governance elements such as acceptable use policies, data classification, vendor vetting, decision rights, and possible alignment with NIST AI Risk Management Framework or the EU AI Act for global operations. On the people side, she cites AI literacy, role-specific skill building, leadership modeling, communities of practice, champions, coaching, and conversations about changing roles.
What to do next
Review whether your AI workstreams are connected rather than running separately. Inventory sanctioned and unsanctioned AI tools, form a cross-functional steering group including L&D, IT, Legal, HR, business leaders, and frontline voices, and draft baseline use and data rules. Treat projected benefits, adoption levels, and risk exposure as uncertainties to measure with quality, time-saved, adoption, and risk indicators before expanding use cases.
About this briefing
Reviewed by TutorFlow Editorial. We link the primary source, preserve its publication date, and distinguish reported claims from TutorFlow analysis. Our commentary focuses on practical decisions for educators and training teams.
Discussion (0)
Open to everyone