When the people who built an ML system move on, someone still has to maintain it. Make ownership explicit from the start rather than relying on the original builders to remain available. section 16.0
Write down each area of accountability so the team shares an unambiguous understanding. The record can be a simple assignment or a more formal RACI matrix: section 16.1
For each task or component, distinguish:
- Responsible: the people who do the work. section 16.1
- Accountable: one person ultimately answerable for completion, preferably with authority to approve or reject the work. section 16.1
- Consulted: experts or stakeholders whose opinions are sought. section 16.1
- Informed: people who need updates but do not directly contribute to the task. section 16.1
Also record how to escalate situations the assignments do not cover. Meeting notes, follow-ups, and updates can keep responsibilities visible, but excessive syncs waste time. Documentation preserves shared understanding when people leave or join. section 16.1 section 16.3
