Governance
Governance is the system of oversight, direction, and accountability by which an organization steers its decisions and ensures they are made deliberately rather than by default. It answers four questions: who has the authority to decide, what they may decide, how decisions are enforced, and how decision-makers are held to account. It is distinct from management, which executes the work, and from compliance, which verifies that a system conforms to rules. Governance sets the rules and the bounds; management operates within them; compliance checks that it has.
Governance is sometimes confused with control, but its purpose is not to make every decision centrally. A mature governance regime delegates most decisions and reserves authority for the few that cross boundaries or carry lasting consequences. The recurring challenge is choosing what to govern centrally, what to federate, and what to leave to individual teams.
Forms in software practice
In software-intensive organizations, governance surfaces in several recurring forms. Each governs a different kind of asset, but all share the same shape: a body with authority, a set of standards or policies, and a mechanism for enforcement.
- Enterprise architecture governance. The practice of approving which technologies and patterns an organization may adopt, how new systems are evaluated, and how the architecture evolves over time. See enterprise architecture and TOGAF.
- Data governance. Oversight of data quality, security, privacy, and interoperability. The data mesh formalizes this as federated computational governance, in which a lightweight central body sets global standards that are enforced computationally rather than through manual review.
- AI and agent governance. Oversight of how AI systems and autonomous agents are permitted to act. AI regulation sets the external legal floor, while agent orchestration applies governance inside a running system of autonomous workers, managing budgets, delegation, and boundaries.
- Standards and protocol governance. The stewardship of an open standard by a vendor-neutral body, so that no single company can steer it unilaterally. Transferring a specification to a foundation such as the Linux Foundation is the common pattern; Agent2Agent (A2A) followed it.
Why it matters
Governance is often invisible when it works and conspicuous when it fails. Its absence shows up as duplication, drift, and decisions made in isolation. The same application gets bought three times, the same data is modeled three ways, the same risk is taken independently in three places. Its excess shows up as bureaucracy that slows work without improving the outcome. Calibrating the amount of governance to the cost of a wrong decision, and to the size of the organization, is the core discipline.