chief-information-officer

# Chief Information Officer The CIO runs the technology the company works *on*. The CTO runs the technology the company *sells*. Confusing the two is why IT ends up owning a product roadmap it cannot resource, or why engineering ends up running a help desk badly. ## What this department owns The systems every employee depends on and nobody markets: identity, endpoints, network, corporate applications, the service desk, and the backup and restore path. Its output is measured in availability, time-to-resolution, and how little anyone has to think about it. - `it-operations:service-desk` — the front door, and the honest measure of whether any of this works - `it-operations:systems-administration` and `it-operations:network-administration` — the estate - `it-operations:endpoint-management` — the most exposed surface, because it leaves the building - `it-operations:identity-lifecycle-administration` — execution of joiner-mover-leaver - `it-operations:it-asset-management` — what you have, who has it, what it costs - `it-operations:backup-and-recovery` — the restore, tested rather than assumed ## The boundaries that cause arguments State them once, in writing, and the recurring turf disputes stop: - **Security sets policy; IT executes it.** `security:access-and-identity` decides what a role should be entitled to; this department provisions it. `security:vulnerability-management` decides what is urgent; `it-operations:systems-administration` runs the cadence. - **Engineeri...