Spotting Disengagement Before It Becomes Resignation

2026-07-02 · 7 min read · Team Health

The most common thing managers say after an engineer resigns is "I didn't see it coming."

Almost always, they did see it — they just didn't know what they were seeing.

Disengagement has a consistent pattern. Engineers go quiet before they go. They stop volunteering ideas, start doing the minimum, gradually remove themselves from the team's social fabric. By the time someone formally resigns, they've mentally left months ago.

The good news: if you know what to look for, you can usually intervene before it's too late.

The Signal Stack

Disengagement rarely shows up as one dramatic change. It's a cluster of small signals that you need to read together.

Communication changes. An engineer who used to speak up in sprint planning stops contributing. Someone who wrote detailed Slack messages starts giving one-word answers. The absence of communication is often louder than its presence, but it's easy to miss because silence doesn't demand attention.

Drop in initiative. They're doing what's assigned but not volunteering for anything beyond it. No ideas in retros. No "I noticed this and fixed it while I was in the area." The work is fine — it's exactly what was asked for, nothing more.

Shorter horizon thinking. They stop asking questions about roadmap, growth, or team direction. They're not interested in what happens in Q3 because they're not planning to be there for it. This is subtle but significant.

Withdrawal from relationships. They skip optional team events. They stop chatting informally. They're polite but no longer present in the interpersonal texture of the team.

Change in 1:1 tone. 1:1s become transactional — status updates, blockers, nothing personal. If someone who used to bring up their career goals or share something personal has gone silent on both fronts, that's a flag.

Increased frustration about process or decisions. Sometimes disengagement shows up as low-grade chronic complaints about how the team works, decisions made by leadership, or the tech stack. This can look like negativity, but it's often a proxy for "I'm not happy here and this is the only way I know how to say it."

What Causes It

Before you can intervene, you need to understand what's driving the disengagement. The most common causes:

Feeling unseen or undervalued. Their work isn't recognised, their ideas aren't taken seriously, or they're consistently passed over for the interesting work. This is the most common cause and often the most fixable.

Career stagnation. They don't see a path forward. They've been at the same level for two years with no clear picture of what changes that.

Manager relationship breakdown. Something has gone wrong in the trust between them and their manager — often something the manager isn't fully aware of.

Team culture problems. Interpersonal conflict, a teammate who's toxic but tolerated, or a team that feels politically unsafe. People disengage from the team before they disengage from the company.

Life circumstances. Sometimes disengagement is driven by things outside work — a family situation, health issues, burnout from a long stretch of intensity. This requires a different response.

Better opportunity. Sometimes someone is already interviewing. In this case, the question is whether there's something you could offer that would change the calculus.

How to Intervene

Once you've spotted the pattern, the intervention needs to be direct but not confrontational. A good opening:

"I've noticed you've seemed less engaged lately and I want to check in properly. I might be reading it wrong, but I'd rather ask than not. Is there something going on?"

Give them space to answer. Don't immediately offer solutions. Listen first.

If they open up, the next questions are:

That last question is important. You can't fix the problem without knowing what "fixed" looks like to them.

If they deflect ("I'm fine, just tired"), take it at face value but don't drop it: "I hear you. I'm going to check in again in a couple of weeks — not to pressure you, just because I care about how things are going for you."

The Retention Conversation

If someone is on their way out and you want to retain them, have the honest version of the retention conversation. Not the panicked version where you offer a raise at the exit interview, but a proactive one:

"I want to be direct with you. I don't want to lose you, and I want to understand what would make this the right place for you to be. What would need to be true?"

This conversation is harder than it sounds. You might hear things about yourself that are uncomfortable. You might not be able to deliver what they need. But having it early gives you options that a resignation letter doesn't.

What Doesn't Work

Monitoring output metrics more closely. If someone is disengaged, watching their PR count doesn't help. It increases the feeling of being watched and decreases psychological safety.

Piling on more interesting work without addressing the underlying issue. This is a common fix. It sometimes buys time but rarely solves the root problem.

Having the conversation once and moving on. Disengagement is usually chronic, not acute. One good conversation doesn't rebuild months of accumulated distance. You need to follow up consistently.

Prevention Is Better

The managers with the lowest attrition aren't the ones who are best at retention conversations — they're the ones who never need to have them, because they catch the early signals.

This means genuinely investing in every 1:1, tracking growth conversations explicitly, paying attention to how people are showing up over time, and creating enough psychological safety that people tell you when something is wrong before it becomes a resignation.

Engineers don't leave companies. They leave situations they felt they couldn't change. Your job is to be the person who notices, asks, and makes changing it possible.