Enterprise Intelligence

TOGAF certification can be useful. But certification is not architecture. A method is not anatomy. A framework is not diagnosis. A roadmap is not enterprise clarity. A governance board is not proof that the enterprise has been architected.

I configure AWS. That is real work. That is useful work. That is important work. But if P1–P4 are not explicit, I am not the architect of the project.

I configure ServiceNow. That is real work. That is useful work. That is important work. But if P1–P4 are not explicit, I am not the architect of the project.

At the GCC, engineering leadership can build faster, scale teams, improve platforms, and deliver releases. But if P1–P4 are not explicit, the GCC is only scaling implementation. Not architecture. The missing work is not more engineering leadership. The missing work is explicit project anatomy.

The enterprise is not one department. It is a system across sales, customer experience, operations, finance, HR, engineering, project delivery, product, marketing, legal, procurement, risk, support, partners, and technology.

My title says Security Architect. My work says something else. I configure IAM, define policies, run scans, respond to vulnerabilities. This is critical work. But is this architecture?

DevOps optimizes how fast we build. Architecture defines what we are building and how it fits together.

A capability model answers one question: what areas exist in the enterprise? Architecture must answer what outcomes must be achieved (P1), how activities are sequenced (P2), how systems interact across rules, functions, UI, data, and timing (P3), and what components exist (P4). A capability map does not define these.

If we look closely at what most roles labeled as “architect” actually do, a pattern emerges. They write code, configure cloud services, set up networks, automate deployments, run DevOps pipelines, manage Agile delivery, review JIRA boards, and create capability models.

The problem is not that I configure routers. The problem is that router configuration is being called architecture.

If I am a coder and I am called an architect…it usually means the architect is missing.

The problem is not that I am doing the wrong work. The problem is that my work is being called by the wrong name.

The problem is not that EA is missing. The problem is that IT Architecture itself is not being done. And the simplest test remains: If your architecture leaves when your Chief Architect leaves, it was never architecture. It was memory.

If architecture is actually code management: Knowledge is embedded in pipelines, logic is embedded in services, decisions are embedded in individuals. When the person exits, there is no architecture to transfer. Only execution to reverse-engineer.

The market has more architects than ever before. Cloud Architects. Digital Architects. Solution Architects. Enterprise Architects. Transformation Architects. On paper, architecture capability has scaled. In reality: Architecture itself has not.

So how did we arrive at this point? Because over time, a dangerous simplification took root: Architecture = Understanding how to build systems= Knowing how to assemble services= Being good at configuring cloud tools= Smart coding