Nobody quiet quits with a bang. That's the whole point — and the whole problem. Quiet quitting is a slow, deliberate withdrawal of discretionary effort: the person still shows up, still closes their tickets, still smiles on the Zoom call, but the extra 20% that made them great has quietly left the building. By the time it's obvious, you're usually months past the moment when it was fixable.
The good news: quiet quitting leaves fingerprints long before it leaves a resignation letter. This post covers what quiet quitting actually is (and what it isn't), the early behavioral warning signs worth watching, a manager playbook for the conversation that follows, and the one data source most teams already have that spots the fade first.
What Quiet Quitting Actually Is (and Isn't)
Strip away the discourse and quiet quitting is simple: an employee stops investing effort beyond the literal requirements of the job. No more volunteering for the gnarly project. No more mentoring the new hire. No more "I noticed this was broken so I fixed it." The job description becomes the ceiling instead of the floor.
Two things it isn't. First, it isn't healthy boundaries — someone who logs off at 5pm but brings full energy and care to their working hours is not quiet quitting; they're doing their job well and sustainably. Second, it isn't laziness. Quiet quitting is almost always a response — to feeling invisible, to a broken promise, to a manager who stopped managing, to watching a louder colleague get credit for shared work. That matters because it changes the fix: you can't performance-manage someone out of a problem your culture created.
And the stakes are real. Quiet quitting is rarely a permanent state — it's a waypoint on the road to actual quitting. Gallup and Workhuman found that employees who don't feel adequately recognized are about twice as likely to say they'll quit within the next year, and the Work Institute estimates that roughly 3 in 4 voluntary departures are preventable. The window between checked-out and walked-out is exactly where a good manager earns their keep. (For the full damage report on what disengagement costs before anyone resigns, see our post on the hidden costs of employee disengagement.)
The Early Warning Signs
None of these signals mean anything in isolation — everyone has an off week. What you're looking for is a pattern: several signs, sustained over weeks, in someone whose baseline used to look different. The baseline is everything. Quiet quitting isn't low effort; it's lowered effort.
1. Participation shrinks to the minimum
They still attend the meeting but no longer speak unless asked. Camera goes off and stays off. In brainstorms, they've gone from idea generator to silent observer. The work assigned gets done — competently, even — but nothing beyond it ever appears.
2. They stop volunteering
This one is easy to miss because absence doesn't ping anyone. The person who used to raise their hand for the migration, the on-call swap, the conference talk — hasn't raised it in a quarter. Nobody notices a hand that stays down.
3. The social fade
Slack messages get shorter and strictly transactional. They stop reacting to teammates' wins, stop dropping into the fun channels, skip the optional team lunch three times running. Disengagement from the work and disengagement from the people usually travel together.
4. They stop recognizing others — and stop being recognized
This is the most underrated signal on the list. Giving recognition requires noticing your teammates' work and caring enough to say something — it's discretionary effort in its purest form, which makes it one of the first things to go. And when someone stops going above and beyond, the shout-outs they receive dry up too. Both directions of the recognition signal fade, often weeks before anything shows up in output.
5. Feedback bounces off
In one-on-ones, everything is "fine." Growth conversations that used to spark something now get a polite shrug. Someone who has mentally left doesn't argue about their career path — arguing takes investment.
6. Quality holds, initiative dies
The tickets close on time. The code passes review. But the "hey, I noticed X is about to break" messages stop, the process improvements stop, the questions in all-hands stop. Output metrics look fine, which is exactly why output metrics miss quiet quitting entirely.
Why Managers Miss It
Managers miss quiet quitting for an uncomfortable reason: the early signs live in places managers don't look. Gallup attributes about 70% of the variance in team engagement to the manager — but even attentive managers see only a slice of a person's day. They see the one-on-one and the standup; they don't see the Slack channels where the social fade happens, or the peer-to-peer favors that quietly stopped.
There's also a selection problem: quiet quitters are often former high performers, and managers extend high performers the longest benefit of the doubt. "She's just heads-down this sprint" is a comfortable story right up until the resignation call. If you want a longer look at what manager intuition systematically misses, we wrote about it in manager blind spots and recognition data.
The Manager Playbook
So you've spotted the pattern. Now what? The instinct to either ignore it ("they'll snap out of it") or escalate it ("let's talk about your performance") are both wrong. Here's the sequence that works.
Step 1: Check yourself first
Before the conversation, audit your own behavior. When did you last recognize this person's work — specifically, not a drive-by "great job"? When did you last talk about their growth? Did they get passed over, ignored, or asked to absorb someone else's workload recently? Quiet quitting usually has a trigger, and an awkward number of triggers sit in the manager's lap.
Step 2: Have the curious conversation, not the corrective one
Book a real conversation — not a performance talk, not an ambush appended to a status meeting. Name what you've observed, neutrally and without accusation: "You used to be the first voice in design reviews, and lately you've been quiet. I might be misreading it, but I wanted to ask how you're doing." Then stop talking. The goal of conversation one is diagnosis, not repair. You're trying to learn which problem you have: burnout, boredom, a broken promise, a pay gap, a personal season, or a foot already out the door. Each has a different fix.
Step 3: Fix something visible, fast
Whatever you learn, act on some piece of it within two weeks — and make the action visible. Re-scope the grunt work, restart the promotion conversation, publicly credit the invisible project they carried. A quiet quitter is running an experiment: does anyone notice or care? A fast, concrete response is the only convincing answer. A sympathetic conversation followed by nothing is worse than no conversation at all — it confirms the hypothesis.
Step 4: Rebuild the recognition habit
People rarely quiet quit while feeling genuinely seen. Recognition is the maintenance dose: specific, frequent acknowledgment — from peers, not just from you — of work that matters. Deloitte's research links strong recognition cultures to up to 31% lower voluntary turnover, and mechanically it makes sense: recognition is a weekly, public answer to "does my effort register?" If your team doesn't have that muscle yet, our guide to building a recognition culture is the place to start.
The Recognition-Data Angle: Your Early Warning System
Here's the part most teams overlook. If your team already gives peer recognition — shout-outs in a Slack channel, props, kudos, whatever you call it — you're sitting on a behavioral dataset that detects quiet quitting earlier than any survey. Surveys are quarterly, anonymous, and easy to satisfice. Recognition activity is continuous, individual, and honest, because nobody fakes enthusiasm in a system with no penalty for silence.
The two signals worth watching: someone who used to give recognition regularly and has gone quiet (disengagement from noticing), and someone whose received recognition has dried up (their above-and-beyond work has stopped generating gratitude — usually because it stopped). Either fade, sustained over four to six weeks against that person's own baseline, is a prompt for a Step 2 conversation — while it's still a conversation and not an exit interview. We've written a full deep-dive on exactly this method in detecting quiet quitting with recognition data, and a broader take on using the same signals as a recognition early warning system for attrition.
Full disclosure of bias: this is what we built Propsly for. It's a Slack app — teammates give each other props with the /props command, every give lands in a public recognition feed, and the free tier covers unlimited users with 200 props per person per month plus leaderboards. The Pro tier ($50/month flat for the whole workspace) adds the analytics layer that makes the fade visible: per-person giving and receiving trends, engagement gaps, and the participation drop-offs described above. But even if you never touch our product, the principle stands — instrument recognition, watch the trend lines, and treat a fade as a knock on the door.
Catch the Fade, Not the Farewell
Quiet quitting is a message delivered in the only channel a discouraged employee feels safe using: withdrawal. Managers who learn to read that channel — the shrinking participation, the vanished hand-raises, the recognition that stopped flowing in both directions — get months of lead time that the resignation letter never offers. And months of lead time matter, because the alternative is expensive: run your own headcount through our employee turnover cost calculator and you'll see what every preventable departure actually costs.
Watch the baseline. Ask early, ask curiously. Fix something visible. And build the kind of recognition habit where going above and beyond never goes unnoticed — because people rarely quietly leave a place that loudly appreciates them.