It was one of those late Friday afternoons when the week finally lets go. A few of us — architects and engineers with years of real delivery — sitting around a table, coffee going cold, talking honestly.
One of the group is a longtime practicing Enterprise Architect we all respect deeply. He's the calm, grounded voice in the room. Never sat the formal exam, holds no stack of credentials. He came up through practice long before "strategy" became the headline. Refreshingly connected to reality.
At one point the conversation turned to a question many of us carry but rarely say out loud:
"Why do so many people doing genuine enterprise-level thinking never actually hold the EA title?"
Several of us have spent years across complex environments — cloud transformations, M&A integrations, multi-stakeholder landscapes — without "Enterprise Architect" on our business cards.
We've noticed the same pattern in interviews: less focus on outcomes, more on whether you've held the exact title or speak the expected language.
Most of us grew into architecture — starting in delivery, shaping systems, guiding direction across messy, complex landscapes.
The formal EA path has its frameworks, certifications, and shared vocabulary. Built by serious people over decades. Real value. We respect it.
But here's what we kept coming back to.
Too often the focus stays on polished artefacts while operational costs keep rising and inefficient parts of the estate drain money. The traditional model of "create the roadmap and step back" feels increasingly insufficient. The real craft is staying involved — adapting direction, reducing cost drag, maintaining coherence when clean strategy meets messy execution.
Our colleague described his role best. Not producing documents. Maintaining the integrity of a direction across hundreds of decisions made by people who were never in the original strategy room. Practice first. Anchored in reality.
In the best organisations the EA acts as connective tissue — translating intent, resolving conflicts, keeping the work coherent when the map collides with the territory.
The conversation left us with a simple reflection.
Enterprise thinking is already happening in SMEs, startups, and large organisations alike — among people who've learned as much from hard outcomes as from frameworks. Many don't carry the formal title or speak the classic dialect. That doesn't mean they aren't doing the work.
The discipline still matters. But its greatest value lies less in titles and beautiful models — and more in the clarity, coherence, and results it creates in the real world.
Written after a real conversation with colleagues I respect. No frameworks were harmed.