The role now
The head of architecture (or chief or enterprise architect) decides how an organisation’s technology fits together: the target state, the standards, and the big design choices. Good architects make fewer, clearer decisions and write them down.
The role has moved closer to delivery. Architecture teams are expected to help programmes move faster, not act as a gate at the end.
Hiring a Head of Architecture: settle these first
What authority will the role have?
An architecture function that can only advise is ignored. Say which decisions it owns and who it answers to.
Enterprise or solution?
Decide whether you need someone to set the long-term picture across the organisation, or someone to lead design on major programmes.
What is the next big decision?
A platform change, a merger, an ERP or a cloud move. Candidates who have made that decision before shorten the path.
Stepping up to Head of Architecture
Solution and domain architects who step up need to lead other architects and to win arguments with executives, not only with engineers.
Own an architecture decision record across programmes, present a target state to executives, and lead a small team of architects.
The techexec network is built for this step. Members get a monthly briefing, small roundtables and a confidential career conversation with Aaron. Join the network.
What we ask candidates about
- A major design decision you made and what it cost to reverse.
- How you got delivery teams to follow standards.
- The frameworks you use, and when you don’t use them.
- How you present architecture to executives.
Questions
Do you recruit enterprise architects?
Yes, and chief, enterprise and lead solution architects. Many go on to CTO or CIO roles.
Do you only recruit permanent architects?
The network is built around leadership careers, which are mostly permanent. Ask us about anything else.