Skip to content
JiraVision
All articles

Team Wellbeing

Preventing burnout: a practical guide for team leads

The five factors behind the burnout score, the four bands it maps to, and the interventions that actually move the number — starting with the disclaimer.

4 min read24 October 2026JiraVision team

A person stepping away from a desk at the end of the working day

Burnout does not arrive as an event. It accumulates as a series of small, individually reasonable decisions — one more task after the scope grew, one more evening because the release slipped, one more meeting because nobody wanted to be the one to cancel it. By the time someone says they are burnt out, the pattern has usually been visible in the work data for weeks.

This guide covers the signals worth watching, the model JiraVision uses to combine them, and what to do when a signal fires.

Start from the disclaimer

The burnout score is a weighted heuristic over five factors. The weights are an illustrative model, not a measured clinical instrument, and the calculator page says so in as many words. Its job is to make a slow trend visible early enough to act on — not to produce a number you can put in a performance review.

If you take one thing from this article, take this: a burnout score is a prompt to have a conversation, never a substitute for one, and never an input to an appraisal.

The five factors

The model scores five inputs, each from 0 to 10, and weights them:

  • Sustained overload, the heaviest weight — committed work regularly exceeds available hours. This is usually visible in your task data before anyone reports feeling it.
  • After-hours bleed, the second heaviest — evenings, weekends or standby becoming the norm rather than the exception.
  • Low autonomy — little say over scope, sequencing, or how the work gets done.
  • Unclear priorities — goals shift mid-sprint and "done" stays negotiable.
  • Recognition gap — effort and care outpace what the team visibly counts.

Two of those five are load problems and three are structural. That split is the useful part: the two most heavily weighted factors are the ones a lead can change next sprint without anyone's permission.

The four bands

The score maps onto four bands, each with its own advice:

  1. Steady — load and control look sustainable. Keep the signals flowing so drift shows up early.
  2. Watch — nothing on fire, but headroom is thin. Protect slack and re-check the trend after the next two cycles.
  3. Strained — patterns are setting in. Rebalance load and make one driver, usually after-hours work, an explicit sprint goal rather than a hope.
  4. At risk — treat this as a now-problem. Cut commitments this sprint, not next quarter.

The model also names the top driver: whichever factor contributed most to the score. That is the field to act on first, because it tells you which lever to pull instead of leaving you with a single alarming number.

What to look at, in order

  • Trend, not snapshot. One high score is a bad week; three in a row is a pattern.
  • Distribution, not average. A healthy team mean hides the person at the floor, so look at the spread.
  • Load concentration. Sort the roster by open work rather than by name and check whether the same two people sit at the top every sprint.
  • Retro follow-through. If the last three retros produced workload action items and none of them completed, the team has already learned that reporting changes nothing.

Interventions that actually move the number

Load builds most of the score, so moving work is the only intervention that reliably moves it. In rough order of cost:

  1. Reassign. Take one committed item off the person at the top of the load list and give it to someone with slack and the matching skill tag.
  2. Cut scope. Drop an item from the sprint out loud, inside the sprint, and say why. Silent de-scoping teaches the team that commitments are fiction.
  3. Move the date. If neither of the above is available, the date moves. Do not accept both the scope and the date without saying so — that is precisely how after-hours bleed starts.
  4. Remove a recurring meeting. The cheapest capacity anyone ever finds. Default to 25 or 50 minutes so there is a gap, and give each meeting an owner who ends it when the agenda is done.
  5. Write down the availability expectation. Which channel is urgent, what response time each one carries, what nobody is expected to answer outside their own hours. Put it where onboarding picks it up.

What not to do

  • Do not use a check-in score as a performance input. The moment the team suspects it, the answers stop being honest and the signal dies.
  • Do not publish individual scores to the group. Aggregate by default and restrict per-person visibility to the person and their lead.
  • Do not answer a bad score with a wellness initiative. A meditation app does not reduce committed load, and offering one reads as a refusal to look at the actual driver.
  • Do not survey without acting. Close the loop visibly — a reassignment, a scope cut, a date moved — or stop asking.

Try the model on your own team

The burnout calculator on the team wellbeing product page runs the same five factors and prints the band, the advice and the top driver. It is a demo of the heuristic, so treat the output as a prompt rather than a verdict, and compare it against the load numbers on your own wellbeing dashboard before you act on either.

Written by the JiraVision team. Corrections and disagreements welcome via the contact page.

Send feedback

Keep reading

AI Scrum Master

The complete guide to AI Scrum Masters

What an AI Scrum Master actually does: where the draft comes from, what the rationale contains, and why nothing reaches your board until a person accepts it.

Read article

AI Scrum Master

How AI changes the agile routine

The ceremonies an AI assistant genuinely improves, the ones it leaves alone, and the five numbers worth measuring in your own workspace instead of trusting ours.

Read article

Read the next one in your inbox

Double opt-in, no tracking pixels, and an unsubscribe link in every message.

Create an account