How to Spot Burnout on Your Team

Most managers find out about burnout in an exit conversation. The person across the table says something like “I just need a change,” and only then does the last year snap into focus: the camera that went dark in standups, the vacation days that never got booked, the way “happy to help” quietly became “sure, I guess.”

None of those moments looked like an emergency on their own. That's the whole problem. Burnout on a team rarely announces itself. It accumulates in small behavior changes that each have a perfectly reasonable alternate explanation. Your job isn't to catch one dramatic moment. It's to notice the drift.

One rule before anything else: you are observing signals, not making a determination about anyone's health. You can see that someone's behavior has changed. You cannot see why, and it's not your call to label it. Everything below is about what a manager can legitimately observe and act on: work patterns, engagement, output, nothing more.

Here's where most burnout checklists go wrong: they list behaviors as if they mean the same thing on every person. They don't. Some people have always kept their camera off. Some people have never spoken in large meetings. Some people send terse messages because that's just how they write.

The signal is never the behavior itself. It's the delta from that person's baseline. The engineer who used to argue passionately in design reviews and now says “whatever the team decides” is telling you something. The one who never argued in design reviews is not. This is why spotting burnout is fundamentally a knowing-your-people problem, and why managers with shallow relationships miss it every time.

The three-signal model this site is built on gives you a useful lens for organizing what you see. Burnout tends to show up along three signals: Exhaustion (how depleted work leaves someone), Detachment (how checked-out they've become), and Professional Efficacy (their sense that they're still effective, the protective one). You can't measure these from the outside, but each one leaks into observable behavior in its own way.

Exhaustion is the easiest signal to spot because energy is hard to fake for long. Watch for shifts like these — sustained over weeks, not a single rough sprint:

The workday edges creep. Commits at 11pm from someone who used to log off at six. Slack messages at 6am. Or the opposite: someone who used to be responsive by 9 is now surfacing at 10:30, visibly running on fumes. Both directions matter — one is a person drowning in work, the other is a person who can no longer make themselves start.

Recovery stops working. They take a long weekend and come back exactly as flat as they left. They return from a two-week vacation and by Wednesday they sound like they never went. When rest visibly stops restoring someone, pay attention.

Small tasks take big effort. The expense report sits for three weeks. The two-line email reply takes four days. People running on empty triage ruthlessly, and the first things dropped are the small administrative tasks that used to be automatic.

Sick days cluster. A string of Monday absences, frequent “not feeling great, working from home today” messages, more short-notice appointments than usual. You don't need to know why — and you shouldn't ask why — but the pattern itself is data.

Detachment is quieter and more dangerous, because a detached person can look low-maintenance. They stop pushing back, stop raising problems, stop asking for things. Overloaded managers often read this as an improvement. It isn't.

Opinions disappear. The person who used to fight for the customer, challenge estimates, or die on hills about code quality now agrees with everything. “Sounds good.” “Whatever works.” Agreeableness from someone who was never agreeable is a loud signal.

They shrink to the job description. Mentoring the junior hire, improving the onboarding doc, volunteering for the gnarly cross-team problem: the discretionary contributions go first. What's left is exactly what's required and nothing more.

The tone about the work turns flat or sour. Projects become “whatever they want this quarter.” Customers become “those people.” A dry sense of humor is fine; a new, persistent cynicism from someone who used to care is not.

Social withdrawal. Skipping optional meetings, going quiet in channels they used to be active in, camera permanently off after years of it being on, eating lunch alone after years of not. Again: only meaningful as a change from baseline.

Your most reliable people are the easiest to lose to burnout, precisely because their output shields them from scrutiny. Strong Professional Efficacy — the protective signal — can keep someone shipping excellent work long after exhaustion and detachment have set in. From your side of the dashboard, everything looks green.

With these people, output metrics are nearly useless. Watch the texture instead: the work is still good but the spark is gone, they've stopped proposing ideas and only execute what's assigned, they deflect recognition (“it's fine, it's just the job”), and every conversation about the future gets shorter. We wrote about this profile in depth in high-functioning burnout, and it's worth reading if you have someone on your team who is exhausted but still somehow crushing it, because that arrangement always has an expiration date, and it usually expires as a resignation letter.

Name the behavior, not a condition. Say “I've noticed you've been quieter in reviews the last month, and you mentioned working late three times this week — how are you actually doing?” Do not say “I think you're burned out.” The first is an observation that opens a door. The second is a verdict that closes one, and it's a verdict you're not qualified to render.

Have the conversation in private, with time. Your regular 1-on-1 is the natural venue; we've written a full guide on using 1-on-1s to catch burnout early. Don't bolt it onto the end of a status update. If the answer is “I'm fine” and the signals persist, ask again in two weeks. People rarely open up on the first pass.

Act on the workload, not just the feelings. Sympathy without a calendar change is noise. If the conversation surfaces real strain, something visible should move: a project handed off, a deadline renegotiated, an on-call rotation adjusted. The structural side of this is covered in our playbook on preventing team burnout, because spotting it late is always more expensive than designing it out.

Know where your role ends. If someone shares that they're struggling in ways that go beyond workload — if what they're describing sounds bigger than work, or nothing at work seems to help — the supportive move is to encourage them to talk with their doctor, a therapist, or your company's EAP if you have one. You can adjust their workload; you can't be their clinician, and pretending otherwise serves no one.

Finally, check your own gauges. Managers who are running on empty themselves have a much harder time noticing anyone else's drift; that's half the reason we wrote our guide to burnout for managers. A quick self-check takes about 4 minutes, and knowing your own Exhaustion, Detachment, and Professional Efficacy signals makes you sharper at reading the room.