Quiet Quitting

Why Quiet Quitting Matters

The phrase went viral around 2022, but the thing it points at is as old as work. Strip the label off and you are looking at disengagement, and the reason it is worth tracking has nothing to do with the catchphrase: the discretionary effort that disappears first is exactly the effort that carries a team. By the time it shows up in the numbers, you have usually already lost it.

Picture a strong engineer who stops reviewing other people's pull requests, stops jumping on the incident calls she used to own, and starts logging off at five sharp. Her own tickets still close. Her manager's dashboard looks completely normal. Six months later she resigns, and everyone calls it sudden. It was not sudden. The signal was there for half a year; nobody was reading it.

The mistake worth naming is treating it as a performance problem. A quiet quitter usually meets the formal standard of the job, so the performance process finds nothing, and leaning on them tends to accelerate the exit. What has actually withdrawn is the extra the standard never measured, which makes it a question about engagement and, ultimately, about the retention side of workforce planning.

How Quiet Quitting Works

Quiet quitting is the withdrawal of discretionary effort while formal duties continue, and reading it means watching for the gap between compliance and contribution. The person still does the defined job; what stops is the extra, the initiative, the volunteering, the going-beyond that was never in the job description but that teams quietly depend on. Because the formal work continues, it rarely shows up in obvious performance metrics, which is exactly why it goes unnoticed until it has spread.

The reframe that makes it useful is treating it as a signal about conditions, not a character flaw in the employee. Sustained withdrawal usually traces to something specific, unrewarded overextension, a broken promise on progression, a manager relationship that has gone cold, and it often precedes actual attrition, making it an early warning rather than an end state. A worked read: a reliable performer stops picking up the informal work they used to, output looks fine on paper, but the disengagement is real and, left unaddressed, is a resignation forming in slow motion.

How to Respond to Quiet Quitting

Start by reading falling discretionary effort as information, not insubordination. Look at the usual causes first, workload, recognition, and whether there is anywhere to grow, since those explain most cases.

Then use engagement and mobility signals to find the teams where it is spreading before it spreads further, and fix the cause rather than the symptom. Pressure applied to someone who has already checked out mostly just sets the resignation date; a genuine path forward is what brings the discretionary effort back.