The Cost of Saying No
Before my accident, the institution decided to fund a solution that I knew was the wrong answer.
Not "I disagreed with it." Not "I preferred a different approach." I knew it was the wrong answer.
I stood up in meeting after meeting and explained why. I pointed to historical failures. I pointed to technical limitations. I pointed to strategic concerns. I pointed to lessons we'd already paid for once before.
The institution had tried this same approach in the past.
It failed then. It was going to fail now.
Nobody listened.
Well, that's not entirely true. They listened. They just didn't care.
Because sometimes organizations stop making decisions based on expertise and start making decisions based on ego. And there is no force in corporate America more powerful than a room full of people who desperately want credit for driving the bus.
Not because they care where the bus goes. But because they want everyone to know that they were the ones driving it.
The funny thing is that I don't particularly care about that stuff.
Don't get me wrong. If somebody offered me more money tomorrow, I'd take it. I'm not stupid.
But advancement has never been the thing that motivates me.
I've spent most of my career caring about outcomes.
I care whether the solution works. I care whether the institution succeeds. I care whether we're building something that will still be standing ten years from now.
That's a very different motivation than building a resume.
So leadership funded the solution. They told me they didn't need my team's help. They told me they could handle the testing. They told me they had the expertise covered.
Okay. Knock yourselves out.
What followed was exactly what anyone paying attention could have predicted: Failure.
Then more failure.
Then expensive failure.
Months passed.
I got hit by a car.
I nearly died.
I spent months learning how to walk again.
I returned to work.
The solution was still failing.
Eventually my team became involved anyway, because reality has a way of demanding participation from the people who actually know what they're doing.
And the deeper we looked, the worse it became.
Yesterday I delivered another round of bad news. The solution isn't merely struggling. It's actively damaging other parts of the system.
Problems that need to be fixed before anyone should consider moving forward.
And the moment I said it, I became the bad guy.
Again.
I've spent much of my career being the person who says “no”.
Not because I enjoy it. Not because I'm negative. Not because I want to slow progress. Because sometimes progress in the wrong direction is worse than standing still.
Anybody can approve a bad idea. Anybody can spend someone else's money. Anybody can smile, nod, and tell leadership what they want to hear. The hard part is standing in a room full of people who have already committed themselves to a mistake and saying: "No."
Not because it's politically advantageous. Because it's true.
The problem, of course, is that being right doesn't build political capital. Being agreeable builds political capital. Being optimistic builds political capital. Being supportive builds political capital.
But being the person who points at the iceberg tends to make people angry … Especially when they're steering directly toward it.
So yesterday I was reminded once again that expertise and authority are not the same thing.
One is earned. The other is assigned.
And sometimes the people with authority become deeply irritated when expertise refuses to validate their decisions.
I probably didn't do my career any favors. I probably bruised a few egos. I definitely wasn't the most diplomatic version of myself.
But after watching hundreds of thousands of dollars get poured into a solution that never should have existed in the first place, I found it difficult to care.
Because excellence has never been about taking shortcuts. Excellence isn't easy. It's humility. It's hard work. It's failure. It's learning. It's listening. It's being willing to admit that an idea isn't working and changing course before it becomes a disaster.
My team has been quietly building the right answer in the background. We'll get there. We always do.
But yesterday reminded me of something important: Sometimes leadership isn't saying yes. Sometimes leadership is having the courage to say no when everyone around you desperately wants to hear otherwise.
And frankly, that felt pretty good.