Blueprint · A · Accountability
Accountability Steward
The Accountability Steward keeps responsibility visible and fair. They make sure it is clear who answers for what, and that when something goes wrong the system is examined first and the person second. And they make sure that both produce learning. They hold the self-responsibility architecture of the system: self-responsibility cannot be decreed, but its conditions can be built.
Effort: 5 to 10 %, depending on the size of the organisation
Outcome
- For every task it is visible who answers for what; the job register is current and complete.
- When something goes wrong the system is examined first, the person second; that order is never skipped.
- Errors and system reviews demonstrably produce learning, personal and organisational.
- Decision and responsibility patterns are reflected factually in reviews, without assessing individuals.
- A stays subsidiary: it only becomes active where learning fails to happen, and it asks before it signals.
Fields
- Clarity of responsibility
- The job register as a living artefact: which core jobs and joblets exist, who holds them, where A and R sit. Ownership and delegation visible and traceable.
- System review and learning
- Error diagnosis following blame the system first, decision-log reviews and ex-post reviews of HGD decisions, pattern recognition, learning accountability, diagnosis of the conditions for self-responsibility.
Design and execution
| Field | The Steward designs | Execution sits with |
|---|---|---|
| Clarity of responsibility | Guardrails for visibility: what the register holds, how ownership and delegation are described | Anchor for clarity of responsibility: maintains the register. The content is owned by the jobs themselves; normative ratification sits in S |
| System review and learning | Diagnostic guardrails: blame the system first, the three guiding questions (Was the accountability taken up? Is someone standing in it? Did learning happen?), review criteria | Anchor for system review and learning: runs diagnoses, decision-log and ex-post reviews. Enablement sits with M, decisions and consequences with S |
| Self-responsibility architecture | The conditions under which self-responsibility is possible: clear spaces of responsibility, real decision rights, available knowledge, no control architecture | Self-responsibility is lived by each person; enablement sits with M, structural correction with S |
Proposed Anchor Core Jobs
- Clarity of responsibility
- The job register as a living artefact: which core jobs and joblets exist, who holds them, where A and R sit. Ownership and delegation visible and traceable.
- System review and learning
- Error diagnosis following blame the system first, decision-log reviews and ex-post reviews of HGD decisions, pattern recognition including where strikingly little is decided through gravity decisions, learning accountability.
Powers at design level
- Sets the guardrails, frames and degrees of freedom of their letter; they take effect immediately.
- Holds the veto when a new core job breaks the guardrails.
- Cuts the anchor structure of their letter; new core jobs are created together with governance.
- Sends governance signals out of their diagnostic function; subsidiary, and only after asking those involved. The A signal never concerns people.
- Holds design authority over the self-responsibility architecture. Where self-responsibility is structurally blocked they send a governance signal; where knowledge is missing they report the learning need to M.
- Chairs the governance review by the steward college: convening, agenda, minutes, carrying the finding. They decide no consequences.
Drift protection
Blame the system first. This steward does not become blame, control, compliance police or personal evaluation: the A signal never concerns people, missing learning is not in itself grounds for dismissal, and A replaces neither performance management nor discipline nor governance. A trusts self-responsibility first: no audit checklists, no mandated frequencies, no forms. In the best case those involved notice in the ex-post review that something went wrong and start the correction themselves; then A has nothing to do.
Competencies
- Responsibility diagnosis
- spots where accountability diffuses, doubles up or is orphaned, and makes it visible without judging.
- Accountability architecture
- describes spaces of responsibility, ownership and delegation so that no diffuse responsibilities emerge.
- System diagnostics
- reads recurring errors as a system signal first and distinguishes error, symptom, cause and system condition.
- Review capability
- reflects decision and responsibility patterns factually and develops them towards learning.
- Awareness of conflict and limits
- recognises when accountability tips into control, blame or a shift of power.
Strengths
- Clarity
- makes responsibility, ownership and boundaries understandable.
- Fairness
- protects people from blame and systems from whitewashing.
- Judgement
- distinguishes error, symptom, cause, responsibility and system condition.
- Integrity
- stays factual even when a diagnosis is uncomfortable.
- Restraint
- acts subsidiarily and leaves the correction to those involved wherever they can make it themselves.