Accountability
One accountable person for each open issue
Three people are copied on a repair request. Everyone assumes someone else will arrange the next step, and the request remains unanswered.
Being informed about a task is different from being accountable for moving it forward.
Ownership does not mean one person performs every part of the work. It means someone knows the current status and is responsible for moving the agreed process forward. The contractor may perform the work, the manager may coordinate access and the owner may approve spending. These responsibilities should be clear without relying on an email’s recipient order.
When assigning an issue, include enough context for the recipient to act. Explain the requested next step, any limits and where supporting information can be found. Ask for acknowledgement through the team’s agreed method. If the assignment is declined or unanswered, keep that state visible rather than treating the issue as covered.
A handover should preserve history. Record who passed the issue, who accepted it and which commitments remain. This is particularly useful across shifts, holidays or staff changes. A short, explicit transfer can prevent the confusion caused by forwarding a long conversation with no clear instruction about what happens next.
Put it into practice
- Name one person responsible for the next action.
- Record the provider, reviewer and decision-maker separately when they differ.
- Require an explicit handover when responsibility changes.
What to verify
Check whether each open issue has an acknowledged owner, a next action and a review date. A name entered in a field is not proof that the person accepted responsibility.
Review five open issues for unaccepted assignments.