Work & leadership / B reading preview
Quiet Quitting Created a Monster. It Was Already in the Room.
The least effective managers have three to four times as many quiet quitters as the most effective leaders. The monster is not quiet quitting. The monster is the management that made it rational.
What They Found
HR Brew's 2022 analysis cut through the quiet quitting noise with a single devastating data point from Zenger/Folkman research: the quiet quitting rate is not evenly distributed across organizations. It clusters around bad managers. The least effective managers have three to four times as many people who fall into the "quiet quitting" category compared to the most effective leaders. The phenomenon is not a generational attitude problem. It is a leadership quality problem with a direct, measurable correlation.
The article notes that "quiet quitting is just a new name for doing what's expected and nothing more" and that "the media hype amplifying this not-so-new trend can wind up overlooking what some say is the underlying cause of many resignations, be they quiet or noisy: bad management." Managers who "lent a human touch to their workplace relationships were far more likely to have engaged workforces." The relationship between the manager and the managed is the variable. Everything else is commentary.
The quiet quitting phenomenon also spawned its own ecosystem of derivative terms -- loud quitting, loud firing, quiet fleecing, fast quitting -- each one a variation on the same theme. The article was prescient in identifying what was coming: an industry of buzzwords growing around a single root cause that nobody wanted to name directly.
What They Missed
HR Brew correctly identifies bad management as the root cause. But the article frames it as a talent problem -- find better managers, train the existing ones, develop human touch. The assumption is that bad management is a skills gap. It is not. It is an identity crisis. Most managers do not lack the skills to connect with their teams. They lack the self-concept that would make connection a priority.
The Antidote
Research on the Hero's Journey framework suggests a different physics. The three-to-four-times multiplier between worst and best managers is a measurement of something the framework calls the Identity Shift. The best managers -- the ones with the lowest quiet quitting rates -- have made a fundamental shift in how they see their role. They do not see themselves as the hero of the team. They see themselves as the guide.
A hero-manager measures their success by their own performance, their own visibility, their own career trajectory. Their team exists to support that trajectory. When the team disengages, the hero-manager takes it personally -- as a failure of the team to appreciate what the hero-manager is providing. A guide-manager measures their success by the growth and performance of the people they serve. When the team disengages, the guide-manager asks: what did I stop providing?
The Identity Shift is not a training module. It is a fundamental reorientation of purpose. You are not here to lead. You are here to serve. You are not the protagonist of this team's story. You are the mentor who makes the protagonist's journey possible. The managers with three to four times the quiet quitting rate have never made this shift. They are still performing the hero role, and their teams are responding by performing the only role left: audience member. An audience member who does exactly what is expected and nothing more.
What This Looks Like Monday
Ask yourself one question: "When my team succeeds, whose story is it?" If the honest answer is "mine," you have not made the Identity Shift. This week, find one team win and tell the story publicly -- in an email, in a meeting, in a Slack message -- without mentioning your own role. Credit the person who did the work. Make them the protagonist. Do it until it stops feeling unnatural.
This is a design preview. A local link works only where the preview server is available. Open clean preview link. You can also use your browser’s Print command.