Architecture Is Not a Technology Profession
For years, the honest answer to “what is an architect” would have been a technical one: someone who knows the cloud platforms, the integration patterns, the trade-offs between a handful of database engines. That is not the wrong knowledge to have. It is the wrong definition — because it defines the role by its instruments instead of its purpose, and instruments never sit still long enough to build a profession on.
Here is the definition that replaced it:
Architecture is an organisational decision-making discipline that happens to use technology as its primary medium.
Read it twice. If it is true, it quietly explains a lot that the instruments-based definition never could:
- why architecture interviews keep drifting into engineering trivia, and keep feeling wrong when they do
- why organisations can staff a role called “architect” for a decade and still argue about what it is for
- why the arrival of AI amplifies architectural judgement instead of making it redundant
- why technical depth is necessary for the job and still nowhere close to sufficient
- why “stakeholder management” was never a soft skill bolted onto the real job — it is the job
- why the architects people remember are remembered for their judgement, not their code
Software engineering asks: how do we build this well? Architecture asks: how do we help the organisation make the best decision, given everything it knows and everything it is constrained by? The two questions overlap constantly — most days, an architect is doing some of both — but they are not the same question, and confusing them is exactly how the role ended up defined by its tools.
The useful test is the one that exposes the gap directly. Take away every technology name — no clouds, no frameworks, no vendors — and ask someone to define the architect’s job in a single sentence. If the sentence survives with the tools removed, the definition was already about purpose. If it collapses without them, it was never a definition at all — it was a parts list.
This is the inversion the Anonymous Architecture Framework is built on: define the role top-down, by the decisions it exists to protect, and let the technology follow. That inversion, and everything it changes about how the profession should train, hire, and judge its own people, is the argument of the manifesto and the books.