An otherwise reliable employee has become withdrawn, is missing small deadlines they never used to miss, and seems exhausted in every meeting. When asked how they're doing, they say "fine, just busy" - the kind of answer that means the opposite.
MBA Lab is independent and is not affiliated with, endorsed by, or an official representative of Virginia Commonwealth University. This scenario is an original MBA Lab analysis, not an official VCU case or case solution - see the FAQ below.
The conventional response
Point them toward the company's wellness resources, encourage them to take some of their unused time off, and suggest they try to prioritize better - while the actual volume and pace of the work assigned to them stays exactly the same.
This response quietly assumes the problem is the employee's coping capacity rather than the workload itself. It also puts the fix entirely on the person already struggling to keep up, which is precisely the group least equipped, in the moment, to redesign their own workload.
The poorly executed people-first response
Notice the exhaustion, express genuine concern, and informally lighten this one person's load - without examining why the load got to this point, and without addressing where that work now goes instead. Usually, it goes to teammates, who absorb it quietly, and the same pattern shows up in a different person a few months later.
This version is well-intentioned and still doesn't fix anything structural - it just moves the same underlying capacity problem to whoever has the least ability, at that moment, to say no.
A response that treats it as a system problem first
Listen first, and check for anything urgent. Understand what the employee is actually experiencing before diagnosing anything, and pay attention to whether there's an immediate health or safety concern that needs a different kind of response than a workload conversation (see the note on professional support above).
Examine the actual system, not just this person's task list: total workload relative to staffing, role clarity, process friction, meeting load, after-hours expectations, and whether priorities have been quietly conflicting for weeks without anyone naming it.
Make the tradeoffs explicit and visible. Something has to change - stop doing one thing, defer another, automate a third, bring in more staffing, or genuinely reduce scope. "Just work more efficiently" is not a tradeoff; it's a way of avoiding naming one.
Agree on concrete recovery steps and a real follow-up date - not just for this conversation, but as an ongoing check rather than a one-time fix.
Address the pattern at the team level using aggregate signals, not by broadcasting one person's private disclosure. If workload is a team-wide issue, the fix should be visibly team-wide too, without turning one person's vulnerability into a public case study.
How mindfulness shapes this
The main trap for a leader here is defensiveness - the instinct to hear "I'm overwhelmed" as a criticism of how the team is being managed, and respond by minimizing it or quietly reframing it as a personal resilience issue instead of a workload one. Noticing that defensive pull, and setting it aside, is what makes it possible to actually hear what's being reported.
How care shapes this
Care means taking the employee's experience seriously without demanding they disclose more than they're comfortable sharing - a diagnosis, a personal circumstance, or anything else - in order to be believed. "I'm at capacity" is sufficient information to act on.
How accountability shapes this
Accountability runs in both directions here. The leader owns the capacity and prioritization decisions that created the workload in the first place - that's not optional, and it's not the employee's job to fix on their own. The employee, in turn, is responsible for communicating real constraints and commitments early enough that they can actually be planned around, rather than only surfacing at the point of exhaustion.
Risks and tradeoffs
Some deadlines genuinely are fixed - a regulatory filing, a client commitment already made - and "reduce scope" isn't always available even when workload is a real problem. Any accommodation offered has to be applied fairly, or it creates a second problem on top of the first. And if what's actually happening includes a mental-health condition beyond typical work stress, that calls for professional support a manager isn't equipped to provide alone - recognizing that boundary is part of handling this responsibly, not a way of avoiding the conversation.