Skip to content
AFTER CERTAINTY
Skip to chapter text

Why Collaboration Is So Hard

Chapter 1 — The Show That Opens Friday

About 13 mins

Central question: What happens when shared work exceeds any one person’s sight—and credit still needs a name?

By tech week a play has become a field of consequences—beams, cues, codes, sickness—beyond any director’s private picture. Shared contribution holds the show together while credit compresses into a name, and accumulated memory of that erasure can look like resistance to collaboration. Some work cannot be done another way even when recognition fails.

The Show That Opens Friday

By Thursday evening, the play no longer belonged to the director.

It may have begun that way. Months earlier, before anyone had built a wall or sewn a costume, the director had sat alone with the script and imagined the production as a whole. She could see where the actors would stand, how the light would narrow during the final scene, how silence would gather just before the last line. In that private version, every movement arrived at the right moment. The set obeyed the story. The actors understood what she meant before she explained it. Nothing weighed too much, arrived too late, or required permission from the fire marshal.

The imagined play was complete because imagination has no building codes. Then rehearsals began.

An actor discovered that a line sounded false when spoken aloud and asked whether it could be changed. The lighting designer built a cue around the original rhythm and had to rebuild it when the pause moved. The set crew learned that the platform the director wanted could not support the number of people who were supposed to stand on it. A costume that looked perfect in sketches caught on the corner of a table during a scene change. The theater learned that a school group would need the hall earlier than expected on the morning of the final rehearsal. The stage manager adjusted the schedule, then adjusted it again when someone became sick.

By tech week, the play had become a collection of consequences.

The director still mattered. She held the broadest picture of what the production was trying to become. But she no longer possessed enough knowledge to make every decision herself. She did not know the weight of each beam, the heat produced by each lamp, the time required to move a platform in darkness, or whether an actor could change costumes in the interval the script allowed. Other people knew those things. Some knew them before the director needed to know them. Others discovered them only when the work refused to behave as planned.

The production that would open on Friday was not the production anyone had imagined alone. It was what interaction had made under constraint.

On Thursday night, a scene that had worked for weeks suddenly stopped working. A doorway on the set had been shifted several inches to make room for a support brace. The change was small enough that no one had thought of it as a creative decision. But now an actor had to take a different path across the stage, arriving half a second later than before. Another actor turned too soon, anticipating the original entrance. A line landed without its response. The lighting cue fired into an empty doorway.

The director stopped the rehearsal.

They tried the scene again. The actor moved faster and nearly slipped. The lighting designer delayed the cue, which made the next transition late. Someone suggested moving the doorway back. The technical director explained why they could not. Someone else suggested cutting the crossing altogether. That solved the timing problem but weakened the scene.

No one had made a mistake in the usual sense. The brace was necessary. The doorway had moved. The scene now had to become something slightly different because the conditions that supported the earlier version no longer existed.

This is one of the first strange things collaboration asks us to accept. A choice can be reasonable in isolation and disruptive in combination.

The set crew can solve the problem in front of them and create a problem for the actors. The actors can solve their problem and create one for the lighting designer. The lighting designer can protect the emotional shape of the scene and leave the stage crew without enough time to move the next piece. Each person can be competent. Each person can be generous. The work can still wobble.

We often respond to that wobble by searching for the person who should have prevented it. Someone should have anticipated the brace. Someone should have communicated the change. Someone should have owned the dependency between the doorway, the entrance, and the lighting cue.

From the edge of the rehearsal, the conclusion can look obvious: this is a communication failure. If the set crew had told the actors, the entrance would have held. Communication still matters. But the brace became necessary only when the load revealed itself, and the shift was small enough that it did not look like news. Treating the wobble only as a missing announcement can hide what the work has entered—a condition where no announcement could have mapped every sideways consequence before the consequence appeared.

Sometimes this search is useful. Complex work still needs responsibility. People should communicate changes. Decisions should be recorded. The fact that no one sees the whole does not mean no one is accountable for anything.

But the search can also hide what the work has become.

Once enough people contribute, the outcome begins to contain relationships that no one designed intentionally. A door becomes a timing decision. A costume becomes a safety problem. A calendar becomes an artistic constraint. The work develops consequences sideways, passing from one person’s area of competence into another’s before anyone has language for what changed.

No chart can reveal all of these relationships in advance because some of them do not yet exist. They appear through the work.

This is often described as emergence, a word that can make ordinary collaboration sound mystical. But there is nothing mysterious about it. Something emerges when several partial understandings meet a reality none of them controls. The outcome contains information that was not available to any person at the beginning because the information was produced by the interaction itself.1

A family caring for an aging parent encounters the same condition without calling it emergence. One sibling understands the medical appointments. Another notices changes in mood. Another lives close enough to see what daily life looks like but may not understand the financial implications. A parent may reveal different pieces of the truth to different children. The family keeps asking who is in charge because authority feels like relief. But the problem is not merely distributed work. It is distributed sight. Each person knows something the others need, and none can be certain how much remains outside their view.

The arrangement that finally holds belongs to everyone and no one. That phrase can sound romantic until credit or blame enters the room.

When shared work succeeds, institutions often describe it as though a single author produced it. A project had an owner. A leader had a vision. A researcher made a discovery. A director created a production. These stories are not entirely false. Someone may have initiated the work, protected it, or made the decisions that allowed it to continue. But the clean story of authorship usually appears after the messy work is finished.

During the work itself, ownership is less satisfying.

People ask questions they may not say aloud. What am I responsible for? How much influence do I have over what will eventually carry my name? If the project fails, which part of the failure will be attributed to me? If it succeeds, will anyone notice what I contributed? How much of my judgment am I expected to surrender before my participation becomes cooperation?

These are sometimes dismissed as ego. The person should care about the work, not the credit. If they were truly collaborative, the questions would not arise. But in collaborative work, effort and result no longer share a line you can follow home.

In individual work, you write the page. You repair the machine. You prepare the meal. Reality may interfere, but judgment and consequence usually remain near enough to keep a person oriented. Collaboration breaks that nearness. An excellent contribution can vanish inside a larger failure. Praise can arrive for labor you barely saw. A revision can improve the work and make it feel less like yours. Asking whether you will still be able to recognize yourself in the outcome is not only vanity. It can be the sound of someone trying not to disappear inside a field where judgment no longer guarantees consequence.

That confusion is not incidental to collaboration. It is part of what collaboration is. To contribute seriously is to place something you value into a field where other people will change it.

They may use your idea in a way you did not intend. They may combine it with an idea you distrust. They may remove the part you considered essential and preserve the part you thought was provisional. The final result may be better than what you imagined and still feel strangely alien.

This is why collaboration requires more than generosity. It requires a partial surrender of authorship.

Not the disappearance of judgment. Not passive acceptance of whatever the group decides. Not a vague belief that every contribution is equally wise. Surrender does not mean becoming indifferent to the outcome. It means accepting that caring deeply about the work does not give you the right to control every form the work may take.

That is harder than most celebrations of teamwork admit.

We like to imagine collaborative people as naturally open, flexible, and untroubled by revision. When someone resists another change, the available story is selfishness: they cannot let go; they are protecting their vision; they are not team players.

A director who refuses one more revision on Thursday night may look like the obstacle in the room. She may be blocking contribution, or clinging to an earlier version of the play. She may also be trying to keep a shape the audience will still recognize after three days of necessary concessions. A writer who protects a sentence after several rounds of notes may be vain. They may also be trying to remain oriented inside feedback that has become a crowd. People tighten control because control helps them know where they stand when no one can hold the whole. They over-specify tasks because ambiguity makes responsibility feel like exposure. They demand agreement early because agreement restores the feeling that someone still knows where the work is going.

The desire to control the whole is often strongest when no one can.

A leader sees the project becoming less coherent and inserts more approvals. A manager asks for increasingly detailed plans because the work no longer resembles the promise made months earlier. Each action may be an attempt to preserve quality. Each may also prevent the contributions that would allow the work to become something better than the original plan.

The problem is not that authorship has no value.

Authorship can create coherence. A strong point of view can keep a group from producing a lifeless compromise. Decision rights matter. Responsibility matters. Some choices cannot be made collectively, and some people are accountable for choices others merely influence.

But centralized authorship and shared contribution are not opposites that can be cleanly selected at the beginning of a project. They are pressures that must be held together. The work needs enough coherence to become recognizable and enough permeability to be changed by knowledge the original author did not possess.

Too much openness, and the work may lose its shape. Too much control, and the work can no longer learn.

This tension appears clearly in artistic work because we expect art to have a voice. Yet even there, the voice is often supported by people whose contributions disappear into the finished experience.

The audience on Friday will see an actor enter through a doorway at precisely the right moment. They will not see the support brace that forced the doorway to move. They will not know that the lighting cue was delayed by half a second, that the actor changed the direction of the crossing, or that the stage manager shortened an earlier transition to recover the lost time.

If the moment works, it will look inevitable.

Successful collaboration often produces this illusion. The final result hides the negotiations that made it possible.2

The smoother the outcome, the easier it is to imagine that someone owned the whole. This illusion shapes how we distribute recognition.

We reward the person who can stand beside the finished result and tell a coherent story about it. The director bows. The executive presents the launch. The principal investigator’s name appears first. Meanwhile, many of the contributions that made the outcome possible are difficult to separate from the work itself.

A regional archive digitizing oral histories may publicly appear as a searchable collection of recordings. But the collection exists because interviewers built trust with narrators, archivists preserved fragile materials, metadata specialists made decades of speech searchable, translators carried meaning across languages, community liaisons negotiated consent, technicians repaired damaged audio, and grant writers translated the work into forms funders could recognize.

Which one created the archive? The question has no satisfying answer.

Yet institutions still need an answer because credit must be distributed, budgets justified, performance reviewed, and stories told. So the archive is compressed into a project, the project into a leader, and the leader into a sentence. What required a field of contribution becomes an achievement with a name beside it.

This compression is sometimes necessary. It is also one reason collaboration can feel like erasure.

People do not need equal praise for every action. They do need some believable relationship between contribution and recognition. When that relationship repeatedly fails, withdrawal can look like a personality problem even when it is a rational response to the structure of the work.

The person who has watched three leaders receive credit for work held together by their invisible attention may become less enthusiastic about the fourth collaborative initiative. The specialist whose warnings are absorbed into the final design but whose presence is omitted from the story may become more territorial about the next decision. The person who always adapts may eventually insist that everyone else adapt instead.

What looks like resistance to collaboration may be accumulated memory of what collaboration has cost. And still, some work cannot be done another way.

No individual can contain all the knowledge required to manage a watershed, design a safe aircraft, care for a complicated patient, raise a child, maintain a city, stage a play, or understand what a community needs from a public space. The fantasy of singular authorship becomes less plausible as the work approaches the complexity of life.

This does not mean that more participation always produces better outcomes. Groups can reproduce ignorance as easily as they can correct it. Committees can dilute responsibility. Shared ownership can become an excuse for nobody making the difficult decision. People can hide behind process, manipulate consensus, or contribute so little that cooperation becomes extraction from those who continue to care.

Collaboration is not automatically wise because it is shared. Its value comes from a narrower possibility: different people can introduce realities into the work that would otherwise remain unseen. The set crew knows what the structure can hold. The actor knows what the line feels like in the body. The stage manager knows what time permits. The lighting designer knows what the audience will be able to see. The director knows the larger shape each decision is supposed to serve.

None of these perspectives is the whole. Remove any one of them, and something important may disappear. Combine them, and the result is not perfect understanding. It is a production coherent enough to continue.

That may be one of the simplest ways to describe collaboration: No one holds the whole, but the whole still has to be made. On Thursday evening, after several attempts, the theater company found a new version of the scene.

The doorway remained where the support brace required it to be. The actor changed the crossing, not by rushing but by beginning the movement one line earlier. The other actor adjusted the pause. The lighting designer moved the cue. The stage manager noted the change and warned the crew that the next transition would now begin from a different position.

No one got exactly what they had first imagined. The scene worked.

On Friday night, the audience watched an actor appear in a doorway as though the moment had always been designed that way. The light found the actor. The response arrived. The story continued.

No one in the seats saw the argument, the brace, the failed entrances, or the sequence of small concessions that produced the moment. They saw only the play.

Perhaps that is why collaboration is so often misunderstood from the outside.

Its failures are visible as confusion, delay, conflict, and compromise. Its successes disappear into the thing that finally works.

The show opens.

And because the outcome looks whole, we forget how many people had to surrender the right to make it alone.

Footnotes

  1. See Weick, Sensemaking in Organizations.

  2. See Richard Sennett, Together: The Rituals, Pleasures and Politics of Cooperation (New Haven, CT: Yale University Press, 2012).