puzzle missing a piece

Enterprise Architecture is not Solution Architecture on a Grander Scale

One company we worked with as EA consultants had a surprisingly large number of enterprise architects. Why did they need so many? In truth, they didn’t. The CIO explained that in a year when his firm had imposed a pay freeze, he had promoted a group of solution architects to the role of enterprise architect as a way of awarding them more money. To justify this decision, he said that the candidates had all been required to get TOGAF accreditation, so that meant they would be fully qualified to work as enterprise architects. Really? Qualified on paper perhaps, but capable of fulfilling the role? We weren’t too sure about that.

Enterprise Architecture vs. Solution Architecture

The roles of solution architect and enterprise architect are certainly related, but they are quite distinctive, and each requires different skill sets and experience. A powerful metaphor that clearly illustrates the difference between the roles is widely used in the French job market. Recruitment adverts in France for enterprise architects often use the term ‘urbaniste’, which literally means town planner. In contrast, the role of a solution architect is compared to that of an architect who designs and oversees the construction of individual buildings. Town planners may have the same basic qualifications as building architects, but they have many more factors to take into account in their work, Including the appropriate zoning of properties (domestic, industrial, retail, etc.), the supply of infrastructure services to large numbers of premises, transportation needs, environmental concerns, and so forth. For the town planner, political constraints are also a constant challenge.

The Solution Architect Role

Like the architect who designs a building, the solution architect is charged with supporting a specific project within a specific scope, a ring-fenced budget and an agreed duration. In conceiving and overseeing the overall design of the processes and systems involved, solution architects certainly have to follow corporate standards and take account of dependencies and links with organisational assets outside the scope of the project, but these are not their primary focus. Politically sensitive matters, such as project governance and ensuring the expected benefits are delivered, are typically handled by the project management team, although the Solution Architect may play a pivotal supporting role in such matters.

The Enterprise Architect Role

Although the solution architect has a vital role to play, the true enterprise architect operates at a very different level. In a similar way to the town planner, enterprise architects have to ensure that the component parts of their organisation, including those that are subject to change projects, mesh together efficiently as a coherent whole and support the business strategy. Therefore, along with a clear and broad appreciation of the current state, to achieve this, they need to understand and communicate the target state business operating model alongside the changes required to deliver it. They should also have the experience and credibility to be given a clear mandate to monitor, guide, support and approve change projects regardless of an organisation’s IT operating model, e.g. service-based, product-based, platform-based. The enterprise architect is thus a key enabler of an organisation’s overall business/IT strategy.

Enterprise Architecture Competences

Given this ambitious scope, what are the competences required of an enterprise architect?  An intensive study carried out several years ago by the Swedish branch of the International Association of Software Architects (IASA) summarised them as follows:

“Deep knowledge in both business and IT; leadership and negotiation skills; experience in governance, project management and economy [budgeting and financial management]; knowledge in enterprise architecture and business modelling.”

We would expand this list of attributes to include the abilities to articulate and sell the business strategy in terms of its impact on the operating model, to balance short term and longer-term interests, and to understand when and where to drop down into detail. Also required as enterprise architects move ever closer to the business will be political skills of the highest order and a talent for communication at all levels.

The enterprise architect role as defined above clearly calls for a demanding combination of skills, experience and personal attributes, and most organisations will struggle to recruit people who can capably fill it. Although the skills and experience gained by Solution Architects can provide an invaluable foundation for taking on the role of Enterprise Architect in the future, simply relabelling solution architects and putting them through a TOGAF course simply won’t hack it.

Contact Us