Do not be a passenger on your own team

The most dangerous person on your team is the one who sees the problem and stays quiet.

Everyone worries about the team member who lacks knowledge. The expensive one is the team member who has it and stops talking after the first time.

In 2010, I was working at Tektronix Communications inside the Danaher group. We were at the global sales team kick-off meeting in Dallas. The speaker was Mike Mullane, a former Space Shuttle astronaut. He told one story that I have carried with me for sixteen years.

Long before he flew the Shuttle, Mullane was a weapons systems officer on a supersonic test flight. As they approached the pre-calculated go-home fuel state, he told the pilot they should turn back. The pilot said there was still time for one more test in the flight plan. Mullane did not argue. The pilot was experienced. The test mattered. Pushing back a second time felt like overstepping.

So he let it go.

They botched the landing, ran out of fuel, and ejected at low altitude. They nearly did not make it.

His lesson was simple. Do not be a passenger on your own team.

A passenger sees something off. Maybe even raises it once. Then, assumes someone more senior, more experienced, or closer to the problem has it covered. Silence feels safer than friction. Deference feels like respect.

But in hazardous work, that silence is a failure. And most meaningful work has some form of hazard, even if it is a missed quarter, a flawed product decision, or a strategy nobody quite believes in.

I have seen this pattern in every company I have led or rebuilt. Somebody in the meeting saw it. They said it once, nobody picked it up, and they moved on.

The person who says "I mentioned it in the meeting" and then goes quiet. The engineer who flags a process risk in an email and never follows up. The sales lead who knows the deal is dead but keeps reporting it as active because nobody asked the hard question. These are not bad people. They are passengers. And passengers do not prevent crashes.

The information was in the room. It just did not survive the hierarchy.

What struck me most about Mullane's story was his honesty about why he did not push harder. It was not ignorance. He knew. He had said it out loud. He just did not want to be the one to keep insisting after the pilot had already decided.

That is the trap. Knowing is not enough. Saying it once is not enough. The value is in the second time you say it, when it is uncomfortable, when the room has already moved on, when you are not sure it is your place. That is where the real contribution lives.

I have spent 30 years building and rebuilding companies. I have taken over organizations with 125 people and no working leadership, built turnaround plans with 1,200 tasks, and sat in rooms where the decision being made was clearly wrong. Mullane's lesson gave me a framework for something I already felt but had not named.

It works in two directions.

As a team member, if I see it, I say it. Even when I am not the most senior person in the room. Even when it is uncomfortable. And if it matters, I say it again. Especially then. A concern that disappears after one mention was never taken seriously. It was just noted.

As a leader, I work to make sure no one on my team feels like a passenger. Every perspective belongs on the table. Every voice gets counted. Silence in a meeting is not agreement. It is a signal that I need to dig deeper. When someone raises a concern once, I take it seriously enough that they should not have to find the courage to raise it twice.

When you lead people who know their work better than you do, your job is not to have the answers. It is to make sure the answers that already exist in the room actually reach the surface.

The cost of getting this wrong is not always as dramatic as an ejection at low altitude. Sometimes it is a production ramp that takes 18 months instead of three because an engineer saw the tooling problem early and only mentioned it in passing. Sometimes it is a customer relationship that dies because the service team knew the issue and assumed someone else would escalate it. Sometimes it is a strategy that fails because the people closest to the market stayed quiet in the planning meeting.

In every case, the information existed. It just did not move.

Here is a simple test. Think about the last meeting where a decision was made. Ask yourself: was there someone in the room who disagreed but did not say so? If you do not know the answer, you probably have passengers.

The companies that build reliable operations, the ones that actually get products from the lab to the factory floor and into patients' hands, are not the ones with the smartest people. They are the ones where the smartest people are not staying quiet.

Sixteen years after that sales kick-off in Dallas, I still think about Mullane's story. The story was ordinary. That is why it stayed with me. A qualified person saw the problem, said it once, and let it go. That happens in every company, every week.

The only question is whether your culture catches it or lets it fly past.

Kauko Vainamo, CEO, Ginolis.