Picture a textile manufacturer in Denizli running 295 employees across weaving and dyeing operations under one roof. At the peak of the export season — that gruelling corridor between late July and early October — the factory manager clocks well over fourteen hours a day. Morning production meetings, afternoon logistics tracking, evening client correspondence. Three weeks in, his decisions still appear timely and sound. Yet the purchasing officer seated nearby notices a significant pricing error in the raw yarn order the manager approved in mid-August. When the manager learns of it, he is genuinely surprised: he had not felt tired. This is precisely where the most dangerous misconception about resilience surfaces — not feeling tired and maintaining decision quality are not the same thing.In business, resilience is most commonly framed as a personal psychological quality: staying upright under stress, remaining productive under pressure, bouncing back from adversity. This framing is not wrong, but it is dangerously incomplete. When a team reaches deep fatigue, the first thing lost is not productivity but the capacity to catch mistakes. The tired brain keeps working — it simply cannot see where it should stop. Substituting individual resilience for organizational system design means labelling that blindness a personal failing. The real question is different: under which conditions, for which category of decision, should the system’s protective mechanisms engage?Turkish business culture tends to frame resilience as a badge of honour. ‘I worked until two in the morning,’ ‘I came in on the weekend,’ ‘I checked my messages on holiday’ — these statements are worn as proof of commitment. This cultural norm hardened noticeably after the currency crisis of 2018, when payrolls were held steady while expectations rose. In a packaging company in Gaziantep employing 312 people, the operations manager’s average weekly overtime exceeded 22 hours across the six months spanning late 2018 and early 2019. No one named this a problem; it was read as dedication. When decision errors eventually surfaced through customer complaints, blame landed on the individual — ‘carelessness’, ‘lack of focus’, ‘poor concentration’. The context was never examined.The steelman counterargument deserves an honest airing: in genuine crisis moments, when a single decision-maker stands without a functioning backstop, individual psychological resilience does matter and can be decisive. That is real. But using the exception to normalise chronic fatigue as a permanent operating condition is a misuse of the concept. There is a meaningful difference between ‘this person held things together during an acute crisis’ and ‘this person will absorb whatever load we assign indefinitely.’ The second statement is not resilience; it is a system design failure disguised as a character assessment. The Denizli manager’s error was not a personal weakness — it was an organizational blind spot wearing his name.If ‘producing quality work while tired’ is genuinely possible, the mechanism is this: classify decisions by cognitive load and attach high-stakes decisions to protective guardrails. Three concrete steps make this operational. First, map the decisions that are costly to reverse and establish a rule that they may only be taken during specified time windows or with dual authorization — an automotive parts supplier in Bursa applied this logic to stock commitment decisions in early 2018 and reduced erroneous purchase orders measurably over the following eight months. Second, replace the question ‘how are you doing?’ with ‘which decision would you want to postpone this week?’ — this converts a fatigue signal into a manageable data point rather than a source of stigma. Third, measure decision process rather than outcome alone: how long did this decision take, who was involved, what information was missing. Tracking these variables makes visible the moment fatigue has entered the decision system. None of these steps is a psychological intervention; each is an organizational design choice.There is a limit to acknowledge plainly. In small and medium-sized Turkish businesses — where a single owner-manager holds most decisions, where IT resources are thin and process documentation is sparse — building this kind of system is far harder than in large corporate structures. In the economic conditions of early 2019, with cost pressure elevated and margins compressed by currency movements, dual-authorization mechanisms and decision metrics can feel like luxuries. That constraint is genuine. But the consequence of the absence of system design is that the full weight of resilience falls entirely on the individual, and individual capacity will eventually run out. The low-cost starting point is simple: which decisions should not be made in the most fatigued hour of this week? Answering that question consistently is building a system from nothing.When the Denizli factory manager discovered the error, his first instinct was self-blame. After a conversation with his team, he established one rule: raw material commitment decisions would not be made on Friday afternoons — the final hours of the week’s most punishing stretch. The rule looks almost trivially simple. But it transferred a small piece of the cognitive risk that had been loaded onto an individual under the label ‘resilience’ onto the organization instead. That is the distinction worth holding onto: resilience is not willing yourself through fatigue; it is designing the system so that the moment fatigue degrades judgment, something other than willpower catches the decision. Organizations that cannot make this shift will eventually exhaust even their most capable people. Look closely at your strongest team member. Look at the hour in which they make your most consequential calls. Then look at the conditions of that hour.
This article was originally published in Turkish by Gökhan MERCANOĞLU on January 17, 2019. The English edition has been reviewed and edited by the author.