The Problem of Organizations Where Unused Systems Persist

Why Do They Remain, Even When We Know They’re “Unused”?

Many organizations harbor systems—tools, policies, rules, workflows—that no one actively uses yet remain in form. Attempts to abolish them often create tension. Despite varying forms, they share a common trait: they are recognized as “unused” yet persist. This article examines why unused systems linger, what this signifies for an organization, and breaks it down into the Management Decision Layer (Why) and the Specialist Implementation Layer (How) to consider the importance of reversible decision-making in SME management.

Management Decision Layer (Why)

The Problem Isn’t That They’re “Unused”

The crucial first point is that the fact they are unused is not the core problem. The fundamental issue is that no one verifies *why* they fell into disuse or *why* they remain despite that. In other words, the problem is not the system itself, but the state of leaving decisions unaddressed.

Systems Become “Traces of Past Decisions”

Most unused systems were once rational, created to solve a specific problem. Over time, however, premises change, work content evolves, and personnel shifts, causing them to lose their purpose. They persist because abolishing a system can feel like negating the past decision that created it. This is a classic example where the reversibility of management decisions—the ability to revert—is not consciously considered.

Inability to Abolish Stems from Ambiguous “Responsibility”

Many systems remain without clear ownership of who decided or who is responsible. Consequently, no one proposes their abolition, and an atmosphere develops where no one wants to take responsibility if problems arise after removal. This is not a system problem but an organizational design issue: the absence of decision accountability.

Specialist Implementation Layer (How)

The Structure That Preserves Unused Systems

At the Specialist Implementation Layer, we examine the structure of why unused systems persist within concrete operational processes.

① “Just in Case” Becomes Official Rule

What begins as “let’s keep it just in case” or “we might use it for some cases” gets documented, formalized, and becomes an official system. At this point, a reversal occurs: an unused system transforms into a system that “must be used.”

② Exception Handling Gets Promoted to Policy

When a one-time exception is institutionalized under the guise of “preventing recurrence” or “preventing personal dependency,” a system for rarely occurring cases persists. The result is inefficiency, where routine work is bound by exception-based standards.

③ The Fact of Non-Use Doesn’t Affect Evaluation

In many organizations, creating or implementing a system is recognized, but its falling into disuse or being abolished is not. Consequently, the structure where “systems increase but never decrease” becomes entrenched.

Questions for Reviewing Persistent Systems

When reviewing business processes or policies, start with these questions:

• For what decision does this system exist?
• Is that decision still important today?
• If this system were gone, who specifically would be inconvenienced, and how?

The key here is not a vague unease that “someone might be inconvenienced,” but the ability to articulate *who* would be inconvenienced and *how*. This is the first step toward clarifying delegation of authority and responsibility.

Common Misconceptions

Misconception ①: Unused Systems Are a Result of Negligence

In most cases, this is not negligence. It is the result of time passing without reclaiming a decision, indicating an incomplete management decision-making process.

Misconception ②: Systems Must Be Preserved Once Created

What should be preserved is not the system itself, but the rationality of the decision. When circumstances change, even once-rational decisions should be reviewed. This is the hallmark of healthy organizational management.

Conclusion (Without a Single Answer)

Unused systems are traces of past decisions. The problem lies not in the systems themselves, but in the failure to reclaim those decisions, and the inability to abolish them stems from ambiguous responsibility. Reviewing systems requires more sophisticated management judgment than creating them. An organization where unused systems persist is not an organization incapable of change, but one incapable of concluding its decisions. This realization is the first step toward flexible management decisions with reversibility in mind and sustainable organizational design.