Why Problems in Your Company Don't Get Fixed (It's Not a Data Problem)

On the night of January 27, 1986, the engineers who built the Space Shuttle's rocket boosters told NASA not to launch. A cold front was moving over Florida that would push temperatures into the twenties, far below anything the O-ring seals had ever flown in, and the chief O-ring engineer had already warned in a memo six months earlier that a failure would be a catastrophe of the highest order and the loss of human life.

The data was not missing. The warning was not vague. It was on the table, in the room, the night before. And the next morning Challenger broke apart seventy three seconds after liftoff, killing all seven people aboard.

What failed that night was not information, it was the response to it. When the engineers held their ground, the contractor's managers asked to go off the line, caucused privately, and pointedly left the engineers out of that final conversation.

A senior executive turned to the head of engineering and told him to take off his engineering hat and put on his management hat, the no launch recommendation was quietly reversed, and NASA was told the data was inconclusive. The bad news did not fail to exist. It failed to survive contact with power.

Most founders assume that if something is broken in their company they will eventually catch it in the numbers, but the uncomfortable truth is that the information almost always exists long before it reaches you.

Someone on the front line usually knows the deal is slipping, the new hire is not working out, the process is quietly broken, the best customer is halfway out the door. The real question is never whether the information exists, it is whether that information can travel upward without being softened, ignored, or punished along the way.

Amy Edmondson spent years studying this and found something that still surprises people, which is that the best performing teams reported more errors than the worst ones, not because they made more mistakes but because they felt safe enough to admit them. The mistakes were always there. Psychological safety simply determined whether anyone said so.

Here is how the silence actually forms, and it is rarely the dramatic cover up people picture. A warning exists at the front line. Raising it carries a real personal cost, because the person who flags the problem becomes associated with it, slows things down, contradicts someone more senior, or risks looking negative in a culture that prizes momentum.

In a low safety environment people run that math privately and quietly decide it is safer to stay quiet, or to round the truth up just a little.

So the signal gets fainter at every handoff, each layer sanitizing it just enough to protect itself, until what began as a red lands on your desk as a manageable yellow. No one lies. Everyone is simply behaving rationally inside a system whose incentives you built without meaning to.

This is why founders are so often the last to hear the worst news rather than the first. The higher you sit, the more filtered your view becomes, because every layer between the front line and your office has a reason to present things as more handled than they are.

You have lived this if a problem you supposedly knew nothing about turns out to have been obvious to three people for months, if your board pack always reads calmer than the conversations happening in the hallway, or if people nod in the meeting and then share their real doubts with each other on the way out.

The view from the top is not clearer. It is just more polished.

The fix is not to tell your team to be more honest, because that asks individuals to absorb a risk the system created, and it is not to demand better reporting, because better reporting of filtered information only gives you cleaner filtered information.

What actually works is changing the math. That means making it genuinely safe, normal, and even rewarded to surface bad news early, separating the messenger from the message so the person who raises a problem is treated as useful rather than guilty, and building at least one channel that bypasses the hierarchy entirely so the truth has somewhere to go that no layer in between can soften.

That last channel is one of the quiet reasons founders work with an outside advisor, because an advisor sits entirely outside your org chart and is therefore the one relationship not subject to the filter.

Founder Advisory at Founded Partners is built on exactly this, a confidential weekly relationship with Adam Miron, a serial entrepreneur with three exits including a unicorn and a background in business psychology, giving you both a place to say the things you cannot safely say to your own team or board and a thinking partner who helps you build the psychological safety and escalation habits that surface problems while they are still small and cheap to fix.

If problems in your company keep reaching you too late, that is not a sign your people are hiding things from you, it is a sign the system is doing exactly what it was built to do, and a system can be redesigned. 

See how Founder Advisory works at foundedpartners.com/founder-advisory, or get in touch to talk through what is actually happening beneath the surface of your own company.