Reading the room: spotting team problems before they explode.
By the time someone resigns, the problem has been visible for 90 days. Here are the weak signals every leader misses — and a five-minute weekly habit that catches them before they cost you a person.
Every resignation I've ever debriefed had the same shape: the leader was surprised, the team wasn't. Someone two desks over had known for months. The signals were there — quieter standups, declined coffees, slightly shorter PRs — but no one had a system to notice them.
Reading a team is a learnable skill, not a personality trait. It's pattern recognition plus a tiny ritual. Here's the model HR leaders teach engineering leaders and founders.
The four signal categories (and what they actually mean)
- Camera off in meetings they used to lead.
- PRs get shorter and less ambitious.
- Stops pushing back in design reviews.
- Takes a Friday off, then a Monday, then both.
- Asks 'is this in scope?' on work they used to own.
- Withdrawal — not laziness. Something happened or is happening.
- Loss of psychological investment. They're protecting energy.
- They've decided you don't want their real opinion. Trust gap.
- Interviewing, burnout, or a personal thing they haven't told you.
- Resentment about workload or recognition. Tactical disengagement.
The psychology: Hirschman's Exit, Voice, Loyalty
Economist Albert Hirschman observed that when people are unhappy in any system — a country, a company, a team — they choose one of three responses: Exit (leave), Voice (speak up), or Loyalty (stay and tolerate). Most leaders only see Exit, because Voice has stopped working long before. Your job is to make Voice the cheapest, safest option in your team. If the only way to be heard is to threaten to quit, you've already lost.
The five-minute Friday habit
Every Friday afternoon, open a private doc with one row per direct report. For each person, fill in three columns from memory: energy this week (up / flat / down), one specific thing they said or did, and one concrete thing you'll do for them next week. If you can't fill it in, that's the signal. You don't know them well enough yet.
What to do when you spot a signal
- Don't ambush. Don't say 'are you okay?' in standup. That's for you, not them.
- Within 48 hours, book a 1:1 in a neutral setting. Walk, coffee, not a glass-walled room.
- Open with the specific observation, not the diagnosis: 'I noticed you've been quieter in design reviews the last few weeks. I might be reading it wrong — what's going on for you?'
- Listen for 90% of the conversation. Resist the urge to solve.
- End with one concrete commitment from you, not a vague 'let me know if you need anything.'
- Write down what you heard. Follow up within a week.
Real case: the senior engineer who 'suddenly' quit
One HR leader shared how a CTO lost his strongest backend engineer with two weeks' notice. He was blindsided. In the post-mortem, his other engineers told the HR team: she had been left off the architecture committee three months earlier, had stopped being assigned the hard problems, and had quietly transitioned her ownership of the payments service. Three signals, three months, zero conversations. She'd been job-hunting for 11 weeks before she resigned. The CTO now runs the Friday five-minute habit. He's caught two near-misses since.
Take this home — your weekly read-the-room ritual
- Block 5 minutes every Friday for the energy / observation / action grid.
- Flag any direct report you 'couldn't describe' — book a real 1:1 within 7 days.
- When you spot a signal, lead with observation, not diagnosis.
- Track one 'Voice indicator' per quarter: how often did each person disagree with you in a meeting? Zero is a problem.
- Debrief every resignation honestly: when was the earliest signal? What stopped you from seeing it?
HR & Operations leader scaling global remote teams across Nepal, the Philippines, Australia, and the US. Tech-leaning writing lives on Medium.