What are the Different Enterprise Architecture Jobs?
Why is There Confusion About Enterprise Architecture Jobs?
Why Use Enterprise Architecture?
Impact of Different Enterprise Architecture Use Cases
Impact of Different Enterprise Architecture Domains
What is an Enterprise Architecture Team?
Types of Jobs on an Architecture Team
How Do all the Enterprise Architects Collaborate?
Enterprise Architecture Job Descriptions
Enterprise Architect Job Description
Security Architect Job Description
Business Architect Job Description
Solution Architect Job Description
Why is There Confusion About Enterprise Architecture Jobs?
Our belief is that the confusion stems from the work done by an enterprise architect. It varies wildly. Different enterprise architecture use cases change the job. The interaction of enterprise architecture domains changes the job.
As an example, look at the job of sales. Sales jobs are described using several specialized terms.
- Enterprise sales
- Inside sales
- Business development
- Outside sales
Most people carry an understanding of sales. They know the job is to find a customer and sell them the company's products and services.
With enterprise architecture we have a problem that most people don't know what an architect is expected to do. When we develop enterprise architecture teams we see four common problems with the job title:
- Architect is used as a seniority award
- Architects are measured on their subject matter knowledge
- Architects are engaged after decisions are made to implement solutions
- Architects think they need to decide what the organization should do
Best practice is wildly different. Enterprise architect is a profession. Just like sales, engineering, or management. The profession has a standard approach, the TOGAF Standard. You don't get promoted top sales because you are the senior customer service agent. You don't become an mechanical engineer operating a production facility.
Enterprise architecture it is not seniority. Skill as an enterprise architect is not measured by technical knowledge. Our understanding of the profession should reflect this. Instead, we are sloppy with language.
Clarifying a few things will help us build our understanding of the different enterprise architecture jobs.
Why Use Enterprise Architecture?
To make the most informed decisions about changing our organization, we use enterprise architecture.
The steps can be simplified to:
- Understand how an organization's different parts work.
Business parts like organizations and processes. IT parts like software, data and infrastructure. - Use this understanding to uncover the root cause of a deficiency or shortfall.
- Find the best change to one or more parts to eliminate the shortfall.
- Execute the improvement projects to change the parts and eliminate the shortfall.
The different enterprise architecture jobs exist because these simplified steps are complex. They require specialized knowledge. They require weighing conflicting priorities and potential alternative solutions.
Impact of Different Enterprise Architecture Use Cases
There are four distinct enterprise architecture use cases. Each of these use cases impacts the different enterprise architecture jobs. The expectations of an enterprise architect working to support strategy are very different than one who works with Solution Delivery.
Re-using our sales example, the core job of finding a customer and selling them a product is executed very differently in enterprise business-to-business sales than retail sales. Let's explore the impact of the enterprise architecture use cases.
Job Impact of Enterprise Architecture to support Strategy
In this use case the enterprise architect needs to be looking out a three to ten-years. They will develop an architecture roadmap. The roadmap will be used to identify change initiatives and supporting portfolio and programs.
Job Impact of Enterprise Architecture to support Portfolio
In this use case the Architect already has a portfolio, and roadmap. There are a set of change initiatives. They will identify projects that deliver improvements. Every project needs terms of reference, an approach aligned to the portfolio. There will be dependency and synergy. A key part of the role is govern the project execution.
Job Impact of Enterprise Architecture to support Project
The enterprise architect starts with a project. It will have an expected outcome and set of constraints. They will need to balance implementation governance of the project with the creativity of the solution designers.
In many cases there is only a very blurry line between the solution designer and the enterprise architects. The key role of the enterprise architect is implementation governance. They must ensure the project delivers the expected purpose and value.
Job impact of Enterprise Architecture to support Solution Delivery
The potential for a blurry line between enterprise architect and solution designer supporting Project is wider and blurrier with solution delivery. As architects they are very focused on defining how the change will be designed and delivered.
They need to provide the complete set of performance expectations constraints, controls and architecture requirements.Then work with the solution designer to find and implement a design that meets performance expectations and constraints.
We think about SABSA's domain model with architecture to support solution delivery. Finding and expressing the boundaries of performance expectation and constraint.
Impact of Different Enterprise Architecture Domains
Within an enterprise architecture team there are usually a number of domain architects - business architect, security architect, application architect, technology architect, solution architect, and the ubiquitous enterprise architect. A source of confusion about the different enterprise architecture jobs is how the different roles and responsibilities overlap.
Like with architects who deal with construction, there are different aspects to coming up with plans for a structure. Each of these various levels of architecture and their systems needs to work in total harmony for the success of any business. Most IT projects are doomed to failure if there is discord between the different architects.
We break the enterprise architecture into domains because it is easier to analyze and describe like things. The same techniques and skills are used to analyze an architecture domain.
Business architecture explains the operational practices, operating models, organization, and information flow of the enterprise.
The security architecture, or information systems security architecture, explains the threats, controls, and security services. The role of a security architect is oriented on the controls that effectively manage the risk associated with information and information technology.
A solution architecture defines an implementable system that meets the performance expectations, constraints and security controls. It will include testing requirements to ensure that the intentions of the architecture and design are realized. Solution architectures are not just implemented IT systems, they are complete solutions.
Go Further with Best Practice Enterprise Architecture Process and Method
Best practice enterprise architecture from Conexiam Navigate
Developing an Architecture View
Developing an Architecture View Enterprise architecture is an essential compass. It helps organizations navigate the complexities of technology, strategy, and operations. The core of enterprise architecture is a systematic approach. The objective is to ensure […]
Ensuring Alignment and Accountability: The Crucial Role of Enterprise Architecture Governance Checklists
Ensuring Alignment and Accountability: The Crucial Role of Enterprise Architecture Governance Checklists Enterprise Architecture Governance Checklists simplify enterprise architecture governance processes. The governance process needs to approve target architecture and provide implementation governance. A robust enterprise […]
Enterprise Architecture Work Management
Enterprise Architecture Work Management Enterprise Architecture Work Management is crucial to the day-to-day success of an Enterprise Architecture Team. Architects must deliver useful guidance before stakeholders make informed decisions. Enterprise architects need to translate the […]
Unlocking Your Business Potential: How to Create an Effective Capability Map
Unlocking Your Business Potential: How to Create an Effective Capability Map Are you struggling to identify the capabilities needed to take your business to the next level? Do you find it challenging to align resources […]
Developing Enterprise Architecture Strategy
Developing Enterprise Architecture Strategy: Strategic Plan for Change Enterprise Architecture Strategy is action. Action your organization will take and the changes you will make to reach your strategic goals. Strategy development is all about choice. […]
How to Define Enterprise Architecture Principles
How to Define Enterprise Architecture Principles To Define Enterprise Architecture Principles start with understanding what a principle is and how to apply them. Then we can develop strong architecture principles that help improve our organization. […]
Enterprise Architecture Roadmap as Design
Enterprise Architecture Roadmap as Design An Architecture Roadmap is a planning tool that helps an organization’s decision-makers. A dynamic Architecture Roadmap is designed to help them develop and travel the best path forward. It also […]
Making Smarter Choices: Why Your Business Needs Architectural Decisions
Making Smarter Choices: Why Your Business Needs Architectural Decisions Enterprises are constantly confronted with the challenge of making crucial decisions. Every day, decisions, including operational practices and technology selections, have a significant impact on a […]
Everything You Need to Know About Using Architecture Alternatives
Everything You Need to Know About Using Architecture Alternatives Architecture alternatives are required for good enterprise architecture development. When you start architecture development, your enterprise has deficiencies. There are areas for improvement. You need to […]
Understanding Enterprise Architecture and Agile
Understanding Enterprise Architecture and Agile Both agile and enterprise architecture are designed to reduce risk. Agile software development excels at building something that we have never had before and do not know how to build. […]
Different Enterprise Architecture Jobs
Here is a deep dive into the different types of enterprise architects and their roles in an organization.
What is An Enterprise Architect
An enterprise architect is one of the senior-most positions in the Enterprise Architecture Team. Enterprise architects ensure that an organization's strategy aligns with its goals. Enterprise architects have the most overarching view of the organization and knowledge of its capabilities and potential. They help companies drive change - to cut costs, grow markets, introduce new products. To be better.
Enterprise architects analyze and keep up with current trends in technology architecture and disseminate their findings of new frameworks and best practices. They focus mainly on capability development, supporting the current operating model, enterprise software, and services. They are also in charge of crafting how the organization will evolve at a portfolio-planning level and are usually responsible for determining which changes will happen.
Enterprise architects work across the organization, determining the needs of a range of business units and processes. They also ensure that business units have the right tools to gear them up for success.
What is A Solution Architect
As the name suggests, solutions architects are required to provide solutions to businesses. Solution architects evaluate business requirements and constraints and turn these into solutions, products, or services through technology. They comprise quite a number of processes and sub-processes that are guided by distinct enterprise architectural perspectives.
Solution architecture involves broadening client demands to comprise business needs linked to technology. This includes carefully looking at how the various components of business, information, and technology can be applied to solve a specific problem. Simply put, solution architecture integrates technical business needs into real IT solutions while also outlining guidelines and directives for spot-on advancement and implementation.
Solution architects act as a bridge between IT and business operations by ensuring that everybody is on the same wavelength while developing and implementing technical solutions for business issues. They are the link between enterprise architects and technical architects. Moreover, they translate the design into a concept for IT operations and ensure that each solution developed has proper technical integrity.
Different Domain Architects
They are the most hands-on of the three types of architects. Most domain architects focus on a single architecture domain. Domain architects have a chief responsibility to ensure their part of the enterprise works with the other architecture domains smoothly.
Using their expertise and skills, domain architects put the identify what needs to change in their domain. Ensuring the complete solution support the strategy or portfolio defined by the enterprise architect. You should keep in mind that domain architects work as a team to provide recommendations and informing stakeholders about any potential risks.
They are the ones who define the structure of a system. Often during implementation projects, they will perform a key architecture governance role and oversee parts of the change program to achieve the result. They are also the closest to the organization's end-user among all architects.
Domain architects include:
- Security Architect
- IT Architect
- Application Architect
- Data Architect
- Business Architect
To understand the differences between different domain architects, you need to understand their domains.
Conclusion of Different Enterprise Architecture Jobs
What is an Enterprise Architect?
When we hear the term architect, we probably picture a person wearing a hard hat and holding a blueprint on a construction site. This is hardly the case despite both having something to do with sites - one works on building sites while the other works to improve your business. Both architects are fundamentally designers. The one we are referring to works in the digital realm.
Similar to how construction architects draft designs and blueprints that guide the way we erected a structure; Enterprise architects create the blueprint for your organization to meet a digital challenge. The designs ensure flexibility, scalability, and security of the entire system while ensuring they align with the business and technical requirements of an organization.
An Enterprise Architect’s role is to translate all necessary characteristics of your digital enterprise into a blueprint shaping its components and defining the communication and coordination between them. All good architecture drives change. In fact, when you think about the analogy of blueprints and building plans, a good enterprise architecture will cover the regional development plan, transportation, zoning, education, recreation, and safety. Your enterprise is a complex system, effectively thinking about your digital transformation presupposes the existence of the elements and the structure that subsumes relations and connections.
Digital transformation is happening at an extremely fast pace, meaning that organizations have to try keeping up with the changes in technology solutions. Architecture has steadily grown into an essential part of the IT department for any successful organization. These need to be working in perfect harmony for the success of business activities.
Businesses that have effective cooperation across the board have proven to be more successful in achieving their goals when compared to others. Fostering the working together for a common goal mentality is what sets apart successful businesses from failed ones. Each party might play a different role, but piecing them together, each of these efforts turns into the successful implementation of a project.
The variables of collaboration might be different depending on the company size, but the bottom line is they all ensure the project or product is successful. Similar to the moving parts of a machine, each piece serves a vital role, and it's sometimes impossible for the machine to operate when one is taken out.
Start Your Enterprise Architecture Journey
If you’re considering a career path in enterprise architecture, you can do it with us! The different Enterprise Architecture Jobs that make up a solid enterprise architecture team use a common industry standard framework, TOGAF. We use our 12-week architectural kick start program for every different enterprise architecture job. Build the skills to be a better architect.
Ready to get started? Get in touch with the consultants at Conexiam to learn more about how our TOGAF Certification Training and Enterprise Architecture Training can help you develop good architecture skills.
