Family Trees Are Not Just for Fantasy: How They Solve Story Problems in Every Genre

In the summer of 2021, deep in the fourth draft of a three-generation family novel, my protagonist called her grandmother "Aunt Rosa." It was not a typo. Somewhere between the second and fourth draft I had quietly split one woman into two people, kept both names, and then let the wires cross. Chapter nineteen. Rosa had been dead for eleven years in one paragraph and was drinking coffee at a wedding, present tense, three pages later.

I did not notice until my critique group did, gently, the way you point out spinach in someone's teeth. I went back through four drafts and ninety-four thousand words with a legal pad and started drawing boxes. Grandmother. Two daughters. One son who did not speak to either sister. A husband who had died in 1987 in one chapter and 1991 in another. By the time I finished the diagram it filled two pages, and it explained, instantly, every continuity problem a beta reader had ever flagged and half the ones nobody had caught yet.

That diagram was a family tree.

I had never drawn one before, because I did not think my book needed one. It was not epic fantasy. There was no crown to inherit, no prophecy running through seven generations, no map with a kingdom on it. It was a novel about three sisters and their mother, set in one American city, over about forty years. I had assumed family trees were for Tolkien and George R. R. Martin. I was wrong, and the diagram on my legal pad is the reason I now build one for every book with more than two generations in it, whether or not a single reader ever sees it.

Here is the argument this piece is going to make, stated plainly and then earned three separate ways: a family tree is not a reference document you draw once and file away. It is a structural tool that shows you, at a glance, where a story's pressure is concentrated -- who owes whom, who resembles whom against their will, who is repeating a mistake they do not know they inherited. Genre has almost nothing to do with whether you need one. Generational depth does.

The Family Tree Is Not a Fantasy-Only Tool

The association is understandable. Appendices with dynastic charts are a genre signature of epic fantasy, from the kings listed in the back of Tolkien's appendices to the Targaryen and Stark family trees that fans redraw obsessively online. When a genre trains you to associate a tool with itself that hard, it is easy to conclude the tool is genre-specific. It is not. Tolkien needed a chart because his readers needed to track a crown across centuries. A domestic novelist needs a chart for an entirely different reason: to track resemblance.

Contemporary and literary fiction is full of multigenerational structure that has nothing to do with succession and everything to do with pattern. A mother's silence becomes a daughter's silence becomes a granddaughter's inability to ask for help. A father's temper skips a generation and lands, unexpectedly, on a favorite grandson. None of that requires a throne. It requires a writer who knows, precisely, who is whose child, who raised whom, and who was in the room when the defining thing happened. Without a tree, you hold that information loosely, in your head, across a draft that might take two or three years to finish. I have never met a writer whose memory survives that timeline intact. Mine certainly did not. I have written elsewhere about how worldbuilding only earns its place when it creates pressure on a character, and a family tree is the purest version of that principle: every branch on the chart is pressure on somebody, whether the chart belongs to a kingdom or a kitchen table.

Mystery and thriller writers know this instinctively, even if they do not call it a family tree. A story that hinges on who inherits the house, who is the secret half-sibling, who benefits from a death, is a genealogy problem wearing a plot's clothing. Romance writers building a family-opposition arc -- the Montague-Capulet shape, updated for a contemporary setting -- need to know exactly how the two families connect and where the old wound sits. The tool is the same tool. Only the genre label changes.

Why García Márquez Named Everyone Aureliano

Gabriel García Márquez's One Hundred Years of Solitude is the clearest argument I know that a family tree can be a novel's engine rather than its scaffolding. Six generations of Buendías live in Macondo, and García Márquez names them almost punishingly alike: a run of Aurelianos, a run of José Arcadios, an Amaranta and an Amaranta Úrsula two generations apart. Readers complain about this constantly, and reasonably -- some editions print a genealogical chart at the front specifically because readers could not hold the family in their heads without one.

But the repetition is not a failure of craft. It is the argument of the book made structural. The Buendías are trapped in cycles they cannot see because they are living inside them, and García Márquez enacts that entrapment at the level of naming: an Aureliano behaves like an Aureliano, a José Arcadio like a José Arcadio, generation after generation, right up until Úrsula, the family's matriarch, says the pattern out loud near the end of her long life -- that history in this family only repeats. The novel's family tree is not a study aid for the reader. It is the thesis, drawn as a diagram, and the prose is the proof.

I do not think most of us are writing a hundred years of anything. But the principle scales down cleanly. If you want a reader to feel that a trait, a wound, or a mistake is inherited rather than coincidental, the family tree is where you decide that on purpose, before you write a single scene, instead of noticing it by accident in revision the way I noticed Rosa's death date moving around my own manuscript.

East of Eden's Family Tree Is Its Thesis

John Steinbeck did something similar with far less flourish. East of Eden retells the story of Cain and Abel twice, once with Adam Trask's generation and once with his sons Cal and Aron, and the entire architecture of the book depends on the reader tracking who is echoing whom. Charles resents his brother Adam the way, a generation later, Cal will resent Aron. Adam withholds love from Cal the way his own father withheld it from him. Steinbeck said, in letters about the book, that he built the whole nine-hundred-page structure around a single Hebrew word, timshel -- thou mayest -- and the possibility that a person is not sentenced to repeat their family's sin.

You cannot land that argument without the reader tracking the family with total clarity. If a reader loses track of who is echoing whom, the parallel collapses into coincidence and the book's entire moral argument goes with it. Steinbeck needed his readers to feel the repetition as repetition, which meant he needed to control, with total precision, which details recurred and which did not. That is a family tree doing thematic work, not just continuity work. It is the difference between a chart that keeps your facts straight and a chart that tells you where your book's meaning actually lives.

I have started asking a blunt question of my own trees now, borrowed from watching Steinbeck work: if I put two people's boxes side by side, what is one generation doing that rhymes with what the other one did? If the honest answer is nothing, that is fine -- not every family needs a rhyme. But if I want the rhyme, I now build it into the chart before I build it into the prose, because a rhyme you notice in draft six is a rewrite. A rhyme you plan in the chart is a choice.

The Tree That Is Missing on Purpose

Hanya Yanagihara's A Little Life belongs on this list for the opposite reason. Jude St. Francis, the novel's central figure, has a biological family the book withholds from the reader almost entirely, in pieces, late, and it is one of the most devastating structural choices in contemporary fiction. What Yanagihara builds instead, in exhaustive and loving detail, is a found family -- Willem, JB, Malcolm, and later Harold, who becomes something closer to a father than Jude's biological family ever offered him. That relational web is not drawn as a bloodline. It functions as one anyway, complete with its own loyalties, its own resentments, its own inheritance -- of trauma, in Jude's case, and of care, in everyone else's.

This is the case that convinced me the tool is bigger than its name suggests. A family tree, as a planning document, does not require blood relation. What it requires is a clear map of who is bound to whom, how tightly, and at what cost. A found-family structure -- four college roommates, a chosen sibling group, a mentor who becomes a parent in every way that matters -- is exactly as trackable, and exactly as prone to the kind of continuity drift that hit my own manuscript, as an actual bloodline. Yanagihara tracked Jude's timeline and his friends' overlapping decades with a level of control that could not have survived on memory alone across a book that long.

If your novel has a found family instead of, or alongside, a biological one, build the tree anyway. Label the edges by what actually binds two people -- blood, marriage, an unspoken debt, a rescue -- instead of assuming the diagram only works for people who share DNA.

Inheritance Nobody Puts in a Will

Toni Morrison's Song of Solomon is, structurally, a genealogy quest. Milkman Dead spends the novel chasing his family's history backward -- through his aunt Pilate, through a half-remembered children's song, through a name, Solomon, that turns out to belong to a great-grandfather who was said to have flown back to Africa rather than live enslaved. The plot is, quite literally, Milkman filling in a family tree that has been deliberately obscured, and what he inherits at the end is not property. It is a name, and with it, a self.

Isabel Allende drew an actual family tree while writing The House of the Spirits, by her own account, because the Trueba women -- Nivea, Clara, Blanca, Alba -- pass down clairvoyance, stubbornness, and political conviction across four generations in a way the reader needs to feel accumulating, not just being told about. Min Jin Lee's Pachinko does the same work across four generations of a Korean family in Japan, where what gets inherited is not a gift but a precarious status, renegotiated by every generation under a new set of pressures. None of these books are especially interested in money changing hands. They are interested in the inheritance nobody writes into a will -- temperament, silence, ambition, shame -- and a family tree is the planning tool built to show you where that kind of inheritance is flowing before you write the scene that reveals it.

It is worth borrowing a habit from outside fiction here. Henry Louis Gates Jr., the Harvard historian who hosts Finding Your Roots, has said in interviews that the moment a guest's face changes on his show is rarely the moment they learn a single fact. It is the moment a pattern across three or four generations suddenly explains something about themselves they had never been able to name. Novelists are, in this narrow sense, doing the same job as genealogists, except we get to decide the facts in advance. The chart is where you decide, on purpose, which pattern you want your reader's face to catch.

Building a Tree Without Spoiling the Mystery

Writers who avoid family trees often tell me the same thing: they worry that mapping everything out in advance will drain the mystery, make the story feel pre-solved before they write it. I understand the instinct. I do not think it holds up. In my experience, the chart is not the reader's experience of the book. It is your private scaffolding, and nothing requires you to reveal any of it on the page in the order you built it.

The method I actually use is short enough to finish in one sitting, even for a large cast:

1. Anchor the tree to one character and one moment in time -- usually the story's present -- and work outward from there rather than trying to start at the family's founding and build forward.
2. For each person, note only four things: their relationship to the anchor, whether they are alive at the story's present, one thing they want, and one thing they know that someone else in the tree does not.
3. Draw the lines last, and label them by function rather than just by relation -- not just "mother" but "the mother she has not spoken to since the funeral" -- because the label is where the pressure lives.

That third step is the one most writers skip, and it is the one that matters most. A line labeled only "sister" tells you nothing. A line labeled "the sister who testified against her" tells you exactly which scene this relationship is going to force, eventually, whether you write toward it deliberately or stumble into it the way I stumbled into Rosa's shifting death date. Once every line on your tree carries that kind of label, the chart stops being a memory aid and starts being an outline you can read like a set of stage directions. If you would rather start from a structured page than a blank one, Plotiar's family tree template walks through the same anchor, scope, and texture fields I use for my own charts.

I keep mine as a flowchart now, not a static image, because relationships in a novel are not static either -- a marriage ends mid-book, an estrangement resolves in the last chapter, someone learns a secret that changes what a line on the chart actually means. A version you can update as the draft moves is worth more than a beautiful one you drew in week one and never touched again.

Rosa is alive in exactly one place now: chapter three, at her granddaughter's wedding, twelve years before the heart attack that the family tree on my wall tells me happens in the winter of the year the book actually starts. I know that because the chart is still taped above my desk, four sisters and two husbands and a scandal from 1974 rendered in blue ballpoint, and I check it more often than I would like to admit for a book that has no crown, no kingdom, and no reason, on the surface, to need either one at all.

Plotiar's family tree tool lives in the same project as your chapters, so the chart that keeps your generations straight is one click from the scene it is quietly running. Start a project for free and build the tree before you need it.