Saying no to good ideas

Anyone can say no to a bad idea. The hard part is saying no to a good one.

Prioritization and focus are often talked about, but most of that advice is about saying yes to the right things. We don't talk as much about the other half: saying no to the wrong ones. And the wrong ones aren't even the hard part. That's what separates "we have a lot of priorities" from "we have a strategy."

I learned that the hard way when we kept getting integration requests at my last company. A customer needed their data in a specific system, a partner wanted a slightly different format, and sales could close the deal if we just built this one thing. Each request was reasonable on its own, and each one felt like a yes.

But saying no meant disappointing people we wanted to help. It meant watching deals slip or telling a partner they had to wait, and it didn't feel like strategy. It felt like holding the line. I'll be honest: if this problem showed up today, AI would make the one-off builds so much easier that the pressure to say yes would be even higher. But the decision would still be the same. We weren't choosing between "custom integrations" and "nothing." We were choosing between fast yeses that scale your pain and a slower yes that scales your impact. Saying no to good ideas was how we chose the system over the request.

That pattern shows up everywhere. When I think about it, I start with a reframe: no isn't rejection, it's protection.