Everything was green.
Every project. Every team. Every update.
On paper, it looked like a leadership dream.
In reality, it was a red flag.
The Meeting That Looked Perfect
We were wrapping up our bi-weekly review of the company’s five most critical initiatives—projects tied directly to product launches, market expansion, and production capacity. These meetings mattered. A lot.
They determined whether we hit timelines, captured new opportunities, and kept pace with demand.
The review process itself was new. I had introduced it after seeing it work well in previous organizations. When teams are clear on priorities, aligned on execution, and operating with urgency, these meetings become powerful drivers of performance.
But this one felt…off.
Every project was marked “green.” No risks. No delays. No issues.
That’s not how real execution works.
Even the strongest teams encounter friction. A healthy pipeline of work should include some yellow (emerging risks) and red (issues that need support). When everything is green, it usually means one of two things:
Either the work isn’t being challenged…
Or the truth isn’t being shared.
The Language That Gave It Away
As I listened more closely, the language told the real story.
“We’re making good progress.”
“There’s a slight bump, but we’ve got it covered.”
What I wasn’t hearing:
“We’ve only hit 50% of our milestones.”
“A key test failed, and here’s how we’re adjusting.”
From experience, I knew several of these projects were not on track. But no one was saying it out loud.
That’s when it became clear: This wasn’t an execution issue.
It was a psychological safety issue.
Why Teams Don’t Speak Up
In a Harvard Business Review article, Amy Edmondson defines psychological safety as:
“A shared belief that it is safe to take risks, speak up, ask questions, and admit mistakes without fear of negative consequences.”
That safety wasn’t present in the room.
Instead, what we had was hesitation. Caution. Filtered communication.
And that’s dangerous, because when teams don’t speak honestly, leaders lose visibility. And when leaders lose visibility, execution suffers.
Edmondson also highlights something even more telling.
When executives are asked how many failures are truly “blameworthy,” they estimate 2–5%.
But when asked how many are treated as blameworthy?
The answer jumps to 70–80%.
Think about that gap.
It explains everything.
When teams expect blame, they protect themselves.
They soften updates.
They hide risks.
They avoid asking for help.
And suddenly, your “green” dashboard is no longer a sign of success—it’s a symptom of silence.
So What Should Leaders Do Instead?
When something goes wrong, most leaders instinctively ask:
- What happened?
- Why did this happen?
- Who’s responsible?
Those questions may feel productive, but they often reinforce fear.
Instead, try this shift:
- What did we learn?
- What needs to happen next?
- How can I help?
It’s a subtle change. But it signals something powerful: We’re here to improve, not assign blame.
The Bottom Line
Execution doesn’t break down because teams don’t care. It breaks down because teams don’t feel safe telling the truth.
If you want better outcomes, start by creating an environment where honesty is expected and supported.
When leaders shift from blame to curiosity, something important happens. Teams become more open. Conversations become more real. Problems surface earlier, when they are still fixable.
The result is a more engaged and motivated team that feels their contributions matter and that they can speak freely without fear of retribution.
Over time, this shifts the culture away from pointing fingers and toward continuous learning and improvement. People become more comfortable sharing mistakes and more open about what they are learning along the way.
Because the moment your team feels safe enough to say, “This isn’t working”…is the moment you can actually fix it.
