"Stakeholder Management" Was Never a Soft Skill
Walk through any organisation and you will hear it speaking several languages at once.
Business speaks outcomes. Finance speaks budgets. Operations speaks reliability. Security speaks risk. Engineering speaks implementation. Each is fluent in its own tongue and reasonably deaf to the others — not through arrogance, but because each was hired to optimise a different thing and rewarded for speaking about it precisely.
Architecture is the one discipline expected to be fluent in all of them at once.
This is why the phrase “stakeholder management” does the profession such quiet damage. It sounds like politics — like something you do around the real work, a knack for keeping people happy while the engineering happens elsewhere. So it gets filed under “soft skills,” as though it were optional polish on top of the technical core.
It is the technical core.
The actual job is to carry a single decision — intact — across five audiences who each hear a different language. The chief executive’s “customers should get refunds within two minutes” has to survive its translation into a budget the CFO will sign, a risk posture security will accept, an availability target operations can hold, and an implementation engineering can build — and still mean, at the end, what it meant at the start. Being multilingual across those five worlds is the competency. Everything else is downstream of it.
You can see the failure clearly once you look for it. A technically flawless design dies in a room because the architect could speak implementation but not risk, and security heard recklessness where none was intended. A sound decision never gets funded because it was explained in latency numbers to people who think in quarters. The design was never the problem. The translation was.
This reframes what “good communication” means for an architect. It is not being articulate or likeable. It is the ability to hold one decision steady while re-expressing it in whatever language the person in front of you actually thinks in — and to notice, in their reply, the moment the meaning starts to drift.
That skill was never soft, and it was never management. It is the load-bearing part of the craft — which is the argument the manifesto and the books are built to make.