Making Connections Visible
summary
Argues that visibility into integration points fixes hidden work and long lead times, showing complexity forces specialization which then raises coordination costs. Cites tooling gaps between ServiceNow, JIRA, PagerDuty, Salesforce, GitHub/GitLab and a 120+ DevOps tool landscape, and cites security talent gaps of roughly 6 million demand vs millions short. Offers a hands-on value stream canvas exercise that mapped a network capacity change from hours to six weeks, made bottlenecks physically visible and forced leadership to act — a practical way to defrag your value stream.
AI-written summary · about
chapters (15)
- 0:00Making Connections Visible
- 2:20Complexity Drives Necessary Specialization
- 4:24Make Connections Visible
- 7:04Security Breaches
- 9:07Im the Calvary
- 11:01specialisation
- 11:18coordination costs
- 14:18full stuck engineers
- 17:09burnout
- 18:01healthcare
- 18:59DevOps tools
- 19:35Different views of the world
- 21:28Poll
- 23:15Exercise
- 27:40Value Stream Canvas
related talks
32mPanel discussion: The journey to building effective engineering teams
05mMany Hands Make Light Work
30mVisualizing Transformation: 5 Ways to Make Work More Visible
30mA Story of DevOps Transformations
48mNew barriers for DevOps adoption
31mFrom Legacy to ...
37mDevOps Topologies 10 years on: what have we learned about silos, collaboration...
39mBuilding the missing links between Strategy and Operations