Every manager has lived this story. A solid performer hands in their notice, and the reaction around the leadership table is genuine surprise: "That came out of nowhere." Except it didn't. By the time someone resigns, they've usually been gone for months — they just hadn't updated the paperwork yet. The withdrawal happened slowly, in plain sight, in a hundred small behaviors nobody was measuring.
Quiet quitting is what that withdrawal looks like while the person is still on payroll. And here's the thing most "warning signs of quiet quitting" articles miss: you don't have to rely on vibes — the camera turned off, the Slack replies getting shorter — to catch it. If your team gives peer recognition through a shared system, the earliest and most honest warning signals are already sitting in your data.
What Quiet Quitting Actually Is
Strip away the discourse and quiet quitting is simple: it's the withdrawal of discretionary effort. The person still attends the meetings, still closes the tickets, still hits "acceptable." What disappears is everything they were never contractually required to do — helping a teammate debug at 6pm, volunteering for the unglamorous migration, noticing that the new hire is drowning and quietly throwing them a rope.
That's why quiet quitting is so hard to catch with performance metrics: performance is the last thing to drop. Discretionary effort goes first, and discretionary effort was never on the dashboard. It's also why quiet quitting matters even when it never becomes actual quitting — a team of people doing the minimum is a team that has stopped compounding. But often it does become the real thing: disengagement is the departure lounge. Gallup and Workhuman's research found employees who don't feel adequately recognized are about twice as likely to say they'll quit within a year — and every departure you fail to see coming carries a real price tag, one you can estimate with our employee turnover cost calculator.
Why the Usual Signals Fail
The standard tools for spotting disengagement all share the same flaw: they're slow, and they're easy to perform.
- Engagement surveys run annually or twice a year. A person can slide into quiet quitting and out the door entirely between two survey windows — and disengaged employees are exactly the ones who answer surveys with polite neutrality or skip them altogether.
- One-on-ones get performed. Someone who has mentally checked out can run a perfectly pleasant 1:1 on autopilot. "Everything's fine" is the cheapest sentence in management.
- Output metrics lag by design. By the time velocity or quality visibly drops, the disengagement is many months old and much harder to reverse.
And if your team is remote or hybrid, even the informal signals — body language, hallway energy — are gone. As we wrote in our piece on recognition in remote and hybrid teams, you can't see someone checking out through a webcam that's turned off.
Recognition Data Is Behavioral Telemetry
Here's what makes recognition activity different from every signal above: it's voluntary, frequent, and timestamped.
Nobody is required to give props to a colleague. Every recognition someone gives is a small, unforced act of engagement — proof they were paying attention to their teammates and cared enough to say something. Every recognition someone receives is a teammate's honest testimony that this person did something worth noticing. And because it happens continuously, week in and week out, it produces a time series — not an annual snapshot.
That combination is exactly what an early-warning system needs. Surveys tell you how people say they feel, twice a year. Recognition data shows you how people actually behave, every week. When the behavior changes, the data changes — long before anything shows up in output, and without anyone having to fill out a form. This measurability is precisely why we've argued recognition deserves to be treated as a strategic need rather than a perk: run it as a system and you get culture telemetry for free.
The Four Warning Signs
1. Giving Stops First
The single earliest signal, and the one almost everyone overlooks, is on the giving side. Recognizing a colleague requires two things quiet quitters withdraw first: attention to other people's work, and the willingness to spend energy on something optional. Someone who gave props twice a month all year and hasn't given any in eight weeks has changed something — their giving rate is a proxy for how connected they feel to the team around them. Watch for the person whose giving quietly goes to zero while everything else still looks normal. Everything else going quiet comes later.
2. Received Recognition Drops
The receiving side tells the complementary story. Recognition is triggered by discretionary effort — the extra help, the unasked-for fix, the save. When someone stops going beyond the minimum, their teammates have less to recognize, and their received props decline even though their formal output hasn't moved. A falling received-recognition trend is your earliest measurable evidence that someone's discretionary effort is evaporating.
One important nuance: sometimes this signal is inverted — the person is still doing great work, and the team has simply stopped noticing. That's not quiet quitting yet, but it's how quiet quitting starts, because feeling invisible is one of its main causes. Either way the signal demands attention; our guide to fixing recognition inequality covers the second case in depth.
3. Team-Wide Participation Drops
When one person goes quiet, look at the person. When a whole team's recognition activity sags — participation rate falling quarter over quarter, fewer unique givers, longer gaps between props — you're not looking at an individual problem. You're looking at a team whose energy is draining: a manager problem, a workload problem, or a morale problem. Team-level participation is the closest thing you'll get to a continuously updating engagement survey, and it doesn't wait for October to tell you the team is struggling.
4. Cross-Team Recognition Dries Up
Quiet quitting is a retreat to the minimum viable job, and the first territory surrendered is always the optional stuff between teams — the favor for another department, the collaboration nobody mandated. When someone's recognition ties to people outside their immediate team disappear, their world is shrinking to exactly the size of their job description. At the team level, the same pattern reveals silos forming, something we explored in what recognition patterns reveal about team culture.
What to Do When You See the Signal
The entire point of an early signal is that you catch it while it's still reversible. What you do next determines whether it stays that way.
- Never ambush with the dashboard. "I noticed you haven't given any props lately" is a surveillance sentence, and it will make everything worse. The data tells you where to look. It is not a script for the conversation.
- Have a genuine check-in. Ask real questions about workload, growth, and what's gotten harder lately — then listen. You're not trying to confirm a hypothesis; you're trying to understand a person. Quiet quitting almost always has a reason, and it's usually one the person will share if the conversation is safe.
- Re-recognize deliberately. If their work has been invisible, fix that this week — specifically and publicly. Feeling unseen is a cause of disengagement, which means visible appreciation is treatment, not just detection.
- Fix the systemic version. If the signal is team-wide, the fix is team-wide: address the workload, the manager gap, or the recognition drought — not fifteen individual check-ins about the same root cause.
A Caveat: Signal, Not Verdict
A drop in recognition activity is a reason to pay attention. It is never proof of anything. People go on parental leave. They get pulled onto a heads-down project with no collaboration surface. They change roles. Some people are simply less expressive, always were, and are perfectly engaged. A signal earns a curious, human follow-up — nothing more.
And a harder rule: the moment recognition data becomes a stick — cited in performance reviews, tracked as a quota, wielded as evidence — people will start gaming it, and every signal described in this article will turn to noise. Recognition data only works as an early-warning system while recognition itself stays genuine. Protect that, and the data stays honest. That's also the argument for keeping this data in the hands of people trying to help rather than people keeping score.
You Can't See Any of This Without a System
None of these signals exist if recognition lives in hallway comments and meeting shout-outs, because spoken appreciation leaves no record. The signals only exist when recognition flows through a shared, digital system — which is what Propsly provides inside Slack. Props take seconds to give, land in a public feed, and accumulate into exactly the time series this article describes: giving rates, receiving trends, participation, and cross-team flows, visible in the analytics dashboard while there's still time to act on them.
The resignation that "came out of nowhere" never did. The signal was there. The only question is whether anything was listening.