Why "Who owns this?" still slows modern engineering teams
Over the past few weeks, I've been speaking with Platform Engineers, SREs, Engineering Managers, Incident Commanders, and Major Incident Managers.
One question keeps surfacing during production incidents:
"Who owns this?"
At first, I assumed this was simply a documentation problem.
Maybe service ownership wasn't clearly defined.
Maybe teams lacked runbooks.
But the conversations suggested something more interesting.
Most organizations already know who owns individual services.
The difficulty starts when an incident crosses service boundaries.
A production issue rarely stays confined to one component.
It may involve:
- an application service
- Kubernetes
- networking
- cloud infrastructure
- authentication
- third-party dependencies
Now several teams are involved simultaneously.
Each team begins investigating from its own perspective.
While everyone is working, another question quietly emerges:
Who should lead the incident?
Several incident managers told me that once a lead team or incident commander is established, coordination becomes noticeably easier.
Not because the root cause has been found.
But because everyone now has a common direction for communication and decision-making.
The interesting insight for me has been this:
The bottleneck isn't always ownership of the technology.
It's ownership of the response.
I'm still researching this pattern, so I'd love to hear from others building or operating distributed systems.
During major incidents, what usually determines who takes the lead in your organization?
Make the lead-selection rule mechanical: the team owning the highest current blast radius leads until evidence moves it, while service owners supply responders. Otherwise the “who leads?” debate becomes a second incident.
That's an interesting way to frame it. Using the team responsible for the highest current blast radius as the temporary incident lead seems like a practical rule.
I'm curious—how often have you seen that work well in practice? Is it usually an explicit policy, or does it emerge informally during incidents?
I can't claim a personal incident history here, so treat it as a policy hypothesis. It only works if the rule is explicit before the incident: define how blast radius is judged, who declares the temporary lead, and what evidence triggers a handoff. If it emerges informally, authority is contested at exactly the moment you need one decision path.
This comment was deleted 2 months ago