The Actual Math Behind Burnout
A practical framework for what actually predicts burnout, built around the balance between what a job demands and what it gives back.
Burnout is often described as a personal failure to cope, a resilience gap that better time management or a more positive attitude would supposedly close. The actual research describes something closer to an equation, and it is worth understanding the equation, because it points toward solutions that have nothing to do with willpower.
In 2001, organizational psychologists Evangelia Demerouti, Arnold Bakker, and colleagues published what has become one of the most influential frameworks in this field, known as the Job Demands Resources model. Its core claim is straightforward: every job can be described along two independent dimensions. Job demands are the aspects of work that cost something to sustain: workload, time pressure, emotionally difficult interactions, physical strain. Job resources are the aspects that help offset that cost: autonomy over how work gets done, support from colleagues and supervisors, clear feedback, a sense of meaning in the work itself.
The model's central, well replicated finding is that burnout does not track simply with how demanding a job is. It tracks with the relationship between demands and resources. A highly demanding job with strong resources, real autonomy, genuine support, clear recognition, can sustain a person for years without producing burnout. A moderately demanding job with almost no resources, no autonomy, no support, no meaningful feedback, can produce burnout surprisingly fast, even at a workload that would look entirely reasonable on paper to someone looking in from outside.
It helps to see this in specific, concrete terms rather than as an abstraction. A demand might be a genuinely heavy caseload, a resource might be a manager who actually reads your updates and adjusts expectations accordingly rather than one who only shows up when something goes wrong. A demand might be constant context switching between unrelated projects, a resource might be real say over which projects you take on in the first place. Two jobs can look identical on an org chart and produce completely different outcomes depending entirely on which of these actually exist underneath the job title.
It helps to see this in specific, concrete terms rather than as an abstraction.
Research building on this model has also found that demands and resources tend to predict different pieces of the burnout picture specifically. High demands correlate most strongly with the exhaustion dimension, the sheer depletion of energy. Low resources correlate most strongly with the cynicism dimension, the growing detachment described elsewhere on this site. This is a genuinely useful distinction, because it means two people who both describe themselves as burned out might be dealing with fairly different underlying problems, one drowning in sheer volume, the other starved of any real say or support even at a manageable workload.
This framework also explains a common and frustrating experience: doing everything within your own control, sleeping better, exercising, trying to think more positively, without the underlying burnout actually lifting. If the core issue is a chronically low level of job resources, autonomy, support, recognition, then individual coping strategies are addressing a variable the model does not identify as the primary driver. They can help at the margins. They rarely resolve the underlying mismatch on their own, because the mismatch lives in the job, not in the person trying to cope with it.
Later refinements to the model have added an important nuance: resources do not just offset demands in a simple subtraction. They specifically buffer the relationship between demands and burnout, meaning the same high workload produces meaningfully less strain when real resources are present alongside it than when they are not. This is part of why two people in nominally identical roles can end up in very different places after a year, even when their actual task list looked nearly the same on paper.
The practical use of this framework is in naming, specifically, which side of the equation feels most broken in your own situation. Is the actual volume of work the core problem, in which case the target is genuinely reducing demands. Or is the workload itself tolerable but the isolation, lack of input, and absence of any real feedback loop the deeper issue, in which case the target is building resources rather than simply working less. These require different conversations, often with different people, and conflating them tends to produce exactly the kind of advice, take a vacation, try meditating, that helps far less than it should.