Your CEO walks in with a “quick feature” that needs to ship by Friday. You know it’s not quick. You know Friday is impossible. You also know that saying “no” without context makes you look like you’re blocking progress.

The trick is never to say no. Say “yes, if” or “yes, but here’s what it costs.”

“We can do this by Friday if we pull two engineers off the billing migration. That pushes billing back two weeks. Do you want to make that trade?”

Now it’s a business decision instead of an engineering objection. You’ve given them the information they need to prioritize. Most of the time, they’ll reprioritize on their own once they see the tradeoff.

What doesn’t work is saying “that’s too hard” or “we don’t have time.” Those sound like excuses. CEOs hear that and think engineering is the bottleneck. They start looking for ways around you instead of through you.

Always frame it in terms they care about. Revenue impact, customer risk, timeline tradeoffs. “We can build the quick version in a week but it won’t scale past 1,000 users” gives them something to work with.

Your job isn’t to say yes to everything. It’s to make sure the company makes informed bets. Sometimes the right answer is the quick and dirty version. Sometimes it’s pushing back. But the CEO should always understand what they’re choosing and what they’re giving up.