I know managers who take pride in how fast they close a problem. An issue surfaces, a meeting is called, someone does something, a report is filed. Three months later the same problem returns in a different department, under a different customer complaint, or disguised as a separate cost overrun. A mid-sized food manufacturer in Konya — roughly 295 employees, supplying both domestic retail chains and private-label clients — was dealing with chronically high return rates before the pandemic hit. Sales said customer expectations were shifting. Logistics said cold-chain conditions were tightening. Production said raw material quality was inconsistent. Each team was partially right. But none of them owned the problem, because each was describing a symptom, not the system underneath it. That is exactly where meaningful problem solving either starts or stalls.There is a common misconception about root cause analysis: that it is a technical exercise. Ask ‘why’ five times, draw the fishbone diagram, produce an action plan. The toolkit is sound. Yet in most applications I have observed, even when the tools are used correctly, the outcome remains shallow. The reason is consistent: the tools exist, but the honest data required to feed them does not. By the time you reach the fifth ‘why’, the answer is no longer technical — it is human or organisational. ‘Why did quality control approve this batch?’ inevitably leads to answers like ‘the decision was made under deadline pressure’ or ‘the approval criteria were ambiguous’. Accepting those answers in a meeting room takes courage. That is precisely why the real issue is culture, not method. Analytical discipline only works when built on a foundation of organisational honesty.Let me state my thesis plainly, because I think it is consistently misunderstood: root cause analysis is not primarily a data problem — it is a problem of power and accountability distribution. The person who patches the symptom quickly gets praised. The person who identifies the root cause and proposes a system change is often framed as ‘someone who complicates things’. In the Konya food manufacturer, the person who identified the real root cause of the return rate problem was the production quality supervisor. His proposal — adding a second verification layer to the shipment approval process — was initially rejected over concerns about delivery delays. Six weeks later, when the return wave escalated into a critical complaint from a major retail chain, the same proposal was implemented. The real question is: what did those six weeks cost?When the pandemic disrupted supply chains in early 2020, these kinds of organisational blind spots became dramatically visible. In teams that shifted to remote work, coordination failures grew rapidly: delays accumulated, customer complaints intensified, inventory discrepancies multiplied. The majority of managers addressed these symptoms separately — calendars were updated, messaging tools were deployed, additional check-in meetings were added. The Konya firm followed a similar path. By the end of 2020, return rates had not spiked again, but shipment coordination errors climbed back. The root cause — ambiguity in the approval process — had not been resolved; remote work simply made it more visible. The pandemic did not create new problems. It exposed existing fragilities. Believing that the pandemic caused the organisation’s problems is itself an act of mistaking symptom for root cause.So what does reaching a root cause actually look like in practice? Three steps, in this order. First: define the symptom with data, not intuition. ‘Returns are increasing’ is a sentiment. ‘Over the past 11 months, 57 per cent of returned units were logged within 72 hours of shipment approval, and 73 per cent originated from the same three SKUs’ is a problem statement that prevents you from chasing the wrong root cause. Second: as you pull the chain of causes, do not stop before you reach a human decision or a process gap. The fifth ‘why’ will always lead to a person’s judgement call, an unclear standard, or a misaligned incentive. Stopping the analysis before that point means accepting the symptom and ignoring the actual problem. Third: the proposed fix must address the root cause you identified — not a side branch of it. When this check is skipped, teams solve adjacent issues and mistake the activity for progress. In Konya, the quality supervisor’s proposal targeted the exact root cause: process ambiguity in the approval stage. That is why it worked.I should be direct about the limits here. For small and mid-sized Turkish businesses operating under significant budget pressure in 2021, data quality often cannot reach the level of granularity that rigorous root cause analysis requires. To answer ‘which SKUs are driving returns?’ you need an ERP configured to track stock movements at that level of detail, with consistent entry discipline across shifts. Without that infrastructure, analysis defaults to intuition — and intuition tends to believe the symptom. Add to this the reality that currency pressure and inflation in Turkey’s current business environment push managers toward fast symptom resolution. Long-term root cause work gets deferred to ‘later’. I understand that instinct. But when ‘later’ never arrives, the same problem returns with double the weight at the next crisis point.Back to the Konya food manufacturer. After the second verification layer was added to the shipment approval process, coordination errors declined noticeably over the following four months. But the more durable outcome was something else: the quality supervisor was no longer seen as someone who complicates things. He became the person who could see the system. That cultural repositioning outlasted any software installation or process diagram. If your team is repeatedly ‘solving’ the same problem, stop and ask one question aloud in your next meeting: are we patching a symptom, or are we changing the system? Asking that question openly — and being willing to sit with an uncomfortable answer — is worth more than any analytical framework you can deploy.
This article was originally published in Turkish by Gökhan MERCANOĞLU on January 14, 2021. The English edition has been reviewed and edited by the author.