How to Overcome Quiet Quitting on Your Team

Two employees do the exact same job. One replies to a Slack message at 9 p.m. because it feels expected. The other closes their laptop at 5 and doesn't think about work again until morning. Only one of them gets called a quiet quitter, and it's usually not a compliment.

We360.ai works with more than 120,000 users across 10,000-plus companies in 21-plus countries, and what we see in that data lines up with Gallup's own numbers: disengagement rarely announces itself. It shows up as slowly shrinking effort long before anyone puts a name to it.

What is Quiet Quitting?

It's doing the work your job description actually requires and declining anything beyond it, without formally resigning or telling anyone you've mentally checked out. It's a boundary, not a resignation letter.

What is quiet quitting?
It's the practice of limiting your effort at work to exactly what your role requires, opting out of unpaid overtime, extra projects, and constant availability, while still technically doing your job.

Zaid Khan, a 24-year-old software engineer, described it simply in the TikTok video that popularized the term: "You're still performing your duties, but you're no longer subscribing to the hustle culture mentality that work has to be your life." His clip and the ones that followed it collected more than 17 million views under the hashtag, though the LA Times has reported the phrase itself surfaced months earlier from an American Gen-Xer, not a Gen Z creator.

What does this look like in the Workplace?

In practice, it usually looks like withdrawal, not sabotage: an employee stops volunteering for extra projects, declines messages after hours, and does the minimum required to avoid a bad review. Nothing about it violates a policy on paper.

That's exactly what makes it hard to manage. A manager can point to a missed deadline or a rule violation. Pointing to someone doing precisely what their job description says, and nothing more, is a much harder conversation to start.

Data helps here more than a manager's gut feeling does. A gradual drop in voluntary collaboration, fewer messages in shared channels, fewer optional meetings attended, shows up in workforce analytics well before it shows up in a formal review. The pattern matters more than any single week, since everyone has an off week now and then without it meaning anything.

What are some Real Quiet Quitting Examples?

Real examples include declining to answer emails after hours, refusing unpaid overtime, sticking strictly to listed job duties, and skipping optional meetings or team events that aren't actually required. Each one is individually reasonable. The pattern across all of them is what signals disengagement.

• The 5 p.m. cutoff. Logging off exactly on time, every day, with zero flexibility even during a genuine crunch.
• The minimum viable task list. Doing only what's explicitly assigned, never picking up dropped work from a teammate.
• The silent meeting. Attending required calls but never volunteering an opinion or raising a concern.
• The declined stretch assignment. Turning down a growth opportunity that used to be an easy yes.

[Image: A simple before-and-after comparison of an engaged employee's task list versus a disengaged one - alt='a shrinking task list shown over several months']

None of these are against the rules. That's the point, and it's why treating this as a discipline problem usually backfires.

Is Silent Quitting the Same as Quiet Quitting?

Silent quitting describes the exact same behavior; it's just a second name that emerged around the same time in 2022. Some writers use "silent quitting" specifically to describe employees who never voice their dissatisfaction at all, versus quiet quitters who at least set visible boundaries.

The distinction rarely matters in practice. Whichever term someone uses, the underlying signal is the same: effort has quietly dropped below what it used to be, and nobody's said anything about it directly yet.

Related terms have piled up since 2022 too. "Quiet firing" describes the employer-side mirror image, withholding raises, feedback, or growth opportunities until someone leaves on their own. "Loud quitting," Gallup's own term, describes actively disengaged employees who make their unhappiness visible instead of keeping it quiet. All three describe points on the same spectrum, not three separate problems.

Why do Employees Actually Quiet Quit?

Employees quiet quit mainly because of unfulfilling work, an unclear or unfair workload, and a lack of recognition, not because an entire generation suddenly decided to stop caring. Blaming a single age group misses what the data actually shows.

Gen Z and young millennial engagement did fall about 4 points between 2019 and 2022, according to Gallup, and a separate Microsoft survey of 30,000 workers found 54% of Gen Z were actively considering quitting their job outright. That's a real shift, but it tracks a broader disengagement trend across every age group, not a uniquely Gen Z phenomenon.

McKinsey found a similar pattern beyond one generation: 40% of the global workforce said they were at least somewhat likely to quit their job within three to six months, in research published around the same period. Younger workers show up more often in these numbers, but the underlying causes, unclear growth paths, thin recognition, workloads that never quite balance out, hit every age group that's been asked.

Workload imbalance shows up constantly as an underlying driver. One person quietly absorbing more than their share while getting the same recognition as everyone else is a fast route there. Our guide on workload distribution mistakes covers how that imbalance builds up in the first place, usually without anyone noticing until it's already a pattern.

How do you Overcome Quiet Quitting as a Manager?

You overcome it by fixing the underlying disengagement, not by policing the boundary itself, since punishing someone for doing exactly their job description tends to make the disengagement worse, not better. The fix has to happen before the resentment sets in, not after.

1. Ask directly, without judgment. A blunt "how are you feeling about your workload" conversation surfaces more than a passive-aggressive comment about someone leaving at 5 sharp.
2. Check whether the workload is actually fair. Compare who's picking up unassigned work against who isn't, using real data instead of a gut feeling.
3. Recognize contribution specifically, not generically. "Good job this quarter" does less than naming the actual project someone carried.
4. Give people a real reason to go beyond the minimum. Growth opportunities, not guilt, are what pull someone back into full engagement.
5. Separate performance issues from boundary-setting. An employee who's genuinely missing deadlines needs a different conversation than one who's simply stopped doing unpaid extra work.

A concrete version of this: a manager notices someone who used to volunteer for cross-team projects has stopped entirely over the last two months. Instead of a vague check-in, the useful move is naming the specific pattern directly. "I noticed you haven't picked up a cross-team project since March. Is something going on with workload, or has something changed for you?" That's a different conversation than a performance review, and it usually gets a more honest answer.

Timing matters more than most managers assume. Waiting until the annual review to raise a pattern that started six months earlier guarantees the employee has already mentally filed it as something the company didn't care enough to mention sooner.

If a genuine performance problem shows up alongside the disengagement, and it's a pattern rather than a one-off, our guide to a fair, consistent disciplinary process covers how to handle that stage without it reading as retaliation for someone simply enforcing a boundary.

Want to see whether disengagement on your own team traces back to workload, recognition, or something else entirely? Start a free trial to check real focus and workload patterns this week, or book a demo to walk through it with us directly.