DevOps: Top Lessons Learned on Shifting Left For Accessibility and Other Experts
summary
Research of 36,000 organizations over six years shows high performers deploy multiple times per day, take one hour or less from commit to production, are seven times less likely to trigger SEV1 incidents and fix outages in an hour, and are twice as likely to beat profitability and have employees recommend the workplace. Examples: Intuit runs 165 experiments and lifts conversions 50%, Microsoft paused features to pay down debt, and shifting accessibility left succeeds when teams build self‑service tooling for fast feedback.
AI-written summary · about
chapters (7)
- 0:00Introduction and journey
- 0:30DevOps and performance
- 21:56Technical debt dangers
- 25:18Cultural foundations
- 28:57Systems thinking metaphors
- 34:09Accessibility integration
- 40:45Q&A and closing
related talks
34mDevOps: Next
47mDevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
45mDevOps: The Key to IT Performance
29mDevOps Anecdotes
27mDevOps Next
54mEffective DevOps for Organizations
31mThe Data Behind DevOps: What Does It Take To...