Retrofitting incident reviews that change the system onto a field service platform

Greenfield advice is easy to write and not much use. This is the same idea applied to a system already carrying production load that isn't allowed to stop, with the compromises left in view.

Most incident reviews produce a document and no change. The difference between the ones that work and the ones that don't isn't blamelessness. It's whether any action item removes a decision rather than asking someone to be more careful.

THE TIMELINE IS THE WHOLE EXERCISE

Building an honest minute-by-minute timeline is where the learning is, and it's the part people rush. Almost always it shows that the technical fault was brief and the expensive part was the twenty minutes establishing what was happening, or the ninety minutes waiting for someone with access.

That's a much better finding than the root cause, because it's about how you respond to a whole class of problems rather than one bug you've now fixed and won't see again.

ACTIONS THAT SURVIVE

Two kinds of action item survive contact with the next quarter: ones that delete a possibility, and ones that shorten the feedback loop. "Add a constraint so this state can't exist" survives. "Be careful when editing this config" does not, and everyone in the room knows it while they're writing it down.

We now sort the list into those two categories before anyone gets assigned anything, and drop the rest. A shorter list that happens beats a thorough list that doesn't.

The code wasn't the hard part. Convincing schedulers that a second reader wouldn't cause a technician drove three hours to a job someone had already closed was, because the last project that promised that did exactly that.

BLAMELESS IS A MEANS

The reason to run these without blame isn't kindness, it's data. People who expect consequences describe what they should have done rather than what they did, and then the timeline is fiction and the exercise is worthless.

It's worth stating that reason out loud, because "blameless" said without explanation sounds like a policy about feelings, and people rightly don't trust policies about feelings during a stressful review.

We ran both paths against live traffic for three weeks and compared every work order. The mismatch rate started at four percent, all of it the old system's undocumented rounding.

WHERE IT GOES WRONG

• A timeline assembled from memory a week later, describing what people wish had happened.
• "Blameless" declared without explaining why, so nobody believes it.
• A root cause identified and fixed, while the twenty-minute diagnosis delay goes unexamined.
• Action items that ask people to be careful, quietly abandoned within a quarter.

Keep the actions that delete a possibility. Drop the ones that ask for more care.

WHAT THE MIGRATION COST

Eleven weeks, one reverted step, nothing customer-visible. The reverted step was the one where we changed two things at once. We keep relearning that and we keep writing it down.