Prosperity, Capacity, and Conflicting Values

Every year we read the story of Avraham and Lot parting ways, and every year it is easy to treat it as a brief episode on the way to the bigger moments of Lech Lecha. Yet read slowly, these few pesukim trace a sequence that anyone building an organization would do well to pay attention to.

Prosperity Experienced by All

The story opens with wealth:

Rashi asks why the Torah describes Lot this way:

Lot's wealth came from his proximity to Avraham. As Avraham prospered, so did the person walking beside him.

The operator mindset can assume the opposite: that the organization can keep growing while the people around the leader stay where they are. For a while, that may even hold. Over time, it doesn't.

A kingdom cannot be built with peasants alone. The king must appoint generals and ministers and give them real positions and real honor. The glory he shares with them is part of what makes the king, and the kingdom, glorious.

The same is true of any organization that scales. As the leader is elevated, the people around him are naturally elevated too.

This is worth holding onto when we plan. When we sit down to envision what our organizations could become, the picture should include the growth of the people who will carry us there: the infrastructure that supports them, the raises and bonuses that reflect what they have built, and the expanded roles that let them grow into the organization's next stage. Those who walk with the leader should prosper with him.

Capacity

The next pasuk:

This pasuk seems superfluous. The Torah could have moved straight to the quarrel between the shepherds and the separation that followed. Instead, it stops to tell us that the land had run out of room, and only afterward mentions the fight. The order matters: capacity ran out first, and conflict came second.

Growth consumes capacity. That is true of land, and it is true of people's time and attention. When an organization has room to spare, the team absorbs friction without anyone noticing. Someone covers for a teammate who dropped a ball. Someone picks up a task that fell between roles. People work around each other's quirks and let small disagreements pass.

As the organization grows, that room disappears. Everyone is working at full capacity, and nothing is left to absorb the friction. Differences that coexisted comfortably in a time of abundance now rub against one another and surface as disputes.

This is the moment leaders often misread: the team suddenly seems entitled, or lazy. The more accurate reading is usually that the organization has outgrown an ambiguity. Questions that never needed answering, such as who owns what, how decisions get made, and what standard the work is held to, were being absorbed quietly, either overlooked or handled by someone who had time to spare. Now no one has time to spare, and the ambiguity is demanding clarity from the leader.

The Default Response: Clarity

Then comes the quarrel:

When conflict like this surfaces, the natural response, and usually the right one, is to ask what it is revealing about the organization. A dispute carries information. It points to something left unclear that now needs defining, or something out of place that needs to be put back. Handled well, the conflict becomes the occasion for clarity, and the organization comes out of it with a sharper sense of what belongs and what doesn't.

In our story, that would have meant Avraham sitting down with Lot's camp and teaching them how pasture works: which fields are theirs, how inheritance actually functions, and where their flocks are meant to graze.

What is striking is that Avraham does none of this. He is the ish chesed, the person we would most expect to work patiently through a dispute. Instead, he goes straight to separation: "Let there be no strife between me and you... Please separate from me" (13:8–9).

That choice tells us this was a different kind of conflict.

Conflicting Values

Rashi explains what the quarrel was about:

Lot's shepherds were grazing in other people's fields and had built a line of reasoning that let them call it something other than stealing. Avraham's camp called it theft. The two camps disagreed about whether taking what belongs to others is acceptable, and that is a disagreement about values.

This is why Avraham didn't reach for clarity. Clarity resolves ambiguity. It defines what was undefined, so that people who share the same values can act on them consistently. Lot's shepherds were missing no information. Explaining the rules of pasture more carefully would only have made the disagreement more explicit.

When the problem is behavioral, there is room for clarity or coaching. When a real conflict exists between the values of an organization and the values of a team member, no amount of clarification will resolve it. You cannot teach someone to behave contrary to who they are. The best course is the one Avraham chose: to go separate ways.

Purifying the Vessel

The story continues:

Rashi comments:

For as long as Lot was in his camp, Hashem did not speak to Avraham. Once they separated, Hashem's "dibbur" returned.

The same holds for our organizations and our lives. Creating alignment means bringing clarity where ambiguity surfaces. And when values truly diverge, it requires having the difficult conversations and even parting ways with what is misaligned. That work purifies the vessel. And a vessel that has been made whole has room for blessing to flow back in.

Keep integrating,
Yosef