Symptoms Aren't Problems

A truck gets stuck under a bridge. Engineers want to cut the truck. Construction wants to raise the bridge. A kid walks up and asks why no one's letting air out of the tires.

The kid wasn't smarter. He was looking past the situation to the constraint underneath. The bridge and the truck were what everyone could see. Height was what mattered.

Most people don't do this. They name what's broken: the meeting felt off, the numbers dipped, the team is missing deadlines, your kid is acting out. They fix the list. Then it comes back in a different shape. The team that hits its deadlines now misses scope instead. The numbers that recovered dip again somewhere else. Same root, new mask.

Symptoms are loud because they're observable. Causes sit underneath. They're quieter, often uncomfortable to name. The work is asking "why" past the first answer that sounds plausible.

"Sales dipped" is the report. The first answer is "our best AE left in February." That's still a symptom. The cause is that one person's exit was enough to move the number at all. The fix isn't a faster hire. It's a system that doesn't depend on heroes.

"The team is missing deadlines" is what you see. The first answer is "we underestimate." Ask why again. "We plan as if nothing will go wrong." That's the cause. The fix isn't a new estimation tool. It's budgeting for the surprises you already know are coming.

When you find the actual cause, the fix is usually small. Let air out of the tires. That's how root causes go. Simple, elegant, permanent. You addressed what was generating the problem, not what it produced.

The world is mostly noise. Most people grab the loudest thing in the pile and call it the answer. The work is staying with the question long enough to find the one underneath.

Anyone can name the symptoms. The person who can name the cause is the person worth listening to.

Symptoms tell you something is wrong. Causes tell you what to do about it.