The Dangerous Rise of Enterprise Architecture Without Thinking, Especially in the AI Era
The danger is not that enterprise architects will run out of answers. It is that we will stop requiring them to demonstrate the thinking behind those answers. When a passing score is accepted as proof of professional competence, the appearance of readiness can replace evidence of the ability to do the work.
Imagine an executive asking which initiatives deserve funding, which dependencies have been overlooked, and what evidence supports the recommendation. There are no four choices on a screen. There is an enterprise decision to be made, and someone must explain why it is the right one.
That is the gap a certification must address. A well-designed multiple-choice examination can test knowledge and aspects of a framework. It does not, by itself, demonstrate that a candidate can define an ambiguous enterprise problem, build a usable architecture, expose a flawed assumption, or defend a consequential recommendation. The criticism is not of people who pass exams. It is of treating the exam as sufficient evidence of practice.
The AI era makes the distinction impossible to ignore. Whether an answer comes from an examination option, a familiar template, or an AI-generated draft, the architect must still establish what it means, whether it fits this enterprise, and what consequences follow. A plausible answer is not a defensible decision. Responsibility cannot be delegated to the source of the answer.
The EACOE Workshop makes the work visible. Participants develop architecture models and relationship models, generate prioritized initiatives, present their work, and receive review from experienced enterprise architects.
The distinction is fundamental: not simply selecting an answer, but producing work that others can examine, question, and use. Practice is the basis of the certification, not an optional activity after it.
Architecture without thinking does not have to look empty. It can arrive with polished diagrams, approved terminology, and a certificate. The safeguard is to require the reasoning behind the work: how the problem was framed, how the evidence was tested, and why the recommendation should be trusted. Certify the ability to do enterprise architecture, not merely the ability to pass an examination about it.
