Order Independence
— Taking Responsibility Without Waiting for Permission

This essay is a reflection on organizational design and decision-making structures. It does not recommend order independence for all organizations.

1. The Multi-Layering of Intentions — When Stakeholders Multiply

Alone, there is no sequence

When you create something alone, the concept of sequence barely registers. You execute ideas in the order they occur to you. No one's approval is needed. If you fail, you alone make corrections. There is no distance between action and judgment.

With two, sequence emerges

The moment another person joins, the question "who goes first?" arises. When opinions align, sequence is not an issue. But when they diverge, deciding whose intention takes priority becomes the essence of the decision itself. Here, the smallest unit of order dependence is born.

The mechanism of multi-layering

As stakeholders grow to three, five, ten, the layers of intention multiply geometrically. Each brings different interests, different time horizons, different priorities. Satisfying A's intention requires B's approval, but B's approval requires C's prior confirmation — such chains become the "order" that governs an organization's movement.

The problem is that this multi-layering progresses without self-awareness. Meetings multiply. Confirmation emails multiply. "Just in case" consensus-building multiplies. Each individual act appears rational, but collectively, decision-making speed declines exponentially. The number of stakeholders grows by addition, but the cost of consensus grows by multiplication.

"A camel is a horse designed by committee."

— Alec Issigonis

2. The Effects and Costs of Waiting

The benefits of waiting — maturation and alignment

Waiting has its positive aspects. Deferring judgment allows information to accumulate, emotions to settle, and better options to emerge. Just as "strategic patience" proves effective in diplomacy, there are indeed cases in organizations where deliberate consensus-building yields better outcomes than hasty decision-making.

Japan's "nemawashi" culture is an institutionalization of this effect. By pre-aligning stakeholder intentions, formal meetings proceed without objections. This appears inefficient on the surface, but it may reduce total cost by minimizing resistance during the execution phase.

The costs of waiting — stagnation and lost opportunity

Yet waiting carries costs. The most obvious is opportunity loss. Markets do not wait. Technology does not wait. Competitors do not wait. While you wait "until everyone agrees," those who act capture first-mover advantage.

The more serious cost emerges when waiting becomes habitual and the organization's capacity atrophies. When "waiting for a decision" becomes routine, the ability to make decisions itself deteriorates. Waiting appears safe, but that safety is purchased at the expense of diminished capability.

The asymmetry of waiting costs

What is striking is that the cost of waiting is largely invisible to those who impose the wait. For the approver, "taking a little more time to consider" is an expression of prudence. For the one waiting, it is a waste of time and motivation. Unless this asymmetry is addressed, organizations will structurally continue to underestimate the cost of waiting.

3. The Boundary Between Obedience and Autonomy

The rationality of waiting for instructions

"Waiting for instructions" is often spoken of critically, but in many organizations it is a rational behavior. Acting independently in areas where you have no authority invites reprimand. Making judgments when you are not in a position of responsibility is deemed an overreach. Waiting for instructions is adaptive behavior that maintains organizational order — not individual laziness.

The danger and necessity of autonomy

On the other hand, autonomy — initiating action based on one's own judgment — always carries risk. Misjudgment invites accountability. Encroaching on others' domains creates friction. Yet in organizations where environmental change is rapid and the approval chain is long, situations inevitably arise where waiting for instructions means missing the window for response.

This contradiction is structural. Organizations seek order, but order sacrifices speed. Pursuing speed disrupts order. The choice between obedience and autonomy is not a matter of individual temperament but of organizational design.

What determines the boundary

The boundary between obedience and autonomy is rarely codified. In most organizations, there is a tacit understanding of "what you can decide on your own" and "what requires approval from above." But tacit understandings are interpreted differently by different people and shift with circumstances. This very ambiguity is the root cause of order dependence in organizations.

"It's easier to ask forgiveness than it is to get permission."

— Grace Hopper

4. The Prerequisites of Permission

When permission is necessary

Not all actions should be permission-free. Irreversible actions, actions with significant impact on others, actions that could damage organizational credibility — these structurally require the procedure of permission. Expenditure of funds, execution of contracts, issuance of official statements. Permission systems are justified in proportion to irreversibility and the magnitude of risk.

When permission is unnecessary

Conversely, demanding permission for reversible actions with limited scope that presuppose trial and error generates cost alone. Code modifications, document drafts, idea prototyping — organizations that require approval for each of these have confused the purpose and the means of permission systems. The purpose of permission is risk management, not action management.

The structural problem of permission

The greatest problem with permission systems is their tendency to expand once introduced. Approval initially required only for critical decisions gradually extends to all decisions. This is a natural consequence of bureaucracy — a variant of Parkinson's Law. The procedure of seeking permission itself becomes work, and granting permission becomes a source of power.

Clarifying the prerequisites of permission is a precondition for order independence. Without structurally defining what requires permission and what does not, everything defaults to a state of waiting for approval.

5. Hierarchy Within Openness

Information asymmetry creates hierarchy

In traditional organizations, hierarchy is bound to information asymmetry. Superiors possess more information and make judgments based on it. Subordinates lack information and therefore cannot make judgments, so they wait for instructions from above. Information gaps create power gaps, and power gaps fix sequence.

Openness transforms hierarchy

In organizations where all information is public, this structure changes fundamentally. When everyone has access to the same information, the premise that "those above know what those below do not" dissolves. The basis of hierarchy shifts from information volume to judgment ability. Hierarchy based on judgment is more fluid than hierarchy based on position — it is context-dependent. In certain domains, a newcomer may make more accurate judgments than a veteran.

TokiStorage's practice

TokiStorage publishes its source code, business information, and identified concerns — everything. This openness structurally eliminates information-based hierarchy. When everyone has the same information, the need to "check before acting" diminishes. See the information yourself, judge for yourself, act for yourself — openness is the foundation of order independence.

6. Transcending the Desire for Limitation

The instinct to limit

Humans have an instinct to limit scope. "My responsibility," "my authority," "my domain" — by drawing boundaries, we clarify the range of responsibility and reduce uncertainty. This is rational as a means of securing psychological safety, but from an organizational perspective, it creates order dependence.

When a problem in A's domain spills over into B's domain, the sequence "first A addresses it, then hands it off to B" arises. The more domain boundaries exist, the more such handoffs occur, and the longer the chain of sequence grows.

Limitation creates sequence

Limiting authority generates the need for permission. The moment you feel "this is beyond my authority," the next action requires someone else's permission. The boundary of authority becomes the exact point where sequence originates. The finer the limitation, the more sequence there is.

Designing for transcendence

Transcending the desire for limitation does not mean erasing boundaries. It means creating a structure where crossing boundaries is tolerated. Not "you won't be scolded for crossing boundaries," but "the design presupposes boundary-crossing." The open-source pull request is one example of this design. Anyone can propose changes to any part of the code. There are no domain limitations — only post-hoc quality assurance through review.

7. Liberation and Suppression

What liberation from sequence produces

In organizations liberated from order dependence, action starts faster. "Move first, adjust later" becomes possible. Prototypes are built quickly, feedback is obtained early, and course corrections happen at low cost. Agile methodologies in software development are an institutionalization of this liberation.

The chaos that liberation brings

Yet the absence of sequence can produce chaos. If everyone moves simultaneously in different directions, integration becomes difficult. Duplicate work occurs, contradictions arise, and overall coherence is lost. Disorder and autonomy are different concepts, but they are hard to distinguish from the outside.

The reinvention of suppression

What is particularly interesting is that organizations that abolish formal sequence often reinvent new forms of suppression. When official hierarchies disappear, unofficial power structures emerge. Without codified procedures, those with louder voices or greater political skill dominate the implicit order. This phenomenon, which Jo Freeman called "the tyranny of structurelessness," demonstrates that abolishing sequence does not automatically produce liberation.

"The idea of 'structurelessness' does not prevent the formation of informal structures, only formal ones. Thus structurelessness becomes a way of masking power."

— Jo Freeman, "The Tyranny of Structurelessness" (1972)

8. Taking Responsibility and Attributing Order to the Self

The core of order independence

The issues discussed so far — multi-layering, waiting costs, the contradiction between obedience and autonomy, the inflation of permission, the rigidity of hierarchy, the desire for limitation, the duality of liberation and suppression — the structural response to all of these is order independence.

Order independence is not about ignoring sequence. It is about shifting the authority to determine sequence from external sources (superiors, systems, customs) to the self. Not "I act because someone has granted permission," but "I act because I take responsibility." When the starting point of action shifts from permission to responsibility, dependence on sequence is structurally dissolved.

The inversion of responsibility and permission

In conventional organizations, people operate on the sequence "permission exists, therefore responsibility follows." They act within the permitted scope and bear responsibility for the results. Order independence inverts this — "I take responsibility, therefore I act." Responsibility comes first, and action follows. Permission is either ratified after the fact or deemed unnecessary altogether.

For this inversion to hold, two conditions are necessary. First, the results of action must be visible. Second, there must be a culture that tolerates failure. If results are invisible, the locus of responsibility becomes ambiguous. If failure is punished, no one moves first.

Self-attribution as design

At TokiStorage, order is attributed to the self. Code changes are made at each person's discretion. Essay writing does not wait for turns. Openness eliminates information asymmetry, GitHub history makes the results of action visible, and records engraved on quartz become irreversible declarations of responsibility.

Attributing order to the self does not mean "doing whatever you want." It means having the resolve to bear the consequences of one's actions and structurally declaring that resolve. Permission is not sought not because one wishes to escape responsibility, but because one wishes to assume responsibility more directly.

Conclusion — Autonomy as Architecture

As stakeholders multiply, intentions become multi-layered, waiting costs mount, and chains of permission grow longer. For many organizations, these are given conditions, and there is no inherent good or evil in them.

But "given conditions" are not "the only conditions." A design that attributes the authority to determine sequence to the self, that takes responsibility first, and that publishes the results of action — such a design is possible, and at least one organization is experimenting with it.

Engraving a QR code on quartz requires no one's permission. What it requires is responsibility for what has been engraved. "Taking responsibility without waiting for permission" — this structure is the physical implementation of order independence.

Order independence is not a creed but an architecture. It was adopted not because it is right, but because this structure was judged to enable the most honest action. Whether that judgment was correct will be demonstrated by results. Published results.