Perceive and don’t tolerate problems

When that safety isn't there, problems don't disappear — they just go underground, and the organization keeps producing the same bad outcomes while everyone involved acts surprised each time, because nobody said anything until it was too late to matter.

I think of this as similar to a doctor reading symptoms. A good diagnostician doesn't get annoyed at a patient's symptoms for being inconvenient — the symptom is the useful data point, the thing that tells you where to look. An organization that treats a raised problem as an inconvenience rather than as diagnostic information is training its own people to stop reporting symptoms, which is exactly backwards.

Not tolerating a problem doesn't mean reacting with panic or treating every issue as a five-alarm fire — that overcorrection burns people out and makes them less likely to surface the next one. It means refusing to let a known issue become background noise that everyone has quietly agreed to live with. Capture the problem explicitly, assign clear ownership for addressing it, and track it until it's actually resolved rather than until people stop mentioning it. The moment a known problem is allowed to sit untouched, you've taught the entire organization, without saying a word, that the stated standards are actually negotiable.

Many organizations instinctively prefer harmony over accuracy — smoothing over friction feels better in the short term than naming what's broken. But accuracy is what protects long-term performance, and harmony bought by silence is a loan against the future with a high hidden interest rate. Seeing problems early is a genuine structural advantage, simply because small, fresh problems are almost always cheaper and faster to fix than the same problem left to compound for another year.