"Energy: the dimension everyone feels and no one names"

Two teams with the same skill, the same tools, and the same task will not perform the same if one is fresh and one is depleted. The depleted team executes worse — slower, less creative, quicker to fracture under a setback, more likely to do the minimum and miss the thing that needed extra care. This is obvious once stated and routinely ignored in practice, because energy is treated as a morale footnote rather than a performance factor, and depletion is treated as an individual problem rather than a team one. It is neither. Energy is a property of the team, and running on empty is a performance problem with a real, measurable cost.

Energy is one of the eight dimensions of a healthy team, and it is the one most easily dismissed as soft, precisely because it sounds like a feeling. But the feeling has hard consequences: a team's collective capacity to bring effort, engagement, and resilience to its work directly shapes what the team can produce, and when that capacity is depleted, the output suffers regardless of skill. Treating energy as a dimension means taking seriously that a team can be capable and depleted at once, and that the depletion, not the capability, may be what is limiting the results. Understanding this is the difference between pushing a tired team harder and restoring the capacity it actually lacks.

Energy is a team property, not a sum of moods

The first thing to see is that team energy is not simply the average of how individuals feel. A team has a collective energy that is more than the sum of its members' moods — it emerges from how the team works together, from whether the interactions give energy or drain it, from whether the team's dynamics leave people more capable or more depleted. A team of individually fine people can have low collective energy if working together is draining; a team under real pressure can sustain high collective energy if the way it works together is generative rather than depleting. The energy is a property of the system, not just of the parts.

This matters because it means team energy can be managed at the team level, not only by attending to individuals. How the team works together — whether meetings energise or exhaust, whether the collaboration is generative or grinding, whether people leave interactions with more or less than they brought — shapes the collective energy in ways that individual wellbeing efforts do not reach. A company can invest heavily in individual wellbeing and still have depleted teams, because the depletion is coming from how the teams work rather than from any individual's state. Reading and managing energy as a team property, not just as an aggregate of individual moods, is what lets a leader address the collective depletion that individual measures miss.

Depletion is invisible because the team still functions

The dangerous thing about team depletion is that it does not announce itself. A depleted team keeps functioning — it shows up, does the work, hits most of its marks — so from the outside it can look fine, right up until the consequences surface. The depletion shows not as an obvious failure but as a quiet erosion: the creativity that is slightly lower, the resilience that is slightly thinner, the extra care that is no longer taken, the small excellences that quietly stop happening because the team has nothing left over for them. None of these is visible as a discrete failure; they are absences, and absences are hard to see.

This invisibility is why depletion is so consistently underestimated and so often allowed to deepen. A leader looking at a depleted team sees a team that is still delivering and concludes it is fine, missing the erosion underneath because the erosion does not show up in the obvious metrics. The team is delivering, but it is delivering less than it could, and it is spending down a reserve that is not being replenished — which continues to look fine until the reserve is gone and the team suddenly cannot cope with the next demand. By then the depletion is severe and the recovery is expensive, whereas it would have been cheap to address when it was still just a slight erosion. Reading energy honestly means looking for the absences, not waiting for the failure.

Where team depletion comes from

Team depletion comes, most often, from sustained overload without recovery — running at maximum for too long with no genuine renewal. A team can run hard for a while and recover; what depletes it is running hard indefinitely, with each peak demand followed immediately by the next, so the team never gets back to a sustainable baseline. The depletion accumulates because the recovery never happens, and eventually the team is running permanently below the line, drawing on reserves that are not being refilled. This is not about the team being weak; it is about the demand being unrelenting, which no team sustains indefinitely.

The specific culprit is usually the absence of recovery rather than the presence of hard work, which is why the fix is not always less work but genuine recovery between demands. A team that works hard and recovers can sustain high energy; a team that works hard and never recovers depletes, even if the total workload is not higher, because it is the lack of renewal, not the amount of effort, that drains the reserve. This is the distinction that the reflexive response to a tired team — a one-off perk, a pizza, a single fun event — misses entirely: a depleted team does not need a treat, it needs genuine recovery, which is a different and more substantial thing, as we argue at length in the context of burnout that needs genuine recovery rather than a pizza party. The depletion came from missing recovery, and only real recovery reverses it.

Individual burnout and team depletion

Team energy is related to individual burnout but not identical to it, and the relationship runs both ways. A depleted team depletes its individuals, because working in a team that is running on empty is itself draining — the low collective energy pulls down the people in it. And burned-out individuals deplete the team, because their diminished capacity and disengagement affect everyone around them. So the two feed each other, and a team in a bad energy state is often producing individual burnout while individual burnout is deepening the team's depletion, in a loop that accelerates if nothing interrupts it.

But the two are distinct, and the distinction matters for the fix. Individual burnout is addressed at the individual level — through an individual's workload, recovery, and support — while team depletion is addressed at the team level, through how the team works and whether it gets collective recovery. A company that treats team depletion purely as a collection of individual burnout cases will address it person by person and miss the systemic cause in how the team works, so the depletion regenerates faster than the individual fixes resolve it. Conversely, treating individual burnout purely as a team-energy issue misses that some individuals need individual support that team-level measures do not provide. Reading energy as a team dimension does not replace attention to individuals; it adds the collective view that individual-only approaches miss, and the two together address what neither does alone. Where an individual is genuinely struggling, the right response is real support, not a team exercise.

Belonging protects energy

Energy interacts closely with belonging, because belonging is one of the things that makes work energising rather than depleting. A person who feels they belong — who feels part of the team, seen, connected — draws energy from the team rather than spending it, so the same workload is less depleting on a team where people belong than on one where they feel isolated. Belonging is, in a sense, a source of renewal built into how the team works: the connection itself is restorative, which is why teams high in belonging sustain energy under pressure that would deplete a disconnected team.

This is why energy and belonging tend to rise and fall together, and why the isolation that damages belonging also accelerates depletion. A team where people feel alone spends energy on the isolation itself — the extra effort of working without genuine connection, the absence of the renewal that belonging provides — so it depletes faster under the same demand. A team where people belong has a built-in buffer against depletion, because the connection replenishes some of what the work spends. Building belonging is therefore partly an energy investment, and reading the two dimensions together reveals how they reinforce each other: strengthening belonging protects energy, and depleted energy erodes belonging, which is one more instance of the dimensions interlocking rather than standing alone.

Pushing a depleted team makes it worse

The instinctive response to a team that is underperforming is to push it harder — more pressure, higher expectations, a demand for more effort. When the underperformance is coming from depletion, this is exactly wrong, and it makes the problem worse. A depleted team pushed harder does not find more energy it was withholding; it depletes further, because it did not have the energy to give, and the additional demand accelerates the erosion. The push may produce a short-term burst as the team spends its last reserves, followed by a deeper collapse as those reserves run out, leaving the team worse off than before the push.

This is the trap that misdiagnosing depletion as a lack of effort leads to: the leader sees underperformance, reads it as insufficient effort, and applies pressure, which deepens the depletion that was actually causing the underperformance. The team gets more tired, more disengaged, and eventually less capable, in a spiral that the pressure drives rather than relieves. The correct response to a depleted team is the counter-intuitive one: genuine recovery, which restores the capacity the team was lacking, rather than pressure, which spends capacity the team does not have. Distinguishing depletion from a lack of effort is therefore critical, because the two look similar — both show as underperformance — and they require opposite responses. Reading energy honestly is what tells them apart, and getting it wrong turns a recoverable depletion into a collapse.

The false economy of skipping recovery

There is a logic that quietly destroys team energy: the belief that recovery is time not spent working, and therefore time that can be cut when the pressure is on. Under deadline, recovery is the first thing sacrificed — the team pushes through, skips the pause, runs straight from one demand into the next, because stopping feels like a luxury the moment cannot afford. It looks like a saving, and it is a false one, because the recovery that gets skipped was maintaining the capacity the team runs on, and cutting it spends down that capacity faster than the saved time is worth.

The false economy is that skipping recovery buys short-term output at the cost of larger long-term output, because a depleted team produces less than a recovered one, so the hours saved by skipping recovery are lost several times over in the reduced capacity that follows. A team that never stops is not more productive than one that recovers; it is less productive, because it spends most of its time running below capacity, having traded the recovery that would have kept it at full capacity for a little extra time now. The leaders who protect recovery under pressure, counter-intuitive as it feels, get more output from their teams over any period longer than the immediate deadline, because they keep the capacity that unrelenting pressure spends. Recovery is not time away from the work; it is what keeps the work sustainable, and cutting it is borrowing against the team's future output at a punishing rate.

Energy is not the same as busyness

It is easy to mistake busyness for energy, and the mistake hides depletion. A busy team — one in constant motion, always occupied, visibly working hard — can be deeply depleted, because busyness is about how much the team is doing and energy is about the capacity it brings to what it does. A frantically busy team running on empty is not an energetic team; it is a depleting one, spending down its reserves at high speed, and the busyness can mask the depletion because it looks like vigour. Motion is not the same as energy, and a team can have a great deal of the first while running out of the second.

This is why reading energy requires looking past activity to capacity. A team that is busy and depleted will show the signs of depletion — the eroded creativity, the thinning resilience — underneath the busyness, if you look for them rather than reading the motion as health. The busiest teams are often the most at risk of depletion precisely because their busyness disguises it, both from their leaders and from themselves: everyone is working so hard that no one notices the capacity draining away, until it is gone. Genuine energy shows not in how much a team is doing but in the quality it brings — the creativity, the resilience, the surplus for the extra care — which busyness can coexist with or can hollow out. Reading the busyness tells you the team is occupied; reading the energy tells you whether the occupation is sustainable.

Renewal is a team practice, not a perk

The reflexive fix for a tired team — a treat, an outing, a one-off bit of fun — misunderstands what renewal is, because genuine recovery is not an occasional perk but a sustained practice built into how the team works. A single fun event does not restore a chronically depleted team any more than a single meal restores someone who has been undernourished for months; the depletion came from a sustained absence of recovery, and only sustained recovery reverses it. Renewal that works is structural — a rhythm of demand and recovery, a way of working that replenishes rather than only drains, protected time that is genuinely restorative rather than merely nominal.

This reframes what a leader should build. Not the occasional morale event, which is a gesture that leaves the underlying rhythm unchanged, but a sustainable way of working where recovery is built into the pattern rather than sacrificed to it — where peak demands are followed by genuine renewal, where the team's normal operating rhythm replenishes energy rather than only spending it. That is harder than throwing an event and far more effective, because it addresses the cause of depletion — the missing recovery — rather than papering over its symptoms with a treat. A team that has genuine renewal built into how it works sustains its energy; a team that relies on occasional perks to offset relentless demand stays depleted between the perks. Renewal is a practice the team runs, not a reward it occasionally receives, and only the practice actually restores the capacity that depletion takes.

Reading team energy

Energy can be read, and reading it means looking past whether the team is delivering to whether it is bringing genuine energy or running on empty. A team can be delivering and depleted, so delivery alone does not reveal the energy state; what reveals it is whether the team has the creativity, resilience, and extra capacity that fresh energy provides, or whether those have quietly eroded. Reading the absences — the creativity that is lower, the resilience that is thinner, the extra care that is no longer taken — surfaces depletion before it becomes collapse, which is exactly when it is cheapest to address.

And energy can be read again over time, to see whether it recovered or deepened — the before-and-after discipline in what Day 14, 30 and 60 tell you. Because energy interacts with belonging and trust, reading it alongside those dimensions reveals its causes: a depleted team often has an isolation problem draining it faster, or is running in a way that the team's own dynamics make depleting. This is why we read energy as part of the whole picture in why measurement changes the conversation, rather than as a standalone morale check. Reading the delivery tells you the team is still functioning; reading the energy tells you whether it is functioning on capacity or on fumes, which is what predicts whether it can handle what comes next.

A worked example

A team's output has quietly declined — still delivering, but with less of the creativity and polish it used to bring — and the leader reads it as a motivation problem, concluding the team has lost its drive. So the leader tries to re-motivate: new goals, more challenge, higher expectations. The decline continues and accelerates, because a reading finds the real issue is depletion, not motivation: the team has been running at maximum through a long stretch of unrelenting demand with no recovery, and it is running on empty, which is why the creativity and polish — the things that require surplus energy — have eroded. The team is not unmotivated; it is exhausted, and the new challenges are demanding energy it does not have.

Adding challenge made it worse, deepening the depletion that was causing the decline. Reading first would have found the depletion and its cause — sustained overload without recovery — and aimed the work at genuine recovery, restoring the collective capacity the team was lacking, rather than at motivation, which was never the problem. Same team, redirected from re-motivating to genuinely restoring, and the creativity and polish return, not because the team was pushed to care more but because it finally had the energy to bring more. The measurable result is recovered capacity showing up as recovered output — which no amount of new challenge would have produced, because the team was never short of motivation; it was short of energy.

Take energy seriously as a performance factor

Energy is one of the eight dimensions, and it is the one most easily dismissed as soft and most consequential when ignored. A depleted team underperforms a fresh one of equal skill, and the depletion is a team property that comes from sustained overload without recovery — invisible because the team keeps functioning, dangerous because it deepens until the team suddenly cannot cope. Treating it as a morale footnote, or as a collection of individual problems, misses both the performance cost and the systemic, team-level cause.

Take energy seriously as a performance factor: read whether a team is running on capacity or on empty, distinguish depletion from a lack of effort, and respond to depletion with genuine recovery rather than pressure, which only deepens it. Energy interacts with belonging, which protects it, and with the way the team works, which either renews or drains it — so managing energy is partly about building connection and partly about ensuring recovery, not just about reducing workload. Take the dimension seriously, and a team's real capacity becomes visible and restorable — which matters, because a depleted team is one whose skill you are paying for and not receiving, and the depletion, not the skill, is what is holding the results back.