Quiet Disengagement Is Not a You Problem. It's an Everyone Problem.
A week ago I published a piece on why your best engineers are quietly disengaging. I figured a few people would nod along and move on.
Instead it crossed 5,500 views, and my inbox filled up.
What surprised me wasn’t the number. It was the DMs. People I’d never met wrote to thank me for calling it out. Almost every one of them said some version of the same thing: “I thought it was just me.” One senior engineer told me he’d read it three times and forwarded it to his manager, because he didn’t have the words for what he’d been feeling until he saw it written down.
That reaction told me something. When a post about people silently checking out makes a stranger feel less alone, the problem is not niche. It’s everywhere, and it’s bigger than most of us running engineering teams want to admit.
The numbers most leaders haven’t looked at lately
Here’s the part that should stop you cold. According to Gallup’s State of the Global Workplace, only about 1 in 5 employees worldwide is actively engaged at work. Nearly two-thirds fall into the “not engaged” middle, the group Gallup describes as putting in time but not discretionary effort. The rest are actively disengaged.
Global engagement fell in 2024 for only the second time since 2009. That decline alone cost the world economy an estimated $438 billion in lost productivity, and Gallup estimates a fully engaged workforce would add roughly $9.6 trillion to the global economy, close to 9% of global GDP.
Now here’s the line that reframes everything for people in leadership. The sharpest drop was among managers. Manager engagement fell from 30% to 27% in a single year, and it fell hardest for managers under 35 and for women.
Sit with that. The people we count on to notice quiet disengagement on their teams are quietly disengaging themselves. The smoke detector is asleep.
That’s why this is bigger than most engineering leaders realize. We tend to picture disengagement as one burned-out person we can coach back. The data says it’s closer to the baseline condition of the modern workplace, and it’s climbing up the org chart, not down.
And the trillions in the headline undersell it, because the cost that actually hurts a team is not on any global ledger. It’s the staff engineer who stops mentoring the juniors. It’s the design review that nobody challenges anymore, so a bad decision ships unopposed. It’s the person who would have caught the edge case if she still cared enough to look. Disengagement doesn’t announce itself as a resignation. It shows up first as a slow erosion of the small acts of ownership that made a team good, and those are exactly the things no dashboard counts.
Why we keep missing it
Quiet disengagement is invisible by design. The engineer who’s checked out doesn’t file a complaint. She stops volunteering for the hard problems. Her PRs get smaller and safer. She goes quiet in standup, still hits her tickets, and stops arguing for the thing she used to care about. Every one of those signals reads as “fine” on a status report.
I’ve been on both sides of this. I’ve led teams where I missed it, and earlier in my career I was the one going through the motions because the direction was unclear and speaking up hadn’t changed anything. Nobody flagged me. My tickets closed on time. From the outside I looked productive right up until I left.
That’s the trap. Our dashboards measure output, and disengaged people produce output for a long time before they stop. By the time it shows up in delivery metrics, you’re already months behind the moment you could have done something.
There’s a second reason we miss it, and it’s less comfortable. Noticing quiet disengagement means admitting that something about how we’re leading might be causing it. It’s easier to read a quiet engineer as “just not a big talker” than to ask whether the roadmap stopped making sense to her six weeks ago. The interpretation that requires nothing of us is always the tempting one. It’s also almost always wrong.
What actually helps
The good news is that the fix is not exotic. It’s mostly attention paid earlier, and a willingness to act on soft signals before they become hard ones. Here’s where I’d start.
Watch the trend, not the snapshot. One quiet week means nothing. A steady three-week slide in how much someone contributes to design discussions, reviews, or planning means something. The signal is almost never a single dramatic event. It’s a slope. You have to be looking at the slope. This is exactly why I built CrewPulse to track health signals like communication, workload, and morale alongside delivery data, because the two together tell you a story neither one tells alone.
Ask better questions in your one-on-ones. “How’s it going?” gets you “fine.” Try “What’s something you used to care about here that you’ve stopped pushing on?” or “If you could change one thing about how we work, what would it be?” The answers are uncomfortable. That’s the point. Disengaged people rarely lie when you ask them something specific enough to be worth answering honestly.
Close the loop or don’t ask. The fastest way to manufacture disengagement is to solicit feedback and then do nothing with it. If someone tells you the roadmap makes no sense and three months later it still makes no sense and no one acknowledged their point, you’ve taught them that speaking up is wasted breath. Either act on what you hear, or explain plainly why you can’t. Silence is the worst option.
Fix your own engagement first. The Gallup data is a message to leaders about themselves, not just their teams. A checked-out manager cannot detect a checked-out engineer, because noticing requires attention you don’t have when you’re running on empty. If you’re the one going through the motions, start there. Your team’s engagement has a hard ceiling set by yours.
Make it safe to say “I’m not okay with this.” People disengage quietly because loud disagreement felt unsafe or pointless. If dissent in your standups always comes with a cost, you’ve trained your team to give you the silent version instead. The teams that catch disengagement early are the ones where saying “this priority is wrong” is treated as useful, not disloyal. I write more about this in tech[inclusive], the community I run for people navigating exactly these dynamics.
The part I keep coming back to
The most common message I got wasn’t from a leader. It was from an individual contributor who felt seen. That gap is the whole problem.
The people living inside quiet disengagement know exactly what it feels like. The people who could fix it often can’t see it, because it’s designed not to be seen and because a lot of them are quietly disengaged too. Closing that gap is not a tooling problem or a perks problem. It’s an attention problem, and attention is a choice leaders make every single day.
If this resonated the way the last one did, I’d genuinely like to hear your version. What did quiet disengagement look like on your team, and what, if anything, pulled someone back? The more of us who say it out loud, the fewer people have to sit there thinking it’s just them.
CrewPulse tracks morale, workload, and communication trends weekly, alongside delivery data, so you catch the slope before it becomes a departure. Start your free trial here.