Responsibilities
One name, or it is not owned.
The test of ownership is simple: if this does not happen, whose phone rings? If the honest answer is "it depends", the responsibility does not have an owner yet.
Owner, backup, contributors
Three distinct relationships. The owner is accountable, the backup can step in, the contributors have to be involved. Collapsing them is how accountability dissolves.
Accepted, not assigned in silence
A responsibility handed to someone is acknowledged by them. Discovering you own something during your own review is not a good way to find out.
Attached to a person or a role
Some responsibilities belong to whoever holds a position; others belong to a particular individual. Both are supported, and the difference decides what happens when they leave.
Responsibilities
The rest of this area.
The work the business depends on, as objects with owners rather than assumptions.
Backups
The second name, and the responsibilities that do not have one.
Key-person risk
What the business depends on one person for.
Escalation
Where a responsibility goes when the owner cannot resolve it.
Evidence
How you know a responsibility was actually discharged.
Recurring work
Monthly, quarterly and annual obligations that arrive whether you remember or not.
Run your team with clarity.
From the moment someone joins to the day their responsibilities are handed over, Orglume keeps your people, their work and your organization connected.
Set up from a spreadsheet · Nothing about the AI is metered · [email protected]