The information that could have changed everything was already in the room. The system just hadn't made it safe to say yet.
We were in a conference room, working through how we were going to hit our targets for the year, when one of my product leaders said something that landed like a hand grenade and a needle scraping across a record at the same time.
He began to enumerate, carefully and methodically, the number of unused product licenses sitting inside our target accounts. Licenses the previous ownership had sold — in bulk, at volume — to inflate the company's value before the acquisition. He explained that the banks we were counting on to drive revenue already had more of our product than they could use. And then, almost as an aside, he mentioned that neither he nor anyone else on the product side had been consulted when the annual targets were set.
The room went quiet.
This wasn't new information to him. He had known it for some time. What was new was that he finally felt he could say it.
The most strategically important thing your team knows is usually the thing they don't yet feel safe telling you.
The easy answer is that people were conflict-averse, or that the previous culture had trained them not to surface bad news. Both were true. But I've come to believe the deeper answer is almost always structural — a system problem, not a people problem.
W. Edwards Deming, the quality theorist whose ideas transformed manufacturing, argued that 95% of organizational problems are caused by systems, not individuals. When something goes wrong, the instinct is to find the person responsible. But in most cases, the person was operating rationally inside a system that produced the wrong outcome. Fix the person, and the system produces the same result with someone else.
The team I inherited had learned, under previous leadership, that raising uncomfortable truths carried risk. Not dramatically — nobody had been fired for speaking up. But over time, the culture had quietly signaled that harmony was valued over honesty, that the official story was the safe story, and that problems were best managed quietly rather than named openly.
That's a system. And it was working exactly as designed — just not in any way that was useful to the organization.
In the weeks before that conference room moment, we had been doing something deliberately unglamorous: having real conversations. Dinners, informal check-ins, leadership team sessions where I asked direct questions and stayed quiet long enough for people to actually answer them.
We started rating ourselves as a leadership team on a simple question: how aligned are we, really, on what we're trying to do? The early scores were politely high. I told the team to expect them to drop. Not because things would get worse, but because as trust built, we would start telling each other harder truths — and that was the point.
I also said something early that I've said to every team I've led since: we are not here to blame people. We are here to fix the system. When a problem surfaces, our first question is not who is responsible. It's what about the way we work made this outcome likely.
That reframe changes everything. When people believe the system is on trial rather than themselves, they become extraordinarily willing to talk. Because now honesty serves them — it's the thing that leads to the problem actually getting solved, rather than the thing that puts a target on their back.
If you want your team to tell you the truth, make truth-telling the rational choice. That means visibly focusing on systems over people when things go wrong — and doing it consistently enough that people believe you mean it.
You can't manufacture psychological safety with a workshop. You build it through repeated, observable behavior over time.
After the room went quiet, we paused. Absorbed what had just been said. And then — because we still had targets to hit and a business to build — we got to work.
What that honest moment unlocked wasn't despair. It was clarity. We now knew, precisely, what we were dealing with. The strategy that had been handed to us wasn't going to work. So we built a new one — redefining the product, reframing the customer, and creating a business model that actually fit the market we were in.
That pivot led to the largest enterprise deal in the company's history. It reduced our cost base significantly. It set the business on a path to sustainability after years of losses.
None of it happens if that product leader doesn't speak up in that conference room. And he doesn't speak up if the system hasn't started — slowly, imperfectly, but genuinely — to make honesty feel safe.
Clarity before action. But you can't get to clarity if the system punishes the people who have it.
If you're leading an organization that's underperforming, it's worth sitting with this question before you look at the people: does my system make it rational for people to tell me what's actually going on?
Not whether you've told them your door is open. Not whether you've said you want honest feedback. Whether the observable reality of working in your organization — what happens when people raise problems, whether bad news travels up or gets managed sideways, whether the official story and the real story are the same — makes honesty feel like the smart move.
If they're not telling you, it's rarely because they don't know. It's usually because the system hasn't made it worth the risk.
The information you need to make better decisions, move faster, and build something that lasts is almost certainly already inside your organization. The question is whether you've built the conditions for it to reach you.