Enterprise architecture does not fail on rigor. It fails on translation.
Here is something I have watched happen for fifty years.
An architect walks into a funding conversation with work that is genuinely correct. The models are sound. The dependencies are real. The analysis would survive any review you put in front of it.
And the room says no.
Not because the work was wrong. Because the work was never translated into the decision that room was actually making.
Not because the work was wrong. Because the work was never translated into the decision that room was actually making.
Four rooms. Four different currencies.
The C-suite is asking whether this moves the strategy. The CFO is asking what it costs and what it stops costing. Operations is asking whether this makes the work flow or adds four more steps. Engineering is asking what to build, retire, and reuse.
Those are four different conversations. Most of us bring one deck to all four and then wonder why only one person in the room nodded.
I walk through the stakeholder presentation kit we use - four audience-specific decks and the specific translations that make each one land:
Why technical debt only works on a CFO when you give it an interest rate and an amortization schedule
Why the application portfolio is not an inventory - it is four disposition decisions, each with its own evidence
Why presenting a future-state diagram to operations before you have proven you understand their current state ends the meeting
The GPS and architectural blueprint analogies, written out word for word - including the room where the GPS one backfires
How to answer “we tried this and got shelfware” and “Agile made this unnecessary” without getting defensive
The glossary that turns fourteen architecture terms into business value metrics your stakeholders already track
I will also give you the three rules that outlast any deck: present the decision, never the deliverable. Use their number, not the industry’s. And make the ask smaller than the objection.
