Non-coding skills for successful Automation in your organization
summary
Automation success depends on adoption not just code: a platform team builds 28 VMs using Azure artifacts, Bicep modules, PowerShell DSC and Azure Policy guest configuration, but object storage becomes a 14‑hour constraint. Typical requester scenario shows 7h45m hands‑on vs 70h30m lead time; automating steps cuts lead time to about 51h30m. Use personas (Sara), map value chains, treat outputs as products with onboarding, start with MVPs and innovators, and measure queues and constraints before optimizing technology.
AI-written summary · about
chapters (15)
- 0:00Non-coding skills in automation
- 1:22Why technology alone doesn’t guarantee success
- 3:27Solutions beyond coding
- 6:43Business value in automation
- 9:53Aligning with business goals
- 13:23Customers and value chains
- 17:41User personas for needs
- 21:59Value chains for prioritization
- 24:28Avoiding workflow silos
- 27:14Pipelines as trust tools
- 29:00Optimizing workflows
- 30:23Tech adoption curves
- 33:52Agile workflows
- 35:17Value stream mapping
- 43:01Q&A
related talks
24mEngaging People & Process Around Enterprise Adoption for Network Automation
20m5 Traits That All Top-performing Automation Engineers Have
34mDevOps culture
40m100 Teams, 100 Ways to Fail
06mSoftware is People
32mWhat Not to Automate
41mWhen /bin/sh Attacks: Revisiting "Automate All the Things"
27mDevOps and Baking