Middle manager ineffectiveness is real, but it is almost never a headcount problem. It is a skills problem, and the gaps show up most visibly when things go wrong: feedback conversations that never happen, conflict that gets avoided rather than managed, direct communication that softens into ambiguity. These skills cannot be learned from a training video or a bot. They require practice in progressively higher-stakes environments, with real support. Organizations that invest in developing those capabilities produce better outcomes than those that eliminate the layer and hope the problem disappears.

In a recent post, we argued that org flattening misidentifies the problem organizations are actually trying to solve. The inefficiency visible in the middle management layer is not primarily a headcount issue. It is a skills issue sitting inside a process issue, and cutting a layer of the org chart does not fix either one.

In this article, we go one level deeper. Because if the argument for investment over elimination is going to hold up, it has to be specific about what the skills gap actually looks like, why it is so common, and what effective development actually requires. Vague commitments to “investing in leadership” are not a strategy. They are a way of deferring the problem while feeling like you have addressed it.

So let us be specific.

The Skills Gap Is Real, and It Shows Up When Things Go Wrong

In our consulting work, we see a consistent pattern across organizations of different sizes, industries, and leadership maturity levels. Managers tend to perform adequately when conditions are stable. They can run a meeting, communicate a directive, and manage a team that is largely functioning well. The gap surfaces when something goes wrong.

The specific skills that break down most consistently are not complex or surprising. They are:

• Providing actionable feedback. Most managers can offer positive reinforcement. Far fewer can deliver specific, behavioral, developmentally useful feedback when someone is underperforming. The conversation either does not happen, or it happens in a form so softened that the recipient does not understand what needs to change.
• Creating psychological safety. The concept has become so widely discussed that many managers believe they are doing it when they are not. Psychological safety is not a general atmosphere of friendliness. It is the specific condition under which people can raise problems, disagree with decisions, and admit mistakes without fear of retribution. Building it requires consistent, observable behavior over time, and it is fragile in ways that most managers do not anticipate.
• Managing conflict. This is the skill we see avoided most aggressively. Most managers do not manage conflict. They manage around it. They redistribute work, avoid certain conversations, or wait for the problem to resolve itself. The short-term cost is low. The long-term cost is a team dynamic that has calcified around the unresolved tension, and a manager who has lost credibility with the people watching.
• Direct communication. The instinct to soften difficult messages is understandable and human. But when clarity is consistently sacrificed in service of comfort, teams lose the ability to calibrate their own performance. They do not know where they stand, what is expected, or what the consequences of continued underperformance will be. Ambiguity at the manager level creates anxiety at the team level.

None of these are exotic leadership competencies. They are foundational. And their absence at scale is what makes middle management look like a structural problem when it is actually a development problem.

Why the Gap Is So Common

The short answer is that most managers were never taught these skills in any meaningful way, and the conditions under which organizations typically promote people do not require them to be.

The path to management in most organizations runs through individual contribution. You perform well as an individual contributor, you get promoted. The skills that made you successful as an individual – technical expertise, reliability, productivity – are largely irrelevant to what management actually requires. But the promotion happens anyway, often without any meaningful development investment, because the organization needed someone in the role and you were the best available option.

This is a stretch promotion masquerading as a recognition. And there is nothing inherently wrong with stretch promotions. They are often how the best leadership development happens. The problem is when organizations make the stretch promotion and then provide no support structure to close the gap. They assume the new manager will figure it out, learn from observation, or somehow absorb the skills required through proximity to the work. Some do. Most do not, at least not quickly enough, and not without significant cost to the teams they are learning on.

The bots are not going to solve this either. AI can help a manager find information, draft a message, or prepare for a conversation. It cannot simulate the discomfort of a real feedback conversation with a real person who pushes back. It cannot replicate the relational dynamics of a team in conflict. If anything, the conversational ease of AI tools creates a false sense of preparation. A manager who has rehearsed a difficult conversation with a bot has not practiced conflict management. They have practiced talking to something that agrees with them.

What Effective Development Actually Requires

The skills that break down under pressure cannot be developed outside of pressure. This is the core design principle that separates effective leadership development from the kind that produces nothing measurable.

Take conflict management as the clearest example. You cannot learn it from a workshop slide, a case study, or a conversation with a chatbot. You learn it by being in a situation that is genuinely uncomfortable, where the stakes feel real, and then applying the skills you have been taught, in real time, with real consequences. The learning is in the doing, not in the knowing.

What effective development structures look like in practice:

• Progressive stakes. Skills are built in safe environments first, then applied in progressively higher-stakes situations. A manager practices giving difficult feedback in a structured role-play before they do it with an employee on a performance plan. The skill transfers through repetition at increasing levels of real-world risk.
• Real practice with real people. The relational skills required for effective management are learned in relationship, not in isolation. Development programs that do not put managers in rooms with other managers, working through real scenarios, are not developing the skills that matter most.
• Structural support after the training ends. The most common failure point in leadership development is not the program itself. It is the absence of any support structure once the program ends. Managers return to their teams, the urgency of daily work reasserts itself, and the new behaviors fade because there is no reinforcement mechanism to sustain them. Coaching, peer cohorts, and manager accountability structures are not add-ons to effective development. They are the part that makes it stick.

The Competency Framework Underneath the Development Strategy

Effective leadership development requires a clear definition of what you are developing toward. Without a common framework, development programs default to whatever content is available rather than whatever gaps are most consequential. Progress is hard to measure because the target was never clearly defined.

The OGC Leadership Competency Wheel organizes leadership capability across six domains, structured around the insight that leadership grows outward from leading self to leading the enterprise. The people leadership and collaboration domains, which include the feedback, conflict management, and direct communication capabilities described above, are not supplementary skills. They are core competencies that determine whether a manager creates conditions for performance or conditions for dysfunction.

The organizations that invest in developing these capabilities systematically, with a shared framework, progressive development structures, and real accountability, consistently outperform those that treat manager development as an optional add-on to performance management. The skills gap is real. But it is also closeable, if you treat it as the actual problem rather than the symptom of a structural one.

If the patterns described here sound familiar and you are seeing them in your organization, we are happy to talk through what leadership development at the manager level actually looks like in practice. Explore the OGC Leadership Competency Wheel or reach out to start that conversation.