Who it's for
An owner or CEO who has received a ready-made explanation of a problem from the team and wants to check it before allocating a budget.
Key idea
A cause is something that, once removed, keeps the symptom from coming back. Everything else is a hypothesis that still needs to be tested.
Contents
- Why the mind picks the symptom
- The three levels where a problem lives
- The cause test: four questions
- The five most common chains
- The "five whys" method and its real problem
- When you do need to treat the symptom
- What to do this week
Take the self-assessment
A business almost never arrives saying "our management system is broken." It arrives saying "we need marketing," "we need a CRM," "we need a new head of sales." That's no longer a problem but a chosen solution. And most often it was chosen before anyone checked the underlying picture.
The difference between a symptom and a cause isn't philosophical. It's measured in money: how many times you pay for the same problem.
Why the mind picks the symptom
A symptom is visible, measurable and triggers emotion. A cause is usually dull, spread across several functions, and belongs to no one personally. So an organization naturally drifts toward the explanation that a) is already familiar, b) doesn't require admitting anyone's mistake, and c) can be bought from outside.
Principle
The more convenient an explanation of a problem is for those who propose it, the more carefully it needs to be checked.
This isn't about distrusting your team. It's that from inside a system, it's almost impossible to see the system itself. A person who closes a gap by hand every day stops noticing the gap is there. To them, it's just work.
The three levels where a problem lives
It helps to break any complaint down into three levels. The levels don't compete; they're nested inside each other.
- 01
Event
What happened: a deal fell through, a key person left, the month closed at a loss. Events are noticeable and demand a response. Working at this level means firefighting.
- 02
Pattern
What repeats: deals fall through at the same stage, people leave the same department, losses happen in the same months. A pattern is only visible over time, never in a single moment.
- 03
Structure
What generates the pattern: how roles, data, incentives and feedback speed are set up, and who makes decisions. Structure is almost never discussed in meetings because it's taken as a given.
The rule is simple: if you work at the event level, you'll be working forever. If you've found a pattern, you're close. If you've changed the structure, the symptom disappears without your involvement.
The cause test: four questions
Before agreeing with any explanation of a problem, run it through four questions. An explanation that doesn't pass all four isn't a cause yet.
- 01 If we remove this, will the symptom stop coming back on its own, or will we have to keep holding it down by hand?
- 02 Does this explain every known instance of the problem, or only the latest, loudest one?
- 03 Can we show it in the data, beyond the impressions of people who have a stake in it?
- 04 Is this within our control, or are we blaming the market, the season and the government?
Trap
Successful companies fail the fourth question most often. An external explanation removes responsibility, so it seems mature and sober. The market does have an effect, but the market is the same for those who are growing.
The five most common chains
Below are typical paths from how a problem is phrased to where it usually lies. This isn't a diagnosis of your business. It's a map of places worth looking.
How the request sounds Where the cause usually lies
"We need marketing, we're not getting enough leads" The economics of acquisition and conversion further down the funnel: the leads exist, but they don't pay off or don't reach a deal
"We need a CRM, the salespeople don't log their deals" No definition of a deal and no stage criteria: people have nothing to record consistently
"We need a new manager" A role with no authority and no success criterion: the next person will land in the same structure
"We need to scale" Unit economics that don't work: scale will multiply the loss by the number of locations
"We need automation" The process isn't documented or stable: automation will lock the current mess into code
Related service: Express Business Audit
A format for testing these chains on your data in a short time.
The "five whys" method and its real problem
The classic technique is to ask "why" five times in a row. It works, but it has a flaw that's rarely mentioned: it's linear. The real cause usually lies where two or three branches intersect.
A practical fix: at each "why," ask two questions, "why did this happen" and "why didn't we notice it sooner." The second branch almost always leads to the structure: missing data, no owner, feedback that's too slow.
A missing signal is also a cause. It's often more expensive than the breakdown itself.
When you do need to treat the symptom
There's one case where working on the symptom is right: when the business is losing money faster than you can make sense of the structure. In a crisis, you stop the bleeding first and look for the cause after. Putting out a fire isn't a mistake. The mistake is stopping once it's out.
Related service: Crisis Management
When stabilization has to come first, with diagnosis right behind it.
What to do this week
Questions to ask yourself
Take one problem that's bothering you right now
- 01 How is it phrased right now: as a problem, or as a solution that's already been chosen?
- 02 Is it an event, a pattern or structure? What would have to happen one more time for you to accept it as a pattern?
- 03 Who inside the company benefits from the current explanation of the problem?
- 04 What data would confirm this explanation, and do you even have it?
- 05 If you couldn't buy an outside solution, what would you change internally?
If there's no honest answer to the third question, that's already a useful result. It means the explanation is worth checking before the budget, not after.
Materials that continue the topic
- The cost of doing nothing
- Strategy as a list of refusals
