How do we stop a family history project from stalling?

Name one editor with final say, divide work by task rather than by chapter, keep everything in one shared folder, and set a pace slow enough to survive ordinary life. Most stalls are organisational, not emotional.

What if siblings remember things differently?

Attribute rather than adjudicate. Recording that one remembers a summer evening and another remembers rain preserves both accounts, avoids overruling anyone, and is more honest than merging them.

Who should do the interviewing?

One person, consistently. Interview style shapes the answers, and rotating interviewers produces material that will not sit together in the same chapter.

Family history

How to write a life story together as a family

September 10, 2026 · 6 min read

Family life story projects stall for organisational reasons, not emotional ones. Give one person final editorial say, split the work by task rather than by chapter, keep everything in one shared place from day one, and agree in advance how disagreements about contested memories will be resolved. Projects with three equal decision-makers and no agreed process almost always stop.

One editor, several contributors

The most common failure is shared editorial control. Three siblings with equal say produces deadlock over tone, inclusion and wording, and the book stops at the point of first disagreement.

Name one person as editor at the start, with everyone else contributing material and comment. This is not about whose memory counts; it is about who breaks a tie so the work continues.

Split by task, not by chapter

Dividing a book into "you do the 1960s, I will do the 1970s" sounds efficient and rarely works, because interviews wander across decades and the two halves end up in different voices.

One person interviews and records. Consistency of approach matters more than sharing the fun part.
One handles photographs: sorting, scanning, labelling.
One handles transcription and correction.
One is the editor, assembling chapters and deciding what goes in.
Everyone contributes memories and corrections, in one place, with their name against them.

Keep everything in one place from day one

The second most common failure is material scattered across phones, inboxes and notebooks. A shared folder from the first day costs nothing and prevents the archaeology that otherwise arrives at month six.

Include recordings, transcripts, scans and a running document of corrections. Name files with dates so they sort themselves.

Agree what happens with contested memories

Siblings remember the same events differently, and the disagreement is often about something that mattered. Decide the rule before it happens rather than during the argument.

The approach that causes least damage is to attribute rather than adjudicate: "Ann remembers it as a summer evening; Peter remembers rain." Both accounts are preserved, nobody is overruled, and the reader gets something more honest than an averaged version.

Set a pace that survives ordinary life

A family project competing with jobs and childcare needs a rhythm slow enough to keep. One question a week, one call a fortnight, one scanning session a month.

Fast starts are the classic pattern: heavy activity for three weeks, then nothing. A slower cadence that runs for a year finishes books that ambitious schedules do not.

Common questions

How do we stop a family history project from stalling?: Name one editor with final say, divide work by task rather than by chapter, keep everything in one shared folder, and set a pace slow enough to survive ordinary life. Most stalls are organisational, not emotional.
What if siblings remember things differently?: Attribute rather than adjudicate. Recording that one remembers a summer evening and another remembers rain preserves both accounts, avoids overruling anyone, and is more honest than merging them.
Who should do the interviewing?: One person, consistently. Interview style shapes the answers, and rotating interviewers produces material that will not sit together in the same chapter.