Situation

The reliable person becomes the route

Work, exceptions, and rescue requests route toward one reliable person until that person becomes informal infrastructure—and absorbing the gap is praised as character.

Focus in observatory

Recognition signals

everyone routes exceptions to the same name
helping slowly becomes absorbing
praise for reliability hides missing system capacity

Questions to ask

What work is the system learning not to carry?
Where has reliability become architecture?

Counterbalances

name routing as a design choice, not only a personality trait
transfer capacity instead of celebrating endless absorption

Active patterns

Pattern

Responsibility Persists Beyond Control

Outcomes often exceed personal influence, yet participation, attention, and response still matter where contact exists. Innocence becomes an escape from participation when systems feel too large to steer. - Scale makes withdrawal feel rational - Formal authority ends while influence continues - Care is mistaken for omnipotence - Answerability is confused with blame Care survives after control disappears; responsibility is not the same as mastery. An executive who has left a role still shapes what others do through permissions and precedents they normalized.

Pattern

Leaders Feel the Consequences

A decision creates cost, risk, or gain for people in a group. Where people decide and where costs land can separate. - Incentives favor visible wins over visible cost - In large settings, effects land unevenly - Distance makes harm easier to miss - Pushing pain downhill is easier Those who decide stay tied to what their choices do to others. If we called it, we sit with the fallout. Leaders feel the consequences on this; we're not sliding the pain down a layer.

Related concepts

Concept

Invisible labor

Work without which collaboration fails but which does not appear in artifacts the organization already counts: tickets, slides, revenue lines. Includes maintenance, trust repair, context-holding, and translation under churn. Related scholarship often calls part of this **emotional labor** when feeling rules are managed for the group's comfort.

Concept

Boundary

Boundary names where one kind of obligation ends and another begins—between roles, institutions, scales, or interpretive frames. It becomes important when coordination must clarify who can decide, who must answer, and what counts as shared ground. It helps preserve legible responsibility and evaluative contact, but can fail when boundaries harden into walls that block correction. In the post-interpretive authority context, a boundary is where external understanding ceases to govern legitimacy while power continues. It differs from coupling because a boundary marks a shift in shape, not the strength of attachment between action and consequence.

Concept

Authorization

Authorization names permission that persists beyond the moment of granting—it becomes normalized, repeatable, and transferable across contexts. Unlike one-off adaptation to crisis, authorization creates standing exceptions that outlive the urgency that made them necessary. Unlike authority, which is about who can coordinate, authorization is about what actions remain permitted after the original justification has faded. People continue acting through permissions left ambiguous, normalized exceptions outlive the pressures that produced them, and insight becomes permission to delay required response. When authorization operates well, it preserves necessary flexibility; when it fails, crisis permissions become standard operating procedure and harm is attributed to the system rather than choosers.

Concept

Coordination

Coordination names the problem of acting together when lives are fragmented—when people must move collectively across distance, time, strangers, and difference without complete information or full agreement. It becomes important when individual judgment alone cannot sustain the group, when behavior must hold across contexts that no one person can see completely. Coordination helps preserve collective capacity by making expectations predictable, by enabling strangers to act together under shared rules, by allowing large-scale projects that no single person could accomplish. Roles, rituals, law, canon, procedure, and bureaucracy are all coordination technologies—tools for making tomorrow recognizable from yesterday so action can continue. But coordination can become brittle when it suppresses the feedback and variation it needs to stay responsive, when inherited patterns keep moving after fit has thinned, when dissent is treated as disruption rather than signal. Coordination purchased at the cost of revision can continue functioning long after it has stopped serving the purposes that gave it authority. The question coordination raises is: what coordination problem is this tool solving? What breaks if behavior stops being predictable? Coordination differs from alignment in that coordination is about collective movement, while alignment is about shared direction or values.

Related books

Book

Boundary Conditions

A Literary Organizational Fiction Novel

Organizational fiction about invisible coordination work, authorization boundaries, and the cost of becoming indispensable inside complex systems.

Book

Why Collaboration Is So Hard

And Why the Effort Still Matters

Why joint work fails when incentives, trust, and shared understanding do not line up—and why the effort to collaborate still matters.

Book

Coupling

Cohesion, Consequence, and the Architecture of Responsibility

A practical framework for seeing where systems are tightly joined, where they drift apart, and how those coupling choices shape accountability over time.