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 wasn’t looking at the situation. He was looking at what was generating the situation. That’s the distinction most people never make.

A symptom is what you can observe: the meeting felt off, the numbers dipped, the team is missing deadlines, your kid is acting out at school. A cause is what is producing the symptom. They’re not the same thing. Treating them as if they are is why the same problems keep coming back in new costumes. The team that starts hitting its deadlines begins missing scope instead. The numbers that recovered dip again somewhere else. The root is still there. You just decorated it.

Two axes help you locate where you actually are. The first is proximity: are you describing the event, or what made the event possible? “Sales dipped” describes the event. “Our best AE left” is one level deeper but still describes the event. “One person’s exit was enough to move the number” describes what made the event possible. That’s a different category. The second axis is recurrence: is this the first time, or has some version of this happened before? If it’s happened before, you haven’t found the cause yet. You’ve been solving the symptom.

The first answer that sounds plausible is almost never the cause. It’s the loudest symptom. Name it and keep going.

Ask why until the answer stops describing this situation and starts describing how the system works. “We underestimate” is still a symptom. “We plan as if nothing will go wrong” is a system.

The real cause is usually uncomfortable. Root causes tend to point at a default you’ve been protecting: a hire you didn’t want to make, a meeting you didn’t want to cancel, a yes you didn’t want to take back. The discomfort is a signal you’re close.

When you find the actual cause, the fix is usually small. Let air out of the tires. Simple, quiet, permanent. If the fix feels large and complex, you’re probably still operating on a symptom.

This compounds. The person who keeps digging stops getting hit by the same problem in different packaging. Their decisions age well. They look slow in the moment and fast over a year.

Before you act, run these questions. Has some version of this happened before? If yes, what did you do last time and why is it back? What would have had to be true for this to not happen at all? If you fixed what you’re about to fix, could the same result recur through a different path? Is the discomfort you’re feeling about the fix pointing at a protected default?

One edge case worth naming: sometimes the symptom is exactly the right place to act. If someone is bleeding, you stop the bleeding before you ask why they fell. Urgent situations call for triage first. The mistake is staying in triage mode once the immediate crisis is over, treating the stabilization as the solution. Stopping the bleed buys you time to find the cause. It doesn’t replace finding it.

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