Most consulting engagements begin with a problem statement. It's usually wrong.
Not because the client is dishonest or uninformed. Because problems are layered. The visible problem — declining margins, slow growth, operational friction — is often a symptom of something structural underneath.
We call this the problem behind the problem.
Symptoms vs. structures
A retailer sees declining foot traffic and commissions a digital marketing campaign. The campaign works. Traffic increases. Revenue doesn't. Because the real problem wasn't awareness — it was that their product positioning had drifted from what their best customers actually valued.
A manufacturer invests in automation to reduce costs. Costs drop. Quality issues rise. Customer churn accelerates. The problem wasn't labour cost — it was process variability that automation amplified rather than solved.
These aren't failures of execution. They're failures of diagnosis.
How to find the real problem
Question the framing. Who defined this as the problem? What incentives shaped that definition? What would change if the problem were defined differently?
Look for patterns, not incidents. Single events feel urgent. Recurring patterns reveal structure. Map the pattern across time, teams, and contexts.
Follow the decision. Most organisational problems are decision problems in disguise. Trace backwards from the outcome to the decision that produced it. What information was available? What wasn't? Who had authority? What constraints were invisible?
Test with small experiments. Before committing to a large solution, design small tests that would confirm or refute your hypothesis about the underlying problem.
The Ludens approach
We don't start with solutions. We start with structured inquiry — a disciplined process of questioning assumptions, mapping systems, and testing hypotheses until the real tension becomes visible.
It's slower at the start. Faster everywhere after.
Because solving the right problem is the highest-leverage activity any organisation can undertake.