How to Support a Colleague Who Is Burning Out (Without Overstepping)

WORKPLACE WELL-BEING • July 19, 2026

Clinically reviewed July 2026 by Annie Wright, LMFT · Licensed Marriage & Family Therapist (#95719)

The Email That Sent at 11:47pm

Shira, 44, is a VP of Operations at a mid-size healthtech company, and I’ve been thinking about her lately, not because she’s a client of mine, but because she is a composite of dozens of women I’ve worked with who occupy her exact role in other people’s lives. Not the burned-out one. The one standing next to the burned-out one, holding a mug of lukewarm coffee outside someone’s office door, trying to figure out if today is the day she finally says something.

The email had come in at 11:47pm the night before. Subject line: “re: Q3 deck, minor updates.” The body was six paragraphs long, fully punctuated, with three separate apologies for the lateness of the reply. Shira had read it twice before she understood what was actually bothering her. It wasn’t the content. The deck updates were fine, even good. It was the tone. Her colleague, Zuzana, a senior engineer she’d worked alongside for four years, had written the email the way a person writes when they are trying very hard to sound like themselves and not quite landing it.

Shira stood outside Zuzana’s office the next morning with her coffee going cold, and she did not know what she was allowed to say. “You seem off” felt presumptuous. “Are you okay” felt like it would get a reflexive “I’m fine!” and end the conversation before it started. She’d read enough to know that burnout was real and common and dangerous to ignore. She had not read anything that told her what to actually do standing in a doorway at 8:52am, holding a cup of coffee, watching someone she respected disappear a little more each week.

This is the gap I want to close in this piece. Not the general awareness that burnout exists, because most driven, ambitious people already have that. The specific, practical, relationally intelligent gap between noticing and acting. Between caring and overstepping. Between being a decent colleague and accidentally making things worse.

What Is High-Functioning Burnout?

In my work with clients, the burnout that worries me most is never the version that shows up as a breakdown. It’s the version that shows up as a slightly-too-perfect Q3 deck sent at midnight with three apologies attached.

Here’s what I keep coming back to when I read Maslach’s original research. She specifically named burnout as a response to the situation, not a deficiency in the person experiencing it. That single reframe matters enormously for how you approach a colleague who’s struggling, because it changes the question from “what’s wrong with her” to “what’s she being asked to carry, and for how long.”

High-functioning burnout is the version of this that hides in plain sight. It’s the colleague whose output actually looks fine, sometimes better than fine, because the exhaustion and cynicism are being masked by sheer effort. She’s still hitting deadlines. She’s still showing up to every meeting. She’s still, on paper, one of your most reliable people. Underneath all of it, though, she’s running on fumes that are running out.

Why Can’t Your Colleague Just Tell You?

I recently found myself returning to Pauline Rose Clance, PhD, and Suzanne Imes, PhD, and the 1978 paper where they first named the Impostor Phenomenon, because I think it explains something crucial about why burned-out, driven colleagues so rarely say the words “I’m burning out” out loud, even to people who could help.

What Clance and Imes documented in that original sample of accomplished women in 1978 is exactly the pattern I see, decades later, in driven professionals across every industry I’ve worked with. Here’s the clinical mechanism, translated. Layer one: a person with impostor patterns attributes her success to external factors like luck or overwork rather than to her own competence. Layer two: think of it like a person convinced her whole career is a Jenga tower built on someone else’s mistake, one tile away from collapse. Layer three: which means, in practice, that admitting exhaustion feels equivalent to admitting the tower was never sound in the first place. So she doesn’t admit it. She sends the six-paragraph email at midnight instead, with three apologies attached, because the apologies are the closest she can get to the truth without saying it.

This is why “are you okay” so often gets a reflexive “I’m fine!” in response. It’s not dishonesty. It’s self-protection, operating exactly as it was built to.

There’s a second layer underneath the impostor pattern that I think is worth naming plainly, because it shows up constantly in my work with clients who are quietly burning out at work: many of them have built entire identities around being the reliable one, the capable one, the person others come to when something breaks. Asking for help doesn’t just risk exposure. It risks losing the identity that made them feel valuable in the first place. If competence is the whole foundation of how you know you’re worth something at work, admitting you’re struggling can feel less like a minor disclosure and more like an existential threat. This is part of why a colleague who’s drowning will often, paradoxically, take on more, not less, in the weeks before things fully unravel. She’s trying to prove to herself that the foundation is still solid, right up until it isn’t.

How Does This Show Up Between Driven Colleagues?

It’s a Tuesday in April, 4:40pm, and Zuzana, 39, a senior engineer, is sitting in a glass-walled conference room with her laptop open to a spreadsheet she’s already checked four times. She’s got a half-eaten protein bar next to her keyboard and a Nalgene bottle with a faded conference sticker on it from three years ago. She hasn’t refilled it since lunch.

“I just need to get through the migration,” she tells Shira, who’s stopped by under the pretense of asking about a Jira ticket. “Once the migration’s done, it’ll calm down. It’s always like this before a migration.”

Shira has heard some version of this sentence at least four times in the past year. There was the migration. Then the security audit. Then the reorg. Then the client escalation. Each time, the promised calm never quite arrives before the next fire starts.

“You look tired,” Shira says, carefully, watching Zuzana’s face for the flinch she’s learned to expect.

“I’m always tired,” Zuzana says, and laughs, but it’s a short laugh, more exhale than sound. “That’s just what having this job is like.”

Sitting across from Zuzana in that conference room, Shira felt the particular ache of recognizing someone else’s exhaustion because she’d worn it herself two years earlier. Not pity. Something closer to dread, watching a pattern repeat itself in someone she respected.

What I’ve come to think of as the migration excuse is something I hear constantly from driven professionals who are burning out. There’s always a next milestone that will supposedly make things calm down, and the milestone keeps moving, and the person keeps believing the next one is the real finish line. It rarely is. The exhaustion isn’t caused by the migration. The migration is just the current occupant of a role that chronic overwork fills no matter what project happens to be running.

Shira didn’t push further that afternoon. She said, “Okay. I’m around if you want to talk about something that isn’t the migration,” and left it there. Zuzana nodded, already looking back at the spreadsheet. Neither of them said anything else about it that day.

What made that moment harder than it needed to be, in hindsight, was that Shira and Zuzana had never actually named the terms of their working relationship outside of deliverables. They knew each other’s project timelines intimately and almost nothing about each other’s actual capacity on a given week. This is common among driven colleagues who respect each other’s competence deeply and rarely, if ever, talk about their limits. Competence becomes the entire language of the relationship, and limits become a foreign dialect neither of them has practiced speaking.

Why Do Well-Meaning Colleagues Get It Wrong?

In my work with clients who’ve been on the receiving end of a well-intentioned coworker’s concern, I hear the same complaints often enough that I’ve started keeping a mental list of what not to say, not because the people saying these things are unkind, but because good intentions and good delivery are two different skills.

“Just take a break” tops the list. It’s not wrong, exactly. It’s incomplete in a way that can land as dismissive, because it implies the burnout is a scheduling problem rather than a structural one. “You seem really stressed” often gets received as a critique of competence rather than an expression of care, especially by someone already primed to hear any observation about her state as evidence she’s failing. Unsolicited diagnosis is its own category entirely. “This sounds like burnout” or, worse, “this sounds like depression,” spoken by a coworker rather than a licensed clinician, tends to produce defensiveness rather than relief, no matter how accurate the observation might be.

Brené Brown’s line about clarity has stayed with me because it reframes what a lot of well-meaning colleagues get backwards. They think vagueness is gentler. “You seem a little off lately, just wanted to check in” feels softer than “I’ve noticed you’re working past midnight several nights a week and I’m worried about you.” But the vague version leaves the burned-out colleague to do all the interpretive work herself, at a moment when she has the least capacity to do it. The specific, clear version, delivered with warmth, actually asks less of her. It hands her something concrete to either confirm or correct, rather than a fog to decode.

The other mistake I see constantly is escalation without consent. Going straight to a manager, or a colleague’s spouse, or HR, without first talking to the person herself, however well-intentioned, tends to be experienced as a betrayal rather than a rescue. There are real exceptions to this, which the FAQ below addresses directly. But the default should be talking to your colleague first, not around her.

Research on workplace mental health disclosure backs up why this sequencing matters so much. A 2025 study on workplace outcomes after mental health disclosure found that positive disclosure experiences, ones where the listener expressed concern, listened attentively, and demonstrated empathy, were associated with higher work ability, higher intent to stay, and lower perceived stigma (Volkov et al., 2025, Journal of Occupational Rehabilitation). Negative experiences, judgmental or condescending remarks among them, predicted the reverse. The tone of the very first conversation tends to set the trajectory for everything that follows, including whether your colleague ever brings it up again.

Separate research on the psychology of disclosure decisions found that most employees begin from a default position of nondisclosure rooted in fear of stigma, and need an active reason to move away from that default (Toth and Dewa, Journal of Occupational Rehabilitation). Your calm, specific, non-judgmental check-in can be that reason. A vague, anxious, or alarmed one usually isn’t. This is part of why the overfunctioning pattern I see so often in clients working through perfectionism and achievement-as-worth tends to intersect so heavily with workplace burnout. The same fear of being seen as insufficient that drives the overwork also governs whether someone will ever admit the overwork has stopped working.

Both/And: Caring About Her and Protecting Your Own Capacity

Here’s the both/and that I think gets missed most often in this conversation. You can genuinely care about a burned-out colleague, and you can protect your own time and emotional bandwidth. These aren’t competing values. They’re both required for the support to be sustainable.

Shira learned this the hard way, six months after the conference room conversation with Zuzana. She’d started staying late herself, picking up pieces of Zuzana’s workload without being asked, telling herself it was temporary, telling herself it was what a good colleague would do. It was not temporary. It became her new normal for the better part of a quarter, and by the time she noticed, she was running the same script Zuzana had been running the year before. Longer hours. A Nalgene bottle she also forgot to refill. A version of the migration excuse, except her version was “once Zuzana’s better, this will calm down.”

Of course that felt unsustainable. Taking on a colleague’s workload as an unspoken act of care, without naming it, without a time limit, without checking in on whether it was even helping, isn’t generosity. It’s a slower version of the same depletion, just relocated to a different desk.

What actually helped Shira was naming a boundary out loud, to Zuzana directly. “I want to support you through this, and I also need to be honest that I can’t keep absorbing pieces of your workload indefinitely without it affecting me too. Can we talk to our manager together about redistributing some of this?” That single sentence did more for both of them than three months of quiet overfunctioning had done. It turned an invisible arrangement into a visible, shared problem, which is a very different thing to carry.

You’re not required to become someone’s unpaid safety net in order to be a good colleague. You’re allowed to say, “I care about you, and I also have limits,” in the same sentence.

The Systemic Lens: Why Do Workplaces Keep Producing This?

It would be easier, and it would be wrong, to frame this whole piece as a personal-resilience issue. As though the fix for high-functioning burnout is simply a better boundary script, a better colleague, a better morning routine. The proverbial ground beneath these individual struggles is a workplace culture that consistently rewards overwork and treats sustainable pace as a personal failing rather than an organizational design choice.

Jeffrey Pfeffer, PhD, the Stanford Graduate School of Business professor who has spent his career studying organizational behavior, has argued for years that workplace practices themselves, not just individual coping skills, are a measurable public health issue. His research reframes burnout less as an individual vulnerability and more as a predictable output of specific management decisions: understaffing, unclear priorities, always-on expectations, and reward systems that quietly punish anyone who takes their limits seriously.

The research on coworker support bears this out from a different angle. A study published in Canadian Family Physician found that higher levels of colleague-based social support were associated with lower levels of loneliness among residents, which in turn predicted lower personal and work-related burnout (Rogers, Polonijo, and Carpiano, Canadian Family Physician). Separate research published in the International Journal of Environmental Research and Public Health found that coworker support reduces emotional exhaustion by increasing what researchers call psychological availability, essentially, the sense of having enough internal resources left to engage (Xiu et al., International Journal of Environmental Research and Public Health). Colleague support isn’t a soft nicety sitting on top of the real work of burnout prevention. It’s one of the actual load-bearing structures.

Which means the sensation-level version of this, the version that shows up in your actual Tuesday, is that when you check in on a struggling colleague, you’re not just performing kindness. You’re one of the only structural buffers she has against a system that will not check in on her for you. Her manager might be stretched too thin to notice. Her org’s wellness benefit might be a once-a-year webinar nobody attends. You, standing in the doorway with cold coffee, might be the actual intervention.

None of this erases her employer’s responsibility to build a workplace that doesn’t manufacture this pattern in the first place. It does mean that your small act of noticing carries more structural weight than it might feel like it does in the moment.

Research on detection and disclosure of workplace mental health challenges points to the same conclusion from the organizational side. A review published in BMC Public Health found that policies that build psychological safety, confidentiality, and inclusivity meaningfully increase the odds that employees will seek help before a crisis point, while cultures of silence delay disclosure until the situation has already become severe (Poddar and Chhajer, BMC Public Health). A colleague who checks in early is, functionally, a piece of that psychological safety infrastructure, whether or not her employer has built any formal version of it.

What Should You Actually Say and Do?

In my work with clients moving through this exact situation, from the other side, as the person trying to figure out how to help, a few concrete moves tend to work better than general concern.

Name what you’ve observed specifically, without diagnosing it. “I’ve noticed you’ve been sending emails really late the past few weeks, and I wanted to check in” lands differently than “you seem stressed.” Specificity signals attention rather than judgment.

Ask an open question and then actually wait. “How are you doing, really?” followed by silence, rather than immediately filling the space, gives your colleague room to answer honestly instead of reflexively.

Offer, don’t prescribe. The warm referral technique I teach clients works like this: instead of “you should really talk to someone,” try “I’ve found it helpful to talk to a therapist when work gets like this, if that’s ever useful for you, I’m happy to share who I see.” This shares a resource without implying she’s broken or that you’ve diagnosed her.

Ask what kind of support she actually wants. “Do you want me to just listen, or are you looking for ideas, or would it help if I took something off your plate?” removes the guesswork and respects her autonomy over her own situation. Edward Deci, PhD, and Richard Ryan, PhD, the psychologists behind self-determination theory, have spent decades documenting that autonomy, the sense of having genuine choice in one’s own actions, is one of three basic psychological needs required for well-being alongside competence and relatedness (Deci & Ryan, 2000, American Psychologist). A burned-out colleague has often lost her sense of choice everywhere else in her work life. Asking what kind of help she actually wants restores a small piece of it, instead of you deciding on her behalf.

Set a boundary on your own involvement, out loud, early. “I want to be here for you, and I also need you to know I can’t be your only support system” is a sentence that protects the relationship rather than damaging it, even though it can feel counterintuitive to say.

Know when it’s above your role. If your colleague mentions thoughts of self-harm, expresses hopelessness, or is showing signs that go beyond exhaustion into crisis, your job shifts from supportive peer to bridge. Encourage her, directly and warmly, to contact a mental health professional or, if there’s any immediate safety concern, a crisis line. You are not equipped to be her therapist, and trying to be is its own kind of overstepping.

A script can carry you through the first few sentences, but it won’t carry the whole conversation, and that’s fine. Most of what actually helps happens in the follow-through, not the opening line. Checking back in a week later. Noticing out loud if something has shifted, for better or worse. Not treating the first conversation as a box checked and a topic closed. Burnout doesn’t resolve on the timeline of a single conversation, however well delivered, and a colleague who brings it up once and then never mentions it again can land as performative rather than genuine, even when the intention behind it was real.

There’s also a version of this that requires almost no script at all. Sometimes the most useful thing you can offer a burned-out colleague isn’t a conversation about burnout. It’s an ordinary, low-stakes gesture that doesn’t require her to talk about anything at all. Covering a meeting so she can leave twenty minutes early. Bringing back a coffee without being asked. Sitting with her at lunch instead of at your desk, on a day when you suspect she needs company more than she needs advice. These gestures don’t solve anything structural. They remind a person who feels invisible in her exhaustion that someone is still paying attention, which, some weeks, is the most sustaining thing available.

The Doorway, Revisited

Shira eventually did say something to Zuzana, a version of it, on a different Tuesday than the one in the conference room. Not a speech. Just, “I’ve noticed you’ve been here really late a lot, and I wanted you to know I’ve noticed, and I’m not going anywhere if you ever want to talk about it.” Zuzana didn’t say much back that day. She said, “Thanks,” and went back to her screen.

Three weeks later, Zuzana knocked on Shira’s office door instead. She didn’t have a spreadsheet with her. She just said, “Can I talk to you for a minute,” and sat down before Shira answered.

That’s usually how it goes. Not a dramatic breakthrough. A door, held open long enough, eventually gets walked through, on someone else’s timeline, not yours.

If you recognize yourself in Shira’s side of this story more than Zuzana’s, the overfunctioning, the quiet absorption of other people’s workload, the discomfort with naming your own limits, that pattern is worth its own closer look. It often traces back further than the current job, into earlier family roles that taught you your worth was tied to how much you could carry. And if you recognize yourself in Zuzana’s side, the six-paragraph emails, the migration that never quite ends, the reflexive “I’m fine,” that pattern deserves its own attention too, ideally before a colleague has to stand in your doorway wondering what to say.

Warmly, Annie.

Medical Disclaimer