You Can't Fix Organizational Dysfunction From Middle Management (But Here's What You Can Do)
The Meeting That Changed How I Think About This
Early in my career, before I moved into management, I sat in a meeting where a senior manager stood before the room and confidently announced a major process change that would "transform how we operate."
The engineers in the room knew immediately it wouldn't work. The process ignored how the network actually functioned. It created dependencies that didn't make sense. It added steps that slowed everything down without improving anything.
We said so. Professionally. With specifics.
The manager nodded, took notes, and implemented the process anyway.
Six months later, after the process created exactly the problems we predicted, leadership quietly abandoned it and implemented something close to what the engineers had suggested. Nobody acknowledged what happened. No lessons were documented. The same pattern repeated itself six months later with a different initiative.
That was my first real introduction to organizational dysfunction.
Not the dramatic kind you see in movies - no screaming executives, no obvious villains. Just the quiet, grinding reality of organizations that make the same mistakes repeatedly, where good ideas get ignored, and bad ones get implemented, where the people closest to the work have the least influence over how it gets done.
Over almost 25 years across multiple organizations - from MSPs to finance to retail to data centers - I've seen variations of this pattern more times than I can count. And now that I've moved into management, I'm learning something important from the other side of that desk:
Middle management cannot fix organizational dysfunction.
You can manage it. You can shield your team from the worst of it. You can fight specific battles and occasionally win. But the deep systemic issues that create dysfunction - those live above your pay grade and outside your sphere of control.
This isn't defeatism. It's clarity.
Because once you accept what you can't fix, you can focus energy on what you actually can influence. And that matters enormously - both for your team and your own sanity.
What Organizational Dysfunction Actually Looks Like
Before talking about what you can and can't do, let's be specific about what we mean by organizational dysfunction. Because it's not always obvious - it often masquerades as normal business operations.
Pattern 1: The Revolving Priority Door
What it looks like:
A project kicks off with executive sponsorship and clear direction. Your team commits resources and starts work. Three weeks in, leadership announces a new "strategic priority." The original project gets deprioritized. Your team pivots.
Four weeks later, the original project is back because the new priority hit obstacles. Your team pivots again.
The cost nobody calculates:
Context switching kills productivity (research consistently shows this takes 20-30 minutes to recover from per switch)
Your team loses trust in organizational direction
Partially completed work creates technical debt
Engineers stop investing in projects because "it'll probably get canceled anyway."
Where it comes from:
Leadership without a clear strategic vision. Reactive decision-making. No mechanism to evaluate whether new priorities are actually more important than existing commitments.
Your level of control: None over the cause. Some over how your team experiences it.
Pattern 2: The Accountability Vacuum
What it looks like:
A project fails. An initiative doesn't deliver. A decision creates problems.
What happens next:
A retrospective meeting where everyone discusses what went wrong in abstract terms. Nobody is held responsible. No decision-making process changes. The people who made the bad decisions are still making decisions.
Six months later: Same type of failure, different project.
The cost:
Good engineers who care about outcomes get frustrated watching dysfunction repeat
Bad decisions aren't connected to consequences
The organization doesn't learn because learning requires accountability
Where it comes from:
A leadership culture that prioritizes relationships over outcomes. Fear of conflict. Organizational politics where accountability is selectively applied downward (individual contributors) but rarely upward (leadership).
Your level of control: None over the culture. Some over how your team operates within it.
Pattern 3: The Communication Black Hole
What it looks like:
Decisions get made above your level. Those decisions affect your team. You find out when your team asks you questions you can't answer.
"Did you hear we're migrating to a new ticketing system next month?"
"Are we doing the office relocation? Because facilities told someone on my team we are."
"Leadership announced we're outsourcing the NOC. Is that true? Should we be worried?"
The cost:
Your team loses confidence in you as a source of reliable information
Anxiety and rumor fill the information vacuum
People make career decisions (looking for jobs, disengaging) based on incomplete information
Where it comes from:
Leadership that makes decisions in isolation and communicates poorly. Organizational silos. Lack of change management discipline.
Your level of control: None over leadership communication patterns. Some of the ways you handle the gaps with your team.
Pattern 4: The Budget That Never Matches Reality
What it looks like:
You build a budget based on actual operational needs. Equipment lifecycle, licensing, and headcount for planned work.
What comes back:
A budget that's 60-70% of what you requested, with no clarity on what got cut or why, and full expectation that you'll deliver the same outcomes.
The conversation:
"We need to find efficiencies."
"Work smarter, not harder."
"Think about what's really essential vs. nice to have."
The reality:
Some of what got cut was essential. The infrastructure that should be replaced will run longer. Projects that need proper resources will be understaffed. Technical debt will accumulate.
And when the aging infrastructure eventually fails - and it will - the same leadership that cut the budget will ask why you didn't flag the risk.
Where it comes from:
Organizations that treat IT as a cost center rather than a strategic investment. Finance processes that don't understand the infrastructure lifecycle. Short-term financial thinking.
Your level of control: None over organizational budget philosophy. Some over how you prioritize within constraints and document risks.
Pattern 5: The Structural Understaffing That Never Gets Fixed
What it looks like:
Your team is genuinely understaffed. Not "could use more people" understaffed - actually understaffed. The workload requires X people to execute safely and sustainably. You have X minus 3.
You document this. You make the business case. You escalate.
What happens:
"We understand the concern. We'll revisit headcount in the next budget cycle."
Next budget cycle: same conversation.
Meanwhile:
Your existing team works unsustainable hours. Burnout increases. Good people leave. When they leave, you can't backfill because headcount is frozen. Now you're X minus 4.
Where it comes from:
Organizational underinvestment. Leadership that believes headcount requests are negotiating tactics rather than genuine needs. Inability to quantify the cost of understaffing vs. the cost of headcount.
Your level of control: None over organizational headcount decisions. Some overprotecting your team from the worst consequences.
Structural understaffing and the cost of organizational underinvestment connect to Both Sides of the Desk: Burnout (Manager's Perspective) - this is where manager burnout comes from.
Why Middle Management Can't Fix Organizational Dysfunction
Let's be honest about something that management books rarely say directly:
The organizational dysfunction that most severely affects your team typically originates well above your level. And the tools you have as a middle manager are insufficient to address root causes that live at the executive or board level.
The Authority Gap
What you have authority over:
How your team operates day-to-day
Processes within your team
How you communicate to your team
How you advocate upward
Hiring decisions (sometimes, with approval)
Resource allocation within your budget
Culture and norms within your team
What you don't have authority over:
Organizational strategy and direction
Budget allocation above your level
Other departments' priorities and behavior
Executive decision-making
Organizational culture above your team
Headcount decisions beyond your team
Compensation structures
Organizational structure
The gap between these two lists is where organizational dysfunction lives.
You can create a great culture within your team while the organization around it is dysfunctional. But you can't fix the organization from within your team.
The Political Capital Problem
Even when middle managers identify organizational dysfunction clearly, fixing it requires:
Building consensus among people who have competing interests in maintaining the current state
Convincing leadership to acknowledge problems they may have created
Sustaining pressure over time against natural organizational inertia
Having enough political capital to keep pushing without burning relationships
The reality:
Most middle managers lack the political capital to drive significant organizational change and spending what capital you have on systemic problems you can't fix depletes resources you need for fighting battles you can win.
I learned this early in a previous role:
There was a fundamental disconnect between how technical priorities were set and how the business actually worked. The people making technical decisions didn't understand the business. The people who understood the business weren't involved in technical decisions.
I spent months pushing for a cross-functional process that would bridge this gap.
I had good arguments. I built a business case. I found allies. I escalated appropriately.
The result: A committee was formed, met twice, and quietly dissolved when priorities shifted. The fundamental problem continued.
What I'd do differently:
Spend that energy on things I could actually influence. Accept that this particular dysfunction lived above my level and focus on protecting my team from its effects rather than trying to fix its cause.
The Timeframe Problem
Organizational change - real cultural and structural change - happens over years, not months.
Middle managers typically:
Are newer to organizations than the dysfunction they're trying to fix
Have shorter time horizons than organizational change requires
Face competing priorities that make sustained focus on systemic change difficult
May leave or be promoted before the change they drove comes to fruition
You can plant seeds. You can advocate. You can create small changes within your sphere.
But fixing deeply embedded organizational dysfunction requires sustained leadership commitment over the years. That's not a middle management function - it's an executive function.
What You Can Actually Control (And What to Focus On)
Here's where the conversation shifts from honest assessment to practical action.
Because accepting what you can't control isn't giving up - it's freeing yourself to focus on what actually moves the needle.
Control Zone 1: Your Team's Culture
You can't fix the organizational culture. You can build a different culture within your team.
What this looks like in practice:
Create psychological safety:
Even if the organization around you is blame-focused and punitive, your team can operate differently. When mistakes happen in your team, address them developmentally. When people take intelligent risks that don't pan out, they treat failure as learning.
Your team will notice the difference. They'll see that your team operates differently from others. That's not trivial - it affects retention, performance, and engagement.
Set a communication standard:
Even if organizational communication is poor, your team can have excellent communication. Weekly team meetings where people know what's happening. 1-on-1s where engineers can raise concerns. Transparency about what you know, what you don't know, and what you're trying to find out.
When leadership makes decisions that affect your team and communicates them poorly, you can be the translation layer that converts organizational noise into team clarity.
Protect development time:
Even when organizational pressure is constant and urgent, you can fight to protect some time for learning, professional development, and certification preparation. Your team will notice when you fight for this.
Building a team culture that differs from organizational culture connects to Changing Culture as a New Manager - you have more influence over your team's culture than the broader organization's.
Control Zone 2: The Buffer Between Team and Dysfunction
Your most important function in a dysfunctional organization isn't fixing the dysfunction - it's buffering your team from its worst effects.
What this looks like:
Absorb priority chaos:
When leadership changes direction for the third time this quarter, your team shouldn't feel the full impact of that whiplash. Your job is to absorb some of that chaos, stabilize the situation, and communicate change in a way that maintains focus and morale.
This doesn't mean lying about what's happening.
It means: "Leadership has shifted direction. Here's what we know, here's what we're doing, here's what stays the same for now."
Not: "Leadership has no idea what they're doing and we're all just along for the ride."
Even when the latter is what you're thinking.
Translate dysfunction into a workable direction:
Vague, contradictory, or poorly communicated organizational direction lands on your desk. Your job is to make it actionable for your team.
"The organizational mandate is unclear, but here's what I understand us to be responsible for. Here's how I'm interpreting this for our work. If I'm wrong about the interpretation, I'd rather find out through my conversation with leadership than have the whole team operating on bad assumptions."
Shield from interpersonal and political toxicity:
If there's conflict between departments, if other managers are difficult, if leadership dynamics are unhealthy - your team should see as little of that as possible.
You handle the external dysfunction. They focus on the work.
Control Zone 3: Documenting Risk You Can't Fix
When you can't fix a problem, the next best thing is documenting it clearly.
Why this matters:
For the organization:
Sometimes documentation builds a case over time. The third risk memo about aging infrastructure carries more weight than the first. Leadership might not act on the first warning, but a documented pattern creates organizational memory.
For your team:
When you've told your team, "we've flagged this risk to leadership and here's their response," they understand you're aware of the problem and fighting for them. You're not ignoring the issue - you're dealing with an organizational constraint.
For yourself:
When aging infrastructure eventually fails - and it will - your documentation shows you raised this. The failure isn't a surprise you didn't see coming. You predicted it, documented it, and were overruled.
What effective risk documentation looks like:
"Current network switches in [environment] are 7 years old and approaching end-of-life. Based on typical failure rates for equipment at this lifecycle stage, the risk of failure increases significantly after year 5. We have flagged this for budget consideration in FY2024 and FY2025. The budget was not allocated. The risk of service disruption is increasing. Recommend [specific action] at a cost of [specific amount]. Without this investment, we anticipate [specific consequences] within [timeframe]."
File it. Send it. Follow up. Document the response.
It won't always get you the resources, but it creates accountability for the decision.
Control Zone 4: Picking Your Battles Strategically
You have limited political capital. Spend it wisely.
The mistake early managers make:
Fighting everything that's wrong. Every bad decision, every dysfunctional process, every organizational problem.
The result:
Burning political capital on battles you can't win, leaving nothing for battles you can.
What I learned across multiple organizations:
Some battles are worth fighting:
Your team's headcount and resources
Recognition and compensation for your team members
Protecting your team from genuinely unreasonable demands
Technical decisions where your expertise makes you right and the stakes are high
Ethical issues (non-negotiable - always worth fighting)
Some battles aren't worth fighting:
Organizational processes you can work around
Decisions that are bad but won't meaningfully harm your team
Political dynamics that exist above your level
Initiatives you disagree with philosophically but that won't cause real damage
The calculus:
Stakes × Probability of winning × Cost of fighting = Whether to spend capital
Low stakes + low probability of winning + high cost = Let it go.
High stakes + reasonable probability + manageable cost = Fight it.
Control Zone 5: Creating Upward Pressure Without Career Suicide
You can't fix dysfunction from the middle, but you can create sustained upward pressure that contributes to change over time.
The approach that works:
Frame issues in business terms, not frustration:
"Our current infrastructure refresh cycle is creating increasing operational risk. Based on current failure rates, I estimate [specific business impact] within [timeframe] if we don't address this. I wanted to make sure leadership has this information when making budget decisions."
Not: "I've told you three times we need new switches and you keep ignoring me."
Build allies:
Other managers probably see the same dysfunction. If three managers raise the same issue with data, it carries more weight than if one manager raises it repeatedly.
Find the escalation path that doesn't put you at risk:
Sometimes there are formal channels (skip-level meetings, employee surveys, HR processes) that create accountability without requiring you to make yourself a target.
Accept that you're planting seeds, not harvesting immediately:
Sometimes the impact of your advocacy doesn't show up until after you've moved on. That's okay. You're contributing to organizational improvement even if you don't see the direct payoff.
"Building effective upward pressure connects to Managing Up as a Technical Manager - advocating for your team within organizational constraints
The Emotional Reality of Working in Dysfunction
Let's talk about something most management content avoids:
Working within organizational dysfunction is emotionally taxing in ways that are hard to explain to people who haven't experienced it.
The Helplessness You Have to Manage
There's something uniquely draining about seeing problems clearly, knowing the solutions, having the data, and advocating correctly - and still watching the wrong decisions get made.
This is the experience of middle management in dysfunctional organizations.
You're not helpless - you can do the things outlined above. But you're limited in ways that are frustrating when you care about doing good work and creating good environments for your team.
What helps:
Accepting early that perfection is not available. The goal isn't fixing the organization. The goal is to do the best possible work within the constraints.
The engineers on your team who came up through technical roles? They're used to problems having solutions. This is one of the adjustments to management that nobody openly talks about: some problems don't get solved; they get managed indefinitely.
The Communication Burden
You can't share everything with your team.
Organizational decisions being made above your level, leadership dynamics you're navigating, political situations you're managing - these stay with you.
You can't share everything with leadership.
Team frustrations, concerns about organizational direction, the specific ways dysfunction is affecting morale - these require careful translation to avoid creating problems.
You're processing information from multiple directions with limited ability to offload it anywhere.
This is the isolation of middle management. It doesn't go away. You learn to manage it by:
Building a peer network outside your organization (other managers who understand the experience)
Finding appropriate outlets that don't compromise organizational relationships
Accepting that carrying some of this is part of the role
Knowing When Dysfunction Becomes Untenable
Here's the question that eventually comes for every manager who's been in a dysfunctional organization:
When do you stop managing the dysfunction and start making a career decision?
Signs it's become untenable:
Your team is genuinely suffering:
Not just frustrated with organizational realities (everyone deals with that) - but experiencing real harm. Burnout. Psychological unsafety. Career stagnation because the organization won't invest in development. Compensation that's genuinely below market.
If you can no longer buffer your team from dysfunction because this is too pervasive, that's a serious signal.
The dysfunction requires you to compromise your integrity:
Being asked to implement decisions you believe are unethical, mislead your team, or cover for bad organizational behavior - this is categorically different from working within constraints you disagree with.
You've stopped growing:
Some organizations are so dysfunctional that the environment prevents professional development. If you're stagnating because organizational problems consume all your energy, that affects your career trajectory.
Your advocacy has no effect over time:
You've repeatedly raised issues through appropriate channels, with appropriate framing and evidence. Nothing changes. Not a battle here and there - systemic inability to drive any improvement.
What to do with these signals:
They don't necessarily mean leave immediately. Context matters. Sometimes you're in the right role at the wrong time - a leadership change, a business cycle shift, or organizational evolution might address root causes.
But they're worth taking seriously. Managers who stay indefinitely in dysfunctional organizations without making conscious choices about it tend to normalize dysfunction, which isn't good for their teams or their own careers.
What Changes When You Accept What You Can't Control
There's a reason the Serenity Prayer is famous. The concept it captures is genuinely useful:
Accepting what you can't change.Courage to change what you can.Wisdom to know the difference.
For middle managers in dysfunctional organizations:
Before acceptance:
You're fighting everything. Spending energy on battles you can't win. Frustrated that the organization won't respond to your advocacy. Carrying the weight of organizational problems as if they're your personal failures.
After acceptance:
You're strategic. You focus on your sphere of actual influence. You document what you can't fix. You fight battles that matter and let go of battles you can't win. You protect your energy for the people and problems you can actually affect.
This isn't a resignation. It's efficiency.
The engineers on your team? They feel the difference. A manager who's constantly fighting organizational windmills is distracted and depleted. A manager who's accepted organizational realities and focused on controllable factors is present and effective.
Your most valuable asset as a middle manager in a dysfunctional organization isn't the ability to fix the dysfunction.
It's the ability to create a good team environment despite it.
The Bottom Line: Clarity Over False Hope
After almost 25 years in IT, across organizations large and small, functional and dysfunctional, here's what experience has taught about organizational dysfunction and middle management:
You cannot fix systemic dysfunction from the middle. Root causes live above your authority level. The tools available to you are insufficient for the scale of the problem.
You can significantly influence your team's experience. Culture within your team, how dysfunction is communicated, how your team is buffered from the worst effects - these are real levers that matter enormously.
Document what you can't fix. Risk memos, budget requests, and documented advocacy - these create accountability for decisions above your level and protect you when the predicted problems materialize.
Pick battles strategically. Limited political capital spent on winnable battles with high stakes. Don't burn resources on battles you can't win.
Create upward pressure through appropriate channels without making yourself a target. Frame business impact, build allies, use formal channels.
Recognize when dysfunction becomes untenable. Team harm, integrity compromise, career stagnation, zero impact from sustained advocacy - these are signals worth taking seriously.
Accept what you can't control. Not as giving up - as gaining clarity about where your energy actually moves the needle.
The organizations I've learned the most from weren't the most functional ones.
They were the ones where I had to figure out how to do good work, support good people, and maintain integrity within systems that weren't designed to make any of that easy.
That's the real curriculum of middle management.
Nobody teaches it directly. You learn it by living it.
And once you understand what you can and can't control, you become a significantly better manager - not because the dysfunction goes away, but because you stop letting it consume you.
Your team needs you to be present and effective. Not depleted from fighting battles that were never yours to win.
Focus on your team. Document your advocacy. Accept your limits. Pick your battles.
That's the job.
📧 Navigating the realities of middle management in complex organizations? Subscribe to my monthly newsletter for honest perspectives on what middle management actually looks like, what you can and can't control, and how to protect your team and your sanity while doing it. First Tuesday of every month. Sign up here
What's your experience with organizational dysfunction from the middle management seat? What have you found you can actually influence vs. what you've had to accept? Share your experiences in the comments or connect with me on LinkedIn - this is one of those topics where we all learn from each other's stories.
Disclaimer: The observations in this blog are drawn from patterns across multiple organizations and career experiences spanning almost 25 years in IT and networking. They do not reflect any specific current employer, team, or individual. Organizational dynamics vary significantly, and not all organizations exhibit the patterns described here.