A finance director opens the quarterly review with a clean line: ‘Budget overrun last quarter because market conditions moved outside our projections.’ The room nods. No follow-up question is asked. The meeting wraps in five minutes. What actually caused that overrun? More likely something else entirely — a flawed forecasting assumption, an overlooked supplier risk, or a cost deviation spotted three months earlier and quietly left unreported. But nobody asked. Because the first explanation was both plausible and comfortable.This is where the real test of critical thinking in business begins. Saying ‘consider alternative hypotheses’ in a workshop is easy. Saying ‘is this actually correct?’ after a senior figure has just explained something — under time pressure, under hierarchy, in front of colleagues — is a genuinely different skill. In Turkish business culture, that second question is rarely asked aloud. And the cost of that silence eventually shows up in the decisions that follow.My core argument here is this: the discipline of not believing the first explanation has almost nothing to do with how analytically capable you are, and everything to do with how willing you are to be momentarily uncomfortable. Most managers have the intellectual capacity to question. The problem is the precise moment they choose not to use it — and that moment is usually not a failure of intelligence. It is a failure of organizational safety, expressed through cultural automatism.Consider an insurance brokerage firm based in Istanbul — roughly 295 employees operating across five provinces in Anatolia — where I observed a telling pattern over the past year. Customer churn had risen steadily across six consecutive quarters. The first explanation was ready and waiting: ‘Competition has intensified, pricing pressure is real.’ Management accepted it and launched discount campaigns in response. Churn continued anyway. Eleven months later, a working group was formed — this time because one person insisted on asking why customers were actually leaving. Survey data and exit feedback told a different story: 62 percent of departing customers cited delays and opacity in claims processing, not pricing. The solution was a process redesign, not a price cut. But for eleven months, the organization believed the first explanation and paid for it.This case illustrates why critical thinking operates conditionally. The ‘competition increased’ explanation was not wrong — competition had increased. But it was answering the wrong question. That is precisely the trap of the first explanation: being partially correct grants it the status of fully correct. And a partially correct explanation routinely produces a fully incorrect response. My practical recommendation follows three steps. First, when an explanation is offered, ask aloud — visibly, on record — ‘what data is this explanation not using?’ Second, before accepting any first explanation as the basis for a decision, generate at least one alternative hypothesis and put it to the group; a decision built on a single narrative is structurally fragile. Third, when time permits, open a short verification window of two to four weeks of actual data collection; this almost always clarifies whether the first explanation is complete, partial, or misleading.Now for the legitimate counter-argument — because it is a real one. ‘Questioning everything kills pace’ is a fair point, but it describes the wrong situation. In an operational emergency, a genuine crisis, or a moment of extreme information asymmetry, adopting the first credible explanation quickly is often the right move. What is worth challenging is the application of that same reflex — automatically, without examination — to routine planning reviews, strategic realignments, and resource allocation decisions. Critical thinking is not equal-opportunity scepticism about everything. It is the deliberate habit of pausing at the right moment to ask the right question. A management team that cannot distinguish these two scenarios either accepts everything or questions everything; both are expensive defaults.There is a dynamic specific to Turkey’s business environment that makes this discipline harder to embed. Holding two ideas simultaneously — respecting hierarchy and acknowledging that a senior person might be wrong — feels contradictory to many employees. It should not. A critical question is not an act of disrespect; it is a request for alignment. ‘Can we see the data behind this explanation?’ is an invitation to a stronger decision, not a challenge to authority. Without this cultural reframing, technical questioning skills never become organizational habits. People absorb the cultural cost before they even formulate the question, and so they stay quiet.Returning to the insurance firm: the working group that finally understood the real driver of churn was not initiated by the company’s most senior executive. It was started by a claims operations team leader — someone close enough to the daily customer voice to sense the gap. That person had not raised the question eleven months earlier, because the meeting culture had not made it safe to do so. The discipline of not believing the first explanation is therefore not an individual intelligence matter. It is an organizational safety matter. If the person who asks the uncomfortable question can leave that meeting feeling respected rather than exposed, the organization has built this discipline into its operating system. If not, no training budget will move it from the classroom into the room where the actual decisions get made.
This article was originally published in Turkish by Gökhan MERCANOĞLU on January 29, 2022. The English edition has been reviewed and edited by the author.