- AllThingsRemote
- Posts
- quiet exits don’t happen overnight
quiet exits don’t happen overnight
how to spot disengagement before it becomes a resignation
Silent disengagement doesn't look like disengagement...
It looks like someone who's really good at their job…
right up until it doesn't.
In today's send:
✅ What silent disengagement actually looks like in your team
✅ The triggers most managers miss until it's too late
✅ What to do before you're reading a resignation letter
But first…
When a great employee leaves, what's usually behind it? |
Top reads this week:
The Slack team have been runnning async longer than most, and their breakdown of what actually works is one of the better reads on the topic.
Heading into the end of year and still figuring out how to keep your team aligned on goals; OKRs for remote teams is a good practical starting point.
Most remote management challenges aren't remote problems; they're just unclear systems.
What silent disengagement looks like
The hardest kind of employee loss to see coming is the one where nothing looks wrong.
They're still hitting their deadlines.
Still showing up to calls.
Still professional in every message.
They're just less present in a way that's difficult to name, and by the time it becomes nameable, they usually have another offer.
In an office, it’s somewhat easier pick up on this.
someone stops getting coffee with their team
starts running late, or not making an effort.
seems a bit flat in the team meeting.
There's ambient signal everywhere.
In a remote team, most of that signal doesn't exist.
You're not watching someone walk through the office.
You're reading their messages and looking at their outputs, and both of those can look completely normal even when someone has emotionally checked out months ago.
The triggers most managers miss
Silent disengagement almost always starts with something specific, not a general feeling of unhappiness.
The most common ones are:
not being stretched in a meaningful way (the work stopped growing before the person did)
feeling invisible to leadership (doing solid work that nobody seems to notice or care about)
a mismatch between what was promised at the start and what the role actually turned into over time.
And the list goes on…
A fourth one which is more specific to remote teams is isolation creep: the slow accumulation of days where the work gets done but the connection to the team and the mission quietly fades.
It's not that anything went badly wrong.
It's that nothing went particularly right either, and eventually the person starts wondering whether something better might be one conversation away.
Most of those triggers are fixable, not because you can fix everything, but because most people who are on the way out would have stayed if someone had noticed and done something about it six months earlier.
What to do before the resignation
The single most useful thing is a stay interview, which is just a 1:1 with a different kind of question at the centre of it.
Not how are things going? but what's keeping you here? and what would make you think about leaving?
Those questions feel a little uncomfortable to ask, which is exactly why most managers don't, and why most managers are surprised when good people leave.
The other thing is making growth visible.
Remote work removes a lot of the ambient signals that tell someone they're valued:
the corridor conversations
the pat on the back
the sense that people see what you're doing.
You have to replace those deliberately.
Specific feedback, visible recognition, conversations about where someone is heading, not just how their current projects are going.
None of that takes much time.
It takes attention, and in a remote team, that attention doesn't happen by accident.
ATR tip of the week
Think of one person on your team who's been consistently solid and who you haven't had a real conversation with recently about how they're doing, not their work, them.
Send them a message this week and ask how things are going outside the current projects.
See what comes up.
Forward this to a remote manager who thinks their team is fine because nobody has complained 👀
Other reads:
Toggl's guide to remote hiring is one of the more thorough ones out there, worth going through before your next role opens.
How to increase psychological safety in a distributed team, and why it matters more than most founders expect.
Not every remote team needs the same stack, but most founders are running too many tools with no clear rules for any of them. This breaks down what you actually need and what you can drop.
Something to think about…
Is there someone on your team right now who you'd be genuinely surprised to lose? Have you told them that recently?
Have a great week!
Thanks,
Sam
PS 👇️
Something more to think about...
Your Q1 strategy deck is done. Your Q1 campaigns aren't booked. Lock in January dates across TLDR's 14 newsletters, read by 8 million tech professionals.
📣 Get in front of 1,677+ remote founders & team leaders.
👋 Say hi on LinkedIn for more!
PS: People often ask me which newsletter platform they should go for. I recommend Beehiiv. Use my link and get 20% off your first 3 months on your paid plan with Beehiiv after a complimentary 14-day free trial.