Back to Guides

EA organizational structure

Guideline for developing the internal organisational structure and hierarchy of the EA practice team: roles, responsibilities, job descriptions, and the organisational placement of the practice within the entity.

Guideline for developing the internal organisational structure and hierarchy of the EA practice team: roles, responsibilities, job descriptions, and the organisational placement of the practice within the entity.

In brief

8
functional roles
4
steps
2
annexes
Description: internal structure and hierarchy of the EA team, with roles, responsibilities, required experience, job descriptions, and the organisational placement of the EA practice.
Objectives: a clear decision path for effective management and continuity; clarity of roles and responsibilities so tasks and services are delivered in a structured, integrated way.
Outputs: list of roles, approved structure, unit founding document, job descriptions, and outsourcing frameworks.

Description

The organisational structure is the internal structure and hierarchy of the team that applies and activates EA practice in the entity. It clarifies functional roles and responsibilities, required experience, job descriptions, and reporting lines, and defines where the EA practice sits in the entity's overall structure. The aim is to design an effective structure that ensures efficient workflow and alignment with the practice's tasks, activities, services, and related strategic objectives.

Objectives of building the structure

A clear decision path for effective management, continuity, and delivery on time.

Clarity of roles and responsibilities in the organisational unit so that tasks are met and services and procedures are delivered in a structured, integrated way.

Inputs / organisational data sources

EA tasks: approved tasks (current or as defined in EA tasks) to understand the practice's scope and focus areas.

EA services: approved or defined EA services.

Entity organisational structure: entity functions that may intersect with EA (e.g. planning, organisational excellence, IT, data management, cybersecurity).

Steps

1

Define and detail functional roles

Analyse approved tasks and services to identify the capabilities and skills the EA unit needs to activate the practice, execute tasks, and deliver services to beneficiaries. Detail the job description for each role (qualifications, responsibilities, professional certifications) as in the job descriptions annex.

2

Define the structure model and sourcing

Choose the structure model that fits the entity, with defined roles reporting to the Chief Enterprise Architect (unit manager). Choose the most appropriate sourcing for each role (detailed in the outsourcing frameworks annex).

3

Define structure placement and practice sponsor

Review EA strategy to choose the best placement. Either: strategy-focused ? practice sponsor in the strategy line (e.g. head of strategy development); or IT-focused ? practice sponsor in the operational line (e.g. Chief Information Officer).

Note: the scope of EA work does not change with organisational placement; all defined EA tasks must be delivered.

4

Prepare the founding document

Prepare the EA practice founding document with approved tasks, proposed structure, roles and responsibilities, and job description links. Have it reviewed by HR for approvals and structure adoption. Adopting the model may require changes to the entity's structure; these are considered and approved by the relevant departments per entity policy.

Example roles (activating EA practice)

Chief Enterprise Architect (unit manager)

Lead, direct, and manage the EA practice team and provide support and recommendations across all EA domain activities (business, experience, applications, data, technology, security).

Business architecture engineer

Translate business strategies and procedures into elements for EA practice; develop reference and other EA designs; provide inputs for EA initiative prioritisation; maintain knowledge of entity unit activities and tasks.

Data architecture engineer

Develop data architecture components and data exchange (integration) in line with business and entity requirements and data controls; focus on technical standards and data EA principles; define the need for data EA designs.

Applications architecture engineer

Develop applications architecture components in line with business and entity needs; focus on technical standards and applications EA principles; define the need for applications EA reference designs.

Technology (infrastructure) architecture engineer

Develop technology architecture components using business and entity requirements and technical constraints; focus on technology EA standards and principles; define the need for related EA designs.

Security architecture engineer

Develop security technical components used to protect and ensure compliance of other EA domain components with security requirements and standards (e.g. cybersecurity, information security).

Beneficiary experience architecture engineer

Develop experience architecture components (journeys, personas, design elements); identify experience improvement opportunities and close gaps between experience, business, and technology; ensure solutions deliver a unified experience for internal and external beneficiaries.

EA tool administrator

Manage and update EA tool users and permissions, provide technical support, and develop periodic reports and dashboards on the tool.

Criteria for choosing organisational reporting

Strategy-focused

Focus: support strategy development and roadmap choice; large strategic digital projects and initiatives.

IT-focused

Focus: align IT capabilities with business strategy; technology alignment, technical architecture development, standards and operational digital improvement.

Expected outputs

List of functional roles for activating EA practice

Approved organisational structure for activating EA practice in the entity

Approved founding document for the EA unit with the responsible sponsor

Job descriptions (details in annex)

Annexes

Job descriptions

Job description cards for EA practice roles: Chief Enterprise Architect, business architecture engineer, beneficiary experience engineer, data architecture engineer, applications architecture engineer, technology architecture engineer, security architecture engineer, EA tool administrator. Each card includes: job title, line manager, tasks and responsibilities, qualifications and core competencies, years of experience, degree.

Outsourcing frameworks

Assess complexity of entity operations and EA practice scope (tasks, services, procedures) to estimate demand for EA services. Determine headcount per role. Define outsourcing frameworks aligned with entity policy: three types (internal employment, contract, consulting) to fill the roles required to activate the EA structure.

Outputs in brief

A clear organisational structure for the EA unit; detailed job descriptions for the eight roles; and appropriate outsourcing frameworks (internal/contract/consulting) to activate the structure per NORA and maturity requirements.

Related topics

Establishing EA practice

Governance & committees

Maturity measurement