You Do Not Know How Bad It Is
There is a particular kind of naivety that is not about being young or uninformed. It is the naivety of assuming that things work because they appear to work. The company is profitable, so the management must be competent. The bridge carries traffic, so it must be structurally sound. The software handles millions of requests, so the architecture must be solid.
Often, the truth is less reassuring.
The Hidden Fragility
Most systems — technical, organizational, societal — are held together by a smaller number of people than you would expect, working harder than you realize, compensating for dysfunction that is invisible from the outside. The software works because one engineer has memorized the quirks and manually intervenes when things break at 2 AM. The department hits its targets because three people routinely work 60-hour weeks. The institution functions because a handful of dedicated employees cover for the gaps that management refuses to acknowledge.
When those people burn out, quit, or get sick, the system does not degrade gracefully. It breaks suddenly, and everyone is surprised — everyone except the people who were holding it together.
Why You Do Not See It
Survivorship bias. You see the systems that are working. The ones that failed are invisible or forgotten. The fact that your company still exists does not mean it is well-run — it may mean it has not yet encountered the shock that exposes its fragility.
Competence conceals problems. Skilled people make broken systems look functional. A great developer can ship reliable software despite terrible infrastructure. A talented manager can maintain team morale despite toxic leadership. Their competence masks the underlying problems.
Nobody wants to talk about it. Admitting that things are bad is risky. The engineer who says “our infrastructure is fragile and we are one incident away from a major outage” is often seen as negative rather than honest. The doctor who says “this hospital is dangerously understaffed” risks retaliation. Silence preserves the illusion.
What to Do With This Knowledge
Not panic. But also not assume that the absence of visible problems means the absence of actual problems. Look at the systems you depend on — your company, your infrastructure, your community services — and ask: who is holding this together? What happens if they leave? What risks are being absorbed by individuals rather than addressed by the system?
The answer is usually “it is worse than it looks.” Knowing that is the first step toward either fixing it or preparing for when it breaks.