Do Low Code projects need Change Management? Appsolutely!
summary
Claims that 75% of new apps will be low/no‑code by 2026 (Gartner) meets concrete failures: a Cisco audit finds ~90 vs 1,200 cloud services, and early copilot rollouts show governance gaps. Advice is specific: create a data charter and data council, enforce CRUD role‑based access, run a Co‑pilot lab sandbox to anonymize prompts, build a center of enablement for fusion teams, run maturity/readiness assessments, and treat change management as continuous — not an 11th‑hour checkbox.
AI-written summary · about
chapters (10)
- 0:00Low-code ecosystems and change management
- 5:05Low-code evolution history
- 10:28Shadow IT risks
- 15:12Data strategy for AI and low-code
- 21:55Silos in enterprise solutions
- 27:40Citizen development enablement
- 35:53Security and compliance
- 40:54Adopting AI capabilities
- 44:23Key takeaways and next steps
- 47:21Q&A on governance
related talks
44mCommunities of Practice: The Missing Piece of your Agile Organisation
29mSupporting Low Resource Regions with your Dev Rel Strategy
26mCulture at Speed Scaling Without Losing People in the AI era
44mWhy Is My Community In Danger?
38mBringing a multicultural team together
34mWhy We Need Codes of Conduct -- and Why They're Not Enough
20mThe Code Dreams are Made of: Ideals, Innovation, Inclusion
19mIt’s Dangerous to Go Alone! Lessons Learnt from Onboarding New Cloud...