On the morning of June 12, 1994, in the Crown Heights neighborhood of Brooklyn, a movement lost the only leader most of its members had ever known. Menachem Mendel Schneerson, the rabbi his followers simply called the...
On the morning of June 12, 1994, in the Crown Heights neighborhood of Brooklyn, a movement lost the only leader most of its members had ever known. Menachem Mendel Schneerson, the rabbi his followers simply called the Rebbe, died at ninety-two. He had led the Chabad-Lubavitch movement since 1951, more than four decades, and by the standard logic of succession he had left it in an impossible position. He had no biological children. He had named no successor. There was no son, no chosen deputy, no heir in waiting to inherit the role.
Every conventional prediction pointed the same way. A movement organized around one towering figure, deprived of that figure with no plan to replace him, should fracture into feuding factions or slide quietly into decline. This is the ordinary fate of the personality-built institution. The founder dies and the thing dies with him, or splinters, or ossifies into a museum of his memory.
That is not what happened. In the decades after 1994, with no one sitting in the Rebbe's chair, the movement he had led did not shrink. It more than doubled. As Joseph Telushkin documents in his biography Rebbe: The Life and Teachings of Menachem M. Schneerson (HarperWave, 2014), a movement that had spread to hundreds of communities in his lifetime spread to well over a thousand after his death, run by people he had trained but who now answered to no living master at all.
That is the single most useful fact in this entire story for any family that has ever lost sleep over the same question in miniature. Who takes over when I am gone. What if there is no obvious one. What if the obvious one is not ready, or not willing, or not able. The Rebbe faced the movement-sized version of exactly this problem, and he did not solve it by finding a better heir. He solved it by building something that did not need one.
Set aside, for a moment, everything specific to the tradition the Rebbe belonged to. This article borrows none of the theology, the religious office, or the reverence that Chabad extends to its Rebbe. Those do not transfer to a secular family, or a Christian one, or any other, and it would be a distortion to pretend they do. What transfers is something narrower and more portable: the human architecture of how one man arranged for his values, his methods, and his mission to keep working after he could no longer be in the room.
The heart of that architecture is a decision most family principals never consciously make. Faced with the question of continuity, the default move is to pick a person. Choose the capable child, or the eldest, or the one who stayed close, and pour everything into that single vessel. It is the primogeniture instinct, and it is a coin flip on competence run once per generation, with the entire inheritance riding on the toss.
The Rebbe did the opposite. Rather than concentrate the future in one successor, he distributed it across a whole cohort of people he deliberately trained to lead. He dispatched young couples, his emissaries, to communities scattered across continents, from major cities to places as remote as Alaska, the Congo, and Nepal, and he did it not once but continuously, for decades. Each one was expected to build and run something largely on their own judgment. By the time he died, the mission did not live in him. It lived in a thousand trained minds who had already been operating semi-independently for years.
Rabbi Jonathan Sacks captured the principle in a single line that Telushkin uses as a chapter epigraph. "A good leader creates followers. A great leader creates leaders. More than the Rebbe was a leader, he created leadership in others" (Chapter 6). Read that as a diagnostic and it becomes uncomfortable for most founders. The measure of your legacy is not how indispensable you are. It is how many capable decision-makers you have produced who no longer need you at all. By that measure, a family enterprise that collapses into confusion the day its patriarch steps back has already failed, no matter how impressive it looked while he was present.
The obvious objection is that a thousand independent leaders with no central authority is not continuity. It is chaos. What stops a leaderless movement from drifting a thousand different directions until it means nothing at all.
The Rebbe answered this with an image Telushkin records in Chapter 29, and it is the most important idea in the book for our purposes. Asked how Chabad could function without him, he pointed to how a building gets built. The architect draws a blueprint. The contractor reads the blueprint and directs the plumber, the mason, the electrician. "It's not that the contractor can do it better than everybody," the Rebbe said, "but he can read the blueprint." Continuity does not require the architect to stand on the site forever. It requires a blueprint clear enough that any trained person can read it and build true to the design.
So he spent his life drawing the blueprint. Part of it was explicitly written. Telushkin records more than two hundred volumes of his talks and teachings and more than ten thousand letters, along with a daily study cycle that every member followed. A member anywhere in the world, on any given day, was reading the same page as every other member. That shared text was not decoration. It was the connective tissue that held a dispersed movement in alignment without anyone issuing orders.
But the other half of the blueprint, Telushkin is careful to note, was never written down at all. It was the narrative of the Rebbe's own life and the thousands of stories his followers told and retold about how he had handled specific situations. When an emissary in a remote place faced a problem no manual covered, he did not phone headquarters for instructions. He recalled a story. He asked, in effect, how did the Rebbe approach a moment like this, and he improvised from the pattern. Telushkin describes exactly this happening: an emissary meeting a Jewish girl in remote Alaska drew his approach not from a rulebook but from remembering the Rebbe's own way of personalizing an encounter (Chapter 29).
This is the mechanism families almost always miss. They spend enormous energy on the written blueprint, the will, the trust documents, the ownership structure, and almost none on the unwritten one, the stories that teach the next generation how the family actually thinks and decides when the documents run out. The documents tell your heirs what they own. The stories tell them who they are and how their people have handled hard things before. Only one of those two is a blueprint you can read in a situation the founder never anticipated.
There is a subtle and counterintuitive discipline underneath all of this, and it is the part most founders find hardest to imitate, because it feels like negligence.
When the Rebbe sent people out, he refused to over-specify what they should do. Telushkin records the pattern in Chapter 6. Asked by Rabbi Sudak what he should do in London, the Rebbe answered that there were "thousands of things to do in London." Told by Rabbi Feller that he needed guidance for Minneapolis, the Rebbe replied, "In general, I cannot give you specific instructions, but you should be flexible." He deliberately withheld detailed direction so that his emissaries would learn to act, in Telushkin's phrasing, spontaneously and creatively.
He extended the same discipline to questions people brought him directly. When his own secretary, a rabbi, asked him to settle a legal question, the Rebbe declined: "You're a rabbi just like me. You study the sources and you decide" (Chapter 6). To a psychologist who called for advice, he observed that sometimes a person simply needs to speak to himself. Telushkin is precise here, and so must we be: the Rebbe gave concrete, specific advice constantly, on thousands of matters. The withholding was not indifference. It was reserved, deliberately, for the moments when answering would have stunted the very growth he was trying to produce.
This is the discipline that actually builds capacity, and it is the opposite of what love usually tells a parent or a founder to do. When someone you are responsible for stands at a genuine crossroads and is capable of choosing well, the instinct is to hand them the answer. It is faster, it is safer, it spares them the anxiety of deciding. And every time you do it, you teach them that they cannot decide without you, which guarantees they will still need you at the one moment you are no longer there. The Rebbe understood that a successor who has never been trusted to read the ground and choose is not a successor. He is a dependent who will be lost the day the instructions stop coming.
Over-instruction, in other words, quietly kills the leadership you are trying to grow. The founder who cannot resist correcting every decision produces heirs who cannot make one. The founder who dispatches capable people with the mission clear and the tactics left open produces heirs who have been running things for years before the handover ever formally occurs.
There is one more piece, and it solves a problem that quietly poisons a great many family successions: the sense that the heirs can never measure up to the person who built it all.
In his very first teaching as leader, in 1951, the Rebbe took up the figure of Moses, whom he called "seventh from the first." The point, as Telushkin records it in Chapter 2, was that Moses achieved what his predecessors could not, "not because of innate superiority" but, in the Rebbe's framing, "as a result of nothing more than his being seventh from the first." The task of the new generation, he taught, is "to finish the mission of the first." Each generation, he said, "accomplished one step more and went one step further than his predecessor," and the work is now handed to the living.
Strip that of its specific religious content and what remains is a startlingly practical reframe of what it means to inherit. Under the ordinary frame, the heir is measured against the founder, and the founder always wins, because the founder is the one whose name is on the thing. The heir who merely maintains the enterprise feels like a disappointment. The heir who changes it feels like a betrayal. Either way, the comparison is a trap, and it is the reason so many capable second and third generations quietly disengage. They cannot win a contest against the person who started it all.
The Rebbe's frame removes the contest entirely. The next generation's greatness is not measured against the founder. It is measured by whether they carried the founder's unfinished work one step further than they received it. That is a standard an heir can actually meet, and meeting it makes them a link in a chain rather than a failed copy of a single great man. Succession stops being a competition the heirs are doomed to lose and becomes a relay they are equipped to run. "Be my partners," Telushkin records the Rebbe telling his followers at the outset. "We're in this together" (Chapter 2). Partners, not replacements.
Here the article extends past anything its source contains, and honesty requires saying so plainly. Joseph Telushkin wrote about a Jewish movement in the twentieth century. He wrote nothing about Uganda, nothing about Africa, nothing about extended families, customary obligation, or the way authority actually flows through a large African household. The application that follows is ours, not his, and not the Rebbe's.
With that said, the fit is unusually close, and in a direction most inheritance advice ignores. Nearly every succession model imported from elsewhere assumes a narrow family: name the one heir, pass the one estate, done. That model does not describe how a great many African families are actually built. Authority in a large extended family is already distributed. Uncles, aunts, elder siblings, and senior cousins already hold real responsibility over different branches, different obligations, different pieces of the whole. The single-heir model does not fit that reality. It fights it.
The Rebbe's architecture fits it exactly. A mission held not by one designated heir but by many trained leaders, each running their own branch on their own judgment, aligned by a shared blueprint and a shared body of stories rather than by a single boss issuing orders. That is not a foreign idea a large African family has to adopt. It is closer to a description of the family it already is, made deliberate. The task is not to force the family into a narrow European mold of one heir and one estate. It is to do consciously and well what the extended structure is already shaped to do: identify the capable people across every branch, give each of them a real portion of the mission, form their judgment until they can run it without you, and bind them together with a story clear enough to read when you are not there to consult.
A caution is owed here, and it belongs in the open rather than buried. The Rebbe held a specific religious office inside a specific tradition. His followers relate to that office in ways that have no equivalent in an ordinary family and should not be imported into one. No family elder is a spiritual conduit. No parent should be venerated the way a religious movement venerates its founder. This article does not ask you to treat anyone as more than human, and it deliberately leaves untouched the theological questions, the internal controversies, and the beliefs that are the movement's own business and not our subject.
What we are borrowing is only the human engineering of transmission, and it is entirely secular in its logic: distribute the mission across many capable people instead of one. Draw a blueprint clear enough to be read without you, written and unwritten both. Withhold the answer at genuine crossroads so that judgment develops. Frame the next generation as finishers of a shared work rather than as rivals to your memory. Those four moves owe nothing to any creed. They are simply how continuity survives the death of the person who started it, and they work whether the thing being continued is a movement, a business, or a family.
Here is the concrete move this story leaves on your desk, and you can make it this month.
Stop looking for the heir. Start mapping the generation. Open your family's Legacy Tree and do the thing the single-heir instinct never lets you do: look at every branch, not just the eldest line, and name the capable people wherever they actually are. The niece who runs her corner of things quietly and well. The son-in-law who married in and has better judgment than half the bloodline. The younger child everyone still treats as a child. Mark each one, and then, against each name, write the specific portion of the family's mission that could one day be theirs to carry. Not a share of the money. A piece of the work.
Then give the first of them something real to run this year, with the mission clear and the tactics left to them, and resist the urge to correct every move. You are not looking for the one person who will replace you. You are building the several people who, between them, will make replacing you unnecessary. The Legacy Tree is where you can see, for the first time, how many capable hands you actually have, and how few of them you have ever trusted with anything.
A movement more than doubled after its founder died because he spent his life refusing to be the one thing it depended on. A family can borrow that refusal. The question is not who inherits when you are gone. The question is how many people you have made ready, and whether the blueprint you leave is clear enough for them to read.