Skip to content
AFTER CERTAINTY
Skip to chapter text

Why Collaboration Is So Hard

Introduction — The Meeting Everyone Remembered Differently

IntroductionAbout 5 mins

Central question: Why can sincere people leave the same room with different meetings in hand?

Five people leave a meeting that looked successful carrying five different meetings—engineers solving different problems, a designer updating a prototype, notes rewritten afterward. Blame often finds a careless person; the introduction considers another possibility: collaboration asks people to keep working where no one fully sees, controls, or owns the result.

The Meeting Everyone Remembered Differently

By the time the meeting ended, everyone believed they understood what had happened.

People gathered their laptops. Someone made a joke about finally getting to lunch. Someone else reminded the group that Friday was probably too ambitious. There were a few nods, a few “Sounds good,” and the familiar scraping of chairs as everyone drifted toward the hallway.

It looked like a successful meeting. Later that afternoon, two engineers began working on different solutions to what they believed was the same problem. A designer updated the prototype because she thought a decision had finally been made. A product manager sent an email asking when everyone would be ready to review the proposal that another person had assumed was already approved. The project manager quietly rewrote the meeting notes because they no longer resembled what people seemed to remember. No one was trying to be dishonest. No one had ignored the conversation. No one had left intending to create confusion. And yet, somehow, five people had walked out of the same room carrying five different meetings with them.1 Most of us have experienced something like this.

Sometimes it happens at work. Sometimes it happens in a family deciding where to spend Thanksgiving. Sometimes it happens while planning a neighborhood event or serving on a volunteer committee. Sometimes it happens in a marriage after what both people sincerely describe as “the conversation we already had.”

After enough experiences like this, we start looking for someone to blame. Maybe the manager wasn’t clear enough. Maybe someone wasn’t paying attention. Maybe one person dominates every conversation. Maybe nobody takes notes. Occasionally those explanations are right.

There are careless people. There are manipulative people. There are leaders who confuse speaking with listening, and organizations that mistake agreement for understanding.2

But there is another possibility that interests me more. What if some of these misunderstandings happen not because people are failing to collaborate, but because collaboration itself asks human beings to do something extraordinarily difficult? We often imagine collaboration as a moral achievement. Good people collaborate. Good teams communicate. Good leaders build consensus. The assumption quietly hiding underneath all of those ideas is that if everyone is skilled enough—or kind enough, or patient enough—the work will eventually become clear.

Experience suggests otherwise. The larger the work becomes, the less any one person can fully see. The more people contribute, the less any individual controls the final result. The more knowledge is required, the more everyone must depend on judgments they cannot personally verify. Strangely, collaboration often succeeds not by removing uncertainty but by asking people to continue working in the middle of it.3

That is a difficult thing to do. We prefer stories with authors. We like knowing who made the decision. We like knowing who deserves the credit. We like knowing who is responsible when something goes wrong.

You can see the preference at the end of almost any shared effort. Someone asks whose vision it was. A name is offered. The room relaxes. The story now has a center.

That explanation often feels complete enough to end the conversation.

Perhaps.

But it may be answering a different question from the one the work actually posed. The named person may have protected the project, started it, or made the decision that allowed it to continue. What the clean story cannot carry is the sequence of revisions, warnings, temporary fixes, and late-night judgments that never fit on a slide. Credit still matters. So does the quieter fact that the finished thing no longer belongs cleanly to anyone who can stand beside it.

Collaboration slowly dissolves those comforts. A great theatrical production belongs to hundreds of people. A successful bridge reflects thousands of decisions that no single engineer remembers making. A scientific discovery carries the fingerprints of technicians, graduate students, reviewers, administrators, mentors, and researchers whose names never appear in newspaper headlines. Even something as ordinary as a neighborhood park is the accumulated work of planners, contractors, maintenance crews, volunteers, elected officials, taxpayers, and children who eventually decide whether anyone wants to spend time there.

The finished work often appears singular. The process almost never is. Perhaps that is why collaboration feels so strange. It asks us to keep contributing to work that none of us can fully see, fully control, or fully claim as our own.

We usually treat the frustrations that follow as separate management problems—uneven workload, bureaucracy, communication failure, optimization gone too far—each with its own diagnosis and temporary fix. Useful as those labels can be, they can also turn one recurring pressure into a set of local defects to train away, process away, or staff away: the pressure of making something together while no one can fully see, control, or claim what is being made.

This book argues they are different expressions of the same human condition. Not because people are irrational. Not because organizations are broken. But because whenever many people attempt to create something together, they enter a world where understanding is always incomplete, ownership is always shared, and certainty always arrives later than we would like.

Successful collaboration is not the absence of tension. It is the ability to keep uncertainty, disagreement, and partial knowledge inside the work long enough for them to change what the group does—without requiring one person to absorb their cost for everyone else.

The remarkable thing is not that collaboration sometimes fails.

The remarkable thing is that it works as often as it does.

The rest of this book is an attempt to understand why.

Footnotes

  1. See Karl E. Weick, Sensemaking in Organizations (Thousand Oaks, CA: Sage, 1995).

  2. See James G. March and Herbert A. Simon, Organizations (New York: Wiley, 1958).

  3. See Niklas Luhmann, Trust and Power: Two Works, trans. Howard Davis, John Raffan, and Kathryn Rooney (Chichester, UK: John Wiley & Sons, 1979).