What Leaders and Managers Can Learn from Sick
Denny had rated Priya his most reliable analyst for two years running. Lately her reports arrived late, thin, sometimes not at all, and her camera stayed off in meetings she used to lead. HR rules meant he couldn't ask what was wrong, only whether she needed anything, and she always said no. He drafted a performance note, then deleted it. Other analysts had started quietly absorbing her work and grumbling about it in a chat he wasn't supposed to see. Denny didn't know if Priya was burned out, grieving, or sick, and the not-knowing made every option feel wrong: push, and risk breaking someone struggling; say nothing, and watch the team's trust erode.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
When a strong performer's story stops adding up
Sick shows how a long, undiagnosed illness gradually reshapes someone's sense of what they can still do, often before they can name it or explain it to anyone else. A manager sees only the visible edge of that shift: missed deadlines, a flatter voice, someone who used to volunteer now going quiet. Reading that edge as a character problem, rather than a possible identity in flux, is the most damaging misread a leader can make.
Assuming a sudden drop in output reflects motivation rather than a possible health change leads to punitive responses that make things worse.
When you see a sustained, uncharacteristic change, ask an open question about support, not performance, and encourage the person to see a qualified physician or specialist rather than guessing at causes yourself.
The unseen costs your org chart doesn't track
Behind dipped output often sits real financial and logistical strain: appointments during work hours, energy spent on tests with no answers, and worry that a manager will read it all as unreliability. The book is candid that this grind is mostly invisible administrative weight, not drama, and it rarely shows up in the metrics a manager reviews.
Managing only to visible output ignores the load a person is carrying just to show up at all.
Build flexible, no-explanation-required options into your team's normal workflow, so support doesn't require a person to justify an unresolved diagnosis.
What your team reads into someone's absence
When one person's condition is invisible and unexplained, the team fills the silence with its own story, usually resentment rather than compassion. The book shows how quickly friends and family default to doubt when illness resists a clean explanation, and a team under deadline pressure defaults the same way, often faster.
Letting rumor fill an information vacuum costs more team trust than a boundaried, general statement about redistributed work would.
Without disclosing specifics, tell the team plainly that support is being provided and ask them to bring concerns to you directly.
Managing for a marathon, not a return date
Sick resists a tidy ending, and so should a manager's plan for a team member navigating unresolved illness. A role that can flex over months, rather than waiting for a return-to-normal date that may not arrive, protects both person and work: responsibilities sized to sustainable capacity now, not to who that person used to be.
Fairness to the team and compassion for the individual pull in different directions almost every week. Protect the struggling employee too visibly, and teammates reasonably ask why they carry more for the same pay. Enforce strict equal treatment too rigidly, and you punish someone for a circumstance largely outside their control. Holding both means making the redistribution of work a transparent team-level decision you own, rather than a private favor, so it reads as management, not preference.
Name one thing, honestly
- Whose recent performance shift have you read as a character issue that might actually be something else? - What in your current workflow would already flex for someone without requiring them to disclose why? - How would your team describe your fairness if they saw exactly what you were accommodating and why?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Without disclosing specifics, tell the team plainly that support is being provided and ask them to bring concerns to you directly.