What Happens When Leaders Hide Their Stress

"How do I not pass my stress onto my team?"

That question came from a project manager in a workshop I ran last week in Amsterdam. I could feel the room lean in. Not because it was a new question, but because everyone in that room had been living inside it.

I want to tell you what I said, what I didn't say, and what happened when I asked this question publicly afterward, because the answer that came back was not what I expected, and it changed the question itself.

But first, let me be honest about what brought me into that room.

The Work Before the Work.

The day before the workshop, I got stressed. I had two hours, too much material, and a nagging voice telling me I needed to prove something. I noticed the impact on my body: tight shoulders, faster thinking, a slight irritability around the edges.

I call that Explore - noticing what is real before you try to fix it.

I then got creative about what I could realistically do in two hours. I cut. I improvised. I trusted the room to co-create rather than expecting myself to deliver everything.

I call that Play — working within constraint rather than fighting it.

The morning of the workshop, I went to a park near the venue. Under the shade of a large tree in central Amsterdam, I sat down to have my breakfast. I was physically and mentally preparing for the session. For me, nature and nurture go together.

I was near a school. I watched the children arrive on their bikes. There was a sense of excitement and openness about them, and I found that same energy when I entered the room to run the workshop.

There is something about being in person, in nature, and in a beautiful workshop space that creates a welcoming environment. A space to receive stress rather than fight it. The wider system: the culture, the setting, the unspoken rules about what can and cannot be said: was designed to hold stress rather than deny it. When I say "system," I mean everything around the individual that shapes what feels possible: the team norms, the leadership expectations, the physical space, the permission structure.

I was kind to myself about the gap between what I wanted to deliver and what was possible. I didn't berate myself for being stressed the day before. That self-criticism is what your team mirrors.

I call that Love — refusing to make stress a character failure.

I arrived early. I greeted people as they came in. I let them see me — not as a polished facilitator, but as someone who had been working with pressure the day before and was choosing to be here, fully, now.

I call that Connection — meeting people from where you actually are, not from where you think you should be.

And all of it was in service of Presence — the ability to be with the situation as it is, not as you wish it were.

What the Workshop Surfaced

So before the session, I asked the group what was causing them stress, because if I was going to be visible, I wanted them to be too. The answers were familiar: deadlines, ambiguity, stakeholders, under-resourcing, the gap between what is expected and what is possible.

But the question that stopped the room was the one I opened with:

"How do I not pass my stress onto my team?"

I understood the instinct behind it. It comes from care. It sounds like trying to be a good parent, the protective leader who absorbs everything so the team does not have to. In the leadership 360 assessment I use, this is called the reactive mindset: the hero or heroine who carries the weight so others do not feel it.

Here is what I can tell you about that mindset.

When you absorb stress silently and project calm, your team does not actually relax. They attune. They begin operating in a field of unspoken tension, by "field," I mean the emotional atmosphere that fills a room before anyone speaks, the invisible climate that every person senses and responds to, even if no one names it. They mirror your "everything is fine" while their nervous systems register the micro-signals that contradict it, the tightness in your jaw, the absence of your usual humor, the slightly faster pace of decisions.

The pretense becomes the new pressure. And nobody gets to actually work with what is real.

What Happened When I Asked This Publicly

I shared that moment on LinkedIn expecting a few nods. What came back was different. People who had been living this exact tension showed up — not to agree, but to complete the thinking. New language arrived. Sharper edges. And in naming it together, something shifted in how the whole thing could be understood.

This is what learning in action looks like. Not one person figuring it out and distributing answers, but enough of us willing to ask publicly and humble enough to let the answers reshape us.

The Gap That Actually Matters

Karen Thomas-Bland arrived with surgical precision:

There it is. The pivot point.

Benjamin P. Taylor named what lives underneath the pretense:

The team knows. The field knows. You know. The only question is whether the stress becomes discussable something the system can respond to, or remains a performance that everyone maintains at their own cost.

The Vulnerability Trap

But here is the harder edge.

Dr. Keith Amoss offered this:

True. But there is a trap in the middle distance.

Opening up without having done your own work with the stress is just asking your team to hold your overwhelm. That is not vulnerability. That is offloading with permission. And it leaves the team in a worse position than silence did, because now they feel responsible for your emotional state on top of everything else.

When Reactive Becomes Creative

Paul Sherwood named something subtle: managers get stuck in reactive mode "as a means to align to their own script / identity and beliefs." You have been the strong one for so long that admitting the field has shifted feels like identity death.

This is why the transition from reactive to creative is not just a technique. It is a shift in who you believe you are allowed to be. The leader who carries everything is not just a role — it is a self-image. And self-images do not surrender quietly.

The field offered the way through: self-love and compassion allow you to see and let go of limiting beliefs. And the system needs to help with that as well. Not just you, alone, trying harder to be unshakeable. The whole culture. The permission structure itself has to shift.

This is where leadership development often fails. It tells the individual leader to change, while leaving the organizational expectation untouched. The leader is told to be vulnerable in a system that still punishes vulnerability. That is not a development plan. That is a trap.

What This Looks Like on Tuesday Morning

Dan Leyland offered something grounded:

Not hiding. Not dumping. Naming. And then modeling what comes next.

So what does that actually look like in practice? Here is what the five elements look like when a leader applies them in a real moment:

These are not steps. In practice they overlap, collapse into each other, and show up in different orders depending on the moment. The table describes what each element looks like, not the order in which to apply them.

Your resilience becomes teachable. Not because you are lecturing about it, but because your team is watching you work with pressure in real time.

The More Radical Possibility

There is an assumption buried in all of this that deserves examination: that the leader's job is to metabolize stress individually before bringing it to the team.

That is partially right. You should not bring unprocessed overwhelm into the room. But Dan Leyland's contribution gestures at something deeper, that the team can learn that "sometimes things don't go the way you'd like, and that what's more important is what comes next."

This suggests that sometimes the team should see the leader mid-process, not just post-process.

Not dumping. Not hiding. But saying:

That is a different kind of modeling, not of resilience as a finished product, but of resilience as a live, messy, collaborative process. The leader is not the one who has arrived at calm. The leader is the one who is practicing out loud, and inviting the team to practice alongside them.

This is not a license to bring unprocessed chaos into every meeting. It requires judgment about what your team can hold and what the culture permits. But the principle stands: sometimes the most powerful thing a leader can model is not the answer, but the practice of working with the question.

When you do this, something unexpected happens. Permission ripples. Your team begins to metabolize their own stress differently. The whole system shifts — not because you fixed it, but because you stopped pretending the stress was yours alone to carry.

The Simplicity

Jan Brause saw it with beautiful clarity:

That is the whole thing. Not systems. Not frameworks. But the actual field that emerges when one person stops performing and starts being.

The Reframed Question

I walked into that workshop asking, on behalf of a project manager:

"How do I not pass my stress onto my team?"

The field reshaped it into something deeper:

Not: How do I hide it?

Not: How do I dump it?

But: How do I work with it so thoroughly that I am no longer trapped in it?

And the answer lives in five practices that are not a framework but a way of being:

• Explore what is real.
• Play creatively within it.
• Love yourself through it.
• Connect with others from authenticity.
• Stay present to what is actually happening.

What Still Needs Asking

I did not figure this out alone and then teach it. The wisdom only became wisdom when it met reality — when Karen, Benjamin, Keith, Paul, Dan, and Jan added their edges to it and sent it back transformed. That is still happening. The field is still learning. It learns fastest when we are willing to ask out loud.

So the question remains:

The pretense dies. Something more honest grows in its place.

If you have thought about this, if you have felt the gap between hiding and dumping, if you have noticed what happens when a leader stops performing and starts being present, the field is still learning. It learns fastest when we ask out loud.