The Exception That Wouldn't Stay Hidden
Not the dramatic kind of failure — the kind with alarms and shutdowns. I'm talking about the other kind. The kind that gets a nod, a "we'll sort it later," and a quiet walk past.
A torque check fails on a Thursday afternoon. Everyone knows. Someone says they'll come back to it. The shift ends. And the exception begins its slow disappear into the noise of next week.
The list that everyone trusted
Every site has one. A spreadsheet, a whiteboard, a folder of open items. The trouble was never listing the exception. It was what happened after: nothing. No owner that meant it. No date that meant it. No closure that proved it.
An exception without an owner isn't managed. It's just remembered. Until it isn't.
What it means to actually close something
Closing a failed check should be harder than noticing it. Someone accountable, a reason, the evidence, a date, and a second pair of eyes when it matters. Not a checkbox. A decision. And if it can't be closed, it doesn't vanish — it escalates, visibly, to someone whose job it is to decide.
The follow-up question shouldn't be "did we log it?" It should be "who closed it, and what did they see?"
One thing worth trying this week: look at your open exceptions list. For each item, can you name the person and the date? If you can't, you don't have a list of exceptions. You have a list of hopes.