When a deficiency is allowed to stay open

The first time a crew sees a deficiency list, someone will try to get it to zero before the next meeting. I understand the impulse. An empty list looks like control. An empty list the day after you started is usually a lie, or a set of closes that say “done” and mean “we looked at it.”

Some failures should stay open. A hinge pin that needs a dry week. A pole item that waits on a planned outage. A dorm deficiency that is honestly a break project. Closing these to tidy a meeting is how you teach everyone that the list is theater. Theater lists get ignored, and then the item that should have blocked a startup is sitting in the same ignored pile. That is the failure mode. Not the open pin. The wallpaper.

A hold is the state we added so “not today” could be true without being vague. It needs an owner, a reason, and a review date. The date is the whole trick. “When we get to it” is not a date, and the product will not save a hold without one. On the morning of the date, the item is back on the open list, looking like work. People curse this. The curse is a sign the date was real.

I want holds to remain visible. A hold is not a close and not a footnote. The pack shows holds in the front section, separate from the blocks, so a startup supervisor can treat a food-contact hold as a stop and a door-sweep hold as a known delay. If you hide holds in a tab called “later,” later becomes never, and never becomes a surprise.

There is an opposite mistake, and I see it in careful people. They refuse to hold anything, so the open list is eighty items of mixed urgency and nobody can find the two that matter today. Holding is not indulgence. Holding is a sort. The pin is held until Thursday. The gasket is not held at all. Both can be true, and the list can be short enough to read at 5:10.

Who decides is the supervisor, not the software, and not the inspector who wants to go home. The inspector records the fail. That part is not optional and not rude. The supervisor holds or closes or leaves it open without a hold, which is also allowed and means “this is live.” An inspector cannot close someone else’s item. They also should not be the person who buries it in a long hold to be helpful. Helpful holds are how a gasket becomes a break project. If you feel the urge to be helpful with a date, you are probably in the wrong role for that click.

East Ward’s sixty-three open pole items at the end of a cycle are the example I use when a buyer flinches. Helen Park is not ashamed of the number. A number with names and dates is a plan. A number with neither is a folder. If your cycle ends at zero because you closed forty items the night before the report, I do not believe the zero, and neither will the person who walks the pole in the rain next year.

Review dates slip. That is fine if the slip is visible. You move the date, the history shows the move, and you say why. Slipping a date in silence, or building a workflow that lets a date slide a week without a person, is wallpaper with a calendar. I will not ship an auto-snooze. I have been asked. The answer is no, in writing, here.

If your list is already wallpaper, do not import it into Tidep and hope the new list smells better. Sit down, mark the items that block, hold the ones with a real date, and close the ones that are already done with a note that says what “done” was. Delete nothing that happened. Then walk for a week without adding a new kind of item. A week of a short true list is worth more than a migration.

The permission to stay open is not a lowering of standards. It is how a standard survives contact with a calendar. A standard that demands zero by Friday will be met with fiction. A standard that demands a name and a date will be met with a list you can argue about. Argument is the work. Fiction is the thing we are trying not to typeset.