4 ms·
These incident role names are fairly common in product companies these days. I guess you are correct that they do suggest a certain culture around incidents, bu
by lemax 5y ago
These incident role names are fairly common in product companies these days. I guess you are correct that they do suggest a certain culture around incidents, but in my experience is definitely a good thing. It's a "don't blame people, let's focus on the root cause, get things back up, and figure out how to prevent this next time" sort of thing. People try to meet SLAs and they treat each other like humans. We focus on improving process/frameworks over blaming individual people. And yup, think this comes along with, "incident yesterday was intense, I'm gonna catch up on sleep".
- pm90 5y agoI agree with your comment. These names are just ways for teams to delegate different responsibilities w.r.t incident management quickly and in a way that's understood by everyone. Having concrete names for such roles is both a good thing (everyone knows who can make the call for hard decisions) and helps you talk intelligently about the evolution of such roles. e.g. "our Incident Commanders used to spend 15% of their time in p0 incidents, but that has reduced to 10% due to improvements in rollout procedures/runbooks/etc."