Reviewing what went wrong without ending at a name

Where a review stops is a choice, and it is made early

Every review of something that went wrong could stop at several different points. It could stop at the person who pressed the button. It could stop at the supervisor who approved the run. It could stop at the template, the deadline, the missing second reader, the absence of any way to test. Each of those is a true account of the same event. Only some of them change anything.

Reviews stop at a person for a reason that has nothing to do with anyone’s intent. A name is a complete answer. It fits in a sentence, it satisfies the request, it closes the file, and it is the cheapest possible finding. A condition is an incomplete answer that creates work: somebody has to own it, somebody has to change it, and somebody has to check whether the change held. Under time pressure, the cheap answer wins unless a unit has decided in advance that it will not.

The test that keeps a review honest is reconstruction. Ask what this person could see at the moment they acted — what the screen showed, what the deadline was, what they had been told, what had happened the last forty times they did the same thing. Then ask what made this the reasonable action given that. There is almost always an answer, and the answer is the condition. If you cannot find one, you are still reasoning from what is obvious now rather than from what was available then.

None of this makes anyone unaccountable. Accountability is the part that produces a change with a name attached to the change, a date, and a check. Blame produces a name attached to the mistake and a reminder to be careful. One of those is still true in six months.

The same notice, written four ways

“The analyst failed to update the effective date before releasing the mailing. Coaching has been provided.” True, complete, closed. Every condition survives it, and the next analyst inherits all of them plus the knowledge that the cost of an error here is personal.

Where a learning review stops and a formal process begins

Reports of maltreatment

If anything in a review suggests maltreatment of a vulnerable adult or a child, the reporting obligation is immediate, it belongs to the person who learned it, and it does not wait for a review to reach a conclusion. The responsible DHS office for investigation takes it from there. A learning review never substitutes for that report and never delays it.

Licensing and contract enforcement

Findings about a licensed program or a contracted provider belong to the offices that hold the license and the contract. Your review can identify a condition the division owns — a template, a deadline, a payment rule, an oversight gap — and it should. It cannot decide a licensing action, and it should not be written as though it might.

Appeals and fair hearings

A person disputing a decision about their own services has a formal route with legal timelines. That route is theirs and it runs independently. What a quality unit can learn from a pattern of appeals — which notices are disputed, in which regions, in which languages — is useful and is a different piece of work.

Complaints of discrimination and personnel matters

Complaints of discrimination, harassment or retaliation, and any question of discipline, belong to the responsible human resources, civil rights and legal offices. A learning review that starts drifting toward whether someone should be disciplined has left its lane; hand that part over and keep working on the conditions.

Send conditions upward when a director asks who

What you can change

You control what the account says, and you can answer a narrow question with a fuller answer without refusing it.

What to watch for

Do not send only a name, and do not withhold one either. A name alone closes the matter. A refusal makes the review look like protection, and the next request comes with less patience.

Your next step

The next time a senior leader asks who, send four lines — what happened, what made it reasonable, what changes with an owner and a date, and what is being done for the people affected — and note that the name is available.

Which finding from an incident review can still be acted on six months from now?

Staff will take additional care when entering effective dates on outgoing notices.

The notice template’s default date field is removed and date changes require a second reader; the communications lead owns both, and the quality unit checks the next two print runs.

The unit will review its notice procedures and reinforce expectations with the team.

The analyst responsible has received coaching and the matter is closed.

Try a situation

A benefit notice for a group of people receiving disability services went out with an effective date three weeks earlier than intended. Roughly a hundred households called; a few had already canceled a service they thought was ending. The template carries a default date that must be overwritten by hand, the print deadline had moved up by two days, there is no second reader for date fields, and there is no way to test a notice against a small sample before the full run. A director asks the quality unit for a short account by the end of the week and wants to know who sent it.

What does the quality unit send the director?

The name of the analyst who released the mailing, with a note that coaching has been provided and the matter is closed.

Four lines: what happened, what made it reasonable at the moment, what changes with an owner and a date, and how the households affected are being told — with the name available if the director still wants it, and a note on where the formal processes sit.

Hold the account until the formal review of the mailing has concluded, so that the two do not contradict each other.

Carry this forward

The person closest to an error is usually the last condition in a long line, and by far the easiest one to name. Naming them ends the review and leaves every earlier condition exactly where it was.
Blame and accountability are different products. Blame produces a name and a reminder to be careful. Accountability produces a change, an owner, a date, and a check that someone can look at afterward.
The useful question is what made this the reasonable thing to do with the information, tools and time available at that moment. If the honest answer is “nothing,” you have not found the conditions yet.
Formal processes — reports of maltreatment, licensing, appeals, complaints of discrimination, discipline — run on their own authority and their own schedule. A learning review neither replaces them nor waits for them to finish before repairing a condition it already understands.
When a review turns into two camps, the region against the central office or the unit against the contractor, it has slipped into Polarization and the condition has stopped being examined. Bringing it back means asking both sides what they could see from where they were standing.

A scenario about a notice released with the wrong effective date, tabs showing the same event written four ways, an accordion on where a learning review stops and a formal process begins, and a knowledge check on what makes a review line usable.

Take the last thing that went wrong in your area and rewrite the account in four lines: what happened, what made it reasonable at the time, what changes, and who checks it and when. Let the person closest to the work read it before anyone above you does.

Your next step

Think about the last review in your area that ended with a person’s name. What was still true about the process the following week?

Write the same account again, ending at a condition rather than at a person, and see how much longer it takes

Name one condition from that event that is still in place, and who could change it

Check whether the people affected were ever told what happened, in a form they could use

Ask who else could have caught it, and what stopped them — that answer is usually a condition too

What you’ll be able to do

Where a review stops is a choice, and it is made early

The same notice, written four ways

Where a learning review stops and a formal process begins

Send conditions upward when a director asks who

What you can change

What to watch for

Your next step

Try a situation

Carry this forward

Your next step

Reviewing what went wrong without ending at a name

What you’ll be able to do

Where a review stops is a choice, and it is made early

The same notice, written four ways

Where a learning review stops and a formal process begins

Send conditions upward when a director asks who

What you can change

What to watch for

Your next step

Try a situation

Carry this forward

Your next step