Linked.Archi EA on a Page Taxonomy
SKOS taxonomy of the 24 EA artifacts identified by Kotusev across 27+ organizations, classified by the CSVLOD types and usage frequency. Also includes the EA Maturity Model (Stage Zero through Stage Three) and the EA Governance classification (architecture tiers, governance bodies, governance activities).
Linked.Archi
EA on a Page Artifact Classification
Classification of 24 EA artifacts by CSVLOD type and usage frequency.
Considerations
Global conceptual rules for IT governance — principles, policies, guidelines.
Standards
Proven reusable solutions — technology reference models, patterns, guidelines.
Visions
High-level future-state descriptions — capability models, target architectures, roadmaps.
Landscapes
Current-state descriptions — landscape diagrams, inventories, portfolios.
Outlines
Initiative-level architecture — solution overviews, options assessments.
Designs
Project-level specifications — solution designs, detailed technical specs.
Principles
High-level policy statements guiding IT-related decision-making across the organization.
Policies
Specific mandatory rules and regulations governing IT decisions and operations.
Conceptual Architectures
High-level conceptual models describing the fundamental structure of the IT landscape.
Guidelines
Non-mandatory recommendations and best practices for IT-related activities.
Technology Reference Models
Structured catalogs of approved technologies organized by functional area with lifecycle status.
Patterns
Proven reusable solution templates for common architectural problems.
IT Principles
Technology-specific principles governing the selection and use of IT components.
Technology Guidelines
Detailed technical recommendations for implementing approved technologies.
Business Capability Models
Structured maps of business capabilities showing what the organization does, independent of how.
Target State Architectures
Descriptions of the desired future state of the IT landscape aligned with business strategy.
Roadmaps
Sequenced plans showing the transition from current state to target state over time.
Value Chains
Descriptions of how value flows through the organization from input to customer outcome.
Landscape Diagrams
High-level visual maps of the current IT landscape showing systems and their relationships.
Inventories
Structured lists of IT assets — applications, technologies, interfaces, data stores.
Enterprise System Portfolios
Assessed collections of enterprise systems with lifecycle status, fitness, and ownership data.
Integration Maps
Diagrams showing data flows and integration points between enterprise systems.
Solution Overviews
High-level descriptions of proposed solutions showing key components and their interactions.
Options Assessments
Comparative evaluations of alternative solution approaches with trade-off analysis.
Initiative Architectures
Architecture descriptions scoped to a specific initiative or program of work.
Architecture Briefs
Concise summaries of architectural decisions and direction for a specific initiative.
Solution Designs
Detailed technical designs of specific solutions with component specifications.
Detailed Specifications
Low-level technical specifications for implementation — interface contracts, data models, deployment configs.
Interface Contracts
Formal specifications of interfaces between systems — APIs, message formats, protocols.
Deployment Architectures
Descriptions of how solutions are deployed to infrastructure — environments, topology, scaling.
EA on a Page Maturity Model
Classification of EA practice maturity into four stages based on empirical observation across 27+ organizations. Describes what is typically observed at each stage, not what should be achieved in a linear progression.
Stage Zero — No Architecture
Stage 0
No established EA practice. IT decisions are made ad hoc by individual project teams without overarching governance, standards, or strategic alignment. There are no dedicated architecture roles, no shared artifacts, and no architecture governance bodies.
Typical characteristics: no EA artifacts in use, no architecture roles, no governance arrangements, no strategic IT planning. IT is purely reactive.
Duplicate systems and redundant technologies proliferate unchecked.
IT investments are not aligned with business strategy.
No shared understanding of the IT landscape across the organization.
Integration between systems is ad hoc and fragile.
Stage One — IT Optimization
Stage 1
EA practice focused on technology rationalization. Standards and Landscapes are the primary artifacts. The Technology Optimization process is established. Architecture governance is informal or limited to technology standards compliance.
Typical artifacts: Technology Reference Models, Landscape Diagrams, Inventories. Typical roles: enterprise architects focused on technology. Governance: informal technology standards review.
Reduced technology duplication through standards enforcement.
Shared visibility of the current IT landscape.
More informed technology selection decisions.
EA perceived as IT-only function with limited business engagement.
Architecture governance may be seen as bureaucratic overhead.
Difficulty demonstrating business value of EA practice.
Stage Two — Solution Delivery
Stage 2
EA practice extends to guiding project delivery. Initiative Delivery process is established alongside Technology Optimization. Outlines and Designs are produced for major initiatives. Solution architect roles emerge. Architecture review becomes a formal gate in the project lifecycle.
Typical artifacts: all Stage One artifacts plus Solution Overviews, Options Assessments, Solution Designs. Typical roles: enterprise architects and solution architects. Governance: formal architecture review board for project-level decisions.
Improved solution quality through architecture review.
Better standards compliance in project implementations.
Reduced rework through early architecture guidance.
Reuse of proven patterns and reference architectures.
Architecture review may slow project delivery if not well-integrated.
Tension between enterprise standards and project-specific needs.
Strategic alignment still limited without business engagement.
Stage Three — Enterprise Architecture
Stage 3
Full EA practice with all three processes established. Strategic Planning is active, producing Considerations and Visions that guide investment decisions. All six CSVLOD artifact types are in use. Architecture governance spans from enterprise strategy to project delivery. Business leaders actively participate in architecture-informed strategic planning.
Typical artifacts: all 24 artifacts across all six CSVLOD types. Typical roles: enterprise architects, solution architects, business leaders, IT leaders. Governance: multi-tier governance with strategic and operational review bodies, formal escalation paths, and governed artifact lifecycle.
IT investments aligned with business strategy.
Business leaders actively engaged in architecture-informed planning.
Coherent technology landscape with managed evolution.
Consistent solution quality across the portfolio.
Reduced total cost of ownership through rationalization and reuse.
Sustaining business engagement over time.
Keeping architecture artifacts current as the organization evolves.
Balancing governance rigor with organizational agility.
Measuring and communicating the value of EA to the business.
EA on a Page Governance Classification
Classification of EA governance arrangements including architecture tiers, governance body types, and governance activities. Based on EA Function on a Page by Kotusev.
Architecture Tiers
Levels in the architecture governance hierarchy.
One-Tier Model
A single EA team handles all architecture activities — strategic planning, technology optimization, and initiative delivery. Typical in smaller organizations or early-maturity EA practices.
Two-Tier Model
Enterprise architects handle strategic and technology artifacts (Considerations, Visions, Standards, Landscapes) while solution architects handle initiative-level artifacts (Outlines, Designs). The most common governance model observed in practice.
Three-Tier Model
Adds a domain or segment architecture layer between enterprise and solution tiers. Domain architects manage domain-specific standards, landscapes, and cross-initiative coordination. Typical in large, complex organizations.
Governance Bodies
Types of organizational bodies that govern architecture decisions.
Architecture Review Board
A governance body that reviews and approves architecture artifacts, particularly Outlines and Designs, for standards compliance and strategic alignment. Typically operates at the solution/project tier.
Steering Committee
A senior governance body that oversees strategic architecture direction, approves Visions and Considerations, and resolves escalated architecture decisions. Typically includes business and IT leaders.
Technology Council
A governance body focused on technology standards and landscape rationalization. Reviews and approves Standards artifacts, manages the Technology Reference Model, and governs technology lifecycle decisions.
Governance Activities
Types of governance activities in an EA practice.
Architecture Review
Review of architecture artifacts against standards, principles, and strategic direction.
Approval
Formal approval of an architecture artifact or initiative to proceed.
Amendment
Modification of an approved architecture artifact to reflect changed requirements.
Exemption
Temporary deviation from established standards or principles for a specific initiative.
Escalation
Escalation of a decision or conflict to a higher-tier governance body.