Squeezed From Both Sides: Why Strategy Stalls in Your Middle Managers

Your leadership team spent two days offsite and came out with three clear priorities. You communicated them well. You held an all-hands, sent a follow-up email, and shared a slide everyone has seen more than once. Six weeks later, you walk through the work, and it looks exactly like it did before the offsite. When you ask the managers in the middle how the rollout is going, they tell you it is going fine.

It is not going fine.

What is happening is something I see in almost every organization once it grows past a few dozen people: the layer between strategy and execution has quietly become a compression zone. Your middle managers are absorbing the distance between what leadership announced and what their teams can actually take on. And they are absorbing it in silence, because absorbing things quietly is very often the behavior that got them promoted in the first place.

This is rarely a competence problem, and it is rarely a communication problem in the way senior leaders assume. It is a load problem, and it has a specific address.

Start by diagnosing what you handed down, not how you said it

When a priority stalls in the middle, the first instinct is almost always to say it again, louder and clearer. That is rarely the issue. The first move in the Rawe Applied Leadership Framework is diagnostic, and it asks a sharper question: what did I actually hand this manager, and what did I hand them alongside it?

In my experience, the answer lands in one of three places.

• Direction without decision rights. The manager is asked to change how their team works, but cannot change the metrics they are measured on, the headcount they have, or the deadlines already promised to a customer.

• Direction without subtraction. Something new was added, and nothing was removed, so the manager becomes the shock absorber. They attempt both, protect their team from the strain, and pay for it with their own evenings.

• Direction without translation. The priority made complete sense at executive altitude, but nobody ever converted it into what Tuesday morning looks like for a team of nine with an existing queue.

All three produce the same visible symptom, which is that nothing changed. All three require a different fix. If you cannot name which one you are looking at, another all-hands is not going to help, and your managers already know that.

Change the habit that rewards the middle for staying quiet

The second move puts the first behavior change on you, which leaders tend to resist. Here, the habit to retire is treating a manager's silence as agreement.

Think about what you are actually asking when you finish a rollout meeting with "any concerns?" You are asking a mid-level manager, in front of their peers and their boss, to be the one person in the room who says the plan will not work. The manager who answers honestly looks like the manager who is not on board. The manager who says it is fine looks like a team player. So they say it is fine, walk back to their desk, and absorb the difference.

There are two practical shifts. The first is to stop asking whether they have concerns and start asking what this costs. "If we take this on, what stops, slows down, or slips?" That question makes naming the trade-off the expected answer, not the brave one. The second shift matters more: respond to the answer. The first time a manager names a real cost and you visibly remove something, you teach that entire layer that candor is safe. The first time you thank them warmly for the honesty and change nothing, you teach the opposite, and they will only need to learn it once.

Put the trade-off conversation into the rhythm you already run

The third move is where good intentions usually go to die. The instinct is to build something new for it, such as a monthly manager roundtable or a fresh round of skip-levels. That instinct adds meetings to the calendars of the people who are already the most overloaded, and within a quarter the new forum is quietly canceled, and the original problem is still sitting there.

Attach it instead to a rhythm that already exists. Your staff meeting, the monthly business review, whatever recurring session already carries operational decisions. Add one standing item: what did we add this month, and what came off the list to make room? Five minutes is enough. The point is not the list. The point is that your organization now has a routine, expected place where subtraction happens on purpose, rather than being left to whoever is most willing to work the weekend.

Two things make that stick. Give every subtraction a name and a date, the same way you would for anything you add. "We are pausing the vendor review until January" is a decision that a manager can carry back to their team; "we'll deprioritize some things" is not. And make the subtraction visible across the layer, so managers can see the trade-off was made at your level, not quietly swallowed at theirs.

What changes when the middle stops absorbing

When leaders make these three moves, strategy starts reaching the frontline with its edges intact. You hear about capacity problems in week two instead of month five, which is the difference between an adjustment and a recovery. Your managers stop protecting you from information, which is a form of protection nobody actually wants. And retention in that layer improves, which matters more than most executives account for, because middle managers are simultaneously the most expensive people to replace and the hardest to backfill from outside.

That is the whole logic of the Rawe Applied Leadership Framework: diagnose what is actually creating the gap, change the leadership behavior before asking anyone else to change theirs, and build the new practice into the rhythm your team already runs on instead of stacking another initiative on top of an overloaded organization.

If your priorities are clear, your managers are capable, and the work on the ground still is not moving, that gap is worth a real look rather than another round of communication. I work with leaders and leadership teams to find where strategy is getting absorbed instead of executed, and to rebuild the middle into a layer that can carry it. If that sounds like what is happening in your organization, reach out and let's talk about it.