How to spot team toxicity before someone quits
Early signs of team toxicity managers miss — and a lighter monthly signal before exit interviews.
Published
Exit interviews are late.
By the time someone says "I am leaving," the toxicity usually ran for months in Slack threads, quiet 1:1s, and work that stopped getting finished. Managers often felt it. They just did not have a clean signal early enough to act.
This post is about spotting that early. Not a drama checklist. A practical read for managers of small tech teams.
What "toxicity" looks like before it has a name
It rarely starts as open conflict.
More often you see:
- Handoffs that need a third person to translate
- Jokes that only one half of the team laughs at
- Strong delivery from one person, avoidance from everyone else
- 1:1s full of "everything is fine" while the roadmap slips
- The same two people carrying review load every week
None of that shows up cleanly in an annual engagement survey. By the time the PDF arrives, the person who cared most already updated their LinkedIn.
Why annual surveys miss it
Long surveys ask too much, too late.
People rush them. They soften answers. Managers get averages. Toxicity lives in the edges: one collaboration score that quietly tanks while skills still look fine.
If you only look once a year, you are reading history.
A lighter early signal
You do not need forty questions to see friction rise.
A monthly Slack pulse with three ratings is enough for a first pass:
- Skills
- Collaboration
- Impact
Private links. Anonymous answers. Scores hidden until at least three people respond.
Watch collaboration and impact month over month. A single low month can be noise. Two months of soft collaboration while impact holds is worth a conversation. Skills high and collaboration low often means the work is fine and the room is not.
For a copy-ready template, see A 3-question Slack pulse template for managers. The deeper setup is in the How-to.
What to do when the signal dips
Keep the response small.
- Ask one open question in a 1:1: "What is getting in the way of working together?"
- Fix one handoff or meeting, not ten
- Separate performance issues from team climate
- Do not blast a public channel post about "toxicity"
The goal is early repair, not a label.
Also watch for "hero culture." One person ships everything. Everyone else waits. It looks like high skills. Collaboration is already broken. A monthly pulse will not fix that alone. It will make the pattern visible before the hero burns out or the quiet people leave.
Read collaboration across two cycles
One low collaboration month can be a launch crunch. Two months on the same weekday is a pattern worth a conversation, not a public label. Compare collaboration against impact: high impact and falling collaboration is how hero culture hides. Skills can look fine while the room is already tired.
Act on a handoff, a meeting, or a demo ritual. Do not announce “toxicity” in a channel. Do not hunt names. The pulse is an early chart, not a court. If someone is already in a performance process, keep that process separate from the monthly score.
Start free
Wolfloyee Team Harmony is a monthly Slack pulse for small teams. Free during beta. Toxicity rarely starts as a Slack fight. It shows up as exits, quiet 1:1s, and collaboration scores that slide for two cycles. A monthly pulse will not replace management, but it gives you an earlier chart than an exit interview. Act on patterns, not people. Next step: run two pulses back to back on the same week pattern and watch collaboration versus impact. Watch collaboration across two cycles before you rewrite the org chart. Early signals beat exit interviews. Act on patterns, not names. Next step: run two pulses on the same weekday and compare collaboration versus impact.
Catch collaboration dips early: start free and compare two monthly Slack cycles.