The Best Teams Never Settle Up

What a history of debt says about motivating people

Think of the people you have worked with for years. Someone covered a meeting when you were stuck at the airport. You took a problem off their desk when they were overwhelmed. After a while it becomes difficult to say who has done more for whom, and usually nobody tries.

That is different from a debt. Someone lends you twenty dollars. You owe twenty dollars. The precision tells you exactly when the relationship can be brought back to zero.

The barter story of motivation

In Debt: The First 5,000 Years, the anthropologist David Graeber pulls apart a story most of us learned so early that it hardly feels like a story at all. Before money, people bartered, and money came later because barter was inconvenient. Anthropologists have found little evidence that ordinary life inside communities actually worked this way. People who knew one another borrowed, remembered, returned favors later, and let obligations remain open. Direct exchange was for strangers.

He describes communities in which people were careful not to close the account. A neighbor might borrow a measure of grain and later return a little more, or a little less. Returning exactly what had been borrowed could carry the strange suggestion that the relationship was finished. Leave something unsettled and there would be a next time, and the small imbalance between two neighbors could continue for years.

The obligation survived because nobody quite settled it.

Corporate motivation

The standard model of motivation is a trade. The employee has effort, the company has money, and motivation becomes a question of price. The model is clean, measurable, and easy to explain, which is probably why it is so appealing.

But a great deal of useful work does not feel like something anyone sold. A colleague reads your draft the night before it goes to the client and sends back the three comments that save it. Someone notices a problem that belongs to another team and says something before it becomes expensive. Nobody stops to negotiate the rate for any of this. They do it because they are already inside a relationship, and because not doing it would feel wrong.

Putting a price on that kind of work changes it. A thank-you arrives with fifty points attached, or someone gets a gift card for staying late. Each one risks turning the help into a transaction with a visible ending. Do that often enough and people begin to learn which kinds of help are rewarded and which are simply expected. A payment tells the other person that you are even. A thank-you with nothing attached tells them that you are not, and that is the point.

How obligation becomes culture

A colleague carries you through a difficult week, and months later you find yourself carrying someone else, not because you owe that person anything but because that is what was done for you. The obligation does not go back to where it came from. It moves on to whoever needs it next.

That is roughly the point at which a relationship starts to turn into a culture. Something that began as one person doing a little more than the job required becomes, after enough repetitions, simply the way people here treat each other.

Feeling valued works in much the same way. Being paid what you are owed can leave a person satisfied. Being given more than the transaction required leaves them with something else, which is closer to attachment. A transactional culture keeps trying to settle the balance. A strong one is content to let it keep moving.

What this asks of a leader

None of this argues against paying people well. Salaries, bonuses and targets need numbers. The practical question is what you choose not to turn into a transaction, and where the obligations that remain are allowed to travel.

When everyone owes the boss and nobody owes each other, the team stalls the moment the boss leaves the room. When people owe each other, the team moves without the boss at the center of every exchange.

Tomorrow, start with one person who did something useful that was not strictly required. Tell them exactly what they did, why it mattered, and that you remember it.

Then give something before you know what you will get back. Make the introduction. Give someone the opportunity they are not quite ready for.

And when someone on the team needs help, resist the urge to provide all of it yourself. Ask who else could. The more those obligations travel sideways, the less the team depends on you to keep it moving.

The best teams are not the ones in which nobody owes anybody anything. They are the ones where nobody is quite keeping score.