CIO · Chief Information Officer
Is it actually connected to anything?
204 units of work on this desk right now — 110 moving, 27 stopped on a person, 71 past their service clock. 3 escalations open or acknowledged, 6 decisions overdue, 23 gaps still on the register. Scope: IT.
Health
The four counts this chair opens on
Each one is the same figure its page shows. Where it is red, the chair opens on a problem.
Source systems returning records
Every system is described. None is connected.
Write-back routes live
Nothing this platform decides reaches a system of record.
Reconciliation breaks
Places where two records of the same fact disagree.
Releases blocked
Change that cannot ship until something else moves.
Operations
How the work is running on this desk
Counted across 33 workflows in 1 of 14 functions. A unit past its service clock is counted as late whether or not anybody has noticed it.
in flight
of 204 units on this desk, moving with an agent now
stopped on a person
13% of the desk is waiting on a human decision
past the service clock
age has already exceeded the service level held against the unit
cleared without a person
against 40 that posted evidence but are not closed
mean autonomy
unweighted mean across 1 function; touchless 79%
Function by function
Units on the desk, what is stuck, and the duty conflicts sitting under it
| Function | Units | Held | Late | Red | Esc | SoD | Autonomy |
|---|---|---|---|---|---|---|---|
| IT | 204 | 27 | 71 | 27 | 3 | 27 | 76% |
Live observability
204 units, as the record has them this moment
IT is carrying the most stopped work on this desk: 27 units on a person and 27 showing red. None of this has been written back to a system of record.
What these numbers rest on
2 source systems feed this desk, 0 of them live
1 of 2 is already past the freshness its own contract commits to, and 0 have never delivered a sync at all. Every figure above this line was read through them.
feeds behind this desk
of 26 on the registry; 0 connected live, 0 not connected at all
feed past its own commitment
worst is Configuration Management Database, late by 36.2 hr
feed not healthy
1 healthy; health here is the state the registry records, not a check run this moment
business terms in scope
1 contested, 0 with no book of record, 2 open disagreements
Feed by feed, and how stale each one is
2 in scope, ordered by how far past commitment they are
| Source system | Connection | Health | Promised | Actual | Where that leaves it |
|---|---|---|---|---|---|
Configuration Management Database itsm · owner IT Operations · 2 terms bound | Modeled feed | Outside commitment | 24.0 hr | 2.5 days | late by 36.2 hr |
IT Service Management itsm · owner IT Operations · 2 terms bound | Modeled feed | Inside commitment | 15 min | 9 min | inside its own commitment |
None of these 2 feeds is connected live. Every number on this page was read from a modeled copy of them, and the ages above are the ages of that copy. Every feed in scope has at least one defined term pointing at it.
The words these numbers use
2 in scope · 6 system bindings
2 unsettled disagreements about what a word means on this desk
Every one is listed; none is summarized away
IT Service Management says An incident is a service interruption raised as a ticket by a person. This platform says An incident is one of the sixteen agentic failure records this platform keeps.
Two non-overlapping populations share one word. A reader told there are sixteen incidents and a reader told there are several thousand are both being told the truth, and neither is told which population they are looking at. Not sized. The two have never been placed on the same page until this one.
IT Service Management says The target is the resolution time held against the priority band. Contract Lifecycle Management says The target is the number written into the service schedule of the contract.
Where the two differ the group reports itself against the softer of them without saying so. Twelve of the twenty-eight service levels this platform carries have no function attached at all, so nobody owns the comparison. Not sized. No extract of contractual thresholds exists to compare against.
Governance
31 things in this chair's scope are open, late or breached
Counted from the registers that name a function. Nothing here has been closed in a source system, because nothing writes back to one.
escalations past SLA
of 3 open or acknowledged, already older than their clock
incident not closed
of 1 recorded in scope
duty conflicts open
of 32 detected; none proven closed in a source system
service level breached
of 1 named to this scope; 0 overdue for review
The control register names no function on any of its entries, so it cannot be cut to this chair. These are the enterprise figures, shown here because these controls gate work on this desk. 12 of the service levels on the register name no function either, and are not in the count above.
Escalated
3 escalations are open or acknowledged in scope
Ordered by whether the clock has already run out, then by how much work sits behind it. The agent's recommendation is shown as written.
Network: IT5B-1033 held at request
14h lateTopology Monitoring Agent recommends approving a partial and holding the remainder.
Data & Integration Platform: IT8C-1006 held at steward approve
9h lateDirector, Data Platform recommends approving with the compensating control attached.
Asset & License: IT9A-1027 held at true-up
59mDirector, IT Asset Management recommends pausing the lane until the upstream data defect is fixed.
Decisions waiting on an executive
12 open, 6 overdue, 114 records blocked behind them
Two source systems have no feed at all
overdueChief of Staff to the CEO, on behalf of the CFO · $84k a week to wait · 3 blocked
Order to Cash inference is running at the cap
overdueFinance Business Partner, Operations · $28k a week to wait · 1 blocked
Nine reconciliation breaks have no owner
overdueGroup Financial Controller · $13k a week to wait · 9 blocked
Seven controls have never been tested
overdueHead of Internal Audit · $10k a week to wait · 9 blocked
Promotion slate agent is running at an adverse-impact ratio of 0.74
overdueChief People Officer · $0 a week to wait · 2 blocked
The decision register carries no function scope, so this list is the enterprise list. It is not filtered to this chair.
What needs improving
23 entries on the register, 0 closed, covering 26,887 records
Facts standing on an inference rather than a read
overdue5,581 facts · unassigned · open
Duty conflicts that have only been detected
overdue291 conflicts · Control owner · in-progress
Checks where the checker is the author
overdue189 checks · Finance · open
Service levels being missed
overdue12 service levels · Function Leader, Revenue Operations · open
Positions that failed and nothing was written down
overdue11 failures · Recorder · open
Control exceptions still open
overdue11 exceptions · customer · in-progress
Not one entry on this register has ever been closed. The register is enterprise-wide and is not filtered to this chair.
Is policy and strategy coming to fruition
0 of 2 checked positions held
Strategy positions and policy items written inside the functions this chair carries, read against their own outcome checks.
Partly holding on the record
12
positions written
2
ratified
2
still in challenge
10
never outcome-checked
0
held
2
partially held
0
did not hold
29
policy items active
10 of the 12 positions on this desk carry no outcome check at all, so most of what this chair set out cannot be said to have worked or failed. 4 policy items are under review against 29 active ones. Every check here was written by the same platform that wrote the position.
Go deeper
The pages this chair works from
Grouped the way this chair reads them. Each opens the page that produced the numbers above.
Systems of record
The ingestion spine
Change and release
What this chair cannot say
Not one source system is returning live records and not one write-back route is live. Everything downstream of that is a model of the estate rather than the estate.