liveBook · Manning

Burnout

Burnout is a state of physical or emotional exhaustion caused by prolonged work-related stress or excessive demands, often accompanied by reduced effectiveness and motivation.

How 3 Manning books explain it

Think Like a CTO

Burnout is a state of physical or emotional exhaustion caused by prolonged work-related stress or excessive demands.

How it is used
Uses burnout as a warning to reassess team capacity and get help before people leave.
How deep it goes
Provides observable warning signs and a staffing response, without a diagnostic scale or fixed capacity threshold.
Examples
Uses missed deadlines, unused time off, and stress during a key person’s absence as practical warning signs.
What you can do after
Practice/perform capacity checks using retrospectives and time-off patterns, then seek support before the team burns out.

Read how Think Like a CTO explains burnout →

Lead Developer Career Guide

A state of physical or emotional exhaustion caused by prolonged or excessive work-related stress.

How it is used
Protects team well-being, morale, productivity, and deliverable quality through workload management and supportive leadership.
How deep it goes
Explains causes, symptoms, prevention, communication, and brief coping tactics without developing a clinical treatment framework.
Examples
Uses overwork, tight deadlines, fatigue, concentration problems, breathing exercises, meditation, workload sharing, and task estimation as examples.
What you can do after
Diagnose/debug with it by recognizing burnout signals, communicating overload, regulating stress briefly, and correcting workload or timeline problems.

Read how Lead Developer Career Guide explains burnout →

Think Like a Software Engineering Manager

Burnout is a state of physical and emotional exhaustion caused by prolonged excessive workplace stress.

How it is used
Uses burnout prevention to protect team well-being, sustain delivery, and strengthen effective engineering management.
How deep it goes
Explains workplace causes, observable warning signs, and prevention practices, then defers more detailed treatment.
Examples
Uses missed deadlines, declining productivity, on-call overload, deteriorating services, and a quarter-long improvement effort as concrete examples.
What you can do after
Apply workload, communication, boundary-setting, recognition, and capacity-planning practices to prevent burnout on a team.

Read how Think Like a Software Engineering Manager explains burnout →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.