Chapter 1: The Upper Limit of One Person
The hundred small decisions
During one busy season I tried to count the non-creative decisions I made in a day. Not the interesting decisions. Not whether a product should exist, how an argument should be framed, or what kind of future was worth building. I counted the little ones.
Should I answer this now? Does this message require a decision or just acknowledgment? Did we mean Friday morning or Friday end of day? Is this silence disagreement, overload, or mere silence? Should this go in chat, email, a document, or a meeting? Has this person seen the previous version? Is 'almost done' a fact, a hope, or a social lubricant?
The number landed somewhere between seventy and one hundred twenty. The exact count does not matter. What matters is the texture. Each decision was tiny, like a grain of sand in a shoe. By late afternoon the shoe was full.
Most of the exhaustion did not come from deep work. It came from renegotiating defaults that should have already been settled.
Communication or structural absence
People call this communication. That word is too flattering. Communication is the deliberate transfer of information. Much of what passes for communication in teams and relationships is not transfer. It is compensation. It is the human mind filling holes where shared structure should be.
When there is no default, every action requires interpretation. When there is no protocol, every exception becomes a small trial. When there is no shared memory, every disagreement begins by reconstructing the past. Someone has to do that reconstruction. In loose systems, that person is usually the most responsible person in the room, which is another way of saying the person easiest to exploit without noticing.
This is why capable people are so often tired. Their competence becomes a patch for the missing system. The better they patch, the longer the system avoids becoming honest about its defects.
The remote-team experiment
I once worked with a remote team of five people in different cities. We had no written collaboration norms. Everything depended on tone, memory, and what we liked to call mutual understanding. Mutual understanding meant that every time confusion appeared, everyone paused, and then someone had to say, 'Next time, let us do it this way.'
That sentence appeared six to eight times a week.
One weekend I wrote a short document titled 'How We Work by Default.' It had seven rules. Messages sent before eleven in the morning get answered the same day; after eleven, by eleven the next morning. Put 'needs feedback' or 'for awareness' in the first line. Anything longer than three sentences belongs in a document, not a chat box. Deadlines live in the shared calendar. If you disagree, restate the other person's point first. If delivery slips, say so twenty-four hours early. If a rule does not apply, name the exception.
Three people replied with reaction images. One said nothing. One said, 'Good.' Then I watched.
Within two weeks the number of moments requiring me to explain the situation dropped sharply. Not because I became more patient. The seven rules began doing explanation on my behalf. On the fourth day someone missed a delivery and had not warned the group. I did not intervene. Another teammate wrote, 'According to rule six, you should have told us yesterday.' The person replied, 'Right. My mistake.' That was it.
No judge. No mother. No emotional invoice. A written default had absorbed a little piece of social heat.
The infrastructure personality
In any environment without shared structure, one or two people become what I call infrastructure personalities. They are not necessarily managers. They may not be authorized. They may not even be thanked. They simply do the work that prevents the system from becoming visibly stupid.
They take notes when no one takes notes. They organize files when versions multiply. They answer the partner nobody else answers. They translate vague disagreement into an agenda item. They onboard the new person because the organization has confused kindness with process. Each action looks small. The total is not small.
If they complain, they sound petty. 'It is just meeting notes.' 'It is just a reminder.' 'It is just a folder.' But a life can be drained by a thousand justs.
The tragedy is that the infrastructure personality often receives praise instead of relief. You are so reliable. You are so organized. You always know what is going on. Praise becomes the polite form of extraction.
A person's limit is not personal
A person's upper limit is not determined only by intelligence, discipline, or moral strength. It is determined by how much repeated coordination they cannot delegate to structure.
One person can carry ten people through charisma, memory, and improvisation. Thirty people, maybe for a season, if the person is unusually strong and unusually willing to suffer. Fifty people? No. The failure will be called leadership, culture, communication, or burnout. Underneath, it is simpler: too much of the shared system still requires one body.
Shared structure is not there to assist the hero. It is there to replace the hero in all the places where heroism was never the right tool.
The hidden budget of attention
Every person has a budget of attention that is much smaller than their ambitions. We pretend otherwise because ambition is socially rewarded and limits are not. The calendar fills. Messages multiply. Commitments accumulate in the soft language of 'just,' as if a task becomes light because the sentence describing it is short.
Just follow up with her. Just check the version. Just remind the team. Just clarify the deadline. Just make sure the new person understands. Just hold the context until everyone else catches up.
A day can be ruined by just.
The attention budget is not only about time. It is about switching, remembering, interpreting, and carrying unresolved social signals. A person doing infrastructure work is often not visibly busy in the heroic sense. They are busy in the background-process sense. Their mind is running small checks all day: did he understand, did she reply, is that promise real, will this become a problem, who is silently confused?
The tragedy is that this background labor produces stability, and stability makes the labor disappear.
When competence creates dependency
Competence is supposed to create freedom. In badly designed systems it creates dependency. The competent person becomes the one who can be trusted with ambiguity. The ambiguous work therefore flows toward them. At first this feels like status. Later it feels like weather.
This is common in startups, families, classrooms, small nonprofits, and fragile partnerships. The person who can tolerate uncertainty becomes the informal operating system. They remember the history, interpret the silence, repair the handoff, and soften the conflict before it becomes visible enough to count.
People call them reliable. But reliability without shared structure is often a polite name for being absorbent.
The exit is not to become less competent. It is to stop allowing competence to substitute for architecture. The repeated part must be moved out of the person and into a structure that others can see.
A local theater group
A local theater group I once observed had no shortage of talent. Actors came prepared. The director was generous. The set designer could build miracles out of plywood and old paint. Yet every production entered the same fog during the final week.
Props went missing. Costume changes lived in one person's memory. Nobody knew which version of the schedule was current. Volunteers asked the same questions because the answers were scattered across text messages, hallway conversations, and the director's head.
The group did not need more passion. It needed a shared production board. Call times, prop owners, costume notes, unresolved risks, and decision changes in one visible place. When they finally built it, the emotional tone changed. People were still tired, but less suspicious. A missing prop became a card on a board, not evidence that someone did not care.
Shared structure does not remove human mess. It gives the mess a surface.
The boundary of personal excellence
Personal excellence is real. Some people truly do carry more context, make better judgments, and move faster through ambiguity. A serious book should not pretend that structure equalizes all ability. It does not.
But structure changes what ability is used for. In a weak system, the best person spends their attention on preventing avoidable confusion. In a stronger system, the best person spends attention on exceptions, invention, judgment, teaching, and repair.
The point is not to make excellent people unnecessary. It is to stop wasting excellence on work a protocol could have done.
Let me be less polite
Let me be less polite for a moment. If you manage a team and your meeting notes, file hygiene, newcomer questions, emotional translation, and deadline memory all depend on the most conscientious person in the room quietly doing the work, you are not empowering that person. You are exploiting their conscience.
You may not mean to. Most exploitation in polite systems is not theatrical. It does not arrive with a villain's laugh. It arrives as a compliment: you are so organized, you are so reliable, you always know what is going on.
That sentence can be praise. It can also be a receipt for labor the system has not paid for.
I am angry about this because I have been both people. I have been the manager who enjoyed the smoothness produced by someone else's invisible work. I have also been the person producing that smoothness and then wondering why I felt used by people who genuinely liked me.
A team that depends on one person's private responsibility is not mature. It is lucky. Luck is not a management philosophy.