Ask someone who has researched their family for a decade to show you what they made.

Watch what happens. They open a laptop. They sign in. Something loads. They zoom out, then in, then apologize for the interface. They scroll to find the person they were telling you about. Somewhere in the second minute they say "hang on" for the third time.

Then they show you a rectangle the size of a paperback, and you lean in politely, and you say it's amazing — and you mean it, because it is. But you've been leaning at a laptop for four minutes and there's nothing to see except a form.

That's the finished object. Twenty years of courthouse visits, microfilm, misspelled surnames, and a cousin in Wisconsin who had the photographs. And what it amounts to, physically, in the world, is a login.

Nobody's fault

This isn't a complaint about genealogy software. The software is good, and it's aimed correctly.

A research interface has one job: help you evaluate evidence. It should show you sources, conflicts, uncertainty, alternate spellings, the fact that two records disagree about a birth year. It should be dense, because you're comparing things. It should be a workspace.

That's exactly what it is. The problem isn't that it's a bad workspace. The problem is that we've all quietly accepted the workspace as the destination — that the place where the work happens is also the place where the work ends up.

No other creative pursuit does this.

Photographers don't stop at the camera roll; they print, frame, publish, make books. Woodworkers don't leave it in the shop. Musicians don't consider the multitrack session the finished piece. Every one of those has a workspace and a separate artifact — and the artifact is the point, and the workspace is just where it got made.

Genealogy skipped that step. The workspace became the artifact by default, because for twenty years the only place a tree could exist was inside the tool that built it.

The forty-second problem

Here's the practical consequence, and it's more damaging than it sounds.

Getting to your tree takes about forty seconds. Open laptop, browser, sign in, load, navigate, zoom.

Forty seconds is nothing. Forty seconds is also, empirically, enough friction to guarantee that nobody ever does it casually. It means every single viewing of your family tree is deliberate — someone has to decide to look, and have a reason, and sit down.

Which means the tree gets seen a handful of times a year. At a holiday, when a relative dies, when a child has a school project. The rest of the time, the most researched thing in your family's history is invisible to everyone in it, including you.

Compare that to a photograph on a hallway wall. Nobody decides to look at it. They pass it four times a day for eleven years, and by the end it's part of the architecture of their memory. A wedding photo on a wall gets more attention across a decade than your family tree will get in your lifetime.

The difference isn't quality. It's that one of them requires a decision and the other doesn't.

What "one person's hobby" really means

There's a second cost, and it's the one that stings.

Because the tree lives inside an account, it's yours — singular. Your family experiences your research as something you talk about, not something they've seen. They know you're into it. They could not tell you the name of your great-great-grandmother.

That's not disinterest. Ask any of them directly whether they'd like to know where the family came from and they'll say yes and mean it. They've just never been shown, in a form that fits how humans actually absorb things, which is together, in a room, without a laptop between them.

The research got done. The transmission didn't. And transmission was the entire reason anyone starts.

The part nobody wants to think about

One more thing about tabs, and then something more cheerful.

Your tree is inside a company. Companies get acquired, change terms, sunset products, and go away. Subscriptions lapse — sometimes because someone died and nobody knew the password. Formats fall out of support. None of this is paranoia; all of it has already happened to genealogy platforms, more than once, and the field is old enough to have a graveyard.

The mitigations are boring and you already know them. Export a GEDCOM and keep it somewhere you control. Print a chart. Make something that exists outside anyone's servers.

The generalized version: if a thing you spent years on exists in exactly one place, and that place is a company, it isn't finished. Not because that company is untrustworthy, but because permanence isn't a feature any of them can actually sell you. More on getting the file out.

What finished looks like

Two things, and neither replaces the research.

Something on a wall. A printed chart in a frame. It's the oldest answer and still the best one — permanent, ownerless, and it needs no electricity, no account, and no explanation. Six generations is 126 people and it fits in a standard frame. More on printing one properly.

Something on the screen the family already looks at. The television is the largest, best-lit surface in the house, everyone in the family already faces it voluntarily, and it's black most of the day. A tree living there is one that gets seen by accident — which, as established, is the only way anything actually gets seen.

That's what we build, so treat the recommendation with appropriate suspicion. But the argument stands on its own regardless of who makes it, and you can act on it without us: print the chart, or point your existing photo screensaver at scanned family pictures. Both are free and both beat a tab.

The actual claim

Research is not the deliverable. Research is the ingredient.

The deliverable is the moment a nine-year-old points at a name on a wall and asks who that was — and somebody in the room knows, and tells them, and now two people carry it instead of one.

That moment cannot happen inside a browser tab. Not because the software is bad, but because a tab is a private place, and the whole point of family history is that it isn't supposed to be private.

You did the hard part already. The easy part is getting it out of the tab.

Keep reading: