OrganizationPractitioner2 min read
Who does what in observability?
Twelve activities, seven roles: build your RACI matrix, check it has exactly one accountable owner and at least one person doing the work per line, spot bottlenecks, export it.
For: team managers · executives and CIOsPrerequisites: None.
An illustrative scenario: a security incident hits customer data on a Friday evening. On Monday, in the meeting, the question comes up: who notified the supervisory authority? The CISO thought IT was handling it. IT thought it was the CISO’s job. The notification deadline is already running.
Think of flatmates moving house. Some carry the boxes, one decides where the sofa goes, one gets consulted because it is their piano, while the others are simply told when the truck arrives. A RACI matrix writes down that split for each activity. R (responsible) is who does the work. A (accountable) is who answers for it and signs off, the final owner. C is who is consulted, I who is informed. On a topic that runs across the whole organization, like observability, it keeps everyone from thinking someone else should act.
The tool helps settle a simple question: for each activity, do we know who decides? The matrix starts from a proposal to discuss and checks the rules as you fill it in.
| Activity | CIO | CISO | DPO | Platform, SRE | Development | Business | CFO | Check |
|---|---|---|---|---|---|---|---|---|
| Define the observability strategy | ||||||||
| Decide the annual budget | ||||||||
| Instrument services | ||||||||
| Define a service’s SLOs | ||||||||
| Run the platform | ||||||||
| Lead the response to a major incident | ||||||||
| Report an incident to the authority | ||||||||
| Set log retention periods | ||||||||
| Sign data processing agreements with vendors | ||||||||
| Steer observability data cost | ||||||||
| Produce leadership reporting | ||||||||
| Steer the roadmap |
R: responsible, does the work. A: accountable, signs off, only one per line. C: consulted before deciding. I: informed afterwards. A+R: the same person is accountable and does the work.
Summary
Load per role
| Role | A | R | C | I |
|---|
Nothing is sent: the matrix stays in this browser. The example loaded by default is a proposal to discuss in a workshop, not a standard.
Things to try
Section titled “Things to try”- Start from the example and look for the line that would spark debate in your organization. It is often “Lead the response to a major incident” or “Set log retention periods”.
- Put two As on “Report an incident to the authority”, for the CISO and the CIO: the line turns red. That is the Friday evening scenario. If two roles share final accountability, neither owns it.
- Make the CIO A everywhere. The summary flags a bottleneck: a CIO accountable for everything cannot follow anything.
- Empty the DPO column, the person in charge of data protection. The summary asks whether this role is really involved. For retention periods and data processing agreements, it is.
- Copy the matrix as CSV and paste it into a spreadsheet for the workshop.
The rule to remember
Section titled “The rule to remember”A RACI is not decreed, it is negotiated. The journal in lesson 3 of the CIO path tells what happens when it is imposed: resignations and a three-month delay. I recommend building it in a workshop with the people it names, signing it in the session, then reviewing it every quarter.
Going further: the organization dimension, the AI observability RACI and the bridges between dimensions.