Why Symptoms Mislead
Why we confuse symptoms with causes — and why it matters for diagnosing friction and improving judgment.
The Core Argument
We often treat symptoms as if they were the problem. This leads us to solve the wrong thing — and leaves the real problem untouched.
When something goes wrong, we look for a cause. But what we find is often a symptom — not the underlying problem.
This is one of the most common sources of friction in organisations. We try to fix what we can see — the symptom — while the root cause continues to operate.
Diagnosing friction requires distinguishing symptoms from causes.
The Symptom-Cause Confusion
Why we get it wrong.
Symptoms are visible
Symptoms are easy to see. They are the surface-level indicators that something is wrong. Causes are often hidden beneath the surface.
Symptoms are urgent
Symptoms demand attention. They create pressure to act. This pressure often leads to quick fixes that address the symptom but not the cause.
Causes are complex
Causes are often complex and multi-layered. They involve multiple factors, relationships, and feedback loops. They are harder to understand and harder to fix.
Causes are uncomfortable
Root causes often involve uncomfortable truths — about culture, leadership, incentives, or design. It is easier to blame a symptom than to confront a cause.
The Acacia perspective:
The symptom-cause confusion is not a personal failing. It is a systemic problem. Our organisations reward quick fixes, not deep diagnosis. We must design systems that encourage and enable root cause analysis.
Real-World Examples
How symptoms mislead in practice.
Slow decision-making
Symptom: Decisions take too long.
Typical fix: Speed up the process, reduce approvals.
Root cause: Unclear authority, lack of information, fear of failure.
Why the symptom misleads: Speeding up the process may make things worse if the root causes are not addressed.
Poor communication
Symptom: Teams are not communicating well.
Typical fix: More meetings, better tools.
Root cause: Misaligned priorities, lack of trust, unclear roles.
Why the symptom misleads: More meetings may just create more noise if the root causes are not addressed.
Low engagement
Symptom: Employee engagement is low.
Typical fix: More perks, better benefits.
Root cause: Lack of purpose, poor leadership, lack of autonomy.
Why the symptom misleads: Perks may not address the underlying issues that are causing disengagement.
Key insight:
In each of these examples, the typical fix addresses the symptom — not the cause. The problem persists because the root cause is still there.
How to Avoid the Trap
Moving from symptoms to causes.
1. Ask "Why?"
When you see a symptom, ask "Why?" Keep asking until you reach a cause. This is the foundation of root cause analysis.
2. Look for patterns
One symptom is an event. Multiple symptoms are a pattern. Look for patterns to identify the underlying cause.
3. Involve others
Different people see different parts of the problem. Involve others to get a fuller picture of the root causes.
4. Resist quick fixes
Quick fixes are tempting. But they often make things worse. Resist the urge to fix the symptom before you understand the cause.
5. Test your diagnosis
Once you have a diagnosis, test it. Does it explain the symptoms? Does it point to a solution? If not, keep digging.
The Acacia perspective:
Moving from symptoms to causes is the core diagnostic skill. It is what separates good judgment from guesswork. ContextOS is designed to support this skill — by providing a structured way to understand the situation and identify the root causes.
Reading path: