How to spot (and prevent) quiet quitting on your team

“Quiet quitting” became a buzzword, which is a shame, because the thing it describes is real and matters. Strip away the hype and it’s simple: someone who used to bring discretionary effort stops, and starts doing only what’s strictly required. They haven’t left. They’ve checked out — and on an engineering team, a checked-out senior engineer is often invisible for months, because they’re still closing their tickets.

It’s worth taking seriously, because quiet quitting is rarely the end state. It’s usually the stage right before someone actually quits.

What it actually is

Quiet quitting isn’t laziness, and it’s usually not a character flaw. It’s the withdrawal of the extra — the ideas, the initiative, the mentoring, the caring about the details — while the baseline keeps ticking over. The work gets done; the investment is gone.

That distinction matters, because it changes how you respond. You’re not dealing with a performance problem to be managed up. You’re dealing with a motivation problem to be understood — and usually one you had a hand in creating.

The signs on an engineering team

• Initiative disappears. The person who used to propose improvements and pick up ambiguous problems now waits to be assigned and does exactly that, nothing more.
• They go quiet. Less in code review, less in design discussions, fewer questions, camera off. Presence drops before output does.
• Scope shrinks to the minimum. They stop volunteering, stop mentoring, stop caring about the things outside their immediate ticket.
• 1:1s go flat. They arrive with nothing, give short answers, stop raising ideas or frustrations. The meeting they used to invest in becomes a formality.
• Cynicism creeps in. More “why bother,” more eye-rolling at the roadmap or the process. Disappointment wearing armour.

If those sound familiar, they overlap heavily with the early signals of burnout — the two often travel together. We cover that side in detail in the early signs of engineer burnout.

Why it happens

People don’t withdraw effort for no reason. The usual causes:

• Effort that went unrecognised or unrewarded one too many times.
• A career that feels stuck — no growth, no path, no stretch.
• Burnout, where pulling back is self-protection, not indifference.
• A broken trust — a promise not kept, a promo missed, a decision that landed badly.
• Work that feels meaningless, disconnected from anything they care about.

How to re-engage someone

The good news is that quiet quitting is often reversible, if you catch it before it hardens into a decision to leave.

• Name it, gently and privately. “I’ve noticed you seem less into things lately — what’s going on?” Then listen without getting defensive, even if part of the answer is about you.
• Find the specific cause. It’s almost always something concrete underneath. Get to it.
• Reconnect them to something they care about. A problem that’s theirs, a bit of growth, real ownership.
• Fix what you can, honestly. If the cause is a broken promise or a missing path, half-measures make it worse. If you can’t fix it, say so plainly.

Quiet quitting vs. healthy boundaries

One important caution before you go hunting for quiet quitters: not everyone doing “only their job” is disengaged. Some people are simply setting healthy boundaries — working their hours, declining the heroics, protecting a life outside work — and doing excellent work inside them. That’s not a problem to fix; it’s often exactly what you want.

The difference is direction, not effort level. Healthy boundaries look stable: the person is engaged, contributes ideas, cares about the outcome, and just doesn’t martyr themselves. Quiet quitting looks like a decline — someone who used to bring more and has visibly pulled back. If you mistake the former for the latter and start pushing, you’ll manufacture the very disengagement you were worried about. Watch the trend in the individual, not their hours against someone else’s.

The re-engagement conversation

If you do see a genuine decline, the conversation matters. Don’t accuse, and don’t lead with productivity. Lead with care and curiosity:

“You used to seem really energised by this stuff, and lately it feels like some of that has gone. That’s not a complaint — I’m asking because I want to understand what changed, and whether there’s something I can do about it.”

Then listen for the real cause, which is usually concrete: a missed promo, a project they cared about killed, a stretch of going unrecognised, or plain exhaustion. Once you know it, you can act on it — and if part of the answer is about you or a decision you made, the most re-engaging thing you can do is take it seriously rather than defend yourself.

Prevention beats rescue

Re-engaging someone who has checked out is real work, and it doesn’t always succeed. The cheaper path is not letting them get there — and the levers are the ordinary ones, applied consistently: recognise effort specifically and often, keep growth moving so the work doesn’t go stale, protect people from chronic overload, and keep your promises about progression. Most quiet quitting is the slow accumulation of small disappointments. Managers who stay close enough to catch those early rarely have to run the rescue conversation at all.

It’s also worth a moment of honesty with yourself. When someone checks out, the cause is sometimes the manager — a pattern of unheard feedback, credit quietly taken, a promise that slipped. That’s uncomfortable to consider, but it’s also good news: the things within your control are the ones you can actually fix. Before concluding that a disengaged engineer is the problem, ask whether anything in how they’ve been managed helped get them there.

Catching it before it’s a resignation

The hard part is that none of these signs is loud. A capable engineer who’s checked out keeps shipping, so nothing trips an alarm. You catch it only by paying attention to the slope — engagement trending down, 1:1s going flat, initiative fading — across each person over weeks, which is genuinely hard to do by hand for a whole team.

That’s what CoManager’s member pulse is for: an engagement and morale score per person, trended weekly, so a quiet withdrawal shows up as a falling line instead of a resignation letter. When someone’s trend bends the wrong way, a signal surfaces it early — with a suggested way to open the conversation — so you reach them while it’s still a conversation and not a goodbye.