top of page

Burnout Systems Audit

S. West
1 hour ago
5 min read

The team was offered a wellness app. The real cause was an on-call rota that paged the same two engineers every weekend.

A platform team of eight shipped on time for three quarters running. Then two senior engineers went quiet in retros, one asked to move teams, and the other stopped reviewing code. Leadership responded with a resilience workshop. Nobody looked at the pager history, which showed those two had absorbed most of the out-of-hours pages since a colleague left and was never replaced.

(Composite example, assembled from patterns common in engineering teams where load drifts onto a few reliable people. The figures are illustrative.)

This is a team and system audit, not a diagnosis. If you are worried about your own health, talk to a doctor or your employee assistance programme. The World Health Organization's ICD-11 treats burn-out as an occupational phenomenon tied to the workplace, not as a medical condition, and this worksheet stays on that side of the line. It starts from the work system (workload, on-call, priorities, decision rights) and asks which conditions keep producing the defect, not which person failed to cope. Surveys disagree too much on method for one reliable burnout figure, so gather your own evidence.

Step 1: check the pattern (this is not a diagnosis)

Maslach and Leiter describe three dimensions. Tick what you are seeing across the team right now:

  • ☐ Exhaustion: depletion that rest no longer repairs; Monday feels like Friday.

  • ☐ Cynicism: detachment from the work, the product or the users, because caring has cost too much.

  • ☐ Reduced efficacy: a sense of ineffectiveness and lack of accomplishment.

All three together match what researchers call the full burnout profile. Exhaustion alone, or cynicism alone, are recognised profiles too, and they are early warnings worth acting on. This is a team and system audit, not a diagnosis. Anyone worried about their own health should talk to a doctor or their employee assistance programme.

Step 2: score the six areas of worklife (Leiter & Maslach)

Score each area for the team's system, 1 (not a factor) to 5 (severe). Write down the evidence, not the impression. The highest scores are where you start.

#

Area

What it looks like in the system

Evidence to check

Score (1–5)

1

Workload

Long weeks treated as normal, deadlines set without estimates, crunch that never ends

Committed work against capacity; overtime; out-of-hours pages per person

___

2

Control

Accountable for outcomes the team cannot decide

Who set the deadline, the scope and the tooling

___

3

Reward

Missing recognition, growth or meaningful work, not only pay

When effort was last acknowledged; who gets growth work

___

4

Community

Isolation, unresolved conflict, low trust or support among peers

Whether people ask for help; conflicts routed around

___

5

Fairness

Uneven standards, credit taken, rules applied to some

On-call spread; who carries the heavy tickets

___

6

Values

Asked to ship what isn't ready or build what harms users

Releases shipped over a "not ready" objection

___

Top area (highest score): ______

Step 3: pull the levers for your top area

Act at all three levels. Individual moves buy time; team and org moves change the conditions.

Area

Individual

Team

Org

Workload

Name it; drop self-imposed extras; protect sleep, which is biology rather than self-care advice

Show load as data: 200 points committed against a velocity of 80 means choosing which 40% ships

Cut the number of concurrent priorities

Control

Say what you need changed, and to whom

Give owners real decision rights over the work they answer for

Match authority to accountability

Reward

Name what is missing and ask for it

Make recognition routine and visible; protect growth time

Treat reward as a standing system, not an annual event

Community

Say when you need help

Make help-seeking normal; resolve conflict rather than routing around it

Staff teams so nobody works alone on critical systems

Fairness

Name the specific broken pattern

Apply standards evenly; rotate and compensate on-call

Fix uneven rules before they spread

Values

Raise the conflict early and in writing

Make "not ready to ship" a respected signal

Set release and product lines people can defend

Step 4: prepare the conversation

Fill this in before you raise it with your manager or, if you are the manager, with your team:

  • The area I'm naming: ______

  • The evidence: ______

  • The one change I'm asking for first: ______

If raising this isn't safe where you are, that is itself a control and fairness finding. Time off helps, but research on vacations found the relief fades after people return to the same conditions (Westman & Eden, 1997). The system did not change while they were away, so change the system.

Step 5: if you are a solo builder

There is no team or manager here: you are the system, and choosing the work does not exempt you from its conditions.

  • ☐ Set working hours, days off and a hard stop.

  • ☐ Ship small pieces often so progress stays visible.

  • ☐ Build a peer group; community is one of the six areas for a reason.

How to use it

  • Who: the engineering manager or team lead, ideally with the team in a retro, scoring the system together. Re-run it quarterly.

  • Output: six evidence-backed scores, a named top area and one agreed change at team or org level.

  • Done when: the top area has an owner, a dated change and a check-in, and the next audit shows whether its score moved.

Where this changes

A small team can run Steps 2 and 3 in one retro. A large or regulated organisation needs more: aggregate scores across teams, route org-level levers to the leadership group, and involve HR and occupational health where policy requires it. This audit covers the work system, not individual cases. For the reasoning, read why burnout is a systems problem. To act on the workload row, try the Eisenhower matrix for engineering prioritisation; to have the conversation well, run effective one-on-ones; and if you work alone, read sustainable building when you're the whole team.

Final takeaway

Burnout keeps coming back when the conditions that produce it stay in place. Score the six areas with evidence, fix the top one at team or org level, and audit again next quarter.

Sources

bottom of page