By the time someone says they're burnt out, they've usually been burnt out for a while. The resignation that follows often comes weeks or months later, but the trajectory was visible much earlier, if there was something to see it in.
Burnout isn't just a workload problem. It's a signal problem. Teams under sustained pressure without acknowledgement, progress, or autonomy will show it in their weekly sentiment before they show it in their behaviour. Here's what to watch for.
Sentiment declines gradually, then holds low
The most common burnout pattern isn't a sudden drop. It's a slow decline over six to ten weeks, followed by a plateau at a low level. The team stops trending down but doesn't recover. When sentiment sits in the same below-average range week after week, it's not a blip, it's a new baseline. That's the signal worth acting on.
A single hard week doesn't produce this pattern. A restructure, a relentless quarter, or sustained pressure without visible progress does. The difference between a team that's having a tough stretch and a team that's burning out is time. The tough stretch resolves. The burnout trajectory keeps going.
Response rates drop before scores do
People who are burning out often disengage from the feedback process before their scores reflect it. They stop filling in the check-in. They complete it but leave free-text blank. They answer in shorter, more neutral terms.
A falling response rate is easy to dismiss as busyness. Sometimes it is. But a sustained drop in participation, particularly if it follows a period of negative sentiment, is a meaningful signal. The people most likely to stop engaging with a feedback channel are often the ones most in need of support.
Free-text shifts from specific to vague
When people are engaged, their open comments tend to be specific: a process that's frustrating, a project that's going well, a decision they don't understand. When they're burning out, the comments get shorter and more generic. "Busy" replaces "the workload from the re-platform is unsustainable." "Fine" appears more often. The signal becomes harder to act on because the specificity disappears.
This isn't about reading too much into any individual comment. It's about noticing a shift in the texture of responses over several weeks. If your team used to give you useful, specific feedback and has shifted to brief and neutral, something has changed.
What to do when you see the pattern
The mistake most leaders make is waiting for certainty before acting. By the time the pattern is unambiguous, it's usually past the point where small interventions work. The better move is to respond to early signals before you're sure - close the loop in the weekly summary, acknowledge that things have been hard, ask what would make the biggest difference.
You don't need to have all the answers. You need to show the team that the signal was received. That changes the dynamic enough to matter.
Relay gives you a weekly read on team sentiment so you can see these patterns as they develop. If you're currently relying on annual surveys or 1:1s to catch burnout, you're probably catching it too late.