Enterprise architect as context engineer

Sadly:

the major issue with EA has always been cost of delay. The big problem is not that architecture tells development teams to change direction — development teams do this routinely. The problem is that architecture historically has taken too long. We have validated that assertion repeatedly with many chief EA pros. Now with agentic pressures, traditional EA models are increasingly untenable.

But, hopefully:

The architects who create the greatest value overthe next decade will spend less time maintainingdocumentation and more time addressingauthority, accountability, decision rights, data and decision quality, policy enforcement, acceptablerisk, and organizational trade-offs. They will workclosely with platform engineering, security, data,and business leaders to establish trustedenterprise context and ensure that it can beconsumed reliably by both people and machines.

They will also help build what may become one ofthe most important assets in the modernenterprise: a reusable, always-on enterpriseintelligence layer consisting of knowledge,policies, standards, ontologies, decision records,dependency information, and business contextthat can be applied repeatedly across AI systemsand autonomous workflows. Call it a context graph if you like.

Seems plausible. That said, it would also be a battle with other SDLC inhabitants who are looking to keep their jobs.

🔗 Will AI Eliminate Enterprise Architects?