A manager told me she felt like a cushion. The word is well chosen. People in that position reach for it instinctively: something that absorbs, separates, protects surfaces from direct contact. It takes the tension coming from above, from leadership, ownership, the organization's decisions, and the tension rising from below, from the team with its needs, resistances, and individual weight. The cushion sits in the middle and compresses.

This is not an isolated experience. It's one of the most widespread and least named dynamics in middle management. Nobody describes it when you start the role. It doesn't appear in the job description. You find it there, day after day, and gradually understand that it's part of the work. The question isn't how to eliminate it. It's knowing when absorbing still makes sense, and when it stops being functional and becomes something that accumulates without ever discharging.

Not all filtering is the same.

There's a filter that makes sense, and has real value: when a manager carries a challenge upward with an authority the team wouldn't have alone, seniority, knowledge of procedure, a broader view of context. In those cases, acting as a filter isn't a surrender of the team's autonomy. It's an act of intelligent protection. A team member contesting a request from commercial leadership carries different weight than the manager doing the same thing. Ignoring that asymmetry isn't democratic. It's just naive.

Then there's the filter that costs: the one that absorbs everything, always, to avoid loading the team, to prevent conflict, to keep a system in balance that would otherwise wobble. This kind of absorption has a sustainability limit, and that limit arrives faster than expected. Pressure doesn't disappear because it's retained. It accumulates.

The deeper question is harder than how to manage individual situations.

A team that has never faced external pressure directly, never learned to negotiate upward, never managed its own errors without a buffer, is fragile, not protected.

It depends on a single node. And when that node isn't there, the system doesn't hold.

Leaving space for autonomy isn't abandoning the team. It's building resilience. It means accepting a margin of error as a necessary part of development, defining clearly which situations belong to the manager and which the team can and should handle independently, even when that means exposure, mistakes, learning. The shift from cushion-manager to team-architect is gradual: not "I'll resolve it" but "let's build the conditions under which you can."

One of the most concrete things a manager can do, and often the most neglected, is making their own position visible to the team. Not to complain, not to move the weight downward, but to create a real bidirectional flow of information: helping people understand that constraints exist, pressures exist, non-negotiable decisions exist that don't depend on the manager's will, and at the same time opening the space to hear what the team can contribute, where it can intervene, where it can share some of what's arriving.

This changes the dynamic. The manager stops being the only load-bearing point. The team starts becoming an active part of the system.

That's a different kind of cushion: distributed, shared, and considerably harder to wear out.