Linked.Archi EA on a Page Taxonomy

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.

  See Also: Consideration

  https://meta.linked.archi/eaonapage/tax#ConsiderationsGroup
  • Principles
    High-level policy statements guiding IT-related decision-making across the organization.

    https://meta.linked.archi/eaonapage/tax#Principles
  • Policies
    Specific mandatory rules and regulations governing IT decisions and operations.

    https://meta.linked.archi/eaonapage/tax#Policies
  • Conceptual Architectures
    High-level conceptual models describing the fundamental structure of the IT landscape.

    https://meta.linked.archi/eaonapage/tax#Conceptual_Architectures
  • Guidelines
    Non-mandatory recommendations and best practices for IT-related activities.

    https://meta.linked.archi/eaonapage/tax#Guidelines
• ▼Standards
  Proven reusable solutions — technology reference models, patterns, guidelines.

  See Also: Standard

  https://meta.linked.archi/eaonapage/tax#StandardsGroup
  • Technology Reference Models
    Structured catalogs of approved technologies organized by functional area with lifecycle status.

    https://meta.linked.archi/eaonapage/tax#Technology_Reference_Models
  • Patterns
    Proven reusable solution templates for common architectural problems.

    https://meta.linked.archi/eaonapage/tax#Patterns
  • IT Principles
    Technology-specific principles governing the selection and use of IT components.

    https://meta.linked.archi/eaonapage/tax#IT_Principles
  • Technology Guidelines
    Detailed technical recommendations for implementing approved technologies.

    https://meta.linked.archi/eaonapage/tax#Technology_Guidelines
• ▼Visions
  High-level future-state descriptions — capability models, target architectures, roadmaps.

  See Also: Vision

  https://meta.linked.archi/eaonapage/tax#VisionsGroup
  • Business Capability Models
    Structured maps of business capabilities showing what the organization does, independent of how.

    https://meta.linked.archi/eaonapage/tax#Business_Capability_Models
  • Target State Architectures
    Descriptions of the desired future state of the IT landscape aligned with business strategy.

    https://meta.linked.archi/eaonapage/tax#Target_State_Architectures
  • Roadmaps
    Sequenced plans showing the transition from current state to target state over time.

    https://meta.linked.archi/eaonapage/tax#Roadmaps
  • Value Chains
    Descriptions of how value flows through the organization from input to customer outcome.

    https://meta.linked.archi/eaonapage/tax#Value_Chains
• ▼Landscapes
  Current-state descriptions — landscape diagrams, inventories, portfolios.

  See Also: Landscape

  https://meta.linked.archi/eaonapage/tax#LandscapesGroup
  • Landscape Diagrams
    High-level visual maps of the current IT landscape showing systems and their relationships.

    https://meta.linked.archi/eaonapage/tax#Landscape_Diagrams
  • Inventories
    Structured lists of IT assets — applications, technologies, interfaces, data stores.

    https://meta.linked.archi/eaonapage/tax#Inventories
  • Enterprise System Portfolios
    Assessed collections of enterprise systems with lifecycle status, fitness, and ownership data.

    https://meta.linked.archi/eaonapage/tax#Enterprise_System_Portfolios
  • Integration Maps
    Diagrams showing data flows and integration points between enterprise systems.

    https://meta.linked.archi/eaonapage/tax#Integration_Maps
• ▼Outlines
  Initiative-level architecture — solution overviews, options assessments.

  See Also: Outline

  https://meta.linked.archi/eaonapage/tax#OutlinesGroup
  • Solution Overviews
    High-level descriptions of proposed solutions showing key components and their interactions.

    https://meta.linked.archi/eaonapage/tax#Solution_Overviews
  • Options Assessments
    Comparative evaluations of alternative solution approaches with trade-off analysis.

    https://meta.linked.archi/eaonapage/tax#Options_Assessments
  • Initiative Architectures
    Architecture descriptions scoped to a specific initiative or program of work.

    https://meta.linked.archi/eaonapage/tax#Initiative_Architectures
  • Architecture Briefs
    Concise summaries of architectural decisions and direction for a specific initiative.

    https://meta.linked.archi/eaonapage/tax#Architecture_Briefs
• ▼Designs
  Project-level specifications — solution designs, detailed technical specs.

  See Also: Design

  https://meta.linked.archi/eaonapage/tax#DesignsGroup
  • Solution Designs
    Detailed technical designs of specific solutions with component specifications.

    https://meta.linked.archi/eaonapage/tax#Solution_Designs
  • Detailed Specifications
    Low-level technical specifications for implementation — interface contracts, data models, deployment configs.

    https://meta.linked.archi/eaonapage/tax#Detailed_Specifications
  • Interface Contracts
    Formal specifications of interfaces between systems — APIs, message formats, protocols.

    https://meta.linked.archi/eaonapage/tax#Interface_Contracts
  • Deployment Architectures
    Descriptions of how solutions are deployed to infrastructure — environments, topology, scaling.

    https://meta.linked.archi/eaonapage/tax#Deployment_Architectures

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.

  Scope Note: Typical characteristics: no EA artifacts in use, no architecture roles, no governance arrangements, no strategic IT planning. IT is purely reactive.

  https://meta.linked.archi/eaonapage/tax#StageZero
• 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.

  Scope Note: Typical artifacts: Technology Reference Models, Landscape Diagrams, Inventories. Typical roles: enterprise architects focused on technology. Governance: informal technology standards review.

  https://meta.linked.archi/eaonapage/tax#StageOne
• 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.

  Scope Note: 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.

  https://meta.linked.archi/eaonapage/tax#StageTwo
• 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.

  Scope Note: 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.

  https://meta.linked.archi/eaonapage/tax#StageThree

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.

  https://meta.linked.archi/eaonapage/tax#ArchitectureTiersGroup
  • 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.

    https://meta.linked.archi/eaonapage/tax#OneTierModel
  • 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.

    https://meta.linked.archi/eaonapage/tax#TwoTierModel
  • 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.

    https://meta.linked.archi/eaonapage/tax#ThreeTierModel
• ▼Governance Bodies
  Types of organizational bodies that govern architecture decisions.

  https://meta.linked.archi/eaonapage/tax#GovernanceBodiesGroup
  • 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.

    https://meta.linked.archi/eaonapage/tax#ArchitectureReviewBoard
  • 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.

    https://meta.linked.archi/eaonapage/tax#SteeringCommittee
  • 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.

    https://meta.linked.archi/eaonapage/tax#TechnologyCouncil
• ▼Governance Activities
  Types of governance activities in an EA practice.

  https://meta.linked.archi/eaonapage/tax#GovernanceActivitiesGroup
  • Architecture Review
    Review of architecture artifacts against standards, principles, and strategic direction.

    See Also: ArchitectureReview

    https://meta.linked.archi/eaonapage/tax#ReviewActivity
  • Approval
    Formal approval of an architecture artifact or initiative to proceed.

    See Also: Approval

    https://meta.linked.archi/eaonapage/tax#ApprovalActivity
  • Amendment
    Modification of an approved architecture artifact to reflect changed requirements.

    See Also: Amendment

    https://meta.linked.archi/eaonapage/tax#AmendmentActivity
  • Exemption
    Temporary deviation from established standards or principles for a specific initiative.

    See Also: Exemption

    https://meta.linked.archi/eaonapage/tax#ExemptionActivity
  • Escalation
    Escalation of a decision or conflict to a higher-tier governance body.

    See Also: Escalation

    https://meta.linked.archi/eaonapage/tax#EscalationActivity