Influence

You were right. You made the case, the analysis was sound, the evidence was there for anyone who cared to look. And nothing happened. Months later, sometimes years later, the organisation arrives, expensively, at the conclusion you handed them for free, and nobody remembers you said it first.

The instinct is to conclude the organisation is irrational, that politics beats merit. There's just enough truth in this to make it comforting — and it's one of the most expensive beliefs a technology executive can hold, because it locates the problem entirely outside themselves. The uncomfortable truth is simpler: being right and being influential are two different things, and a technical career builds the first while almost entirely neglecting the second.

In a technical context, correctness is most of the battle. At the executive level, that coupling breaks — the decisions that matter most are judgment calls made under uncertainty, and there is no proof that ends the argument. There is only a case, made well or badly.

What Influence actually asks for

Influence is the discipline of building a case people find compelling, not just a case that is correct — translating technical work into language business leaders trust, reading political dynamics accurately, building relationships before you need them, and negotiating from genuine understanding of what the other side actually needs.

Where to start

• Before your next proposal, draft the one-sentence business version before you draft the technical version. If the business version doesn't exist yet, the proposal isn't ready.
• Notice who outside your function trusts your judgment on things that aren't technology. That's the actual measure of enterprise credibility — not being right, being trusted.