Quiet quitting became one of those workplace terms that everyone had an opinion on the moment it appeared. Some saw it as a generational attitude problem. Others recognised it immediately as something they'd been experiencing in their own teams for years, just without a name for it.
What I've noticed, working with companies across the UK on recruitment, is that quiet quitting is rarely about laziness or disengagement in the way people assume. It's usually a signal — and the companies that learn to read it end up with much more stable teams and far fewer urgent hiring needs.
What quiet quitting actually is
At its core, quiet quitting is a rejection of the idea that going above and beyond is simply what's expected. Employees return to the original scope of their job description — doing what they were hired to do, and no more. They leave at the end of the working day. They stop attending optional meetings. They decline projects that fall outside their role.
For many managers, this comes as a surprise. But for the employees involved, it often feels like a reasonable response to years of expanding scope without expanding recognition, compensation, or support.
Why it's not what you think
The temptation is to treat quiet quitting as a performance issue. It usually isn't. What it signals is a transition — from someone giving discretionary effort freely, to someone making conscious decisions about where their energy goes.
In many cases, this is actually healthy. It's a prevention of burnout. An employee who has recalibrated their boundaries is often more sustainable, more focused, and more honest about their capacity than one who has been quietly overextending for years.
The question for managers isn't "how do we get them to do more again?" It's "what changed, and what does this person actually need?"
How to prevent it — without gimmicks
Engagement has been declining across hybrid and remote workforces, and no amount of team socials or ping-pong tables changes that. What does work is simpler and harder:
- Empathetic one-to-ones — genuine conversations where employees can raise challenges without it becoming a performance discussion. Not scripted. Not tick-box.
- Clarity about scope — regularly revisiting what's actually in someone's role, what's been added informally over time, and whether that's sustainable.
- Visible leadership behaviour — people replicate what they see. Managers who demonstrate healthy boundaries create teams that feel safe to have them too.
- Development that's real — not a training catalogue, but genuine conversations about where someone wants to go and what support they need to get there.
The direct connection to your hiring plan
Here's where it becomes a recruitment issue. When an engaged employee quietly scales back, the duties they were informally carrying don't disappear — they accumulate. Other team members pick them up, or they simply don't get done. Either way, you end up with capacity gaps that weren't in your hiring plan.
The best moment to address this is before it becomes a crisis. That means regularly reviewing your team's actual scope of work, not just their job descriptions — and being honest about whether the headcount you have matches the work you're asking people to do.
Your hiring plan should never be set in stone. The workplace changes, roles evolve, and the people doing the work have lives and limits. The companies I work with that hire most effectively are the ones that treat their staffing plan as a living document — and act early when they see the signals, rather than waiting until someone's out the door.
"Quiet quitting is rarely about laziness. It's a signal. The companies that read it early hire far less urgently."
— Joanna Black