Yeah, at $WORK, the incident doc has a section for corrective actions. And they mostly get done, but having them struggle for priority with regular work is a problem.
Also, it occurs to me that we leaders should do a better job of saying, "look at that excellent job of attacking that corrective item that team just did!" so that it's clear to people that this is not clean-up work, but in fact the most essential kind of tech debt that's actively being paid down, which identified itself as such by causing an outage.
Comments
Yeah, at $WORK, the incident doc has a section for corrective actions. And they mostly get done, but having them struggle for priority with regular work is a problem.
Also, it occurs to me that we leaders should do a better job of saying, "look at that excellent job of attacking that corrective item that team just did!" so that it's clear to people that this is not clean-up work, but in fact the most essential kind of tech debt that's actively being paid down, which identified itself as such by causing an outage.