Architecting the IT Organization: Clarifying the Contributions of Enterprise Architecture, IT Governance, and ITSM to the IT Value Chain

Clear Scopes and Responsibilities Enable the IT Value Chain

As the examples above illustrate, EA, IT governance, and ITSM can contribute most effectively when their scope is well defined and understood. As these practice areas grow together in an organization, their scope should be discussed and aligned. Otherwise, these practices may inadvertently develop competing visions that can disrupt the IT value chain.

Without coordination, practitioners in EA, IT governance, and ITSM in your organization could all reasonably believe that they hold primary responsibility for enabling key parts of the IT value chain. A reasonable perspective from each practice area could be:

  • Enterprise Architecture: "We work with teams and managers at all levels to increase alignment of IT with institutional needs. We proposed the current IT governance structure, operate it, and are key to the IT organization's relationships with non-IT stakeholders. We help the organization mature all its internal processes, of which ITSM processes are one important part."
  • IT Governance: "We align IT to institutional goals, define IT strategy, and identify institutional outcomes for IT. We prioritize not only what services ITSM should work on but also the resources allocated to service management itself. Regarding EA, we direct its strategic priorities like any other IT service."
  • IT Service Management: "We lead IT's long-term roadmap for how to manage and grow itself as an organization—all of its services, products, processes, resources, and assets. IT governance and EA are both functions that contribute within the overall ITSM approach."

As these statements suggest, EA, IT governance, and IT service management have the potential to intersect in their contributions to the IT value chain in IT strategy and portfolio management, in engagement with non-IT stakeholders, and in guiding the design of IT products, services, and processes (figure 3).

graphic representation of the intersection of the contributions of EA, IT governance, and IT service management to the IT value chain in IT strategy and portfolio management, in engagement with non-IT stakeholders, and in guiding the design of IT products, services, and processes
Figure 3. Typical intersections of EA, IT governance, and ITSM

An IT organization's capabilities at these intersections directly affect its ability to react to changes, including digital transformation and all its impacts on the institution. These capabilities represent the IT organization's ability to integrate the strategic vision of the institution and respond with effective service delivery. To support discussion in your IT organization, typical activities in each capability are shown in table 2. You should feel free to add activities that are important to your organization.

Table 2. Capabilities and typical activities

Capability Typical Activities
IT Strategy
  • Review institutional strategies to identify drivers for IT.
  • Assess industry trends in higher education IT to identify drivers for IT.
  • Propose and gain agreement on IT strategies, including drivers, goals, initiatives, and measures of success.
  • Work with IT teams to develop their specific strategies in greater detail.
IT Portfolio Management
  • Based on agreed-upon strategies, prioritize investment in IT services and projects.
  • Review current IT services relative to demand.
  • Propose, review, and prioritize new or changing IT services.
  • Propose roadmaps of IT projects.
  • Review and prioritize proposed IT projects.
  • Resolve escalated issues as projects are executed.
Engagement with Non-IT Stakeholders
  • Assess demand for and satisfaction with IT products and services.
  • Work with non-IT stakeholders to define measures of value for IT.
  • Engage non-IT stakeholders in productive relationships with IT at multiple levels.
  • Ensure that non-IT stakeholders and institutional needs are represented in decision-making about, and within, IT projects and services.
Guiding the Design of IT Products, Services, and Processes
  • Translate from strategy, investment, and portfolio decisions to high-level design for specific products, services, and processes.
  • Define decision-making about and delegation of accountability for design of products, services, and processes.
  • Establish architectural guidelines or standards for the design of products, services, and processes.
  • Establish processes by which guidelines or standards are applied and design decisions are reviewed as needed.
  • Ensure that the designs are based on thorough understanding of actual needs.