The Moment “It Can’t Be Helped” Becomes the Norm

Introduction

The phrase “It can’t be helped,” frequently heard in fast-growing environments, is often the correct judgment to move the business forward in the moment. However, when this temporary decision lacks a defined deadline and conditions, it transforms into a permanent premise, becoming a structural factor that breeds technical debt, organizational fatigue, and decision-making stagnation. This article systematically examines the mechanism by which “It can’t be helped” becomes the norm and the management challenges it triggers.

“It Can’t Be Helped” is a Correct Judgment

In situations of high urgency, significant customer impact, or unmissable growth opportunities, the judgment to prioritize speed over perfect design—”It can’t be helped”—is a rational management decision. The core issue lies not in the judgment itself, but in the failure to attach a “by when” and “under what conditions” to it.

The Moment Exception Handling Becomes the Premise

When “It can’t be helped” is repeated, exceptions, manual workarounds, and provisional rules accumulate. By nature, exceptions are temporary. But as they multiply and intertwine, there comes a moment when it’s no longer clear what constitutes the rule. At this point, exceptions become the organization’s implicit premise.

When Provisional Measures Become Official Operations

In many IT environments, it’s not uncommon for temporary fixes or provisional integrations to remain in place as official operations for years. This is often underpinned by a situation where “we can’t stop what’s working,” “the impact is unclear,” and “no one has a complete overview.” This creates a structure where the “decision not to fix it” is seen as the safest choice.

Technical Debt is a Debt of Judgment

The true nature of technical debt is not merely old code or messy implementations. It is the “record of deferred decisions” and the “accumulation of things left undecided.” The repeated use of “It can’t be helped” results in the decisions themselves becoming liabilities. This is the true strategic risk in IT.

Why the “Revert” Decision Becomes Impossible

To resolve “It can’t be helped” and repay technical debt, irreversible management decisions are required: “Where do we stop?”, “What do we discard?”, “What do we rebuild?”. However, these decisions are too heavy for frontline teams, the IT department lacks the authority, and management avoids getting involved in specific judgments. Consequently, no one takes ownership of the “revert” decision.

When “It Can’t Be Helped” Becomes Culture

When this state persists, operations premised on overwork, dependence on specific individuals, and an atmosphere that discourages raising issues become entrenched as organizational culture. The moment the recognition that “we know the problems, but we can’t address them now” is shared across the organization, improvement activities effectively cease.

What Was Missing as a Management Decision?

What was missing was a “time-bound management decision” that clearly defined the conditions for tolerating “It can’t be helped.” It was essential to explicitly state, “How long is this provisional?” and “At what point do we revert to the intended state?” “It can’t be helped” only becomes a sound IT investment decision when paired with a deadline, a recovery plan, and a responsible party.

The Only Acceptable Form of “It Can’t Be Helped”

“It can’t be helped” is only acceptable when all three of the following conditions are met:

• A clear deadline (“by when”) is established.
• The trade-offs (“what is being sacrificed”) are articulated.
• It is decided who will make the decision to revert.

Without these, the phrase is merely an incantation that postpones future failure.

The Next Question to Ask

The crucial step is not to ask “Why does the overwork continue?” but to concretely ask and act upon: “Which ‘It can’t be helped’ will be addressed, by whom, and when?” In the next article, we will examine the mechanism by which organizations where ad-hoc responses have become the norm fail to replicate successes and cease to learn.