London

June 28–29, 2027

New York

September 15–16, 2026

Berlin

November 9–10, 2026

Burnout: A team failure mode

Reframe burnout as a systems failure and apply SRE principles to build sustainable, high-performing engineering teams.

Speakers: Diana Nanuti

Register or log in to access this video

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register
November 17, 2026
NYC 27 Pre sale ticket block image

This talk reframes burnout as a systems failure and applies SRE principles to design sustainable, high-performing engineering teams.

Is your team’s health as observable as your software?

High-performing engineering teams are celebrated for their velocity and “whatever it takes” commitment. Yet, these same traits often make them the most vulnerable to a predictable, systemic failure mode: burnout.

This isn’t a lack of individual grit; it’s a design flaw. When we architect software for 99.9% uptime but run our teams at 100% capacity, we create a system with zero fault tolerance. In this talk, we move beyond the superficial “resiliency” narrative and analyze team health through the lens of systems engineering.

We will explore how to apply SRE principles (like load shedding, redundancy mechanisms, and leading indicators) to the human element of the stack. You’ll learn why “idle capacity” is the secret to low latency, how to make cognitive load visible, and how to build a system where high performance doesn’t require a “hero culture” destined for a catastrophic outage.

Key takeaways

  • Boundaries only work when the system enforces them.
  • Burnout is a systems failure, not a people problem.
  • High performance requires slack, not heroics.