Collaboration and coordination
What happens when the reliable person becomes part of the system’s architecture?
Fiction can dramatize how helping becomes absorbing. The question is about responsibility routing—not a management tip list.
What this question is not asking
- Not empirical proof from a single novel.
- Not a boundary checklist or productivity hack.
- Not a claim that reliability is a vice.
The path
5 stops · ~106 min · primary book: Boundary Conditions
Stop 1 of 5Situation
The reliable person becomes the route
Recognize routing toward the reliable person as a structural pattern.
Why this follows: The question starts in a recognizable organizational scene.
Stop 2 of 5Book
Boundary Conditions
Fiction doorway: what begins as helping can become absorbing.
Why this follows: The novel dramatizes the cost of indispensability without proving a theory.
Stop 3 of 5Book
Why Collaboration Is So Hard
Nonfiction on invisible coordination labor and diffuse ownership.
Why this follows: After the story, diagnose the structural conditions of shared work.
Stop 4 of 5Book
Coupling
How systems join and who bears consequences when routing hardens.
Why this follows: Coupling shows architecture beneath the reliable person.
~25 min
Open Coupling (Book) →Stop 5 of 5Book
When Others Look to You
Leadership when others look to you—and when looking becomes over-routing.
Why this follows: Being looked to is both influence and risk of absorption.
What may feel different—and what remains open
Reliability can become architecture. The work is to notice when praise for absorption hides missing capacity.
Carry forward: What work is your system learning not to carry because someone reliable always will?