I’m fine. (Narrator: They were not fine.)
A manager’s guide to addressing burnout: what to say after “I’m fine,” how to start to fix the system behind it, and when to bring in support that goes beyond you.

A survey published in October 2026 (commissioned by Hubstaff on 1,068 US workers) found that 55% of people have told a manager they were fine when they were actually overwhelmed.
Amongst those burned-out employees whose manager knew they were overwhelmed, 64% said nothing changed.
Only 19% had a manager who both knew they were overwhelmed and did something to help.
For managers, this is why our continued focus is on what we do with information about employee well-being and how we can channel this into positive change, even if what we’re hearing is “I’m fine”.
☀️ Things looked sunny…but they weren’t
In one of my first manager assignments, my team’s technical lead was carrying the technical knowledge required to support more than a dozen customers we worked with at any given time.
This lead was supported by a smart team and had good friends around them. They were also one of those people who believed (part generation, part personality) that a leader takes on whatever comes their way and does the very best they can, whether or not that makes sense priority-wise.
It didn’t help that they were genuinely curious about almost everything. They wanted to help everyone. Of course they did.
By the time I arrived, they were still the same outwardly sunny person they’d purportedly “always been.”
But they were also visibly exhausted.
The lead agonized over taking even a few days off for a family milestone they never wanted to miss. I told them those moments were essential and that the team would be very ok covering.
They took a few short days (after I pleaded with them), but before and after, they kept mentioning that they couldn’t get work out of their head.
Sometimes that was the good kind of tinkering, working a problem until it clicked and the anxiety dissipated.
Sometimes it meant they weren’t sleeping and the worry had nowhere to go.
After someone in our broader organization had an unexpected health event, I talked to the whole team about it.
I told them the very last place I wanted to meet their families for the first time was at the hospital, because of a health event related to stress from work.
That conversation did seem to help, at least for a while.
We also made some changes to the actual work the lead was doing to try to reduce overwhelm. More on that in a minute, because it’s the part that (in my opinion) made a difference systemically.
But even as some positive changes happened, when the lead decided to apply for a prestigious technical promotion, I saw his confidence gradually (and then suddenly) collapse as the deadline for the application approached.
At the time, I remember feeling so confused as this collapse occurred, because the signals didn’t match:
The management chain believed in the lead and supported the application.
I met with the lead weekly to identify ways to protect time for the application.
Nobody indicated doubt in the lead’s technical ability.
What I kept hearing, over and over, was some version of: “I’m fine, thank you, I’m figuring it out. I’m tired but I’m pushing through it.”
The lead’s application didn’t even make it to launch.
Then they retired before the next application cycle, so we’ll never know if they would have made it. But I like to think they would have.
🧯 “I’m fine” is a trust signal
Here’s the insight I wish I’d had as a new manager:
“I’m fine” is a trust signal.
If someone has been transparent with how they felt before and then found out (or perceived) that nothing changed as a result, “I’m fine” is the efficient answer.
Because why spend emotional energy on a conversation that won’t lead to change…again?
Layer on a “just push through it” culture (and plenty of technical, hands-on workplaces still have one, whether anyone says it out loud or not) and “I’m fine” becomes the safe answer too.
Admitting you’re not fine can also feel like admitting you’re not good at your job.
💡So the important question is:
How do I make it worth it for a team member to share when they feel overwhelmed / burned out, so that I can help?
💬 What to say after hearing “I’m fine”
In my experience, it depends on the depth of the relationship.
If it’s a shallow connection (my barista at the coffee shop close to work, for example, which is a shallow connection, but who knows, might become important someday), I’ll say something like:
“I’m glad to hear that, I hope it stays that way!” and move on with my vanilla latte.
Not every “I’m fine” is yours to dig into.
If it’s someone on my team, or someone I’m building trust with, I’ll say something like:
“You’re the person best positioned to know how you’re feeling and what kind of support you might need day to day, so I trust you to keep me posted if that changes and I can help.”
It respects their autonomy and leaves the door open (even right then).
⚠️ But here’s something to be mindful about with that approach.
Leaving it at what I said above hands the responsibility back to the person who just told you they’re fine. My technical lead would have heard it and kept saying “I’m fine” for months.
So when I’m picking up on signals (they mentioned they’re not sleeping, they’re online late, small things are landing harder than they used to), I name what I’ve heard:
“Since you mentioned you weren’t sleeping, I want you to know that worries me.
As someone who cares about you, I’m hopeful that if there’s something I can do as your manager to help, we can talk about it.”
Two small tweaks:
I’m using their words, so it doesn’t feel like surveillance.
And it separates the person who cares about them from the manager (me) who can actually change something.
Which brings us to the part that we know (from survey data, anyway) that is toughest to follow through on.
🔧 Getting started with systemic change
With my technical lead, the change that helped most (in starting to address causes of overwhelm, systemically) was actually a scheduling deadline.
Our team built a weekly prioritization proposal with input from our customers, and it went up through our management chain for approval.
There had been a “no later than” date for requesting changes to the next week’s plan. It had just never been enforced, so it had eroded into chaos. Priorities changed constantly, and the team couldn’t tell which ones were real.
So I started holding firm on the “no later than” date (with support from my own leadership, which mattered a lot).
The schedule stabilized. Work moved through more predictably, which reinforced the practice.
At the same time, a couple of high-potential engineers on the team started training as co-leads so the lead could build trust with them and hand off pieces of the broader knowledge workload bit by bit.
💡If you take one thing from this story: look for the rule that eroded over time.
The deadline nobody enforces.
The intake process everyone routes around.
The “temporary” coverage plan that became permanent.
Burnout is often a process problem dressed up as a personal one.
And once you’ve made a change:
Make it visible. Tell the person what you changed and why. If you can’t change something, say that too (and why). “I can’t move this deadline, but I can take this other thing off your plate” is still a real answer.
Make it timely. My changes took things in a positive direction, but they were also slower than the rate my lead was burning out.
Adjusting someone’s workload bit by bit takes months, and someone whose identity is built on carrying everything can keep saying “I’m fine” the whole way…until things go wrong suddenly. I learned this the hard way so you don’t have to.
Check how it’s going. A week or two later, ask directly whether it actually made a difference.
That follow-up is what earns you the next transparent answer.
📜 The fine print: what isn’t your job
Looking back years later, I think some of what my technical lead was working through (confidence, emotional capacity, burnout that had built up over a long time) probably needed support from someone outside work, like a therapist or our employee assistance program.
You as a manager can’t fix everything and you aren’t supposed to, but knowing when to connect someone to support bigger than you is part of the job.
I wrote about that in What to Say When Someone is Falling Apart, including the resources worth knowing before you need them.
And if you’re the manager everyone brings their “not fine” to, THIS is my cautionary tale about doing that for 18 months with no boundaries.
I was the Emotionally Available Manager for 18 Months, Do Not Recommend
My Substack bio says “I managed a team, a team of teams, and 18 months of terrible sleep.”
🪞 Your own version of “I’m fine”
Managers say it too. And right now there’s a new reason we might be quietly overloaded: a Founder Reports survey published November 3rd found that 40.7% of managers spend three or more hours a week checking and fixing AI-generated work, compared to 25% of individual contributors. They call it “botsitting.” Weird, right? Whatever the sources of overload, they aren’t all showing up in your capacity plan I bet.
When managers (my own, or stakeholders, or mentors) have asked me how I’m doing, I’m usually trying to gauge their emotional intelligence (EQ) before I answer.
With lower-EQ leaders (the ones who glorify the hustle, or think “toughen up” is a helpful response), I’m more guarded.
I might deploy an “I’m fine” in an absolute worst case, gotta-go scenario. But I still look for a way for them to help, usually by framing it around something they care about: a key result that’s lagging, or a stakeholder we need help connecting with. That way I’m not putting up a wall of stoicism, which never feels honest to me.
With higher-EQ leaders, I’m more transparent about what I and the team are running into: fear, denial (more on that in Fear and Denial in Las Vegas), burnout, lack of collaboration, and how those are getting in the way of the work.
Fear and Denial in Las Vegas
Here’s a hunch I’ve been following for a while now: almost every difficult behavior you encounter in a leadership context has one of two root causes. Fear or denial.
Your team is reading you before they respond too, so remember:
How do I make it worth it for a team member to share when they feel overwhelmed / burned out, so that I can help?
I’d love to hear from you: what’s one change you made after someone on your team was transparent with you about feeling burned out, and did it actually help?
Leave a comment, find me on Notes, or send me a message!
See you next Tuesday,





Discussion about this post