PRESSURE PATTERN #4 Inherited WeightOn the problem you believe you can see but can't fix, the decision you must announce without full context, and the difference between making the call and leading through one you didn't make. Pressure: Seeing the problem clearly isn’t the same as being authorized to fix it.Most leaders operate inside systems they didn’t design and execute decisions they didn’t make. That is the condition of leadership. I lived a version of this. Years ago, a product strategy decision came down from above me, and I learned about it only days before my team did. It cut against the thing we had built our identity around, an obsession with delivering value for customers, and I hadn’t been read into the reasoning yet. I handled the public-facing communication, including media interviews, so I held the official line. Meanwhile, inside the building, the why questions were mounting, and they were coming to me. The sentence I most wanted to say, “I don’t fully understand this either,” felt off limits. Saying it seemed to point a finger up the chain, and owning the message was one of our own stated values. The trap closed from both sides. That is inherited weight. Not just a failure you can see and can’t fix. A load you didn’t choose that you still have to hold up in public. Pattern: When the problem is above your reach, the gap between what you can see and what you can change becomes its own leadership challenge.The cost arrives in two forms. The familiar one is passivity: the leader conflates “I can’t change the call” with “I can’t act.” The subtler one is performance: the leader acts, but as a spokesperson, delivering conviction they don’t hold. Teams detect the difference quickly. Few things erode trust faster than a leader saying words that don’t sound like their own. Authority over the decision and agency to act are different things. Under inherited weight, most of your agency lives in what you say and to whom. The response that holds up is constructive transparency: say what you know, say what you don’t, name who holds the conviction and that you will go get their reasoning, then ask the team to commit to each other and to what you can control. You might be missing something, too. The decision above you may rest on context you can’t see: portfolio logic, financial pressure, constraints that can’t be announced yet. Part of the discipline is holding your read loosely enough to go ask, instead of issuing a private verdict and leading from resentment. It changes what you say: you ask for the reasoning as a partner, not as someone who has already ruled. When I finally stood in front of my product and engineering teams, that is what I did. I didn’t fake conviction. I told them the decision was made, that I had learned of it recently, that the leaders who made it held real conviction, and that I would go get more context and share it as I learned it. In the end, the launch was a mixed success. Some never agreed it was the right call. But the team that came out the other side was stronger than the one that went in, and the bond didn’t come from agreement. It came from the delivery: risks named, mitigations made, real effort put in, and trust earned before the why ever fully arrived. Shift: Where am I waiting for authority I don’t hold, instead of using the agency I do?One question to carry this week: where have you performed conviction you don’t hold, and what did it cost the last time your team could tell the difference? If this one landed, the full piece goes deeper: the four ways leaders respond to inherited weight and what each one costs, and inside the one that holds, the three moves for carrying it: insulation, translation, and constrained action. Plus the account of how it actually played out for me. Read the full version. This pattern is part of the library of leadership content at Resonant Vector published by Mark Benson with the goal of helping leaders and teams thrive under pressure. |
Clear thinking for leaders and teams navigating constant pressure, complexity, and change.