Think about how a single hurt travels through a person. Someone is treated badly on a Tuesday — dismissed in a meeting, blamed for a decision that was never theirs, handed a consequence out of all proportion to the mistake. They absorb it. There is no room to say what happened, no one to say it to, no way to set it down. So it stays in the body, and it looks for an exit. By Thursday it has found one. A quieter colleague catches a sharpness that had nothing to do with them. The hurt did not disappear. It moved. It got passed on rather than worked through, because passing it on was the only channel left open.
This is an old and ordinary human mechanism, and most people recognize it the moment it is named. What gets noticed far less often is that organizations do exactly the same thing — at scale, and usually without anyone intending it.
A team is also a body that absorbs shocks
An organization takes hits. A reorganization lands badly. A major account walks. A respected leader leaves and takes half the institutional memory with them. A quarter comes in short and the pressure arrives from above like weather. These are shocks to a system, and a healthy team has ways to process them — honest conversation, a leader who names what happened, enough slack in the schedule to absorb the blow and recover before the next one lands.
When those ways are missing, the shock does what an unprocessed hurt always does. It does not vanish. It travels. A manager who was handed an impossible target, and given no space to push back on it, passes the impossibility straight down to their team as an impossible deadline. A team that was blindsided by a decision made three levels up passes the same blindsiding to the people they work with, because that is now simply how information moves here. Strain that cannot be metabolized at the top gets exported downward and outward, one layer at a time, until it reaches the people with the least power to send it anywhere else. There, it finally settles — and hardens into culture.
The tell is a sentence you have almost certainly heard inside a struggling organization: that's just how things are here. It is worth pausing on, because it is doing a lot of quiet work. It takes a specific injury — a specific moment when a shock was passed on instead of worked through — and launders it into a permanent feature of the landscape, as though no one made it and no one could unmake it. Almost every dysfunction that gets described this way started as a single unprocessed shock that no one had the room, the safety, or the standing to interrupt. Repeated enough times, transmission becomes tradition.
The interruption is a leadership act
Here is the part that matters, and it is genuinely good news: the cycle is interruptible. It is not a moral flaw baked into certain people, and it is not a weather system that leaders simply endure. It is a pattern of transmission, and a pattern can be broken at any point along its path. The person who breaks it is usually not the one who first absorbed the shock. It is whoever notices the strain arriving and decides not to pass it on.
That decision is the whole thing, and it is smaller and more concrete than it sounds. A manager gets a punishing target from above and, instead of relaying the pressure verbatim, does the harder work of absorbing what can be absorbed, being honest with the team about what is real, and pushing back up the chain on what is genuinely unworkable. A leader whose own week has been brutal chooses not to let that brutality set the temperature of every conversation they walk into. None of this is softness. It takes more composure to hold a shock and metabolize it than to hand it to the next person down. The leaders who do it are not being kind at the expense of results. They are refusing to let a bad week become a bad culture.
When the deadline stopped rolling downhill
An operations group inside a mid-sized logistics company had a reputation for being tense in a way no one could quite explain. Deadlines always seemed to land as emergencies. People were competent and worked hard, yet something in the group ran hot, and turnover among the newer staff was quietly climbing.
Traced back, the pattern was almost mechanical. Commitments were made to clients at the top without a real check on capacity. Those commitments arrived at the group's director as fixed and already promised. The director, with no room to renegotiate, passed them to the team leads as urgent. The team leads, with no room of their own, passed them to the floor as crises. By the time a deadline reached the people who had to meet it, every ounce of the original overreach had been converted into stress and dropped on the people least able to send it anywhere else. Each layer had done the only thing the layer above had left it room to do.
The fix was a single decision, made at the right point in the chain. One person — the director — stopped being a clean conduit for pressure. She began pushing back on commitments before they were promised, giving her team leads honest capacity numbers instead of relayed panic, and telling the floor the truth about what was real and what was negotiable. The pressure did not disappear; some of it was genuine and stayed. But it stopped compounding as it fell, because one person in the middle of the cascade chose to absorb what she could and refuse to forward the rest. The heat came out of the group within a quarter. Nothing about the work had changed. What changed was that one link stopped passing the hurt along.
That is the entire lesson, and it scales in both directions. A hurt travels through a person until someone chooses to set it down instead of hand it on. Dysfunction travels through an organization the same way, along the same logic, until a leader does the same thing. The cycle is real. It is also, at every single point along its path, interruptible — and interrupting it is one of the plainest, least sentimental things a leader is actually there to do.