In a remote town in Alaska, about as far from Brooklyn as an American rabbi can stand, a young emissary named Berkowitz found himself in a situation no instruction had prepared him for. He was face to face with a Jewish...
In a remote town in Alaska, about as far from Brooklyn as an American rabbi can stand, a young emissary named Berkowitz found himself in a situation no instruction had prepared him for. He was face to face with a Jewish girl in a place with almost no Jewish community around her, and he needed to make her heritage feel like it belonged to her, personally, that day. There was no manual for this. There was no one senior to call. The headquarters that had sent him was thousands of miles away, and the leader whose vision had sent him could not be consulted at all.
So he did what, by then, thousands of people in his movement had learned to do. He remembered a story. As Joseph Telushkin tells it in the closing chapters of his 2014 biography Rebbe, Berkowitz recalled how the man who built the movement had always personalized an act of faith for the individual in front of him, one person at a time, and he improvised from that memory. Not from a rulebook. From a remembered scene. And the improvisation landed, because the story had carried exactly the information he needed: not what to do, but how to decide what to do.
That is the subject of this article, and it is worth saying plainly at the start. Stories are not the decoration on a family's legacy. They are the operating manual. They are the part of the inheritance that tells your children and grandchildren how to act when you are not in the room, in situations you never predicted, in places you have never been. A family that captures its stories deliberately is writing its own manual. A family that does not is trusting that manual to memory, and memory scatters.
Rabbi Menachem Mendel Schneerson, known as the Rebbe, led the Chabad-Lubavitch movement from 1951 until his death in 1994. He was, by any sober measure, one of the most consequential religious leaders of the twentieth century: he dispatched emissaries to more than a thousand communities on every inhabited continent, met individuals one on one from eight in the evening until two or three in the morning for decades, and was posthumously awarded the Congressional Gold Medal.
Then comes the fact that should stop anyone who thinks seriously about continuity. He named no successor. He had no biological children. And after his death, the movement he built did not shrink, fracture, or drift. Telushkin reports that it more than doubled.
Before going further, two notes on how we are reading this. First, on sourcing: Telushkin's biography is admiring but unusually careful. In Chapter 8 he explicitly flags and debunks the inflated legends that grew around his subject, the claim of nine doctorates, the claim of reading fifteen pages in twenty seconds, before presenting the verified record. Everything cited in this article is from that documented record, quoted as the book prints it. Second, on framing: LegacyPot is not here to borrow anyone's theology. The office of a Rebbe is a specific religious role inside a specific tradition, and it has no equivalent in your family; no parent or grandparent should be venerated the way a Chasidic community relates to its Rebbe, and we will not pretend otherwise. What we are studying is the human architecture underneath: how a community carried its values across a generational handover that had every structural reason to fail. A tradition that has transmitted values across many generations has something to teach any family that wants to do the same.
So the question stands. No successor. No heirs of the body. Continuity anyway. How?
Telushkin gives the answer in Chapter 29, and it comes with an analogy worth memorizing. The movement kept functioning, he writes, because its members were left with "a code of instruction for how to lead their lives." The Rebbe himself had used the image of a construction site: the architect draws a blueprint, and the contractor reads it and directs the plumber, the mason, the electrician. "It's not that the contractor can do it better than everybody, but he can read the blueprint." Authority did not have to sit in one irreplaceable person, because the knowledge sat in a document any trained member could read.
Now look closely at what that blueprint actually consisted of, because this is where most families misunderstand their own succession problem.
Half of it was written in the way we usually mean. More than two hundred volumes of teachings. More than ten thousand letters. A daily study cycle that put the same texts in front of every member of the movement, every day, wherever in the world they woke up.
The other half was not written at all. It was the narrative of the Rebbe's life: the stories his followers told and retold, studied and circulated, about how he treated a stranger at two in the morning, how he chose his words, how he answered a question by refusing to answer it. Telushkin's explanation for the movement's growth after 1994 is blunt: it "is the secret of its growth during his life: the Rebbe himself. By studying his teachings every day, the Rebbe's followers see him as an ever-present force." The teachings gave them the principles. The stories gave them the pattern. Together they formed something a rulebook alone can never be: a transmissible picture of how a person who holds these values behaves.
That is the full anatomy of an operating manual. Written principles plus told-and-retold stories. Most families, if they prepare anything at all, prepare only the first half, and usually only the legal sliver of it: a will, a land title, perhaps a letter. Then they are surprised when the next generation holds the assets but not the judgment.
Why do the stories matter so much? Why is the written half not enough?
Because rules under-specify reality. A rule is written in advance, by someone who cannot see the situation you will actually face. The Rebbe seems to have understood this with unusual clarity, because Telushkin records him deliberately refusing to give detailed instructions to the very people he was sending to the ends of the earth. When Rabbi Sudak asked what he should do in London, the answer was: "there are thousands of things to do in London." To Rabbi Feller, heading for Minneapolis: "In general, I cannot give you specific instructions, but you should be flexible." Telushkin notes the under-specification was intentional, so that emissaries would act "spontaneously and creatively" (Chapter 6).
This looks, at first, like a leader shirking the job of leading. It is the opposite. It is a leader who knows exactly what can and cannot be transmitted. You cannot transmit a decision for a situation you have not seen. You can transmit the values and the pattern of judgment, and then trust the person on the ground to read the ground. But that trust only works if the pattern of judgment has actually been installed, and the delivery mechanism for a pattern of judgment is not a rule. It is a story.
Think about what Berkowitz retrieved in Alaska. Not an instruction; no instruction existed for that room. He retrieved a remembered scene of how his teacher treated an individual, and the scene contained the whole method: see the person in front of you, find the role that is theirs alone, make the heritage a gift and not a weight. A story compresses a hundred rules into one memorable pattern, and unlike the rules, it travels. It survives translation, distance, and decades. It can be unpacked in situations its original teller never imagined.
Your family will face its Alaska moments. A granddaughter offered a contract in a city you have never visited, in an industry that did not exist when you were her age. A son deciding whether to sell land during a crisis that resembles nothing in your lifetime. You cannot leave them instructions for those rooms. You can leave them the stories of how you decided in your rooms: what you weighed, what you refused, what it cost, and why you would do it again. That is what they will actually reach for. People under pressure do not recall clause four of a values statement. They recall what their mother did in 1994.
There is a second mechanism in the book, quieter than the blueprint but just as instructive. Telushkin records a man who asked the Rebbe to autograph a photograph so that he could feel closer to him. The Rebbe declined, and offered something better: the man should follow the movement's daily study cycle, so that "the man and the Rebbe would connect every day as they studied the same texts" (Chapter 4).
Notice what is being claimed. Connection at a distance does not come from a souvenir. It comes from a shared practice, done separately but simultaneously: the same story, the same text, the same day, across any number of miles. The movement's members in Bangkok and Buenos Aires were not held together by a headquarters. They were held together by the fact that on any given morning they were all inside the same page.
For families, this is the difference between an archive and a living manual. A story that is captured once and filed away is a museum piece. A story that is retold on a rhythm, at a family gathering, at a monthly call, on the anniversary of the event it describes, becomes shared property. The retelling is not repetition for its own sake. Each retelling re-installs the pattern in whoever is listening, including the members who were not born when it happened, and it quietly binds the scattered ones to the same source. A family spread across three continents cannot share a compound or a table most of the year. It can share a story cycle.
One more scene from the book belongs here, because it answers a question elders often ask: which stories count?
Telushkin devotes part of Chapter 14 to the Rebbe's lifelong gratitude toward Rabbi Zalman Vilenkin, the teacher who taught him as a boy. Decades later, leading a global movement, he would stand whenever Vilenkin entered the room, explaining simply: "he put me on my feet." When Vilenkin died, the Rebbe paid for the burial and the gravestone, and asked the children to contribute one dollar each, only so that they could share in the honor of honoring their father.
Read that as a transmission mechanism and you see something easy to miss. The Rebbe was not only telling people to be grateful. He was being watched being grateful, publicly, permanently, toward the person who formed him. That performance became a story, and the story became curriculum. The generation watching learned that in this community, you honor upstream, not only endow downstream.
So when you choose which stories to capture, do not stop at your own victories. Capture the stories of the people who put you on your feet: the aunt who paid a school fee at the decisive moment, the neighbor who lent the first capital, the teacher who saw something. A family manual that contains only the founder's triumphs teaches the next generation to perform. A manual that shows the founder honoring their own teachers teaches the next generation how debts of formation are carried and repaid. That second lesson is the one that keeps a family humane across generations.
Everything above comes from Telushkin's record of a Chasidic movement headquartered in Brooklyn. The author wrote nothing about Africa, and what follows is our translation, LegacyPot's own application, offered to the families we serve.
African families are, in one sense, ahead of everyone on this subject. Ours are oral civilizations of enormous depth: clan histories, praise names, proverbs, the grandmother who could recite the lineage back seven generations, the evening retellings that were themselves a school. The idea that stories carry a family's operating knowledge is not an import here. It is the ancestral default.
But the default is under strain, and it is worth being honest about why. The retelling architecture assumed proximity: the same compound, the same village, the same fire. Migration has dissolved that assumption. The listeners are now in Kampala, Nairobi, London, Boston, on shifts and time zones that never overlap. The tellers and the audience are rarely in the same room, and the rooms they do share are shorter and busier than the ones the tradition was built for. The stories still exist. What has broken is the transmission schedule.
The answer is not to mourn the fire. It is to do deliberately what proximity once did automatically: capture the stories in the teller's own voice, hold them somewhere the whole family can reach, and put the retelling back on a calendar. The Chabad case shows that a dispersed community can stay formed by a shared story cycle across any distance, so dispersion is not the obstacle. The absence of a system is.
Here is the practical shape of the work, drawn from the anatomy above: written principles plus told stories, captured deliberately, retold on a rhythm.
Choose stories that carry judgment, not just history. Dates and begats matter, but the operating manual lives in a different kind of story. The decision stories: the hardest call you got right, and exactly what you weighed. The failure stories: the loss that taught the family a rule, told without varnish, because a manual that contains no failures teaches nobody how to recover. The origin stories: how the first plot was bought, what was sacrificed for it, so the next generation knows what the asset actually cost. The repair stories: the quarrel that was mended and how, because every family will need that pattern again.
Capture the scene, not the moral. A story flattened into its lesson loses the very thing that makes it usable. "Work hard and be honest" installs nothing. The afternoon you turned down the shortcut, who was in the room, what was said, what it cost you that year: that installs the pattern. Ask the teller for the moment. The listeners will extract the moral themselves, each time they retell it, which is precisely how a manual stays alive.
Keep the teller's voice. A transcript typed by a grandchild is better than nothing, but a recording of the actual voice, with its pauses and laughter and the phrases only that person uses, carries formation no summary can. This is what the Wisdom Library in LegacyPot is built for: a permanent place for your family's recorded and written stories, held where every member, on any continent, can return to them. Pair it with your Legacy Tree, so each story stays attached to the person and the generation it belongs to, and the manual and the map of the family grow together.
Put the retelling on a rhythm. A captured story that no one revisits is an archive, not a manual. Make one story a standing item in your Family Council: one retelling per gathering, with the youngest members present, and let the teller take questions. Between gatherings, use a Habit to keep the capture going, one recorded story a month is a modest pace that builds a formidable library within a few years. The goal is the Chabad pattern in family form: the same stories, held in common, revisited on a schedule, binding the scattered ones to the same source.
The Rebbe's movement crossed its hardest handover because its people carried a readable blueprint: written teachings, and a body of stories so well circulated that a young man in Alaska could navigate an unmapped moment by memory. Your family's blueprint is sitting in the same two places, in what you have written down, and in the stories that today live only in your telling.
So here is the decision this month, and it is deliberately small. Choose three stories: one decision you got right and how you weighed it, one failure that taught the family a rule, and one story of a person who put you on your feet. Record them in your own voice, unpolished, scene first and moral last, and place them in your family's Wisdom Library in LegacyPot. Then schedule a single retelling: one story, at your next Family Council or family gathering, with the youngest generation in the room.
Three recordings and one retelling. That is the whole assignment. It is also, quite literally, the first three pages of your family's operating manual, the beginning of the document that will one day let someone you love stand in a room you never imagined and know exactly how your family decides.