The Organizations That Call Management Overhead Have Already Decided Who Doesn't Matter

The pattern is consistent enough to be a design. A technically excellent individual contributor gets promoted into management because they were the best at the work. No training follows the promotion. The assumption is that technical excellence transfers: someone who could master a codebase can surely manage the people who build one. Several months in, the team is underperforming, the new manager has reverted to individual contribution because that is the only place they feel capable, and leadership draws the conclusion the structure guaranteed: management is overhead. The experiment confirms the belief. The belief was wrong before the experiment started.

The people who pay for this are not the organization. Organizations externalize the cost. The people who pay are the team members who needed someone to build them and were given a peer with a new title instead. The people who pay are the newly promoted managers who were set up to fail and blamed for failing. There is a quiet anger in watching this happen, and in watching leadership respond not with investment but with reorganization, not with training but with termination, not with accountability but with the conclusion that people are, after all, a cost center.

Every organization running this playbook has a values document that says people are the priority. The document is sincere in the sense that leaders generally prefer it to be true about themselves. It is not operative in the sense of governing how budgets are built, how managers are built, or what policies require of the organization toward the people inside it. The gap between the language and the actions is where you find the real values, and that gap is almost always visible.

The belief that management is overhead begins at the top. When technical excellence becomes the credential for authority at every level, the signal propagates downward: management is what technically excellent people do between the real work. That belief governs every subsequent promotion decision, every training investment that does not happen, and every management failure that confirms the hypothesis. An organization that does not invest in building its managers does not have a management problem. It has a values problem, and it is expressing that values problem through its structure.

The cost does not appear on a quarterly call. It shows up in the team member who stops growing because no one is building them. It shows up in the attrition of people who had options and used them. It shows up in the long-term destruction of the conditions that made performance possible in the first place. Organizations that optimize only for the short term do not just underperform over time; they consume their own future. Many organizations have an internal function whose primary purpose has drifted from building people toward protecting the organization from them. That drift is not incidental. It is a structural expression of the same belief: people are a liability to be managed, not a capacity to be built.

The managers who produce extraordinary results in these environments did not find better organizations. They made a different decision inside the same organizations, and the results became visible in ways that could not be explained by technical excellence alone.

Building people is not a soft function. It is the operating condition that determines whether everything else the organization tries to do is possible. Compensating people fairly, designing policies that treat them as people rather than resources to be exploited, investing in their growth as a primary rather than optional expense: these are structural decisions that compound over time. A team that has been genuinely built will outperform a team that has not. They will produce results that get noticed. They will follow a manager who built them to the next role and say so openly.

Here is the test: if the company your mother worked for treated her the way your organization treats its employees, how would you feel? Not in the abstract. Specifically: the policies, the compensation, the manager she reported to, how they invested in building her, the way her time was treated. If the answer is anything other than exactly right, you already know what needs to change.

I write about structural leadership for technical leaders in high-stakes operating environments. The full operating model is in LeadershipOS: http://TheLeadershipOSBook.com

---

I write about structural leadership for technical leaders in high-stakes operating environments. If you want to see where your system is load-bearing on you personally, the LeadershipOS™ Scorecard maps it: https://theleadershiposbook.com/scorecard