The Technology Governance Codebook supports systematic, outcome-neutral analysis of technology governance. It is the research instrument behind every Governance Files case: the same definitions and questions are applied whether the matter at hand ended well, ended badly, or is still unfolding.
How do governance decisions and mechanisms shape the adoption, use, transformation, operation, and consequences of technology within organizations?
The codebook is designed to examine governance across favorable, adverse, mixed, recovered, ongoing, and indeterminate outcomes. It does not assume that:
- an adverse outcome establishes governance failure;
- a favorable outcome establishes effective governance;
- a governance deficiency necessarily produces realized harm;
- effective governance eliminates the possibility of adverse consequences; or
- technology governance occurs only within formal projects or implementations.
Coding first establishes how governance operated. Governance effectiveness, consequences, and the relationship between them are assessed separately, and only afterward.
What we study: the Governance Matter
The unit of research is a Governance Matter: a defined instance in which organizational authority, oversight, accountability, policy, control, or decision-making is exercised, or reasonably may be expected to be exercised, over a consequential technology activity, decision, system, relationship, or use.
Governance Matters include, among others: technology projects and transformations; ERP and student information system implementations; AI deployments and use cases; enterprise technology policies; technology acquisitions and investment decisions; vendor and third-party relationships; data practices and cybersecurity decisions; and technology incidents and how institutions respond to them. A single matter may draw on many source documents and many separately coded pieces of evidence.
Outcome neutrality
Outcome neutrality is foundational to the methodology. Transformidable does not begin with whether an initiative succeeded or failed and work backward to decide whether governance was good or bad. Governance is coded independently of the known outcome: a successful initiative may still contain governance deficiencies, and an unsuccessful one may contain governance mechanisms that operated effectively.
Governance effectiveness, consequences, and any relationship between them are characterized separately, and each only after governance itself has been described.
The ten governance domains
Every coded piece of evidence is assigned one primary governance domain, and may be assigned secondary domains when independently supported. Select a domain to see its definition, the question it asks, and what it covers.
G1
Governance Structure & Authority
Who has authority to govern this matter, and how is that authority structured?
The formal or practical allocation of governance authority over a technology matter, including governing bodies, retained and delegated authority, organizational jurisdiction, and governance capacity.
Includes: Governance bodies, steering committees, executive sponsorship, retained and delegated authority, charters, governance-body composition, organizational jurisdiction, governance capacity, and authority allocated to vendors or third parties.
Delegation is not treated as inherently deficient.
How the analysis works
Each governance mechanism found in the evidence is described first, then examined for how it was designed and how it actually operated in practice, and separately for the strength and quality of the evidence supporting that description. Effectiveness and consequences are assessed afterward, and only then, cautiously, any relationship between them. Several distinctions hold throughout:
- Governance mechanisms are not consequences.
- Effectiveness is not inferred from the outcome.
- Governance and consequences are characterized independently before any relationship between them is assessed.
- Causal language is used only to the extent the evidence actually supports it.
Evidence & research standards
Findings are built from audits and oversight reports, litigation and court records, laws and regulations, policies and governance frameworks, contracts and procurement records, institutional records, labor agreements, academic research, journalism, interviews, hearings and testimony, and vendor or interested-party material.
Not every source carries the same evidentiary weight. Transformidable tracks the role a source plays (discovery, evidence, corroboration, or context), how independent or interested its origin is, and whether it was produced at the time of the matter or afterward. A source that is valuable for locating information is not automatically sufficient to support an analytical conclusion on its own.
Absence of evidence is not treated as evidence of absence. If available sources are silent on a governance mechanism, it is classified as not evidenced, not as absent; classifying a mechanism as absent requires evidence that affirmatively supports that conclusion.
Version & validation status
Technology Governance Codebook v0.1 is a prototype, and UCPath is its initial operational pilot. UCPath alone cannot validate an outcome-neutral technology-governance codebook, so v0.1 should not be read as validated, an industry standard, predictive, statistically established, a maturity model, or a best-practice framework. It is a developmental instrument, and the research program intentionally allows evidence to test and refine it.
Before any promotion to v1.0, the codebook will be tested against a deliberately varied set of matters, favorable, adverse, and mixed outcomes; project and non-project governance; and matters with genuinely indeterminate evidence, to surface overlapping domains, missing mechanisms, and ambiguous definitions before the taxonomy is treated as settled.
Current version: 0.1 (Prototype), released August 2026. Initial release of the Technology Governance Codebook, expanding the research methodology from ERP and student-information-system failure mechanisms to outcome-neutral analysis of technology governance across both project and non-project governance matters. Definitions change only through a version bump; no version is silently altered, and prior versions remain archived as the codebook evolves.
How this connects to the Governance Files
Every published Governance Files case identifies which version of the Technology Governance Codebook governed its analysis. If a case is later recoded under a newer version, the original methodological provenance is preserved alongside the current one, so a reader can always determine which analytical framework produced a given published finding.