A lot of good technical people struggle to be heard by the business, and it's rarely because they're wrong. It's because they're speaking the wrong language. When you tell a business leader "we can't do that, it's insecure" or "that timeline isn't realistic," what they often hear is an engineer being difficult. The message is right. The framing makes it easy to overrule.
The shift that changed how effective I could be was learning to translate technical objections into the language of risk and tradeoff, which is the language the business already thinks in. Instead of "this isn't secure," something like: "we can ship on that date, but to do it we skip the security review, which means we're accepting the risk of a breach in this component. Is that a risk we want to own?" You haven't refused anything. You've made the tradeoff visible and handed the decision, with its real cost attached, to the people whose job it is to own that cost.
This matters because most of the disasters I've seen weren't caused by someone in IT failing to raise a concern. They were caused by the concern being raised in a way that was easy to dismiss. "It's not best practice" gets waved off. "We are choosing to accept a specific, named risk in exchange for a specific benefit" is much harder to wave off, because now it's a documented business decision, not a technical opinion, and someone's name is on it.
Saying no in the language of risk also protects you. When you frame a decision as an explicit tradeoff and the business chooses to accept the risk anyway, that's a legitimate outcome — it's their call to make. But it's now a shared, recorded decision rather than a warning you gave and they ignored. On the day the risk materializes, the conversation is very different when everyone agreed, eyes open, to accept it.
You don't get influence in a business by being the most technically correct person in the room. You get it by making the consequences of technical decisions legible to the people who make the calls. Learn to speak in risks, costs, and tradeoffs, and your "no" stops sounding like obstruction and starts sounding like exactly what it is: someone protecting the business from a cost it couldn't see.
– Serguey Shinder
Top comments (0)