There is a persistent myth in architecture that you can separate the technical work from the organisational work. That the architect’s job is to produce technically excellent designs, and then someone else — a project manager, a business analyst, a change manager — facilitates the conversations needed to make those designs happen.
This is wrong, and organisations that operate on this assumption consistently fail to get value from their architecture investment.
The research on how effective architects actually work is clear: every architect who delivers sustained value wears two hats simultaneously. Neither can be delegated.
The Technology Expert hat
Deep, current, authoritative knowledge of IT domains, technologies, vendor products, architecture patterns, and the specific technical landscape of the organisation. This hat produces technically sound solutions — IT Designs that actually work, IT Standards that reflect current best practice, IT Landscapes that accurately describe reality. Without it, an architect has no credibility with the project teams and technical specialists they need to influence.
The Change Agent hat
The ability to engage stakeholders — to understand what they actually need rather than what they say they need, to navigate conflicting interests without losing relationships, to translate between business language and technical language in both directions, to achieve the consensus needed to move a planning decision forward. This hat makes architecture artefacts legitimate: produced through genuine collective agreement rather than technical authority.
Neither hat is sufficient alone
The pure Technology Expert — brilliant on the technical side, impatient with organisational dynamics, preferring to solve problems at the desk rather than in conversations — produces technically excellent work that doesn’t get implemented. Their solutions are overridden by political decisions they didn’t anticipate because they weren’t in the room. Their Standards are ignored because project teams find them impractical. Their Designs are deviated from because business stakeholders don’t feel ownership of them.
The pure Change Agent — excellent with people, skilled at facilitation, deeply trusted by business leaders — produces consensus without technical substance. Their planning decisions are politically viable but technically flawed. Their enthusiasm for collaboration isn’t matched by the technical depth needed to evaluate what they’re agreeing to.
Effective architects use both hats in the same conversations. Producing a Business Outline requires Technology Expert work (assessing technical feasibility, estimating cost, evaluating sourcing options) and Change Agent work (understanding the business sponsor’s actual goals, making the investment case legible to non-technical decision-makers) simultaneously. These are not sequential activities.
This has a direct implication for how architects are hired and developed. The population of people who combine deep technical competence with genuine organisational effectiveness is small. Finding it, or developing it in existing people, is the central talent challenge of an architecture function.
For architects early in their careers: the Technology Expert hat comes first — not because it is more important, but because technical credibility is the prerequisite for the Change Agent hat to work. Business leaders trust architects who clearly know what they’re talking about. That trust is the precondition for the conversations through which alignment is actually achieved. Build technical depth first. The organisational skills follow more naturally from a position of credibility than from a position of enthusiasm.