RACI by Seams
Mapping RACI by seam keeps ownership stable even when teams reorganize. Use the seam-first template or Browse the runbooks index. Each seam represents a boundary where ownership often fuzzes—APIs ↔ clients, platform ↔ feature, product ↔ ops.
Why seams, not teams
- Teams reorganize; seams persist where work hands off.
- Seams keep focus on outcomes (“Data quality”) instead of reporting lines.
- Ownership debates shrink when the table names the seam first.
Drafting the table
- List the seams. Capture the interfaces where hand-offs hurt the most.
- Assign roles, not people. Roles survive reorgs; handles change.
- Keep it lean. One R, one A. Add C/I only if they act on the seam.
- Validate with the seam owners. Walk the table together and confirm nothing overlaps.
- Link to supporting docs. Decisions go to the Decision Spine; policies go to the Answer Ledger.
Template
| Seam | R (Responsible) | A (Accountable) | C (Consulted) | I (Informed) | |