How to set up an EA practice

Establishing an Enterprise Architecture (EA) practice is a strategic initiative that involves a comprehensive process to align IT with business goals.

This article outlines the key challenges and steps involved in setting up an EA practice, including defining the vision, business drivers, and goals, assessing the current culture, context, and maturity, establishing the operational structure, building the EA team, determining objectives, and deciding the enterprise scope.

Additionally, it covers the importance of establishing authority levels and governance processes, and choosing the appropriate tools, methods, and frameworks.

By following these guidelines, organizations can successfully implement an EA practice that enhances efficiency, agility, and alignment with their strategic objectives.

First challenge (the why)

Establish vision, business drivers and goals

Establishing the vision, business drivers, and goals is the first challenge in setting up an Enterprise Architecture (EA) practice. This involves defining the overarching purpose and direction for the EA initiative. Here are the key steps:

1. Define the Vision: This is about articulating a clear and compelling picture of the future state that the EA practice aims to achieve. The vision should align with the overall strategic objectives of the organization and provide a long-term perspective.
2. Identify Business Drivers: Business drivers are the key factors that necessitate the establishment of the EA practice. These could include the need for improved efficiency, better alignment of IT with business goals, enhanced agility, or compliance with regulatory requirements. Understanding these drivers helps in prioritizing efforts and resources.
3. Set Goals: Goals are specific, measurable outcomes that the EA practice aims to achieve. These should be aligned with the business drivers and vision. Goals provide a clear roadmap and benchmarks for success, helping to track progress and make necessary adjustments.

Assess current culture, context and maturity

Assessing the current culture, context, and maturity is a crucial step in establishing an Enterprise Architecture (EA) practice. This involves evaluating the existing organizational culture, the current state of IT and business alignment, and the maturity level of existing governance processes and EA capability. Here are the key steps:

1. Evaluate Organizational Culture: This involves understanding the values, beliefs, and behaviors that characterize the organization. It is important to identify any cultural factors that may support or hinder the EA initiative. This can be done through surveys, interviews, and workshops with key stakeholders.
2. Assess Current State of IT and Business Alignment: This step involves evaluating how well the IT infrastructure and services are aligned with the business goals and objectives. It includes analyzing the current IT landscape, identifying gaps and inefficiencies, and understanding the level of collaboration between IT and business units.
3. Determine Maturity Level: This involves assessing the maturity of existing governance processes and EA capability. It includes evaluating the current practices, methodologies, and tools used for EA, as well as the level of expertise and experience within the EA team. This assessment helps in identifying areas for improvement and setting realistic goals for the EA practice.

Second challenge (the what)

Establish EA operational structure

Establishing the operational structure for an Enterprise Architecture (EA) practice involves deciding on the organizational model and determining under which CxO the EA team will report. Here are the key considerations:

1. Centralized Structure: In a centralized structure, the EA team is consolidated under a single CxO, typically the Chief Information Officer (CIO) or Chief Technology Officer (CTO) but also the Chief Executive Officer (CEO), Chief Financial Officer (CFO) or Chief Operating Officer (COO). This model ensures consistent standards and practices across the organization, providing a unified approach to architecture and governance.
2. Federated Structure: A federated structure involves a hybrid approach where the EA team is distributed across different business units or departments, but there is a central coordinating body. This model allows for flexibility and responsiveness to specific business needs while maintaining overall alignment with the organization's strategic goals. The EA team may report to multiple CxOs.
3. Feudal Structure: In a feudal structure, the EA team operates independently within different business units or departments, with little to no central coordination. Each unit has its own EA team that reports to its respective CxO. This model allows for maximum autonomy and customization but may lead to inconsistencies and misalignment across the organization.

When deciding on the operational structure, it is important to consider the organization's size, complexity, and strategic objectives. The chosen structure should support effective communication, collaboration, and governance, ensuring that the EA practice can deliver value to the organization.

Build the EA team and determine objectives

Building the EA team and determining objectives are crucial steps in establishing an Enterprise Architecture (EA) practice. Here are the key considerations.

Building the EA Team:

• Identify Key Roles: Determine the essential roles needed for the EA team, such as Enterprise Architects, Solution Architects, and Business Analysts. Each role should have clearly defined responsibilities and required skills.
• Recruit and Train: Recruit individuals with the necessary expertise and experience. Provide training and development opportunities to ensure the team is well-equipped to handle the EA practice's demands.
• Foster Collaboration: Encourage collaboration within the EA team and with other departments. This can be achieved through regular meetings, workshops, and cross-functional projects.

Determining Objectives:

• Align with Business Goals: Ensure that the objectives of the EA practice align with the organization's overall business goals and strategic direction.
• Set Specific, Measurable Goals: Define clear and measurable objectives for the EA practice. These could include improving IT and business alignment, enhancing operational efficiency, or achieving compliance with regulatory requirements.

Decide the EA scope

Deciding the enterprise scope is a critical step in establishing an Enterprise Architecture (EA) practice. This involves determining the breadth and depth of the EA practice within the organization. Here are the key considerations:

1. Define the Scope: Clearly articulate the boundaries of the EA practice. This includes identifying which parts of the organization will be included in the EA efforts and which will not. The scope can be defined in terms of business units, geographical regions, or specific processes and systems.
2. Engage Stakeholders: Involve key stakeholders in the decision-making process to ensure that their needs and expectations are considered. This includes business leaders, IT leaders, and other relevant parties. Their input is crucial in defining a scope that is realistic and achievable.
3. Set Priorities: Identify and prioritize the key areas that the EA practice will focus on. This could include specific business processes, systems, or technologies that are critical to the organization's success. Prioritization helps in allocating resources effectively and ensuring that the most important areas are addressed first.
4. Document the Scope: Clearly document the defined scope, including the boundaries, priorities, and any assumptions or constraints. This documentation serves as a reference for the EA team and other stakeholders, ensuring that everyone is aligned and aware of the scope.

Third challenge (the how)

Establish EA governance

Establishing the authority level given to the Enterprise Architecture (EA) team and defining governance processes are crucial steps in ensuring the success of the EA practice. Here are the key considerations:

1. Define Authority Levels: Clearly articulate the decision-making authority and responsibilities of the EA team. This includes specifying the scope of their influence over architectural decisions, standards, and policies. The authority level should be aligned with the organization's strategic goals and should enable the EA team to effectively drive architectural initiatives.
2. Establish Governance Processes: Governance processes are essential for ensuring that architectural decisions are made consistently and transparently. This involves setting up committees or boards that oversee the EA practice, defining roles and responsibilities, and establishing procedures for decision-making, conflict resolution, and compliance monitoring.
3. Engage Stakeholders: Involve key stakeholders in the governance processes to ensure their buy-in and support. This includes business leaders, IT leaders, and other relevant parties. Their involvement helps in aligning the EA practice with the organization's strategic objectives and ensures that architectural decisions are well-informed and accepted.
4. Implement Monitoring and Reporting Mechanisms: Establish mechanisms for monitoring the progress and effectiveness of the EA practice. This includes setting up regular reporting processes, performance metrics, and feedback loops. Monitoring and reporting help in identifying areas for improvement and ensuring that the EA practice delivers value to the organization.
5. Communicate and Educate: Ensure that the authority levels and governance processes are clearly communicated to all relevant parties. Provide training and education to stakeholders to ensure they understand their roles and responsibilities within the governance framework. Effective communication and education help in fostering a culture of collaboration and compliance.

?

?

Choose EA tools, methods and/or frameworks

Choosing the appropriate tools, methods, and frameworks is a critical step in establishing an Enterprise Architecture (EA) practice. Here are the key considerations:

1. Evaluate Available Options: Research and evaluate the various tools, methods, and frameworks available in the market. Consider factors such as functionality, ease of use, scalability, and compatibility with existing systems. Some popular EA frameworks include TOGAF (The Open Group Architecture Framework), Zachman Framework, and FEAF (Federal Enterprise Architecture Framework).
2. Consider Industry Standards: Choose tools and frameworks that are widely recognized and accepted in the industry. This ensures that your EA practice aligns with best practices and can easily integrate with other industry-standard processes and systems.
3. Assess Integration Capabilities: Ensure that the chosen tools and frameworks can seamlessly integrate with your organization's existing systems and processes. This includes evaluating the compatibility with current IT infrastructure, data management systems, and other enterprise applications.
4. Pilot and Test: Before fully implementing the chosen tools and frameworks, conduct a pilot test to evaluate their effectiveness and suitability for your organization. This helps in identifying any potential issues and making necessary adjustments before full-scale implementation.
5. Provide Training and Support: Ensure that the EA team and other relevant stakeholders are adequately trained on the chosen tools and frameworks. Provide ongoing support and resources to help them effectively utilize these tools and frameworks in their daily activities.
6. Monitor and Review: Continuously monitor the performance and effectiveness of the chosen tools and frameworks. Regularly review and update them to ensure they remain aligned with the evolving needs and goals of the organization.

Adopting an Enterprise Architecture (EA) tool can indeed introduce costs associated with maintaining it up-to-date. These costs can include software licensing fees, regular updates, training for staff, and potential integration with existing systems.

Benefits

Establishing an Enterprise Architecture (EA) practice offers numerous benefits that can significantly enhance an organization's efficiency, agility, and alignment with business goals.

Here are some key benefits:

• Improved Efficiency: EA practices streamline processes and reduce operational costs by providing a structured approach to managing IT and business processes.
• Better Alignment of IT with Business Goals: EA ensures that IT initiatives support and enhance the overall business strategy, leading to better alignment between IT and business units.
• Enhanced Agility: EA practices enable organizations to quickly adapt to market changes and new opportunities by providing a flexible and scalable IT infrastructure.
• Compliance with Regulatory Requirements: EA helps organizations meet legal and regulatory standards, reducing the risk of penalties and ensuring smooth operations.
• Improved System Flexibility and Scalability: EA practices enhance system flexibility, scalability, and performance, making it easier to accommodate growth and changes in business needs.
• Optimized Resource Utilization: EA practices improve resource effectiveness by leveraging best practices, design patterns, and clear guidelines, leading to increased economies of scale.
• Reduced Costs: EA practices can lead to reduced application development, testing, and data interface costs, as well as reduced IT system outages by leveraging standards.
• Improved Technology Awareness and Training: EA practices enhance technology awareness and provide training opportunities, leading to improved IT employee satisfaction and reduced churn.
• Enhanced Credibility and Relationships: EA practices improve credibility and relationships with business areas by providing a clear and consistent approach to managing IT and business processes.

Conclusion

Establishing an Enterprise Architecture (EA) practice is a comprehensive and strategic endeavor that involves several key challenges and steps. The process begins with defining the vision, business drivers, and goals, and assessing the current culture, context, and maturity. It then moves on to establishing the operational structure, building the EA team, determining objectives, and deciding the enterprise scope. Finally, it focuses on establishing the authority level and governance processes, and choosing the appropriate tools, methods, and frameworks.

By carefully addressing each of these challenges and following the outlined steps, organizations can successfully set up an EA practice that aligns with strategic objectives and delivers long-term benefits. The EA practice will provide a structured approach to managing and optimizing the organization's IT and business processes, ultimately enhancing efficiency, agility, and alignment with business goals.

Now you are ready to start running your EA practice and reaping the long-term benefits.

?

USEFUL READINGS

Enterprise Architecture vs. Enterprise Anarchy: The Cost of No EA

A Comprehensive Approach to Enterprise Architecture and Solution Delivery

Decoding EA – The Role, The Title, and The Practice

The Return of Enterprise Architecture as Business Strategy

How many (IT) Architects do I need?

A Simple Guide to Business Architecture Concepts and Models