- Atlas
- Business, Management & Finance
- It Governance
It Governance
IT governance is the set of arrangements by which an organization decides how computing is used, who gets to make which technology decisions, and how anyone knows whether the money was well spent.
10 frameworks, from 1975 to today · Information Systems · Business, Management & Finance
- COBIT 1975-Present
- Enterprise Architecture Governance 1987-Present
- ITIL 1989-Present
- Strategic Alignment Model 1993-2010
- Relational Governance 1995-Present
- IT Risk and Compliance Governance 2002-Present
- IT Decision Rights and Governance Archetypes 2004-Present
- Data Governance 2005-Present
- Data and Algorithmic Governance 2015-Present
- Government by algorithm 2016-Present
Overview
IT governance is the set of arrangements by which an organization decides how computing is used, who gets to make which technology decisions, and how anyone knows whether the money was well spent1. It is not the same as managing IT projects; it is the layer above, where authority, accountability, and priorities are settled1. The stakes are concrete: a bank that lets every division buy its own systems ends up with incompatible records and no single view of a customer, while a firm that centralizes every decision can strangle the business units that actually understand the market. The history of the field is a long argument about where that line should fall, and about what tools—frameworks, committees, contracts, architectures—can hold it in place.
Auditing the Machine: Control Frameworks from the 1970s
The earliest systematic IT governance was financial. As mainframe systems became the place where accounting records lived, auditors needed a way to assure that those records were complete and trustworthy. The answer was the control objective: a statement of what a well-run system should achieve, paired with tests of whether it does. In the United States, the EDP Auditors Association (founded 1969, later ISACA) built a body of guidance around these ideas, and in 1996 it published COBIT—Control Objectives for Information and Related Technology. COBIT organized controls around information criteria (effectiveness, efficiency, confidentiality, integrity, availability, compliance, reliability) and around processes, giving auditors and managers a common checklist.
COBIT's significance was that it treated IT as a governance object rather than a technical specialty. Its later editions (COBIT 4.1 in 2007, COBIT 5 in 2012, COBIT 2019) moved from an audit checklist toward a full framework of processes, goals, and accountability, explicitly separating governance from management: governance sets direction and monitors, management plans and executes. The framework's weakness was always the same—it told you what good control looked like, not how to make hard trade-offs between competing business demands.
Service Management and the Process View
A parallel tradition came from operations. British government computing in the 1980s produced a set of practices for running IT services, codified as the IT Infrastructure Library (ITIL), first published in the late 1980s2. ITIL's insight was that IT should be understood as a service delivered to customers under agreed terms, not as a set of machines2. Its central device, the service-level agreement, made the relationship between IT and the business explicit and measurable. ITIL's process catalog—incident management, change management, problem management, configuration management—gave organizations a shared vocabulary, and its widespread adoption in the 1990s and 2000s made "IT service management" a profession in its own right.
ITIL and COBIT were often used together: ITIL described how services run, COBIT described how they are controlled. Both shared a limitation that critics pressed hard. They were normative—they described good practice in general—and they said little about why organizations with similar frameworks performed differently. That question pushed the field toward empirical research.
Alignment: The Problem That Named the Field
The idea that gave IT governance its modern identity was strategic alignment: the fit between business strategy and IT strategy. In 1993, John Henderson and N. Venkatraman published the Strategic Alignment Model, which mapped four domains—business strategy, IT strategy, organizational infrastructure, and IT infrastructure—and described how a change in one could be carried through to the others. The model's practical contribution was to show that alignment could be driven from either direction: from business strategy down through IT, or from an IT capability outward into new business options.
Alignment research dominated the 1990s and early 2000s. Its finding, repeated across many surveys, was that firms reporting better alignment also reported better performance—though the causal direction was always contested. The deeper contribution was conceptual: alignment reframed IT spending as a strategic question rather than a cost question, and it gave executives a language for asking whether their technology investments matched their intentions.
Who Decides? Decision Rights and Relational Governance
The alignment literature described what should fit; it did not say who should decide. That gap was filled in the mid-2000s by work on IT decision rights. The most influential statement was Peter Weill and Jeanne Ross's IT Governance (2004), which argued that governance is fundamentally about specifying decision rights and accountability for five key areas: IT principles, IT architecture, IT infrastructure, business application needs, and IT investment. Their framework distinguished archetypes—business monarchy, IT monarchy, federal, IT duopoly, feudal, and anarchy—and observed that high-performing firms tended to use a federal arrangement, mixing central and divisional authority.
Around the same time, a complementary line of work examined relational governance mechanisms: the informal and contractual devices that coordinate IT relationships across organizational boundaries. Research on outsourcing showed that contracts alone could not govern complex IT relationships; trust, shared norms, and repeated interaction did much of the work. This literature connected IT governance to transaction-cost economics and to the broader study of interorganizational relationships, and it explained why two firms with identical formal structures could govern IT very differently.
Architecture as a Governance Instrument
If decision rights say who decides, enterprise architecture says what the decisions must fit together. The discipline of describing an organization's business processes, data, applications, and technology in an integrated model emerged in the late 1980s and 1990s, with frameworks such as the Zachman Framework (1987) and The Open Group Architecture Framework (TOGAF, first published 1995). Architecture governance—the review boards, standards, and exception processes that enforce architectural principles—became a recognized governance mechanism in its own right.
The practical case is easy to state. A firm that lets each business unit choose its own customer database saves money in the short term and pays for it in integration costs for a decade. Architecture governance exists to make those trade-offs visible before they are locked in. Its persistent difficulty is that architecture standards constrain exactly the local flexibility that business units value, so architecture boards are perpetually negotiating between central design and local autonomy—the same tension the decision-rights literature had identified.
Risk, Compliance, and the Regulatory Turn
The 2000s brought a shift in the environment. Corporate scandals and the regulations that followed—most visibly the U.S. Sarbanes-Oxley Act of 2002—made IT controls a legal matter, not merely a managerial one. IT risk and compliance governance grew as a distinct concern: identifying technology-related risks, mapping them to controls, and demonstrating to regulators and auditors that the controls operate. Frameworks such as COBIT were adapted for this purpose, and the role of the chief information security officer rose in prominence.
The regulatory turn had two effects on the field. It raised the status of IT governance inside firms, since boards now had explicit obligations. It also risked reducing governance to compliance—a checklist exercise that satisfied auditors without improving decisions. Researchers repeatedly noted the difference between substantive governance, which changes how resources are allocated, and symbolic governance, which produces documentation. That distinction remains one of the field's central cautions.
Data and Algorithms: Governance Moves Beyond the IT Department
The most recent turning point is the extension of governance from IT systems to data and algorithms. As organizations accumulated large datasets and deployed machine-learning models in decisions about credit, hiring, and pricing, the questions changed. It was no longer only "who approves the system?" but "who is accountable for what the model does, and to whom?" Data governance—the assignment of ownership, quality standards, and access rules for data—became a formal discipline, and algorithmic governance added concerns about bias, explainability, and redress.
This work drew on older governance ideas but also broke from them. Traditional IT governance assumed a bounded organization with clear hierarchy; algorithmic governance must contend with models whose behavior emerges from training data, with vendors who supply opaque systems, and with regulators who demand explanations the technology may not readily provide. The European Union's General Data Protection Regulation (2018) and later AI-specific rules made these concerns legally operative, and the field now treats data and algorithm governance as core to IT governance rather than a specialist annex.
Where the Field Stands
Contemporary IT governance research and practice combine all of these strands. COBIT and ITIL remain widely used as reference frameworks, though practitioners increasingly treat them as vocabularies rather than prescriptions. Decision-rights analysis and the federal archetype remain the standard way to describe authority structures. Enterprise architecture governance persists as the mechanism for enforcing integration. Risk and compliance functions have become permanent fixtures, and data and algorithmic governance are the fastest-growing area.
The open questions are recognizable descendants of the field's oldest tensions. How much centralization is optimal when business units need speed? Do formal frameworks improve outcomes, or do they mainly produce legitimacy? How can governance keep pace with systems—cloud platforms, third-party models—that the organization does not fully control? And how should accountability be assigned when a decision is made partly by an algorithm and partly by a person? The history suggests that each generation of technology reopens the same argument about where authority should sit, and that the answer is always provisional.
References
- Corporate governance of information technology (introduction, Problems), Wikipedia
- ITIL (History, introduction), Wikipedia
The frameworks of It Governance
Each framework is a way of working the field has used: when it held, and the question it answers.
- 1975-Present
COBIT
What controls should a well-run IT system have?
About COBIT
COBIT (Control Objectives for Information and Related Technologies) was introduced in 1996 by the Information Systems Audit and Control Association (ISACA) to address the growing need for structured controls over IT processes. Unlike the earlier Strategic Alignment model that focused on the high-level relationship between business and IT strategies, COBIT provided a detailed, process-oriented framework with specific control objectives. It quickly became the foundation for IT governance practices, offering a shared language for auditors, managers, and executives.The following concepts form the core curriculum of COBIT. First, the distinction between IT governance and management is fundamental, especially from COBIT 5 onward, separating governance (evaluating, directing, monitoring) from management (planning, building, running). Control objectives are the original building blocks—statements of desired outcomes to ensure processes are effectively controlled. COBIT organizes IT activities into a set of standard processes grouped into domains such as Plan and Organize, Acquire and Implement, Deliver and Support, and Monitor and Evaluate. Maturity models, borrowed from the SEI's Capability Maturity Model, provide a scale to assess process performance from non-existent to optimized. The five principles of COBIT 5—meet stakeholder needs, cover the enterprise end-to-end, apply a single integrated framework, enable a holistic approach, and separate governance from management—guide the overall framework. Enablers are factors that influence governance and management achievement, including principles, policies, processes, organizational structures, culture, information, and skills. The goals cascade links stakeholder needs to enterprise goals, IT-related goals, and enabler goals. The process assessment model, aligned with ISO 15504, provides a consistent evaluation of process capability. RACI charts clarify decision rights and accountability by assigning responsible, accountable, consulted, and informed roles. Finally, the generic enabler model describes how enablers are governed and managed.The intellectual history of COBIT begins in the early 1990s when ISACA recognized the need for a framework to guide IT control and audit. The first edition (1996) contained 34 high-level control objectives organized into domains, primarily for auditors. COBIT 2.0 (1998) expanded coverage and introduced maturity models. The third edition (2000) added management guidelines, shifting COBIT from an audit checklist to a governance tool. The most significant overhaul came with COBIT 5 (2012), which integrated insights from Val IT and Risk IT, aligned with ISO 38500, and introduced the principles- and enablers-based approach with a clear separation of governance and management. Throughout its evolution, COBIT has been developed by ISACAThe 11 concepts its tower teaches
- COBIT
- Control Objectives
- Enablers
- Five Principles of COBIT 5
- Generic Enabler Model
- Goals Cascade
- Governance vs. Management
- IT Process Domains
- Maturity Model
- Process Assessment Model
- RACI Chart
- 1987-Present
Enterprise Architecture Governance
How should an organization's systems fit together?
- 1989-Present
ITIL
How should IT services be delivered and measured?
About ITIL
IT Governance is the system by which an organization’s information technology decisions are made, monitored, and aligned with its overall objectives. It is not the management of IT operations themselves—such as running servers, writing code, or providing help-desk support—but rather the framework of accountability, decision rights, and oversight that determines what IT should do, who decides, and how performance is evaluated. The field sits at the intersection of corporate governance, business strategy, and information systems, and it addresses a persistent problem: technology investments are costly, risky, and pervasive, yet without deliberate governance they tend to drift toward technical convenience or departmental silos rather than organizational value.The Central Problem and StakesThe core question of IT governance is deceptively simple: who is entitled to make which IT decisions, and how are those decisions held accountable? In practice, this breaks into several recurring concerns. First, alignment: ensuring that IT investments and priorities support the organization's strategic goals rather than merely reflecting what is technically feasible or what individual departments happen to want. Second, value delivery: determining whether IT spending produces measurable business benefits, and how those benefits are tracked. Third, risk management: deciding how much risk the organization is willing to accept in areas like data security, system downtime, regulatory compliance, and project failure. Fourth, resource allocation: choosing which projects to fund, which to defer, and how to balance innovation against stability. Fifth, performance measurement: defining what “good” looks like for IT and establishing metrics that connect technical activity to business outcomes.The stakes are high because IT is no longer a back-office support function. In most organizations, IT is embedded in products, customer relationships, supply chains, and internal operations. Poor governance can produce spectacular failures—runaway projects, security breaches, incompatible systems, or massive spending with no visible return—while effective governance is associated with better financial performance and strategic agility. Yet the field is not primarily about avoiding disaster; it is about creating a structure in which technology decisions are made deliberately, transparently, and with the right information.Historical DevelopmentIT governance emerged as a distinct discipline in the late 1980s and early 1990s, driven by the growing recognition that technology decisions were too important to be left to technical staff alone. Early frameworks focused on aligning IT with business strategy, often borrowing concepts from corporate governance and strategic management. The field matured through the 1990s and 2000s as organizations sought more systematic approaches to managing technology risk and value, leading to the development of specialized frameworks such as COBIT, ISO/IEC 38500, and ITIL. Each brought a different emphasis: COBIT focused on control objectives and audit, ISO/IEC 38500 on board-level accountability, and ITIL on service management processes. Over time, the field has expanded to include relational mechanisms, governance archetypes, and adaptive approaches that recognize the complexity and dynamism of modern technology environments.Core Concepts and PrinciplesIT governance rests on several foundational concepts. Decision rights define who has the authority to make specific types of IT decisions—such as architecture, infrastructure, applications, and investment priorities. Accountability ensures that individuals or groups are answerable for the outcomes of those decisions. Alignment is the ongoing process of ensuring that IT strategy and business strategy are mutually reinforcing. Value delivery focuses on optimizing IT investments to generate business value, while risk management involves identifying, assessing, and mitigating technology-related risks. Performance measurement uses metrics and KPIs to track whether IT is meeting its objectives. Stakeholder engagement recognizes that effective governance requires input from business leaders, IT leaders, and other key parties. Transparency ensures that decision-making processes and outcomes are visible and understandable to all relevant stakeholders.Framework and MethodologiesSeveral frameworks operationalize IT governance. COBIT (Control Objectives for Information and Related Technologies) provides a comprehensive framework for governing and managing enterprise IT, emphasizing control objectives, risk management, and alignment with business goals. ISO/IEC 38500 is an international standard that provides guiding principles for corporate governance of IT, focusing on the role of the board and executive management. ITIL (Information Technology Infrastructure Library) focuses on IT service management, providing best practices for delivering and supporting IT services. The Strategic Alignment Model (SAM) emphasizes the alignment between business and IT strategies, exploring how they can be synchronized. IT Governance Archetypes describe different models for distributing decision rights, such as monarchies, federal systems, and duopolies. Relational Mechanisms include structures and processes that foster collaboration between business and IT, such as steering committees and executive councils. Agile and Adaptive Governance approaches recognize the need for flexibility and responsiveness in dynamic environments.Tools and Best PracticesEffective IT governance relies on a range of tools and practices. Steering committees bring together business and IT leaders to prioritize projects and allocate resources. Architecture review boards ensure that technology decisions align with the enterprise architecture. Balanced scorecards translate IT strategy into performance metrics. Risk registers track and manage technology-related risks. Maturity models assess the organization's governance capabilities and identify improvement areas. Communication plans ensure that governance decisions and rationale are clearly conveyed. Training and awareness programs build governance literacy across the organization. Continuous improvement processes ensure that governance practices evolve with changing circumstances.Impact and ApplicationsIT governance has a profound impact on organizational performance. Effective governance is associated with better financial returns, improved risk management, and greater strategic agility. It helps organizations avoid costly failures, such as failed system implementations or security breaches, and enables them to seize opportunities more quickly. IT governance is applied across industries, from financial services and healthcare to manufacturing and government. It is particularly critical in highly regulated sectors, where compliance requirements demand robust control and oversight. In the public sector, IT governance ensures that taxpayer-funded technology investments deliver public value. In the private sector, it supports competitive advantage by ensuring that technology investments are aligned with business strategy.Challenges and LimitationsDespite its benefits, IT governance faces several challenges. Complexity is a major issue, as organizations must balance multiple frameworks, stakeholders, and priorities. Resistance to change can impede the adoption of governance practices, particularly when they challenge existing power structures. Rapid technological change makes it difficult to maintain relevant governance structures. Data quality is a persistent challenge, as governance decisions depend on accurate and timely information. Cultural differences can affect how governance is implemented across global organizations. Over-governance is a risk, as excessive bureaucracy can stifle innovation and slow decision-making. Under-governance is equally problematic, leaving the organization exposed to unnecessary risk.Future DirectionsThe future of IT governance is likely to be shaped by several trends. Artificial intelligence and machine learning are being used to automate governance processes, such as risk assessment and compliance monitoring. Agile and DevOps practices are challenging traditional governance models, requiring more adaptive and iterative approaches. Cloud computing is shifting the focus from managing infrastructure to managing services and outcomes. Cybersecurity is becoming a central concern, with governance frameworks increasingly integrating security considerations. Sustainability is emerging as a new dimension of governance, as organizations seek to align technology with environmental and social goals. Decentralized governance models are gaining traction, empowering teams while maintaining enterprise-level oversight.ConclusionIT governance is a critical discipline for any organization that relies on technology. It provides the structure and processes needed to ensure that IT decisions are aligned with business objectives, deliver value, and manage risk. While the field faces challenges, it also offers significant opportunities for organizations that embrace it. By adopting sound governance practices, organizations can transform IT from a cost center into a strategic asset, enabling them to compete more effectively in an increasingly digital world. The ongoing evolution of IT governance reflects the changing nature of technology and business, and its continued relevance is assured as long as organizations depend on technology to achieve their goals.The 24 concepts its tower teaches
- IT Governance
- Decision Rights
- IT Governance Archetypes
- Agile and Adaptive Governance
- Accountability
- Strategic Alignment
- Value Delivery
- IT Risk Management
- Performance Measurement
- Stakeholder Engagement
- Transparency
- COBIT
- ISO/IEC 38500
- ITIL
- Strategic Alignment Model
- Relational Mechanisms
- Steering Committees
- Architecture Review Boards
- Balanced Scorecards
- Risk Registers
- Maturity Models
- Communication Plans
- Training and Awareness Programs
- Continuous Improvement Processes
- 1993-2010
Strategic Alignment Model
How should business and IT strategy fit together?
About Strategic Alignment Model
The Strategic Alignment Model, introduced by John C. Henderson and N. Venkatraman in their seminal 1993 IBM Systems Journal article, "Strategic Alignment: Leveraging Information Technology for Transforming Organizations," emerged during a critical period in information systems history. Throughout the early 1990s, organizations had moved beyond back-office automation and were beginning to use IT for competitive advantage, yet they lacked a structured way to connect technology decisions with business strategy. The model was created to address a persistent puzzle: why do so many IT investments fail to deliver business value, even when the technology itself is sound? The answer, Henderson and Venkatraman argued, was not technical failure but a failure of alignment—a mismatch between business strategy, IT strategy, organizational structures, and IT infrastructure.The model's distinctive organizing idea is that alignment is not a one-time event or a simple checklist, but a dynamic process of continuous adaptation across four fundamental domains. These domains are: business strategy, IT strategy, organizational infrastructure and processes, and IT infrastructure and processes. The model's power lies in its recognition that these domains are not isolated silos. Instead, they are connected by two types of relationships: strategic fit (the vertical linkage between a strategy and its corresponding infrastructure) and functional integration (the horizontal linkage between the business and IT domains). This creates a two-by-two matrix that allows managers to diagnose where misalignments occur and to plan how to move from a current state to a desired future state.To understand the model, it is helpful to learn its components in a logical order. First, consider the two strategy domains. Business strategy concerns how the firm competes in its product-market space—its scope, its distinctive competencies, and its governance choices. IT strategy concerns how the firm positions itself in the IT marketplace—the technology scope, the systemic competencies that IT enables, and the governance of IT itself. Second, consider the two infrastructure domains. Organizational infrastructure and processes refers to the firm's internal structure, its business processes, and the skills of its people. IT infrastructure and processes refers to the firm's technology architecture, the data and applications that support the business, and the skills of the IT staff. The model holds that a strategy without a corresponding infrastructure is merely an aspiration, while an infrastructure without a strategy is a cost center with no direction.The model's most important contribution is its articulation of four distinct alignment perspectives, each representing a different starting point for achieving alignment. The first is the strategy execution perspective, where business strategy drives organizational infrastructure, which in turn drives IT infrastructure. This is the classic top-down view, where the CEO or business unit head sets the direction and IT is expected to support it. The second is the technology transformation perspective, where business strategy drives IT strategy, which then drives IT infrastructure. Here, IT is seen as a source of new capabilities that can reshape the firm's products or services. The third is the competitive potential perspective, where IT strategy drives business strategy, which then drives organizational infrastructure. This is a more radical view, where IT is used to create new business models or disrupt existing markets. The fourth is the service level perspective, where IT strategy drives IT infrastructure, which then drives organizational infrastructure. This perspective emphasizes the importance of IT being run as a competitive service provider, with a clear understanding of its own capabilities and costs.These four perspectives are not merely theoretical constructs; they are diagnostic tools. The model suggests that organizations often get into trouble because they unconsciously adopt a single perspective and never question whether it is appropriate for their current competitive situation. For example, a firm in a stable industry might rely on strategy execution, while a firm in a rapidly changing market might need to adopt a competitive potential perspective. The model also highlights the importance of cross-domain relationships, particularly the distinction between strategic fit (the alignment between strategy and infrastructure within the business or IT domain) and functional integration (the alignment between the business and IT domains). A firm can have a brilliant business strategy and a brilliant IT strategy, but if the two are not integrated, the result is misalignment.The intellectual history of the model is rooted in the broader management literature of the 1980s, particularly the work on competitive strategy by Michael Porter and the resource-based view of the firm. Henderson and Venkatraman were responding to a growing sense that traditional IT planning methods, which focused on aligning IT projects with business strategy in a linear fashion, were inadequate. Their model was a significant departure from earlier approaches because it treated alignment as a dynamic, multi-directional process rather than a static, top-down one. It also differed from contemporary frameworks like ITIL, which focused on IT service management and operational efficiency, and from early versions of COBIT, which were more concerned with control and auditability. The Strategic Alignment Model was fundamentally about strategy and value creation, not about operational processes or control frameworks.The model's continuing significance lies in its enduring relevance to the problem of IT governance. While the specific technologies have changed dramatically since 1993, the fundamental challenge of ensuring that IT investments support business goals remains as pressing as ever. The model's four perspectives are still used in consulting and academic research to diagnose alignment problems and to design governance structures. It also laid the groundwork for later frameworks like COBIT, which incorporated many of its ideas about aligning IT with business objectives, but the Strategic Alignment Model remains distinct in its focus on the strategic dimension of alignment rather than the control dimension. For a modern IT leader, the model provides a powerful mental model for asking the right questions: Are we merely executing the business strategy, or are we actively shaping it? Is our IT infrastructure a source of competitive advantage, or a liability? Are we managing the trade-offs between strategic fit and functional integration effectively?No specialist knowledge is required to begin learning this framework. A basic familiarity with business strategy concepts, such as competitive advantage and organizational structure, is helpful but not essential. The model is best understood as a conceptual lens for thinking about the relationship between business and IT, and it can be applied in any organization, regardless of industry or size. The value of the model is not in its prescriptive detail but in its ability to surface assumptions and to structure a conversation about the role of IT in the enterprise. It asks leaders to be explicit about their theory of how IT creates value, and it provides a vocabulary for discussing that theory with others.The 8 concepts its tower teaches
- Four Domains of Strategic Alignment
- Strategic Fit
- Functional Integration
- Strategy Execution Perspective
- Technology Transformation Perspective
- Competitive Potential Perspective
- Service Level Perspective
- Alignment Diagnosis
- 1995-Present
Relational Governance
How are IT relationships coordinated across organizations?
- 2002-Present
IT Risk and Compliance Governance
How can IT risks be controlled and demonstrated?
- 2004-Present
IT Decision Rights and Governance Archetypes
Who should decide about IT?
- 2005-Present
- 2015-Present
Data and Algorithmic Governance
Who is accountable for what an algorithm does?
- 2016-Present
Government by algorithm
How should automated public decisions be governed?
How the ideas connect
Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.
IT Risk and Compliance Governance grew out of COBIT
IT risk and compliance governance grew directly out of COBIT's control objectives: after Sarbanes-Oxley in 2002, firms adapted COBIT's control catalog to map IT risks to auditable controls for regulators.
Carried by Sarbanes-Oxley Act (2002); COBIT.
Data and Algorithmic Governance grew out of Data Governance
Algorithmic governance grew out of data governance: once ownership and quality rules for data were formalized, the same accountability questions were extended to the models trained on that data, adding bias, explainability and redress.
Enterprise Architecture Governance influenced by COBIT
COBIT's process-and-control view of IT gave enterprise architecture governance a vocabulary for reviewing and enforcing architectural standards, and TOGAF's architecture governance drew on the same control-objective logic of checkable conformance.
Carried by COBIT (1996); TOGAF (1995).
IT Decision Rights and Governance Archetypes influenced by Strategic Alignment Model
The strategic alignment model framed IT as a strategic question but left open who decides; Weill and Ross's decision-rights work took up that gap and specified the authorities and archetypes that make alignment operational.
Carried by Henderson and Venkatraman (1993); Weill and Ross, IT Governance (2004).
IT Decision Rights and Governance Archetypes rival of Relational Governance
Decision-rights work and relational governance addressed the same question of how IT relationships are coordinated, one through formal authority archetypes and the other through trust and shared norms, and they competed as explanations of governance performance.
Carried by Weill and Ross, IT Governance (2004).
Data Governance influenced by COBIT
Data governance borrowed COBIT's control-objective and accountability structure, applying it to data ownership, quality standards and access rules rather than to IT processes as a whole.
Carried by COBIT.
IT Decision Rights and Governance Archetypes influenced by Enterprise Architecture Governance
Architecture governance supplied the decision-rights literature with one of its five key decision areas, IT architecture, and with the review-board mechanism that Weill and Ross treated as an archetype of federal governance.
Carried by Weill and Ross, IT Governance (2004).
Beyond the field
Where It Governance's ideas came from in other fields, and what they led to there: the strongest 12 of 32 links.
COBIT grew out of Audit in Accounting
COBIT was created by ISACA, an association of IS auditors, as an IT-specific extension of the audit control framework used to assess information systems. Its control objectives and audit guidelines grew directly out of the IT audit profession's practices.
Carried by ISACA; COBIT (1996).
Data Governance led to Data and Model Governance in Business Analytics
Data and model governance grew out of IT data governance, extending its stewardship, ownership and quality controls to analytical models and machine-learning pipelines.
Government by algorithm grew out of Digital government in Public Administration
Government by algorithm grew directly out of digital government and e-government research, extending its focus from online service delivery to automated and algorithmic decision-making in public administration. The later field treats algorithmic public decision-making as a new phase of the same digitization program.
COBIT influenced by Internal control reliance and audit sampling in Auditing
COBIT's control objectives and control framework were built on the COSO internal control model, which itself descends from the auditing profession's internal control reliance and sampling tradition. The COBIT authors drew on this audit lineage to define IT control objectives for auditors and managers.
Carried by COBIT (1996); COSO Internal Control Framework (1992).
Enterprise Architecture Governance influenced by Zachman Framework in Enterprise Architecture
The Zachman Framework supplied the descriptive taxonomy of architecture artifacts that later architecture governance processes used to assign ownership and standards. Governance frameworks such as TOGAF built their architecture content and control structures on Zachman's rows and columns.
Carried by John Zachman; Zachman Framework (1987).
Enterprise Architecture Governance influenced by Business Systems Planning in Enterprise Architecture
IBM's Business Systems Planning method established the practice of planning information systems top-down against business processes, a precursor that enterprise architecture and its governance formalised. Zachman, working at IBM, drew on this planning tradition when framing his architecture framework.
Carried by IBM Business Systems Planning; John Zachman.
Strategic Alignment Model influenced by IT as Competitive Weapon in Digital Strategy
The idea of IT as a competitive weapon framed the strategic question the Strategic Alignment Model answered by mapping business and IT domains. Henderson and Venkatraman built their model to explain how IT strategy could deliver that competitive value.
Carried by John C. Henderson; N. Venkatraman.
Relational Governance influenced by Governance and network theory in Public Administration
Relational governance theory borrowed the network conception of governance, in which coordination arises from sustained relationships among interdependent actors rather than hierarchy. This network view of governance supplied the relational governance literature its core framing.
Relational Governance influenced by Relational contract in Transaction Costs And Governance
Relational governance in inter-firm exchange drew on the relational contract tradition, which held that long-term relationships are governed by norms and trust rather than discrete contracts alone. This concept passed into the governance of inter-organisational relationships.
Carried by Ian Macneil.
IT Risk and Compliance Governance influenced Information governance in Records And Information Management
IT risk and compliance governance practices, including control frameworks and risk registers, were carried into information governance as its risk-management and compliance machinery.
IT Risk and Compliance Governance influenced by Turnbull Guidance and Board-Level Internal Control in Enterprise Risk Management
The Turnbull Guidance made board-level internal control and risk management an explicit governance duty, a model that IT risk and compliance governance extended to information systems. IT governance frameworks then folded this board-level control expectation into their risk and compliance structures.
Carried by Turnbull Guidance (1999).
IT Risk and Compliance Governance influenced by Corporate Compliance Programs in Global Business Ethics
Corporate compliance programs established the organisational machinery of codes, monitoring and reporting that IT risk and compliance governance adapted to technology controls. The later field took over this compliance-program structure for IT-specific regulation.

It Governance is a planet in Nousfarer
Its city has a tower for each of these 10 frameworks. Land, walk in, and climb one concept at a time.
Land on It GovernanceRelated fields
Fields its ideas are linked to
- Enterprise Architecture 6 links
- Records And Information Management 4 links
- Digital Strategy 4 links
- Data Protection And Privacy Law 3 links
- Imaging Informatics 2 links
- Public Administration 2 links
- Accounting 1 link
- Auditing 1 link
- Global Business Ethics 1 link
- Data Science 1 link
- Critical Hci 1 link
- Business Analytics 1 link