Leading software teams with context (visibility)
summary
Claims four measurable pillars—process, operation, people, product—and shows how to instrument each with concrete signals: run DORA metrics and watch deployment frequency and lead time trends, add regular engineering surveys and monthly engagement checks, set 99.9% SLO targets and a policy to pause features when SLOs break, use one-on-one conversations to triage surprising metric shifts, and plan migrations (split monolith into microservices) when reliability and firefighting trends predict imminent failure.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:26Presentation
- 1:18Drawing Board
- 1:34Accountability
- 2:02Questions
- 2:39Objectives
- 3:39Data
- 4:32Process
- 5:45Feasibility
- 6:36OneonOne
- 7:21Dora Metrics
- 8:27Engineering Surveys
- 9:46Operations
- 10:20Growth
- 10:58Reliability
- 13:21People
- 16:13Engagement
- 16:50Products
- 17:28Metrics
- 19:07Recap
related talks
44mEnhancing the Performance of Engineering Teams
42mHow engineering managers can lead with visibility
30mThe Sociotechnical Path to High-Performing Teams
25mCapabilities for Building High-performing Technology Teams
27mLeading a Team with Values
32mPanel discussion: The journey to building effective engineering teams
39mThe Secrets of High Performing Technology Organizations
21mBeyond Observability - Aligning Technology Performance to Business Outcomes