I walked away from a deal last year that looked good on paper. Good terms, credible people, real upside. I said no without being able to fully explain why, and I spent about two weeks second-guessing it.
I was right to say no. I know that now. But I had no clean answer at the time — no metric I could point to, no framework that made the decision obvious.
What I’ve learned, slowly, is that the explanation is often not the point. Most of the things worth saying no to aren’t obviously bad. They’re subtly wrong — a slightly off fit, a relationship that would require more managing than it should, a direction that’s technically fine but pulls energy away from the thing that’s actually the thing.
That kind of wrongness is hard to articulate. It lives in pattern recognition built from a lot of previous decisions, many of which were mistakes. You can’t always name it in a pitch meeting.
The pressure to explain is real because “no” without explanation feels dismissive. And sometimes it is. But there’s another version: you’ve done enough reps with your own judgment that you can feel the misalignment before you can prove it. Forcing the explanation sometimes means manufacturing a reason for a decision you already made with better information than you can currently put into words.
This is why I try to reduce the inputs before the big decisions. Less noise, more signal. Fewer asks, slower context-switching. When you operate in that mode long enough, the instinct sharpens. You start to trust it.
What you don’t do defines you as much as what you do. Sometimes more.