Debugging your communication for more success and efficiency in DevOps
summary
DevOps succeeds when communication is debugged not when more tools are added: tools help but cannot replace communication. Measured impact is 7% words, 38% voice, 55% body language, so email loses most signal; use video chat for distributed standups and tie remote members to the Kanban board with a movable camera that the remote person controls. Emphasize feedback loops, commitment over consensus, nonviolent phrasing and appreciative inquiry to reduce rework and missed expectations.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:41Different behavior
- 10:12Solution?
- 14:17We cannot not communicate!
- 26:33The inconsistent message
- 41:30Context matters!
related talks
46mDebugging your communication for more efficiency in DevOps
55mDevOps isn't just about developing
23mCommunication is just as important as Code
55mEffective Communication in a Remote First World
30mIf DevOps Is Culture, Why Does Everyone Only Talk About Tools?
25mDevOps: Why do we Keep Messing Up?
05mDevOps Is Not a Department
41mHow UX Saved My DevOps