Notes from a regional housing authority: incident reviews that change the system

The first thing we asked for wasn't a spec. It was thirty case record records picked at random, exceptions left in. That sample told us more about the place than the requirements document did.

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 clearest thing we saw was how caseworkers handled a contested case record. On paper it's one step. In practice it's five, three of them over the phone, none of them written down. Which is why nobody could ever explain statutory turnaround to their director.

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.

Here it showed up as a queue nobody owned. Roughly 6,000 open cases went through it, and caseworkers had learned to check it twice a day because the alternative was a statutory clock was missed because the case had two owners. A better queue wasn't the answer. Making ownership a property of the case record was.

WHERE IT GOES WRONG

• 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.
• A timeline assembled from memory a week later, describing what people wish had happened.
• "Blameless" declared without explaining why, so nobody believes it.

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

WHAT WE TOOK AWAY

The work shipped and statutory turnaround moved, but the thing we're proudest of is smaller than the system: caseworkers stopped keeping a private spreadsheet. That's usually the honest signal that the model finally matches the job.