Is your team burning out? A two-minute check

Most teams do not collapse loudly. They slow down. Replies get shorter, the camera stays off, the person who used to push back in reviews goes quiet, and a project that should have shipped in March is still open in June. By the time someone resigns, the warning signs have usually been visible for months. A good team burnout assessment is really just a way of reading those signs early, before they harden into attrition, sick leave, and rework.

The instinct is to treat all of this as a motivation problem or a personality problem. It is usually neither. The World Health Organization classifies burnout in its ICD-11 as an occupational phenomenon: something that arises from chronic workplace stress that has not been successfully managed. That framing matters because it moves the question from "who is struggling" to "what about the work is producing this", which is the only version of the question an organisation can actually act on.

WHO is precise about this. In the ICD-11, burnout is described through three dimensions: feelings of energy depletion or exhaustion; increased mental distance from one's job, or feelings of negativism or cynicism related to the job; and a reduced sense of professional efficacy. WHO is also clear that the term refers specifically to phenomena in the occupational context and should not be applied to other areas of life.

Two things follow. First, burnout is not the same as being tired after a hard week, and it is not the same as clinical depression or anxiety, though they can overlap and feed each other. Second, all three dimensions matter. Someone can be exhausted but still engaged, or cynical but not yet exhausted. When you see exhaustion, mental distance, and a creeping sense of "none of this makes a difference" together, that pattern is what the definition is pointing at.

At an individual level this is hard to self-diagnose, because the cynicism dimension quietly rewrites how people interpret their own situation. At a team level the same three dimensions show up as observable behaviour, which is what makes a structured check worthwhile.

Exhaustion at team level looks like chronic overrun: people consistently working past hours, leave that is accrued but never taken, and a visible drop in the quality of work late in every cycle. In an Indian context this is often masked by shift patterns and long commutes, so the fatigue gets attributed to logistics rather than load.

Mental distance, or cynicism, is the one managers miss most. It shows up as disengagement that looks like compliance: tasks get done to the letter and no further, people stop volunteering ideas, retros go silent, and "that is not my problem" becomes a reasonable-sounding default. Reduced efficacy is the third: capable people start describing their own work as pointless, stop believing effort changes outcomes, and lower their own standards because raising them feels futile.

No single signal is proof. A quiet retro might just be a quiet week. The point of looking across all three dimensions, and across a team rather than one person, is to separate a bad fortnight from a structural pattern that will keep producing the same result until something about the work changes.

The case for taking burnout seriously does not rest on sentiment. WHO and the ILO estimate that depression and anxiety cost the global economy roughly 12 billion working days and around US$1 trillion in lost productivity each year, largely through reduced performance and absence. A separate WHO-led study published in The Lancet Psychiatry put the return on scaling up treatment for these conditions at roughly US$4 for every US$1 invested, mostly through restored productivity and better health. These are macro figures and they are illustrative, not a forecast for any single organisation, but they establish the order of magnitude.

The cost that lands closest to home is replacement. Analyses from SHRM and Gallup commonly put the cost of replacing an employee at roughly one-half to two times their annual salary once you count notice-period drag, hiring, onboarding, and the months before a new joiner is fully productive. For a mid-level role that is a large, recurring, and largely avoidable line. Burnout is one of the more preventable drivers of that turnover.

There is also a statutory and trust dimension that is specific to India. Anything you measure about employee wellbeing involves personal data, and under the Digital Personal Data Protection Act, 2023, that brings obligations around consent, purpose limitation, and data principal rights. The practical implication is simple: collect the minimum, be explicit about why, keep individual responses anonymised at the team level, and never let a wellbeing signal feed a performance file.

A team burnout assessment earns its keep only if it points at causes you can change. The well-documented drivers are structural: sustained workload with no recovery, low control over how work gets done, unfair or unpredictable processes, weak reward and recognition, breakdowns in the team community, and unclear or conflicting expectations. None of these are fixed by telling people to be more resilient.

This is also where psychological safety belongs. Amy Edmondson's research, and Google's Project Aristotle study of its own teams, both point to psychological safety, the shared sense that it is safe to speak up, admit a mistake, or flag that you are underwater, as a defining feature of teams that perform and sustain. A team that cannot say "this pace is not workable" will keep absorbing pressure silently until it shows up as exhaustion and exits. The check is one structured, lower-stakes way to surface that signal before it gets that far.

The value of a two-minute check is not the score. It is that it forces a team to look at exhaustion, cynicism, and efficacy together, on purpose, instead of explaining each one away in isolation. The score tells you where to point your attention. What you do next, ideally one concrete change to the work followed by a confidential way for people to get support if they need it, is what actually moves the picture.

We built the assessment above, and the wellbeing support behind it at Aha, around exactly that loop: measure honestly, change something structural, then check again. But the principle stands on its own. Read the signals early, treat burnout as something the organisation produces and can therefore reduce, keep the data anonymised and consented, and act on the cause rather than the person. The teams that do this do not eliminate hard weeks. They just stop mistaking a structural problem for a personal one until it is too late to fix cheaply.