Governance
Where nobody is responsible
“Who is responsible?” is the question every tool answers. In large programmes the other one matters more: What is nobody responsible for?
Because responsibility in the model hangs on objects instead of sitting in a list, this can be computed – across processes, epics, tasks, tests and organisational units.
Responsibility gap analysis
Example state of a running programme
| 🔴 | 3 processes without an accountable |
| 🔴 | 2 epics without an owner |
| 🟠 | 6 tasks without an assignee |
| 🟠 | 4 tests without a tester |
| 🟠 | 3 roles not yet confirmed |
| 🟡 | 2 organisational units without a lead |
| 🟡 | 3 responsibilities expiring |
This is not a search but a control: it runs continuously and speaks up for as long as the gap exists – not only when someone goes looking.