The Fourth Load
There is one part of any job that never appears in an official letter. On paper, a person is hired for a single skill. Perhaps teaching, counting, drafting reports, or analyzing. That skill is what carries them through the selection. Yet once they truly sit down at the desk, something not written in any document slowly becomes visible. Most of a worker's energy, it turns out, is not spent finishing the task. It is spent tending the cooperation of the people all around them.
Every worker usually comes prepared for the official load. There is a pile of tasks that fall under their responsibility. There is a performance target that must meet what the leaders expect. There is also the constant call to keep learning so that skills do not fall behind. Those three are heavy, but at least their shape is clear and there are ways to face them. What is rarely spoken about is the fourth load, the one that quietly wears down the heart the most: communication. With the boss, with teammates, with colleagues from the next team, and with anyone whose data is suddenly needed at the busiest possible moment.
Looked at honestly, a great deal of work stalls not because the task is hard, but because something is not flowing in the way people communicate. A report is late not because the data is missing, but because two people are both waiting, each feeling the ball is in the other's hands. A job halts not because it is complicated, but because one important message came to rest with someone who read it, nodded inwardly, and then forgot to pass it on. What looks like a work problem is, more often than not, a problem of how people talk to one another.
None of this is new. Peter Drucker once observed that more than half of the problems in management actually stem from poor communication. Bruce Tuckman, far back in 1965, explained that every newly formed team must pass through a phase he called storming, a stretch of adjusting to one another, testing one another, occasionally rubbing against one another, before it can finally work in harmony. So friction is natural, and at times even necessary. What deserves more attention is the team that appears never to have any friction at all. Often they are not truly at peace, but merely storing away what has not been resolved, tightly, until one day it spills out through an email with a Cc line of faintly puzzling length.
Patrick Lencioni, in his book on the five weaknesses of a team, places one thing at the very foundation: trust. Where mutual trust has not yet grown, people become hesitant to disagree in a healthy way, and the disagreement that should have been settled in the meeting room drifts instead into whispers by the water dispenser. Google, too, once ran a well-known internal study called Project Aristotle to find out what makes a team truly great. The answer turned out not to be a gathering of the smartest people. What mattered most was the sense of safety to speak, known in its original term as psychological safety. Put simply, whether each member feels safe enough to be honest, to ask a question that sounds trivial, and to admit a mistake without fear of being embarrassed. Amy Edmondson, who introduced the term, was essentially saying something very simple. A team whose members dare to speak up will outdo a team whose members are quietly clever.
The matter grows more delicate when the friction happens between teams rather than within one. Inside a single team, there is at least one superior who can step in. But when someone on Team A and someone on Team B have not yet found common ground, very often no one feels they own the bridge between them. Everyone assumes it is someone else's business. In psychology this tendency is called diffusion of responsibility, meaning that the more people who could actually act, the smaller the chance that anyone truly does. There was also a programmer named Melvin Conway who framed a small law, one that turns out to reach far beyond his own field. An organization, he said, tends to produce work whose shape mirrors its own patterns of communication. Where two parts rarely speak to each other, the seam will show in the result. Work has a quiet way of revealing the quality of the communication behind it.
So what can be done, especially by those who are not in charge and cannot simply change other people?
Perhaps it all begins with letting go of the hope that others can guess a thought that was never spoken. The communication load often arises from what experts call the curse of knowledge. Once a person understands something, they easily forget that others may not understand it yet. A two-line message is sent with the feeling that it is clear enough, and disappointment follows when it is read differently. Yet what is bright in one head is not necessarily bright in another. Adding a little context, not by lengthening the message but by clarifying it, is almost always lighter than untangling a misunderstanding later on.
The next thing is to separate the person from the problem. This old advice from Roger Fisher and William Ury in the book Getting to Yes still rings true. What should be confronted is the problem, not the person. The sentence "this report is late" speaks about a matter. The sentence "you are always late" speaks about a person. And once someone feels that they themselves are under attack, the heart closes, and the conversation turns into a contest of self-defense.
A relationship, too, is best tended before it is truly needed. Stephen Covey used the image of an emotional bank account. Every sincere greeting, every small kindness, and every kept promise is a deposit. So that one day, when someone is forced to ask for something inconvenient or to offer criticism that is not easy to hear, there is a balance to draw on. A person who appears only when they need something will always feel like a bill that arrives without knocking.
And the part most often avoided: someone has to be willing to be the bridge. When a deadlock between teams drags on, it is usually not because there is no way out, but because every side is waiting for the other to begin. Being the one who reaches out first, who picks up the phone instead of typing one more email, is not always comfortable. Yet a deadlock left alone is far more uncomfortable, and it quietly costs everyone.
In the end, communication is not merely a nice extra skill to have. It is more like the load-bearing wall of a house. The substance of the work may be fine, but if the communication collapses, the whole building of the work leans with it. Perhaps it is the skill least often practiced, and yet the one that most decides whether a person can endure and grow in their place of work.
And what about your own workplace? Is more of the work delayed because the task is genuinely hard, or because the people have not yet had the chance to talk to one another? Those stories are most welcome in the comments. (J)
