“Why can’t we just change this?”
Most change is blocked or enabled by a rule or a person, not a system. This page adds two things to the business layer: an inventory of policies linked to the work they govern, and decision rights that say who must agree before anything changes.
2Step 2 of 5 · Run — business layerA policy record names the processes, data and systems it applies to, so a policy change shows what it touches, and a process change shows which rules stand in the way. Sample records for Example State University:
| Policy | Governs | Owner | Review |
|---|---|---|---|
| Data classification | All data topics; every system’s classification field | CIO with the data governance council | Annual |
| Records retention | Student, HR and finance records; archive and deletion jobs | University records manager | Every 3 years |
| Acceptable use of technology | Identity and access, all user-facing systems | CIO | Every 2 years |
| Course withdrawal and late drop | Enrolment and registration process; SIS rules | Academic senate with the registrar | Every 3 years |
| Procurement thresholds | Purchasing process; Finance ERP approval workflows | CFO | Annual |
| Electronic signatures | Forms and approval workflows across units | General counsel | Every 3 years |
On each system record, policy_refs lists the policies that apply. Read the other way, it is the list of systems a policy change would touch.
Decision rights are recorded per kind of change, not per system. The decision_owner on a system record points to the row that applies.
| Kind of change | Decides | Must agree | Consulted | Informed |
|---|---|---|---|---|
| Replace a core system | Cabinet, on the CIO’s recommendation | CFO; owning vice president | Academic senate; affected units; IT architecture review | Campus community |
| Change a shared data definition | Data governance council | Data owner for the topic | Data stewards; institutional research | System owners |
| Change an academic policy | Academic senate | Provost | Registrar; student affairs | Students and advisors |
| Retire a service | Owning vice president | CIO if technology is involved | Service users; help desk | Campus community |
| Adopt an AI agent that acts on records | AI governance group | Data owner; system owner | Security; legal; affected staff | Users of the process |
A policy nobody reviews, or a decision with no named decider. Changes stall waiting for someone to say yes.
Every unit must agree, so the default answer is no.
A policy written for a paper process now forces a workaround in a digital one.
A practice everyone follows that is not written anywhere, so it cannot be changed on purpose.
Each pattern points to a lever: change the policy, or reorganize who decides. See levers.