Agile Without Psychological Safety Is Just Theater

Team issues, Toxic Culture?

Jun 21, 2025

Welcome to the Agile Admiral weekly newsletter. Your Essential Resource for Project Management Excellence.

Each week, I tackle reader questions about PMP preparation, how to implement PMP into real-life projects, and a Senior Project Manager career.

What's Inside This Edition:

A typical day in the life of a Project Manager
Agile Without Psychological Safety Is Just Theater
How PMs shield their teams from toxic cultures?

Join 700 PMs who passed PMP in 8 weeks

Agile Without Psychological Safety Is Just Theater

by William Meller → Project Management Compass

We talk a lot about process, but we rarely talk about the conditions that make a process actually work. Agile is a great example of this.

It sounds simple on paper: short feedback loops, small teams, working software, regular reflection.

But most frameworks, by default, assume something fragile underneath: trust.

And that’s the part most teams don’t really have.

Trust is invisible until it breaks. And once it does, all the rituals in the world won’t save the process. The standups feel forced. The retros become quiet. The planning meetings drag.

Progress slows, not because people are lazy or confused, but because the system is now running on low psychological safety.

Agile frameworks don’t mention this explicitly. They talk about collaboration, adaptation, and self-organization, but they quietly assume that the people involved are willing to speak up, take risks, admit when something isn’t working.

That requires trust. Without it, what’s left is theater.

You can see it most clearly in retrospectives. The space that’s supposed to be open, honest, even a bit uncomfortable. But in many teams, it turns into a polite loop. People mention small, safe issues. Things like "better ticket grooming" or "more focus time."

The deeper problems never surface. The cross-team tension. The product decisions that didn’t make sense. The meetings that waste time. The lack of support. It’s not that people don’t see these issues. They do. But they’ve learned that bringing them up doesn’t change anything, or worse, it creates friction. So they stay quiet. Smile. Post a thumbs-up emoji. Move to the next sprint.

This is not an Agile problem. It’s a culture problem that Agile quietly depends on.

Real collaboration requires friction. Not the aggressive kind, but the honest kind. The kind where someone can say, “I don’t think this plan is going to work,” or “We’ve been carrying the same blockers for weeks and no one is fixing them.” That level of honesty is uncomfortable, especially in environments where conflict is seen as disloyal or negative.

But without it, you can’t adapt. You can’t inspect and improve. You can only go through the motions. I’ve seen teams with perfect velocity metrics who were completely stuck. Everything looked fine on the dashboard, but nobody was asking hard questions anymore. Trust had been replaced with performance. People were doing their part, closing their tickets, attending their meetings. But the learning had stopped. And without learning, Agile is just a loop of movement without progress.

The tricky thing is that trust doesn’t come from big declarations. It comes from small signals over time. A leader who listens without interrupting. A team member who admits a mistake and isn’t punished for it. A retrospective where feedback leads to a real change. These moments charge what you could call the team’s “trust battery.”

When the battery is full, people speak up early. They challenge decisions. They surface risks before they grow. But when the battery is low, everyone waits. Feedback arrives too late. Problems pile up silently. And by the time they explode, the sprint is already lost. Agile doesn’t fail because of story points or Scrum boards. It fails because the system around it refuses to support the human conditions it needs to work.

And this is where leaders often miss the mark. They optimize the process, not the environment. They try to fix delivery with new roles or better tools, instead of fixing the way decisions are made, or how people are heard. But process doesn’t replace trust. It can only help when trust is already there.

So what does this mean in practice?

It means that if your retrospectives feel shallow, the issue isn’t the questions, it’s the safety. If your standups are stiff, it’s probably not the format, it’s that people don’t feel they can be honest. If your sprint reviews are full of polite nodding and no real feedback, you don’t need better stakeholders. You need more openness.

The hard truth is that most companies want Agile results without Agile conditions. They want speed without mess. Autonomy without disagreement. Feedback without discomfort. But the reality is that good teams don’t just follow the Agile playbook. They trust each other enough to challenge it when it stops serving the work. So before your next sprint planning or retrospective, ask yourself something simple.

Can the people in this room say what they really think?

Can they disagree with the plan?

Can they bring up a risk that’s not on the board?

If not, then you’re not working in an Agile team. You’re performing the rituals of one, hoping that trust will appear on its own.

It won’t. But you can build it.

Slowly. Intentionally. Conversation by conversation.

Because Agile without trust isn’t Agile. It’s just a nice name for silence.

Great project managers don’t just manage tasks, they shield their teams from toxic cultures.

Great project managers don’t just manage tasks, they shield their teams from toxic cultures. ☂️

Imagine a project environment where:

•Priorities shift constantly
•Deadlines are always unrealistic
•False urgencies pop up out of nowhere
•Micromanagement stifles creativity
•Politics and unfair policies erode trust

👎 These are the realities that can drain your team’s motivation and productivity faster than any technical challenge.

💪 The best project managers act like an umbrella protecting their teams from these distractions so they can focus on what they do best: delivering great work.

👉 Are you that umbrella? Or are you letting the rain pour on your people?