Every leader sits between pressure and the people doing the work. It originates above you: a board that wants growth, a CEO who has just read something about AI, a quarter of missed targets. That pressure has to go somewhere, and what you do with it is a choice most leaders make without ever really thinking about it.
There are two paths that pressure can take, and that one of them is almost always the wrong one
The umbrella
The umbrella leader absorbs and deflects pressure so the team doesn't have to. A designer working under one gets to explore properly, take risks, show work early and be wrong in public without it costing anything. That is what psychological safety is made of. Not a workshop or a values slide, but someone senior standing between the team and the exec, taking the hits.
It is the right default. Ambitious work doesn't happen in a team that spends its energy managing the mood of the people above it.
It is also tiring, and it has a cost the team can't see. A leader who absorbs everything has a limited lifespan, at which point the shielding stops working. An umbrella can deflect the pressure, but eventually the pressure will win out. The question is how long it survives.
The downpipe
The downpipe leader lets pressure flow through. The LT is anxious, so the VP is anxious, so the director is anxious, so the designer is anxious. Nothing is deflected, and often it is amplified, because each layer adds its own reading of what it means for them.
Downpipes tend to describe themselves as transparent, and some of that is true. Treating people as adults is right. But information tells people what is happening, and pressure tells them to be afraid of it. The downpipe delivers both without separating them, which is the actual job. It is also the path of least effort. It needs no judgment, only a Slack message. And it’s a convenient way to make sure failures belong to someone below you which is a salve for a leader lacking the ability to turn that pressure into something more productive.
Choosing on purpose
Being the umbrella doesn't mean shielding the team from everything. Some pressure is information they need to do their work: the company is missing a business target, a given project is a big bet, a competitor has launched a competing feature, etc.
A team kept entirely in the dark loses its calibration, because it is working against a filtered version of reality. So part of the job is deciding what comes through, and sending it as information rather than the way the information makes you feel. "We have six weeks to move retention" is something a team can design against. "Leadership is really worried" is not.
It also means sometimes letting people choose their own exposure. A designer who asks to take the exec review, or to own the call on a contested implementation is asking for that pressure knowing it might well serve them - that development comes from these opportunities.
That is lowering the umbrella, not becoming a drainpipe


